MRP0-Background Media Recovery terminated with error 1111

Source: Internet
Author: User

MRP0-Background Media Recovery terminated with error 1111

Due to the improper configuration of db_file_name_convert, the data file cannot be automatically synchronized to the standby database for troubleshooting.
Check Master/Slave log Synchronization
SQL> select max (sequence #) from v $ archived_log;
MAX (SEQUENCE #)
--------------
386952
SQL> select max (sequence #) from v $ archived_log where applied = 'yes ';
MAX (SEQUENCE #)
--------------
386932
Check alter log
Managed Standby Recovery starting Real Time Apply
Thu Apr 07 10:04:08 2016
Errors in file/app/Oracle/diag/rdbms/pgsadg/trace/pgsadg_dbw0_31401.trc:
ORA-01186: file 35 failed verification tests
ORA-01157: cannot identify/lock data file 35-see DBWR trace file
ORA-01111: name for data file 35 is unknown-rename to correct file
ORA-01110: data file 35: '/app/oracle/product/11.2.0/db_1/dbs/unnamed00035'
File 35 not verified due to error ORA-01157
MRP0: Background Media Recovery terminated with error 1111
Errors in file/app/oracle/diag/rdbms/pgsadg/trace/pgsadg_pr00_5529.trc:
ORA-01111: name for data file 35 is unknown-rename to correct file
ORA-01110: data file 35: '/app/oracle/product/11.2.0/db_1/dbs/unnamed00035'
ORA-01157: cannot identify/lock data file 35-see DBWR trace file
ORA-01111: name for data file 35 is unknown-rename to correct file
ORA-01110: data file 35: '/app/oracle/product/11.2.0/db_1/dbs/unnamed00035'
Managed Standby Recovery not using Real Time Apply
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION
Recovery Slave PR00 previusly exited with exception 1111
MRP0: Background Media Recovery process shutdown (pgsadg)

Check the db_file_name_convert parameter configuration.
SQL> show parameter conver

NAME TYPE VALUE
-----------------------------------------------------------------------------
Db_file_name_convert string + DATA_JD_DG/pgs/datafile/,/da
Ta/pgs/datafile/, + DATA_JD_DG/
Pgs/tempfile/,/data/pgs/tempf
Ile/

Select file_name, file_id from dba_data_files where file_id = 35;
FILE_NAME FILE_ID
--------------------------------------------------------------
/App/oracle/product/11.2.0/db_1/dbs/UNNAMED00035

$ Ls-l/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00035
Ls: cannot access/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00035: No such file or directory

The error occurs because the tablespace is created on the disk group FRAJD_DG other than the db_file_name_convert parameter, and the path cannot be converted, causing data files to fail to be synchronized.

Solution:
The slave database modifies the db_file_name_convert parameter configuration and adds the new disk group conversion to the parameter.
Alter system set db_file_name_convert = '+ DATA_JD_DG/pgs/datafile/', '/data/pgs/datafile/', '+ DATA_JD_DG/pgs/tempfile /', '/data/pgs/tempfile/', '+ FRAGT_DG/pgs/datafile/', '/data/pgs/datafile/', '+ DATA_GT_DG/pgs/datafile /', '/data/pgs/datafile/', '+ FRAJD_DG/pgs/datafile/', '/data/pgs/datafile/' scope = spfile;
Restart the slave database. You can only start the database to the mount status:
Shutdown immediate
Startup mount;

Change the standby_file_management parameter of the slave database to the manual management mode.
SQL> alter system set standby_file_management = 'manual' scope = both;

System altered.

Put the UNNAMED data file in the correct path
SQL> alter database create datafile '/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00035 'as'/data/pgs/datafile/tbs_rpt_data.256.908316191 ';

Database altered.

Change the standby_file_management parameter of the standby database back to the automatic mode.
SQL> ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT = AUTO scope = both;

System altered.

Enable real-time application log Synchronization
SQL> alter database recover managed standby database using current logfile disconnect;

Database altered.

SQL> SELECT PROCESS, STATUS, THREAD #, SEQUENCE #, BLOCK #, BLOCKS, PID FROM V $ MANAGED_STANDBY;

Process status thread # SEQUENCE # BLOCK # BLOCKS PID
-----------------------------------------------------------------------
Arch closing 2 9028 6144 382 5627
Arch connected 0 0 0 5629
Arch connected 0 0 0 5631
Arch closing 1 386953 61440 223 5633
Rfs idle 0 0 0 5982
Rfs idle 1 386954 91968 1 5986
Rfs idle 0 0 0 5988
Rfs idle 0 0 0 6014
Rfs idle 0 0 0 6018
Rfs idle 2 9029 14418 1 6020
MRP0 APPLYING_LOG 2 9021 9118 104400 9409

11 rows selected.

Select file_name, file_id from dba_data_files where file_id = 35;
FILE_NAME FILE_ID
--------------------------------------------------------------
/Data/pgs/datafile/tbs_rpt_data.256.908385191 35

$ Ls-l/data/pgs/datafile/tbs_rpt_data.256.908425191
-Rw-r ----- 1 oracle oinstall 17179877376 Apr 7/data/pgs/datafile/tbs_rpt_data.256.908425191

SQL> select max (sequence #) from v $ archived_log;

MAX (SEQUENCE #)
--------------
386953

SQL> select max (sequence #) from v $ archived_log where applied = 'yes ';

MAX (SEQUENCE #)
--------------
386937

SQL> SELECT PROCESS, STATUS, THREAD #, SEQUENCE #, BLOCK #, BLOCKS, PID FROM V $ MANAGED_STANDBY;

Process status thread # SEQUENCE # BLOCK # BLOCKS PID
-----------------------------------------------------------------------
Arch closing 2 9028 6144 382 5627
Arch connected 0 0 0 5629
Arch connected 0 0 0 5631
Arch closing 1 386953 61440 223 5633
Rfs idle 0 0 0 5982
Rfs idle 1 386954 113192 2 5986
Rfs idle 0 0 0 5988
Rfs idle 0 0 0 6014
Rfs idle 0 0 0 6018
Rfs idle 2 9029 18285 1 6020
MRP0 APPLYING_LOG 1 386939 90 307616 9409

11 rows selected.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;

Database altered.

SQL> alter database open;

Database altered.

SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT FROM SESSION;

Database altered.

SQL> select max (sequence #) from v $ archived_log where applied = 'yes ';

MAX (SEQUENCE #)
--------------
386953

SQL> select max (sequence #) from v $ archived_log;

MAX (SEQUENCE #)
--------------
386953

Created by Tony. Tang [TangYun] 2016.04
------------- End -----------------

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian

Important configuration parameters of Oracle Data Guard

Configure Oracle 11g Data Guard based on the same host

Explore Oracle 11g elastic uard

Oracle Data Guard (RAC + DG) archive deletion policies and scripts

Role conversion for Oracle Data Guard

FAL gap in Oracle Data Guard logs

Oracle 11g Data Guard Error 16143 Heartbeat failed to connect to standby

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.