Refresh the database recovery history to Oracle7.3.2 again-redo exception recovery

Some netizens asked me about Oracle7.3's database on QQ, and asked me if I could restore the database to get the following information: SVRMGRselect * fromv $ version; BANNER has Oracle7WorkgroupServerRelease7.3.2.2.1

Some netizens asked me about Oracle 7.3 databases on QQ, and asked me if I could restore the database to obtain the following information: SVRMGR select * from v $ version due to redo exceptions; BANNER ---------------------------------------------------------------- Oracle7 Workgroup Server Release 7.3.2.2.1-P

Some netizens asked me on QQ about Oracle 7.3's database and asked me if I could restore it due to redo exceptions.

Check the database to obtain the following information:

SVRMGR> select * from v $ version; BANNER implements Oracle7 Workgroup Server Release 7.3.2.2.1-Production ReleasePL/SQL Release 2.3.2.2.0-ProductionCORE Version 3.5.2.0.0-ProductionTNS for 32-bit Windows: version 2.3.2.1.0-ProductionNLSRTL Version 3.2.2.0.0-Production 5 rows selected

Data File Information

Redo Information

Skip redo for restoration. During the resetlogs process, the rbs tablespace Bad blocks are reported. Then, the dul tool is used to obtain the rollback segment name, and hidden parameters are used to block the segment.

License high water mark = 2Starting up ORACLE RDBMS Version: 7.3.2.2.1.System parameters with non-default values:  processes                = 800  shared_pool_size         = 540000000  control_files            = D:\ORANT\DATABASE\ctl1orcl.ora, D:\ORANT\DATABASE\ctl2orcl.ora  compatible               = 7.3.0.0.0  log_buffer               = 327680  log_checkpoint_interval  = 1000000  db_files                 = 40  db_file_simultaneous_writes= 1280  max_rollback_segments    = 12800  _offline_rollback_segments= RB13, RB14, RB15, RB16, RB20  _corrupted_rollback_segments= RB13, RB14, RB15, RB16, RB20  sequence_cache_entries   = 100  sequence_cache_hash_buckets= 100  remote_login_passwordfile= SHARED  mts_servers              = 0  mts_max_servers          = 0  mts_max_dispatchers      = 0  audit_trail              = NONE  sort_area_retained_size  = 65536  sort_direct_writes       = AUTO  db_name                  = oracle  open_cursors             = 800  text_enable              = TRUE  snapshot_refresh_processes= 1  background_dump_dest     = %RDBMS73%\trace  user_dump_dest           = %RDBMS73%\traceMon Jun 16 16:46:57 2014PMON startedMon Jun 16 16:46:57 2014DBWR startedMon Jun 16 16:46:57 2014LGWR startedMon Jun 16 16:46:57 2014RECO startedMon Jun 16 16:46:57 2014SNP0 startedMon Jun 16 16:46:57 2014alter database  mount exclusiveMon Jun 16 16:46:58 2014Successful mount of redo thread 1.Mon Jun 16 16:46:58 2014Completed: alter database  mount exclusiveMon Jun 16 16:48:15 2014alter database openMon Jun 16 16:48:16 2014Beginning crash recovery of 1 threadsCrash recovery completed successfullyMon Jun 16 16:48:17 2014Thread 1 advanced to log sequence 9  Current log# 1 seq# 9 mem# 0: D:\ORANT\DATABASE\LOG2ORCL.ORAThread 1 opened at log sequence 9  Current log# 1 seq# 9 mem# 0: D:\ORANT\DATABASE\LOG2ORCL.ORASuccessful open of redo thread 1.Mon Jun 16 16:48:18 2014SMON: enabling cache recoveryMon Jun 16 16:48:19 2014Completed: alter database openMon Jun 16 16:48:20 2014SMON: enabling tx recoverySMON: about to recover undo segment 14SMON: mark undo segment 14 as needs recoverySMON: about to recover undo segment 15SMON: mark undo segment 15 as needs recoverySMON: about to recover undo segment 16SMON: mark undo segment 16 as needs recoverySMON: about to recover undo segment 17SMON: mark undo segment 17 as needs recoverySMON: about to recover undo segment 18SMON: mark undo segment 18 as needs recoveryMon Jun 16 16:48:20 2014Errors in file D:\ORANT\RDBMS73\trace\orclSMON.TRC:ORA-00600: internal error code, arguments: [4306], [21], [2], [], [], [], [], []

A ORA-00600 [4306] occurs during database startup, causing smon exceptions. This error occurs because smon clears the temporary segment during the database open process. By setting the event to skip, the database is opened as a whole.

Mon Jun 16 17:53:10 2014 Errors in file D: \ ORANT \ RDBMS73 \ trace \ orclDBWR. TRC: ORA-00600: internal error code, arguments: [3600], [3], [14], [], [], [], [], [], [] Mon Jun 16 18:05:12 2014 Errors in file D: \ ORANT \ RDBMS73 \ trace \ ORA06880.TRC: ORA-01578: ORACLE Data Block Error (file 12, block 46644) ORA-01110: file '12' no online ORA-00600: Internal error code, variable: [4194], [18], [5], [], [], [], [] ORA-00600: Internal error code, variable: [2, 4194], [18], [5], [], [], []

ORA-00600 [3600] is caused by a problem with the tablespace lock in the offline rollback segment
ORA-00600 [4194] is caused by bad blocks in the tablespace data file where the rollback segment is located

• Undo Exception Handling Procedure (9i)
• ORA-00600 [kcrf_resilver_log_1] exception recovery
• ORACLE 8.1.7 database ORA-600 4194 fault recovery
• A group's ebs database redo undo loss causes tragedy
• In-depth analysis of a ORA-00314 Error
• Record A ORA-600 3004 recovery process and handling ideas
• Oracle Security Warning redo exception caused by bare device Error
• ORA-00600 [kcratr1_lostwrt]/ORA-00600 [3020] error recovery

Original article address: refresh the database recovery history to Oracle 7.3.2-redo exception recovery. Thanks to the original author for sharing.