Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: ORA-01092 error after upgrade to 9.2

Re: ORA-01092 error after upgrade to 9.2

From: Pete Sharman <peter.sharman_at_oracle.com>
Date: 16 Jul 2002 21:16:31 -0700
Message-ID: <ah2r2v029fk@drn.newsguy.com>


In article <47006ee2.0207161826.6d782e0d_at_posting.google.com>, suthaz_at_yahoo.com says...
>
>G'day folks,
>
>After upgrading Oracle from 9.0.1.3 to 9.2 (using dbua) on
>Sun-Blade-100 (SunOS 5.8), I get the following error when I tried to
>startup the database instance in SQLPlus:
>
>
>PLSQL/admora1>startup
>ORACLE instance started.
>
>Total System Global Area 286188248 bytes
>Fixed Size 434904 bytes
>Variable Size 218103808 bytes
>Database Buffers 67108864 bytes
>Redo Buffers 540672 bytes
>Database mounted.
>ORA-01092: ORACLE instance terminated. Disconnection forced
>
>---------------------------------------------------------
>
>The alert log has the following details:
>
>Wed Jul 17 11:31:26 2002
>Updating 9.2.0.1.0 NLS parameters in sys.props$
>-- adding 9.0.1.3.0 NLS parameters.
>Wed Jul 17 11:31:34 2002
>Errors in file /space/oracle/oracle9i/admin/admora1/udump/admora1_ora_1030.trc:
>ORA-00600: internal error code, arguments: [17069], [0x386DC0350], [],
>[], [], [
>], [], []
>Wed Jul 17 11:31:40 2002
>Errors in file /space/oracle/oracle9i/admin/admora1/udump/admora1_ora_1030.trc:
>ORA-00600: internal error code, arguments: [krvxdka2], [], [], [], [],
>[], [], [
>]
>Wed Jul 17 11:31:43 2002
>Errors in file /space/oracle/oracle9i/admin/admora1/udump/admora1_ora_1030.trc:
>ORA-00600: internal error code, arguments: [krvxdka2], [], [], [], [],
>[], [], [
>]
>Error 600 happened during db open, shutting down database
>USER: terminating instance due to error 600
>Instance terminated by USER, pid = 1030
>ORA-1092 signalled during: ALTER DATABASE OPEN...
>
>-----------------------------------------------------
>
>Any ideas on how to rectify this problem?
>
>TIA,
>Sutha

Yup, call Support and tell them the first argument for the 600 errors. A 600 error means you got somewhere you shouldn't and have an unhandled exception. The only resolution is to call Support and they will either:

  1. Tell you how to fix the problem
  2. Tell you it's a documented bug and what the patch is to fix it
  3. Tell you you're lucky enough to be the first one to strike this bug.

HTH. Additions and corrections welcome.

Pete

SELECT standard_disclaimer, witty_remark FROM company_requirements; Received on Tue Jul 16 2002 - 23:16:31 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US