ADUTILITIES in R12.1/R12.2 EBS
ADUTILITIES in R12.1/R12.2 EBS
---------------------------------------------
Forms Compilation:
-------------------
frmcmp_batch.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/forms/US/
XXX.fmb userid=APPS/APPS output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/
12.0.0/forms/US/XXX.fmx module_type=form compile_all=special
ADLICMGR:
==========
1. After purchasing a license for an Application Product/Module, the first thing is to use license manager to record that the product/module is now licensed. License manager can be run 2 ways:
a. log in through Oracle Application Manager (OAM) and select Site Map -> Administration tab -> License Manager
b. run adlicmgr.sh from AD_TOP/bin
Using both methods you can license by Module or by individual Product. Select the check box for the Module/Product to be licensed and Save/Next
2. The Products are now licensed but not ready to be used as none of the Forms/Packages etc would have been compiled and loaded into the Database for these new Products. Use adadmin to generate the files for the new Product/s
a. run adadmin
b. Select Generate Application Files menu
c. Select all of the following Menu options:
– Generate message files
– Generate forms files
– Generate report files
– Generate graphic files
– Generate product JAR files
dnivra3152@gmail.com
d. Back to Main Menu
e. Select Compile/Reload Applications Database Entities menu
f. Select all of the following Menu options:
– Compile APPS schema
– Compile menu information
– Compile flexfields
3. Once complete, check that the Forms/JSPs for the new Products licensed now work. The Products are now ready to be configured.
4. Run autoconfig.
adrelink:
===========
Note:
To relink AD Utilities, use adrelink.sh. To relink non-AD products, use adadmin.
Relink is recommended after cloning, upgrades and patching. Or when an AD executable got corrupt or lost.
Script Location: $AD_TOP/bin
Syntax:
To relink adpatch, adsplice and adadmin:
adrelink.sh force=y “ad adpatch” “ad adsplice” “ad adadmin”
To relink all AD executables:
adrelink.sh force=y “ad all”
If you are relinking files on the Concurrent Manager node, then shutdown the Concurrent Managers
before relink operation.
If you are relinking files on Forms Server, then all Oracle application users must be logged off
before relink operation.
Sysadmin:
==========
System Administrator should have a thorough knowledge in
R12 Oracle Architecture and Directory Structures
Create and Administer Users and Responsibilities
Assign Responsibilities to Users
Register a Custom Application
Role Based Access Control
Manage Concurrent Programs and Reports
Administer Concurrent Managers
Manage Profile Options
Incorporate a Custom Program
Audit System Resources
Set Up and Manage Printers
Monitor the System with Oracle Applications Manager
Run Diagnostic and Troubleshooting Utilities from OAM
Administer Folders
Manage Document Sequences
Define Value Sets
Personalize Forms
Monitor Workflow Processes
Oracle Alert Overview
These are the most common responsibilities of a System Administrator in Oracle R12
AD Utilities in R12
=====================
AD Utilities are a group of tools designed to install, upgrade, maintain, and patch applications.
ADDBCTL - is a utility to start the database
ADDLNCTL- is used to start the listener control
ADSTRTAL- is a utility for starting all the application in Application tier
ADCMCTL - is used for starting the concurrent manager
ADSTPALL - is a utility to stop all the process in Application tier
ADADMIN - is used to perform maintenance/administration tasks on an Oracle Apps Instance.
ADCTRL -Utility to determine status of worker
ADRELINK -Used to relink apps executables with product libraries
ADMRGPCH -Merge different patches & create single patch .
ADCLONE -Utility to clone Insatnce from Test to Prod or PROD to TEST
ADCONFIG -To configure different components like changing port number or to increase number of JVM
ADIDENT -utility to find version of a file
ADLICMGR -To license a product in applications
ADSPLICE -You add a product in application
apps patching modes:
======================
Modes of adpatch:
Interactive mode
Non-Interactive mode
Test mode
Pre-Install mode
Interactive Mode:
It is the default mode of adpatch when we don’t use anything. We can apply patch in this mode by going into patch directory and simply type adpatch in command prompt and hit enter.
Non-Interactive:
We can apply in this mode as:
$adpatch Interactive=no
It uses default files to store prompt values and can be applied from patch directory.
Test Mode:
This mode is purposely used to check the what exactly patch is doing and will do everything without actually changing anything.
We can apply patch in this mode as:
$adpatch apply=no
By default apply=yes
PreInstall Mode:
This mode is used to apply adpatch for any upgrade or consolidated update of utilities itself. So, it would be suggested to apply pre-install patch first.
When we apply patch in preinstall mode, it updates all AD utilities befre upgrade or update.
We can apply adpatch in this mode as:
$adpatch preinstall=y
Adpatch Options:
We have multiple adpatch options and based on the requirement we can use specific options. Here, I will try to cover most often used adpatch options.
Noautoconfig:
$adpatch options=noautoconfig
This options is used to skip the autoconfig execution as by default it executes the autoconfig and updates the configuration file if any template file is added. This option is helpful when we apply multiple adpatch and they are not merged.
Nocompiledb(without compiling database):
While we apply adpatch, It may create invalid objects and by default adpatch compiles the invalid objects after patch application. But in case you do not want to compile invalid objects to ensure the minimal autopatch time, you can apply adpatch as below:
$adpatch options=nocompiledb
Nocopyportion:
This option is used to apply adpatch without copying the files present in copy driver. This can be applies as:
$adpatch options=nocopyportion
Nocompilejsp:
Adpatch also compiles the java server pages(JSP) after completion of patch application and can be skipped using the option nocompilejsp as below:
$adpatch options=nocompilejsp
Nodatabaseportion:
Nodatabaseportion option is used to skip the adpatch the activity of database driver. It can be used as:
$adpatch options=nodatabaseportion
Nogenerateportion:
Nogenerateportion option is used to skip the adpatch activity of generate driver portion of the patch and you can use the option nogenerateportion as below:
$adpatch options=nogenerateportion
Maintenance Mode disabled:
If you want to apply your adpatch without enabling maintenance mode, you can apply using the option as hotpatch as below:
$adpatch options=hotpatch
Nolink:
Nolink option is used to skip the relinking and can be used as:
$adpatch options=nolink
Nogenform:
Nogenform option is used to skip the generate form file and can be used as:
$adpatch options=nogenform
Maintainmrc:
Maintainmrc is used for adpatch to execute the maintain MRC schema as part of patch. By default maintain MRC is done for standard patch and is disabled for documentation and translation patches.
$adpatch options=nomaintainmrc
Noprereq:
This option is used to skip the checking of pre-requisite patches and by default it checks for pre-requisite patch. This option can be used as below:
$adpatch options=noprereq
Stop the concurrent manager services. Connect to apps user and run cmclean.sql script.
This script can be downloaded from metalink. Remember to commit the script after execution.
Start the CM services and then check the CM. If CM is up then fine else perform the following
================================================================================================
Stop the concurrent manager service....and run the following statement on concurrent manager node
Go to cd $FND_TOP/bin
adrelink.sh force=y "fnd FNDLIBR"
adrelink.sh force=y "fnd FNDSM"
adrelink.sh force=y "fnd FNDFS"
adrelink.sh force=y "fnd FNDCRM"
Start the CM services and then check the CM. Concurrent managers should be up and running fine now.
For Apache, use "ps -ef | grep apache"
For Forms/Reports, use "ps -ef | grep frmweb" and "ps -ef | grep rwrun"
For Concurrent Manager, use "ps -ef | grep FNDLIB"
You can list all application services by using "ps -ef | grep applmgr".
adadmrgpch:
============
creatr "Patch" : /u01/Patch/source patches
Dest : /u01/Patch/Dest_patches
3)$adpatch
---------------------------------------------
Forms Compilation:
-------------------
frmcmp_batch.sh module=/u01/oracle/TEST/apps/apps_st/appl/au/12.0.0/forms/US/
XXX.fmb userid=APPS/APPS output_file=/u01/oracle/TEST/apps/apps_st/appl/inv/
12.0.0/forms/US/XXX.fmx module_type=form compile_all=special
ADLICMGR:
==========
1. After purchasing a license for an Application Product/Module, the first thing is to use license manager to record that the product/module is now licensed. License manager can be run 2 ways:
a. log in through Oracle Application Manager (OAM) and select Site Map -> Administration tab -> License Manager
b. run adlicmgr.sh from AD_TOP/bin
Using both methods you can license by Module or by individual Product. Select the check box for the Module/Product to be licensed and Save/Next
2. The Products are now licensed but not ready to be used as none of the Forms/Packages etc would have been compiled and loaded into the Database for these new Products. Use adadmin to generate the files for the new Product/s
a. run adadmin
b. Select Generate Application Files menu
c. Select all of the following Menu options:
– Generate message files
– Generate forms files
– Generate report files
– Generate graphic files
– Generate product JAR files
dnivra3152@gmail.com
d. Back to Main Menu
e. Select Compile/Reload Applications Database Entities menu
f. Select all of the following Menu options:
– Compile APPS schema
– Compile menu information
– Compile flexfields
3. Once complete, check that the Forms/JSPs for the new Products licensed now work. The Products are now ready to be configured.
4. Run autoconfig.
adrelink:
===========
Note:
To relink AD Utilities, use adrelink.sh. To relink non-AD products, use adadmin.
Relink is recommended after cloning, upgrades and patching. Or when an AD executable got corrupt or lost.
Script Location: $AD_TOP/bin
Syntax:
To relink adpatch, adsplice and adadmin:
adrelink.sh force=y “ad adpatch” “ad adsplice” “ad adadmin”
To relink all AD executables:
adrelink.sh force=y “ad all”
If you are relinking files on the Concurrent Manager node, then shutdown the Concurrent Managers
before relink operation.
If you are relinking files on Forms Server, then all Oracle application users must be logged off
before relink operation.
Sysadmin:
==========
System Administrator should have a thorough knowledge in
R12 Oracle Architecture and Directory Structures
Create and Administer Users and Responsibilities
Assign Responsibilities to Users
Register a Custom Application
Role Based Access Control
Manage Concurrent Programs and Reports
Administer Concurrent Managers
Manage Profile Options
Incorporate a Custom Program
Audit System Resources
Set Up and Manage Printers
Monitor the System with Oracle Applications Manager
Run Diagnostic and Troubleshooting Utilities from OAM
Administer Folders
Manage Document Sequences
Define Value Sets
Personalize Forms
Monitor Workflow Processes
Oracle Alert Overview
These are the most common responsibilities of a System Administrator in Oracle R12
AD Utilities in R12
=====================
AD Utilities are a group of tools designed to install, upgrade, maintain, and patch applications.
ADDBCTL - is a utility to start the database
ADDLNCTL- is used to start the listener control
ADSTRTAL- is a utility for starting all the application in Application tier
ADCMCTL - is used for starting the concurrent manager
ADSTPALL - is a utility to stop all the process in Application tier
ADADMIN - is used to perform maintenance/administration tasks on an Oracle Apps Instance.
ADCTRL -Utility to determine status of worker
ADRELINK -Used to relink apps executables with product libraries
ADMRGPCH -Merge different patches & create single patch .
ADCLONE -Utility to clone Insatnce from Test to Prod or PROD to TEST
ADCONFIG -To configure different components like changing port number or to increase number of JVM
ADIDENT -utility to find version of a file
ADLICMGR -To license a product in applications
ADSPLICE -You add a product in application
apps patching modes:
======================
Modes of adpatch:
Interactive mode
Non-Interactive mode
Test mode
Pre-Install mode
Interactive Mode:
It is the default mode of adpatch when we don’t use anything. We can apply patch in this mode by going into patch directory and simply type adpatch in command prompt and hit enter.
Non-Interactive:
We can apply in this mode as:
$adpatch Interactive=no
It uses default files to store prompt values and can be applied from patch directory.
Test Mode:
This mode is purposely used to check the what exactly patch is doing and will do everything without actually changing anything.
We can apply patch in this mode as:
$adpatch apply=no
By default apply=yes
PreInstall Mode:
This mode is used to apply adpatch for any upgrade or consolidated update of utilities itself. So, it would be suggested to apply pre-install patch first.
When we apply patch in preinstall mode, it updates all AD utilities befre upgrade or update.
We can apply adpatch in this mode as:
$adpatch preinstall=y
Adpatch Options:
We have multiple adpatch options and based on the requirement we can use specific options. Here, I will try to cover most often used adpatch options.
Noautoconfig:
$adpatch options=noautoconfig
This options is used to skip the autoconfig execution as by default it executes the autoconfig and updates the configuration file if any template file is added. This option is helpful when we apply multiple adpatch and they are not merged.
Nocompiledb(without compiling database):
While we apply adpatch, It may create invalid objects and by default adpatch compiles the invalid objects after patch application. But in case you do not want to compile invalid objects to ensure the minimal autopatch time, you can apply adpatch as below:
$adpatch options=nocompiledb
Nocopyportion:
This option is used to apply adpatch without copying the files present in copy driver. This can be applies as:
$adpatch options=nocopyportion
Nocompilejsp:
Adpatch also compiles the java server pages(JSP) after completion of patch application and can be skipped using the option nocompilejsp as below:
$adpatch options=nocompilejsp
Nodatabaseportion:
Nodatabaseportion option is used to skip the adpatch the activity of database driver. It can be used as:
$adpatch options=nodatabaseportion
Nogenerateportion:
Nogenerateportion option is used to skip the adpatch activity of generate driver portion of the patch and you can use the option nogenerateportion as below:
$adpatch options=nogenerateportion
Maintenance Mode disabled:
If you want to apply your adpatch without enabling maintenance mode, you can apply using the option as hotpatch as below:
$adpatch options=hotpatch
Nolink:
Nolink option is used to skip the relinking and can be used as:
$adpatch options=nolink
Nogenform:
Nogenform option is used to skip the generate form file and can be used as:
$adpatch options=nogenform
Maintainmrc:
Maintainmrc is used for adpatch to execute the maintain MRC schema as part of patch. By default maintain MRC is done for standard patch and is disabled for documentation and translation patches.
$adpatch options=nomaintainmrc
Noprereq:
This option is used to skip the checking of pre-requisite patches and by default it checks for pre-requisite patch. This option can be used as below:
$adpatch options=noprereq
Stop the concurrent manager services. Connect to apps user and run cmclean.sql script.
This script can be downloaded from metalink. Remember to commit the script after execution.
Start the CM services and then check the CM. If CM is up then fine else perform the following
================================================================================================
Stop the concurrent manager service....and run the following statement on concurrent manager node
Go to cd $FND_TOP/bin
adrelink.sh force=y "fnd FNDLIBR"
adrelink.sh force=y "fnd FNDSM"
adrelink.sh force=y "fnd FNDFS"
adrelink.sh force=y "fnd FNDCRM"
Start the CM services and then check the CM. Concurrent managers should be up and running fine now.
For Apache, use "ps -ef | grep apache"
For Forms/Reports, use "ps -ef | grep frmweb" and "ps -ef | grep rwrun"
For Concurrent Manager, use "ps -ef | grep FNDLIB"
You can list all application services by using "ps -ef | grep applmgr".
adadmrgpch:
============
creatr "Patch" : /u01/Patch/source patches
Dest : /u01/Patch/Dest_patches
3)$adpatch
Comments
Post a Comment