DataPump Import (IMPDP) Fails With Internal Error ORA-600 [kupclscb_02] While Importing A Big Table With A LONG RAW Column (Doc ID 1442437.1)

Last updated on NOVEMBER 28, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms

While importing a big table into 11.2.0.x, the import was running for a long time and failed with the following errors logged in impdp log file:

;;;
Import: Release 11.2.0.3.0 - Production on Mon Mar 26 15:31:27 2012

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
;;;
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, Real Application Clusters, Oracle Label Security, OLAP,
Data Mining, Oracle Database Vault and Real Application Testing options
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_01":  system/******** DUMPFILE=<dir_name>:<dumpfile_name>_C%u.dmp,<dir_name>:<dumpfile_name>_D%u.dmp
logfile=<dir>:<logifile_name> full=y parallel=8 CONTENT=DATA_ONLY
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-31693: Table data object "<schema_name>"."<table_name>" failed to load/unload and is being skipped due to error:
ORA-02354: error in exporting/importing data
ORA-00600: internal error code, arguments: [kupclsCB_02], [], [], [], [], [], [], [], [], [], [], []
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1 error(s) at 00:17:52

The underlying trace file shows:

*** MODULE NAME:(Data Pump Worker) 2012-03-26 17:47:44.617
*** ACTION NAME:(SYS_IMPORT_FULL_01) 2012-03-26 17:47:44.617

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

========= Dump for incident 145070 (ORA 600 [kupclsCB_02]) ========
*** 2012-03-26 17:47:44.638
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=4wh7tv915whaq) -----
INSERT INTO RELATIONAL("<schema_name>"."<table_name>" )
("<column_name1>", "<column_name2>", "<column_name3>", "<column_name5>", "<column_name6>", "<column_name7>",
"<column_name8>", "<column_name9>", "<column_name10>", "<column_name4_long_raw>")
VALUES (:1, :2, :3, :4, :5, :6, :7, :8, :9, :10)

Current cursor: 28

Cursor#28(0x2ad92fd82a80) state=BOUND curiob=0x2ad930089a60
curflg=4d fl2=200000 par=(nil) ses=0x22eaebbb8
----- Dump Cursor sql_id=4wh7tv915whaq xsc=0x2ad930089a60 cur=0x2ad92fd82a80 -----
----- Bind Info (kkscoacd) -----

Bind#9
oacdty=23 mxl=4001(2147483647) mxlc=00 mal=00 scl=00 pre=00
oacflg=01 fl2=0000 frm=00 csi=00 siz=4000 off=0
kxsbbbfp=2ad935307bf0 bln=4000 avl=4001 flg=05
value=<very_long_value_here>

In the bind variable section of the cursor dump, you can see that the bind variable causing the error has the oacdty=23 and the avl value (4001) that is greater than bln value (4000). A description of the table "<schema_name>"."<table_name>" shows there is a column of type LONG RAW:

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms