Constraints in IMPDP
Hi Everyone,
I have an expdp dump from 10 g and I am importing that to 11g r 2 DB. After the import I have checked the number of constraints for the imported schema It seems like it has imported 5 to 6 less constraints from the original in 10g r2. My import is successful apart from compilation errors for the procedures. And firget to mention that I am excluding grants and statistics. I am not to figure out why its showing less has the source. Please give me some advice on this issue.
Thanks for your time in advance.
You know OS name & version.
You knows Oracle version to 4 decimal places.
You have tables.
You have data.
You know both expdp & impdp command lines.
You know actual details what exists & what is missing.
You can not discern what is wrong.
We know you post complaint about some problem.
Please give me some advice on this issue. My advice is that you need to tell us how we can reproduce your problem what ever it may be.
Similar Messages
-
Hi everybody
I can't understand why my data pump import execution with parameter TABLE_EXISTS_ACTION=TRUNCATE returned ORA-00001 (unique constraint violation), while importing schema tables from a remote database where the source tables have the same unique constraints as the corresponding ones on the target database.
Now my question is "If the table would be truncated, why I get unique constraint violation when inserting records from a table where the same unique constraint is validated?
Here are the used parameter file content and the impdp logfile.
parfile
{code}
DIRECTORY=IMPEXP_LOG_COLL2
CONTENT=DATA_ONLY
NETWORK_LINK=PRODUCTION
PARALLEL=1
TABLE_EXISTS_ACTION=TRUNCATE
EXCLUDE=STATISTICS
{code}
logfile
{code}
Import: Release 10.2.0.1.0 - Production on Gioved� 22 Ottobre, 2009 15:33:44
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connesso a: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
FLASHBACK automatically enabled to preserve database integrity.
Starting "IMPEXP"."PROVA_REFRESH_DBCOLL": impexp/********@dbcoll SCHEMAS=test_pump LOGFILE=test_pump.log parfile=refresh_dbcoll.par JOB_NAME=prova_refresh_dbcoll
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 523 MB
ORA-31693: Table data object "TEST_PUMP"."X10000000_TRIGGER" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (TEST_PUMP.SYS_C00726627) violated
ORA-31693: Table data object "TEST_PUMP"."X10000000_BASIC" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (TEST_PUMP.SYS_C00726625) violated
Job "IMPEXP"."PROVA_REFRESH_DBCOLL" completed with 2 error(s) at 15:34:04
{code}
Thank you
Bye AlessandroI forgot to read the last two lines of the documentation about TABLE_EXISTS_ACTION where it says:
"TRUNCATE cannot be used on clustered tables or over network links."
So it seems that it ignored the clause for the use of NETWORK_LINK and unreasonably opted for an APPEND action instead of throwing an error to highlight the conflicting parameters in the used configuration.
Bye Alessandro -
Expdp/impdp :: Constraints in Parent child relationship
Hi ,
I have one table parent1 and tables child1, child2 and chld3 have foreign key created on this parent1.
Now I want to do some deletion on parent1. But since number of records are very high on parent1 , we are going with expdp / impdp with querry option.
I have taken query level expdp on parent1. Now I dropped parent1 with cascade constraints option and all the foreign keys created by child1 ,2 and 3 which references parent1 are automatically dropped.
Now If i fire the impdp for the query level dump file , will these foreign key constraints will get created automatically on child1 ,2 and 3 or I need to manually re-create it ??
Regards,
AnuHi,
The FK's will not be in the dumpfile - see the example code below where i generate a sqlfile following pretty much the process you would have done. THis is because the FK is part of the DDL for the child table not the parent.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning option
OPS$ORACLE@EMZA3>create table a (col1 number);
Table created.
OPS$ORACLE@EMZA3>alter table a add primary key (col1);
Table altered.
OPS$ORACLE@EMZA3>create table b (col1 number);
Table created.
OPS$ORACLE@EMZA3>alter table b add constraint x foreign key (col1) references a(col1);
Table altered.
OPS$ORACLE@EMZA3>
EMZA3:[/oracle/11.2.0.1.2.DB/bin]# expdp / include=TABLE:\"=\'A\'\"
Export: Release 11.2.0.3.0 - Production on Fri May 17 15:45:50 2013
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 option
Starting "OPS$ORACLE"."SYS_EXPORT_SCHEMA_04": /******** include=TABLE:"='A'"
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 0 KB
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
. . exported "OPS$ORACLE"."A" 0 KB 0 rows
Master table "OPS$ORACLE"."SYS_EXPORT_SCHEMA_04" successfully loaded/unloaded
Dump file set for OPS$ORACLE.SYS_EXPORT_SCHEMA_04 is:
/oracle/11.2.0.3.0.DB/rdbms/log/expdat.dmp
Job "OPS$ORACLE"."SYS_EXPORT_SCHEMA_04" successfully completed at 15:45:58
Import: Release 11.2.0.3.0 - Production on Fri May 17 15:46:16 2013
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 option
Master table "OPS$ORACLE"."SYS_SQL_FILE_FULL_01" successfully loaded/unloaded
Starting "OPS$ORACLE"."SYS_SQL_FILE_FULL_01": /******** sqlfile=a.sql
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Job "OPS$ORACLE"."SYS_SQL_FILE_FULL_01" successfully completed at 15:46:17
-- CONNECT OPS$ORACLE
ALTER SESSION SET EVENTS '10150 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10904 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '25475 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10407 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10851 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '22830 TRACE NAME CONTEXT FOREVER, LEVEL 192 ';
-- new object type path: SCHEMA_EXPORT/TABLE/TABLE
CREATE TABLE "OPS$ORACLE"."A"
( "COL1" NUMBER
) SEGMENT CREATION IMMEDIATE
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
NOCOMPRESS LOGGING
STORAGE(INITIAL 16384 NEXT 16384 MINEXTENTS 1 MAXEXTENTS 505
PCTINCREASE 50 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "SYSTEM" ;
-- new object type path: SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ALTER TABLE "OPS$ORACLE"."A" ADD PRIMARY KEY ("COL1")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 16384 NEXT 16384 MINEXTENTS 1 MAXEXTENTS 505
PCTINCREASE 50 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "SYSTEM" ENABLE;
-- new object type path: SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
DECLARE I_N VARCHAR2(60);
I_O VARCHAR2(60);
NV VARCHAR2(1);
c DBMS_METADATA.T_VAR_COLL;
df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS';
stmt varchar2(300) := ' INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,d1,cl1) VALUES (''I'',6,:1,:2,:3,:4,:5,:6,:7,:8,:9,:10,:11,:12,:13,NULL,:14,:15,NULL,:16,:17)';
BEGIN
DELETE FROM "SYS"."IMPDP_STATS";
c(1) := 'COL1';
DBMS_METADATA.GET_STAT_INDNAME('OPS$ORACLE','A',c,1,i_o,i_n);
EXECUTE IMMEDIATE stmt USING 0,I_N,NV,NV,I_O,0,0,0,0,0,0,0,0,NV,NV,TO_DATE('2013-05-17 15:43:24',df),NV;
DBMS_STATS.IMPORT_INDEX_STATS('"' || i_o || '"','"' || i_n || '"',NULL,'"IMPDP_STATS"',NULL,'"SYS"');
DELETE FROM "SYS"."IMPDP_STATS";
END;
/Regards,
Harry
http://dbaharrison.blogspot.com/ -
Hello all,
I'm running impdp for a DATA_ONLY import to a single schema.
I have set:
EXCLUDE=REF_CONSTRAINT
EXCLUDE=CONSTRAINT
SCHEMAS=SCHEMA1
CONTENT=DATA_ONLY
In my par file.
However, when importing I still get several errors such as:
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE_DATA
ORA-31693: Table data object "SCHEMA1"."STD_TABLE1" failed to load/unload and is being skipped due to error:
ORA-02091: transaction rolled back
ORA-02291: integrity constraint (SCHEMA1.FKSTD_CONSTRAINT_NAME1) violated - parent key not found
. . imported "SCHEMA1"."STD_TABLE2" 3.672 MB 35023 rows
ORA-31693: Table data object "SCHEMA1"."STD_TABLE3" failed to load/unload and is being skipped due to
error:
ORA-02091: transaction rolled back
ORA-02291: integrity constraint (SCHEMA1.FKSTD_CONSTRAINT_NAME2) violated - parent key not found
These are foreign keys, any suggestions on what to look for as to why these constraints aren't being overlooked so the tables can be loaded?
Is there something else I need to exclude in order to get these tables loaded?
Thanks in advance,
cayenneHi Cayenne,
Try this:
1) Disable constraints:
SELECT 'alter table LS_SRV.'||table_name||' disable constraint '||constraint_name||';' FROM dba_constraints where R_CONSTRAINT_NAME IN ('FKSTD_CONSTRAINT_NAME1','FKSTD_CONSTRAINT_NAME2');
2) Import it again
3) Enable again (with novalidate option if you don't want to check the data concisntency of the inserted data):
SELECT 'alter table LS_SRV.'||table_name||' disable constraint '||constraint_name||';' FROM dba_constraints where R_CONSTRAINT_NAME IN ('FKSTD_CONSTRAINT_NAME1','FKSTD_CONSTRAINT_NAME2');
or NOVALIDATE
SELECT 'alter table LS_SRV.'||table_name||' enable novalidate constraint '||constraint_name||';' FROM dba_constraints where R_CONSTRAINT_NAME IN ('FKSTD_CONSTRAINT_NAME1','FKSTD_CONSTRAINT_NAME2');
Hope it helps
Regards,
Rodrigo -
Impdp extremely slow during CONSTRAINTS
We have a Oracle RAC instance 10.2.0.4 on Linux systems(two node). we are getting the expdp dump from client and while trying to import it is taking 26 hours for just 40gb files.
In impdp - Processing object type DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/CONSTRAINT----- this step is running for more than 15 hrs.
We tried expdp/impdp from prod to non prod databases and that takes 6-7 hrs.(DB size is same arnd 40gb)
we also tried regular export and import and this takes 24 hrs.
we do not see any errors, one this different here is client system where we get the export dump is on solaris and on 10.2.0.3 ...while we are on 10.2.0.4 linux system.
please let me know if anyone has faced such issue.
Thanks!Trace the impdp session to see what actually happens:
Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pump
Doc ID: 286496.1
Werner -
IMPDP constraints extremely slow
Hello,
We are getting data from 11.1.x solaris platform and running impdp into 11.2.x on Linux DB. Using PARALLEL=9 on a 16 cpu machine.
However notice that impdp only constraints is running for 12-15 hours. DB size is approx 120 gb.
there are no errors in impdp log or alert log. please advise....
Thanks!Pl see MOS Doc 453895.1 (Checklist for Slow Performance of Export Data Pump (expdp) and Import DataPump (impdp))
Enable trace as per MOS Doc 286496.1 (Export/Import DataPump Parameter TRACE - How to Diagnose Oracle Data Pump) to see if additional details can be gathered. Have you opened an SR with Support ?
HTH
Srini -
After IMPDP in new schema all pl/sql in UPPERCASE.
Hi,
I am using ORACLE 11g R2 DB and IBM AIX OS.
I have faced a very different situation. I had last night's backup dump file of the user, in the morning we had some issue so we need to restore that dump in the current user. So i dropped the user first and then created it. Gave all the respective privileges and started the IMPDP process in which i passed the same dump file from last night's backup. This dump file belonged to the same user. So , the dump is of the same user in which it is getting imported.
But to my surprise all the pl/sql blocks(procedures,functions,packages) all have been imported in UPPERCASE. Even the comments and the single quotes values by which we can do the data matching, all are turned into UPPERCASE. So we are facing a lot issue with it as data is not getting matched as per the procedure.
The user is passing the value as 'app server' and in the procedure the value is as "SELECT.......WHERE SERVER_NAME='APP SERVER' " . so the data is not matched and it returns no output. This is a case in many procedures and we found this only after we imported this dump file.
The IMPDP command is as follows:-
impdp \'sys as sysdba\' directory=remote dumpfile=dblink_ngpmt_mt_mt01_19-03-2012-13-10-20.dmp logfile=dblink_ngpmt_mt_mt01_19-03-2012-13-10-20.log remap_schema=MT01:mt01The log file is as below :-
Import: Release 11.2.0.2.0 - Production on Tue Mar 20 17:22:26 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, Oracle Label Security, OLAP, Data Mining,
Oracle Database Vault and Real Application Testing options
Master table "SYS"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYS"."SYS_IMPORT_FULL_01": "sys/******** AS SYSDBA" directory=remote dumpfile=dblink_ngpmt_mt_mt01_19-03-2012-13-10-20.dmp logfile=dblink_ngpmt_mt_mt01_19-03-2012-13-10-20.log remap_schema=MT01:mt01
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"MT01" already exists
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/TABLESPACE_QUOTA
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SYNONYM/SYNONYM
Processing object type SCHEMA_EXPORT/TYPE/TYPE_SPEC
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
. . imported "MT01"."FLX_CS_AUDIT_ITEM" 53.19 MB 5369 rows
. . imported "MT01"."FLX_CS_AUDIT_ITEM_LOG" 26.93 MB 197599 rows
. . imported "MT01"."FLX_RL_RULE_CODES" 13.16 MB 228 rows
. . imported "MT01"."XF_OL_ST_EXT_TXN_XREF" 6.913 MB 89083 rows
. . imported "MT01"."FLX_RL_EVALUATION_DTLS" 5.920 MB 51309 rows
. . imported "MT01"."FLX_SM_AUTH_REASON_CONFIG" 4.284 MB 29584 rows
. . imported "MT01"."FLX_RL_RULE_DRAFTS_B" 3.744 MB 228 rows
. . imported "MT01"."FLX_MD_SERVICE_ATTR_SRC" 888.0 KB 3807 rows
. . imported "MT01"."FLX_MD_FIELDS_DEFN" 3.517 MB 15758 rows
. . imported "MT01"."FLX_MD_SERVICE_ATTR" 658.7 KB 2173 rows
. . imported "MT01"."FLX_SM_SERVICE_INPUTS_B" 3.794 MB 26859 rows
. . imported "MT01"."FLX_PM_PRODUCT_FLOW" 376.6 KB 16 rows
. . imported "MT01"."FLX_RL_EXPRESSION_CODES" 1.825 MB 164 rows
. . imported "MT01"."FLX_PC_FIN_INST_B" 2.752 MB 14065 rows
. . imported "MT01"."FLX_MD_KEY_FIELDS" 2.400 MB 13367 rows
. . imported "MT01"."FLX_MD_SERVICE_INPUTS" 2.040 MB 13645 rows
. . imported "MT01"."FLX_MD_UI_TEXT_LABEL" 2.405 MB 6994 rows
. . imported "MT01"."FLX_ME_BUS_FUNC_QUERY_ID" 1.740 MB 7973 rows
. . imported "MT01"."FLX_EP_ACT_LOG_B" 1.456 MB 110 rows
. . imported "MT01"."FCR_TXN_SERVICE" 1.122 MB 8743 rows
. . imported "MT01"."FLX_PM_ACCT_ENTRY_TMPLT" 851.4 KB 5543 rows
. . imported "MT01"."FLX_SM_AUTHORIZATIONS_B" 862.7 KB 5654 rows
. . imported "MT01"."FLX_SM_SERVICES_DEFN" 1003. KB 5753 rows
. . imported "MT01"."FLX_PR_PLAN_LOG_B" 733.1 KB 45 rows
. . imported "MT01"."FLX_WL_WORKITEM" 637.9 KB 26 rows
. . imported "MT01"."FLX_FA_FACTS_B" 556.9 KB 2129 rows
. . imported "MT01"."FLX_ME_BUSINESS_OBJECT_B" 558.7 KB 4877 rows
. . imported "MT01"."FLX_WL_DRAFT_ITEM" 296.1 KB 41 rows
. . imported "MT01"."FLX_RL_RULE_EXPRESSIONS" 462.4 KB 7661 rows
. . imported "MT01"."FLX_RL_RULE_OUTCOMES" 478.0 KB 3425 rows
. . imported "MT01"."FLX_EP_ACT_GEN_ATTR_B" 379.5 KB 1939 rows
. . imported "MT01"."FLX_MD_DATA_DEFN" 385.8 KB 1714 rows
. . imported "MT01"."FLX_PC_FIN_INST_CONST_B" 391.6 KB 14066 rows
. . imported "MT01"."FLX_FA_VALUE_DATASOURCES" 323.2 KB 1612 rows
. . imported "MT01"."FLX_LN_ACCT_CONFIG_DTLS_S" 47.44 KB 3 rows
. . imported "MT01"."FLX_PC_FIN_IDENTIFICATION_B" 336.2 KB 14065 rows
. . imported "MT01"."FLX_SM_SERVICE_INP_AUTH_B" 18.01 KB 34 rows
. . imported "MT01"."FLX_EP_ACN_LOG_B" 144.8 KB 42 rows
. . imported "MT01"."FLX_EP_MSG_TMPL_B" 202.0 KB 403 rows
. . imported "MT01"."FLX_RL_RULE_CONDITIONS" 260.4 KB 2118 rows
. . imported "MT01"."FLX_EP_MSG_SRC_B" 203.7 KB 741 rows
. . imported "MT01"."FLX_PI_IND_CLASS" 228.8 KB 4206 rows
. . imported "MT01"."FLX_PI_KYC_VER_DTL_B" 12.88 KB 6 rows
. . imported "MT01"."FLX_PM_PRODUCT_GROUP_FLOW" 31.71 KB 4 rows
. . imported "MT01"."FLX_PR_RCHART_EVAL_TIERS" 248.1 KB 1287 rows
. . imported "MT01"."FLX_SM_UNAPPR_TXN_B" 86.62 KB 2 rows
. . imported "MT01"."FLX_TD_TRANSACTION_STATE" 11.90 KB 3 rows
. . imported "MT01"."FLX_CS_AUDIT_SEARCH_CONTEXT" 121.2 KB 44 rows
. . imported "MT01"."FLX_FA_AGGREGATE_LINKS" 176.7 KB 1804 rows
. . imported "MT01"."FLX_FA_GROUP_XREF" 151.8 KB 2102 rows
. . imported "MT01"."FLX_FA_VALUE_BINDINGS" 201.0 KB 1947 rows
. . imported "MT01"."FLX_IN_LN_SIM_LOG_ITEM" 176.1 KB 684 rows
. . imported "MT01"."FLX_OR_FTT_PM_CODES_XREF" 141.5 KB 11210 rows
. . imported "MT01"."FLX_PM_DOMAIN_CAT_FLOW" 26.80 KB 5 rows
. . imported "MT01"."FLX_PM_PRODUCT_ACCTROLE" 165.1 KB 1238 rows
. . imported "MT01"."FLX_PR_CONSOL_OFF_MAP_B" 177.4 KB 1409 rows
. . imported "MT01"."FLX_RL_RULE_EXECUTION_H" 154.8 KB 1448 rows
. . imported "MT01"."FLX_RL_RULE_EXP_FACT_XRF" 186.0 KB 2313 rows
. . imported "MT01"."FLX_RL_RULE_GEN_OUTCOMES" 196.4 KB 3425 rows
. . imported "MT01"."FLX_RL_RULE_STATEMENTS" 154.0 KB 1473 rows
. . imported "MT01"."FLX_RL_TEMPLATES_ALL_B" 110.0 KB 8 rows
. . imported "MT01"."FLX_ACCOUNT_TXN_AUDIT_ITEM" 101.9 KB 37 rows
. . imported "MT01"."FLX_EP_MSG_ATTR_B" 114.1 KB 2035 rows
. . imported "MT01"."FLX_LN_ACCT_PREF_CONFIG_T" 19.15 KB 6 rows
. . imported "MT01"."FLX_PR_INDEXES_B" 138.7 KB 659 rows
. . imported "MT01"."FLX_PR_INTEREST_OUTCOMES" 107.4 KB 1694 rows
. . imported "MT01"."FLX_PR_OFFER_SET_B" 136.0 KB 1321 rows
. . imported "MT01"."FLX_PR_OFF_ELM_SET_B" 132.4 KB 1357 rows
. . imported "MT01"."FLX_PR_RCHART_TIER_LKUPS" 146.6 KB 2378 rows
. . imported "MT01"."FLX_RL_RULE_ACTIONS" 138.8 KB 1900 rows
............... ( output truncated ) ............
. . imported "MT01"."TEMP_TMP_MISMATCH" 0 KB 0 rows
. . imported "MT01"."TEMP_TMP_MISMATCH_1" 0 KB 0 rows
. . imported "MT01"."TEST" 0 KB 0 rows
. . imported "MT01"."TLOGLEVEL" 0 KB 0 rows
. . imported "MT01"."XF_OL_ST_EXT_TXN_XREF_MMDD" 0 KB 0 rows
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_CM_CH_WORKDAY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_CM_WORKDAY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_CO_COMBINE_LOGS_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_CO_MV_BROPTXN_SHELL_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_CO_PR_BROPTXN_SHELL_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_CH122" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_PL002" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_PL006" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_PL009" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_PL010" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_PL011" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_PL013" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_TD102" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_TD104" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_TD126" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_CH122" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_PL002" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_PL006" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_PL009" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_PL010" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_PL011" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_PL013" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_TD102" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_TD104" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_TD126" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DT_C_ADDSUB" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DT_C_BEGIN_END_PERD" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DT_SET_EOP_BOP_FLAGS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EOD_CHECK_ALL" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EOD_INITIALIZE" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EOD_IS_MONTHEND" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EOD_PROCESS_BROP_LOGS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EOD_PROLOGUE" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EXT_CHK_DAY_HOLIDAY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EXT_GET_NEXT_DATE" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_GLVALTXNSET_SHELL_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_GL_INIT_RESTART" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_GL_UPD_RESTART" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_GL_VAL_TXNS_SET" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_INS_OL_INST_DETAIL" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_LN_WR_ACTNS_PROLOGUE_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_OL_CHECK_TRAN" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_OL_CH_UPD_INST_DETAIL" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_OL_CUTOFF_MOVE_TXNLOGS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_OL_UNSET_CUTOFF" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_PI_GET_MEMOS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_RJS_INSERT_REC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_SETDATE_POSTEOD" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_SETDATE_PREEOD" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_ST_EOD" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_ST_EOD_PREPROC" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_ST_EOD_PROLOGUE_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_ST_EOD_SHELL_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_UPD_CASH_POS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."FLX_AP_DDL_OS02" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."INITIALIZE_HOST" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."PROC_DEPEND" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_BA_PURGE_OL_BOTS_BCL" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_BA_PURGE_SHELL_ENTRY" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_BRING_CASH_FORWARD" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_LCM17" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_LCM18" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_LCM19" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_LCM17" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_LCM18" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_LCM19" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_EXT_SPLIT_LOAN_DTLS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_GET_NEXT_WORKING_DATE" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_IS_USER_VAULT" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_OL_BATCH_OPERATIONS" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_OL_CALC_DAT_LOG" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_OL_GET_DAT_LOG" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_ST_PURGE" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_TELLER_CASH_FORWARD" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_UPD_BAT_STAT" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_XMIT_CLOSE_BRANCH_BATCH" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_XMIT_CLOSE_TELLER_BATCH" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_XMIT_CLOSE_VAULT_BATCH" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_XMIT_OPEN_BATCH" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DML_LCM06" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."AP_DDL_LCM06" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."FLX_AP_DDL_OS16" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."FLX_AP_DDL_OS23" created with compilation warnings
ORA-39082: Object type ALTER_FUNCTION:"MT01"."FLX_AP_DDL_OS09" created with compilation warnings
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_LN_ACCR_GET_PERIOD_END_DATE" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_LN_ACCR_MONTH_CROSSOVER" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_LN_POP_DRV_AMORTIZATION" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_LN_POP_DRV_REDO_TXNS" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_LN_WR_ACTIONS" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_PC_POP_DRV_REJECT_POLER" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."FLX_AP_DML_OS02" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."SETDATES" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_LN_ACCR_IS_YEAR_CROSSOVER" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."FLX_AP_DML_OS23" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."FLX_AP_DML_OS09" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_OR_POP_DEV_SUB_EXP" created with compilation warnings
ORA-39082: Object type ALTER_PROCEDURE:"MT01"."AP_OR_POP_DRV_SUB_EXP" created with compilation warnings
Processing object type SCHEMA_EXPORT/VIEW/VIEW
ORA-39082: Object type VIEW:"MT01"."VWE_CS_HO_ACCT_MODULE_XREF" created with compilation warnings
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-39082: Object type PACKAGE_BODY:"MT01"."ACPKS" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."ACPKS_POSITION" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_AC_GLOBAL" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_BA_PURGE" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_GLTBGLBAL" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_GLTXNPOSTING" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_GL_UPDATE" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_PI_LN_INTEGRATION" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_ST_BOD_SHELL" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_VAL_BATCH" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PK_VAL_CLOSE_BATCH" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVDATA" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVDDD" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVFILE" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVGEN" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVIO" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVJOB" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVREP" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLVXMN" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLV_LOG_IO" created with compilation warnings
ORA-39082: Object type PACKAGE_BODY:"MT01"."PLV_TRACE_IO" created with compilation warnings
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
Processing object type SCHEMA_EXPORT/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
Processing object type SCHEMA_EXPORT/POST_SCHEMA/PROCOBJ
Job "SYS"."SYS_IMPORT_FULL_01" completed with 120 error(s) at 18:24:32Please advice me what is the solution for this? what exactly must have been happen that all the pl/sql got converted in UPPERCASE.
Thanks in advance.Ok, so with the sql fie, you verified that the dump file is being represented in all upper case. Now you want to check the source database. Can you do this on the source data base.
set pagesize 10000
set long 900000000
select dbms_metadata.get_ddl('PACKAGE_BODY', 'SOME_PACKAGE_THAT_LOOKS_WRONG', 'SCHEMA_OWNING_PCK) from sys.dual;
If this comes out in all caps, then someone messed with your source database. If it doesn't, then I can't figure out how the dumpfile got to be all caps.
Let us know what the results are for the above query.
Thanks
Dean -
Error while impdp: ORA-02374: conversion error loading table
Hi,
I am trying to convert the character set from WE8ISO8859P1 to AL32UTF8 using expdp/impdp. for this I first convert WE8ISO8859P1 to WE8MSWIN1252 in source DB to get rid of “lossy” data. I created new database(target) with character set AL32UTF8 and nls_length_semantics = ’CHAR’ and created all the tablespaces as in source DB with auoexend on. I took full export (expdp) of source DB excluding TABLESPACE,STATISTICS,INDEX,CONSTRAINT,REF_CONSTRAINT and imported using impdp to target DB. I found below error in the import log file:
ORA-02374: conversion error loading table "SCTCVT"."SPRADDR_CVT"
ORA-26093: input data column size (44) exceeds the maximum input size (40)
ORA-02372: data for row: CONVERT_STREET_LINE1 : 0X'20202020202020202020202020202020202020202020202020'
I checked with select query on both DBs with below results.
source DB:
04:58:42 SQL> select count(*) from "SCTCVT"."SPRADDR_CVT";
COUNT(*)
74553
target DB:
04:59:24 SQL> select count(*) from "SCTCVT"."SPRADDR_CVT";
COUNT(*)
74552
please suggest me a solution to this.
Thanks and Regards.
Edited by: user12045167 on May 9, 2011 10:39 PMThanks for your update maher.
09:15:53 SQL> desc "SCTCVT"."SPRADDR_CVT"
Name Null? Type
SPRADDR_PIDM NUMBER(8)
CONVERT_PIDM VARCHAR2(9 CHAR)
SPRADDR_ATYP_CODE VARCHAR2(2 CHAR)
CONVERT_ATYP_CODE VARCHAR2(2 CHAR)
SPRADDR_SEQNO NUMBER(2)
CONVERT_SEQNO VARCHAR2(2 CHAR)
SPRADDR_FROM_DATE DATE
CONVERT_FROM_DATE VARCHAR2(8 CHAR)
SPRADDR_TO_DATE DATE
CONVERT_TO_DATE VARCHAR2(8 CHAR)
SPRADDR_STREET_LINE1 VARCHAR2(30 CHAR)
CONVERT_STREET_LINE1 VARCHAR2(40 CHAR)
SPRADDR_STREET_LINE2 VARCHAR2(30 CHAR)
CONVERT_STREET_LINE2 VARCHAR2(40 CHAR)
SPRADDR_STREET_LINE3 VARCHAR2(30 CHAR)
CONVERT_STREET_LINE3 VARCHAR2(40 CHAR)
SPRADDR_CITY VARCHAR2(20 CHAR)
CONVERT_CITY VARCHAR2(25 CHAR)
SPRADDR_STAT_CODE VARCHAR2(3 CHAR)
CONVERT_STAT_CODE VARCHAR2(25 CHAR)
SPRADDR_ZIP VARCHAR2(10 CHAR)
CONVERT_ZIP VARCHAR2(15 CHAR)
SPRADDR_CNTY_CODE VARCHAR2(5 CHAR)
CONVERT_CNTY_CODE VARCHAR2(5 CHAR)
SPRADDR_NATN_CODE VARCHAR2(5 CHAR)
CONVERT_NATN_CODE VARCHAR2(5 CHAR)
SPRADDR_PHONE_AREA VARCHAR2(3 CHAR)
CONVERT_PHONE_AREA VARCHAR2(3 CHAR)
SPRADDR_PHONE_NUMBER VARCHAR2(7 CHAR)
CONVERT_PHONE_NUMBER VARCHAR2(7 CHAR)
SPRADDR_PHONE_EXT VARCHAR2(4 CHAR)
CONVERT_PHONE_EXT VARCHAR2(4 CHAR)
SPRADDR_STATUS_IND VARCHAR2(1 CHAR)
CONVERT_STATUS_IND VARCHAR2(1 CHAR)
SPRADDR_ACTIVITY_DATE DATE
CONVERT_ACTIVITY_DATE VARCHAR2(8 CHAR)
SPRADDR_USER VARCHAR2(30 CHAR)
CONVERT_USER VARCHAR2(30 CHAR)
SPRADDR_ASRC_CODE VARCHAR2(4 CHAR)
CONVERT_ASRC_CODE VARCHAR2(4 CHAR)
SPRADDR_DELIVERY_POINT NUMBER(2)
CONVERT_DELIVERY_POINT VARCHAR2(2 CHAR)
SPRADDR_CORRECTION_DIGIT NUMBER(1)
CONVERT_CORRECTION_DIGIT VARCHAR2(1 CHAR)
SPRADDR_CARRIER_ROUTE VARCHAR2(4 CHAR)
CONVERT_CARRIER_ROUTE VARCHAR2(4 CHAR)
SPRADDR_GST_TAX_ID VARCHAR2(15 CHAR)
CONVERT_GST_TAX_ID VARCHAR2(15 CHAR)
SPRADDR_REVIEWED_IND VARCHAR2(1 CHAR)
CONVERT_REVIEWED_IND VARCHAR2(1 CHAR)
SPRADDR_REVIEWED_USER VARCHAR2(30 CHAR)
CONVERT_REVIEWED_USER VARCHAR2(30 CHAR)
SPRADDR_DATA_ORIGIN VARCHAR2(30 CHAR)
CONVERT_DATA_ORIGIN VARCHAR2(30 CHAR)
SPRADDR_CVT_RECORD_ID NUMBER(8)
SPRADDR_CVT_STATUS VARCHAR2(1 CHAR)
SPRADDR_CVT_JOB_ID NUMBER(8)
so here we can see its value is 40 (CONVERT_STREET_LINE1 VARCHAR2(40 CHAR)).
shall i go ahead altering the column? -
How to filter parent and child tables data in impdp?
Hi Friends,
i hope everyone doing good..
I have two tables in my schema like below.
STUDENT_DTLS:-
SID Sname CID
1 venkat 001
2 uppy 002
3 deepu 003
4 trinath 003
5 naveen 004
6 ramesh 005
COURSE_DTLS:-
CID CNAME Fee
001 Oracle 2000
002 java 6000
003 sieble 4000
004 informatica 3000
005 obiee 4000
if I load only few Student details say sid=1,2,3 into another environment using impdp,corresponding to those students course details from COURSE_DTLS table only need to be loaded.Not all course details.
Iam Expecting Result in new schema as below:-
SID Sname CID
1 venkat 001
2 uppy 002
3 deepu 003
CID CNAME Fee
001 Oracle 2000
002 java 6000
003 sieble 4000
But when i am using the below import scrit,The COURSE_DTLS is loading first and its query option(select cid from STUDENT_DTLS) is returning no rows.Because at that time no data is insertred into STUDENT_DTLS yet.
secondly it is importing data into STUDENT_DTLS with query option where sid=in (1,2,3) which is loaded propelry.
Thirdly it is trying to enable primary key and Foreign key constraints which is also failing because of no data in COURSE_DTLS table.
i have changed the order of tables in TABLES clause like tables=COURSE_DTLS ,STUDENT_DTLS.But still COURSE_DTLS table is loading first.
impdp pa_data_sub/******* NETWORK_LINK=qdssih30 tables=STUDENT_DTLS,COURSE_DTLS query='STUDENT_DTLS:"where SID IN(1,2,3)"','COURSE_DTLS:"where cid in(select cid from STUDENT_DTLS)"', CONTENT=all table_exists_action=replace directory=DATA_PUMP_DIR logfile=exp_join.log
output:
Total estimation using BLOCKS method: 128 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
. . imported "PA_DATA_SUB"."COURSE_DTLS" 0 rows
. . imported "PA_DATA_SUB"."STUDENT_DTLS" 3 rows
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-02298: cannot validate (PA_DATA_SUB.SYS_C0040905) - parent keys not found
Failing sql is:
ALTER TABLE "PA_DATA_SUB"."STUDENT_DTLS" ADD FOREIGN KEY ("CID") REFERENCES "PA_DATA_SUB"."COURSE_DTLS" ("CID") ENABLE
Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
Job "PA_DATA_SUB"."SYS_IMPORT_TABLE_01" completed with 1 error(s) at 17:28:13
Please suggest me how to achieve this task in a single import command?
Is there any option in impdp to prioritize the table to be loaded first?
Thanks,
Venkat VadlamudiYou can't be guaranteed which order the data will be loaded in, so using a query that examines a table that is being imported is not going to always work the way you want it. The failing constraints makes sense because there is no data.
So, in your case, course_dtls gets imported first and the table student-dtls exists, but it not populated yet, so the select cid from student_dtls comes back with 0 rows. The second query works fine.
You might be able to change the query to be:
'COURSE_DTLS:"where cid in(select cid from STUDENT_DTLS@qdssih30 where SID IN(1,2,3)"'
This way, you query the source table pointed to by the network link and you use the same subquery from the first table.
This should work for you... I think anyway.
Dean -
Error when doing importing with impdp
Hi,
I tried to do export then import the schema from and to same schema. However, when doing export with expdp everything was okay.
Problem begins when I tried to do importing by using impdp. I also tried to drop the current schema and created the new one but it still doesn't work.
If I didn't drop the current schema, it logs looks like this
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
ORA-31684: Object type SEQUENCE:"HSS"."LCM-MIGRATION_ID-SEQ" already exists
ORA-31684: Object type SEQUENCE:"HSS"."WKS_IDENTITY_SEQ" already exists
ORA-31684: Object type SEQUENCE:"HSS"."ESS_FAILOVER_RESOURCE_SEQ" already exists
ORA-31684: Object type SEQUENCE:"HSS"."ESS_FAILOVER_LEASE_OWNER_SEQ" already exists
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39151: Table "HSS"."HSS_COMPONENT" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."HSS_COMPONENT_LINKS" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."HSS_COMPONENT_PROPERTY_VALUES" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."HSS_COMPONENT_TIERS" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."ESS_CLUSTER_SERVER_MAPPING" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."HSS_COMPONENT_TYPES" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."CSS_IDENTITY" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."CSS_GROUP_MEMBERS" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
ORA-39151: Table "HSS"."CSS_USERS" exists. All dependent metadata and data will be skipped due to table_exists_action of skip
Job "HSS"."SYS_IMPORT_FULL_01" completed with 95 error(s) at 08:47:21
And then this is the log when doing importing, I only highlighted the necessary part which I think related with my problem
Starting "HYPSS"."SYS_IMPORT_FULL_01": HYPSS/******** TRANSFORM=oid:n:type directory=test_dir logfile=imptest.log dumpfile=HYPSS.dmp
Processing object type SCHEMA_EXPORT/USER
ORA-31684: Object type USER:"HYPSS" already exists
. . imported "HYPSS"."CSS_ROLE_LOCALES" 1.630 MB 6358 rows
. . imported "HYPSS"."HSS_COMPONENT_FILES" 601.5 KB 33 rows
. . imported "HYPSS"."HSS_COMPONENT_PROPERTY_VALUES" 130.7 KB 1657 rows
. . imported "HYPSS"."CES_APPS" 10.54 KB 1 rows
etc....
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
ORA-39083: Object type INDEX_STATISTICS failed to create with error:
ORA-01403: no data found
ORA-01403: no data found
Failing sql is:
DECLARE I_N VARCHAR2(60); I_O VARCHAR2(60); c DBMS_METADATA.T_VAR_COLL; df varchar2(21) := 'YYYY-MM-DD:HH24:MI:SS'; BEGIN DELETE FROM "SYS"."IMPDP_STATS"; c(1) := 'TRIGGER_NAME'; c(2) := 'TRIGGER_GROUP'; DBMS_METADATA.GET_STAT_INDNAME('HYPSS','QRTZ_TRIGGERS',c,2,i_o,i_n); INSERT INTO "SYS"."IMPDP_STATS" (type,version,flags,c1,c2,c3,c5,n1,n2,n3,n4,n5,n6,n7,n8,n
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
The source schema is on USERS tablespace (default). The destination schema I tried to put on the same tablespace but it doesn't work. However when I changed the destination tablespace, it also doesn't work.
Anybody got the idea why this occurs? Thanks.got error like this
ORA-39152: Table "HSS"."CSS_GROUP_MEMBERS" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-39152: Table "HSS"."CSS_USERS" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-39152: Table "HSS"."CSS_ROLES" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-39152: Table "HSS"."CSS_DELEGATED_MEMBERS" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-39152: Table "HSS"."CSS_ROLE_MEMBERS" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-39152: Table "HSS"."CSS_ROLE_LOCALES" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-39152: Table "HSS"."CSS_GROUPS" exists. Data will be appended to existing table but all dependent metadata will be skipped due to table_exists_action of append
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-00001: unique constraint (HSS.COMPONENT_LINKS_PK_IND) violated
ORA-31693: Table data object "HSS"."HSS_COMPONENT_TYPES" failed to load/unload and is being skipped due to error:
ORA-00001: unique constraint (HSS.COMPONENT_TYPES_PK_IND) violated
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists
ORA-39111: Dependent object type COMMENT skipped, base object type VIEW:"HSS"."VW_APPLICATIONS" already exists -
IMPDP SQLFILE : multibyte characters in constraint_name leads to ORA-00972
Hi,
I'm actually dealing with constraint_name made of multibyte characters (for example : constrain_name='VALIDA_CONFIRMAÇÃO_PREÇO13').
Of course this Bad Idea® is inherited (I'm against all the fancy stuff like éàù in filenames and/or directories on my filesystem....)
The scenario is as follows :
0 - I'm supposed to do a "remap_schema". Everything in the schema SCOTT should now be in a schema NEW_SCOTT.
1 - The scott schema is exported via datapump
2 - I do an impdp with SQLFILE in order to get all the DDL (table, packages, synonyms, etc...)
3 - I do some sed on the generated sqlfile to change every occurence of SCOTT to NEW_SCOTT (this part is OK)
4 - Once the modified sqlfile is executed, I do an impdp with DATA_ONLY.
(The scenario was imagined from this thread : {message:id=10628419} )
I'm getting some ORA-00972: identifier is too long at step 4 when executing the sqlfile.
I see that some DDL for constraint creation in the file (generated at step#2) is written as follow :ALTER TABLE "TW_PRI"."B_TRANSC" ADD CONSTRAINT "VALIDA_CONFIRMAÃÃO_PREÃO14" CHECK ...Obviously, the original name of the constraint with cedilla and tilde gets translated to something else which is longer than 30 char/byte...
As the original name is from Brazil, I also tried do add an EXPORT LANG=pt_BR.UTF-8 in my script before running the impdp for sqlfile. This didn't change anything. (the original $LANG is en_US.UTF-8)
In order to create a testcase for this thread, I tried to reproduce on my sandbox database... but, there, I don't have the issue. :-(
The real system is an 4-nodes database on Exadata (11.2.0.3) with NLS_CHARACTERSET=AL32UTF8.
My sandbox database is a (nonRAC) 11.2.0.1 on RHEL4 also AL32UTF8.
The constraint_name is the same on both system : I checked byte by byte using DUMP() on the constraint_name.
Feel free to shed any light and/or ask for clarification if needed.
Thanks in advance for those who'll take on their time to read all this.
I decided to include my testcase from my sandbox database, even if it does NOT reproduce the issue +(maybe I'm missing something obvious...)+
I use the following files.
- createTable.sql :$ cat createTable.sql
drop table test purge;
create table test
(id integer,
val varchar2(30));
alter table test add constraint VALIDA_CONFIRMAÇÃO_PREÇO13 check (id<=10000000000);
select constraint_name, lengthb(constraint_name) lb, lengthc(constraint_name) lc, dump(constraint_name) dmp
from user_constraints where table_name='TEST';- expdpTest.sh :$ cat expdpTest.sh
expdp scott/tiger directory=scottdir dumpfile=testNonAscii.dmp tables=test- impdpTest.sh :$ cat impdpTest.sh
impdp scott/tiger directory=scottdir dumpfile=testNonAscii.dmp sqlfile=scottdir:test.sqlfile.sql tables=testThis is the run :
[oracle@Nicosa-oel test_nonAsciiColName]$ sqlplus scott/tiger
SQL*Plus: Release 11.2.0.1.0 Production on Tue Feb 12 18:58:27 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> @createTable
Table dropped.
Table created.
Table altered.
CONSTRAINT_NAME LB LC
DMP
VALIDA_CONFIRMAÇÃO_PREÇO13 29 26
Typ=1 Len=29: 86,65,76,73,68,65,95,67,79,78,70,73,82,77,65,195,135,195,131,79,95
,80,82,69,195,135,79,49,51
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@Nicosa-oel test_nonAsciiColName]$ ./expdpTest.sh
Export: Release 11.2.0.1.0 - Production on Tue Feb 12 19:00:12 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Starting "SCOTT"."SYS_EXPORT_TABLE_01": scott/******** directory=scottdir dumpfile=testNonAscii.dmp tables=test
Estimate in progress using BLOCKS method...
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 0 KB
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
. . exported "SCOTT"."TEST" 0 KB 0 rows
Master table "SCOTT"."SYS_EXPORT_TABLE_01" successfully loaded/unloaded
Dump file set for SCOTT.SYS_EXPORT_TABLE_01 is:
/home/oracle/scott_dir/testNonAscii.dmp
Job "SCOTT"."SYS_EXPORT_TABLE_01" successfully completed at 19:00:22
[oracle@Nicosa-oel test_nonAsciiColName]$ ./impdpTest.sh
Import: Release 11.2.0.1.0 - Production on Tue Feb 12 19:00:26 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SCOTT"."SYS_SQL_FILE_TABLE_01" successfully loaded/unloaded
Starting "SCOTT"."SYS_SQL_FILE_TABLE_01": scott/******** directory=scottdir dumpfile=testNonAscii.dmp sqlfile=scottdir:test.sqlfile.sql tables=test
Processing object type TABLE_EXPORT/TABLE/TABLE
Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Job "SCOTT"."SYS_SQL_FILE_TABLE_01" successfully completed at 19:00:32
[oracle@Nicosa-oel test_nonAsciiColName]$ cat scott_dir/test.sqlfile.sql
-- CONNECT SCOTT
ALTER SESSION SET EVENTS '10150 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10904 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '25475 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10407 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '10851 TRACE NAME CONTEXT FOREVER, LEVEL 1';
ALTER SESSION SET EVENTS '22830 TRACE NAME CONTEXT FOREVER, LEVEL 192 ';
-- new object type path: TABLE_EXPORT/TABLE/TABLE
CREATE TABLE "SCOTT"."TEST"
( "ID" NUMBER(*,0),
"VAL" VARCHAR2(30 BYTE)
) SEGMENT CREATION DEFERRED
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 COMPRESS FOR OLTP LOGGING
TABLESPACE "MYTBSCOMP" ;
-- new object type path: TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
ALTER TABLE "SCOTT"."TEST" ADD CONSTRAINT "VALIDA_CONFIRMAÇÃO_PREÇO13" CHECK (id<=10000000000) ENABLE;I was expecting to have the cedilla and tilde characters displayed incorrectly....
Edited by: Nicosa on Feb 12, 2013 7:13 PMSrini Chavali wrote:
If I understand you correctly, you are unable to reproduce the issue in the test instance, while it occurs in the production instance. Is the "schema move" being done on the same database - i.e. you are "moving" from SCOTT to NEW_SCOTT on the same database (test to test, and prod to prod) ? Do you have to physically move/copy the dmp file ? Hi Srini,
On the real system, the schema move will be to and from different machines (but same DBversion).
I'm not doing the real move for the moment, just trying to validate a way to do it, but I guess it's important to say that the dump being used for the moment comes from the same database (the long story being that due to some column using object datatype which caused error in the remap, I had to reload the dump with the "schema rename", drop the object column, and recreate a dump file without the object_datatype...).
So Yes, the file will have to move, but in the current test, it doesn't.
Srini Chavali wrote:
Obviously something is different in production than test - can you post the output of this command from both databases ?
SQL> select * from NLS_DATABASE_PARAMETERS;
Yes Srini, something is obviously different : I'm starting to think that the difference might be in the Linux/shell side rather than on the impdp as datapump is supposed to be NLS_LANG/CHARSET-proof +(when traditional imp/exp was really sensible on those points)+
The result on the Exadata where I have the issue :PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 11.2.0.3.0the result on my sandbox DB :PARAMETER VALUE
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CHARACTERSET AL32UTF8
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY $
NLS_COMP BINARY
NLS_LENGTH_SEMANTICS BYTE
NLS_NCHAR_CONV_EXCP FALSE
NLS_NCHAR_CHARACTERSET AL16UTF16
NLS_RDBMS_VERSION 11.2.0.1.0------
Richard Harrison . wrote:
Hi,
Did you set NLS_LANG also when you did the import?Yes, that is one of the difference between the Exadata and my sandbox.
My environnement in sandbox has NLS_LANG=AMERICAN_AMERICA.AL32UTF8 where the Exadata doesn't have the variable set.
I tried to add it, but it didn't change anything.
Richard Harrison . wrote:
Also not sure why you are doing the sed part? Do you have hard coded scheme references inside some of the plsql?Yes, that is why I choose to sed. The (ugly) code have :
- Procedures inside the same package that references one another with the schema prepended
- Triggers with PL/SQL codes referencing tables with schema prepended
- Dynamic SQL that "builds" queries with schema prepended
- Object Type that does some %ROWTYPE on tables with schema prepended (that will be solved by dropping the column based on those types as they obviously are not needed...)
- Data model with object whose names uses non-ascii characters
+(In France we use to call this "gas power plant" in order to tell how a mess it is : pipes everywhere going who-knows-where...)+
The big picture is that this kind of "schema move & rename" should be as automatic as possible, as the project is to actually consolidate several existing databases on the Exadata :
One schema for each country, hence the rename of the schemas to include country-code.
I actually have a workaround yet : Rename the objects that have funky characters in their name before doing the export.
But I was curious to understand why the SQLFILE messed up the constraint_name on one sustem when it doesn't on another... -
Impdp does not create user/schema
I'm an Oracle noob. I'm trying to copy (expdp/impdp) schema (no data) from one machine to another. I do not want any remapping. I just want empty table structure created on targetHOST.
Error I get is:
ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
ORA-31625: Schema ZABBIX is needed to import this object, but is unaccessible
ORA-01435: user does not exist
My understanding is that if the user performing import has 'IMPORT FULL DATABASE' privilege, it'll create the users/schemas in the targetHOST. I granted it to 'scott' and tried with that too, same error.
- DB version: SQL*Plus: Release 11.2.0.1.0 Production on Thu Oct 24 14:27:41 2013
- If it matters the DB version on sourceHOST is 11.2.0.***3***
- OS: Linux targetHOST 2.6.18-308.el5 #1 SMP Fri Jan 27 17:17:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
Import errors:
(0)oracle@targetHOST$ sqlplus system/manager
SQL*Plus: Release 11.2.0.1.0 Production on Thu Oct 24 14:27:41 2013
Copyright (c) 1982, 2009, Oracle. All rights reserved.
SQL> select * from session_privs;
PRIVILEGE
IMPORT FULL DATABASE
CREATE SESSION
.......200 other privileges.......
202 rows selected.
SQL> ^D
(0)oracle@targetHOST$
(0)oracle@targetHOST$ impdp system/oracle123 directory=TEST_DIR dumpfile=ZABBIX.dmp logfile=impdpZabbix.log
Import: Release 11.2.0.1.0 - Production on Thu Oct 24 14:14:51 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded
Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** directory=TEST_DIR dumpfile=ZABBIX.dmp logfile=impdpZabbix.log
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
ORA-39083: Object type PROCACT_SCHEMA failed to create with error:
ORA-31625: Schema ZABBIX is needed to import this object, but is unaccessible
ORA-01435: user does not exist
Failing sql is:
BEGIN
sys.dbms_logrep_imp.instantiate_schema(schema_name=>SYS_CONTEXT('USERENV','CURRENT_SCHEMA'), export_db_name=>'XXX.YYY.COM', inst_scn=>'7788478540892');COMMIT; END;
Processing object type SCHEMA_EXPORT/TABLE/TABLE
ORA-39083: Object type TABLE:"ZABBIX"."TABLE1" failed to create with error:
ORA-01918: user 'ZABBIX' does not exist
Failing sql is:
CREATE TABLE "ZABBIX"."TABLE1" ("COLUMN1" VARCHAR2(20 BYTE) NOT NULL ENABLE, "COLUMN2" VARCHAR2(20 BYTE), "COLUMN3" VARCHAR2(20 BYTE)) SEGMENT CREATION IMMEDIATE PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAU
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 2 error(s) at 14:14:53
(5)oracle@targetHOST$
Export was done using following command (on a different machine)
(0)oracle@sourceHOST$ expdp zabbix/zabbix schemas=ZABBIX content=METADATA_ONLY directory=TEST_DIR dumpfile=ZABBIX.dmp logfile=expdpZABBIX.log
Complete export log available here.:I figured it out on my own. Required privilege is 'CREATE USER'. I don't have system's password so I granted CREATE USER to zabbix, made it DBA and it seems to be exporting more than it did last time:
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Yet to import but looks good so far..
Appreciate you taking the time..
Thanks... -
Hi,
I am trying to generate sql script form the dmp file.
but getting this error.
C:\Documents and Settings\satish.HTSS>impdp egift/egift@local directory=DIR1 dum
pfile=exp.dmp sqlfile=create.sql
Import: Release 10.2.0.1.0 - Production on Saturday, 24 May, 2008 0:16:07
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Produc
tion
With the Partitioning, OLAP and Data Mining options
Master table "EGIFT"."SYS_SQL_FILE_FULL_01" successfully loaded/unloaded
Starting "EGIFT"."SYS_SQL_FILE_FULL_01": egift/********@local directory=DIR1 du
mpfile=exp.dmp sqlfile=create.sql
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/PROCEDURE
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_
PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
Processing object type SCHEMA_EXPORT/PROCEDURE/ALTER_PROCEDURE
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/TRIGGER
ORA-39125: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS while calling D
BMS_METADATA.CONVERT []
ORA-06502: PL/SQL: numeric or value error
LPX-00007: unexpected end-of-file encountered
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 6235
----- PL/SQL Call Stack -----
object line object
handle number name
20B135F8 14916 package body SYS.KUPW$WORKER
20B135F8 6300 package body SYS.KUPW$WORKER
20B135F8 12279 package body SYS.KUPW$WORKER
20B135F8 3279 package body SYS.KUPW$WORKER
20B135F8 3956 package body SYS.KUPW$WORKER
20B135F8 6931 package body SYS.KUPW$WORKER
20B135F8 1262 package body SYS.KUPW$WORKER
18E96684 2 anonymous block
Job "EGIFT"."SYS_SQL_FILE_FULL_01" stopped due to fatal error at 00:16:31and this error always comes when it turns to generate sql for the triggers.
i am facing this error continuously.
thanksHi,
Its an unpatched db.So you must patch it first.Here is what is mentioned about this error
39125, 00000, "Worker unexpected fatal error in %s while calling %s [%s]" // *Cause: An unhandled exception was detected internally within the worker
// process for the Data Pump job while calling the specified external
// routine. This is an internal error. Additional information may be
// supplied.
// *Action: If problem persists, contact Oracle Customer Support.
So the better part is to contact Support.See if this thread can help you.Its not having much but still ,
Error ORA-39125 and ORA-04063 during export for transportable tablespace
Aman.... -
hi all,
I am doing a table import using impdp and getting the following error.
both the Source and Target database have the same Oracle Anyversion 11.2.0.1.0,same Characterset and same IBM AIX 5.3 Servers.
Below is the parfile:
Userid=system
DUMPFILE=directory4:dump01.dmp,directory4:dump02.dmp,dump03.dmp,dump04.dmp,directory4:dump05.dmp,directory5:dump06.dmp
logfile=xxxxxxxxxxxxxxx.log
directory=dump1
remap_schema=xxxxxxxxxxxxxx:xxxxxxxxxxxxxx
remap_tablespace=xxxxxxxxxxxxxx:xxxxxxxxxxxxxx
Table_exists_action=TRUNCATE
remap_tablespace=xxxxxxxxxxxxxx:xxxxxxxxxxxxxx
remap_tablespace=xxxxxxxxxxxxxx:xxxxxxxxxxxxxx
LOG:
++Import: Release 11.2.0.1.0 - Production on Sat May 21 21:17:10 2011++
++Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.++
++;;;++
++Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production++
++With the Partitioning, Real Application Clusters, OLAP, Data Mining++
++and Real Application Testing options++
++Master table "SYSTEM"."SYS_IMPORT_FULL_01" successfully loaded/unloaded++
++Starting "SYSTEM"."SYS_IMPORT_FULL_01": system/******** parfile=s_c.par++
++Processing object type TABLE_EXPORT/TABLE/TABLE++
++ORA-39153: Table "Schema_Name"."Table_Name" exists and has been truncated. Data will be loaded but all dependent metadata wi++
++ll be skipped due to table_exists_action of truncate++
++Processing object type TABLE_EXPORT/TABLE/TABLE_DATA++
++ORA-31693: Table data object "Schema_Name"."Table_Name":"Partition_name" failed to load/unload and is being skipped du++
++e to error:++
++ORA-29913: error in executing ODCIEXTTABLEOPEN callout++
++ORA-29400: data cartridge error++
++ORA-02373: Error parsing insert statement for table "Schema_Name"."Table_Name".++
++ORA-22921: length of input buffer is smaller than amount requested++
++......++
++......++
++ORA-31693: Table data object "Schema_Name"."Table_Name":"Partition_name" failed to load/unload and is being skipped du++
++e to error:++
++ORA-29913: error in executing ODCIEXTTABLEOPEN callout++
++ORA-29400: data cartridge error++
++ORA-02373: Error parsing insert statement for table "Schema_Name"."Table_Name".++
++ORA-22921: length of input buffer is smaller than amount requested++
++. . imported "Schema_Name"."Table_Name":"Partition_name" 0 KB 0 rows++
++. . imported "Schema_Name"."Table_Name":"Partition_name" 0 KB 0 rows++
++Processing object type TABLE_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT++
++Processing object type TABLE_EXPORT/TABLE/INDEX/INDEX++
++Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT++
++Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS++
++Processing object type TABLE_EXPORT/TABLE/TRIGGER++
++Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS++
++Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 23 error(s) at 21:17:24++
Any suggestions?You have used directory=dump1 but instead of dump1 i think it should be directory 4..
And also You need to get whoever created the directory to grant you user access (read/write) to that directory -
Full expdp and impdp: one db to another
Hi! Good Day!
I Would like to ask for any help regarding my problem.
I would like to create a full export of one database to and import it on another database. This 2 database are on a separate machines.
I am trying to use the expdp and impdp tool to do this task. However, i have been experiencing some problems during the import task.
here is the detail of my problems:
When i try to impdp the dump file, it seems that i was not able to iimport the user's data and metadata.
Here is the exact command that i've used during the import and export task:
export (server #1)
expdp user01/******** directory=ora3_dir full=y dumpfile=db_full%U.dmp filesize=2G parallel=4 logfile=db_full.log
import (server #2)
impdp user01/******** directory=ora3_dir dumpfile=db_full%U.dmp full=y log=db_full.log sqlfile=db_full.sql estimate=blocks parallel=4
here is the log that was generated during the impdp running:
Import: Release 10.2.0.1.0 - 64bit Production on Friday, 27 November, 2009 17:41:07
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Master table "SSMP"."SYS_SQL_FILE_FULL_01" successfully loaded/unloaded
Starting "SSMP"."SYS_SQL_FILE_FULL_01": ssmp/******** directory=ora3_dir dumpfile=ssmpdb_full%U.dmp full=y logfile=ssmpdb_full.log sqlfile=ssmpdb_full.sql
Processing object type DATABASE_EXPORT/TABLESPACE
Processing object type DATABASE_EXPORT/PROFILE
Processing object type DATABASE_EXPORT/SYS_USER/USER
Processing object type DATABASE_EXPORT/SCHEMA/USER
Processing object type DATABASE_EXPORT/ROLE
Processing object type DATABASE_EXPORT/GRANT/SYSTEM_GRANT/PROC_SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/GRANT/SYSTEM_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/ROLE_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/DEFAULT_ROLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLESPACE_QUOTA
Processing object type DATABASE_EXPORT/RESOURCE_COST
Processing object type DATABASE_EXPORT/SCHEMA/DB_LINK
Processing object type DATABASE_EXPORT/TRUSTED_DB_LINK
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/SEQUENCE
Processing object type DATABASE_EXPORT/SCHEMA/SEQUENCE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/DIRECTORY/DIRECTORY
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/DIRECTORY/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type DATABASE_EXPORT/CONTEXT
Processing object type DATABASE_EXPORT/SCHEMA/PUBLIC_SYNONYM/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/SYNONYM
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_SPEC
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/PRE_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SYSTEM_PROCOBJACT/POST_SYSTEM_ACTIONS/PROCACT_SYSTEM
Processing object type DATABASE_EXPORT/SCHEMA/PROCACT_SCHEMA
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TABLE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/PRE_TABLE_ACTION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/INDEX
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/CONSTRAINT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/INDEX_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/COMMENT
Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE/PACKAGE_SPEC
Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/FUNCTION
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/PROCEDURE
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/FUNCTION/ALTER_FUNCTION
Processing object type DATABASE_EXPORT/SCHEMA/PROCEDURE/ALTER_PROCEDURE
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/VIEW
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/GRANT/CROSS_SCHEMA/OBJECT_GRANT
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/COMMENT
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/REF_CONSTRAINT
Processing object type DATABASE_EXPORT/SCHEMA/PACKAGE_BODIES/PACKAGE/PACKAGE_BODY
Processing object type DATABASE_EXPORT/SCHEMA/TYPE/TYPE_BODY
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/FUNCTIONAL_AND_BITMAP/INDEX
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/STATISTICS/FUNCTIONAL_AND_BITMAP/INDEX_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/STATISTICS/TABLE_STATISTICS
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_TABLE_ACTION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/JOB
Processing object type DATABASE_EXPORT/SCHEMA/DIMENSION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCACT_INSTANCE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCDEPOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
Job "SSMP"."SYS_SQL_FILE_FULL_01" successfully completed at 17:43:09
Thank you in advance.I believe there are lines like that in the export log.
here's an extract from the log file:
Processing object type DATABASE_EXPORT/SCHEMA/VIEW/TRIGGER
Processing object type DATABASE_EXPORT/SCHEMA/JOB
Processing object type DATABASE_EXPORT/SCHEMA/DIMENSION
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCACT_INSTANCE
Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_INSTANCE/PROCDEPOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCOBJ
Processing object type DATABASE_EXPORT/SCHEMA/POST_SCHEMA/PROCACT_SCHEMA
. . exported "SSMP"."SMALLBOX" 450.2 MB 2489790 rows
. . exported "SSMP"."LTCONFSB" 397.9 MB 3122899 rows
. . exported "SSMP"."INFRJCT" 317.3 MB 3615810 rows
. . exported "SSMP"."ICTEST1" 202.5 MB 789618 rows
. . exported "SSMP"."EQUIPERF" 315.3 MB 3008636 rows
. . exported "SSMP"."INFOPE2" 190.7 MB 569039 rows
. . exported "SSMP"."SMALLBSB" 189.8 MB 2659468 rows
. . exported "PRS1"."STKDTLOLD" 193.4 MB 983322 rows
. . exported "SSMP"."ICTEST11" 185.2 MB 553916 rows
. . exported "PRS1"."PURCHASE" 166.5 MB 122787 rows
. . exported "SSMP"."JIGREC" 183.5 MB 2664488 rows
. . exported "SSMP"."SALES" 112.4 MB 294134 rows
. . exported "SSMP"."P_INFOPE" 160.4 MB 485773 rows
. . exported "SSMP"."CIOP" 128.1 MB 385160 rows
. . exported "SSMP"."SMALLBOX2" 126.0 MB 589964 rows
. . exported "SSMP"."SHIPOUT" 123.4 MB 281778 rows
. . exported "SSMP"."INFHISTORY" 129.9 MB 786844 rows
. . exported "SYSMAN"."MGMT_TARGETS" 14.90 KB 11 rows
. . exported "SSMP"."LOGCNT" 4.937 KB 1 rows
. . exported "SSMP"."WEEKINF" 45.07 KB 700 rows
. . exported "SSMP"."DEPTNM" 12.33 KB 81 rows
. . exported "SSMP"."WFRID" 5.953 KB 2 rows
. . exported "SSMP"."MATDTLS" 85.53 KB 199 rows
. . exported "SSMP"."ICRATTACH" 9.257 KB 11 rows
. . exported "SSMP"."WIP2" 20.34 KB 67 rows
. . exported "SSMP"."MATINFO" 17.83 KB 43 rows
. . exported "SSMP"."ICRFAPP" 11.48 KB 11 rows
. . exported "SSMP"."WMXINF" 43.60 KB 500 rows
. . exported "SSMP"."MLDMACHINE" 32.30 KB 228 rows
. . exported "SSMP"."ICRNAME" 10.48 KB 23 rows
. . exported "SSMP"."XLODCNT" 4.937 KB 1 rows
. . exported "SSMP"."IJPLODCNT" 5.234 KB 1 rows
. . exported "SSMP"."MONTHINF" 14.67 KB 152 rows
. . exported "SSMP"."YYSTMP" 15.57 KB 59 rows
. . exported "SSMP"."MPRICE" 39.95 KB 365 rows
. . exported "SYSMAN"."ESM_COLLECTION" 8.585 KB 91 rows
. . exported "SSMP"."INFCHKSHT" 6.406 KB 4 rows
. . exported "SSMP"."MRKLNO" 4.929 KB 1 rows
. . exported "SSMP"."JPNMARK" 5.890 KB 2 rows
. . exported "SSMP"."LODCNT" 4.921 KB 1 rows
. . exported "SSMP"."MRPNAME" 29.73 KB 310 rows
. . exported "SYSMAN"."EXPORT000381" 49.68 KB 244 row
Maybe you are looking for
-
Creating xml file from fields of a fmb
Hi, What i want to do is to create a "generic" button (which can work for all forms of my application) which ables the application to create a xml file completed with all fields on my form. The matter is that i can't know by advance all fields of my
-
Mac doesn't boot after splitting BOOTCAMP drive under Windows 8.1
Macbook pro mid 2012, OS X Mavericks I've installed Windows 8.1 x64 using Bootcamp assistant. In Windows I went to Disk Management and shrank drive C: from 200 GB to 94 GB and created a new drive D: from unallocated space. After restart Windows doesn
-
How to configure Third party software with SAP ??
Hi all! Its little urgent!!! I have an overview of XI. Currently we have scenario like Third party tool is there which i want to connect to SAP through XI. Can anybody provide answer my few queries? 1. Step by Step guide for configuration. 2. Basis
-
Not availing CVD for Import material
Hi All, My client has one requirement , they are importing few materials as a part of their Final goods and they do export , since Export order in Indian scenario does not subject to Excise Duty , hence they dont want to avail CVD for those type of
-
Best Way To Reastart In To MacOS X
What Is The Best Y To Start MacOS X From Win XP