Using Distributed AD
In my last post i talked about implementing a Shared Application Tier Filesystem. On of the important advantages of this is that ability to drastically reduce your patching down time by using the concept ofDistributed AD.My current post talks about using distributed AD.The main concept behind distributed AD is that you can run part of your workers on one node and distribute the remaining among other nodes which share the same application tier filesystem for applying the same patch. This results in an improved performance and helps in reducing your downtime related to patching.
Two important pre requisites for using Distributed AD are
- You must have AD Minipack H (patch 2673262)
- You must have implement either a shared application tier filesystem or a shared APPL_TOP
Assuming i have implemented a Shared Application Tier Filesystem between Node A and Node B i could apply the ATG RUP 4 Patch using distributed AD in the following way.
On Node A i start the adpatch session after putting my system in maintenance mode. To start adpatch in a distributed mode you can use the localworkers and workers parameter.
On Node A
su – applsam
$adpatch localworkers=4 workers=8
Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
Oracle Applications AutoPatch
Version 11.5.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 ‘/s01/apps/samappl’.
Is this the correct APPL_TOP [Yes] ?
AutoPatch records your AutoPatch session in a text file
you specify. Enter your AutoPatch log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adpatch.log] : sampt04.log
Num Workers = 8.
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 [SAM] : SAM *
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 [samlx01] : samlx01 *
You are about to apply a patch to the installation of Oracle Applications
in your ORACLE database ‘SAM’
using ORACLE executables in ‘/s01/apps/samora/8.0.6′.
Is this the correct database [Yes] ?
AutoPatch 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] :
AutoPatch is verifying your username/password.
The status of various features in this run of AutoPatch 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
Identifier for the current session is 1781
Reading product information from file…
Reading language and territory information from file…
Reading language information from applUS.txt …
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 : [11i.AD.I.4]
Trying to obtain a lock…
Attempting to instantiate the current-view snapshot…
Was already instantiated. So no instantiation done this time.
**************** S T A R T O F U P L O A D ****************
Start date: Wed Feb 21 2007 01:20:10
0 “left over” javaupdates.txt files uploaded to DB: Wed Feb 21 2007 01:20:10
0 patches uploaded from the ADPSV format patch history files: Wed Feb 21 2007 01:20:10
Uploading information about files copied during the previous runs …
0 “left over” filescopied_<session_id>.txt files uploaded to DB: Wed Feb 21 2007 01:20:10 ****************** E N D O F U P L O A D ******************
End date: Wed Feb 21 2007 01:20:10
Enter the directory where your Oracle Applications patch has been unloaded
The default directory is [/s01/apps/4676589] :
Please enter the name of your AutoPatch driver file : u4676589.drv
On Node B
You can start adctrl on node b in a distributed mode by using the distributed parameter. It will prompt for the number of works you need to run on this node at which you can specify the range
$su – applsam
$adctrl distributed=y
Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA
AD Controller
Version 11.5.0
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.
Attention: AD Controller 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 ‘/s01/apps/samappl’.
Is this the correct APPL_TOP [Yes] ?
AD Controller records your AD Controller session in a text file
you specify. Enter your AD Controller log file name or press [Return]
to accept the default file name shown in brackets.
Filename [adctrl.log] :adcrtls03.log
************* Start of AD Controller session *************
AD Controller version: 11.5.0
AD Controller started at: Wed Feb 21 2007 12:49:12
APPL_TOP is set to /s01/apps/samappl
Reading product information from file…
Reading language and territory information from file…
Reading language information from applUS.txt …
Enter the ORACLE username of Application Object Library [APPLSYS] :
Enter the ORACLE password of Application Object Library [APPS] :
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
Enter contiguous range of workers to run on this machine
Enter the worker range:5-8
Waiting…
The workers will be in waiting state till all pre requisite steps are finished by the adpatch session on the first node.
Managing the workers
You can see the status of all your works both local and remote using adctrl from any of the nodes.
Control
Worker Code Context Filename Status
—— ——– ———————- ——————– ————–
1 Run AutoPatch R115 alalrt.odf Running
2 Run AutoPatch R115 afflex.odf Running
3 Run AutoPatch R115 afcmgr.odf Running
4 Run AutoPatch R115 ecepoo.odf Running
5 Run AutoPatch R115 afmisc.odf Running
6 Run AutoPatch R115 afform.odf Running
7 Run AutoPatch R115 ecxbase.odf Running
8 Run AutoPatch R115 afatch.odf Running
All the options of adcrtl hold good in a distributed AD environment.
Restarting a Failed worker
You can restart a failed worker from any of the nodes irrespective of the fact where the worker was actually running
Worker Code Context Filename Status
—— ——– ———————- ——————– ————–
1 Run AutoPatch R115 Wait
2 Run AutoPatch R115 afcmgr.odf FAILED
3 Run AutoPatch R115 Wait
4 Run AutoPatch R115 Wait
5 Run AutoPatch R115 Wait
6 Run AutoPatch R115 Wait
7 Run AutoPatch R115 Wait
8 Run AutoPatch R115 Wait
In the above case worker 2 has failed which has been running on node BThis can be restarted from either of the nodes after fixing the problem, using the option 2 from the adcrtl menu ‘Tell worker
to restart a failed job’
Using Distributed AD
No comments:
Post a Comment