資料泵匯入時出現ORA-600(klaprs_11)錯誤
今天在使用資料泵匯入的時候碰到了這個ORA-600錯誤。
執行的匯入命令和對應的錯誤資訊如下:
-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], [], [], [], [], [], [], []
錯誤居然發生在一開始的建立匯入工作表SYS_IMPORT_FULL_01處,看來問題比較奇怪。檢查了一下對應的日誌,錯誤資訊和上面的基本一致。
檢查了一下alert檔案,發現了同樣的ORA-600錯誤:
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], [], [], [], [], [], [], []
檢查對應的trace檔案:
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 15:24:32.398
*** MODULE NAME:(Data Pump Worker) 2009-12-26 15:24:32.398
*** SERVICE NAME:(SYS$USERS) 2009-12-26 15:24:32.398
*** SESSION ID:(158.37252) 2009-12-26 15:24:32.398
*** 2009-12-26 15:24: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
L,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL)
----- 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 ?
從trace檔案中看不出什麼有意義的東西,感覺可能是Oracle的bug,於是查詢了一下metalink,結果在文件ID 743483.1中發現了相關的描述。
Oracle認為導致這個錯誤的原因可能是DMP檔案被損壞。這個說明是合理的,否則很難解釋為什麼Oracle在建立匯入工作表的時候都會出現錯誤。而且根據這個錯誤描述,回想到當時執行的一個操作:在匯出操作執行完以後,本打算用gzip壓縮一下,不過壓縮剛開始執行就放棄了這個想法,於是中止了壓縮操作。看來很可能是這個原因導致了錯誤。
嘗試重新匯出DMP檔案,直接ftp到目標站點,再次執行同樣的匯入操作,匯入順利完成,看來果然是由於DMP檔案損壞導致的。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/4227/viewspace-623701/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- impdp 匯入資料導致ora-600,arguments: [klaprs_11]錯誤
- 資料泵匯出碰到ORA-600(kcbz_check_objd_typ_3)錯誤OBJ
- 資料泵轉換模式匯入時出現0ra31655錯誤模式
- 資料泵匯出匯入
- 資料泵的匯入匯出
- 資料泵匯出匯入表
- 資料泵匯出時報錯ORA-1422錯誤
- 資料泵匯出出現ORA-4030錯誤
- Oracle資料泵-schema匯入匯出Oracle
- 資料泵匯出出現ORA-31617錯誤
- 資料泵匯出匯入資料標準文件
- Oracle資料泵的匯入和匯出Oracle
- Oracle資料泵匯出匯入(expdp/impdp)Oracle
- Oracle使用資料泵匯出匯入表Oracle
- 資料泵取匯出和匯入(一)
- 轉oracle資料泵匯出時報錯Oracle
- 資料泵匯出資料包錯處理
- 資料泵匯出出現ORA-31623錯誤
- 資料庫泵(expdp/impdp)匯入匯出流程資料庫
- 12c 資料泵匯入匯出級別
- Impdp資料泵匯入
- Oracle使用資料泵expdp,impdp進行資料匯出匯入Oracle
- shell,ant指令碼實現自動資料泵(exp.expdp)匯出匯入資料指令碼
- SWITCHOVER RAC資料庫出現ORA-600(kcctrdf_2)錯誤資料庫
- Oracle用資料泵匯入資料包12899的錯誤碼解決方法Oracle
- 【ORACLE 匯入匯出】exp 錯誤Oracle
- 使用資料泵impdp匯入資料
- 資料泵匯出匯入物化檢視(ORA-39083)
- oracle10G新特性之資料泵匯出/匯入Oracle
- 【匯入匯出】資料泵 job_name引數的使用
- python實現oracle資料泵匯出功能PythonOracle
- imp匯入資料庫表時浮現ORA-01658錯誤資料庫
- oracle監控資料泵匯入和匯出的sql語句OracleSQL
- 12c pdb的資料泵匯入匯出簡單示例
- Oracle使用資料泵在異機之間匯出匯入表Oracle
- 10g資料泵和匯入匯出效能對比(三)
- 10g資料泵和匯入匯出效能對比(二)
- 10g資料泵和匯入匯出效能對比(一)