1)Distributed AD offers improved scalability, performance, and resource utilization by allowing workers of the same AD session to be started on additional middle tier systems.
2)AD has always utilized a Parallel Jobs System, where multiple AD workers start and are assigned jobs. Information for the Jobs System is stored in the oracle database, and workers receive their assignments by monitoring certain tables in the database.
3) Distributed AD allows workers to be started on remote machines, where they can utilize the resources on the remote machines when completing their assigned jobs
Prerequisites
1) Shared APPL_TOP
2) AD.H
Working
On one of your shared APPL_TOP nodes, start your AutoPatch(adpatch) or AD Administration session(adadmin) with the following command line options:
localworkers= workers=
For example to run an AutoPatch session with 3 workers on the local node and 5 workers on a remote node:
adpatch localworkers=3 workers=8
On one or more of the additional shared APPL_TOP nodes, start an AD Controller session with the following command line option:
adctrl distributed=y
After providing basic information, AD Controller will prompt for the worker number(s) to be started. For example, enter “4 5 6 7 8” or “4-8” to start workers 4 through 8. If AD Controller is started prior to AutoPatch or AD Administration starting the Jobs System, AD Controller will ask if you want to wait. Choosing yes will cause AD Controller to wait until the Jobs system is started, at which point it will start the appropriate worker processes. If an AutoPatch session has already been started, AD Controller will wait automatically.
Example of a two node session with five workers:
Node 1) adpatch localworkers=30 workers=20 Node 2) adctrl distributed=y and choose Enter the worker range 21-30
For R12.2,Things remains same, we just need to use adop in place of adpatch
Example 1 – Distribute a total of eight workers across a two-node system
1. To begin, enter a command that will run an adop session with three workers on the
primary node and five workers on secondary nodes:
$ adop phase=apply input_file=myinput.txt
The file myinput.txt will need to include the lines:
workers=8
localworkers=3
2. Now start an AD Controller session on each of the secondary nodes that will run
workers, using the distributed=y argument.
$ adctrl distributed=y
- To start workers 4 through to 8 on a secondary node, enter “4-8” in response to the
prompt from AD Controller:
Enter the worker range: 4-8
Example 2- Distribute a total of twelve workers across a three-node system
1. To begin, enter a command that will run an adop session with four workers on the
primary node and eight workers on secondary nodes:
$ adop phase=apply input_file=myinput.txt workers=12 localworkers=4
The file myinput.txt will need to include the lines:
workers=12
localworkers=4
2. Now start an AD Controller session on the second node, specifying that workers 5-8
should run there:
$ adctrl distributed=y
Enter the worker range: 5-8
3. Finally, start AD Controller on the third node, specifying that the last four workers
(9-12) should run there:
$ adctrl distributed=y
Enter the worker range: 9-12
Related Articles
Oracle patching: Adpatch Complete Overview
31 Useful adop (AD online patching ) command line for R12.2
Adop(Ad online patching utility) explained R12.2
40 Adpatch question every DBA should know