Shulou(Shulou.com)06/01 Report--

What to do when the ORA-600 klaprs_11 error occurs when the data pump is imported? in view of this problem, this article introduces the corresponding analysis and solution in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible method.

I encountered this ORA-600 error while using the data pump import today.

The import command executed and the corresponding error message are as follows:

-bash-3.00$ impdp system/sjsystem15js directory=DMP_DIR dumpfile=jsdemo_091226.dp logfile=jsdemo_091226_imp.log remap_schema=bjsq_demo_ndmain:jssq_demo_ndmain,bjsq_demo_trade:jssq_demo_trade remap_tablespace=bjsq:jssqtbs

Import: Release 10.2.0.3.0-64bit Production on Saturday, 26 December, 2009 15:20:51

Copyright (c) 2003, 2005, Oracle. All rights reserved.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production

With the Partitioning and Data Mining options

ORA-39002: invalid operation

ORA-31694: master table "SYSTEM". "SYS_IMPORT_FULL_01" failed to load/unload

ORA-02354: error in exporting/importing data

ORA-39776: fatal Direct Path API error loading table "SYSTEM". "SYS_IMPORT_FULL_01"

ORA-00600: internal error code, arguments: [klaprs_11], []

It seems strange that the error occurred in the initial establishment of the import worksheet SYS_IMPORT_FULL_01. Check the corresponding log, and the error message is basically the same as the above.

I checked the alert file and found the same ORA-600 error:

Sat Dec 26 15:20:59 2009

Errors in file / data/oracle/admin/jiangsu/bdump/jiangsu_dw01_16742.trc:

ORA-00600: internal error code, arguments: [klaprs_11], []

Check the corresponding trace file:

Bash-3.00$ more / data/oracle/admin/jiangsu/bdump/jiangsu_dw01_16750.trc

/ data/oracle/admin/jiangsu/bdump/jiangsu_dw01_16750.trc

Oracle Database 10g Enterprise Edition Release 10.2.0.3.0-64bit Production

With the Partitioning and Data Mining options

ORACLE_HOME = / data/oracle/product/10.2

System name: SunOS

Node name: jsdb

Release: 5.10

Version: Generic_118833-33

Machine: sun4u

Instance name: jiangsu

Redo thread mounted by this instance: 1

Oracle process number: 21

Unix process pid: 16750, image: oracle@jsdb (DW01)

* ACTION NAME: (SYS_IMPORT_SCHEMA_01) 2009-12-26 15Suzhou 2432.398

* MODULE NAME: (Data Pump Worker) 2009-12-26 15Suzhou 2432.398

* SERVICE NAME: (SYS$USERS) 2009-12-26 15Suzhou 2432.398

* SESSION ID: (158.37252) 2009-12-26 15purl 2432.398

* * 2009-12-26 15 15 24 purl 32.398

Ksedmp: internal or fatal error

ORA-00600: internal error code, arguments: [klaprs_11], []

Current SQL statement for this session:

