1. Readme
  2. Readme Information for Oracle Database 12c Release 2 (12.2)
  3. Open Bugs
  4. Oracle Automatic Storage Management (Oracle ASM) Known Bugs

2.13.7 Oracle Automatic Storage Management (Oracle ASM) Known Bugs

These are known bugs for Oracle Automatic Storage Management (Oracle ASM) in Oracle Database 12c Release 2 (12.2).

2.13.7.1 Bug 24805974

In an extended cluster, once the storage split issue has been addressed, the administrator can issue the command crsctl modify site <site_name> -s rejuvenate to rejuvenate the site. This command, however, does not automatically restart Oracle ASM instances or its clients, such as database instances, on the rejuvenated site.

Workaround:

Identify the Oracle ASM instances that should be running on this site and manually issue the srvctl start asm or the srvctl relocate asm command.

2.13.7.2 Bug 20760821

Oracle Database 12c Release 1 (12.1) database instances cannot access disk groups with the COMPATIBLE.ASM attribute set to Oracle Database 12c Release 2 (12.2). If attempted, the following errors are returned: 

ORA-15001: diskgroup %s does not exist or is not mounted
ORA-15040: diskgroup is incomplete

Workaround:

Apply the patch for Bug 20760821 to the Oracle Database 12c Release 1 (12.1) ORACLE_HOME directory.

2.13.7.3 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 12c Release 2 (12.2.0.1):

  • node1 and node2 are upgraded to 12.2.0.1 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 12.2.0.1).

To proceed with the upgrade, start nodes still at 11.2.0.4 only (for example, node3 ornode4, or both) and execute the following command on the Oracle ASM instance on node3 ornode4, or both before starting any 12.2.0.1 nodes: 

ALTER SYSTEM START ROLLING MIGRATION TO '12.2.0.1'

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, one of the Oracle ASM versions fail with either the ORA-15153 or ORA-15163 error message.