In this Document
APPLIES TO:Oracle Database - Enterprise Edition - Version 10.1.0.4 to 10.2.0.3 [Release 10.1 to 10.2]Information in this document applies to any platform. ***Checked for relevance on 13-Oct-2017*** SYMPTOMSThe import log file shows the errors:
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.PUT_DDLS [TRIGGER:"APPS"."FND_PROD_LIC_TGR"]
ORA-06502: PL/SQL: numeric or value error LPX-00007: unexpected end-of-file encountered ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95 ORA-06512: at "SYS.KUPW$WORKER", line 7839 CHANGESAfter applying the interim patch for theBug 4352110 - IMPORT EXITS WITH ORA-39125 UNEXPECTED FATAL ERROR IN KUPW$WORKER.PUT_DDLS the errors continue. Note the bug has also been fixed in patch set 10.2.0.4. Please refer to: Note 4352110.8 - Bug 4352110 - ORA-39125 from expdp/impdp of triggers with nulls in WHEN clause CAUSEThe patch was not properly installed. The catmeta.sql script, as installed with the patch, needs to be run as mentioned in the Patch Readme.SOLUTION1. Check that the issue is resolved and that the patch has been properly installed.Please make sure the new catmeta.sql script is executed by running the catdph.sql script as instructed in the Patch Readme:
# Patch Special Instructions:
# --------------------------- # After the patch has been applied please reload the package/s into # the database. To do this connect as SYS and execute the following; # SQL> @?/rdbms/admin/catdph.sql # SQL> @?/rdbms/admin/catdpb.sql 2. Often the error message refers to one trigger (see the example in the reported error) that has NULL characters resolved by the bug fix. a. dbms_metadata.get_ddl package on all triggers can help show what the actual problem trigger is. b. Get the following for one of the problematic triggers:
select whenclause, dump (whenclause, 16, 1, 999)
from trigger$ where obj# = <id_of_problem_trigger>; |
No comments:
Post a Comment