Exadata Hierarchical Snapshot Database deletion Not Deleting Files And Not Releasing Space from sparse diskgroup (Doc ID 2543844.1)

Last updated on SEPTEMBER 28, 2021

Applies to:

Symptoms

After deleting Hierarchical Snapshot (test Primary) database, data files are still present in sparse disk group and space is not getting released

"Drop the Snapshot Databases" section in "Exadata users guide", does not have specific instructions for Hierarchical Snapshot (test Primary) database.

Changes

Hierarchical Snapshot Database (test Primary) always in READ-ONLY mode and its data files present in SPARSE disk group with symbolic links pointing to RECO / DATA diskgroup where physical copy of source/standby database data files present.

'Snapshot clone' database from this 'Hierarchical Snapshot' (test Primary) can be created and deleted without any issues as snapshot clone database data files are always in READ WRITE mode.

Cause

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