dgupta70
asked on
ORA-0600
Friends,
I need help.
I am on windows 2000. Database is oracle 9i. Database s starting up clean but getting shutdown within minutes. Here is the alert_log.
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 98 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:36:22 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 99 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:36:51 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 100 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:37:18 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON exceeded the maximum limit of 100 internal error(s).
Fri Apr 22 12:37:34 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 6464
Fri Apr 22 12:38:17 2005
Starting ORACLE instance (normal)
Starting up ORACLE RDBMS Version: 9.0.1.1.1.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
shared_pool_size = 301989888
large_pool_size = 10485760
java_pool_size = 58720256
control_files = e:\oracle\oradata\ldss\CON
db_block_size = 8192
db_cache_size = 721420288
db_cache_advice = ON
compatible = 9.0.0
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS
undo_retention = 10800
remote_login_passwordfile=
db_domain = cp.lucent.com
instance_name = ldss
dispatchers = (PROTOCOL=TCP)(SER=MODOSE)
hash_area_size = 1048576
background_dump_dest = e:\oracle\admin\ldss\bdump
user_dump_dest = e:\oracle\admin\ldss\udump
core_dump_dest = e:\oracle\admin\ldss\cdump
sort_area_size = 1916927
db_name = ldss
open_cursors = 300
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Fri Apr 22 12:38:21 2005
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PR
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PR
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PR
Fri Apr 22 12:38:23 2005
ALTER DATABASE MOUNT
Fri Apr 22 12:38:29 2005
Successful mount of redo thread 1, with mount id 1239416961.
Fri Apr 22 12:38:29 2005
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Fri Apr 22 12:38:30 2005
ALTER DATABASE OPEN
Fri Apr 22 12:38:30 2005
Beginning crash recovery of 1 threads
Fri Apr 22 12:38:30 2005
Started first pass scan
Fri Apr 22 12:38:30 2005
Completed first pass scan
Fri Apr 22 12:38:30 2005
Started recovery at
Thread 1: logseq 13257, block 77, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 2 Seq 13257 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\LDSS\RED
Mem# 1 errs 0: F:\ORACLE\ORADATA\LDSS\RED
Fri Apr 22 12:38:30 2005
Ended recovery at
Thread 1: logseq 13257, block 81, scn 0.961818048
6 data blocks read, 6 data blocks written, 4 redo blocks read
Crash recovery completed successfully
Fri Apr 22 12:38:30 2005
Thread 1 advanced to log sequence 13258
Thread 1 opened at log sequence 13258
Current log# 3 seq# 13258 mem# 0: E:\ORACLE\ORADATA\LDSS\RED
Current log# 3 seq# 13258 mem# 1: F:\ORACLE\ORADATA\LDSS\RED
Successful open of redo thread 1.
Fri Apr 22 12:38:30 2005
SMON: enabling cache recovery
Fri Apr 22 12:38:31 2005
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Fri Apr 22 12:38:31 2005
SMON: enabling tx recovery
Fri Apr 22 12:38:32 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818163], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:39:12 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818163], [0], [962272929], [4228158], [], []
Fri Apr 22 12:39:13 2005
replication_dependency_tra
Completed: ALTER DATABASE OPEN
Fri Apr 22 12:39:54 2005
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 2 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:39:54 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 3 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:40:13 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 4 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:40:31 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 5 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:41:00 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 6 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:41:27 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
ANy idea, what is the problem and how to fix it.
Thanks
Deepak
I need help.
I am on windows 2000. Database is oracle 9i. Database s starting up clean but getting shutdown within minutes. Here is the alert_log.
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 98 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:36:22 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 99 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:36:51 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 100 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:37:18 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON exceeded the maximum limit of 100 internal error(s).
Fri Apr 22 12:37:34 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961798049], [0], [962272929], [4228158], [], []
SMON: terminating instance due to error 600
Instance terminated by SMON, pid = 6464
Fri Apr 22 12:38:17 2005
Starting ORACLE instance (normal)
Starting up ORACLE RDBMS Version: 9.0.1.1.1.
System parameters with non-default values:
processes = 150
timed_statistics = TRUE
shared_pool_size = 301989888
large_pool_size = 10485760
java_pool_size = 58720256
control_files = e:\oracle\oradata\ldss\CON
db_block_size = 8192
db_cache_size = 721420288
db_cache_advice = ON
compatible = 9.0.0
fast_start_mttr_target = 300
undo_management = AUTO
undo_tablespace = UNDOTBS
undo_retention = 10800
remote_login_passwordfile=
db_domain = cp.lucent.com
instance_name = ldss
dispatchers = (PROTOCOL=TCP)(SER=MODOSE)
hash_area_size = 1048576
background_dump_dest = e:\oracle\admin\ldss\bdump
user_dump_dest = e:\oracle\admin\ldss\udump
core_dump_dest = e:\oracle\admin\ldss\cdump
sort_area_size = 1916927
db_name = ldss
open_cursors = 300
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4
CKPT started with pid=5
SMON started with pid=6
RECO started with pid=7
Fri Apr 22 12:38:21 2005
starting up 1 shared server(s) ...
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PR
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PR
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PR
Fri Apr 22 12:38:23 2005
ALTER DATABASE MOUNT
Fri Apr 22 12:38:29 2005
Successful mount of redo thread 1, with mount id 1239416961.
Fri Apr 22 12:38:29 2005
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Fri Apr 22 12:38:30 2005
ALTER DATABASE OPEN
Fri Apr 22 12:38:30 2005
Beginning crash recovery of 1 threads
Fri Apr 22 12:38:30 2005
Started first pass scan
Fri Apr 22 12:38:30 2005
Completed first pass scan
Fri Apr 22 12:38:30 2005
Started recovery at
Thread 1: logseq 13257, block 77, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 2 Seq 13257 Reading mem 0
Mem# 0 errs 0: E:\ORACLE\ORADATA\LDSS\RED
Mem# 1 errs 0: F:\ORACLE\ORADATA\LDSS\RED
Fri Apr 22 12:38:30 2005
Ended recovery at
Thread 1: logseq 13257, block 81, scn 0.961818048
6 data blocks read, 6 data blocks written, 4 redo blocks read
Crash recovery completed successfully
Fri Apr 22 12:38:30 2005
Thread 1 advanced to log sequence 13258
Thread 1 opened at log sequence 13258
Current log# 3 seq# 13258 mem# 0: E:\ORACLE\ORADATA\LDSS\RED
Current log# 3 seq# 13258 mem# 1: F:\ORACLE\ORADATA\LDSS\RED
Successful open of redo thread 1.
Fri Apr 22 12:38:30 2005
SMON: enabling cache recovery
Fri Apr 22 12:38:31 2005
Undo Segment 1 Onlined
Undo Segment 2 Onlined
Undo Segment 3 Onlined
Undo Segment 4 Onlined
Undo Segment 5 Onlined
Undo Segment 6 Onlined
Undo Segment 7 Onlined
Undo Segment 8 Onlined
Undo Segment 9 Onlined
Undo Segment 10 Onlined
Successfully onlined Undo Tablespace 1.
Fri Apr 22 12:38:31 2005
SMON: enabling tx recovery
Fri Apr 22 12:38:32 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818163], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing logging scn->time mapping.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:39:12 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818163], [0], [962272929], [4228158], [], []
Fri Apr 22 12:39:13 2005
replication_dependency_tra
Completed: ALTER DATABASE OPEN
Fri Apr 22 12:39:54 2005
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 2 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:39:54 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 3 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:40:13 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 4 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:40:31 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 5 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:41:00 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
Non-fatal internal error happenned while SMON was doing extent coalescing.
SMON encountered 6 out of maximum 100 non-fatal internal errors.
Fri Apr 22 12:41:27 2005
Errors in file e:\oracle\admin\ldss\bdump
ORA-00600: internal error code, arguments: [2662], [0], [961818168], [0], [962272929], [4228158], [], []
ANy idea, what is the problem and how to fix it.
Thanks
Deepak
There are many reasons for ORA-600 error
Mishandled block information (in certain conditions), upon reading the database block, which indicates that a good block is corrupted. This is the bug in the Oracle version 8.1.x - 9.x, where the Oracle will raise the error:
ORA-600 [kcoapl_blkchk][ABN][RFN][
Pointing to failure condition during block check. This only happens when block checking is enabled
Oracle error indicating soft corruption:
ORA-00600: internal error code, arguments: [3339], [RBA1], [RBA2], [], [], [], [], []
There is a TOOL
Oracle Metalink has an ORA-600 Lookup tool.
http://ora-00600.ora-code.com/
jaspreet
Mishandled block information (in certain conditions), upon reading the database block, which indicates that a good block is corrupted. This is the bug in the Oracle version 8.1.x - 9.x, where the Oracle will raise the error:
ORA-600 [kcoapl_blkchk][ABN][RFN][
Pointing to failure condition during block check. This only happens when block checking is enabled
Oracle error indicating soft corruption:
ORA-00600: internal error code, arguments: [3339], [RBA1], [RBA2], [], [], [], [], []
There is a TOOL
Oracle Metalink has an ORA-600 Lookup tool.
http://ora-00600.ora-code.com/
jaspreet
ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:
timeouts
file corruption
failed data checks in memory
hardware, memory, or I/O errors
incorrectly restored files
The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.
Action: Report this error to Oracle Support Services after gathering the following information:
events that led up to the error
the operations that were attempted that led to the error
the conditions of the operating system and databases at the time of the error
any unusual circumstances that occurred before receiving the ORA-00600 message
contents of any trace files generated by the error
the relevant portions of the Alter files
Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.
Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:
timeouts
file corruption
failed data checks in memory
hardware, memory, or I/O errors
incorrectly restored files
The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.
Action: Report this error to Oracle Support Services after gathering the following information:
events that led up to the error
the operations that were attempted that led to the error
the conditions of the operating system and databases at the time of the error
any unusual circumstances that occurred before receiving the ORA-00600 message
contents of any trace files generated by the error
the relevant portions of the Alter files
Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I think my comments were also helpful. If not author should have posted back to ask for more help.
Jaspreet
Jaspreet
sorry my mistake...
Will need more information to start down the troubleshooting path:
Is this a new DB or a system that has been running for a while?
If new DB: I'd say it's a bug and you should go to at least the latest patchset or as I already suggested, get to 9.2.
If old DB: What has changed?