ASM diskgroups unmounting, getting ORA-01157: cannot identify/lock data fil

Question

All,
We've recently purchased a RAMSAN device for better throughput. I created the initial diskgroup with the following syntax:
CREATE DISKGROUP EMTPRD0X_SSD01 NORMAL REDUNDANCY
FAILGROUP RS1 DISK '/dev/rdsk_ramsan_primary' NAME ssd_prim
FAILGROUP RS2 DISK '/dev/rdsk_ramsan_backup' NAME ssd_bkup;
and then created a temporary tablespace on top of that diskgroup:
create temporary tablespace temp04 tempfile '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g, '+EMTPRD0X_SSD01' size 25g;
Everything seemed fine at first and then end users started seeing the following errors in the alert log:
SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was mounted
SUCCESS: diskgroup EMTPRD0X_SSD01 was dismounted
Tue Oct 12 16:12:51 2010
Errors in file /opt/oracle/oradump/emtprd02/udump/emtprd02_ora_11578.trc:
ORA-01157: cannot identify/lock data file 3009 - see DBWR trace file
ORA-01110: data file 3009: '+EMTPRD0X_SSD01/emtprd0x/tempfile/temp04.256.732210281'
After talking with Oracle support I was told that the only workaround for diskgroups unmounting themselves is to put a control file/redo log/dummy tablespace inside of that diskgroup and continually write/read from it.
Does that make sense?
They pointed me to note 603204.1 - Why FRA Diskgroup Gets Mounted/Dismounted.
The system is a 3 node Oracle 10.2.0.4 rac running on ASM Solaris x86 64bit.
Any ideas?
Thanks,
Brian

Answer 1

Post Operating System (OS) name & version for DB server system.
Post results of
SELECT * from v$version
My db is not in archivelog mode poor choice
and no backup was taken. Worse choise
Is there any way I can recover this db? Recover as in no data loss?
Very doubtful.
Possible to open with data loss.
01157, 00000, "cannot identify/lock data file %s - see DBWR trace file"
// *Cause:  The background process was either unable to find one of the data
//         files or failed to lock it because the file was already in use.
//         The database will prohibit access to this file but other files will
//         be unaffected. However the first instance to open the database will
//         need to access all online data files. Accompanying error from the
//         operating system describes why the file could not be identified.
// *Action: Have operating system make file available to database. Then either
//         open the database or do ALTER SYSTEM CHECK DATAFILES.What exactly cause this mess?
Edited by: sb92075 on Jan 7, 2010 8:59 PM