Shulou(Shulou.com)06/01 Report--

Case

Environment: 2-node RAC asm + single instance DG prepares the library, which uses a file system to store data files, and ogg is deployed on one node without using ASM;RAC.

Failed to create a data file on the standby library when partitioning the table through online redefinition on the main library.

As a result, the log transfer to the slave database cannot be applied, and the slave database stops the log application.

The script for rman backup to clean up the archive cannot clean up the archive in time. The disk space of the main database and standby database is full. The ogg process does not work and the process is normal, but the time since chkpt continues to rise.

After cleaning up the archive, the standby library can receive logs but not apply them. Check that DG switchover_status is unresolvable gap. The following is the recovery of the repository.

The alert log information in the repository is as follows:

Managed Standby Recovery starting Real Time ApplyTue Apr 07 08:39:57 2015Errors in file / u01/app/oracle/diag/rdbms/centerdg/center/trace/center_dbw0_4645.trc:ORA-01186: file 63 failed verification testsORA-01157: cannot identify/lock data file 63-see DBWR trace fileORA-01111: name for data file 63 is unknown-rename to correct fileORA-01110: data file 63:'/ u01/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00063'File 63 not verified due to error ORA-01157Errors in file / u01/app/oracle/diag/rdbms/centerdg/center/trace/center_dbw0_4645.trc:ORA-01186: file 201failed verification testsORA-01157: cannot identify/lock data file 201- see DBWR trace fileORA-01110: data file 201:'+ DATA'File 201not verified due to error ORA-01157MRP0: Background Media Recovery terminated with error 1111Errors in file / u01/app/oracle/diag/rdbms/centerdg/center/trace/center_pr00_5770.trc:ORA-01111: name for data file 63 is Unknown-rename to correct fileORA-01110: data file 63:'/ u01/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00063'ORA-01157: cannot identify/lock data file 63-see DBWR trace fileORA-01111: name for data file 63 is unknown-rename to correct fileORA-01110: data file 63:'/ u01/app/oracle/product/11.2.0/db_1/dbs/UNNAMED00063'Managed Standby Recovery not using Real Time ApplySlave exiting with ORA-1111 exception

How to deal with it:

1. Stop ogg

