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

This article mainly introduces "how to solve the ORA-01194 and ORA-01110 problems of Oracle error reporting". In daily operation, I believe many people have doubts about how to solve the problem of Oracle error reporting ORA-01194 and ORA-01110. The editor consulted all kinds of materials and sorted out simple and easy-to-use operation methods. I hope it will be helpful for you to answer the doubts of "how to solve the ORA-01194 and ORA-01110 problem of Oracle error reporting"! Next, please follow the editor to study!

Use _ allow_resetlogs_corruption to open the rman backup library without archive logs. The operation and maintenance DBA indicates that after the server is down, the database error ORA-01194 ORA-01110 is turned on. The reason is that the database cannot be started due to inconsistent Oracle SCN. Use _ allow_resetlogs_corruption to open the database.

1.rman restore restore operation-restore database RMAN > restore database;-- restore database RMAN > recover database Starting recover at 2012-03-08 21:20:45using target database control file instead of recovery catalogallocated channel: ORA_DISK_1channel ORA_DISK_1: SID=65 device type=DISKstarting media recoveryRMAN-00571: = = RMAN-00569: = ERROR MESSAGE STACK FOLLOWS = RMAN-00571: = RMAN-03002: failure of recover command at 03 21:20:47RMAN-06053: unable to perform media recovery because of missing logRMAN-06025: no backup of archived log for thread 1 with sequence 2936 and starting SCN of 25991695 found to restoreRMAN-06025: no backup of archived log for thread 1 with Sequence 2935 and starting SCN of 25991652 found to restoreRMAN-06025: no backup of archived log for thread 1 with sequence 2934 and starting SCN of 25991649 found to restore … RMAN-06025: no backup of archived log for thread 1 with sequence 2902 and starting SCN of 25991156 found to restore the missing log is reported here. In fact, after the backup of the database file, the archive log is not backed up and all the archive log is lost.

Perform an incomplete recovery

SQL > recover database until cancel; ORA-00279: change 25991194 generated at 03ax 08 Specify log: 20:33:58 needed for thread 1 ORA-00289: suggestion: / opt/oracle/oradata/archivelog/chf/1_2902_752334071.dbf ORA-00280: change 25991194 for thread 1 is in sequence # 2902 Specify log: {

= suggested | filename | AUTO | CANCEL} cancel ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1:'/ opt/oracle/oradata/chf/system01.dbf' ORA-01112: media recovery not started SQL > alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1:'/ opt/oracle/oradata/chf/system01.dbf'

two。 Check the related SCNSQL > select file#,to_char (checkpoint_change#,'999999999999') from v$datafile FILE# TO_CHAR (CHECK--1 25992214 2 25992214 3 25992214 4 25992214 5 25992214 6 25992214 7 25992214 8 25992214 9 25992214 10 25992214 11 25992214 FILE# TO_CHAR (CHECK--13 25992214 14 2599221413 rows selected.SQL > select file# Online_status,to_char (change#,'999999999999') from v$recover_file FILE# ONLINE_ TO_CHAR (CHANG- 1 ONLINE 25991194 2 ONLINE 25991194 3 ONLINE 25991194 4 ONLINE 25991194 5 ONLINE 25991194 6 ONLINE 25991194 7 ONLINE 25991194 8 ONLINE 25991194 9 ONLINE 25991194 10 ONLINE 25991194 11 ONLINE 25991194 FILE# ONLINE_ TO_CHAR (CHANG- 13 ONLINE 25991194 14 ONLINE 2599119413 rows selected.SQL > select file# To_char (checkpoint_change#,'999999999999') from v$datafile_header FILE# TO_CHAR (CHECK--1 25991194 2 25991194 3 25991194 4 25991194 5 25991194 6 25991194 7 25991194 8 25991194 9 25991194 10 25991194 11 25991194 FILE# TO_CHAR (CHECK--13 25991194 14 2599119413 rows selected.-- found that the data file scn is inconsistent with the control file Rebuild the control file, and then query the related scnSQL > select file#,to_char (checkpoint_change#,'999999999999') from v$datafile FILE# TO_CHAR (CHECK--1 25991194 2 25991194 3 25991194 4 25991194 5 25991194 6 25991194 7 25991194 8 25991194 9 25991194 10 25991194 11 25991194 FILE# TO_CHAR (CHECK--13 25991194 14 2599119413 rows selected.SQL > select file# Online_status,to_char (change#,'999999999999') from v$recover_file FILE# ONLINE_ TO_CHAR (CHANG- 1 ONLINE 25991194 2 ONLINE 25991194 3 ONLINE 25991194 4 ONLINE 25991194 5 ONLINE 25991194 6 ONLINE 25991194 7 ONLINE 25991194 8 ONLINE 25991194 9 ONLINE 25991194 10 ONLINE 25991194 11 ONLINE 25991194 FILE# ONLINE_ TO_CHAR (CHANG- 13 ONLINE 25991194 14 ONLINE 2599119413 rows selected.SQL > select file# To_char (checkpoint_change#,'999999999999') from v$datafile_header FILE# TO_CHAR (CHECK--1 25991194 2 25991194 3 25991194 4 25991194 5 25991194 6 25991194 7 25991194 8 25991194 9 25991194 10 25991194 11 25991194 FILE# TO_CHAR (CHECK--13 25991194 14 2599119413 rows selected.--) all scn are consistent at this time 3. Try to open the database

SQL > alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1:'/ opt/oracle/oradata/chf/system01.dbf' SQL > recover database using backup controlfile until cancel; ORA-00279: change 25991194 generated at 03 Unip 08 needed for thread 1 ORA-00289: suggestion: / opt/oracle/oradata/archivelog/chf/1_2902_752334071.dbf ORA-00280: change 25991194 for thread 1 is in sequence # 2902 Specify log: {

= suggested | filename | AUTO | CANCEL} cancel ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1:'/ opt/oracle/oradata/chf/system01.dbf' ORA-01112: media recovery not started SQL > alter database open resetlogs; alter database open resetlogs * ERROR at line 1: ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1:'/ opt/oracle/oradata/chf/system01.dbf'

5. Open the database SQL > create pfile='/tmp/pfile' from spfile with implicit parameters Add-_ allow_resetlogs_corruption= TRUE--SQL > startup mount pfile='/tmp/pfile' forceORACLE instance started.Total System Global Area 622149632 bytesFixed Size 2230912 bytesVariable Size 419431808 bytesDatabase Buffers 192937984 bytesRedo Buffers 7548928 bytesDatabase mounted.SQL > alter database open resetlogs to File created.-/tmp/pfile Database altered.SQL > select open_mode from vested database security open model read WRITE so far, the study on "how to solve the ORA-01194 and ORA-01110 problem of Oracle error reporting" is over. I hope to be able to solve everyone's doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

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.