My database version is 9.2.0.6, i got error in alert log file ORA-00600: internal error code, arguments: [2662], [0], [1822694840], [0], [1977
003713], [4194306], [], []
alert log file
{\code\}
Sat Oct 18 15:25:45 2008
alter database open read only
Sat Oct 18 15:25:45 2008
SMON: enabling cache recovery
Sat Oct 18 15:25:45 2008
Database Characterset is WE8ISO8859P1
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
Completed: alter database open read only
Sat Oct 18 15:25:59 2008
Errors in file /arch/dump/udump/icai_ora_18711.trc:
ORA-00600: internal error code, arguments: [2662], [0], [1822694840], [0], [1977
003713], [4194306], [], []
Sat Oct 18 15:26:12 2008
Errors in file /arch/dump/udump/icai_ora_18711.trc:
ORA-00600: internal error code, arguments: [2662], [0], [1822695912], [0], [1977
003713], [4194306], [], []
ORA-00600: internal error code, arguments: [2662], [0], [1822694840], [0], [1977
003713], [4194306], [], []
Mon Oct 20 10:43:34 2008
***Warning - Executing transaction without active Undo Tablespace
***Warning - Executing transaction without active Undo Tablespace{\code\}
{\code\}
I know that ora-0600 is an oracle internal error, and when i checked the metalink i found that 2662 internal error occurs occurs when an SCN is compared to the dependent SCN
**stored in a UGA variable.[/b
Suggestions which has been found in metalik is
SUGGESTIONS:
There are different situations where ORA-600 [2662] can be raised.
It can be raised on startup or duing database operation.
If not using Parallel Server, check that 2 instances have not mounted
the same database.
Check for SMON traces and have the alert.log and trace files ready
to send to support.
Check the SCN difference [argument d]-[argument b].
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.
If the Known Issues section below does not help in terms of identifying
a solution, please submit the trace files and alert.log to Oracle
Support Services for further analysis.
nut as argument b and d is zero , so it means that SCN are equal then why this error is raised
and how to check the current SCN...
and this database is maual physical standby...**