IMPDP command

Hello,
Let me describe my situation here, one of my users had asked me to refresh a database with the following dumpfile bob_schema.dmp
The command he used to export the database was
expdp bob dumpfile=DATPMP1:bob_schema.dmp schemas=bob
I'm trying to import the database he provided with the command
impdp phil/password@SERVER dumpfile=bob.dmp logfile=log.txt
These are the problems I am experiencing.
ORA-39001: invalid argument value
ORA-39000: bad dump file specification
ORA-31619: invalid dump file "E:localapps\oracle\app\administrator\admin\SERVER\dpdump\bob.dmp
In this case, whenever an expdp command is used, does the impd command have to be similar?
Also, since he is specifying DATPMP1 as the directory do I need to create and specify the same name on my end? I had placed bob.dmp in the directory shown above, because any database I import is always placed within the oracle directory of dpdump. The user and I are both on oracle 11g.
Thanks,
What are your thoughts and suggestions about this problem I am encountering?

SYS
ORACLE_OCM_CONFIG_DIR
E:\localapps\oracle\app\administrator\product\11.2.0\dbhome_1/ccr/state
SYS
DATA_PUMP_DIR
E:\localapps\oracle\app\administrator\admin\SERVER\dpdump
SYS
XMLDIR
E:\localapps\oracle\app\administrator\product\11.2.0\dbhome_1\rdbms\xml
SYS
MY_DATA_PUMP_DIR
E:\localapps\oracle\app\administrator\admin\SERVER\dpdump
Problem still exists when I am specifying the MY_DATA_PUMP_DIR as a directory.

