My Oracle Support Banner

Context Files Are Out Of Sync Resulting in: "ERROR: Context Value Management Failed" and "java.lang.Exception:" (Doc ID 463895.1)

Last updated on JANUARY 08, 2018

Applies to:

Oracle Applications Manager - Version to [Release 11.5.10]
Oracle E-Business Suite Technology Stack - Version to [Release 11.5.10]
Information in this document applies to any platform.


Symptom #1:

Looking in Oracle Application Manager (OAM), it shows that the context files are not synchronized for a particular node.

NOTE: Each Context File is stored in the file system and also in the "FND_OAM_CONTEXT_FILES" table. These Context Files should always be synchronized, when they do not match the following problem may occur.

Symptom #2:

When running Autoconfig, it fails with:


File system template : /ebs_prod/prd/appltier/prdappl/ad/11.5.0/admin/template/adxmlctx.tmp

Checking for customizations to Context template
Customizations found : None

File system Context file :/xxxx/prd/appltier/prdappl/admin/PROD_apps101.xml

Checking the Context file for possible updates from the Database
Comparing the Context file stored in database with the Context file in the
file system

Result : File system Context is below par with respect to the data base Context

Action to be taken : Copy the Data Base Context onto the file system
Result : Download of Context file failed

java.lang.Exception: java.lang.Exception:
FsCtxFileException: End tag does not match start tag 'oa_htmlbin'.

ERROR: Context Value Management Failed.
. . .

Symptom #3:

Autoconfig may run fine on some nodes and fail with the above error on others.


There are no specific changes known to cause this issue.


To view full details, 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 a vibrant support community of peers and Oracle experts.