11i Payments Patch 4607647 Fails With Error ' FAILED: file ibysecop.ldt on worker 1 for product iby username APPS' And 'ORA-06550: line 164, column 32: PL/SQL: ORA-00904: "SUBKEY_AGE_MAXIMUM": invalid identifier' (Doc ID 2231070.1)

Last updated on FEBRUARY 14, 2017

Applies to:

Oracle Payments - Version 11.5.10.2 and later
Information in this document applies to any platform.

Symptoms

E-Business Suite 11.5.10.2 Payments, Patch Application Issues

 



<Patch 4607647> fails during adpatch installation on 11i E-Business Suite applications with the errors listed below:


  FAILED: file ibysecop.ldt on worker 1 for product iby username APPS.
ATTENTION: All workers either have failed or are waiting:
  FAILED: file ibysecop.ldt on worker 1.
ATTENTION: Please fix the above failed worker(s) so the manager can continue.


**********************************************************
Current system time is Tue Jan 17 07:44:05 2017


Uploading from the data file /u01/app/TEST2/test2appl/iby/11.5.0/patch/115/import/US/ibysecop.ldt
Altering database NLS_LANGUAGE environment to AMERICAN
Dumping from LCT/LDT files (/u01/app/TEST2/test2appl/iby/11.5.0/patch/115/import/ibyasec.lct(115.4), /u01/app/TEST2/test2appl/iby/11.5.0/patch/115/import/US/ibysecop.ldt) to staging tables
Dumping LCT file /u01/app/TEST2/test2appl/iby/11.5.0/patch/115/import/ibyasec.lct(115.4) into FND_SEED_STAGE_CONFIG
Dumping LDT file /u01/app/TEST2/test2appl/iby/11.5.0/patch/115/import/US/ibysecop.ldt into FND_SEED_STAGE_ENTITY
Dumped the batch (IBY_SEC_OPTIONS 1 , IBY_SEC_OPTIONS 1 ) into FND_SEED_STAGE_ENTITY
Uploading from staging tables
 Error during uploading. ORA-06550: line 164, column 32:
PL/SQL: ORA-00904: "SUBKEY_AGE_MAXIMUM": invalid identifier
ORA-06550: line 160, column 5:
PL/SQL: SQL Statement ignored
ORA-06550: line 177, column 8:
PL/SQL: ORA-00904: "SUBKEY_AGE_MAXIMUM": invalid identifier
ORA-06550: line 173, column 7:
PL/SQL: SQL Statement ignored


Concurrent request completed
Current system time is Tue Jan 17 07:44:05 2017

************************************************************


The issue can be reproduced at will with the following steps:
1. Apply patch 4607647.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms