This ora-600 is issued when the SCN in a data block is ahead of the
current SCN; are you sure the restore was OK ?
According to Metalink Note:28929.1 listed underneath there should be
more arguments to this ora-600 than the single 2662 you mentioned.
Regards
Hans
########################################################################
##########
Subject: ORA-600 [2662] "Block SCN is ahead of Current SCN"
Doc ID: Note:28929.1 Type: REFERENCE
Last Revision Date: 27-MAR-2006 Status: PUBLISHED
Note: For additional ORA-600 related information please read Note
146580.1
PURPOSE:
This article discusses the internal error "ORA-600 [2662]", what
it means and possible actions. The information here is only applicable
to the versions listed and is provided only for guidance
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-600 [2662] occurs when an SCN is compared to the dependent SCN
stored in a UGA variable.
If the SCN is less than the dependent SCN then we signal the ORA-600
[2662]
internal error.
ARGUMENTS:
Arg [a] Current SCN WRAP
Arg [b] Current SCN BASE
Arg [c] dependent SCN WRAP
Arg [d] dependent SCN BASE
Arg [e] Where present this is the DBA where the dependent SCN came
from.
FUNCTIONALITY:
File and IO buffer management for redo logs
IMPACT:
INSTANCE FAILURE
POSSIBLE PHYSICAL CORRUPTION
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.
Known Issues:
Bug# 4453449 See Note 4453449.8
OERI:3020 / corruption errors from multiple FLASHBACK DATABASE
Fixed: 10.2.0.2, 11
Bug# 2899477 See Note 2899477.8
Minimise risk of a false OERI[2662]
Fixed: 9.2.0.5, 10.1.0.2
Bug# 2764106 See Note 2764106.8
False OERI[2662] possible on SELECT which can crash the instance
Fixed: 9.2.0.5, 10.1.0.2
Bug# 2216823 See Note 2216823.8
OERI [2662] reusing a TEMPFILE with a restored database
Fixed: 10.1.0.2
Bug# 2054025 See Note 2054025.8
OERI:2662 possible on new TEMPORARY index block
Fixed: 9.0.1.3, 9.2.0.1
Bug# 851959 See Note 851959.8
OERI:2662 possible from distributed OPS select
Fixed: 7.3.4.5
Bug# 647927 P See Note 647927.8
Digital Unix ONLY: OERI:2662 could occur under heavy load
Fixed: 8.0.4.2, 8.0.5.0
-----Original Message-----
From: BenBart
[mailto:oracledba-ezmlmshield-x3056712.[Email address protected]
Sent: donderdag 30 maart 2006 13:49
To: LazyDBA Discussion
Subject: ORA-00600: internal error code, arguments: [2662]
Hi all,
Does anyone have any tricks up their sleeves to get around this problem?
Customer have a DEV database that went down, restore filesystems from a
filesystems backup, can do startup mount, recover database reports Media
Recovery complete but ALTER DATABASE OPEN RESETLOGS gives the above
error.
Any response or advise will be very much appreciated. Perhaps there are
some hidden parameters that I can use to get around this?
Thanks in advance ...
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.
Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
Oracle LazyDBA home page