AutoPatch error: Missing file format id in file applcust.txt

APPLIES TO:

Oracle Order Management - Version 12.1.2 and later
Information in this document applies to any platform.

SYMPTOMS

On :  12.1.2 version, Install / Upgrade

When attempting to apply OM Patch 10087292:R12.ONT.B per Note 1195450.1 Error In Sales Order Form OEXOEORD: Please Choose An Existing Combination, the following error occurs.

NOTE: this error can happen with any patch or product and is not specific to OM.

ERROR
-----------------------
Getting error when applying the patch:
STRT_TASK: [Display customized files] [] [Fri Oct 01 2010 19:06:38]

Reading customized files list (if any)...

AutoPatch error:
:
Missing file format id in file
/u01/appldev/DEV/apps/apps_st/appl/admin/applcust.txt

This version of AutoPatch requires a file format id
on the first line of the file.

Error reading customized files file
Freeing includes hash table
Freeing fixes hash table
Freeing basedons hash table
Freeing entities hash table

You should check the file
/u01/appldev/DEV/apps/apps_st/appl/admin/DEV/log/u10087292.log
for errors.,

NOTE: the log file will vary per customer and instance.  This is only an example shown above.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Apply patch with AutoPatch
2. Receive error:
Missing file format id in file applcust.txt
This version of AutoPatch requires a file format id on the first line
of the file.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot apply the patch without error.

CAUSE

The applcust.txt file is not used in R12i, and has been replaced by registering
any customized files in the Register Flagged Files tool in Oracle Applications
Manager (OAM).

SOLUTION

To implement the solution, please execute the following steps:

1. Rename the applcust.txt file :

  mv applcust.txt  applcust_BAK.txt

2. If there are no custom files:
  a) Try to re-apply the patch at this time, and report any errors/logs back to us.

3. If there are custom files:
 a) refer to Note 459156.1 "Oracle Applications Patching FAQ for Release 12" FAQ section "How can I track my customizations? What happens to my customizations during patching?"

This will direct you to follow the procedure outlined in the document titled:
"Oracle Applications Patching Procedures Release 12.1 part No E12148-02"
      section "Register Flagged Files".

 Note: Registering customized files does not prevent the object or the patch from being applied. It only makes them available to AutoPatch for review.

  b) Try to re-apply the patch at this time, and report any errors/logs back to us.


4. Retest the issue.

5. Migrate the solution as appropriate to other environments.

MOS Doc ID 1227113.1