Ora-00600 Internal Error Code Arguments 2662 4
System table spaces ora 00600 internal error code arguments 2662 1 are deleted, the recovery data files the ora-16433: the database must be opened in read/write mode. way to recover the database to the start state, database no archive mode. Open in alter database open resetlog database ora-600 [2662] error when prompted. The following information: SQL> col member for a80 SQL> select group#,status,member from v$logfile; GROUP# STATUS MEMBER ---------- ------- -------------------------------------------------------------------------------- 3 /u01/app/oracle/ORAC1/onlinelog/o1_mf_3_9r1wx0r7_.log 3 /u01/app/oracle/fast_recovery_area/ORAC1/onlinelog/o1_mf_3_9r1wx0tq_.log 2 /u01/app/oracle/ORAC1/onlinelog/o1_mf_2_9r1wwyrm_.log 2 /u01/app/oracle/fast_recovery_area/ORAC1/onlinelog/o1_mf_2_9r1wwyvm_.log 1 /u01/app/oracle/ORAC1/onlinelog/o1_mf_1_9r1www7g_.log 1 /u01/app/oracle/fast_recovery_area/ORAC1/onlinelog/o1_mf_1_9r1wwwdz_.log 6 rows selected. SQL> recover database until cancel using backup controlfile ; ORA-00279: change 1104149 generated at 06/06/2014 09:50:26 needed for thread 1 ORA-00289: suggestion : /u01/app/oracle/fast_recovery_area/ORAC1/archivelog/2014_06_06/o1_mf_1_23_%u_.arc ORA-00280: change 1104149 for thread 1 is in sequence #23 Specify log: {
Session and ProcessTracing Performance Faster Primary Key creation orenabling MyNotes 2014 Notes Dec-14 Jan-14 Mar-14 Apr-14 May-14 Aug-14 OCT-14 Nov-14 2013 Notes Apr-13 May-13 Jun-13 July-13 Aug-13 Sep-13 Oct-13 Nov-13 Dec-13 2015 Notes Jun-15 Feb-15 Mar-15 Apr-15 May-15 Jul-15 Aug-15 Sep-15 Oct-15 Feedback About Profile Home > Oracle > ORA-00600: internal error code, arguments: [2662], ORA-00600: internal error code, arguments: [2662], July 8, 2010 Ora600Tom Leave a comment Go to comments Wed Jul 7 03:59:44 2010 Errors in file /opt/oracle/admin/xxx/bdump/xxx_smon_7875.trc: ORA-00600: internal error code, arguments: [2662], [1696], [1478225386], [1696], [1956780490], [8388610], [], [] replication_dependency_tracking turned off (no async multimaster replication found) Completed: alter database open Wed Jul 7 03:59:45 2010 Fatal internal http://www.programering.com/a/MDMxYTNwATg.html error happened while SMON was doing active transaction recovery. Wed Jul 7 03:59:45 2010 Errors in file /opt/oracle/admin/xxx/bdump/xxx_smon_7875.trc: ORA-00600: internal error code, arguments: [2662], [1696], [1478225386], [1696], [1956780490], [8388610], [], [] That was an interesting problem. Infact database was UP in READONLY mode, what the DBA did, just brought it down. When he re-started (sql> startup;) the database started throwing ORA-00600 error and instance terminated by https://ora600tom.wordpress.com/2010/07/08/ora-00600-internal-error-code-arguments-2662/ SMON. ORA-00600: internal error code, arguments: [2662], [1696], [1478225386], [1696], [1956780490], [8388610], [], [] That was very interesting why a re-start caused an ORA-00600 and SMON terminated the instance. We search through Metalink for this specific ORa-00600 error and found the first argument [2662] points a SCN mismatch, or block corruption etc. But, since the [b] and [d] are same, shows there is no SCN mismatch. we tried to open the database in READ ONLY mode, and failed with database need recovery. Wed Jul 7 01:21:30 2010 alter database open read only Wed Jul 7 01:21:30 2010 ORA-16005 signalled during: alter database open read only… But intestingly, it was clear from the alert log, the recovery was completed! Beginning crash recovery of 1 threads Wed Jul 7 01:18:08 2010 Started redo scan Wed Jul 7 01:18:08 2010 Completed redo scan 282 redo blocks read, 96 data blocks need recovery Wed Jul 7 01:18:08 2010 Started recovery at Thread 1: logseq 1, block 3871, scn 0.0 Recovery of Online Redo Log: Thread 1 Group 5 Seq 1 Reading mem 0 Mem# 0 errs 0: /oradata1/xxx/redo5.log Wed Jul 7 01:18:08 2010 Completed redo application Wed Jul
failure of startup due needs recovery; this applies to the EBS 11.5.9 instance on database version: 9.2.0.5. the database results in down state and needs to be up http://testyazans.blogspot.com/2012/06/recovering-corrupted-database-with.html with missing archive. Symptoms When starting up an instance, it fails at mount state and shows the following error ORA-01194 File 1 needs more recovery to be consistent Which means it needs recovery, issuing "RECOVER DATABASE" for recovering instance, it reports the need for a missing archive number 483. The current archives sequence just hit 5013 and the archive log in question internal error is missing. ORA-00308: cannot open archived log '/u01/pcb/db/pcbdb/9.2.0/dbs/arch1_483.dbf' Case #1: 1. Recreating the control file from SQL "ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS ..."2. Issuing recovery command "RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL"3. Open database using "ALTER DATABASE OPEN RESETLOGS"4. Result is the same; ORA-01194 is still showing, needs archive 483. Case #2: 1. Adding a hidden parameters_allow_resetlogs_corruption= TRUE _allow_read_only_corruption= TRUE internal error code 2. Open database using "ALTER DATABASE OPEN RESETLOGS"3. Result is : ORA-01092: ORACLE instance terminated Disconnection forced4. Alert log shows ORA 600ORA-00600: internal error code, arguments: [2662], [1389], [17722400], [1389], [17810351], [1589641225], [], []5. Oracle Support shows that ORA-600 [2662] "Block SCN is ahead of Current SCN" which is the case. Data files are inconsistent which SCN is different and some are larger than current. Solution To solve this issue, database should be opened at least for exporting as much data as we can by using Data Pump of Export tool. In order to do this we have to bump up all SCN on all data file to a value that is higher than any block SCN or current SCN. This is done by determining how much SCN range should be bumped up. The ORA 600 shows after [2662] bracket 2 values for SCN, current and block. Current = 17722400 < block = 17810351 as per metalink note on ORA-600 tool: ERROR: ORA-600 [2662] [a] [b] [c] [d] [e] VERSIONS: versions 6.0 to 10.1 DESCRIPTION: A data block SCN is ahead of the current SCN. The ORA-