Similar Messages

  • 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

  • Errors in impdp command on oracle 10g database

    Hi,
    could you plz help me to solve below errors which are coming while doing import with impdp command in oracle 10g 10.1.0.4.0 os: Red Hat Enterprise Linux ES release 4
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    Job "DCA"."SYS_IMPORT_SCHEMA_01" stopped due to fatal error at 15:31
    i tried to restart job but the following errors coming
    UDI-00008: operation generated ORACLE error 39078
    ORA-39078: unable to dequeue message for agent KUPC$A_1_20081111155728 from queue "KUPC$C_1_20081111155728"
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 2356
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 3261
    ORA-06512: at line 1
    thanks in advance

    NAME TYPE VALUE
    streams_pool_size big integer 0
    sga_target big integer 200M
    what could be the value for avoiding errors! thanks in advance

  • Errors in impdp command on oracle 10g database-urget help needed

    Hi,
    could you plz help me to solve below errors which are coming while doing import with impdp command in oracle 10g 10.1.0.4.0 os: Red Hat Enterprise Linux ES release 4
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    Job "DCA"."SYS_IMPORT_SCHEMA_01" stopped due to fatal error at 15:31
    i tried to restart job but the following errors coming
    UDI-00008: operation generated ORACLE error 39078
    ORA-39078: unable to dequeue message for agent KUPC$A_1_20081111155728 from queue "KUPC$C_1_20081111155728"
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 2356
    ORA-06512: at "SYS.DBMS_DATAPUMP", line 3261
    ORA-06512: at line 1
    thanks in advance

    Can you check Metalink Note 376022.1? Your STREAMS_POOL_SIZE parameter may be too small.
    If you don't have Metalink access, try this :
    sql> alter system set STREAMS_POOL_SIZE=100M scope=spfile;
    sql> shutdown immediate
    sql> startup
    Note : the Portal Applications forum may not be the appropriate forum for this datapump issue. Try one of the database forums as you'll have a wider audience there.

  • Impdp command returning errors in oracle xe

    Hi All
    I am using a CentOS server with Oracle express edition installed on it .
    I tried to import a dump file with the impdp command and got following list of errors .
    ORA-39002:
    ORA-31694:
    ORA-02354:
    ORA-39776:
    ORA-12952:
    What could be the possible cause for the errors ? Any help will be appreciated .
    Regards
    V.T.

    Hi
    The errors that came were because of the exceeded size limit that is 4 GB ... The dump file is a valid data pump file and i tried importing partial dump .
    Now , i am using the following import command and am still getting some errors :
    impdp SYSTEM/oracle123456@XE DIRECTORY=dmpdir DUMPFILE=20070201.dmp LOGFILE=200702013.log EXCLUDE=STATISTICS TABLE_EXISTS_ACTION=REPLACE CONTENT=METADATA_ONLY
    Error : ORA-39083: MATERIALIZED_VIEW
    ORA-00600: [kkqfca:invalid input],[],[],[],[],[],[],[]
    CREATE MATERIALIZED VIEW "XYZ"."V_XYZ" USING ("V_XYZ", (5, 'TEST', 1, 0, "XYZ", "X_TABLE", '2007-02-01:07:00:06', 8, 55404, '2007-02-01:07:00:06', '', 1, '560001', 503331866, 0, NULL), 2101313, 7, ('1950-01-01:12:00:00', 461, 0, 0, 503331866, 0,
    what could be the cause of this error ?
    I think it is because of ORA-13011 (Perhaps some value is out of range ).
    Can't resolve this error .
    Waiting for an early response .
    Regards
    V.T.

  • Error when using IMPDP command on import

    I'm following an Oracle document guiding me thru the creation of schemas and importing of data for a Sample OBIEE App. But I'm getting an error using the IMPDP command. The command I'm issuing at the Command Prompt is as follows:
    impdp sys/password@Eagle as sysdba directory=datapumpdir dumpfile=SASchemas.dmp version=11.2.0.0.0 schemas=BISAMPLE,OBIEE_NAVTEQ,BIFOD,BIBPM,DEV_ODI_REPO,ODI_STAGING LOGFILE=SASchemas_imp.log
    (Note that I'm using my actual password in place of 'password')
    Unfortunately, I keep getting the error: unknown command beginning "impdp sys/..." rest of line ignored'
    Why is this not working? I've checked the syntax very carefully.
    Thanks, John

    Thanks for the replies. Yep it's a duplicate post, which I rarely do, but the subject matter related more to the database than OBIEE and I got no response in the OBIEE forum.
    Yes, this is a single machine installation so I am running the command on the machine where the database is up and running. I tried leaving version= 11.2.0.0 out of the command as Fiedi Z suggested, but I still get the same error. I'm scratching my head as to why the error handler doesn't even recognize that I'm using the IMPDP command. Any other ideas?
    Thanks, John

  • Error when importing Sample OBIEE Files using the IMPDP command

    I'm trying to follow the lengthy directions to create the Sample App, and I'm on page 7 of this installation guide:
    http://www.oracle.com/technetwork/middleware/bi-foundation/downloads/sampleapp107-deploymentguide-435786.pdf]description
    I've successfully completed the first 3 bullets on the page and I'm at the step of using the 'impdp' command to import data from the dmp file. The customized command I'm using is as follows:
    impdp sys/password@Eagle as sysdba directory=datapumpdir dumpfile=SASchemas.dmp version=11.2.0.0.0 schemas=BISAMPLE,OBIEE_NAVTEQ,BIFOD,BIBPM,DEV_ODI_REPO,ODI_STAGING LOGFILE=SASchemas_imp.log
    (Note that I'm using my actual password in place of 'password')
    Unfortunately, I keep getting the error: unknown command beginning "impdp sys/..." rest of line ignored'
    Why is this not working? I've checked the syntax very carefully.
    Thanks, John

    Whoops I was running this from the SQL Prompt and not the Dos Prompt... Never mind.

  • Not able to import(getting error on impdp command)

    hi,
    i have taken the export of my database db6 using below command
    expdp system/password@db6 SCHEMAS=(CODASYL,DNET,FINANCE,BILLPAY) DUMPFILE=qr_bkp_9nov.dmp DIRECTORY=qr_bkp LOGFILE=qr_bkp_9nov.log PARALLEL=4
    the dump was created success fully(i have also created the directory n given permission before executing the above command).
    now on a different server i have created the directory as below
    CREATE OR REPLACE DIRECTORY qr_bkp AS '/opt/quikremit';
    GRANT READ, WRITE ON DIRECTORY qr_bkp to HR;
    and when executing the command for import i am getting the below error.
    bash-3.00$ impdp SCHEMAS=(CODASYL,DNET,FINANCE,BILLPAY) DIRECTORY=qr_bkp DUMPFILE=qr_bkp_9nov.dmp LOGFILE=qr_bkp_9nov1.LOG PARALLEL=4
    Import: Release 10.2.0.1.0 - 64bit Production on Thursday, 10 November, 2011 13:47:37
    Copyright (c) 2003, 2005, Oracle. All rights reserved.
    Username: HR
    Password:
    Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    ORA-39002: invalid operation
    ORA-39070: Unable to open the log file.
    ORA-29283: invalid file operation
    ORA-06512: at "SYS.UTL_FILE", line 475
    ORA-29283: invalid file operation
    some one plz help????

    bash-3.00$ ls -la /opt/quikremit/
    total 2997776
    drwxrwxr-x 15 pqapp other 512 Nov 10 13:44 .
    drwxr-xr-x 15 root sys 512 Oct 24 13:18 ..
    drwxrwxr-x 13 pqapp other 1024 Nov 3 11:32 adodb
    drwxrwxr-x 17 pqapp other 512 Nov 3 12:16 apache2
    drwxrwxr-x 3 pqapp other 512 Nov 3 12:02 batch
    -rwxrwxr-x 1 pqapp other 451 Nov 3 18:21 conntest.php
    drwxrwxr-x 3 pqapp other 512 Nov 3 10:35 dev_envs
    drwxrwxr-x 12 pqapp other 1024 Oct 27 07:17 httpd-2.2.9
    drwxrwxr-x 2 pqapp other 512 Nov 3 10:20 logs
    drwxrwxr-x 2 pqapp other 512 Nov 3 10:26 mail_logs
    drwxrwxr-x 13 pqapp other 512 Oct 27 08:56 mysql-5.5.17-solaris10-sparc-64bit
    -rwxrwxr-x 1 pqapp other 1534005760 Oct 27 08:51 mysql-5.5.17-solaris10-sparc-64bit.tar
    drwxrwxr-x 3 pqapp other 512 Oct 27 09:12 mysql5.5.17
    drwxrwxr-x 23 pqapp other 2560 Nov 3 10:33 php
    drwxr-xr-x 2 pqapp other 512 Nov 10 13:44 qr_bkp
    -rw-r--r-- 1 pqapp other 66007 Nov 9 15:38 qr_bkp_9nov.log
    -rwxrwxrwx 1 pqapp other 134 Nov 10 11:46 qr_impdp.sh
    drwxrwxr-x 4 pqapp other 512 Nov 3 11:41 smarty_temp
    -rw-r--r-- 1 pqapp other 4003 Nov 10 13:32 sqlnet.log
    drwxrwxr-x 3 pqapp other 512 Nov 3 12:03 tmp

  • 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 command question

    Hi All,
    I am trying to import into and 11.2.0.2 database on Linux. I am trying to exclude 2 tables from 2 different users and exclude constrains as well. This is the syntax I have. Any help would be appreciated.
    nohup impdp bb_bb60@BB9TEST schemas=BBADMIN,BBINSTHOST,BB_BB60,BB_BB60_REPORT,BB_BB60_STATS,CMS,CMS_DOC,COURSELIFE,LCYCLE,MSC197 directory=TEST_DIR parallel=4 dumpfile=SCHEMAS_01.dmp,SCHEMAS_02.dmp,SCHEMAS_03.dmp,SCHEMAS_04.dmp logfile=impdpSCHEMAS1.log EXCLUDE=TABLE: "IN ('BB_BB60.ACTIVITY_ACCUMULATOR','BB_BB60_STATS.ACTIVITY_ACCUMULATOR')" content=DATA_ONLY &
    Thanks

    When you specify an exclude statement, it only accepts object names, not schema.object_name. So, you can't really do what you want to do. If your dumpfile had:
    user1.table1
    user1.table2
    user2.table1
    user1.table2
    You can exclude user1.tablle1 and user2.table2. You can exclude table1,table2, but you would be excluding 4 tables instead of 2.
    This is not supported.
    Dean

  • 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 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

  • ORA-39166: Object was not found in impdp

    I am trying to do an impdp to another database.
    Both databases are 11g on AIX.
    This is the command I use.
    impdp &dUSR/&dPASS@&dCONN REMAP_SCHEMA=&uUSR:&dUSR directory=DATA_PUMP_DIR dumpfile=file.dmp logfile=...log content=DATA_ONLY table_exists_action=truncate 'TABLES=(table1,table2,...)'
    &dUSR is for destination databsse.
    &uUSR is for source database.
    I am getting the following errors:
    ======================
    ORA-39166: Object TAR.TABLE1 was not found.
    ORA-39166: Object TAR.TABLE2 was not found.
    ======================
    When import command was modified (table1 -> &uUSR.table1) so it becomes:
    impdp &dUSR/&dPASS@&dCONN REMAP_SCHEMA=&uUSR:&dUSR directory=DATA_PUMP_DIR dumpfile=file.dmp logfile=...log content=DATA_ONLY table_exists_action=truncate 'TABLES=(&uUSR.table1,&uUSR.table2,...)'
    The import works. I am already using REMAP_SCHEMA so why is this necessary?

    VST,
    Expdp was done as tables=foo rather than tables=user2.foo.This means that the foo table that is in the dumpfile would have to be originally in the schema running the job. So, let's say your export was
    expdp user1/pass1 tables=foo dumpfile=mydump.dmp ...
    This means that table user1.foo would have to exist (or you would get an export error) and this table would be in the dumpfile.
    So the bottom line is to transfer between databases and schemas I need to use schema either during expdp or impdp and remap_schema is still necessary?If you want the table user1.foo to be imported into the target database, all you need to do is run either this command:
    impdp any_prived_user/password full=y dumpfile=mydump.dmp ...
    -- this would require that the user1 is already created in the target database. It will create table user1.foo
    or this command:
    impdp user1/password full=y dumpfile=mydump.dmp ...
    -- this would require that the user1 exists because you are running the job from user1.
    If you want this to go into another schema, then you will need to use remap_schema in the impdp command.
    Hppe this helps
    Dean

  • Impdp Worker unexpected fatal error KUPW$WORKER.PUT_DDLS

    I`m trying to import IMPDP, dump from (linux oracle 10.02.00.01.00) to oracle 11
    and i get :
    ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TRIGGER:"SKASUJMNIE"."ADD_BS_CM"] ]
    ORA-06502: PL/SQL: numeric or value error
    LPX-00225: end-element tag "COLS_ITEM" does not match start-element tag "BODY"
    ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
    ORA-06512: at "SYS.KUPW$WORKER", line 8164
    ----- PL/SQL Call Stack -----
    object line object
    handle number name
    0x112977a48 19028 package body SYS.KUPW$WORKER
    0x112977a48 8191 package body SYS.KUPW$WORKER
    0x112977a48 15631 package body SYS.KUPW$WORKER
    0x112977a48 3944 package body SYS.KUPW$WORKER
    0x112977a48 8874 package body SYS.KUPW$WORKER
    0x112977a48 1651 package body SYS.KUPW$WORKER
    0x11f7bee10 2 anonymous block
    it happens only where i import triggers ( include=triggers )
    file copy was made by scp (so i guess it binary mode ) , i think it occurs in metalink and it problem requires install patch.
    Is that any other way to read this trigger pl sql code from dmp file, using pl sql package or program such as awk or sed ?
    Kamila

    This looks like a corrupted dumpfile.
    From what I see in the text that you listed, DataPump import is trying to convert an xml document to ddl and LPX was looking for <BODY> and it got <COLS_ITEM>.
    LPX-00225: end-element tag "COLS_ITEM" does not match start-element tag "BODY"
    I'm not familiar with scp, but you can try this on the source.
    run the same impdp command with this:
    sqfile=my_objects.sql
    If it works then the dumpfile on the source is good. If not, then the dumpfile on the source is bad.
    Looking in the dumpfile will not help much. What you will see in there is xml and you would have to find the right xml document for the object you are looking for and then try to figure out how to convert it to ddl.
    Dean

  • Impdp import schema to different tablespace

    Hi,
    I have PRTDB1 schema in PRTDTS tablespace, I need encrypt this tablespace.
    and I have done this steps:
    1. I created new encrypted PRTDTS_ENC tablespace.
    2. I take export PRTDB1 schema. (expdp system/system schema=PRTDB1 directory=datapump dumpfile=data.dmp logfile=log1.log)
    and I want import this dump to new PRTDTS_ENC tablespace.
    can you give me impdp command, which I need?

    Hello,
    ORA-14223: Deferred segment creation is not supported for this table
    Failing sql is:
    CREATE TABLE "PRTDB1"."DATRE_CONT" ("BRON" NUMBER NOT NULL ENABLE, "PCDID" NUMBER(9,0) NOT NULL ENABLE, "OWNERSID" NUMBER NOT NULL ENABLE, "VALUESTR" VARCHAR2(4000 CHAR), "VALNUM" NUMBER, "VALDATE" DATE, "VALXML" "XMLTYPE") SEGMENT CREATION DEFERRED PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING So it means that these Tables "need" a Segment but, they are created with the option SEGMENT CREATION DEFERRED.
    A workaround is to create a Segment for these Tables on the Source Database before exporting them. Then, at the Import you won't have the option SEGMENT CREATION DEFERRED. The following Note of MOS detail this Solution:
    - *Error Ora-14223 Deferred Segment Creation Is Not Supported For This Table During Datapump Import [ID 1293326.1]*
    The link below gives more informations about the DEFERRED SEGMENT CREATION:
    http://docs.oracle.com/cd/E14072_01/server.112/e10595/tables002.htm#CHDGJAGB
    With the DEFERRED SEGMENT CREATION feature, a Segment is created automatically at the first insert on the Table. So the Tables for which the error ORA-14223 occurs are empty.
    You may also create them separately by using a script generated by the SQLFILE parameter in which you change the option SEGMENT CREATION DEFERRED by SEGMENT CREATION IMMEDIATE.
    Hope this help.
    Best regards,
    Jean-Valentin

Maybe you are looking for

  • HT204053 Using IOS apple id to purchase in Mac Store

    I have apple id which I am using on developer account for ios. Can I use the same to purchase Mac software such as Final cut pro? Thanks

  • Waiting for printer to become available

    I'm on OS X 10.8.5, and have a USB printer: HP p4015dn.   It used to work fine to print.  All of a sudden, it shows "Waiting for printer to become available", forever, and will not print. I can successfully print to networked HP printers, but even th

  • Promoting These for Academics

    I am a graduate student and teacher and have thousands of PDFs to read each semester for my classes and research. I looked into every eReader on the market for months before buying a Sony PRS900 (I would have gone with the 950, but couldn't fund the

  • How to dynamically call a Taskflow

    Hi All, We have a task flow say "CreateA". When the parameters are passed to this task flow, it will create some document. Now, this taskflow can be consumed by many teams i.e., when user clicks on "Add" button in the consumer page, this taskflow sho

  • Forcing a "Save As"/"Export" Command

    Hey guys and gals, Is there a Terminal command that you can use to force any given app to "Save As" or "Export", such as a sudo command? Thanks, -Preston