Impdp

Hi,
I am importing partitions separately in a new schema and using this command
impdp sh2/xxx directory=dp_dir dumpfile=export_sh1.dmp logfile=exportsh1.log tables=sh1.costs1_part:p4 table_exists_action=append content=all remap_schema=sh1:sh2
It gives an error ORA-39151: Table "SH2"."COSTS1_PART" exists. All dependent metadata and data will be skipped due to table_exists_action of append
Although it imports that partition and I can verify the records as well. How to fix this error, I have to import the indexes as well which it skipped. How can i do that?
Any suggestions?
Thanks

Check
ORA-39151 in impdp
use
CONTENT=DATA_ONLY TABLE_EXISTS_ACTION=APPEND EXCLUDE=INDEX,CONSTRAINT
Edited by: Osama_mustafa on Oct 24, 2012 9:13 AM

Similar Messages

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

Impdp triggers always give error ORA-04071:missing BEFORE, AFTER or INSTEAD

Hello,
I am using 11g impdp to create a test system.
I use this cmd to import
impdp 'SYS/xxxxx@PWRFUN AS SYSDBA' dumpfile=PWRPROD.DMP logfile=PWRFUNimportPROD.log SCHEMAS=pwrplant TABLE_EXISTS_ACTION=REPLACE
Then I get this error for all the triggers
ORA-39083: Object type TRIGGER failed to create with error:
ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword
Failing sql is:
CREATE TRIGGER "PWRPLANT"."APPROVAL_STEPS_HISTORY" PS_HISTORY
BEFORE UPDATE OR INSERT ON PWRPLANT.APPROVAL_STEPS_HISTORY
FOR EACH ROW
BEGIN    :new.user_id := USER;    :new.time_stamp := SYSDATE; END;
As you can see, the trigger does contain the word "before".
When I remove " "PWRPLANT"."APPROVAL_STEPS_HISTORY" " and run the trigger below, it compiles correctly. Why is this, and how do I make my impdp to run correctly?
CREATE TRIGGER PS_HISTORY
BEFORE UPDATE OR INSERT ON PWRPLANT.APPROVAL_STEPS_HISTORY
FOR EACH ROW
BEGIN    :new.user_id := USER;    :new.time_stamp := SYSDATE; END;

same error, thanks for your attemp
Error starting at line 1 in command:
CREATE TRIGGER "PWRPLANT"."APPROVAL_STEPS_HISTORY" PS_HISTORY
BEFORE UPDATE OR INSERT ON PWRPLANT.APPROVAL_STEPS_HISTORY
REFERENCING new AS new
FOR EACH ROW
BEGIN :new.user_id := USER; :new.time_stamp := SYSDATE; END;
Error report:
ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword
04071. 00000 - "missing BEFORE, AFTER or INSTEAD OF keyword"
*Cause:    The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.
*Action:   Specify either BEFORE, AFTER or INSTEAD OF.

Can we use impdp to import the data from an normal exp dump?

Hi All,
I have a export dump taken from a 9i database. Can i use impdp to import the data into 10g database from that 9i exp dump?
Please suggest
thanks and Regards
Arun

Hi,
I have a export dump taken from a 9i database. Can i use impdp to import the data into 10g database from that 9i exp dump?Yes, it can be.
Refer:
http://wiki.oracle.com/thread/3734722/can+a+9i+dump+file+be+imported+into+10%3F
thanks,
X A H E E R

Error while using REMAP_TABLE and WHERE clause together in IMPDP

I am trying to move some records from a very large table to another small table.
I am facing trouble while using REMAP_TABLE and WHERE clause together in IMPDP.
Problem is data filter is not getting applied and all records are getting imported.
here is how I have simulated this. please advice.
CREATE TABLE TSHARRHB.TMP1
A NUMBER,
B NUMBER
begin
Insert into TSHARRHB.TMP1
   (A, B)
Values
   (1, 1);
Insert into TSHARRHB.TMP1
   (A, B)
Values
   (2, 2);