INSERT / * + SYS_DL_CURSOR * / INTO RELATIONAL ("SYSTEM". "SYS_IMPORT_SCHEMA_01") ("PROCESS_ORDER", "DUPLICATE", "DUMP_FILEID", "DUMP_POSITI"

ON "," DUMP_LENGTH "," DUMP_ALLOCATION "," COMPLETED_ROWS "," ERROR_COUNT "," ELAPSED_TIME "," OBJECT_TYPE_PATH "," OBJECT_PATH_SEQNO "," OBJECT_TYP "

E "," IN_PROGRESS "," OBJECT_NAME "," OBJECT_LONG_NAME "," OBJECT_SCHEMA "," ORIGINAL_OBJECT_SCHEMA "," PARTITION_NAME "," SUBPARTITION_NAME "," FLA "

GS "," PROPERTY "," COMPLETION_TIME "," OBJECT_TABLESPACE "," SIZE_ESTIMATE "," OBJECT_ROW "," PROCESSING_STATE "," PROCESSING_STATUS "," BASE_PROCE "

SS_ORDER "," BASE_OBJECT_TYPE "," BASE_OBJECT_NAME "," BASE_OBJECT_SCHEMA "," ANCESTOR_PROCESS_ORDER "," DOMAIN_PROCESS_ORDER "," PARALLELIZATIO "

N "," UNLOAD_METHOD "," GRANULES "," SCN "," GRANTOR "," NAME "," VALUE_T "," VALUE_N "," IS_DEFAULT "," FILE_TYPE "," USER_DIRECTORY "," USER_FILE_NAME "

"FILE_NAME", "EXTEND_SIZE", "FILE_MAX_SIZE", "PROCESS_NAME", "LAST_UPDATE", "WORK_ITEM", "OBJECT_NUMBER", "COMPLETED_BYTES", "TOTAL_BYTES",

METADATA_IO "," DATA_IO "," CUMULATIVE_TIME "," PACKET_NUMBER "," OLD_VALUE "," SEED "," LAST_FILE "," USER_NAME "," OPERATION "," JOB_MODE "," CONTROL_ "

QUEUE "," STATUS_QUEUE "," REMOTE_LINK "," VERSION "," DB_VERSION "," TIMEZONE "," STATE "," PHASE "," GUID "," START_TIME "," BLOCK_SIZE "," METADATA_BUF "

FER_SIZE "," DATA_BUFFER_SIZE "," DEGREE "," PLATFORM "," ABORT_STEP "," INSTANCE "," XML_CLOB ") VALUES (NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL

, NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,N

ULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NUL

Null paraphrase null parcels null parcels

-PL/SQL Call Stack-

Object line object

Handle number name

3b7490240 54 package body SYS.KUPD$DATA_INT

4ab1bed70 1324 package body SYS.KUPD$DATA

52029c950 10716 package body SYS.KUPW$WORKER

52029c950 3687 package body SYS.KUPW$WORKER

52029c950 6896 package body SYS.KUPW$WORKER

52029c950 1259 package body SYS.KUPW$WORKER

4c3c46730 2 anonymous block

-Call Stack Trace-

Calling call entry argument values in hex

Location type point (? Means dubious value)

Ksedmp () + 744 CALL ksedst () 000000840?

FFFFFFFF7FFEAC7C?

000000000?

FFFFFFFF7FFE7770?

FFFFFFFF7FFE64D8?

FFFFFFFF7FFE6ED8?

Kgerinv () + 200 PTR_CALL 0000000000000000 000105C00? 105F06924?

105F06000? 000105F06?

000105C00? 105F06924?

Kgeasnmierr () + 28 CALL kgerinv () 105F012D8? 000000000?

105C91AE0? 000000000?

FFFFFFFF7FFEB120?

000001430?

Klaprs () + 5260 CALL kgeasnmierr () 105F012D8? 10613D640?

105C91AE0? 000000000?

000105C00? 000105C91?

Kpodpls () + 632 CALL klaprs () 105F00F98?

FFFFFFFF78EB8390?

FFFFFFFF78E35493?

000000002? 000009B6E?

FFFFFFFF78EBB748?

Opiodr () + 1548 PTR_CALL 0000000000000000 000000001? 10512A8D8?

000004200? 00000012C?

000000000?

FFFFFFFF78EB93A8?

Kpoodr () + 444 CALL opiodr () 1051BA480? 000000081?

105F011C0? 000000001?

FFFFFFFF79B266D8?

000105F03?

Upirtrc () + 1164 PTR_CALL 0000000000000000 FFFFFFFF79479598?

000000081?

FFFFFFFF7FFEEED8?

FFFFFFFF7FFF6AE8?

000000000?

FFFFFFFF796B00B0?

I couldn't see anything meaningful from the trace file, so I thought it might be the bug of Oracle, so I queried metalink and found the relevant description in the document ID 743483.1.

Oracle believes that the cause of this error may be that the DMP file is corrupted. This description is reasonable, otherwise it is difficult to explain why Oracle has errors when creating import worksheets. And according to this error description, recall an operation performed at that time: after the export operation was executed, it was intended to be compressed with gzip, but the idea was abandoned as soon as the compression started, so the compression operation was aborted. It seems likely that this reason led to the mistake.

Try to re-export the DMP file, ftp directly to the target site, perform the same import operation again, and the import completes smoothly, which seems to be caused by the corruption of the DMP file.

The answer to the question about what to do when there is an ORA-600 klaprs_11 error in the data pump is shared here. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.