What Happens during adop cutover Phase?

Cutover Phase Requires a brief downtime.


Following activities occur during Cutover:


+Users are logged off the system
+Finalize is run as part of cutover -if not run earlier in adop cycle
+Cutover phase cancels ADZPPATCH Concurrent Program
+Stops all Services on RUN and PATCH editions , switches filesystem and starts services on new RUN FS
+Flipping snapshots in run and patch editions.
+Users are brought back online on the patched system 


Environment is changed after cutover. Need to Re-source the env, for performing any actions after cutover.


Syntax:


$ adop phase=cutover


Multi-node Considerations
========================
By default cutover is invoked automatically on remote nodes.
If you want cutover individually:      
1. First node the cutover should be:           
$ adop phase=cutover allnodes=no       
2. For all other nodes you should do:        
$ adop phase=cutover allnodes=no action=nodb           
 * nodb because db work is already done




Cutover Parameters:
===================


mtrestart :Specifies whether or not to start Mid-Tier services at end of cutover, it allows you to perform some additional maintenance operations in the system before bringing it up.        – Takes values “yes” or “no”.        – Default: yes
allnodes : Specifies whether or not to run on all the nodes.        – Takes values “yes” or “no”.        – Default: yes
action: Specifies whether or not to take database action        – Takes values “db” or “nodb”        – Default: db

Leave a Reply

Your email address will not be published. Required fields are marked *