ora-600
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 4 of 4

Thread: ora-600

  1. #1
    Join Date
    Jun 2000
    Posts
    104
    hello,
    when I try to query v$pwfile_user,I get the error ora-600
    internal error
    ora-00600-internal error code,arguments :[12333],[7],[5],[49],[],[]

    I am also not being able to connect as internal/oracle.
    its saying invalid username/password.
    should I recreate the password file as pando said,I also made
    remote_login_paaswordfile=shared
    still it does not work.
    bye

  2. #2
    Join Date
    Sep 2000
    Posts
    128
    Nicked this from an Oracle Forum:

    ---------------
    The ORA-600 [12333] error sequence is a generic error which just means that something has gone wrong in the communication between the client and the server processes.

    Often, this could be the result of an abnormal condition (a process is inadvertently killed, or a database shuts down, for example).
    ------------

    Do you get any trace files - I'd take a look at these and raise them with Oracle if need be.


    Terry

  3. #3
    Join Date
    Jun 2000
    Posts
    104
    THIS FILE ORA00134.TRC WAS HAVING ERRORS AS SHOWN IN ALERTLOG.BUT I COULD NOT FIND ANYTHING IN IT.
    TKPROF: Release 8.1.5.0.0 - Production on Fri Nov 10 13:25:59 2000

    (c) Copyright 1999 Oracle Corporation. All rights reserved.

    Trace file: e:\oracle\admin\ortelapp\udump\ora00134.trc
    Sort options: default

    ********************************************************************************
    count = number of times OCI procedure was executed
    cpu = cpu time in seconds executing
    elapsed = elapsed time in seconds executing
    disk = number of physical reads of buffers from disk
    query = number of buffers gotten for consistent read
    current = number of buffers gotten in current mode (usually for update)
    rows = number of rows processed by the fetch or execute call
    ********************************************************************************
    Trace file: e:\oracle\admin\ortelapp\udump\ora00134.trc
    Trace file compatibility: 7.00.12
    Sort options: default

    1 session in tracefile.
    0 user SQL statements in trace file.
    0 internal SQL statements in trace file.
    0 SQL statements in trace file.
    0 unique SQL statements in trace file.
    27370 lines in trace file.



  4. #4
    Join Date
    Sep 2000
    Posts
    128
    Don't run it through tkrpof - that's only any use for generating stats and execution plans.

    The trace file will probably just contain a stack dump which will most likely need to be sent to Oracle for analysis.

    You may find some useful readable information at the start of it though.

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