Below are some of the important Operating system level environment variables related to R12.2.
$ echo $FILE_EDITION
<shows which file edition you are using, run or patch>
$ echo $RUN_BASE
<shows absolute path to run file system>
$ echo $PATCH_BASE
<shows absolute path to patch file system>
$ echo $NE_BASE
<shows absolute path to non-edition file system>
$ echo $APPL_TOP_NE
<non-editioned appl_top path. Equivalent to $NE_BASE/EBSapps/appl>
$ echo $LOG_HOME
<Application Instance Specific Log Directory>
$ echo $ADOP_LOG_HOME
<Online patching Specific Log Directory. Equivalent to $NE_BASE/EBSapps/log/adop>
$ echo $IAS_ORACLE_HOME
<FMW Web Tier Home Directory>
$ echo $ORACLE_HOME
< 10.1.2 ORACLE_HOME>
$ echo $CONTEXT_FILE
<Source for information populating template files (autoconfig)>
$ echo $EBS_DOMAIN_HOME
<WLS Deployment of Oracle E-Business Suite 12.2 Domain (instance specific)>
$ echo $ADMIN_SCRIPTS_HOME
<Shell scripts to control processes associated to the Applications Instance>
$ echo $EBS_ORACLE_HOME
<Oracle E-Business Suite 12.2 FMW Deployment directory>
$ echo $RW
<10.1.2 reports directory>
$ echo $HOSTNAME
<hostname without domain name>
$ echo $APPS_VERSION
<to get the EBS version>
And the most important part is for setting up the right environment don’t directly hard code the RUN environemnt .env file in the .profile of OS user as online patching switches the filesystem from RUN to PATCH and vice versa and it can really create confusion.
Instead use EBSapps.env environment file (created under BASE directory) with ‘RUN’ as argument. It will automatically find which file system (fs1 or fs2) is currently RUN file system and lay out the correct environment.
For example, in our case base directory is ‘/u01/oracle/dba’
. /u01/oracle/dba/EBSapps.env RUN
It will set environemnt and display below information on screen.
E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/dba/fs2/EBSapps/appl
PATCH File System : /u01/oracle/dba/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/dba/fs_ne
DB Host: dbhost.hertz.com Service/SID: dba
Sourcing the RUN File System …
$ echo $FILE_EDITION
<shows which file edition you are using, run or patch>
$ echo $RUN_BASE
<shows absolute path to run file system>
$ echo $PATCH_BASE
<shows absolute path to patch file system>
$ echo $NE_BASE
<shows absolute path to non-edition file system>
$ echo $APPL_TOP_NE
<non-editioned appl_top path. Equivalent to $NE_BASE/EBSapps/appl>
$ echo $LOG_HOME
<Application Instance Specific Log Directory>
$ echo $ADOP_LOG_HOME
<Online patching Specific Log Directory. Equivalent to $NE_BASE/EBSapps/log/adop>
$ echo $IAS_ORACLE_HOME
<FMW Web Tier Home Directory>
$ echo $ORACLE_HOME
< 10.1.2 ORACLE_HOME>
$ echo $CONTEXT_FILE
<Source for information populating template files (autoconfig)>
$ echo $EBS_DOMAIN_HOME
<WLS Deployment of Oracle E-Business Suite 12.2 Domain (instance specific)>
$ echo $ADMIN_SCRIPTS_HOME
<Shell scripts to control processes associated to the Applications Instance>
$ echo $EBS_ORACLE_HOME
<Oracle E-Business Suite 12.2 FMW Deployment directory>
$ echo $RW
<10.1.2 reports directory>
$ echo $HOSTNAME
<hostname without domain name>
$ echo $APPS_VERSION
<to get the EBS version>
And the most important part is for setting up the right environment don’t directly hard code the RUN environemnt .env file in the .profile of OS user as online patching switches the filesystem from RUN to PATCH and vice versa and it can really create confusion.
Instead use EBSapps.env environment file (created under BASE directory) with ‘RUN’ as argument. It will automatically find which file system (fs1 or fs2) is currently RUN file system and lay out the correct environment.
For example, in our case base directory is ‘/u01/oracle/dba’
. /u01/oracle/dba/EBSapps.env RUN
It will set environemnt and display below information on screen.
E-Business Suite Environment Information
—————————————-
RUN File System : /u01/oracle/dba/fs2/EBSapps/appl
PATCH File System : /u01/oracle/dba/fs1/EBSapps/appl
Non-Editioned File System : /u01/oracle/dba/fs_ne
DB Host: dbhost.hertz.com Service/SID: dba
Sourcing the RUN File System …
No comments:
Post a Comment