Apps DBA administration:
--------------------------*******--------------------
Hi,
To maintain Oracle R12 Applictions the below article can be useful(Some changes are present in filesystem if you want to maintain for Oracle 11i which I will put in separate post to avoid confusions).
Whenever we are working with Oracle Application we have to make sure Oracle
Environment is set than you can proceed with the administration tasks based on the
requirements.So let us proceed with setting environment file which makes our Oracle Application server ready for doing administration tasks.
There are basically 2 environments file you need to set to start working with
ad scripts
Location of Environment files:
1)Application Environment file: The Application Environment file is located in the path where Application stack sits like '/oraAPP/apps/apps_st/appl' which is nothing but what we called as APPL_TOP
2)Application Database Environment file: The Database environment is present in Database technology stack like '/oraDB/db/tech_st/11.1.0'.
Step 1:Set the environment file for Applications:
Login as root user(Grant Applmgr or Oracle user the privilege to execute Environment files)
[root@test300949v20ebs appl]# cd /oraAPP/apps/apps_st/appl
[root@test300949v20ebs appl]# . VIS_test300949v20ebs.env
[root@test300949v20ebs appl]# pwd
/oraAPP/apps/apps_st/appl
(or)
[applmgr@test300949LX6 appl]$ . VIS_test300949lx6.env
[applmgr@test300949LX6 appl]$ pwd
/u01/oraEBS/apps/apps_st/appl
[applmgr@test300949LX6 appl]$ echo $APPL_TOP
/u01/oraEBS/apps/apps_st/appl
[applmgr@test300949LX6 appl]$ echo $INST_TOP
/u01/oraEBS/inst/apps/VIS_test300949lx6
[applmgr@test300949LX6 appl]$ echo $COMMON_TOP
/u01/oraEBS/apps/apps_st/comn
Step 2:Set the environment file for Application Database:
Login as root user and do the below steps for setting the environement files.
Setting of environment file plays major role in Applications as it create the
environment for working with AD utilities and working with various tops
like APPL_TOP,COMMON_TOP,INST_TOP,AD_TOP...
[root@test300949v20ebs tech_st]# cd /oraDB/db/tech_st/11.1.0
[root@test300949v20ebs 11.1.0]# . VIS_test300949v20ebs.env
[root@test300949v20ebs 11.1.0]# pwd
/oraDB/db/tech_st/11.1.0
(or)
[oracle@test300949LX6 11.1.0]$ . VIS_test300949lx6.env
[oracle@test300949LX6 11.1.0]$ pwd
/u01/oraEBS/db/tech_st/11.1.0
Step 3:Connect to sqlplus for obtaing URL for your Oracle E-businness suite home page.
Login as apps user(Apps user holds all the privileges in application)
Obtain the URL for the front end,which is also termed as Oracle E-business suite
home page as follows:
[oracle@test300949LX6 11.1.0]$ sqlplus "/as sysdba"
SQL*Plus: Release 11.1.0.7.0 - Production on Tue Mar 22 22:07:15 2011
Copyright (c) 1982, 2008, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select name from v$database;
NAME
---------
VIS
SQL> CONN APPS
Enter password:
Connected.
SQL> sho user
USER is "APPS"
SQL> select home_url from icx_parameters;
HOME_URL
--------------------------------------------------------------------------------
http://Test300949lx6.in.test.com:8000/OA_HTML/AppsLogin
The above URL is useful for login to your Front-end of Oracle E-businness suite and do lot of tasks.
Note: Like in Oracle Database there are few users in Oracle Applictions which are blessed with maximum privileges like sysadmin,apps...
sysadmin=>sysadmin user can login to Oraclee E-business suite home page and do lot of System administration tasks(Responsibility),he can create new users from front end and can do lot of tasks like viewing the status of patches which are application,status of Concurrent managers and so on...
apps=>apps user is like 'system' user of Database.In Apps it is having the access to all the objects of all the modules like (ar,gl,ap...),Whenever you are doing administration tasks in Application this user password is required.
Ofcourse there are many other users for each modules but for the initial stage of learning knowing the above user can be added to advantage.
Step 4:Working with AD Utilities:
All AD Utilities are found in $ADMIN_SCRIPTS_HOME path.We have to use this based on our requirements.Once you are ready with environment setting now you can direct go to the path where your scripts are located and other TOPs of your choice like APPL_TOP,COMMON_TOP,INST_TOP where your scripts are present.
[root@test300949v20ebs appl]# cd $ADMIN_SCRIPTS_HOME
[root@test300949v20ebs scripts]# ls -altr
total 268
-rwx------ 1 applmgr dba 5945 Mar 15 09:06 adstrtal.sh =>For starting all applications
-rwx------ 1 applmgr dba 5801 Mar 15 09:06 adstpall.sh =>For stopping all applications
-rwx------ 1 applmgr dba 7353 Mar 15 09:06 adalnctl.sh =>For starting/stopping RPC listeners
-rwx------ 1 applmgr dba 16547 Mar 15 09:06 adcmctl.sh =>For starting concurrent manager
-rwx------ 1 applmgr dba 1552 Mar 15 09:06 adautocfg.sh =>For running autoconfig
-rwx------ 1 applmgr dba 15332 Mar 15 09:06 adpreclone.pl =>For cloning apps
-rwx------ 1 applmgr dba 7181 Mar 15 09:06 adexecsql.pl =>For Executing sql scripts that update the profiles in an AutoConfig run.
-rwx------ 1 applmgr dba 2201 Mar 15 09:07 java.sh =>For Calling java executable with additional argumentss(It is used by opmn,Concurrent Managers)
-rwx------ 1 applmgr dba 2260 Mar 15 09:07 gsmstart.sh =>For starting/stopping FNDSM(i.e Standard concurrent manager)
-rwx------ 1 applmgr dba 8840 Mar 15 09:07 adformsctl.sh =>For starting/stopping forms services
-rwx------ 1 applmgr dba 8339 Mar 15 09:07 adapcctl.sh =>For starting/stopping Oracle HTTP/Apache/web services
-rwx------ 1 applmgr dba 8110 Mar 15 09:07 adoafmctl.sh =>For starting/stopping oafm(Oracle Application forms) OC4J
-rwx------ 1 applmgr dba 8102 Mar 15 09:07 adoacorectl.sh=>For starting/stopping oacore(Oracle Application core) OC4J
-rwx------ 1 applmgr dba 7376 Mar 15 09:07 adopmnctl.sh =>For starting/stopping OPMN(Oracle Process Manager & Notification)
-rwx------ 1 applmgr dba 10318 Mar 15 09:07 adformsrvctl.sh =>For starting forms services in socket mode
Note: Oracle Applications uses RPC server processes such as Report Review Agent (FNDFS) and OE Transaction
Manager (OEORPC) for listener ports.
Eg:
---
Starting All applications(services) :
--------------------------------------
[root@test300949v20ebs scripts]# ./adstrtal.sh =>Starts all the applications
You are running adstrtal.sh version 120.15
Enter the APPS username: apps
Enter the APPS password:
The logfile for this session is located at /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adstrtal.log
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/adopmnctl.sh start
script returned:
****************************************************
You are running adopmnctl.sh version 120.6
Starting Oracle Process Manager (OPMN) ...
adopmnctl.sh: exiting with status 0
adopmnctl.sh: check the logfile /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adopmnctl.txt for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/adalnctl.sh start
script returned:
****************************************************
adalnctl.sh version 120.3
Checking for FNDFS executable.
Starting listener process APPS_VIS.
adalnctl.sh: exiting with status 1
adalnctl.sh: check the logfile /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adalnctl.txt for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/adapcctl.sh start
script returned:
****************************************************
You are running adapcctl.sh version 120.7.12010000.2
Starting OPMN managed Oracle HTTP Server (OHS) instance ...
adapcctl.sh: exiting with status 0
adapcctl.sh: check the logfile /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adapcctl.txt for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/adoacorectl.sh start
script returned:
****************************************************
You are running adoacorectl.sh version 120.13
Starting OPMN managed OACORE OC4J instance ...
adoacorectl.sh: exiting with status 0
adoacorectl.sh: check the logfile /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adoacorectl.txt for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/adformsctl.sh start
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/adoafmctl.sh start
script returned:
****************************************************
You are running adoafmctl.sh version 120.8
Starting OPMN managed OAFM OC4J instance ...
adoafmctl.sh: exiting with status 0
adoafmctl.sh: check the logfile /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adoafmctl.txt for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/adcmctl.sh start
script returned:
****************************************************
You are running adcmctl.sh version 120.17.12010000.3
Starting concurrent manager for VIS ...
Starting VIS_0322@VIS Internal Concurrent Manager
Default printer is noprint
adcmctl.sh: exiting with status 0
adcmctl.sh: check the logfile /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adcmctl.txt for more information ...
.end std out.
.end err out.
****************************************************
Executing service control script:
/oraAPP/inst/apps/VIS_test300949v20ebs/admin/scripts/jtffmctl.sh start
script returned:
****************************************************
You are running jtffmctl.sh version 120.3
Validating Fulfillment patch level via /oraAPP/apps/apps_st/comn/java/classes
Fulfillment patch level validated.
Starting Fulfillment Server for VIS on port 9300 ...
jtffmctl.sh: exiting with status 0
.end std out.
.end err out.
****************************************************
adstrtal.sh: Exiting with status 1
adstrtal.sh: check the logfile /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log/adstrtal.log for more information .
[root@test300949v20ebs log]# cd /oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log
[root@test300949v20ebs log]# ls -altr
total 172
drwxr-xr-x 3 applmgr dba 4096 Mar 15 09:13 ..
drwxr-xr-x 2 applmgr dba 4096 Mar 16 00:47 .
-rw-r--r-- 1 applmgr dba 20172 Mar 21 21:45 adstpall.log
-rw-r--r-- 1 applmgr dba 2518 Mar 22 22:15 adopmnctl.txt
-rw-r--r-- 1 applmgr dba 14367 Mar 22 22:15 adalnctl.txt
-rw-r--r-- 1 applmgr dba 3234 Mar 22 22:15 adapcctl.txt
-rw-r--r-- 1 applmgr dba 3039 Mar 22 22:15 adoacorectl.txt
-rw-r--r-- 1 applmgr dba 3127 Mar 22 22:15 adformsctl.txt
-rw-r--r-- 1 applmgr dba 2961 Mar 22 22:15 adoafmctl.txt
-rw-r--r-- 1 applmgr dba 2509 Mar 22 22:15 adcmctl.txt
-rw-r--r-- 1 applmgr dba 33850 Mar 22 22:15 adstrtal.log
-rw-r--r-- 1 applmgr dba 1702 Mar 22 22:15 javacache.log
-rw-r--r-- 1 applmgr dba 9717 Mar 22 22:15 jtffmctl.txt
For viewing the logfiles the location is $APPL_TOP/admin/log
[root@test300949v20ebs log]#
[root@test300949v20ebs log]# pwd
/oraAPP/inst/apps/VIS_test300949v20ebs/logs/appl/admin/log =>logfiles location after running ad(Application database) scripts.
Note:
-----
As said above you can start any of the applications or services by going to
the $ADMIN_SCRIPTS_HOME
Eg:
To start concurrent manager:$./adcmctl.sh start
To stop concurrent manager:$./adcmctl.sh stop
To start Apache/HTTP server:$./adapcctl.sh start
To stop Apache/HTTP server:$./adapcctl.sh stop
Similarly we can start/stop other applications based on our need in the same way.
5)AD Administration(adadmin utility):
The main task of Apps DBA is to maintain the application with adadmin utility,Ofcourse there are other tasks like cloning and patching.First you have to set the environment.The environment file of Oracle Application which is located in APPL_TOP directory.
With 'adadmin' utilities you can do various tasks listed in the menu.Let me change
the maintainance mode which we do while applying patches.The other tasks are done whenever there is a need or request from developer to do so in your Oracle Applications.When you have upgraded your Oracle Application and whenever you applied a patch based on the module you have applied,than that time if the configuration gets changed we might have to use these 'adadmin' utility to make the configurations stable.
Working with ADUTILITIES(adamin)
[applmgr@test300949LX6 appl]$cd /u01/oraEBS/apps/apps_st/appl
[applmgr@test300949LX6 appl]$ . APPSVIS_test300949lx6.env
[applmgr@test300949LX6 appl]$ pwd
/u01/oraEBS/apps/apps_st/appl
[applmgr@test300949LX6 appl]$ adadmin
Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
Oracle Applications AD Administration
Version 12.0.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
Your default directory is '/u01/oraEBS/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?
AD Administration records your AD Administration session in a text file
you specify. Enter your AD Administration log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adadmin.log] : adadmintest7.log
************* Start of AD Administration session *************
AD Administration version: 12.0.0
AD Administration started at: Wed Mar 23 2011 00:13:54
APPL_TOP is set to /u01/oraEBS/apps/apps_st/appl
You can be notified by email if a failure occurs.
Do you wish to activate this feature [No] ?
Please enter the batchsize [1000] :
Please enter the name of the Oracle Applications System that this
APPL_TOP belongs to.
The Applications System name must be unique across all Oracle
Applications Systems at your site, must be from 1 to 30 characters
long, may only contain alphanumeric and underscore characters,
and must start with a letter.
Sample Applications System names are: "prod", "test", "demo" and
"Development_2".
Applications System Name [VIS] : VIS *
NOTE: If you do not currently have certain types of files installed
in this APPL_TOP, you may not be able to perform certain tasks.
Example 1: If you don't have files used for installing or upgrading
the database installed in this area, you cannot install or upgrade
the database from this APPL_TOP.
Example 2: If you don't have forms files installed in this area, you cannot
generate them or run them from this APPL_TOP.
Example 3: If you don't have concurrent program files installed in this area,
you cannot relink concurrent programs or generate reports from this APPL_TOP.
Do you currently have files used for installing or upgrading the database
installed in this APPL_TOP [YES] ? YES *
Do you currently have Java and HTML files for HTML-based functionality
installed in this APPL_TOP [YES] ? YES *
Do you currently have Oracle Applications forms files installed
in this APPL_TOP [YES] ? YES *
Do you currently have concurrent program files installed
in this APPL_TOP [YES] ? YES *
Please enter the name Oracle Applications will use to identify this APPL_TOP.
The APPL_TOP name you select must be unique within an Oracle Applications
System, must be from 1 to 30 characters long, may only contain
alphanumeric and underscore characters, and must start with a letter.
Sample APPL_TOP Names are: "prod_all", "demo3_forms2", and "forms1".
APPL_TOP Name [test300949lx6] : test300949lx6 *
You are about to use or modify Oracle Applications product tables
in your ORACLE database 'VIS'
using ORACLE executables in '/u01/oraEBS/apps/tech_st/10.1.2'.
Is this the correct database [Yes] ?
AD Administration needs the password for your 'SYSTEM' ORACLE schema
in order to determine your installation configuration.
Enter the password for your 'SYSTEM' ORACLE schema:
The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :
AD Administration is verifying your username/password.
The status of various features in this run of AD Administration is:
<-Feature version in->
Feature Active? APPLTOP Data model Flags
------------------------------ ------- -------- ----------- -----------
CHECKFILE Yes 1 1 Y N N Y N Y
PREREQ Yes 6 6 Y N N Y N Y
CONCURRENT_SESSIONS No 2 2 Y Y N Y Y N
PATCH_TIMING Yes 2 2 Y N N Y N Y
PATCH_HIST_IN_DB Yes 6 6 Y N N Y N Y
SCHEMA_SWAP Yes 1 1 Y N N Y Y Y
JAVA_WORKER Yes 1 1 Y N N Y N Y
CODELEVEL Yes 1 1 Y N N Y N Y
Identifier for the current session is 542217
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
AD Administration warning:
Product Data File
/u01/oraEBS/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product "zfa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AD Administration warning:
Product Data File
/u01/oraEBS/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product "zsa".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
AD Administration warning:
Product Data File
/u01/oraEBS/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product "jts".
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.
Reading database to see what industry is currently installed.
Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:
Code Language Status
---- --------------------------------------- ---------
US American English Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Reading database for information about how products depend on each other.
Reading topfile.txt ...
Saving product information.
AD code level : [B.1]
AD Administration Main Menu
--------------------------------------------------
1. Generate Applications Files menu
2. Maintain Applications Files menu
3. Compile/Reload Applications Database Entities menu
4. Maintain Applications Database Entities menu
5. Change Maintenance Mode
6. Exit AD Administration
Enter your choice [6] :
Enter your choice [6] : 5
Change Maintenance Mode
----------------------------------------
Maintenance Mode is currently: [Disabled].
Maintenance mode should normally be enabled when patching
Oracle Applications and disabled when users are logged on
to the system. See the Oracle Applications Maintenance
Utilities manual for more information about maintenance mode.
Please select an option:
1. Enable Maintenance Mode
2. Disable Maintenance Mode
3. Return to Main Menu
Enter your choice [3] : 1
sqlplus -s &un_apps/***** @/u01/oraEBS/apps/apps_st/appl/ad/12.0.0/patch/115/sql/adsetmmd.sql ENABLE
Successfully enabled Maintenance Mode.
Review the messages above, then press [Return] to continue.
Backing up restart files, if any......Done.
Change Maintenance Mode
----------------------------------------
Maintenance Mode is currently: [Enabled].
Maintenance mode should normally be enabled when patching
Oracle Applications and disabled when users are logged on
to the system. See the Oracle Applications Maintenance
Utilities manual for more information about maintenance mode.
Please select an option:
1. Enable Maintenance Mode
2. Disable Maintenance Mode
3. Return to Main Menu
Enter your choice [3] : 2
sqlplus -s &un_apps/***** @/u01/oraEBS/apps/apps_st/appl/ad/12.0.0/patch/115/sql/adsetmmd.sql DISABLE
Successfully disabled Maintenance Mode.
Review the messages above, then press [Return] to continue.
Backing up restart files, if any......Done.
Change Maintenance Mode
----------------------------------------
Maintenance Mode is currently: [Disabled].
Maintenance mode should normally be enabled when patching
Oracle Applications and disabled when users are logged on
to the system. See the Oracle Applications Maintenance
Utilities manual for more information about maintenance mode.
Please select an option:
1. Enable Maintenance Mode
2. Disable Maintenance Mode
3. Return to Main Menu
Enter your choice [3] : 3
AD Administration Main Menu
--------------------------------------------------
1. Generate Applications Files menu
2. Maintain Applications Files menu
3. Compile/Reload Applications Database Entities menu
4. Maintain Applications Database Entities menu
5. Change Maintenance Mode
6. Exit AD Administration
Enter your choice [6] :
Please make sure you disable maintenance mode once your
patching activity is completed to avoid unnecessary issues.
Hope this helps our Beginner Apps DBAs for Administraton of Oracle R12 Applications.
Best regards,
Rafi.
No comments:
Post a Comment