AD UTILITES

AD_TOP is product in Aplication which is under directory /tlcc/apps/apps_st/appl/ad/12.0.0

AD Utility :AD Utilities are a group of tools designed to install, upgrade, maintain, and patch applications.

ADPATCH is a utility that is used to apply individual patches, mini-packs, or maintenance packs to an Oracle Applications instance.

ADADMIN AD Administration (adadmin) is used performs maintenance/administration tasks on an Oracle Apps Instance. Task associated with adadmin are divided into two broad categories database and file system task.

ADCTRL Utility to determine status of worker (started by ad patch , adadmin or other ad utility) and to control ( restart/drop/skip) workers.

ADRELINK Used to relink apps executables with product libraries , if some library definition is changed or executable is corrupted.

ADMRGPCH To merge different patches & create single patch . This is helpful when you have too many patches , you can merge them & apply in one shot.

ADCLONE Utility to clone Instance from Test to Prod, Vice Versa

ADCONFIG To configure different components in Applications like changing port number or domain name or increasing number of JVM's

ADIDENT Utility to find version of a file in oracle applications (Identification )

ADLICMGR To license a product in applications , you might have license to use only 10 products initially then later decided to use 5 more so license them first by this utility

ADSPLICE You add a product in application, by default you might have 90-105 ( may be more ) products like AP, GL, AR and now oracle released one more product so add this product using this utility .
Using adadmin
Example:
[apdlcc@lcctest ~]$ 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 '/dlcc/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ?YES
Filename [adadmin.log] :
Do you wish to activate this feature [No] ?NO
Please enter the batchsize [1000] : Press Enter (Batch Size By default 1000 Only)
using ORACLE executables in '/dlcc/apps/tech_st/10.1.2'.

Is this the correct database [Yes] ? YES Just Check UR in TLCC 0r DLCC
Enter the password for your 'SYSTEM' ORACLE schema: MANAGER
Enter the ORACLE password of Application Object Library [APPS] :APPS

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] :
If u Select 1 Means generate some applications files like message,form,report,JAR

Generate Applications Files
----------------------------------------

1. Generate message files

2. Generate form files

3. Generate report files

4. Generate product JAR files

5. Return to Main Menu


If u Select 2 Means Maintain Applications Relink,Copy, Snapshot etc
Maintain Applications Files
----------------------------------------

1. Relink Applications programs

2. Copy files to destinations

3. Convert character set

4. Maintain snapshot information

5. Check for missing files

6. Return to Main Menu

If u Select 3 Means Compilation
Compile/Reload Applications Database Entities
---------------------------------------------------

1. Compile APPS schema

2. Compile menu information

3. Compile flexfields

4. Reload JAR files to database

5. Return to Main Menu



If u Select 4 Means Maintain Applications


Maintain Applications Database Entities
---------------------------------------------------

1. Validate APPS schema

2. Re-create grants and synonyms for APPS schema

3. Maintain multi-lingual tables

4. Check DUAL table

5. Return to Main Menu

If u Select 5 means Change Maintenance Mode

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

Now we discus How to Apply the patch using ad patch

Patch applying is an Major AppsDBA Activity



Shutdown the Application server after that enable maintenance mode using adadmin

1)Download the Patch
2)Using FTP Move to the PATCH_TOP Directory

PATCH_TOP:/tlcc/apps/patches or /dlcc/apps/patches
3) Unzip the Patch
Afterr unzipping it create and Directory for that Patch number
Ex:unzip p12345.zip
12345
4) Go to 12345
5) [apdlcc@lcctest 6836355]$adpatch

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA

Oracle Applications AutoPatch

Version 12.0.0

NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.


Attention: AutoPatch no longer checks for unapplied pre-requisite patches.
You must use OAM Patch Wizard for this feature. Alternatively, you can
review the README for pre-requisite information.


Your default directory is '/dlcc/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes] ? YES
Filename [adpatch.log]:patchnumber.log
Do you wish to activate this feature [No] No
Please enter the batch size [1000]:1000
Using ORACLE executables in '/dlcc/apps/tech_st/10.1.2'.

Is this the correct database [Yes] YES
Enter the password for your 'SYSTEM' ORACLE schema: manager
Enter the ORACLE password of Application Object Library [APPS]: APPS

Your default directory is '/dlcc/apps/patches/patchnumber': Press Enter
Please enter the name of your Auto Patch driver file [patch.drv]:u12345.drv
Do you want to continue with Auto Patch [Yes]? YES
Enter the number of parallel workers [16]:

Patch Process going on……

How to tell if a patch completed successfully
If ad patch completes successfully, it will first spool out the contents of the readme.txt file, then display a message like the following.
Auto Patch is complete
You should check the file /u02/applmgr/PROD/install/log/D762433.log
for errors.
Resolving Patching Problems:
Reviewing Log Files:
Location of patchlogfile: $APPL_TOP/admin/SID/log
Mostly we are facing worker failures only in logfile mention which worker is failed
Go to that workerlog is like adwork004.log
Location of worker log:$APPL_TOP/admin/SID/log

The administrative tool used to manage patch workers is AD Control(adctrl)

[apdlcc@lcctest log]$ adctrl

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA

AD Controller

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 '/dlcc/apps/apps_st/appl'.
Is this the correct APPL_TOP [Yes]: YES
Filename [adctrl.log] : xxxx.log
Enter the ORACLE username of Application Object Library [APPLSYS] :APPLSYS
Enter the ORACLE password of Application Object Library [APPS] :APPS
AD Controller Menu
---------------------------------------------------

1. Show worker status

2. Tell worker to restart a failed job

3. Tell worker to quit

4. Tell manager that a worker failed its job

5. Tell manager that a worker acknowledges quit

6. Restart a worker on the current machine

6. Exit

To execute an adctrl menu option, simply type the menu option and press Enter. If options 2–6 are chosen, either specifies the number of the worker that requires action, or presses Enter for the action to be executed for all workers.
The “Skip Worker” menu option is a hidden adctrl menu option. If a worker needs to be skipped, start adctrl, enter 8, and then enter the worker number. Only use this option if advised by Oracle Support.

If you want to restart the patch first go to
$cd $APPL_TOP/admin/SID $mv restart restart_old $mkdir restart
After cleaning up the restart files, you may then restart the adpatch session using adpatch.



CLONING PROCESS:

Cloning is process of creating replica of your source apps R12 Instance ( lets say you have one apps Instance with name TLCC and you want to create similar instance ( including same patches & user data) like DLCC then you will use adclone utility (Also called as Rapid Clone these days). In this case source Instance will be TLCC and target Instance will be DLCC.So here I am putting broad level steps you will use to clone apps instance .

Step1 . Prerequisites Steps you do before start cloning using rapid clone

1.1 Verify source and target nodes software versions

1.2 Apply the latest AutoConfig Template patch

1.3 Apply the latest Rapid Clone patches

Step2 . Clone Source to Target

2.1 Run preclone on DB tier
location: /tlcc/db/tech_st/10.2.0/appsutil/scripts/TLCC_lcctest
perl adpreclone.pl

2.2 Run preclone on Apps or middle tier
location: /tlcc/inst/apps/TLCC_lcctest/admin/scripts
perl adpreclone.pl

2.3 Copy source file system to target file system2.4 Configure db tier2.5 Configure apps/middle tier

Step 3 Finishing Task

3.1 Update profile options

3.2 Update printer settings (If printers are not configured or you don't want to use printer you can skip this step)

3.3 Update workflow configuration settings (Important)Related Metalink Note # 230672.1