Home » RDBMS Server » Server Utilities » Unable to import ( impdp ) (oracle 11.2.0.2.0 linux 2.6)
Unable to import ( impdp ) [message #575305] Tue, 22 January 2013 02:32 Go to next message
kesavansundaram
Messages: 183
Registered: October 2007
Location: MUMBAI
Senior Member
Team,
I need to import one schema into 3 different DBS. out of 3, have imported into 2 databases without any error. during 3rd import iam getting below error:

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, OLAP
and Data Mining options
ORA-31626: job does not exist
ORA-31637: cannot create job SYS_IMPORT_FULL_01 for user SYSTEM
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPV$FT_INT", line 798
ORA-39244: Event to disable dropping null bit image header during relational select
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.KUPC$QUE_INT", line 1825
ORA-01403: no data found


Could you please advise me on this error ? I am using same parfile. no changes on the syntax.
this is a schema export.

---partfile content

> more QSHOUT_ALARMPOINT4_import.par
directory=APP_EXPORT
dumpfile=exp_PSHOUT_01182013_ALARMPOINT4_SCHEMA.dmp
logfile=exp_PSHOUT_01182013_ALARMPOINT4_SCHEMA_impQSHOUT.log
TABLE_EXISTS_ACTION=truncate
parallel=2
cluster=n
full=y


Thank you
kesavan
Re: Unable to import ( impdp ) [message #575307 is a reply to message #575305] Tue, 22 January 2013 02:39 Go to previous messageGo to next message
Michel Cadot
Messages: 68625
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-39244: Event to disable dropping null bit image header during relational select
 *Document: NO
 *Cause:    N/A
 *Action:   Do not strip off null bit image header on relational select
            during a Data Pump external table export.

Re: Unable to import ( impdp ) [message #575308 is a reply to message #575307] Tue, 22 January 2013 02:45 Go to previous messageGo to next message
Michel Cadot
Messages: 68625
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
Searching on the web, it seems this error comes from the fact that a target tablespace is full and files are not in autoextend mode.

Regards
Michel
Re: Unable to import ( impdp ) [message #575310 is a reply to message #575307] Tue, 22 January 2013 02:46 Go to previous messageGo to next message
kesavansundaram
Messages: 183
Registered: October 2007
Location: MUMBAI
Senior Member
Hi Michel,

Thanks for your prompt reply. Could you please tell in some other words ? you mean, export is to be taken properly ? i have pasted the export log. do we need to take export in different manner to suppress this error duing import ? if so, guide me to take export accordingy so that I can advise my Prod DBA to generate export dump file again.

export log



[Edit MC: wrap export log in spoiler to ease topic reading]

[Updated on: Tue, 22 January 2013 04:14] by Moderator

Report message to a moderator

Re: Unable to import ( impdp ) [message #575311 is a reply to message #575308] Tue, 22 January 2013 02:48 Go to previous messageGo to next message
kesavansundaram
Messages: 183
Registered: October 2007
Location: MUMBAI
Senior Member
oops, checking tablespace now.
Re: Unable to import ( impdp ) [message #575312 is a reply to message #575311] Tue, 22 January 2013 03:04 Go to previous messageGo to next message
kesavansundaram
Messages: 183
Registered: October 2007
Location: MUMBAI
Senior Member
Michel,
Tablepace looks fine. i already given unlimited quota as well.

USERNAME                       ACCOUNT_STATUS                   DEFAULT_TABLESPACE             TEMPORARY_TABLESPACE
------------------------------ -------------------------------- ------------------------------ ------------------------------
ALARMPOINT4                    OPEN                             ALARMPOINT4                    TEMP




--we have 44 gb free as of now

TABLESPACE                    TOTAL       USED       FREE   PCT_FREE    LARGEST  FRAGMENTS
------------------------ ---------- ---------- ---------- ---------- ---------- ----------
ALARMPOINT4                   43008         .7    43007.3 99.9983724      31248          3



in export dump also, tablespace name is same only ( ALARMPOINT4 ). further i am also checking and update you.

Thank you
Re: Unable to import ( impdp ) [message #575313 is a reply to message #575312] Tue, 22 January 2013 03:05 Go to previous message
kesavansundaram
Messages: 183
Registered: October 2007
Location: MUMBAI
Senior Member
just adding.


datafile#7 should be fine for further usage for which AUTOEXTEND enabled.
TABLESPACE_NAME       FILE_ID FILE_NAME                                                            Allocated Size(MB) AUT MAX UPTO(MB)
------------------ ---------- -------------------------------------------------------------------- ------------------ --- ------------
ALARMPOINT4                 6 +SHOUT_T1_DATA_01/qshout/datafile/alarmpoint4.dbf                            32767.9844 YES   32767.9844
ALARMPOINT4                 7 +SHOUT_T1_DATA_01/qshout/datafile/alarmpoint4.285.759859437                       10240 YES   32767.9844
Previous Topic: EXP-00008: ORACLE error 6552 encountered
Next Topic: error ORA-04063: package body "SYS.DBMS_INTERNAL_LOGSTDBY" has errors
Goto Forum:
  


Current Time: Thu Mar 28 15:46:45 CDT 2024