Fleet: In UPDATE_DB Operation Closing All Blackouts Associated With The Targets Which Is Created Manually Outside Fleet Operations.
(Doc ID 2810848.1)
Last updated on DECEMBER 01, 2021
Applies to:
Enterprise Manager for Oracle Database - Version 13.4.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
A manual blackout is created before a Fleet UPDATE_DB patching operation.
When the UPDATE_DB operation stops the Fleet blackout created during patch appliation, it also stops the manually blackout created before the Fleet operation.
#############################################################
Job Name: STOP_BLACKOUT_C77D2A72CF9C197BE05365FE3C0A8D20
Step Name: evaluateExpression
Step Status: Succeeded
Start Time: 19/07/2021 16:16:11
Start Time: 19/07/2021 16:18:45
Job OutPut:
Stopping blackout...
Stopping blackout for : 8196D428CC95D422AEE983B7D81F9479Blackout stopped.. ======> Blackout GUID created Manually
Stopping blackout for :
F606A49A87488D5E79D36BC9DE32A0A4Blackout stopped..Step: Stop blackout for Database Targets to be patched has been executed successfully. ======> Blackout GUID created by Fleet Operation
#############################################################
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |