2.6.2 Oracle Automatic Storage Management (Oracle ASM) Known Bugs

These are the Oracle Automatic Storage Management (Oracle ASM) bugs in Oracle Database 18c.

• Bug 12332603
  

2.6.2.1 Bug 12332603

Oracle Automatic Storage Management (Oracle ASM) loses the rolling migration state if Cluster Ready Services (CRS) shuts down on all nodes and the initial version of Oracle ASM is earlier than Oracle Database 12c Release 1 (12.1.0.2).

Workaround:

Consider the following scenario of 4 nodes (node1, node2, node3, and node4) that are at Oracle Database 11g Release 2 (11.2.0.4) and that are being upgraded to Oracle Database 18c:

• node1 and node2 are upgraded to 18c and running.

• node3 and node4 are still at 11.2.0.4 and running.

Now, consider that there is an outage where all CRS stacks are down which leaves the cluster in a heterogeneous state (for example, two nodes at 11.2.0.4 and two nodes at 18c). To proceed with the upgrade, start nodes still at 11.2.0.4 only (for example, node3 or node4, or both) and execute the following command on the Oracle ASM instance on node3 or node4, or both before starting any 18c nodes:

ALTER SYSTEM START ROLLING MIGRATION TO '18.0.0'

Continue the upgrade procedure as already documented from this point forward.

Note that before executing the preceding step to bring the Oracle ASM cluster back into rolling migration, you cannot start two nodes of different versions in the cluster. If you do so, then one of the Oracle ASM versions fail with either the ORA-15153 or ORA-15163 error message.