Encountered ORA-00600: internal error code, arguments: [krvxbpns01], [], [], [],

Error is as follows:

SQL> EXEC SYS.DBMS_LOGMNR.START_LOGMNR

(OPTIONS => SYS.dbms_logmnr.dict_from_redo_l
ogs + sys.dbms_logmnr.committed_data_only + sys.dbms_logmnr.ddl_dict_tracking);
BEGIN SYS.DBMS_LOGMNR.START_LOGMNR

(OPTIONS => SYS.dbms_logmnr.dict_from_redo_logs +
sys.dbms_logmnr.committed_data_only + sys.dbms_logmnr.ddl_dict_tracking); END;

*
Error line 1:
ORA-01291: missing log file
ORA-06512: at "SYS.DBMS_LOGMNR", line 58
ORA-06512: at line 1

SQL> select filename from v $ logmnr_logs;

FILENAME
-------------------------------------------------- --------------------------

----

C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00227_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00228_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00229_0699741520.001
Missing log file (s) for thread 1, sequence (s) 230 to 252
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ REDO02.RDO
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ REDO03.RDO

Have chosen 6 rows.

SQL> begin
2 for x in (select * from v $ archived_log where sequence # between 230 and 250) loop
3 sys.dbms_logmnr.add_logfile (logfilename => x.name, options => sys.dbms_logmnr.a
ddfile);
4 end loop;
5 end;
6 /

PL / SQL procedure successfully completed.

SQL> select filename from v $ logmnr_logs;

FILENAME
-------------------------------------------------- --------------------------

----

C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00227_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00228_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00229_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00230_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00231_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00232_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00233_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00234_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00235_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00236_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00237_0699741520.001

FILENAME
-------------------------------------------------- --------------------------

----

C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00238_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00239_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00240_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00241_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00242_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00243_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00244_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00245_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00246_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00247_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00248_0699741520.001

FILENAME
-------------------------------------------------- --------------------------

----

C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00249_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00250_0699741520.001
Missing log file (s) for thread 1, sequence (s) 251 to 252
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ REDO02.RDO
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ REDO03.RDO

Has selected 27 rows.

SQL> begin
2 for x in (select * from v $ archived_log where sequence # between 251 and

252
) Loop
3 sys.dbms_logmnr.add_logfile

(logfilename => x.name, options => sys.dbms_logmnr.a
ddfile);
4 end loop;
5 end;
6 /

PL / SQL procedure successfully completed.

SQL> select filename from v $ logmnr_logs;

FILENAME
-------------------------------------------------- --------------------------

----

C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00227_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00228_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00229_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00230_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00231_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00232_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00233_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00234_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00235_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00236_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00237_0699741520.001

FILENAME
-------------------------------------------------- --------------------------

----

C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00238_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00239_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00240_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00241_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00242_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00243_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00244_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00245_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00246_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00247_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00248_0699741520.001

FILENAME
-------------------------------------------------- --------------------------

----

C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00249_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00250_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00251_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ ARCHIVE \ ARC00252_0699741520.001
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ REDO02.RDO
C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ YSPENG \ REDO03.RDO

Has selected 28 rows.

SQL> exec sys.dbms_logmnr.start_logmnr

(options => sys.dbms_logmnr.dict_from_redo_logs + sys.dbms_logmnr.committed_data_only + sys.dbms_logmnr.ddl_dict_tracking);

PL / SQL procedure successfully completed.

SQL> insert into tomshan select * from v $ logmnr_contents where

seg_name = 'MYTEST'
;
insert into tomshan select * from v $ logmnr_contents where seg_name = 'MYTEST'
*
Error line 1:
ORA-00600: internal error code, arguments: [krvxbpns01], [], [], [], [], [], [], []

google look, found a BUG which is Oracle 10G

metalink described as follows:
Logminer ad-hoc can hang or fail with an ORA-600 when mining logs
from a RAC database that has thread enable and disables or if there are
missing sequences from the log list.

Preliminary judging is due to discontinuity caused by the log.

By querying v $ logmnr_logs can see my list of log files inside two online log files redo02.rdo redo03.rdo these two log files corresponding to the serial number of 253 and 254, respectively. Problem is that in these two log files, because I want to save trouble, followed by two did not use the corresponding archive file, while the direct use of the online journals. START_LOGMNR the time no problem. However, when the INSERT was a problem. As the INSERT will generate REDO data, and my set REDO file is relatively small, resulting in the log file switch several times, so now's REDO02.RDO and REDO03.RDO the corresponding serial number should not be 253 and 254, and after I Check the log file is now two serial numbers are as follows: 256 and 257

SQL> SELECT GROUP #, SEQUENCE #, STATUS FROM V $ LOG;

GROUP # SEQUENCE # STATUS
---------- ---------- ----------------
1 255 INACTIVE
2 256 ACTIVE
3 257 CURRENT

We know that v $ LOGMNR_CONTENTS table only if we are in the request (SELECT) will fill the time, LogMiner will analyze the log list, and will meet the needs of the results returned to us. Each request for a v $ LOGMNR_CONTENTS, LogMiner will analyze one. Therefore, when we insert into tomshan select * from v $ logmnr_contents time, LogMiner will be in accordance with the serial number of the log file sequence analysis of each log file, and the results inserted into tomshan in this table. In the process of inserting the table will generate a lot of REDO data, and log switch occurs, and thus the present redo02.rdo, redo03.rdo inside the data has already been covered. And now the LogMiner logs in the list of redo02.rdo, redo03.rdo the corresponding serial number 256,257, which appears the log file breakpoints.

Know the cause of the problem, the problem is like solved.

Remove the log list, the log for the redo02.rdo, redo03.rdo files:

SQL> EXEC SYS.DBMS_LOGMNR.REMOVE_LOGFILE (LogFileName => 'C: \ ORACLE \ PRODUCT \ 10.2.0 \
ORADATA \ YSPENG \ REDO02.RDO ');

PL / SQL procedure successfully completed.

SQL> EXEC SYS.DBMS_LOGMNR.REMOVE_LOGFILE (LogFileName => 'C: \ ORACLE \ PRODUCT \ 10.2.0 \
ORADATA \ YSPENG \ REDO03.RDO ');

PL / SQL procedure successfully completed.

Re-add the log sequence number for the 253 and 254 of the archive file:

SQL> EXEC SYS.DBMS_LOGMNR.ADD_LOGFILE (LogFileName => 'C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORA
DATA \ YSPENG \ ARCHIVE \ ARC00253_0699741520.001 ', OPTIONS => SYS.DBMS_LOGMNR.ADDFILE);

PL / SQL procedure successfully completed.

SQL> EXEC SYS.DBMS_LOGMNR.ADD_LOGFILE (LogFileName => 'C: \ ORACLE \ PRODUCT \ 10.2.0 \ ORA
DATA \ YSPENG \ ARCHIVE \ ARC00254_0699741520.001 ', OPTIONS => SYS.DBMS_LOGMNR.ADDFILE);

PL / SQL procedure successfully completed.

Start Log Analysis:

SQL> EXEC SYS.DBMS_LOGMNR.START_LOGMNR (OPTIONS => SYS.DBMS_LOGMNR.DICT_FROM_REDO_L
OGS + SYS.DBMS_LOGMNR.COMMITTED_DATA_ONLY + SYS.DBMS_LOGMNR.DDL_DICT_TRACKING);

PL / SQL procedure successfully completed.

SQL> INSERT INTO TOMSHAN SELECT * FROM V $ LOGMNR_CONTENTS WHERE SEG_NAME = 'MYTEST';

PL / SQL procedure successfully completed.
  • del.icio.us
  • StumbleUpon
  • Digg
  • TwitThis
  • Mixx
  • Technorati
  • Facebook
  • NewsVine
  • Reddit
  • Google
  • LinkedIn
  • YahooMyWeb

Related Posts of Encountered ORA-00600: internal error code, arguments: [krvxbpns01], [], [], [],

  • ORACLE10G full version centos5 installed (the installation has passed)

    ORACLE10G full version centos5 installed (the installation has passed) 1. Centos 5.0 install rn GUI must be installed, it is best not to start selinux rn rn rn 2. . Ready to install the software: (this is very important, is the first installation fai ...

  • SGA extended the principle of 32bit oracle

    SGA extended the principle of 32bit oracle From: http://www.itpub.net/247048.html Because the median 32bitrnoracle restrictions can only visit the oracle process 4g (2 of 32 power) following virtual memory address, the time at a lot of people this is ...

  • AX3.0 + Oracle 10G RAC installation

    During these two days, you installed RAC, in a virtual machine inside, with a full day, there have been some questions on his way. Now have their own solution. In fact, it is loaded, it is easy, as long as planned, carefully point on OK, the trouble ...

  • Oracle in the relationship between User and Schema

    If we want to know the database and the User What is the relationship between Schema, we must first know about User and Schema database What is the concept in the end. In SQL Server2000 in architecture because of the reason, User and Schema there is ...

  • High Availability Oracle Flashback

    Brief introduction Flashback Database is a point in time (PIT) restore the database approach. This incomplete recovery strategy can be used to restore the logic because of human error cause damage to the database. At the introduction of 10g, it is de ...

  • An example of the use of TKPROF

    First, view and edit parameters SQL> show parameter max_dump_file_size NAME TYPE VALUE ------------------------------------ ----------- --- --------------------------- max_dump_file_size string UNLIMITED SQL> show parameter user_dump_dest NAME TYPE

  • Diagnosis and principles of order

    SQL> select disk.value "Disk", mem.value "Mem", 2 (disk.value / mem.value) * 100 "Ratio" 3 from v $ sysstat mem, v $ sysstat disk 4 where mem.name = 'sorts (memory)' 5 and disk.name = 'sorts (disk)'; D ...

  • ORACLE 10G dataguard configuration Step by Step

    oracle dataguard

Leave a Reply

Recent
Recent Entries
Tag Cloud
Random Entries
Latest Comments