This environment is using secure file. There is no backup due to customer ordering wrong hardware from Sun to perform the backup to. Customer tried to add 8 disks to the diskgroup. One of the disks added was slice2 which had the partition table for the disk on it. After the add failed and they realized what had happened they work with System Administrators and according to customer successfully switched slice2 and slice6. After this they used the disks to successfully create dummy diskgroup DATA3. The diskgroup has critical production data and it not mounting is causing the production database not to mount resulting in significant revenue loss for the company. As there presently is no backup of this data and they are using secure file DUL is not an option to extract the data from the failed diskgroup. The diskgroup will not mount because disks that were just added cannot be discovered. Last attempt by customer to use AMDU resulted in core dumps and no AMDU output. Customer is request that the existing disk headers for the disk be repaired so that they can get the diskgroup mounted and then add the correct disks to the diskgroup.   
Refer  http://parnassusdata.com/en/emergency-services  for more info.

If you cannot recover the data by yourself, ask Parnassusdata, the professional ORACLE database recovery team for help.

Parnassusdata Software Database Recovery Team

Service Hotline:  +86 13764045638

E-mail: service@parnassusdata.com