Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about how to deal with noarchive database current redo log damage and no backup. Many people may not know much about it. In order to make you understand better, the editor summarized the following content for you. I hope you can get something according to this article.

Yesterday, an oracle database caused current due to a disk problem.

The redo log is damaged and the database cannot be started after the down machine.

Environment: windows2003 + oracle 9i

Do the following:

Startup mount

Create pfile from spfile

Shudown immediate

After shutting down the current database, copy all the\ ora92\,\ oradata\ yw\ directories under oracle, and back up the password file and pfile.

A new oracle is installed on another computer, and the library is rebuilt with the same instance name and database name as before-yw.

Overwrite the new library's\ ora\ data\ yw\ with the backup\ oradata\ yw\.

Overwrite the original password file and pfile.

Add to pfile:

_ _ ALLOW_RESETLOGS_CORRUPTION=TRUE

SQL > startup mount pfile=c:\ oracle\ ora92\ database\ INITyw.ora

ORACLE instance started.

Total System Global Area 2483027968 bytes

Fixed Size 2074760 bytes

Variable Size 1090520952 bytes

Database Buffers 1375731712 bytes

Redo Buffers 14700544 bytes

Database mounted.

SQL > recover database until cancel

Enter cancel

SQL > alter database open resetlogs

Alter database open

*

ERROR at line 1:

ORA-01092: ORACLE instance terminated. Disconnection forced

SQL > alter database open

View the alert_yw.log file:

RESETLOGS after incomplete recovery UNTIL CHANGE 9431879262014

Resetting resetlogs activation ID 3761166285 (0xe02ed7cd)

Online log 2 of thread 1 was previously cleared

Online log 3 of thread 1 was previously cleared

Mon Dec 21 14:43:32 2009

Assigning activation ID 3761145403 (0xe02e863b)

Thread 1 opened at log sequence 1

Current log# 1 seq# 1 mem# 0: d:\ ORACLE\ ORADATA\ NMYW\ REDO01.LOG

Successful open of redo thread 1.

Mon Dec 21 14:43:32 2009

SMON: enabling cache recovery

Mon Dec 21 14:43:32 2009

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_ora_265156.trc:

ORA-00600: internal error code, parameters:

[2662], [2196], [131080003], [2196], [131139845], [8388617], [], []

Mon Dec 21 14:43:32 2009

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_ora_265156.trc:

ORA-00600: internal error code. Parameters: [2662], [2196], [131080003], [2196], [131139845], [], []

Mon Dec 21 14:43:32 2009

Error 600 happened during db open, shutting down database

USER: terminating instance due to error 600

Instance terminated by USER, pid = 265156

ORA-1092 signalled during: alter database open resetlogs...

Mon Dec 21 14:48:33 2009

USER: terminating instance due to error 1092

Instance terminated by USER, pid = 265156

SQL > connect / as sysdba

SQL > startup mount pfile=c:\ oracle\ ora92\ database\ INITyw.ora

SQL > select file#,checkpoint_change# from v$datafile

It is found that the checkpoint_scn of all datafile is surprisingly large:

Using 10015 events for adjust_scn

Level 1 = 1billion (12-bit integer)

SQL > alter session set events' 10015 trace name adjust_scn level 1'

SQL > alter database open

Alter database open

*

ERROR at line 1:

ORA-01092: ORACLE instance terminated. Disconnection forced

SQL > alter database open

View the alert_yw.log file:

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_ora_269012.trc:

ORA-00600: internal error code. Parameters: [2256], [0], [1073741824], [2196], [131100005], []

Mon Dec 21 15:18:11 2009

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_ora_269012.trc:

ORA-00600: internal error code. Parameters: [2256], [0], [1073741824], [2196], [131100005], []

Level = (21968.1) * 416788

SQL > alter session set events' 10015 trace name adjust_scn level 8788'

SQL > alter database open

Error report:

View the alert_yw.log file:

Debugging event used to advance scn to 9436043149312

