My prod db is 7.3.4 installed on Sun Solaris 2.6
due to power outage, I encounter this error.
Nothing happend when I booted the database, but
when I tried to make user connection, Internal error comes up.
could anyone explain for this error please.....
Now I'm restoring my db from export backup...
since I don't have any other idea....
let's eat fish!
I've only seen that message w/ trying to connect to a 9i database w/ 8i JDBC drivers. Could you be using the wrong oracle client on the Sun server?
Imron , someone face the same problem and the solution is :
Doc ID: Note:1026653.6
Subject: ORA-600 UNABLE TO CONNECT FROM SQL*PLUS
Content Type: TEXT/PLAIN
Creation Date: 31-JAN-1997
Last Revision Date: 10-APR-2001
All users (including SYSTEM) are unable to connect to SQL*PLUS and receive
ORA-600. The DBA is only able to connect internal from Server Manager
If the user has in fact deleted the AUDSES$ sequence, it can be re-created
providing there are no users connected other than internal.
If any users are connected other than Internal, have them log off normally,
shutdown the database, and startup before creating the sequence.
*** NOTE: If there are current users connected when this problem
is discovered, it is NOT recommended to re-create AUDSES$,
as this could have unpredictable consequences for the
To recreate the AUDSES$ sequence:
1. Login to SQL*DBA or Server Manager as internal and issue the
2. Drop sequence audses$;
(if this sequence was already dropped, you'll see a message
indicating the sequence does not exist)
3. Create sequence audses$
start with 1
increment by 1
4. You should now be able to connect to SQL*PLUS normally
This internal error is raised when the sequence object identifier number
cannot be obtained from the internal sequence AUDSES$, which is required for
new sessions connecting to the database. Connecting internal does not
increment this sequence. The error can be due to this sequence having been
dropped inadvertently by a user while connected as SYSTEM.
Recreating the AUDSES$ sequence will allow new connections to the database to
obtain the sequence object identifier number required for a successful
connection to the database.
it seems, somehow the AUDSES$ was vannished
during power outage...
actually I got this problem for 3 times,
the others two occured last year on my Prod DB V 6.2
and the cause is the same, due to power outage...
maybe Oracle put AUDSES$ inside the power suppy
instead of my RAID.... ;-)...
let's eat fish!
Click Here to Expand Forum to Full Width