My Oracle Support Banner

OEM 13C: Fleet: UPDATE_GI Failed To Start Databases Due To Cluster Kept In "The cluster upgrade state is [UPGRADE AV UPDATED]" State (Doc ID 3014478.1)

Last updated on APRIL 19, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.20.0.0.0 and later
Information in this document applies to any platform.

Symptoms

In Enterprise Manager (EM) Cloud Control, Fleet UPDATE_GI failed to start databases as cluster upgrade state is [UPGRADE AV UPDATED]

Command :
$ emcli db_software_maintenance -performOperation -name="Update GI" -purpose=UPDATE_GI -target_type=cluster -target_list="<target_name>" -normal_credential="GRID:SYSMAN"
- privilege_credential="ROOT:SYSMAN"

Job Step Log :
> CLSRSC-180: An error occurred while executing the command '/opt/oracle/gi/product/19.0.0/grid/bin/srvctl start asm -proxy'
>End Command output
2021-11-18 17:15:38: CLSRSC-180: An error occurred while executing the command '/opt/oracle/gi/product/19.0.0/grid/bin/srvctl start asm -proxy'
2021-11-18 17:15:39: Failed to start asm proxy; counter = 0
2021-11-18 17:15:39: Executing cmd: /opt/oracle/gi/product/19.0.0/grid/bin/clsecho -p has -f clsrsc -m 373
2021-11-18 17:15:39: Executing cmd: /opt/oracle/gi/product/19.0.0/grid/bin/clsecho -p has -f clsrsc -m 373
2021-11-18 17:15:39: Command output:
> CLSRSC-373: Failed to start ASM proxy instance

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.