Methods for Oracle database recovery caused by Operation errors

Source: Internet
Author: User

The following content mainly introduces the syntax for solving the Oracle database large recovery caused by an incorrect operation, that is, before recreating the control file and the control file, back up controlfile and online redolog.

Reference

 
 
  1. Create controlfile reuse set database "LDBRA"  
  2. MAXINSTANCES 8  
  3. MAXLOGHISTORY 1  
  4. MAXLOGFILES 16  
  5. MAXLOGMEMBERS 3  
  6. MAXDATAFILES 100  
  7. Datafile  
  8. '/ora10g/app/oradata/ldbra/system01.dbf',  
  9. '/ora10g/app/oradata/ldbra/undotbs01.dbf',  
  10. '/ora10g/app/oradata/ldbra/sysaux01.dbf',  
  11. '/ora10g/app/oradata/ldbra/users01.dbf',  
  12. '/ora10g/app/oradata/ldbra/example01.dbf',  
  13. '/ora10g/app/product/10.2.0/db_1/dbs/ company.dbf',  
  14. '/ora10g/app/product/10.2.0/db_1/dbs/streams.dbf'  
  15. LOGFILE GROUP 1 ('/ora10g/app/oradata/ldbra/redo01.log')
     SIZE 51200K,  
  16. GROUP 2 ('/ora10g/app/oradata/ldbra/redo02.log')
     SIZE 51200K,  
  17. GROUP 3 ('/ora10g/app/oradata/ldbra/redo03.log') 
    SIZE 51200K RESETLOGS;  

Using the above statements to solve the Oracle database large recovery operation caused by an incorrect operation seems to have been successfully rebuilt! However, an error was reported during recover!

Reference

 
 
  1. SQL> RECOVER DATABASE USING BACKUP CONTROLFILE;  
  2. ORA-00283: recovery session canceled due to errors  
  3. ORA-00600: internal error code, arguments: [kcvhvdf_1], 
    [], [], [], [], [], [],  
  4. []   

We can see that the control file is reset by dbid during reconstruction.

Reference

 
 
  1. SQL> select dbid from v$database;  
  2. DBID  
  3. 1498845164  

The problem seems to have lost a clue here. Haha, copy back the backup control file to replace the just-created control file. Because I use the resetlog option to create a control file, in theory, it should reset redolog, that is, re-create redolog. However, using this option currently does result in a ORA-01227 error. Incredible! Later, it may be related to the dbid in the data file being 0. So we use the ultimate repair method, bbed! First, reset the dbid of all data files to 1488207495 using the bbed tool, and then mark the fuzzy mark as 0x2000 because the database is terminated abnormally by the ckpt process, mark it as 0x2000, indicating that the database is shut down immediate). After using the above method, the control file is successfully created!

Reference

 
 
  1. SQL> STARTUP NOMOUNT  
  2. CREATE CONTROLFILE REUSE DATABASE "LDBRA" RESETLOGS 
    ARCHIVELOG  
  3. MAXLOGFILES 16  
  4. MAXLOGMEMBERS 3  
  5. MAXDATAFILES 100  
  6. MAXINSTANCES 8  
  7. MAXLOGHISTORY 292  
  8. LOGFILE  
  9. ORACLE instance started.  
  10. Total System Global Area 1073741824 bytes  
  11. Fixed Size 1271616 bytes  
  12. Variable Size 461375680 bytes  
  13. Database Buffers 608174080 bytes  
  14. Redo Buffers 2920448 bytes  
  15. GROUP 1 '/ora10g/app/oradata/ldbra/redo01.log' SIZE 50M,  
  16. GROUP 2 '/ora10g/app/oradata/ldbra/redo02.log' SIZE 50M,  
  17. GROUP 3 '/ora10g/app/oradata/ldbra/redo03.log' SIZE 50M  
  18. -- STANDBY LOGFILE  
  19. DATAFILE  
  20. '/ora10g/app/oradata/ldbra/system01.dbf',  
  21. '/ora10g/app/oradata/ldbra/undotbs01.dbf',  
  22. '/ora10g/app/oradata/ldbra/sysaux01.dbf',  
  23. '/ora10g/app/oradata/ldbra/users01.dbf',  
  24. '/ora10g/app/oradata/ldbra/example01.dbf',  
  25. '/ora10g/app/product/10.2.0/db_1/dbs/company.dbf',  
  26. '/ora10g/app/product/10.2.0/db_1/dbs/streams.dbf'  
  27. CHARACTER SET ZHS16GBK  
  28. 21 ;  
  29. Control file created.  

Try to open a database in Oracle

 
 
  1. SQL> alter database open RESETLOGS; 

When the database is suspended, the alert Log in the background displays a [2662] error!

Reference

 
 
  1. SMON: enabling cache recovery  
  2. Tue Mar 9 03:11:38 2010  
  3. Errors in file /ora10g/app/admin/ldbra/udump/
    ldbra_ora_13676.trc:  
  4. ORA-00600: internal error code, arguments: 
    [2662], [2268], [3799096903], [2268], [3799098345], 
    [8388617], [], []  
  5. Tue Mar 9 03:11:40 2010  
  6. Errors in file /ora10g/app/admin/ldbra/udump/
    ldbra_ora_13676.trc:  
  7. ORA-00600: internal error code, arguments: [2662],
     [2268], [3799096903], [2268], [3799098345], [8388617],
     [], []  
  8. Tue Mar 9 03:11:40 2010  

The above content is an introduction to the actual operations on the syntax reconstruction control file for Oracle Database large recovery caused by an incorrect operation.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.