Skip to main content

ORA-01111: name for data file 975 is unknown - rename to correct file MRP0: Background Media Recovery terminated with error 1111

 ORA-01111: name for data file 975 is unknown - rename to correct file  MRP0: Background Media Recovery terminated with error 1111

Issue: 

Standby database throws below errors and stops the MRP. 

MRP0: Background Media Recovery terminated with error 1111

Errors in file /u01/app/oraprod/diag/diag/rdbms/sprod/SPROD1/trace/SPROD1_pr00_23061.trc:

ORA-01111: name for data file 975 is unknown - rename to correct file

ORA-01110: data file 975: '/u01/app/oraprod/11.2.0.4/dbs/UNNAMED00975'

ORA-01157: cannot identify/lock data file 975 - see DBWR trace file

ORA-01111: name for data file 975 is unknown - rename to correct file

ORA-01110: data file 975: '/u01/app/oraprod/11.2.0.4/dbs/UNNAMED00975'

Recovery Slave PR00 previously exited with exception 1111

Solution:

- Please cancel the managed recovery by

SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

- Set standby_file_management=manual

SQL>ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=MANUAL;

If the physical standby database is RAC, then please make the change to all standby instances.

SQL>ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=MANUAL SID='*';


alter database create datafile '/u01/app/oraprod/11.2.0.4/dbs/UNNAMED00975' as '+DATA_DG' size 30g;

- Set standby_file_management=auto 

SQL>ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO;

If the physical standby database is RAC, then please make the change to all standby instances.   

SQL>ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT=AUTO SID='*';


- Start managed recovery by  

SQL>ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;







Comments

Post a Comment

Popular posts from this blog

Warning Message When Creating A Keystore

  Warning Message When Creating A Keystore When we try to list the contents of the keystore, using the below command, keytool -list -v -keystore adkeystore.dat Enter keystore password: Keystore type: JKS Keystore provider: SUN Your keystore contains 1 entry Alias name: prod_apps002 Creation date: Jan 26, 2012 Entry type: PrivateKeyEntry Certificate chain length: 1 Certificate[1]: Owner: CN=PROD_apps002, OU=apps, O=apps002, C=US Issuer: CN=PROD_apps002, OU=apps, O=apps002, C=US Serial number: 4f208085 Valid from: Thu Jan 26 01:21:57 AST 2012 until: Tue Jan 16 01:21:57 AST 2052 Certificate fingerprints:          MD5:  XX: XX XX XX          SHA1:  XX: XX XX XX          SHA256:  XX: XX XX XX Signature algorithm name: SHA1withDSA Subject Public Key Algorithm: 1024-bit DSA key Version: 3 ******************************************* ******************************************* Warning: The JKS keystore...
Post a Comment
Read more

CLEARING an ADOP patching session

In some case adop prepare phase fails due to some issues and if you wish to apply any patch in hotpatch mode, it will fail with below errors [STATEMENT] There is already a session which is incomplete. Details are: [STATEMENT]     Session Id: 2 [STATEMENT]     Prepare phase status: R [STATEMENT]     Apply phase status: N [STATEMENT]     Cutover  phase status: N [STATEMENT]     Abort phase status: N [STATEMENT]     Session status: F [ERROR]     Cannot apply hotpatch as another online patching cycle is going on [ERROR]     Unrecoverable error occured. Exiting the current session. [STATEMENT] [START 2019/10/22 16:13:00] Unlocking sessions table [STATEMENT] [END   2019/10/22 16:13:00] Unlocking sessions table [STATEMENT] Log file: /adop_20191022_161221.log [STATEMENT] [START 2019/10/22 16:13:02] Unlocking sessions table [STATEMENT] [E...
4 comments
Read more

XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator.

  XX_XXXXXXX is not a valid responsibility for the current user. Please contact your System Administrator. Issue : When user logs into EBS, he gets the following Error :  xx_XXXXX  is not a valid responsibility for the current user. Please contact your System Administrator. Solution: 1. Check if the responsibility is end dated.  Extend the end-date if required and try to login again.  2. Check the profile option  Applications Start Page for the user ( User Level). If there is any value defined, remove it and save it. Try to login again and it worked in our case.  Before: After:
Post a Comment
Read more