Re: ORA-00600: [2662]

2003-01-07 Thread Mogens Nørgaard
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

Re: ORA-00600: [2662]

2003-01-07 Thread Peter Gram
Mogens I do agree that this ora-600 [2662] is in the code that handle SCN numbers, since SCN handling is used many places in the code the stack trace that show which path throw the code you took is necessary if there is no hits on metalink fits the problem ;-) Mogens Nørgaard wrote: This

RE: ORA-00600: [2662]

2003-01-07 Thread Rachel Carmichael
Ferenc, There's this new FREE product on the Metalink site. It's called ORA-600 Lookup (I don't bother to bookmark it, just do a search on that and the first one in the search list is the link to the product). You put in the version number, the first argument on the ora-600 and then, if there is

RE: ORA-00600: [2662]

2003-01-07 Thread Deshpande, Kirti
Mogens, You meant K. Gopal (aka X$KG) is on the right track... and not Kirti. ;) I do not recall posting in this thread. - Kirti -Original Message- Sent: Tuesday, January 07, 2003 1:59 AM To: Multiple recipients of list ORACLE-L This response from Oracle is not a good one. Kirti

RE: ORA-00600: [2662]

2003-01-07 Thread Deshpande, Kirti
Here is another product that goes after ORA-600: http://www.ubTools.com/cgi-bin/ib/ikonboard.cgi?act=Pages;page=iorabugfinder The creator, Danisment Unal, used to be on the list. - Kirti -Original Message- Sent: Tuesday, January 07, 2003 7:34 AM To: Multiple recipients of list

RE: ORA-00600: [2662]

2003-01-07 Thread K Gopalakrishnan
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

Re: ORA-00600: [2662]

2003-01-07 Thread Mogens Nørgaard
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

RE: ORA-00600: [2662]

2003-01-06 Thread mantfield
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

Re: ORA-00600: [2662]

2003-01-06 Thread K Gopalakrishnan
Sinardy: Have you force opened the database? (_allow_resetlogs_corruption). In this case the SCN Mismatch (block SCN vs Currnet SCN) is causing the OERI-2662, and you need to bump the SCNS globally to get the database up. Speak to Oracle Support and ask for the details to bump the SCN, then you

Re: ORA-00600: [2662]

2003-01-06 Thread K Gopalakrishnan
Other than the allow_resetlogs_corruption, _disable_logging also will greet you with OERI-2662 if the shutdown is not normal. KG --- Sinardy Xing [EMAIL PROTECTED] wrote: Hi all, I hit by this error ORA-00600: internal error code, arguments: [2662], [0], [54151123], [0], [54173017],

RE: ORA-00600: [2662]

2003-01-06 Thread MacGregor, Ian A.
http://metalink.oracle.com/metalink/plsql/showdoc?db=NOTid=153788.1 Can be used to look up such errors and also examine the stack trace. The lookup function does not return information on all the 600 error codes, it does not return any for yours. Ian MacGregor Stanford Linear Accelerator

RE: ORA-00600: [2662]

2003-01-06 Thread Sinardy Xing
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