Forgot your password?    
+ Reply to Thread
Results 1 to 5 of 5

Thread: "ora -600 & ora -7445"

  1. #1
    Oracle DBA
    Join Date
    Oct 2011
    Posts
    17

    "ora -600 & ora -7445"

    Troubleshoot ORA-600 and ORA-7445 errors :-

    In general, ORA-7445 and ORA-600 messages should be reported to Oracle.
    They are the internal errors of oracle.
    We should consider the argument that follow the error. Because there are many reasons for that error and that argument tells, in which area one should look for to resolve the problem.

    For ORA -600

    This contains all internal error message for Oracle program exceptions.
    It indicates that a process has met a low-level, unexpected condition.
    Various causes of this message include:
    * time-outs
    * file corruption
    * failed data checks in memory
    * hardware, memory, or I/O errors
    * incorrectly restored files

    Action :-Report as a bug - the first argument is the internal error number.

    For ORA-7445

    An operating system exception occurred which should result in the creation of a core file.

    We have to apply the patch sets or patch to resolve that internal errors.

  2. #2
    Expert Oracle Administrator
    Join Date
    Oct 2011
    Location
    New Delhi, India
    Posts
    427
    Additionally ,

    To Diagnose these errors , look at the subsequent arguments relating to the error.
    The subsequent arguments would proivide more insight on the type of error . eg : It could be a heap error.

    In most cases , you would find an accompaning trace file (details of which will be there in the alert log) . This trace file can be provided to Oracle to diagnose the error.
    Diagnosis is normally done using the stack trace in the accompanying trace file.

  3. #3
    Oracle DBA
    Join Date
    Oct 2011
    Posts
    17

    Internal error experiance.....

    Quote Originally Posted by harsh View Post
    Troubleshoot ORA-600 and ORA-7445 errors :-

    In general, ORA-7445 and ORA-600 messages should be reported to Oracle.
    They are the internal errors of oracle.
    We should consider the argument that follow the error. Because there are many reasons for that error and that argument tells, in which area one should look for to resolve the problem.

    For ORA -600

    This contains all internal error message for Oracle program exceptions.
    It indicates that a process has met a low-level, unexpected condition.
    Various causes of this message include:
    * time-outs
    * file corruption
    * failed data checks in memory
    * hardware, memory, or I/O errors
    * incorrectly restored files

    Action :-Report as a bug - the first argument is the internal error number.

    For ORA-7445

    An operating system exception occurred which should result in the creation of a core file.

    We have to apply the patch sets or patch to resolve that internal errors.


    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01163: SIZE clause indicates 12800 (blocks), but should match header 2560
    ORA-01110: data file 7: '/u02/catbase/oradata/catalog/undotbs02.dbf'



    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01195: online backup of file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/catbase/oradata/catalog/system01.dbf'


    ORA-01112: media recovery not started

    tarting backup at 17-SEP-11
    RMAN-00571: ================================================== =========
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ================================================== =========
    RMAN-03002: failure of backup command at 09/17/2011 16:59:28
    RMAN-03014: implicit resync of recovery catalog failed
    RMAN-03009: failure of partial resync command on default channel at 09/17/2011 16:59:28
    RMAN-10015: error compiling PL/SQL program
    RMAN-10033: error during compilation of job step 1: ORA-04029: error ORA-600 occurred when querying ORA_KGLR7_DEPENDENCIES


    ORA_KGLR7_DEPENDENCIES: Error related to libraray cache...
    The arguments accompanying the ORA 600 error can help us diagnose the oracle internal or the bug we are experiencing.
    Last edited by Hemant; 10-31-2011 at 09:43 PM.

  4. #4
    Oracle DBA
    Join Date
    Oct 2011
    Posts
    11
    Thanks Harsh for very nice post.

  5. #5
    Expert Oracle Administrator
    Join Date
    Oct 2011
    Location
    Delhi, India, India
    Posts
    128
    good work!!
    Regards,
    -Amit

+ Reply to Thread

Similar Threads

  1. " Unable to find 'kshell' in path "
    By harsh in forum Oracle Apps Patching and Cloning, Installation , Migration,Upgrades
    Replies: 3
    Last Post: 03-31-2012, 09:16 PM
  2. " Unable to find 'kshell' in path "
    By harsh in forum Concepts,Service Management,Apache,OC4J,OPMN,JServ,Forms, Issues,Troubleshooting,
    Replies: 5
    Last Post: 11-12-2011, 04:53 PM

Tags for this Thread

Posting Permissions

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

DBA Lounge (P) Ltd. deals in Oracle Technologies on Consulting, Resourcing, Corporate Training


Online and corporate training available on Oracle Database 11g, Oracle 11g Real Application Cluster (RAC), Oracle Applications 11i/R12, Oracle Fusion Middleware 11g, Oracle Identity Management-OIM, Oracle Internet Directory 11g-OID, Oracle Business Intelligence Enterprise Edition-OBIEE, Oracle Golden Gate, Oracle Access Management-OAM, Oracle Internet Directory-ODS, Oracle Identity Analytics Architecture-OIA Statistics