When Registering E-Business Suite R12 With OID Using The Automated EAGProvision Mode Of Script TXKRUN.pl The DBC File Is Generated with an Incorrect Name

(Doc ID 2159739.1)

Last updated on MARCH 16, 2017

Applies to:

Oracle E-Business Suite Technology Stack - Version 12.1.3 and later
Information in this document applies to any platform.

Goal

E-Business Suite R12 Applications Technology Stack, OID, SSO, Oracle Access Manager (OAM) issues

 

 


When registering OID the Txkrun.pl EAGProvision option creates an improperly named DBC file.



The automated EAGProvision mode of the TXKRUN tool creates an improperly named DBC file which the subsequent registration steps cannot locate resulting in the below failure:

Validation: Success
Creating Desktop DBC File...
*** Log File =
/u01/app/R12/dev1/inst/apps/dev1/logs/appl/TXK/txkProvisionEAG_generateDesktopDBCFile_Fri_Apr_22_20_36_03_2016.xml
Successfully created /home/apdev1/dev1_BALANCE_HOST.dbc desktop dbc file
Updating plan.xml file...

Errors encountered running /u01/app/R12/dev1/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkProvisionEAG.pl
*******FATAL ERROR*******
PROGRAM : /u01/app/R12/dev1/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkProvisionEAG.pl
(/u01/app/R12/dev1/apps/apps_st/appl/fnd/12.0.0/bin/txkrun.pl)
TIME : Fri Apr 22 20:38:32 2016
FUNCTION: TXK::IO::open [ Level 3 ]
MESSAGES:
error = Unable to open file
errorno = No such file or directory
file = ===================
The above output and log file state that the desktop dbc file {sid}_BALANCE_{target}.dbc was created, however the file actually created is {sid}_{target}.dbc.

The incorrectly named file then causes the script to fail.

A workaround is to create a softlink from the {sid}_{target}.dbc to {sid}_BALANCE_{target}.dbc.

Do not simply copy the file.

Each time the txkrun.pl script is run a new SERVER_ID value is generated which overwrites the DBC file.

A mismatch can result which will prevent the WebLogic Server from creating / starting the Data Source required by the EBS AccessGate.

The following versions were involved for the above case, but could occur for other versions also:

EBS 12.1.3
OAM 11.1.2.3.5
EAG 1.2.3.4
OID 11.1.1.9.2

Solution

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