Internal Error Code Arguments 2662
Contents |
System table spaces are deleted, the recovery data files the way to recover the database ora 00600 internal error code arguments 2662 1 to the start state, database no archive mode. Open
Ora-16433: The Database Must Be Opened In Read/write Mode.
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: {
resetlogs * ERROR at line 1: ORA-00603: ORACLE server session terminated by fatal error ORA-00600: internal error code, arguments: [2662], [0], [25501152], [0], [25521272], [12583040], [], [], [], [], [], [] ORA-00600: internal error code, arguments: [2662], [0], [25501151], [0], [25521272], [12583040], [], [], [], [], [], [] ORA-01092: ORACLE instance terminated. Disconnection forced ORA-00600: internal error code, arguments: [2662], [0], [25501149], [0], [25521272], [12583040], [], [], http://www.programering.com/a/MDMxYTNwATg.html [], [], [], [] Process ID: 10846 Session ID: 1 Serial number: 5 _allow_resetlogs_corruption=true ------------OR 1. shutdown immediate; 2. backup all 3. startup mount; 4. alter session set events '10015 trace name adjust_scn level 1'; 5. alter database open; ------------OR alter session set events '10015 trace name adjust_scn level 1'; Subject: How http://myoracledbablogon.blogspot.com/2010/09/all-that-ive-found-to-recover-database.html to Force the Database Open Creation Date: 12-OCT-1999 There are times when it may become necessary to force a database open. This document identifies one way to attempt to get the database open. You may need to use this procedure because something happened to the database that required you to perform recovery. The recovery completed, but you receive the following error message: ORA-01194 - file 1 needs more media recovery to be consistent You have determined that there is nothing else that can be done to get the database to a consistent state. You tried opening the database using RESETLOGS, but that also failed. Procedure: ========== To ATTEMPT to force the database open, perform the following steps: 1. Add the parameter _ALLOW_RESETLOGS_CORRUPTION = TRUE to the init.ora file 2. STARTUP MOUNT the database 3. Issue the appropriate RECOVER DATABASE command: a) RECOVER DATABASE UNTIL CANCEL or b) RECOVER DATABASE USING BACKUP CONTRO
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 https://ora600tom.wordpress.com/2010/07/08/ora-00600-internal-error-code-arguments-2662/ 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 http://www.progtown.com/topic567752-ora00600-internal-error-code-arguments-2662.html 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], internal error [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 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], [], internal error code [] 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 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 th
internal error code, arguments: [2662] Pages 1 You must login or register to post a reply Topic RSS feed Posts [ 5 ] 1 Topic by The administrator so cal 2012-05-06 08:22:32 The administrator so cal New member Offline Registered: 2012-05-06 Posts: 3 Topic: ORA-00600: internal error code, arguments: [2662] We have the fallen basis (at a startup the administrator cut down a server from the socket), , certainly, no.Error in alert.log:ORA-00600: internal error code, arguments: [2662], [0], [217443653], [0], [217503738], [4194306], [], []Metalink concerning this error speaks here that: wrote: Subject: ORA-600 [2662] "Block SCN is ahead of Current SCN" (Note:28929.1)DESCRIPTION:A data block SCN is ahead of the current SCN. The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN stored in an UGA variable. If the SCN is less than the dependent SCN then we signal the ORA-600 [2662] internal error..... If the SCNs in the error are very close, then try to shutdown and startup the instance several times.In some situations, the SCN increment during startup may permit the database to open. Keep track of the number of times you attempted a startup. It would be desirable to achieve the last. Tried to launch basis some times: conn / as sysdba startup mount recover database using backup controlfile until cancel; cancel alter database open resetlogs; Thus, predictably, Current SCN WRAP increases on 2. But to the necessary value 60 000, i.e. 30 000 starts are necessary.Questions at me such:1. Whether it is possible to cause a command recover database using backup controlfile until cancel; with instructions that instead of a broad gull name there will be a command cancel. How it to make? It is necessary to write shell-script which 30 000 times will launch a DB.2. Whether it is possible using WinHex to correct value Current SCN WRAP? In what file (ah)? I looked search in system01.dbf, but did not find a