We got an issue on in having the DATADG Oracle ASM Diskgroup is missing and cannot be mounted over Oracle Database while both Database servers can see the LUNs on the Operating System level without any issue. Multiple efforts done trying to mount this Disk to Oracle Database, But it seems that this resulted in overwriting the Header of the DATADG ASM Diskgroup.

So the Disk was shown for Oracle as a very New disk/LUN and added as DATA Diskgroup. This resuted in an ASM Diskgroup (Empty) as of being new and without Data. When we referred back to Oracle Special service; They said that the Header of the disk (DATADG) was overwritten and that the file directory metadata were deleted in the Diskgroup.

So we left the system aside for extra activities for retrieving the Data and moved to a temporary solution till we get the data retrieved.

As talked, DBRECOVER can provide the asm diskgroup recovery service, the recovery step is

A. make contract

B. we provide remote recovery service, load data into new database

C. user check the data

DBRECOVER Recovery Options

For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.

When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.

Archive ParnassusData Blog Migration Archive