=========
Each time AutoConfig contextfile is amended and Autoconfig is run the changes made to the Contextfile are not implemented in the instance and the changed values in the Contextfile revert to their previous values.
Cause
========
Each Contextfile version has a serial number given in the parameter:
When autoconfig is run, this serial number is written to the table: FND_OAM_CONTEXT_FILES against the version of the Context file:
For example for a Context file containing the following information:
-
However it is possible that the Apps Tier Contextfile serial number can become unsynchronised with the serial number information in the table.If the serial number in the filesystem reads a lower value compared with that showing in the table for the same contextfile version, then each time Autoconfig is run, AutoConfig will see that the table is showing the higher value and it will replace the Contextfile in the filesystem with the parameter values from the contextfile associated with the serial number in the table. This results in any changes made to the filesystem Contextfile being ignored.
The adconfig log file will show the following:
---------------------------------------------------------------- File system Context file :/u11/app/
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 : Context file successfully copied
Solution1. Manually change the serial number parameter "s_contextserial" in the Apps Tier Contextfile on the Filesystem to a value which is one more than the highest version of the serial number in the FND_OAM_CONTEXT_FILES table, for the relative Contextfile version. 2. Run AutoConfig.
