r12.2

[satish]

Hi Erman,

i have created a custom env(customSAREAPP_EBSTEST.env) file in run appl_top.I have ran fsclone but the file is not copied to patch filesystem.can you please update what would happen in my case

Run fs

[appldev@erpdevelopment appl]$ cd /u01/SAREAPP/fs1/EBSapps/appl
[appldev@erpdevelopment appl]$ ls -lrt *.env
-rwxr-xr-x. 1 appldev dba   126 Oct  9 09:20 customSAREAPP_EBSTEST.env--file which i created
-rw-r--r--. 1 appldev dba 19136 Oct  9 09:22 SAREAPP_EBSTEST.env
-rw-r--r--. 1 appldev dba  1521 Oct  9 09:30 APPSSAREAPP_EBSTEST.env
[appldev@erpdevelopment appl]$

ran fsclone but the file was not synced

Thanks

[Sri]

Hi Erman,

I have created some sample files under run appl top and ran fsclone again and i am able to see all the files in patch appl top except this file custom<context_name>.env

will fsclone not copy the file starting with custom or custom environment file,please advice

[ErmanArslansOracleBlog]

Yes it seems normal. (fs_clone recreates the APPL_TOP in a way that makes your custom env to be removed.)

For making custom env persistent accross fs_clone  ->you have 2 options:

1)using adop_sync.drv file as per the steps in 1577661.1. (for specifically custom env file)
2)create the custom env file in $INST_TOP/appl/admin directory of both RUN and PATCH file systems. After that, set your s_custom_file variable to this file.  (fs_clone doesn't touch the inst_top)

This is already answered in Oracle Community.

[Sri]

Thank you very much for your help..appreciate all your efforts

[satish]

Hi erman,

you said fsclone will not touch inst top
if i lost my inst top in patch filesystem and if run fsclone from runfile system,then this will recreate the inst top in patch file system right?

That means fsclone will also take care of inst top,can you suggest

[ErmanArslansOracleBlog]

I said -> create the custom env file in $INST_TOP/appl/admin directory of both RUN and PATCH file systems.
"both", don't be dependent on fs_clone on this.

[ErmanArslansOracleBlog]

Oracle says:

If you need a custom environment file, you must create it in the <INST_TOP>/appl/admin directory of both run and patch file systems, and amend the s_custom_file context variable to point to it. This is because a custom environment file may contain absolute paths with respect to one file system, which are not valid for the other file system. So a custom environment file copied from the run to the patch file system may not be valid in the patch file system, and vice versa.

[satish]

thanks erman,got the answer in detail.thanks again