Oracle has introduced online patching functionality called ADOP(AD Online Patching) in version R12.2.0. Online patching uses the latest feature of the Oracle database 11gR2 which is called “Edition Based Redefinition” and also uses multiple file systems on the application side.During online patching, business application users continue using the Oracle application and simultaneously a patch or a sequence of patches can be applied to another edition of the same database and application. Another edition here means another exact copy of database and application. And once the patching is complete the users are switched over to a patched file system/database in cutover phase by just bouncing middle tier services.
adop online patching utility doesn't require downtime. It involves minimal downtime during cutover phase where switching of filesystems happens.We can apply lot of patches and do cutover any time to minimize downtime.where as in adpatch we just apply patch most of the times by bringing down applications or in hot patch mode.
There are five phases or life cycles of ADOP which are:
1) PREPARE
2) APPLY
3) FINALIZE
4) CUTOVER
5) CLEANUP
Prepare :- Prepares the environment for patching. It involves synchronization of the filesystems fs1 (run ,filesystem) and fs2(patch filesystem), filesystems are inter changeable.
Apply :- Applies the specified patches to the environment. In this phase we can apply all the patches related to application. (Note: These patches need to be copied in fs_ne (non editioned filesystems))
Finalize :- Performs any final steps required to make the system ready for cutover.In this phase we are getting ready for cutover phase.
Cutover :- Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase the involves a brief downtime. In cutover phase the filesystem switchover takes place. Previously the filesystem which was patch filesystem will now become run filesystem.
Cleanup :- Removes obsolete code and data from old editions. In cleanup phase all the obsolute objects gets compiled .
abort - Aborts the online patching cycle by dropping the database patch edition. This phase cannot be specified with any other phase.
fs_clone - Recreates the patch edition file system as an exact copy of the run edition file system. This phase cannot be specified with any other phase. Use of fs_clone is normally not required. Situations that do require fs_clone are will explicitly document that requirement. If running this phase, ensure that your current working directory is not within the patch edition file system.
Steps:-
1. Download the patch and unzip on patch_top.
2. Must go through Readme.html or readme.txt.
3. Prepare the system for patching
a. we can run the .env file . or the adop utility sets its own environment.
b. Then run the below command for prepare the System for patching:
Note: The adop utility sets its own environment. There is therefore no need to source the environment before running it.
$ adop phase=prepare
4. Wait for the prepare phase to be complete.
Please check the status from below points:
$ adop -status
Enter the APPS username: apps
Enter the APPS password:
5. After completion Prepare phase, go to next phase called Apply phase:
$adop phase=apply patches=1234567
adop phase=apply patches=, workers=
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...
6 . After completion of apply phase, goto next phase called Finalize phase:
i.e like Ready the instance for cutover.
Used to perform the final patching operations that can be executed while the application is still online:
$ adop phase=finalize
adop phase=finalize workers= (called automatically)
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...
7. After completion of Finalize phase, goto next phase called Cutover:
Used to perform the transition to the patched environment:
$ adop phase=cutover
adop phase=cutover workers=
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...
Note: Keep checking Status after every Phases.
8. After completion of Cutover phase, run next Cleanup Phase
We can do this step after instance is released to Customer.
Used to remove old objects that are no longer needed:
$adop phase=cleanup
adop phase=cleanup (called automatically)
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Now synchronise the technology level between patch and run fc_clone.
7. adop phase=fs_clone
Note:
If there are some reason either the prepare or apply phase failed or any problems then you can abort this patching cycle.
Used only if the online patching cycle needs to be terminated before completion:
The abort phase can only be run after the prepare phase and before completion of the cutover phase. After the cutover phase completes, it is no longer possible to abort the online patching cycle.
$adop phase=abort
But always remember, after running abort, you must always run a full cleanup as:
$adop phase=cleanup cleanup_mode=full
So, this will remove all columns that were added by the patches but are no longer needed because of the abort.
And If that columns are not removed, then that may create problems in a later patching cycle.
Last two commands for adop
a. adop -help
b. adop -examples
Patch Log Files:-
To review the relevant log files after any patching operation. The adop log files are located on the non-editioned file system (fs_ne), under:
$NE_BASE/EBSapps/log/adop//__//log
adop online patching utility doesn't require downtime. It involves minimal downtime during cutover phase where switching of filesystems happens.We can apply lot of patches and do cutover any time to minimize downtime.where as in adpatch we just apply patch most of the times by bringing down applications or in hot patch mode.
There are five phases or life cycles of ADOP which are:
1) PREPARE
3) FINALIZE
4) CUTOVER
5) CLEANUP
Prepare :- Prepares the environment for patching. It involves synchronization of the filesystems fs1 (run ,filesystem) and fs2(patch filesystem), filesystems are inter changeable.
Apply :- Applies the specified patches to the environment. In this phase we can apply all the patches related to application. (Note: These patches need to be copied in fs_ne (non editioned filesystems))
Finalize :- Performs any final steps required to make the system ready for cutover.In this phase we are getting ready for cutover phase.
Cutover :- Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase the involves a brief downtime. In cutover phase the filesystem switchover takes place. Previously the filesystem which was patch filesystem will now become run filesystem.
Cleanup :- Removes obsolete code and data from old editions. In cleanup phase all the obsolute objects gets compiled .
abort - Aborts the online patching cycle by dropping the database patch edition. This phase cannot be specified with any other phase.
fs_clone - Recreates the patch edition file system as an exact copy of the run edition file system. This phase cannot be specified with any other phase. Use of fs_clone is normally not required. Situations that do require fs_clone are will explicitly document that requirement. If running this phase, ensure that your current working directory is not within the patch edition file system.
Steps:-
1. Download the patch and unzip on patch_top.
2. Must go through Readme.html or readme.txt.
3. Prepare the system for patching
a. we can run the .env file . or the adop utility sets its own environment.
b. Then run the below command for prepare the System for patching:
Note: The adop utility sets its own environment. There is therefore no need to source the environment before running it.
$ adop phase=prepare
4. Wait for the prepare phase to be complete.
Please check the status from below points:
$ adop -status
Enter the APPS username: apps
Enter the APPS password:
5. After completion Prepare phase, go to next phase called Apply phase:
$adop phase=apply patches=1234567
adop phase=apply patches=, workers=
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...
6 . After completion of apply phase, goto next phase called Finalize phase:
i.e like Ready the instance for cutover.
Used to perform the final patching operations that can be executed while the application is still online:
$ adop phase=finalize
adop phase=finalize workers= (called automatically)
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...
7. After completion of Finalize phase, goto next phase called Cutover:
Used to perform the transition to the patched environment:
$ adop phase=cutover
adop phase=cutover workers=
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Please wait. Validating credentials...
Note: Keep checking Status after every Phases.
8. After completion of Cutover phase, run next Cleanup Phase
We can do this step after instance is released to Customer.
Used to remove old objects that are no longer needed:
$adop phase=cleanup
adop phase=cleanup (called automatically)
Enter the APPS password:
Enter the SYSTEM password:
Enter the WLSADMIN password:
Now synchronise the technology level between patch and run fc_clone.
7. adop phase=fs_clone
Note:
If there are some reason either the prepare or apply phase failed or any problems then you can abort this patching cycle.
Used only if the online patching cycle needs to be terminated before completion:
The abort phase can only be run after the prepare phase and before completion of the cutover phase. After the cutover phase completes, it is no longer possible to abort the online patching cycle.
$adop phase=abort
But always remember, after running abort, you must always run a full cleanup as:
$adop phase=cleanup cleanup_mode=full
So, this will remove all columns that were added by the patches but are no longer needed because of the abort.
And If that columns are not removed, then that may create problems in a later patching cycle.
Last two commands for adop
a. adop -help
b. adop -examples
Patch Log Files:-
To review the relevant log files after any patching operation. The adop log files are located on the non-editioned file system (fs_ne), under:
$NE_BASE/EBSapps/log/adop//__//log
No comments:
Post a Comment