adsplice errors

[ali evrim]

Hi,

I am getting an error when add a custom top  for XXTKB  

SQL Command: SELECT status||',' FROM ad_adop_session_patches WHERE node_name = 'erpprod' AND applied_file_system_base = '/apps/fs2' AND patch_file_system_base IS NULL AND bug_number = 'ADSPLICE_xxtkb' ORDER BY TO_CHAR(end_date,'YYYY.MM.DD:HH24:MI:SS') DESC
patch_status = Y,Y,Y
STATUS has MULTIPLE VALUES. Picking up the latest value.
Updated patch_status = Y
EXIT STATUS: 1
=============================
Inside evalADPATCHStatus()...
=============================
message_status: ERROR
Adsplice action did not go through successfully.
*******FATAL ERROR*******
PROGRAM : (/apps/fs2/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl)


Result of the above select :

STATUS
Y,
Y,
Y,
Y,




Also :

select ORACLE_ID from FND_ORACLE_USERID where oracle_username like '%XXTKB%'
13555

select application_id from fnd_application where application_short_name = 'XXTKB';
13355

select * from fnd_product_installations where oracle_id=13555
application_id  oracle_id
    13355     13555
    13555   13555
    50017   13555

Different three values for oracle_id 13555

Please help me!!!!

[ErmanArslansOracleBlog]

what is written in the log of lastly executed perl script ? (pl)
 

[ErmanArslansOracleBlog]

I didnt hear back from you.
you know what..
just backup the relevant tables and delete the unnecessary rows for the repeating application declaration..
Thus you will have 1 row for the custom app.
Once you delete te unnecessary rows, retry the operation

[Eren]

hi erman ,
custom top issue was solved.
we deleted the duplicate fnd_application_tl row about custom schema error,
and solved.
ty for yor assistance

[Eren]

Erman sorry i forgot ,
This issue not solved with that ,
I solved this with skipsyncerror=YES parameter,
this parameter is not sync previous fail patch cycle
This is the oracle doc;

In some circumstances, the delta-style (incremental) synchronization method may
fail when applying a series of patches to the patch edition. This can happen if the
previous patching cycle included patches that failed to apply correctly, and was
followed by subsequent patches that corrected the issue.
The skipsyncerror parameter enables you to specify that you expect any
synchronization errors in the prepare phase to be fixed automatically in the
synchronization that takes place with subsequent patches.
If the value of the parameter is passed as 'yes', the first patch to be synchronized
will be done with the 'autoskip' flag set.
Important: It is your responsibility to check the log files and correct
any errors in the subsequent apply phase, or to confirm that
synchronization with subsequent patches resolved the issue

1. You run adop phase=prepare.
2. The phase fails with an error when trying to synchronize the run and patch file
systems. That is, the attempt to synchronize a patch fails, but it is known that a
subsequent patch will correct the problem.
3. You examine the log files and conclude that the synchronization errors will be
fixed automatically in the synchronization that takes place with subsequent
patches.
4. You run the command adop phase=prepare skipsyncerror=yes to
restart the prepare phase. This time, application of the patch that failed in the
previous prepare will be retried with the 'autoskip' flag set.
Alternatively, if you are not confident that the error will be fixed (for example, you
cannot identify the cause from examination of the log files), you should:
1. Run the command adop phase=abort
2. Run the command adop phase=fs_clone

if you wonder,
https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm
https://docs.oracle.com/cd/E26401_01/doc.122/e22954.pdf

[ErmanArslansOracleBlog]

In prepare phase; txkADOPPreparePhaseSynchronize.pl is executed to synchronize the patches applied to the run appltop. This scripts look to the adop repository for the patches that applied on the Run APPL_TOP.

I already recorded this error. The following action plan may fix your problems if you have an incorrectly added custom top in your environment.


SQL Command: SELECT status||',' FROM ad_adop_session_patches WHERE node_name = 'erptest' AND applied_file_system_base = '/u01/oracle/TEST/fs1' AND patch_file_system_base IS NULL AND bug_number = 'ADSPLICE_YOURCUSTOMTOP' ORDER BY TO_CHAR(end_date,'YYYY.MM.DD:HH24:MI:SS') DESC
patch_status = Y
Updated patch_status = Y
EXIT STATUS: 1

This is actually a little different from yours, as there is only one custom top is returned by the query, but the solution will be te same.

Solution: This is because of an erroneous Custom top adding operation .. There is an improper Custom top definition in the System .
1)Remove the following entries from the adxmlctx.tmp file:
<oa_customized>
<c_fss oa_var="c_fss" scope="CUSTOM" oa_type="PROD_TOP" oa_enabled="FALSE" default="/u01/sim2/fs1/EBSapps/appl">%c_fss%</c_fss>
</oa_customized>
</oa_context> 
2. Run autoconfig .
3. Re-run fs_clone.

[ErmanArslansOracleBlog]

I will update this issue, as I have news.

In this kind of error, it is always good to review adsplice log.

It is located in the patch environment file system :
For ex: /u01/oracle/TEST/fs1/EBSapps/appl/admin/TEST_patch/log/adsplice.log

It says the actual problem:

For example: It says:
Issues :

1. The file xxefaprod.txt is found but corrupted.
The format of <APPL_TOP>/admin/<prod>prod.txt is :

%%% Single-product product data file format 12.0.A
<application shortname in lowercase> <application id>
END_OF_PRODUCT_ABBREVIATIONS   -999
<application id> <application shortname in lowercase> <application shortname in uppercase> APP
No No No No
Yes Yes
<oracle id> <oracle schema name in uppercase> <default product schema password>
0
1.0.0 1.0.0
none
none
none
none
END_OF_PRODUCTS
Release 12.0.0
12.0.0
R120 R120_ additional-this-mpl
<application shortname in uppercase> 12.0.0
END_OF_RELEASE  0.0.0

[ErmanArslansOracleBlog]

Yes, tested & verified .. The action plan in my last update fixes this issue..