ACMP Custom NLS Patch Deployment Failed because Custom Patch (in Base Language US) is Not Detected as "Applied" (Doc ID 1957306.1)

Last updated on FEBRUARY 27, 2015

Applies to:

Application Management Pack for Oracle E-Business Suite - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

ACMP fails when applying NLS patches despite the Base Language custom patch (in this case US) having apparently been applied successfully.   This would also apply to any customer with a Base Language other than US (for example FRC) that would have applied the custom base patch and then is trying to apply the other NLS languages for the same patch.

For example: applying custom patch in other NLS languages after having applied the custom patch in the base language (US in this case) will give an error:

LOG : Command result:   Patch 100000001033:CS is a NLS patch.
LOG : Command result:   You must first apply the corresponding US patch     <<< because US was the base language for this customer; this would apply to any base language
LOG : Command result:   for the NLS patch(es) listed above.
LOG : Command result: AutoPatch error:
LOG : Command result: A fatal error related to codelines or codelevels has occurred.

Reviewing the log we can find the following error the NLS custom patch 100000001033  in CS language.

For the Current View:
  l_appl_top_id .............. 196
  l_eav_patch_release_name ... 12.0.0
Current View - 100000001033:CS is NOT_APPLIED
Comprising patches - 100000001033:US is NOT_APPLIED
Current View - 100000001033:US is NOT_APPLIED
Current View - 100000001033:US is NOT_APPLIED
 Patch 100000001033:CS is a NLS patch.

 One must first apply the corresponding US patch for the NLS patch(es) listed above.

 

The base language custom patch (US in this case) is found in AD_BUGS, but the following code used by AD module cannot find it.

SQL> select AD_PATCH.is_patch_applied('12.0.0',196,'100000001033') from dual;              <<<< this might not work for custom patches as they are not generated by ARU

AD_PATCH.IS_PATCH_APPLIED('12.0.0',196,'100000001033')
--------------------------------------------------------------------------------
NOT_APPLIED

SQL> select AD_PATCH.is_patch_applied('R12',196,'100000001033') from dual;

AD_PATCH.IS_PATCH_APPLIED('R12',196,'100000001033')
--------------------------------------------------------------------------------
NOT_APPLIED

SQL> select BUG_NUMBER,LAST_UPDATE_DATE from ad_bugs where BUG_NUMBER=100000001033;

BUG_NUMBER                     LAST_UPDATE_DATE
------------------------------ ------------------
100000001033                   15-DEC-14

 

One has already validated that AD_PATCH package is the right version by identifying <Note 1227373.1> - "You Must First Apply The Corresponding US Patch" Error When Applying NLS Patch 6678700 and the AD_PATCH package Headers in the EBS database showed the minimum versions or higher:

/* $Header: adphpchs.pls 120.5 2007/12/14 13:09:13 diverma ship $ */
/* $Header: adphpchb.pls 120.10 2007/12/14 13:09:05 diverma ship $ */

Changes

A custom patch in the base language has been created using ACMP Patch Manager.  The custom patch was created in the base language (US) then translated in other NLS languages.  The custom base language patch (US) was applied using Customization Manager.   When the NLS custom translation patches were selected (including CS) to be applied in Customization Manager after the custom base language (US) had been successfully applied, an error was wrongly reported in ACMP that the base language custom patch (US) had not been applied yet.

 

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