ORA-7445: exception encountered: core dump [kpodpals()+11332] [SIGSEGV]

renjixinchina發表於2013-04-11
ExceptionGse

ORA-7445 [kpodpals] During DataPump Import [ID 1096837.1]

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.1 - Release: 10.2 to 11.2
Information in this document applies to any platform.

Symptoms

You perform. a DataPump import and this breaks with errors:

#> impdp system/password directory=dpu dumpfile=a_table.dmp table_exists_action=replace

Import: Release 10.2.0.1.0 - Production on Wednesday, 21 April, 2010 9:21:43
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** directory=dpu 
dumpfile=a_table.dmp table_exists_action=replace
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-39014: One or more workers have prematurely exited.
ORA-39029: worker 1 with process name "DW01" prematurely terminated
ORA-31672: Worker process DW01 died unexpectedly.
Job "SYSTEM"."SYS_IMPORT_FULL_01" stopped due to fatal error at 09:23:32

The file alert.log contains:

- On Windows platforms
ORA-7445: exception encountered: core dump [ACCESS_VIOLATION]
[__VInfreq__kpodpmop+7524] [PC:0x3121BE8] [ADDR:0x0] [UNABLE_TO_READ] []

- On Unix/Linux
ORA-7445: exception encountered: core dump [kpodpals()+11332] [SIGSEGV]
[Address not mapped to object] [0x000000000] [] []

DataPump import (impdp) in version 11gR2 ends with:

Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Job "SYSTEM"."SYS_IMPORT_FULL_01" stopped due to fatal error at 09:29:24

(no ORA-39014 ORA-39029 ORA-31672), The alert.log contains:

ORA-7445: exception encountered: core dump [kpodpals()+3959] [SIGSEGV] 
[ADDR:0x0] [PC:0xC2B8C25] [Address not mapped to object] []

Cause

This is produced by . A no-name column "" is included in table definition. The imported table is defined as:

create table a_table 
(
    id    number, 
    " "   varchar2(10), -- " " means ""
    text  varchar2(10)
);

Solution

1. Don't use columns like "" in source database

Or:

2 If a table has such columns, then exclude the table during import with:

exclude=table:\"IN ('A_TABLE')\"

Or:

3. Use original export/import utilities (exp/imp)

Note: Columns including spaces in name, like "COL  1" don't raise any errors. 

來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/15747463/viewspace-758304/，如需轉載，請註明出處，否則將追究法律責任。

相關文章