HAPPY NEW YEAR 2021

For Any queries, please mail us at support@funoracleapps.com

Different Status of Cutover and their Meaning on Oracle Apps R12.2

No comments

Different Status of Cutover and their Meaning on Oracle Apps R12.2

The cutover operation is the most critical phase of an online patching cycle. Although other adop operations can be left to run unattended, you should carefully monitor the progress of cutover, so that you can respond quickly in case of any issues. If cutover fails to complete, check log messages for any problems that may require correction. Then try executing the cutover command again. When cutover is re-executed after a previous failure, adop will restart cutover processing at the failure point for any nodes that did not complete, and the processing may be successful this time.

If we run the below script, we can see various status codes for cutover. These can be helpful if the cutover has failed and we need to perform the next steps to fix it.

Script

select NODE_NAME,ADOP_SESSION_ID, PREPARE_STATUS , APPLY_STATUS  ,CUTOVER_STATUS, CLEANUP_STATUS , ABORT_STATUS , STATUS
from AD_ADOP_SESSIONS
order by ADOP_SESSION_ID;


If we see CUTOVER_STATUS column the below will determine the code and status

-->='Y' 'COMPLETED'
--> not in ('N','Y','X') and status='F' 'FAILED'
-->='0' 'CUTOVER STARTED'
-->='1' 'SERVICES SHUTDOWN COMPLETED'
-->='3' 'DB CUTOVER COMPLETED'
-->='D' 'FLIP SNAPSHOTS COMPLETED'
-->='4' 'FS CUTOVER COMPLETED'
-->='5' 'ADMIN STARTUP COMPLETED'
-->='6' 'SERVICES STARTUP COMPLETED'
-->='N' 'NOT STARTED'
-->='X' 'NOT APPLICABLE'




If you like please follow and comment

No comments :

Post a Comment