My Oracle Support Banner

Dataguard Physical Apply stops after ORA-00242 maximum allowed filename records used up in control file (Doc ID 1501420.1)

Last updated on JANUARY 09, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.2.0 [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

The dataguard physical standby recovery stopped with an error. ora-00242: maximum allowed filename records used up in control file.

 

SQL> select type, record_size, RECORDS_TOTAL, RECORDS_USED from v$controlfile_record_section;

 

shows 

 

TYPE RECORD_SIZE RECORDS_TOTAL RECORDS_USED
---------------------------- ----------- ------------- ------------
DATABASE 316 1 1
CKPT PROGRESS 8180 35 0
REDO THREAD 256 32 2
REDO LOG 72 1024 22
DATAFILE 520 32767 138
FILENAME 524 65535 65535 <<<65,535 filenames in use. 
TABLESPACE 68 32767 9
TEMPORARY FILENAME 56 32767 2
RMAN CONFIGURATION 1108 50 4
LOG HISTORY 56 33012 17964
OFFLINE RANGE 200 1063 0

 

Where all the possible number of file names have been used up. 

 

SQL> select FNNAME, FNFLG from x$kccfn;

 

Also shows 65,535 entries. 

 

The Media Recovery Process (MRP) will also have an entry in the alert log 

 

MRP0: Background Media Recovery terminated with error 242  

 

The value of db_file_retention_target is set to a high value (90 days).                             



Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.