COMMIT;
end;
expdp system/password TABLES=tsharrhb.TMP1 DIRECTORY=GRDP_EXP_DIR DUMPFILE=TMP1.dmp REUSE_DUMPFILES=YES LOGFILE=EXP.log PARALLEL=8
impdp system/password DIRECTORY=GRDP_EXP_DIR DUMPFILE=TMP1.dmp LOGFILE=imp.log PARALLEL=8 QUERY='TSHARRHB.TMP1:"WHERE TMP1.A = 2"' REMAP_TABLE=TSHARRHB.TMP1:TMP3 CONTENT=DATA_ONLY
Import: Release 11.2.0.1.0 - Production on Fri Dec 13 05:13:30 2013
Copyright (c) 1982, 2009, 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, Automatic Storage Management, 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/********@GRD6.RBSG DIRECTORY=GRDP_EXP_DIR DUMPFILE=TMP1.dmp LOGFILE=SSD_93_TABLES_FULL_EXP.log PARALLEL=8 QUERY=TSHARRHB.TMP1:"WHERE TMP1.A = 2" REMAP_TABLE=TSHARRHB.TMP1:TMP3 CONTENT=DATA_ONLY
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "TSHARRHB"."TMP3"                           5.421 KB       2 rows
Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at 05:13:33
here I am expecting only 1 record to get imported but both the records are getting imported. please advice.

The strange thing compared to your output is that I get an error when I have table prefix in the query block:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.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/******** DUMPFILE=TMP1.dmp LOGFILE=imp.log PARALLEL=8 QUERY=SYSADM.TMP1:"WHERE TMP1.A = 2" REMAP_TABLE=SYSADM.TMP1:TMP3 CONTENT=DATA_ONLY
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
ORA-31693: Table data object "SYSADM"."TMP3" failed to load/unload and is being skipped due to error:
ORA-38500: Unsupported operation: Oracle XML DB not present
Job "SYSTEM"."SYS_IMPORT_FULL_01" completed with 1 error(s) at Fri Dec 13 10:39:11 2013 elapsed 0 00:00:03
And if I remove it, it works:
Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.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/******** DUMPFILE=TMP1.dmp LOGFILE=imp.log PARALLEL=8 QUERY=SYSADM.TMP1:"WHERE A = 2" REMAP_TABLE=SYSADM.TMP1:TMP3 CONTENT=DATA_ONLY
Processing object type TABLE_EXPORT/TABLE/TABLE_DATA
. . imported "SYSADM"."TMP3"                             5.406 KB       1 out of 2 rows
Job "SYSTEM"."SYS_IMPORT_FULL_01" successfully completed at Fri Dec 13 10:36:50 2013 elapsed 0 00:00:01
Nicolas.
PS: as you can see, I'm on 11.2.0.4, I do not have 11.2.0.1 that you seem to use.

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 PM

Thanks 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?

Impdp error while attaching the job - Urgent - Prod batches are stopped

I am getting following error, when I invoke the following command.
impdp "'/ as sysdba'" attach ="SYS"."SYS_IMPORT_TABLE_01"
Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORA-39006: internal error
ORA-39065: unexpected master process exception in DISPATCH
ORA-44003: invalid SQL name
ORA-39097: Data Pump job encountered unexpected error -44003
The actual import job was stopped with stop_job in impdp> prompt.
DB Version: 10.2.0.2.
Please throw some lights to fix this issue. Production batches are already on hold. It is very urgent.

I can't remember the number of the bug sorry, but i haven't the same issue and I had to update to 10.2.0.3.0 (I opened a SR before in my previous company when i worked)

ORA-00001: unique constraint @ impdp with table_exists_action=truncate

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 Alessandro

I 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

While using data pump (impdp) how to rename references within objects?

using 10g;
what i want to accomplish is to change schema & tablespace ownership using the data pump method via the command line; i have had success using the command line for expdp / impdp. Problem is that there are objects that reference the old schemas that DO NOT get updated (e.g. procedure may reference usr1.table1 in the PL/SQL statement) and this is where i have been UN-successfull). Anyone know of a way to change references from old schema to new schama name in objects(procedures, views, etc) via the command line?
this is what i currently use that works to change schema, tablespace, but will not change references within my objects;
expdp system/<pass> schemas=usr1,usr2 DIRECTORY=dp_dir DUMPFILE=dataPump_BothSchemas.dmp LOGFILE=expdpAllSchema.log parallel=2
impdp system/<pass> DIRECTORY=dp_dir DUMPFILE=dataPump_BothSchemas.dmp LOGFILE=impbothSchToEE.log remap_schema=usr1:newUsr1,usr2:newUsr2 remap_tablespace=old_ts_tables:new_ts_tables full=y
Thanks!
p.s. I have acomplished this using the enterprise manager.

(e.g. procedure may reference usr1.table1 in the PL/SQL statement) If you hard coded such reference in stored procedure, you have to manually correct them. Consider use synonym if your storage procedure referencing other schema's objects.

Impdp fails with ORA-01427 during full import of 10.2 db into 11.2

Hello all,
I'm running a full import from a dump file taken from our production db (10.2.0.4.0) on RHEL4 into a test db (11.2.0.3.0) on RHEL6. I've done something very similar before with no errors but this time it returns the following in the output at the end of the partially successful import:
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TABLE_STATISTICS]
ORA-06502: PL/SQL: numeric or value error
LPX-00225: end-element tag "COL_STATS_ITEM" does not match start-element tag "HIVAL"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 9001
----- PL/SQL Call Stack -----
object      line object
handle    number name
0x1ea3a92c8     20462 package body SYS.KUPW$WORKER
0x1ea3a92c8      9028 package body SYS.KUPW$WORKER
0x1ea3a92c8     16665 package body SYS.KUPW$WORKER
0x1ea3a92c8      3956 package body SYS.KUPW$WORKER
0x1ea3a92c8      9725 package body SYS.KUPW$WORKER
0x1ea3a92c8      1775 package body SYS.KUPW$WORKER
0x1e9ec90f8         2 anonymous block
ORA-39097: Data Pump job encountered unexpected error -1427
ORA-39065: unexpected master process exception in DISPATCH
ORA-01427: single-row subquery returns more than one row
Job "SYSTEM"."SYS_IMPORT_FULL_02" stopped due to fatal error at 13:32:00
The import is into a database that has had all the application users dropped (only Oracle-defined users still existing) but with table_exists_action set to skip (the default). Several user objects from the source db are missing from the target.
I've run this twice with the same results. I can imagine that there is a problem with the master table and/or the data dictionary but it gives no indication of the deeper cause.
Any ideas, anyone?
Regards, Keith.

Pl post the complete expdp and impdp commands used.
Retry expdp or impdp with the EXCLUDE=STATISTICS option.
MOS Doc 878626.1
HTH
Srini

EXP/IMP..of table having LOB column to export and import using expdp/impdp

we have one table in that having colum LOB now this table LOB size is approx 550GB.
as per our knowldge LOB space can not be resused.so we have alrady rasied SR on that
we are come to clusion that we need to take backup of this table then truncate this table and then start import
we need help on bekow ponts.
1)we are taking backup with expdp using parellal parameter=4 this backup will complete sussessfully? any other parameter need to keep in expdp while takig backup.
2)once truncate done,does import will complete successfully..?
any SGA PGA or undo tablespace size or undo retention we need to increase.. to completer susecfully import? because its production Critical database?
current SGA 2GB
PGA 398MB
undo retention 1800
undo tbs 6GB
please any one give suggestion to perform activity without error...also suggest parameter need to keep during expdp/impdp
thanks an advance.

Hi,
From my experience be prepared for a long outage to do this - expdp is pretty quick at getting lobs out but very slow at getting them back in again - a lot of the speed optimizations that may datapump so excellent for normal objects are not available for lobs. You really need to test this somewhere first - can you not expdp from live and load into some test area - you don't need the whole database just the table/lob in question. You don;t want to find out after you truncate the table that its going to take 3 days to import back in....
You might want to consider DBMS_REDEFINITION instead?
Here you precreate a temporary table (with same definitiion as the existing one), load the data into it from the existing table and then do a dictionary switch to swap them over - giving you minimal downtime. I think this should work fine with LOBS at 10g but you should do some research and see if it works fine. You'll need a lot of extra tablespace (temporarily) for this approach though.
Regards,
Harry

Log file's format in expdp\impdp

Hi all,
I need to set log file format for expdp\impdp utility. I have this format for my dump file - filename=<name>%U.dmp which generates unique names for dump files. How can i generate unique names for log files? It'd better if dump file name and log file names will be the same.
Regards,
rustam_tj

Hi Srini, thanks for advice.
I read doc which you suggest me. The only thing which i found there is:
Log files and SQL files overwrite previously existing files.
So i cant keep previos log files?
My OS is HP-UX (11.3) and database version is 10.2.0.4
Regards,
rustam

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 Vadlamudi

You 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

Changing database to noarchivelog mode during impdp

Hi Guys,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production on RHEL5.
I am in the middle on the impdp and I want my database to run on noarchivelog as it creates a lot of archivelogs.
Will it be proper if I stop the import:
e.g Import> STOP_JOB=IMMEDIATE
and shutdown the database put the database on noarchivelog mode.
then opne database and
impdp hr/hr@mydb ATTACH=myfulljob Will these work fine?
Or should I execute:
alter system archive log stop;
Please Help !!!!!!!!!!!

Vinod Dhandapani wrote:
Running the database in Noarchivelog mode means you should be ready to lose data incase there is any crash. I would recommend you to change the size of the redologs so that it will not create frequent archivelogs. Which does nothing about the space required for the archivelogs. If you are generating redo at the rate of 1gb/hour, you will consume archivelog dest space at the rate of 1gb/hour. Doesn't matter if those files are 10mb each or 100mb each.
If space is the problem then use a shell script to move the archivelog to another location (Tape)....And hopefully that shell script is invoking rman to do the work, so that in the event of recovery, rman will know that backups were taken and where they are located.
>
Incase you want to convert the database from archivelog to noarchivelog, follow the steps provided in the following link.
http://racadmin.blogspot.com/2011/06/convert-archivelog-mode-to-noarchivelog.html
Thanks

Getting Errors while using IMPDP command in UNIX

Hi All,
My work involves Refreshing of DB with latest Data. For this i am using IMPDP command to import the data. But Every time during refresh i will get errors saying like "oracle Generated Errors Oracle Not available".
I don't know what is the reason for getting this error, and that too my db goes down after this error. Again i will startup the db , and i will try my luck to complete the process.
so please tell me what are the actual problems that might cause the IMPDP to be failed.
with one advise , i have stopped my listener and done the importing, Interestingly this time IMPDP works without errors. But this is also not always working.
But i feel that every time starting and stopping the listener is not the correct solution.
so please help me in this regard.
Regards
Naveen R.

The error i am getting is...
UDI-03113: operation generated ORACLE error 3113
ORA-03113: end-of-file on communication channel
Process ID: 6208
Session ID: 346 Serial number: 298
UDI-03114: operation generated ORACLE error 3114
ORA-03114: not connected to ORACLE
[user1@node1 cpt]$
DB version is 11.1.0.6.0
os is.. Red Hat Linux

Regarding IMPDP command in oracle10g 10.2.0.4.0

Hi
I am trying importing the dump file into my local system database.
While i try to issue impdp scott/owb directory=test_dir dumpfile=mca.dmp logfile=impdpmca.log
i am getting following errors and window is getting closed.
ORA-39002 Invalid operation
ORA-39070-Unable to open file
ORA-29283-Invalid file operation
ORA-06512-at "SYS.UTL_FILE"
ORA-29283 Invalid File Operation
can any one help me here ...
Regards
Rajesh

Rajesh,
Do you have permission to open file in that directory as an oracle user? It's say unable to open file, so verify directory permission. ANd if possible, please post your exact code enclosed between tag \ to preserve formatting.
\Your code
\Regards

Impdp

Similar Messages

Maybe you are looking for