Last updated on July 22nd, 2018 at 05:04 pm
oracle apps dba training
This is in continuation of the Online oracle apps dba training Course Series
Here is Online oracle apps dba training Course Part 2 . I will be discussing Oracle application Filesystem,Oracle Applications Environment Files and Server Process Scripts,Oracle Applications Entire File System,The Applications and Database Context Files
Lets get started
Introduction to Oracle application Filesystem
An Oracle Applications Release 12 system utilizes components from many Oracle products. These product files are stored below a number of key top-level directories on the database and application server machines.
Depending on how you chose to install Applications, these product directories may be located on a single machine (the simplest case) or on multiple machines (the most common type of deployment). Operating system environment settings indicate the location of the various files in the file systems of the database and application tier machines.
As you know already know ,the latest offereing of apps R12.2 is quite different, I will start with application filesystem for R12.1 and then I will move on to explain the difference in R12.2
So here is the description of top Level directory in R12.1
|db/apps_st/data||This directory is located on the database node machine, and contains the system tablespaces, redo log files, data tablespaces, index tablespaces, and database files. This is standard location but we can change the datafiles to be stored in different directory structure altogether. It can be stored in ASM also|
|This directory is located on the database node machine, and contains the ORACLE_HOME for the Oracle database. It could be any version like 220.127.116.11. This is standard location but we can change the Oracle Home to be stored in different directory structure altogether.|
|apps/apps_st/appl (APPL_TOP)||This directory contains the product directories and
files for Oracle Applications. It is present on Application Node machine. In single node installation both Database Node and application node are same
|apps/apps_st/comn (COMMON_TOP)||Thus directory contains Java classes, HTML
pages, and other files and directories used by multiple products
|apps/tech_st/10.1.2||This directory contains the ORACLE_HOME used for the Applications technology stack tools components|
|apps/tech_st/10.1.3||This directory contains the ORACLE_HOME used for the Applications technology stack Java components|
Application Environment and INSTANCE HOME
Oracle Applications makes extensive use of environment settings to locate executable programs and other files essential to Applications operation. These environment settings are defined when you install Oracle Applications. Many of the settings are defined by information you provide when running Rapid Install, while others have the same values in all installations. The environment settings and their associated values are stored in environment files. Environment files have .env suffix on Unix OS.
Before R12, the environment files were scattered across different product directories/top level directories .With R12 Oracle introduced the concept of Instance Home.
Oracle Applications Release 12 introduces the concept of a top-level directory for an Applications instance. This directory is referred to as the Instance Home, and denoted by the environment variable $INST_TOP
The basic structure of the instance home is: <APPS_BASE>/inst/apps/<context_name>,where APPS_BASE (which does not have or need a corresponding environment variable) is the top level of the Applications installation, and <context_name> is the highest level at which the Applications context exists. For example, the setting of
$INST_TOP might be /u01/applmgr/inst/apps/TEST_TECH, where TEST_TECH, is the context name. All configuration files created by AutoConfig are stored under the Instance Home. This facilitates use of a shared application tier file system,
Another advantages is log files can be stored centrally for an instance, and therefore managed more easily.
For more information of INST_TOP, read below article
Now lets us take a detailed look at the top level directories defined above
This directory contains the product directories and files for Oracle Applications
The APPL_TOP directory contains:
• The core technology files and directories.
• The product files and directories (for all products).
• The main applications environment file, called <CONTEXT_NAME>.env on UNIX,
• The consolidated environment file, called APPS<CONTEXT_NAME>.env on UNIX,
Rapid Install creates a directory tree for every Oracle Applications product in this APPL_TOP directory, whether licensed or not.
All Oracle Applications products are installed in the database and the file system, regardless of registration status. Do not attempt to remove files for any unregistered products.
Each product has its own subdirectory under APPL_TOP. The subdirectories are named in accordance with the product’s standard abbreviation, such as INV for OracleInventory Within each product directory is a subdirectory that is named using the base Oracle Applications release number, such as 12.0.0. This directory contains the various subdirectories for the product files.
Within each <PROD>_TOP directory, the product’s files are grouped into subdirectories according to file type and function. The belo figure expands the inset to show the full directory structure
Description of product files can be found on below links
Core Technology Directories in APPL_TOP
The admin, ad, au, and fnd directories are the core technology directories.
|admin||This directory and its sub directories contain files and scripts used by the AD utilities
during upgrade and maintenance processes.
These files and scripts include:
• The adovars.env environment file, which defines certain file and directory locations
• Scripts run during the upgrade
• <SID>/log and <SID>/out directories for upgrade, log, and output files respectively
• A <SID>/restart directory where AD programs create restart files
|This directory and its sub directories contain installation and maintenance utilities,
• AD Administration (adadmin)
• AutoConfig (adconfig.sh)
|Au||This directory and its sub directories contain product files that are consolidated in a
single location for optimal processing. These files include:
• PL/SQL libraries used by Oracle Forms, in the resource subdirectory
• Oracle Forms source files, in the forms subdirectory
• A copy of all Java files used when regenerating the desktop client JAR files, in the
|fnd||The fnd (Application Object Library) directory
This directory and its sub directories contain the scripts and programs that are used asthe foundation for all Applications products to build data dictionaries, forms and C object libraries
The apps/apps_st/comn (COMMON_TOP) directory contains files used by many different Oracle Applications products, and which may also be used with third-party products.
|admin||The admin directory, under the COMMON_TOP directory, is the default location for the concurrent manager log and output directories. When the concurrent managers run Oracle Applications reports, they write the log files and temporary files to the log subdirectory of the admin directory, and the output files to the out subdirectory of the admin directory.
The install subdirectory of the admin directory contains scripts and log files used by Rapid Install. The scripts subdirectory of admin contains scripts used to start and stop services such as listeners and concurrent managers.
|Applications HTML-based sign-on screen and Oracle HTML-based Applications HTML files are installed here. The html directory also contains other files used by the HTML-based products, such as JavaServer Page (JSP) files, Java scripts, XML files, and style sheets. Typically, the path will look like:
Two new subdirectories are META-INF and WEB-INF, introduced to meet J2EE specifications.
|java||Release 12 introduces some significant changes to the locations in which the various types of Java files are stored. Rapid Install installs all Oracle Applications class files in the COMMON_TOP/classes directory, pointed cto by the $JAVA_TOP environment variable. Zip and jar files are installed in the $COMMON_TOP/java/lib directory, pointed to by the $AF_JLIB environment variable (introduced with Release 12). The top-level Java directory, $COMMON_TOP/java, is pointed to by the $JAVA_BASE
|util||The util directory contains the third-party utilities licensed to ship with Oracle
Applications. These include, for example, the Java Runtime Environment (JRE), Java Development Kit (JDK), and the Zip utility
The 10.1.2 and 10.1.3 Oracle Home
These are standard Oracle Home directories . Oracle Applications supports running Multiple Applications components out of Multiple. ORACLE_HOMEs. This multiple ORACLE_HOMEs configuration allows Applications to
utilize new features of the Oracle database and associated technologies in the most flexible manner.
Application Environment Settings
Rapid Install creates several environment files that set up the Oracle database, the
Oracle technology stack, the Oracle HTTP server, and the Oracle Applications
The location of these in below table
|<CONTEXT_NAME>.env||Stored in Oracle Database Home Path db/tech_st/<Oracle version>( Database Oracle Home)
This set the Database related Environment
|<CONTEXT_NAME>.env||Stored in inst/apps/<context>/ora/10.1.2. ( Oracle 10.1.2 Home) This set the Oracle tools
Technology stack setting
|<CONTEXT_NAME>.env||Stored in inst/apps/<context>/ora/10.1.3.( Oracle 10.1.3 Home) This set the Java
|<CONTEXT_NAME>.env||Stored in apps/apps_st/appl(APPL_TOP). This set the Application Variable like Product top|
|APPS<CONTEXT_NAME>.env||Stored in apps/apps_st/appl(APPL_TOP). This is the consolidated setup file which sets up both the Oracle Applications and Oracle
technology stack environments.
You might ask what is CONTEXT_NAME here
What is context_name
Where the System Identifier (SID) has traditionally been used to identify a file as belonging to a particular Oracle Applications environment, an Applications context is used in an AutoConfig-managed Applications environment such as E-Business Suite Release 12. The default context name as <CONTEXT_NAME>, is <SID>_<hostname>.
Using an Applications context has a number of advantages:
• Simplifies overall management of an Applications system
• Allows easier startup and shutdown of Applications services
Key Environment Variable
|APPLFENV||The name of the environment file, <CONTEXT_NAME>.env. If you rename the environment file, this parameter setting must
|PLATFORM||The operating system in use. The value (for
example, LINUX) should match the value in
the APPL_TOP/admin/adpltfrm.txt file. APPL_TOP The top-level directory for this Oracle Applications installation
|ADMIN_SCRIPTS_HOME||Directory under $INST_TOP that Identifies
the location of scripts such as adautocfg.sh,
adpreclone.sh, adstrtal.sh, and adstpall.sh.
|FNDNAM||The name of the ORACLE schema to which
the System Administration responsibility
connects. The default is APPS.
|GWYUID||The public ORACLE username and password
that grants access to the Oracle Applications
initial sign-on form. The default is APPLSYSPUB/PUB.
|FND_TOP||The path to the Application Object Library directory. For example, apps/apps_st/appl/fnd/12.0.0|
|AU_TOP||The path to the Applications Utilities directory. For example, apps/apps_st/appl/au/12.0.0|
|<PROD>_TOP||The path to a product’s top directory. There is
one entry for each Oracle Applications
|PATH||Sets the directory search path, for example for
FND_TOP and AD_TOP.
|APPCPNAM||Indicates whether the format of the concurrent
manager log and output files follow 8.3 file
name conventions (maximum of 8 characters
to the left of the dot and 3 to the right; for
example, alogfile.log). If this parameter is set
to “REQID” (required), the concurrent
manager uses file names that meet 8.3 naming
|APPLCSF||Identifies the top level directory for concurrent manager log and output files if they are consolidated into a single directory across all products. For example,
|APPLLOG||The subdirectory for concurrent manager log
files. The default is log
|APPLOUT||The subdirectory for concurrent manager
output files. The default is out
|APPLTMP||Identifies the directory for Oracle
Applications temporary files. The default is
/tmp on UNIX
APPLPTMP Identifies the directory for temporary PL/SQL output files. The possible directory options
must be listed in the init.ora parameter
|INST_TOP||Identifies the top-level directory for this
instance. For example, inst/apps/<context>.
Introduced with Release 12.
Other Important environment files
|Adovars.env||The adovars.env file, located in $INST_TOP/app/admin, specifies the location of various files such as Java files, HTML files, and JRE (Java Runtime Environment) files. It is called from the main applications environment file,<CONTEXT_NAME>.env.|
|Adconfig.txt||AD utility programs perform a variety of database and file management tasks. These utilities need to know certain configuration information to run successfully. This configuration information is specified when Oracle Applications is installed, and subsequently stored in the adconfig.txt file in the <APPL_TOP>/admin directory. Once it has been created, this file is used by other Oracle Applications utilities.
Note: adconfig.txt is created with the APPL_TOP file system, and it shows the tiers that have been configured on a particular node.
|Fndenv.env||This file sets additional environment variables used by the Application Object Library.|
As already discussed in previous two parts, R12.2 is different animal in term of techstack and file system
The 10.1.2 Oracle Home remains but 10.1.3 Oracle home has been replaced by Fusion Middleware Home
We have Three filesystem to support Online Patching.
|FS1(Production file system)||Used by the current users of the system|
|FS-2 (Copy of Production file system)||Used by the patching tools|
|FS-NE (Non Editioned file system)||It holds AD executables, PATCH_TOP and CM Log/Output files|
New Environment variable
|EBS_DOMAIN_HOME||/u99/app/app/ebiz/EBSR122/VISR122/at2/FMW_Home/user_projects /domains /EBS_domain_VISR122|
- APPL_TOP, COMMON_TOP, INST_TOP, JAVA_TOP &FND_SECURE remains same except COMMON_TOP has more web applications under webapps directory.
- There are various WebLogic servers created in FMW Home: AdminServer, oacore_server1, oafm_server1, forms-c4ws_server1, and forms_server1.
R12.2 Filesystem Layout
I hope you like this Oracle Apps DBA Training part on Application filesystem layout for both R12.1 and R12.2
Please do provide the feedback