InternalError ORA-600 arg [12803]
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: InternalError ORA-600 arg [12803]

  1. #1
    Join Date
    May 2002
    Posts
    22

    Red face

    Gurus....


    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.

    ORA-00600 [12803]...

    could anyone explain for this error please.....

    Now I'm restoring my db from export backup...
    since I don't have any other idea....


    thanks......
    let's eat fish!

  2. #2
    Join Date
    Mar 2001
    Posts
    46
    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?
    ora_newbie@yahoo.com

  3. #3
    Join Date
    Aug 2000
    Location
    Shanghai
    Posts
    433
    Imron , someone face the same problem and the solution is :

    Doc ID: Note:1026653.6
    Subject: ORA-600[12803] UNABLE TO CONNECT FROM SQL*PLUS
    Type: PROBLEM
    Status: PUBLISHED
    Content Type: TEXT/PLAIN
    Creation Date: 31-JAN-1997
    Last Revision Date: 10-APR-2001


    Problem Description:
    ====================

    All users (including SYSTEM) are unable to connect to SQL*PLUS and receive
    ORA-600[12803]. The DBA is only able to connect internal from Server Manager
    or SQL*DBA.


    Solution Description:
    =====================

    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
    existing sessions.


    To recreate the AUDSES$ sequence:
    ---------------------------------

    1. Login to SQL*DBA or Server Manager as internal and issue the
    following commands:

    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
    minvalue 1
    maxvalue 32000
    cycle
    cache 20
    noorder;

    4. You should now be able to connect to SQL*PLUS normally


    Explanation:
    ============

    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.


    Solution References:
    ====================

    1. www.dbasupport.com
    2. www.dbforums.com
    3. www.itpub.net
    4. www.csdn.net
    5. www.umlchina.com
    6. www.tek-tips.com
    7. www.cnforyou.com
    8. fm365.federal.com.cn
    9. www.programmersheaven.com
    10.http://msdn.microsoft.com/library/default.asp
    ligang1000@hotmail.com

  4. #4
    Join Date
    May 2002
    Posts
    22

    Talking

    Hi...!!

    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.... ;-)...

    thanks anyway......
    let's eat fish!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width