ORA-00600: internal error code, arguments: [7001], [1], [], [], [], [], [], []
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: ORA-00600: internal error code, arguments: [7001], [1], [], [], [], [], [], []

  1. #1
    Join Date
    Apr 2000
    Location
    McDonough, GA, USA
    Posts
    6
    Please Help.....

    ORA-00600: internal error code, arguments: [7001], [1], [], [], [], [], [], []


    lenaf7@yahoo.com
    Selena Flowers

  2. #2
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    look metalink, ora-00600 are not documented errors

  3. #3
    Join Date
    Apr 2000
    Location
    McDonough, GA, USA
    Posts
    6

    Ora 600 Argument 7001

    I've seen every other error but argument 7001
    Selena Flowers

  4. #4
    Join Date
    Jun 2000
    Location
    Madrid, Spain
    Posts
    7,448
    if there is nothing on Metalink you better open an iTAR

  5. #5
    Join Date
    Apr 2001
    Posts
    108
    You will have to open an iTar with Oracle. That error message is often associated with a data dictionary corruption problem. (I found that on Metalink.) There is also a bug listed for that error that is reported fixed in 8.1.6.
    Eric Hanson

    There are 10 types of people in the world:

    Those who understand binary and those who don't!

  6. #6
    Join Date
    Apr 2000
    Location
    McDonough, GA, USA
    Posts
    6
    WHat is the bug#? I looked on Metalink all day yesterday and I never found an issue related to this specific error.

    Thanks for your help..

    Selena Flowers

  7. #7
    Join Date
    Apr 2001
    Posts
    108

    ora-600 errors

    I'll past the reply out of Metalink.

    Hi. The trace file is not for a SNP process, but your alert.log shows that they terminated for some reason. Is that part of this error consistent? Do you have any jobs in DBA_JOBS? If the errors repeat after database startup prior to any users connecting, it is possible that a job is producing this error. You should try restarting the database with JOB_QUEUE_PROCESSES = 0 to see if the error stops.

    This error appears to signal that an attempt was made to convert an Oracle number to a (signed) integer or vice versa and an overflow occurred during the attempted conversion. Unfortunately, due to the lack of a valid trace file (this is bug 934839, which will be fixed in the next patchset release for 8.1.6), it is not clear what the cause is.

    Hope this provides some help.

    Eric Hanson

    There are 10 types of people in the world:

    Those who understand binary and those who don't!

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