Undskyld! for the mistake of names. Ah yes, the 10015 and the adjust_scn. Those were the days.

K Gopalakrishnan wrote:
Mogens:

Yes. You are right. You have to bump the SCNs globally
(i.e. across all data files to higher number, say 1 Billion)
using the event 10015 and ADJUST_SCN. Then we can safely
open the database and rebuild that.

KG


Best Regards,
K Gopalakrishnan




-----Original Message-----
Norgaard
Sent: Monday, January 06, 2003 11:59 PM
To: Multiple recipients of list ORACLE-L


This response from Oracle is not a good one. Kirti is on the right track
regarding the SCN stuff as far as I remember. Other than that, I know
that Peter Gram and Bjorn Engsig (among a lot of other guys) might be
able to suggest something, so I've CC'ed them.

I have my own law on ora-600s: If you supply all the required
information (tracefiles, alertlogs, repro-case, etc.) chances are
Support is not gonna need them. If you miss out just one of those
things, chances are Support will tell you they cannot proceed without
that vital piece of information. In other words: There's no hope :-)))

Could also be related to db-links between v7 and v8...

But back to the good questions from Kirti: Have you set the funny
_-parameters he mentions?


Mogens

PS: I do beleive there are ways around this with an alter system or
alter session command where you bump the SCN some <level>, but
Peter/Bjorn/someone can confirm this.

Sinardy Xing wrote:

  
Hi guys,


This is what I get from Oracle

==============================================================

Hi Sinardy,

I've check several bug looking for the cause of this problem. However, what
    
I've found is that Development could not diagnosis the problem other than
the possibily hat there was some memory corruption that gave a bad SCN.
Although, they could "sometimes" determine the root cause prior to the
problem occurring by using certain parameters were set in the database.
  
Those parameters are:

a)_db_block_cache_protect.
b)_db_block_checking
c)DB_BLOCK_CHECKSUM

They also recommended running dbverify on all datafiles tomake sure all
    
files are clean on disk.
  
IMPORTANT
==========
These parameter may help later determine what cause the ORA-600 [2662] (and
    
it's not for certain that a cause can be found). They parameters does have
some performance overhead, but unfortunately this is the only way that can
help in catching and we have to wait until the problem happens again.
  
So, the bottomline is there is no list of reason for why this error
    
occuring other than the error occurs when a data block SCN is ahead of the
current SCN.
  
Sorry Sinardy, we don't have more information.

Thanks!
Wonda

=================================================================

What can I do, help me please...


Sinardy



-----Original Message-----
Sent: 07 January 2003 13:09
To: Multiple recipients of list ORACLE-L


Sinardy

ORA-0600 is really an encoded message from Oracle that reads :

'Thank you for helping find yet another bug in our software. You can now
release your sphincter (some herbal tea might help), especially if this has
cropped up in production. We suggest you do not try to solve this one by
yourself, which is why the arguments are supplied. Kindly call OWWS with
your CSI number, tell them exactly which version and platform you ran this
on, and if we have encountered this previously, there is a small chance
that we could have a patch. If not, please do not hold your breath waiting,
while we assign this to an experienced software engineer, or perhaps a
recent college grad, in which case, you're toast !' However, we will ask
you to ftp up to our ftp site loads of dumps and traces which might prove
useful.

Seriously though, ORA-0600 are mysteries. Your best chance is to get Tim
Gorman to look at it, he has an amazing knowledge of these. And of course,
Tim should not work for free either. (Tim, it was 10% commission we agreed
on, right ? ) :-)

Ferenc Mantfeld

-----Original Message-----
From:	Sinardy Xing [SMTP:[EMAIL PROTECTED]]
Sent:	Tuesday, January 07, 2003 2:34 PM
To:	Multiple recipients of list ORACLE-L
Subject:	ORA-00600: [2662]

Hi all,

I hit by this error

ORA-00600: internal error code, arguments: [2662], [0], [54151123], [0],
[54173017], [16781180], [], []


Can you help me where to find info about this error




Sinardy

--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: Sinardy Xing
 INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).



    


--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: =?ISO-8859-1?Q?Mogens_N=F8rgaard?=
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).


  

Reply via email to