two。 Set the partition table space cdtbs_par2-10, idxtbs_2-10 readonly [the table space comes from the following query create_change# > the current SCN number of the slave database, in which the cdtbs_par1 of the slave database is not found, but not found].

3. Copy the data file corresponding to the partition tablespace.

4. Add more, do the recovery.

Specific operations:

1. Set the tablespace to read only:

-- find out the scn number of the repository before that.

Select current_scn from vault database share 10329528031425

-- query on the main database

Select 'alter tablespace' | | b.name | | 'read only;' from v$datafile a makeshift tablespace b where a.CREATION_CHANGE# > = 10329528031425and a.TShumb.TSystole alter tablespace CDTBS_PAR2 read only;alter tablespace CDTBS_PAR3 read only;alter tablespace CDTBS_PAR4 read only;alter tablespace CDTBS_PAR5 read only;alter tablespace CDTBS_PAR6 read only;alter tablespace CDTBS_PAR7 read only;alter tablespace CDTBS_PAR8 read only;alter tablespace CDTBS_PAR9 read only;alter tablespace CDTBS_PAR10 read only;alter tablespace IDXTBS_2 read only;alter tablespace IDXTBS_3 read only Alter tablespace IDXTBS_4 read only;alter tablespace IDXTBS_5 read only;alter tablespace IDXTBS_6 read only;alter tablespace IDXTBS_7 read only;alter tablespace IDXTBS_8 read only;alter tablespace IDXTBS_9 read only;alter tablespace IDXTBS_10 read only

-- because it is found that there is no data file corresponding to the cdtbs_par1 tablespace on the slave database, the processing method is as above, first read only and then statically copy to the slave database.

Alter tablespace CDTBS_PAR1 read only

two。 Copy the file to the repository.

First copy from ASM to the local file system:

Cp CDTBS_PAR1.345.875609233 / home/gridcp CDTBS_PAR2.346.875609279 / home/grid/archcp CDTBS_PAR3.347.875609293 / home/grid/archcp CDTBS_PAR4.348.875609307 / home/grid/archcp CDTBS_PAR5.349.875609319 / home/grid/archcp CDTBS_PAR6.350.875609333 / home/grid/archcp CDTBS_PAR7.351.875609345 / home/grid/archcp CDTBS_PAR8.352.875609359 / home/grid/archcp CDTBS_PAR9.353.875609371 / home / grid/archcp CDTBS_PAR10.354.875609385 / home/grid/archcp IDXTBS_10.363.875609811 / home/grid/archcp IDXTBS_2.355.875609535 / home/grid/archcp IDXTBS_3.356.875609679 / home/grid/archcp IDXTBS_4.357.875609687 / home/grid/archcp IDXTBS_5.358.875609693 / home/grid/archcp IDXTBS_6.359.875609699 / home/grid/archcp IDXTBS_7.360.875609707 / home/grid/archcp IDXTBS_8.361. 875609713 / home/grid/archcp IDXTBS_9.362.875609719 / home/grid/arch

Grid users copy scp directly, for example:

Scp CDTBS_PAR10.354.875609385 oracle@host:/datadg/center/datafilescp CDTBS_PAR [3, 4, 5, 6] * oracle@host:/datadg/center/datafile

-- multiple copies at the same time, batch test example sentences:

Scp IDXTBS_ [2, 3, 4] * oracle@host:/datadg/center/datafilescp IDXTBS_ [5, 6, 7, 8, 9] * oracle@host:/datadg/center/datafile

PS: after copying, it is found that the file permissions are correct, but the file names on the slave library are all converted to lowercase. In order to avoid case sensitivity of linux system file names, rename the file names to lowercase, but did not verify whether uppercase file names are affected.

3. The main database makes additional backup based on the SCN number of the standby database.

-- assign multi-channel to speed up, and it takes a long time to recover without multi-channel.

Add to the main library:

Rman target / run {allocate channel C1 type disk;allocate channel c2 type disk;allocate channel c3 type disk;allocate channel c4 type disk;BACKUP INCREMENTAL FROM SCN 10329528031425 DATABASE FORMAT'/ home/oracle/upstd_%U_%p' tag 'upstd';release channel C1 to release channel c2 to channel c3 to release channel c4;} backup current controlfile for standby format' / home/oracle/upstdctl_%U'

4. Prepare the operation on the library and clean up the problematic data files:

Alter system set standby_file_management=manual;alter database create datafile'/ u01 offline drop; apprenticespact oracleUniproductUniverse 11.2.0Unixamed00063' as'/ datadg/center/datafile/cdtbs_par1.345.875609233'; alter database datafile'/ alter database datafile'/ u01applash oracleUniproductActure11.2.0pxamed00063' offline drop; should be equivalent to the above two sentences, but not verified. -- then the static read only copies the corresponding data file to alter system set standby_file_management=auto

5. Restore on standby database

Rman target / catalog start with'/ home/oracle/dgbak'; recover database noredo; shutdown immediate;STARTUP NOMOUNT;RESTORE STANDBY CONTROLFILE FROM'/ home/oracle/dgbak/upstdctl_9uq3rv22_1_1';alter database mount;RMAN > alter database open;RMAN-00571: = RMAN-00569: = ERROR MESSAGE STACK FOLLOWS = RMAN-00571: = RMAN-03002: failure of alter db command at 04max 08 16:32:47ORA-10458: standby database requires recoveryORA-01194: file 1 needs more recovery to be consistentORA-01110: datafile 1:'/ datadg/center/datafile/system.260.797342827'

Continue to operate on the repository:

SQL > set num 50SQL > select current_scn from vault database; apply log SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION; SQL > select file#,status,name from vault datafile; SQL > select * from vested dataguardstatus; ARC4: Beginning to archive thread 1 database 171370 (10331448528074-10331448899608) SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE cancel; SQL > alter database open read only; SQL > ALTER DATABASE RECOVER MANAGED STANDBY DATABASE using current logfile DISCONNECT FROM SESSION

Additional information related to subsequent DG

Prepare the database application log and some information in alert when opening to read only status:

Although the prompt information in the alert log of some operations on the repository is displayed as an error message, it can be ignored and is just an information prompt.

Mount status cancels log application error ORA 16037:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCELMRP0: Background Media Recovery cancelled with status 16037Errors in file / u01/app/oracle/diag/rdbms/centerdg/center/trace/center_pr00_6282.trc:ORA-16037: user requested cancel of managed recovery operationThu Apr 09 08:32:09 2015Recovery restored data files to a consistent state at change 10331906716894Thu Apr 09 08:32:10 2015MRP0: Background Media Recovery process shutdown (center) Thu Apr 09 08:32:10 2015Managed Standby Recovery Canceled (center) Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCELThu Apr 09 08:32:38 2015

Open the slave library and prompt that the temporary tablespace data file cannot be locked and can be ignored, and the temporary tablespace will be processed automatically:

Data Guard Broker initializing...Data Guard Broker initialization completeThu Apr 09 08:32:41 2015SMON: enabling cache recoveryDictionary check beginningThu Apr 09 08:32:46 2015RFS [6]: Selected log 26 for thread 2 sequence 189031 dbid-68775212 branch 797342936Thu Apr 09 08:32:53 2015Errors in file/ u01/app/oracle/diag/rdbms/centerdg/center/trace/center_dbw0_4855.trc:ORA-01157: cannot identify/lock data file-see DBWR trace fileORA-01110: data file:'+ DATA/center/tempfile/temp.264 .797342939'ORA-17503: ksfdopn:2 Failed to open file + DATA/center/tempfile/temp.264.797342939ORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15077: could not locate ASM instance serving a required diskgroupORA-29701: unable to connect to Cluster Synchronization ServiceErrors in file/ u01/app/oracle/diag/rdbms/centerdg/center/trace/center_dbw0_4855.trc:ORA-01186: file 201failed verification testsORA-01157: cannot identify/lock data file 201- see DBWR trace fileORA-01110: data file 201: '+ DATA/center/tempfile/temp.264.797342939'File 201 not verified due to error ORA-01157Thu Apr 09 08:32:53 2015Dictionary check completeCannot re-create tempfile + DATA/center/tempfile/temp.264.797342939 The same name file existsErrors in file/ u01/app/oracle/diag/rdbms/centerdg/center/trace/center_dbw0_4855.trc:ORA-01157: cannot identify/lock data file 201-see DBWR trace fileORA-01110: data file 201:'+ DATA/center/tempfile/temp.264.797342939'ORA-17503: ksfdopn:2 Failed to open file + DATA/center/tempfile/temp.264.797342939ORA-15001: diskgroup "DATA" does not exist or is not mountedORA-15077: could not locate ASM instance serving a required diskgroupORA-29701: Unable to connect to Cluster Synchronization ServiceDatabase Characterset is ZHS16GBKNo Resource Manager plan activereplication_dependency_tracking turned off (no async multimaster replication found) Thu Apr 09 08:32:55 2015Archived Log entry 485 added for thread 2 sequence 189030 ID 0xfd3d5b54 dest 1:Physical standby database opened for read only access.Completed: alter database open read only

The library has been restored successfully by this time.

A case of gap sequence repair based on Data Guard is attached, but no data file is created.

Http://www.xifenfei.com/1176.html

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.