Database recovery History in Oracle refreshed again to Oracle 7.3.2 version-redo exception recovery

There are netizens on QQ to find me, said Oracle 7.3 database, because redo abnormal consultation I can restore

Check the database for the following information

The code is as follows	Copy Code
Svrmgr> select * from V$version; BANNER ---------------------------------------------------------------- Oracle7 Workgroup Server Release 7.3.2.2.1-production release Pl/sql Release 2.3.2.2.0-production CORE Version 3.5.2.0.0-production TNS for 32-bit windows:version 2.3.2.1.0-production Nlsrtl Version 3.2.2.0.0-production

5 Rows selected
Data file information

Redo Information

Skip redo for recovery, report a bad chunk of the RBS table space during the resetlogs process, and then get the rollback segment name through the Dul tool, and then use the suppressed parameters to mask off

The code is as follows

Copy Code

License High Water mark = 2 Starting 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%/trace Mon June 16 16:46:57 2014 Pmon started Mon June 16 16:46:57 2014 DBWR started Mon June 16 16:46:57 2014 LGWR started Mon June 16 16:46:57 2014 Reco started Mon June 16 16:46:57 2014 SNP0 started Mon June 16 16:46:57 2014 ALTER DATABASE Mount EXCLUSIVE Mon June 16 16:46:58 2014 Successful mount of Redo thread 1. Mon June 16 16:46:58 2014 Completed:alter Database Mount Exclusive Mon June 16 16:48:15 2014 ALTER DATABASE Open Mon June 16 16:48:16 2014 Beginning crash recovery of 1 threads Crash Recovery completed successfully Mon June 16 16:48:17 2014 Thread 1 advanced to log sequence 9 Current log# 1 seq# 9 mem# 0:D:/ORANT/DATABASE/LOG2ORCL. ORA Thread 1 opened at log sequence 9 Current log# 1 seq# 9 mem# 0:D:/ORANT/DATABASE/LOG2ORCL. ORA Successful open of Redo thread 1. Mon June 16 16:48:18 2014 Smon:enabling Cache Recovery Mon June 16 16:48:19 2014 Completed:alter Database Open Mon June 16 16:48:20 2014 smon:enabling TX Recovery Smon:about to recover undo segment 14 Smon:mark Undo Segment Needs Recovery Smon:about to recover undo segment 15 Smon:mark Undo segment as needs recovery Smon:about to recover undo segment 16 Smon:mark Undo segment as needs recovery Smon:about to recover undo segment 17 Smon:mark Undo segment as needs recovery Smon:about to recover undo segment 18 Smon:mark Undo segment as needs recovery Mon June 16 16:48:20 2014 Errors in file d:/orant/rdbms73/trace/orclsmon.trc: Ora-00600:internal error code, arguments: [4306], [21], [2], [], [], [], [], []

The database appears ora-00600[4306 during startup], causing a Smon exception. This error occurs because the Smon clears the temporary segment during the database open, and the database is turned on by setting event skipping, but during the recovery process, you encounter a

The code is as follows	Copy Code
Mon June 16 17:53:10 2014 Errors in file d:/orant/rdbms73/trace/orcldbwr.trc: Ora-00600:internal error code, arguments: [3600], [3], [14], [], [], [], [], [] Mon June 16 18:05:12 2014 Errors in file d:/orant/rdbms73/trace/ora06880. TRC:

Ora-01578:oracle Data block Error (file number 12, block number 46644)
ORA-01110: File ' 12 ' is not online
ORA-00600: Internal error code, variable: [4194], [18], [5], [], [], []
ORA-00600: Internal error code, variable: [4194], [18], [5], [], [], []
ORA-00600[3600] is due to problems with the table space lock in the offline rollback segment
ORA-00600[4194] is caused by a bad block in the table space data file where the rollback segment occurs

Contact: Mobile Phone (13429648788) QQ (107644445)

Link: http://www.xifenfei.com/5378.html

Title: Database recovery History refreshed again to Oracle 7.3.2 version-redo exception recovery