Ora-00600
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 3 of 3

Thread: Ora-00600

  1. #1
    Join Date
    Jan 2007
    Posts
    231

    Ora-00600

    Hello,
    Today, i met with a problem ora-00600.What is the actual problem it specifies.
    ORA-00600: internal error code, arguments: [12235], [], [], [], [], [], [], []

    Thanks in advance.

  2. #2
    Join Date
    Dec 2002
    Location
    Bangalore ( India )
    Posts
    2,434
    can be anything.. you must have trace in core dump..?

  3. #3
    Join Date
    Apr 2006
    Posts
    50
    If you login to metalink and use the ora-600 lookup tool you get the following output for argument 12235

    PURPOSE:
    This article discusses the internal error "ORA-600 [12235]", what
    it means and possible actions. The information here is only applicable
    to the versions listed and is provided only for guidance.

    ERROR:
    ORA-600 [12235] [a] [b] [c] [d] [e]

    VERSIONS:
    versions 7.0 to 9.2

    DESCRIPTION:

    This error shows up when Oracle detects an Oracle defunct process.

    When an Oracle process starts up, it reads data from the SGA that defines
    what type of process it should become.

    If the process does not locate any valid customization data, it reports
    ORA-600 [12235] and exits.

    On a heavily loaded system, ORA-600 [12235] may be a symptom that the server
    process was too slow in starting. That is, the process that initiated the
    new server may timeout waiting for the new process to start and abandon the
    new server request. In the new server process it is possible that the new
    server reaches the code to customize its operation before the os request to
    kill the process is actioned. The messages "ksbsrv: No startup
    acknowledgement from forked process ..." and "Timed out trying to start
    shared server ..." may be reported to trace and alert files.

    FUNCTIONALITY:
    USER/ORACLE INTERFACE LAYER

    IMPACT:
    NO IMPACT

    SUGGESTIONS:

    Ignore the error.

    One of the most common reasons for this error to be reported is that
    someone typed 'oracle' manually at the OS prompt.

    If this error is reported regularly and appears not to be explained
    by comments made in this note, contact Oracle Support Services.

    Known Issues:

    Bug# 3616023 P See Note 3616023.8
    Tru64: "skgpspawn failed:category = 27143" during process / instance startup
    Fixed: 10.2.0.1

    Bug# 405159 See Note 405159.8
    OERI:12235 possible starting any slave process
    Fixed: 8.0.6.0

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