My Oracle Support Banner

GI on last node: ASM rolling upgrade action failed (Doc ID 1598959.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.


Upgrading to GI, failed on last node

Successfully upgraded the Oracle Clusterware.
Oracle Clusterware operating version was successfully set to

ORA-01034: ORACLE not available

ASM rolling upgrade action failed, see logs for details
Failed to perform last node tasks for ASM rolling upgrade at /ocw/b204/crs/install/ line 9290.
/ocw/b204/perl/bin/perl -I/ocw/b204/perl/lib -I/ocw/b204/crs/install /ocw/b204/crs/install/ execution failed


As ASM is down, tried to start ASM with sqlplus but fails with the following:

$ sqlplus / as sysasm

SQL*Plus: Release Production on Fri Nov 8 19:54:34 2013

Copyright (c) 1982, 2013, Oracle. All rights reserved.

Connected to an idle instance.

SQL> startup
ORA-48108: invalid value given for the diagnostic_dest init.ora parameter
ORA-48140: the specified ADR Base directory does not exist [/ocw/b204/dbs/{ORACLE_BASE}]
ORA-48187: specified directory does not exist
Linux-x86_64 Error: 2: No such file or directory
Additional information: 1



Looking at ASM alert.log, the following was found while running on node1 to set ASM to rolling upgrade mode:



The ASM init.ora/spfile parameter diagnostic_dest wasn't explicitly set before upgrade and default to <Pre-Upgrade-HOME>/log/diag




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

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