My Oracle Support Banner

After Re-Creating the ASM Instance, Old Diskgroup Information Remains (Doc ID 266078.1)

Last updated on FEBRUARY 27, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 and later
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 Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Following the removal and re-creation of an ASM instance, you may see old data left behind from the old ASM instance.

Example:

ls -l /dev/rdsk/<osm>*
-rw-rw-rwT 1 <USER> <GROUP> 524288000 Jul 31 12:03 /dev/rdsk/<osm1>
-rw-rw-rwT 1 <USER> <GROUP> 524288000 Jul 31 12:04 /dev/rdsk/<osm2>

You may also be unable to create an ASM diskgroup with the same name as an old diskgroup and may receive the following errors:

ORA-15018: diskgroup cannot be created
ORA-15033: disk '/dev/rdsk/<osm2>' belongs to diskgroup "<DGNAME>"
ORA-15033: disk '/dev/rdsk/<osm1>' belongs to diskgroup "<DGNAME>"

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.