impdp issue ...

[vnktummala]

Hi All,

I have got a strange issue when I am trying to import the prod dumps in sit. In sit impdp is not starting at all ... it is hanging in the below state for hours and not even giving any error message.

Import: Release 10.2.0.3.0 - 64bit Production on Tuesday, 11 August, 2009 17:23:31

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

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

both prod and sit are in same Oracle version, same patch level. export is taken using expdp and i am trying to import using impdp. Can any one shed some light?

Thanks,

[PAVB]

What do you see in v$sessionwait ?

[vnktummala]

Hi PAVB,

I see following event in v$session_wait whose wait_time = 0

wait for unread message on broadcast channel

Thanks,

[vnktummala]

I have also find the below messages in the alert log file.

The value (30) of MAXTRANS parameter ignored.
kupprdp: master process DM00 started with pid=30, OS id=29924
to execute - SYS.KUPM$MCP.MAIN('SYS_IMPORT_SCHEMA_01', 'SYSTEM', 'KUPC$C_1_20090828000000', 'KUPC$S_1_20090828000000
', 0);
kupprdp: worker process DW01 started with worker id=1, pid=31, OS id=29926
to execute - SYS.KUPW$WORKER.MAIN('SYS_IMPORT_SCHEMA_01', 'SYSTEM');
Tue Aug 11 14:51:23 2009
The value (30) of MAXTRANS parameter ignored.
The value (30) of MAXTRANS parameter ignored.
The value (30) of MAXTRANS parameter ignored.

I search in google and fine Metalink document 6347775 has some information.


Thanks,

[vnktummala]

The value (30) of MAXTRANS parameter ignored is expected in 10G because MAXTRANS is obsoleted in 10G.

Still didn't find any information in oracle to trouble shoot this issue.

Thanks,

[vnktummala]

I am tracing impdp with trace=480300. Please see the tail output from the trace file.

KUPM: 17:36:19.914: ...defaulting parameter REUSE_DATAFILES
KUPM: 17:36:19.914: ...defaulting parameter SKIP_UNUSABLE_INDEXES
KUPM: 17:36:19.915: ...defaulting parameter STREAMS_CONFIGURATION
KUPM: 17:36:19.916: ...defaulting parameter TABLE_CONSISTENCY
KUPM: 17:36:19.916: ...defaulting parameter TABLE_EXISTS_ACTION
KUPM: 17:36:19.917: ...defaulting parameter TTS_FULL_CHECK
KUPM: 17:36:19.918: ...defaulting parameter USER_METADATA
KUPM: 17:36:19.933: Starting worker: 1 using SYS.KUPW$WORKER.MAIN('SYS_IMPORT_SCHEMA_02', 'SYSTEM');
KUPM: 17:36:20.017: Worker started.
KUPM: 17:36:20.018: *******OUT DISPATCH , request type=1003 response type =

It is not moving from here. Master and worker sessions are showing active in the DB.

DATE PROGRAM SID STATUS USERNAME
-------------------- ------------------------------ ---------- -------- ---------------
JOB_NAME SPID SERIAL# PID
------------------------------ ------------ ---------- ----------
2009-09-16 00:00:00 udi@test-t5220 (TNS V1-V3) 508 ACTIVE SYSTEM
SYS_IMPORT_SCHEMA_02 6794 2089 29

2009-09-16 00:00:00 oracle@test-t5220 (DM00) 473 ACTIVE SYSTEM
SYS_IMPORT_SCHEMA_02 6796 662 30

2009-09-16 00:00:00 oracle@test-t5220 (DW01) 423 ACTIVE SYSTEM
SYS_IMPORT_SCHEMA_02 6798

I appreciate your comments.

Thanks,