txkADOPValidations.error while Running fs_clone

Fs_clone fails with the following error:

Validating configuration on node: [tst-ebs021].
Log: /u01/app/ebstst/fs_ne/EBSapps/log/adop/129/20210205_003039/fs_clone/validate/tst-ebs021
[UNEXPECTED]Error occurred running “perl /u01/app/ebstst/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPValidations.pl -contextfile=/u01/app/ebstst/fs2/inst/apps/TEST_tst-ebs021/appl/admin/TEST_tst-ebs021.xml -patchctxfile=/u01/app/ebstst/fs1/inst/apps/TEST_tst-ebs021/appl/admin/TEST_tst-ebs021.xml -phase=fs_clone -logloc=/u01/app/ebstst/fs_ne/EBSapps/log/adop/129/20210205_003039/fs_clone/validate/tst-ebs021 -promptmsg=hide”
[UNEXPECTED]Error 1 occurred while Executing txkADOPValidation script on tst-ebs021

 

/u01/app/ebstst/fs_ne/EBSapps/log/adop/129/20210205_003039/fs_clone/validate/tst-ebs021/txkADOPValidations.error

Cause:

Patch context file is missing in the FND_OAM_CONTEXT_FILES table. Line 1291 of ADOPValidationUtils.pm line (see error below) is expecting the full path of CONTEXT_FILE name from the patch file system. However, the command returns no results.

Solution:

If you run the following query it should return no rows:

select distinct(PATH) from FND_OAM_CONTEXT_FILES where NAME not in (‘TEMPLATE’,’METADATA’,’config.txt’) and CTX_TYPE=’A’ and (status is null or upper(status) in (‘S’,’F’)) and EXTRACTVALUE(XMLType(TEXT),’//file_edition_type’) = ‘patch’;

Having no rows returned to the query is a SYMPTOM, not a CAUSE of the issue. The symptom is there are no rows returned when running the query.

To fix this issue test the following to upload the missing PATCH context file to the database:

1. Get the value of your patch context file.

1.1. Source your PATCH file system

1.2. Echo the value of $CONTEXT_FILE and take note of it. You will use this value in step #3.

2. Source the RUN filesystem.

3. On the master node, execute the following command on the run filesystem to upload the patch context file to the database.

Example:

[TEST]_[run]$ . /u01/app/ebstst/EBSapps.env patch

E-Business Suite Environment Information
—————————————-
RUN File System : /u01/app/ebstst/fs2/EBSapps/appl
PATCH File System : /u01/app/ebstst/fs1/EBSapps/appl
Non-Editioned File System : /u01/app/ebstst/fs_ne

 

DB Host: prd2dbadm03.ohdc.com Service/SID: TEST

 

Sourcing the PATCH File System …

ebstst@tst-ebs021:/rhome/ebstst
[TEST]_[patch]$ echo $CONTEXT_FILE
/u01/app/ebstst/fs1/inst/apps/TEST_tst-ebs021/appl/admin/TEST_tst-ebs021.xml
ebstst@tst-ebs021:/rhome/ebstst
[TEST]_[patch]$

Source the RUN File System and run the below.

[TEST]_[run]$ $ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer \
> action=upload \
> contextfile=/u01/app/ebstst/fs1/inst/apps/TEST_tst-ebs021/appl/admin/TEST_tst-ebs021.xml \
> logfile=/tmp/patchctxupload.log
Enter the APPS password:
ebstst@tst-ebs021:/rhome/ebstst

4. Run the following query and it should return one entry for the recently uploaded context file.

select distinct(PATH) from FND_OAM_CONTEXT_FILES where NAME not in (‘TEMPLATE’,’METADATA’,’config.txt’) and CTX_TYPE=’A’ and (status is null or upper(status) in (‘S’,’F’)) and EXTRACTVALUE(XMLType(TEXT),’//file_edition_type’) = ‘patch’;

 

Recent Posts