Svetoslav,
Thank you! I checked our datafiles. They are all in the DATA diskgroup:
SQL> select name from v$asm_diskgroup;
NAME
------------------------------
DATA
DBFS_DG
RECO
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination +RECO
...
SQL> select distinct substr(name,1,20) from v$datafile;
SUBSTR(NAME,1,20)
-------------------------------------------------------
+DATA/exacp2/datafil
It's possible that at some point in time, we temporarily created a datafile in
the RECO disk group. But I don't think that could have caused our problem.
There may be other cases where the default caching policy is 'none' instead of
'default'. But thanks for pointing out this Oracle note.
Yong Huang
----- original message -----
Yong, Oracle released a similar note today:
Oracle Data Files should not be placed on the +RECO ASM diskgroup (Doc ID
2074156.1)
If you upgrade from ESS less than 11.2.3.2.0 the cachingPolicy for RECO
diskgroup will be changed from default to none but should be kept default
for DATA.
--
//www.freelists.org/webpage/oracle-l
