Re: Unable to open database after instance failure with ORA-00600 internal error and management operations on LMT before the failure

"Sergey Adamenko" <asv_no__s_p_a_m_at_i.com.ua> wrote in message news:bo412d$1h4v$2_at_news.dg.net.ua...
> Hello, ALL.
>
> Recently I had instance failure and since then I'm unable to open the
> database. I tried some actions to bring database online but nothing
> helped. I'm not worried about loss of data. I have only several
> questions related to the accident:
> 1. Can anything else be done to recover the database?
> 2. Had anyone unexpected errors then altering locally managed
> tablespaces (LMT) offline or execution ALTER TABLE MOVE
> from/to LMT<->DMT?
> 3. Does anyone recommend NOT using LMT in 8.1.7.4?
>
>
> Configuration of server is as follows:
> | DB Version: Oracle EE 8.1.7.4.1
> | OS: Windows 2000 AS SP4
> | Database purpose: Developer DB
> | Database mode: NOARCHIVELOG
>
> Instance of the server unexpectedly terminated with
> ORA-00600: internal error.
> Opening of database ends up with the same error. See ACTION1 log at
> the end of this post. Generated orakmuSMON.TRC file contains
> information I'm unable to interpret.
>
> Two things I want to notice about usage of DB.
> First, there where rare ORA-00600 errors then I used to alter an LMT
> offline to create export dump excluding data of specified tablespace.
> These were memory leak errors. I'm using this trick with offlining a
> tablespace before running EXP as a solution to produce export with only
> system and dictionary data, excluding data of tables with on-line data
> and audit data of our applied system. Running ahead, I want to say,
> these errors didn't disappeared on new database, I created on a reserved
> host. This time all tablespaces except SYSTEM and RBS are LMT.
>
> Second, in the day of failure I was moving some tables from DMT
> (USERS) to LMT (named WORKTBS) via ALTER TABLE MOVE å
> ALTER INDEX REBUIDå During of execution of script there was an
> ORA-00600: internal error (memory leak). But re-execution of the
> statement succeeded.
>
> Now abount what I did to recover the DB.
> After failure I copied all db files to a host with the same configuration,
> so I have unchanged files to do further experiments.
> At this separated host tried:
> 1. Opening the DB.
> Result: ORA-00600: internal error code,
> arguments: [5120], [0], [16], [369], [2], [], [], [].
> See ACTION1 log.
> 2. Opening with RESETLOGS + offline drop of all datafiles
> except belonging to SYSTEM, RBS, and USERS01 (DMT)
> Result: ORA-00600 in SMON, DBW0. See ACTION2 log.
> 3. Opening with RESETLOGS + offline drop of all datafiles.
> Only SYSTEM datafile is preserved. The following underscore
> parameters added to initSID.ora file:
> _allow_resetlogs_corruption= TRUE
> _offline_rollback_segments= rbs
> _corrupted_rollback_segments= rbs
> Result: ORA-00600. See ACTION3 log.
>
>
> Thank you in advance!
>
> Best regards,
> Sergey Adamenko.
>
>
> +=========================================
> | Log ACTION1
> | Descipton: Opening of DB
> +----------------------------------------------------------------------
> | ALTER DATABASE OPEN
> | Beginning crash recovery of 1 threads
> | Sun Nov 02 13:34:11 2003
> | Thread recovery: start rolling forward thread 1
> | Recovery of Online Redo Log: Thread 1 Group 3 Seq 1344 Reading
> | mem 0
> | Mem# 0 errs 0: D:\ORADATA\REDO01A.LOG
> | Sun Nov 02 13:34:12 2003
> | Thread recovery: finish rolling forward thread 1
> | Thread recovery: 4 data blocks read, 4 data blocks written, 56 redo
> | blocks read
> | Crash recovery completed successfully
> | Sun Nov 02 13:34:12 2003
> | Thread 1 advanced to log sequence 1345
> | Thread 1 opened at log sequence 1345
> | Current log# 1 seq# 1345 mem# 0: D:\ORADATA\REDO03A.LOG
> | Successful open of redo thread 1.
> | Sun Nov 02 13:34:12 2003
> | SMON: enabling cache recovery
> | SMON: enabling tx recovery
> | Sun Nov 02 13:34:14 2003
> | Errors in file C:\oracle\admin\orakmu\bdump\orakmuSMON.TRC:
> | ORA-00600: internal error code, arguments: [5120], [0], [16], [369],
> | [2], [], [], []
> |
> | Sun Nov 02 13:34:15 2003
> | Completed: ALTER DATABASE OPEN
> | Sun Nov 02 13:34:16 2003
> | Errors in file C:\oracle\admin\orakmu\bdump\orakmuSMON.TRC:
> | ORA-00600: internal error code, arguments: [5120], [0], [16], [369],
> | [2], [], [], []
>
> | Sun Nov 02 13:34:16 2003
> | SMON: terminating instance due to error 600
> | Instance terminated by SMON, pid = 728
>
>
> +=========================================
> | Log ACTION2
> | Descipton: Opening of DB with RESETLOGS
> +----------------------------------------------------------------------
> |Sun Nov 02 13:45:35 2003
> |CREATE CONTROLFILE REUSE DATABASE ORAKMU
> | RESETLOGS NOARCHIVELOG
> | MAXLOGFILES 8
> | MAXLOGMEMBERS 2
> | MAXDATAFILES 32
> | MAXINSTANCES 1
> | MAXLOGHISTORY 453
> |LOGFILE
> | GROUP 1 'D:\ORADATA\REDO03A.LOG' SIZE 24M,
> | GROUP 2 'D:\ORADATA\REDO02A.LOG' SIZE 24M,
> | GROUP 3 'D:\ORADATA\REDO01A.LOG' SIZE 24M
> |DATAFILE
> | 'D:\ORADATA\SYSTEM01.DBF',
> | 'D:\ORADATA\RBS01.DBF',
> | 'C:\ORACLE\ORADATA\ORAKMU\USERS01.DBF',
> | 'D:\ORADATA\STARTEAM.DBF',
> | 'D:\ORADATA\TOOLS01.DBF',
> | 'D:\ORADATA\INDX01.DBF',
> | 'D:\ORADATA\REQPRO_DATA.DBF',
> | 'D:\ORADATA\LOGDATA.DBF',
> | 'D:\ORADATA\WORKTBS.DBF'
> |CHARACTER SET CL8MSWIN1251
> |
> |ORA-1503 signalled during: CREATE CONTROLFILE REUSE
> | DATABASE ORAKMU RESETLOGS...
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE DATAFILE 'D:\ORADATA\TOOLS01.DBF'
> | OFFLINE DROP
> |
> |Completed: ALTER DATABASE DATAFILE
> 'D:\ORADATA\TOOLS01.DBF' O
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE DATAFILE 'D:\ORADATA\INDX01.DBF'
> | OFFLINE DROP
> |
> |Completed: ALTER DATABASE DATAFILE
> | 'D:\ORADATA\INDX01.DBF' OF
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE DATAFILE
> | 'D:\ORADATA\REQPRO_DATA.DBF' OFFLINE DROP
> |
> |Completed: ALTER DATABASE DATAFILE
> |'D:\ORADATA\REQPRO_DATA.DB
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE DATAFILE 'D:\ORADATA\LOGDATA.DBF'
> | OFFLINE DROP
> |
> |Completed: ALTER DATABASE DATAFILE
> |'D:\ORADATA\LOGDATA.DBF' O
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE DATAFILE 'D:\ORADATA\WORKTBS.DBF'
> |OFFLINE DROP
> |
> |Completed: ALTER DATABASE DATAFILE
> | 'D:\ORADATA\WORKTBS.DBF' O
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE RECOVER DATABASE until cancel
> |Media Recovery Start
> |Media Recovery Log
> |ORA-279 signalled during: ALTER DATABASE RECOVER
> | DATABASE until cancel ...
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE RECOVER CONTINUE DEFAULT
> |Media Recovery Log C:\ORACLE\ORA81\RDBMS\ARC01345.001
> |ORA-308 signalled during: ALTER DATABASE RECOVER
> |CONTINUE DEFAULT ...
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE RECOVER CANCEL
> |ORA-1547 signalled during: ALTER DATABASE RECOVER
> | CANCEL ...
> |Sun Nov 02 13:45:35 2003
> |ALTER DATABASE OPEN RESETLOGS
> |
> |RESETLOGS is being done without consistency checks. This may
> |result
> |in a corrupted database. The database should be recreated.
> |RESETLOGS after incomplete recovery UNTIL CHANGE 29797265
> |Sun Nov 02 13:45:38 2003
> |Thread 1 opened at log sequence 1
> | Current log# 1 seq# 1 mem# 0: D:\ORADATA\REDO03A.LOG
> |Successful open of redo thread 1.
> |Sun Nov 02 13:45:38 2003
> |SMON: enabling cache recovery
> |Sun Nov 02 13:45:38 2003
> |Dictionary check beginning
> |File #5 is offline, but is part of an online tablespace.
> |data file 5: 'D:\ORADATA\TOOLS01.DBF'
> |File #6 is offline, but is part of an online tablespace.
> |data file 6: 'D:\ORADATA\INDX01.DBF'
> |File #7 is offline, but is part of an online tablespace.
> |data file 7: 'D:\ORADATA\REQPRO_DATA.DBF'
> |File #8 is offline, but is part of an online tablespace.
> |data file 8: 'D:\ORADATA\LOGDATA.DBF'
> |File #9 is offline, but is part of an online tablespace.
> |data file 9: 'D:\ORADATA\WORKTBS.DBF'
> |Dictionary check complete
> |Sun Nov 02 13:45:38 2003
> |SMON: enabling tx recovery
> |Sun Nov 02 13:45:39 2003
> |Errors in file C:\oracle\admin\orakmu\bdump\orakmuSMON.TRC:
> |ORA-00600: internal error code, arguments: [5120], [0], [16], [369],
> |[2], [], [], []
> |
> |Sun Nov 02 13:45:41 2003
> |Completed: ALTER DATABASE OPEN RESETLOGS
> |Sun Nov 02 13:45:42 2003
> |Errors in file C:\oracle\admin\orakmu\bdump\orakmuSMON.TRC:
> |ORA-00600: internal error code, arguments: [5120], [0], [16], [369],
> |[2], [], [], []
> |
> |Sun Nov 02 13:45:42 2003
> |SMON: terminating instance due to error 600
> |Sun Nov 02 13:45:42 2003
> |Errors in file C:\oracle\admin\orakmu\bdump\orakmuDBW0.TRC:
> |ORA-00600: internal error code, arguments: [], [], [], [], [], [], [], []
> |
> |Instance terminated by SMON, pid = 688
> |
>
>
>
> +=========================================
> | Log ACTION3
> | Descipton: Opening of SYSTEM tablespace only + RESETLOGS
> +----------------------------------------------------------------------
>
> | ALTER DATABASE OPEN RESETLOGS
> |
> | RESETLOGS is being done without consistency checks. This may
> |result
> | in a corrupted database. The database should be recreated.
> | RESETLOGS after incomplete recovery UNTIL CHANGE 29797269
> | Sun Nov 02 14:09:00 2003
> | Thread 1 opened at log sequence 1
> | Current log# 3 seq# 1 mem# 0: D:\ORADATA\REDO01A.LOG
> | Successful open of redo thread 1.
> | Sun Nov 02 14:09:00 2003
> | SMON: enabling cache recovery
> | Sun Nov 02 14:09:00 2003
> | Errors in file C:\oracle\admin\orakmu\udump\ORA00528.TRC:
> | ORA-00600: internal error code, arguments: [25012], [1], [2], [], [],
[],
> |[], []
> |
> | Sun Nov 02 14:09:01 2003
> | Errors in file C:\oracle\admin\orakmu\udump\ORA00528.TRC:
> | ORA-00600: internal error code, arguments: [25012], [1], [2], [], [],
[],
> |[], []
> |
> | Sun Nov 02 14:09:01 2003
> | Error 600 happened during db open, shutting down database
> | USER: terminating instance due to error 600
> | Instance terminated by USER, pid = 528
> | ORA-1092 signalled during: ALTER DATABASE OPEN
> |RESETLOGS
>
>
>

ORA-00600 [5120] This ora-600 has to do with
tablespace quota and possible corruption when it comes to tablespace information.

Suggest you open a TAR

ORA-00600: internal error code, arguments: [25012],

think that means the DB cant find the online redo logs

get help from Support Received on Sun Nov 02 2003 - 17:03:32 CST