Re: impdp using network_link fails with ORA-39126: KUPW$WORKER.LOOK_FOR_OBJECT [PROCACT_SCHEMA:"ABC"
- From: Andy Klock <andy@xxxxxxxxxxxxxxx>
- To: Sarabjit_Toor@xxxxxxxxxxxxxx
- Date: Mon, 19 Jul 2010 14:25:51 -0400
Is ABC identical in both schemas?
"ORA-00932: inconsistent datatypes: expected UDT got CHAR"
From the error, it doesn't look like it.
On Mon, Jul 19, 2010 at 2:18 PM, <Sarabjit_Toor@xxxxxxxxxxxxxx> wrote:
>
> Hi All,
>
> I am having strange issue with importing schemas across a network link
> using impdp. Both source and target are on 11.1.0.7 . This process was
> working fine till a few weeks ago. The user running the impdp has dba access
> on both source and target databases. If I run the expdp job locally on the
> source database with same exclude commands it finishes without any errors.My
> par file has some exclude commands as following.
>
> DIRECTORY=DATA_PUMP_DIR
> SCHEMAS=ABC
> EXCLUDE=TABLE:"IN (SELECT TABLE_NAME FROM DBO.IMPDB_EXC_TAB where
> OWNER='ABC')"
> EXCLUDE=REF_CONSTRAINT
> EXCLUDE=MATERIALIZED_VIEW , MATERIALIZED_VIEW_LOG,VIEW,SEQUENCE
> EXCLUDE=PROCEDURE, TRIGGER, FUNCTION
> TABLE_EXISTS_ACTION=REPLACE
> LOGFILE=imp_app_exc_daily.log
> NETWORK_LINK=BBBQA1.XXX.CA
> JOB_NAME=IMP_DAILY_JOB
> FLASHBACK_TIME="TO_TIMESTAMP(TO_CHAR(SYSDATE,'YYYY-MM-DD
> HH24:MI:SS'),'YYYY-MM-DD HH24:MI:SS')"
>
> The import fails with the following error:
>
> Processing object type SCHEMA_EXPORT/USER
> ORA-31684: Object type USER:"ABC" 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
> ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA
> [PROCACT_SCHEMA:"ABC"]
> ORA-00932: inconsistent datatypes: expected UDT got CHAR
> ORA-06512: at "SYS.DBMS_METADATA", line 1965
> ORA-06512: at "SYS.DBMS_METADATA", line 2008
> ORA-06512: at "SYS.DBMS_METADATA", line 2314
> ORA-06512: at "SYS.DBMS_METADATA", line 4408
>
> ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
> ORA-06512: at "SYS.KUPW$WORKER", line 7839
>
> ----- PL/SQL Call Stack -----
> object line object
> handle number name
> 700000061cde628 18237 package body SYS.KUPW$WORKER
> 700000061cde628 7866 package body SYS.KUPW$WORKER
> 700000061cde628 2744 package body SYS.KUPW$WORKER
> 700000061cde628 8504 package body SYS.KUPW$WORKER
> 700000061cde628 1545 package body SYS.KUPW$WORKER
> 700000064333df8 2 anonymous block
>
> ORA-39126: Worker unexpected fatal error in KUPW$WORKER.LOOK_FOR_OBJECT
> [PROCACT_SCHEMA:"ABC"]
> SELECT process_order, duplicate, completion_time, in_progress FROM
> "DBO"."IMP_XXX_DAILY_JOB" WHERE partition_name IS NULL AND
> subpartition_name IS NULL AND object_type = :1 AND object_schema = :2 AND
> object_name IS NULL AND :3 IS NULL AND object_long_name IS NULL AND :4 IS
> NULL AND base_object_type IS NULL AND :5 IS NULL AND base_object_schema IS
> NULL AND :6 IS NULL AND base_object_name IS NULL AND :7 IS NULL AND grantor
> = :8
> ORA-01422: exact fetch returns more than requested number of rows
>
> ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
> ORA-06512: at "SYS.KUPW$WORKER", line 7845
>
> Any input will be appreciated.
>
>
> Thanks,
>
> Sarabjit Toor
>
>
>
>
> Please consider the environment before printing this email
>
> This message, including any attached documents, is intended for the
> addressees only. It may contain information that is confidential, privileged
> and/or exempt from disclosure. No rights to privilege or confidentiality
> have been waived. Any unauthorized use or disclosure is prohibited. If you
> have received this message in error, please reply to the sender by e-mail
> and delete or destroy all copies of this message.
>
> Avant d'imprimer ce courriel, pensez à l'environnement
>
> Ce message, incluant tous les documents joints, est à l'intention des
> destinataires visés seulement. Il peut contenir des renseignements
> confidentiels, protégés et/ou ne pouvant pas être divulgués. Aucune
> renonciation n'est faite quant à sa nature confidentielle et privilégiée.
> Par conséquent, toute diffusion ou utilisation non autorisée est strictement
> interdite. Si vous avez reçu ce message par erreur, veuillez en aviser
> immédiatement l’expéditeur par retour de courriel et en détruire toutes les
> copies existantes.
>
>
>
>
>
Other related posts:
