12.2 Application Manager Rapid Clone Users Report Issues After Fs_clone As The FORMS_TMPDIR Is Incorrect And Has Been Synced to The Same Value as RUN File System
(Doc ID 2346691.1)
Last updated on FEBRUARY 07, 2019
Applies to:Oracle Applications DBA - Version 12.2 and later
Oracle Applications Manager - Version 12.2 and later
Information in this document applies to any platform.
E-Business Suite 12.2 Applications Manager, Rapid Clone related issues
After setting the forms_tmpdir from /tmp (default value) to an fs1/fs2 dependent value (e.g. $INST_TOP/appltmp) via OAM, after fs_clone or adop prepare which calls fs_clone, the newly created PATCH context file has the forms_tmpdir value synced from the RUN FS, which causes a cross reference error:
ERROR: File - <install directory>/apps/fs1/inst/apps/<SID>_<host>/appl/admin/<SID>_<host>.xml contains cross reference in it.
Corrective Action: Contact Oracle Support to identify the best course of action.
[ERROR]: There are some cross references between the RUN and PATCH file system in FS config files.
The issue is similar to the case reported in the following document:
12.2 - Patching ADOP Cutover Phase Fails with Error "ERROR: File - <installdirectory>/apps/fs1/inst/apps/<SID>_<host>/appl/admin/<SID>_<host>.xml contains cross reference in it" (Doc ID 2099179.1)
The issue could be reproduced by the following steps
Edit the forms_tmpdir from /tmp (default value) to a special value which is an fs1/fs2 dependent value, e.g. $INST_TOP/appltmp.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document