ORACLE12Credo exception recovery test-patch-based recovery complete

In the previous article, we deleted redo and made cdbopen successful through unconventional methods, but pdb could not mount normally. by querying mos, we determined it was bug16784143. For details, see: ORACLE12Credo exception recovery test-some PDBs are not open normally. After applying the 12.1.0.3 patch to the database, it is found that the pdb of the damaged database cannot be open normally,

In the previous article, we deleted redo and made cdb open successful through unconventional methods, but pdb could not mount normally. by querying mos, it was determined to be bug 16784143. For details, see: ORACLE 12C redo exception recovery test-some pdb are not open normally. After applying the 12.1.0.3 patch to the database, it is found that the pdb of the damaged database cannot be open normally,

In the previous article, we deleted redo and made cdb open successful through unconventional methods, but pdb could not mount normally. by querying mos, it was determined to be bug 16784143. For details, see: ORACLE 12C redo exception recovery test-some pdb are not open normally,After applying the patch 12.1.0.3 to the database, it is found that the pdb of the damaged database cannot be opened normally. However, if the pdb of the database is patched before the patch is damaged, it can be opened normally.
Patch Information

C:\Users\XIFENFEI>E:\oracle\product\11.2.0\dbhome_1\OPatch\opatch lspatches17977915;WINDOWS DB BUNDLE PATCH 12.1.0.1.3 (64bit): (17977915)

Session 1

XIFENFEI_CDB $ ROOT @ SYS> show con_name; CON_NAME------------------------------CDB $ ROOTXIFENFEI_CDB $ ROOT @ SYS> create table t_xifenfei as select * from dba_users; the table has been created. XIFENFEI_CDB $ ROOT @ SYS> delete from t_xifenfei; 35 rows have been deleted. XIFENFEI_CDB $ ROOT @ SYS>

Session 2

XIFENFEI_CDB $ ROOT @ SYS> show con_name; CON_NAME------------------------------PDB1XIFENFEI_CDB $ ROOT @ SYS> create table t_xifenfei as select * from dba_users; the table has been created. XIFENFEI_CDB $ ROOT @ SYS> delete from t_xifenfei; 36 rows have been deleted. XIFENFEI_CDB $ ROOT @ SYS>

Session 3

XIFENFEI_CDB $ ROOT @ SYS> alter session set container = pdb2; the session has been changed. XIFENFEI_CDB $ ROOT @ SYS> alter database open; the database has been changed. XIFENFEI_CDB $ ROOT @ SYS> show con_name; CON_NAME------------------------------PDB2XIFENFEI_CDB $ ROOT @ SYS>

Session 4

XIFENFEI_CDB $ ROOT @ SYS> shutdown abort; the ORACLE routine has been disabled.

Delete all redo and start the database

