I believe that the interest is in providing a minimum of code path so that the essential bits of an Oracle database can be most effectively and stably managed by ASM. There does exist an Oracle Clustered File System as well, and I suppose it would be counterproductive to duplicate those features in ASM itself. Finally, there is a bit of a catch twenty-two with the idea of storing diagnostic and administrative files that you might need to view for diagnosis or change to effect repairs when ASM or some key part of the hardware it needs to fully operate is unavailable. Regards, mwf -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of vikram singh Sent: Tuesday, December 26, 2006 11:32 AM To: freelists Subject: ASM - Why doesnt ASM support alert logs and trace files? Hi All, This thing strikes strange that there is no explanation provided in the Oracle docs why Automatic Storage Management (ASM) doesnt support some Operating System files, and administrative files. I was reading http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14231/storeman.h tm#i1023250 The doc suggests that the above files are not supported, but fail to provide any explanation. May be the reason is very obvious, and i missed it. Can anyone please let me know why is this? I repeat my doubt: Why are the administrative files (trace files, alert logs, audit files, export files and so on.) not supported by ASM? Thanks, Vikram.