6 Replies Latest reply: Jul 25, 2011 11:42 AM by 822194 RSS

    ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59D

    segzey
      Can anyone please try check out this ORA-600 error, ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59DA4],
      [2], [], [], [], [], [].
      My db went down abruptly due to power source ....now the database mounts successfully but when u try opening the db i.e. alter database open; it comes up with the error. Plz kindly treat urgently.Thanks
        • 1. Re: ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59D
          Oviwan
          check the ora 600 with this metalink utility:
          Troubleshoot an ORA-600 or ORA-7445 Error Using the Error Lookup Tool
          ID#: 153788.1

          HTH
          • 2. Re: ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59D
            Kamran Agayev A.
            For all kind of internal errors, you should open SR (Service Request) in metalink. You need to contact Oracle Support

            - - - - - - - - - - - - - - - - - - - - -
            Kamran Agayev A. (10g OCP)
            http://kamranagayev.wordpress.com
            [Step by Step install Oracle on Linux and Automate the installation using Shell Script |http://kamranagayev.wordpress.com/2009/05/01/step-by-step-installing-oracle-database-10g-release-2-on-linux-centos-and-automate-the-installation-using-linux-shell-script/]
            • 3. Re: ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59D
              Nicolas.Gasparotto
              Plz kindly treat urgently
              Even if I had a clue about the error you are facing to, you don't give your OS, the Oracle version...
              And if it was really urgent, open a P1 service request to your prefered Oracle support.

              Nicolas.
              • 4. Re: ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B
                Abk
                Check the following metalink document for error lookup

                153788.1
                • 5. Re: ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59D
                  669771
                  Hi,

                  ORA-00600: internal error code, arguments: [kcrfr_update_nab_2],
                  [0x7000000905969E8], [2], [], [], [], [], []

                  call stack:

                  ksedmp kgerinv kgeasnmierr kcrfr_update_nab kcrfr_read kcrfr_read_buffer
                  kcrfrgv kcratr1 kcratr kctrec kcvcrv kcfopd
                  adbdrv opiexe opiosq kpooprx kpoal8 opiodr

                  I found similar bugs with: 5692594, 6655116, 5364658

                  Regards,
                  Tom
                  http://asktom.cz
                  • 6. Re: ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0xB1B59D
                    822194
                    Hi all, I solved a similar issue... see how.

                    ---- Trying to recover the database after a power outage
                    RMAN> startup mount;
                    RMAN> recover database;

                    ****** Alert.log *******
                    Sun Jul 24 10:35:05 2011
                    Recovery of Online Redo Log: Thread 1 Group 7 Seq 2033 Reading mem 0
                    Mem# 0: /oracle/oradata1/DBPROD/onlinelog/o1_mf_7_6z2blmbz_.log
                    Mem# 1: /oracle/oradata2/DBPROD/onlinelog/o1_mf_7_6z2blp0t_.log
                    Sun Jul 24 10:35:09 2011
                    Errors in file /oracle/admin/DBPROD/udump/dbprod_ora_10868.trc:
                    ORA-00600: internal error code, arguments: [kcrfr_update_nab_2], [0x4A6307E38], [2], [], [], [], [], [] <<----------
                    *********

                    ----- Checking the redo logfile groups
                    SQL> select GROUP# , SEQUENCE#, ARCHIVED, STATUS from v$log order by SEQUENCE#
                    ********
                    GROUP# SEQUENCE# ARC STATUS
                    ---------- ---------- --- ----------------
                    8 2022 YES INACTIVE
                    9 2023 YES INACTIVE
                    10 2024 YES INACTIVE
                    11 2025 YES INACTIVE
                    12 2026 YES INACTIVE
                    6 2027 YES INACTIVE
                    1 2028 YES ACTIVE
                    2 2029 YES ACTIVE
                    3 2030 YES ACTIVE
                    4 2031 YES ACTIVE
                    5 2032 YES ACTIVE
                    7 2033 NO CURRENT <<<----------
                    ********

                    ----- Put the second member of current redo logfile group unavailable
                    ***
                    Mem# 0: /oracle/oradata1/DBPROD/onlinelog/o1_mf_7_6z2blmbz_.log
                    Mem# 1: /oracle/oradata2/DBPROD/onlinelog/o1_mf_7_6z2blp0t_.log
                    ***

                    mv /oracle/oradata2/DBPROD/onlinelog/o1_mf_7_6z2blp0t_.log /oracle/oradata2/DBPROD/onlinelog/o1_mf_7_6z2blp0t_.log.ori


                    ----- Try the recover again, you can see in the alert.log that Oracle use the remaining member of the redo logfile group
                    RMAN> recover database;
                    RMAN> shutdown immediate;
                    RMAN> startup;

                    - Remember to recreate the logfile group (or remove/add the logifle member you put unavailable)
                    SQL> alter database drop logfile group 7;
                    SQL> alter database add logfile group 7 SIZE <same size as group just removed>K;

                    Regards,
                    William Quintero


                    Edited by: wquinter on Jul 25, 2011 9:02 AM