C: \ Users \ XIFENFEI> sqlplus/as sysdbaSQL * Plus: Release 12.1.0.1.0 Production on Sunday March 30 21:07:55 2014 Copyright (c) 1982,201 3, Oracle. All rights reserved. Already connected to idle routines. Idle> startup mount; the ORACLE routine has been started. Total System Global Area 400846848 bytesFixed Size 2440024 bytesVariable Size 289408168 bytesDatabase Buffers 100663296 bytesRedo Buffers 8335360 bytes database loaded. Idle> alter database open; alter database open * 1st Line Error: ORA-00313: Unable to open member ORA-00312 for log group 3 (for thread 1): Online log 3 thread 1: 'e: \ APP \ XIFENFEI \ ORADATA \ XIFENFEI \ REDO03.LOG 'ora-27041: file OSD-04002 cannot be opened: file O/S-Error cannot be opened: (OS 2) the system cannot find the specified file. Try restoring database 1 idle> select status, group # from v $ log; status group # ------------------ INACTIVE 1 CURRENT 3 INACTIVE 2 idle> recover database until cancel; ORA-00279: change 2821739 (generated at 03/30/2014 20:58:39) ORA-00289 required for thread 1: Recommended: E: \ APP \ XIFENFEI \ FAST_RECOVERY_AREA \ XIFENFEI \ ARCHIVELOG \ 2014_03_30 \ o%mf_%36 _ % U_.ARCORA-00280: change 2821739 (for thread 1) Specify the log in sequence #36: {= suggested | filename | AUTO | CANCEL} autoORA -00308: Unable to open archive log 'e: \ APP \ XIFENFEI \ FAST_RECOVERY_AREA \ XIFENFEI \ ARCHIVELOG \ 2014_03_30 \ o1_mf_000036 _ % U_.ARC 'ORA-27041: Unable to open file OSD-04002: unable to open file O/S-Error: (OS 2) the system cannot find the specified file. ORA-00308: Unable to open archive log 'e: \ APP \ XIFENFEI \ FAST_RECOVERY_AREA \ XIFENFEI \ ARCHIVELOG \ 2014_03_30 \ o1_mf_000036 _ % u_.arc' ORA-27041: Unable to open file OSD-04002: unable to open file O/S-Error: (OS 2) the system cannot find the specified file. ORA-01547: Warning: RECOVER successful but open resetlogs will see the following error ORA-01194: File 1 requires more recovery to maintain consistency ORA-01110: Data File 1: 'e: \ APP \ XIFENFEI \ ORADATA \ XIFENFEI \ SYSTEM01.DBF 'idle> alter database open resetlogs; alter database open resetlogs * row 1st error: ORA-01194: file 1 requires more recovery to maintain consistency ORA-01110: Data File 1: 'e: \ APP \ XIFENFEI \ ORADATA \ XIFENFEI \ SYSTEM01.DBF 'idle> alter system set "_ allow_resetlogs_uption" = true scope = spfile; the system has changed. Idle> shutdown immediateORA-01109: the database has not been opened and the database has been detached. The ORACLE routine has been disabled. Idle> startup mount; the ORACLE routine has been started. Total System Global Area 400846848 bytesFixed Size 2440024 bytesVariable Size 289408168 bytesDatabase Buffers 100663296 bytesRedo Buffers 8335360 bytes database loaded. Idle> recover database until cancel; ORA-00279: Change 2821739 (generated at 20:58:39) ORA-00289 required for thread 1: Recommended: E: \ APP \ XIFENFEI \ FAST_RECOVERY_AREA \ XIFENFEI \ ARCHIVELOG \ 2014_03_30 \ o1_mf_000036 _ % U_.ARCORA-00280: Change 2821739 (for thread 1) Specify the log in sequence #36: {= suggested | filename | AUTO | CANCEL} cancelORA-01547: Warning: RECOVER successful but open resetlogs will have the following error ORA-01194: File 1 requires more recovery to maintain consistent ORA-01110: data File 1: 'e: \ APP \ XIFENFEI \ OR ADATA \ XIFENFEI \ SYSTEM01.DBF 'ora-01112: Disabled media recovery idle> alter database open resetlogs; alter database open resetlogs * 1st row error: ORA-01092: ORACLE instance terminated. disconnection forcedORA-00704: bootstrap process failureORA-00704: bootstrap process failureORA-00600: internal error code, arguments: [2662], [0], [2821746], [0], [2822649], [4194545], [], [], [], [], [], [] process ID: 6880 session ID: 242 serial number: 3 idle> Startup mount; SP2-0642: SQL * Plus internal error status 2133, context 3114: 0: 0 continue execution will be unsafe ORA-03114: not connected to ORACLE -- Solve dul problems with bbed, new Problem: Line idle> alter database open; alter database open * 1st error: ORA-01092: ORACLE instance terminated. disconnection forcedORA-00600: internal error code, arguments: [4194], [61], [4], [], [], [], [], [], [], [], [], [] process ID: 5932 session ID: 242 serial number: 3 idle> alter system set UNDO_MANAGEMENT = 'manaul' SCO PE = SPFILE; the system has been changed. Idle> shutdown immediate; ORA-01109: the database is not open and has been detached. The ORACLE routine has been disabled. Idle> startup mount; the ORACLE routine has been started. Total System Global Area 400846848 bytesFixed Size 2440024 bytesVariable Size 281019560 bytesDatabase Buffers 109051904 bytesRedo Buffers 8335360 bytes database loaded. Idle> alter database open; the database has been changed. [/Sqlopen pdb1idle> alter session set iner = pdb1; the session has been changed. Idle> alter database open; the database has been changed. Idle> alter session set container = pdb2; the session has been changed. Idle> alter database open; the database has been changed. Idle> alter session set container = pdb1; the session has been changed.

ORACLE 12C may not have too few bugs. If you are eager for 12C, we strongly recommend that you set the first patch to minimize the number of bugs.

• ORACLE 12C redo exception recovery test-some pdb are not open
• ORACLE 12C control file exception recovery
• Database recovery experience ORA-00600 [3705]
• Promote the database scn by modifying the control file scn
• Current redo damage due to abnormal power failure
• Record 8.0.5 database recovery process
• ORACLE 12C ORA-07445 [ktuhistrecusespontmain () + 1173] restore
• Recover the backup control file and avoid opening the database using resetlogs.

Original article address: ORACLE 12C redo exception recovery test-patch recovery complete, thanks to the original author for sharing.