Undo Segment 1 Onlined

Undo Segment 2 Onlined

Undo Segment 3 Onlined

Undo Segment 4 Onlined

Undo Segment 5 Onlined

Undo Segment 6 Onlined

Undo Segment 7 Onlined

Undo Segment 8 Onlined

Undo Segment 9 Onlined

Undo Segment 10 Onlined

Successfully onlined Undo Tablespace 1.

Dictionary check beginning

Dictionary check complete

Mon Dec 21 15:50:52 2009

SMON: enabling tx recovery

Mon Dec 21 15:50:52 2009

Database Characterset is ZHS16GBK

Mon Dec 21 15:50:54 2009

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_ora_273712.trc:

ORA-00600: internal error code. Parameters: [4193], [38371], [38432], []

Mon Dec 21 15:50:54 2009

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_p000_272924.trc:

ORA-00600: internal error code, arguments: [ktbsdp1], []

Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0

Mem# 0 errs 0: d:\ ORACLE\ ORADATA\ NMYW\ REDO02.LOG

Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0

Mem# 0 errs 0: d:\ ORACLE\ ORADATA\ NMYW\ REDO02.LOG

Mon Dec 21 15:50:56 2009

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_p000_272924.trc:

ORA-00339: archived log does not contain any redo

ORA-00334: archived log:'d:\ ORACLE\ ORADATA\ NMYW\ REDO03.LOG'

ORA-00600: internal error code, arguments: [ktbsdp1], []

Mon Dec 21 15:50:56 2009

Recovery of Online Redo Log: Thread 1 Group 2 Seq 2 Reading mem 0

Mem# 0 errs 0: d:\ ORACLE\ ORADATA\ NMYW\ REDO02.LOG

Mon Dec 21 15:50:56 2009

Errors in file d:\ oracle\ admin\ nmyw\ udump\ nmyw_ora_273712.trc:

ORA-00607: an internal error occurred while changing the block

ORA-00600: internal error code. Parameters: [4193], [38371], [38432], []

An ora-00600 [4193] error is reported, indicating that there is an error in the undo message. Just drop the undo datafile offline:

SQL > alter database datafile'c:\ oracle\ oradata\ yw\ undotbs01.ora' offline drop

SQL > alter database open

Database opened.

Export the data using exp. Re-build the library to import, everything ok.

If an ora-600 [4193] [4194] error occurs in the last step, the solution is as follows:

ORA-600 's 4194 and 4193 errors, according to the error message, appear to be a problem with Oracle during recovery. Query METALINK and find that it is caused by the inconsistency between the rollback record in REDO and the UNDO. Try to open the database with the implicit parameter _ CORRUPTED_ROLLBACK_SEGMENTS. Add the following information to the inittest08.ora initialization file you just created:

Undo_management='MANUAL'

_ corrupted_rollback_segments= (_ SYSSMU1&,_SYSSMU2&,_SYSSMU3&,_SYSSMU4&,_SYSSMU5&,_SYSSMU6&,_SYSSMU7&,_SYSSMU8&,_SYSSMU9&,_SYSSMU10&,_SYSSMU11&,_SYSSMU12&,_SYSSMU13&,_SYSSMU14&,_SYSSMU15&,_SYSSMU16&,_SYSSMU17&,_SYSSMU18&,_SYSSMU19&,_SYSSMU20&,_SYSSMU21&,_SYSSMU22&,_SYSSMU23&,_SYSSMU24&,_SYSSMU25&,_SYSSMU26&,_SYSSMU27&,_SYSSMU28&,_SYSSMU29&,_SYSSMU30&,_SYSSMU31& _ SYSSMU32&,_SYSSMU33&,_SYSSMU34&,_SYSSMU35&,_SYSSMU36&,_SYSSMU37&,_SYSSMU38&,_SYSSMU39&,_SYSSMU40&,_SYSSMU41&)

After reading the above, do you have any further understanding of how to deal with noarchive database current redo log corruption and no backup? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

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.