The aud file of the oracle asm instance is generated in the $ ORACLE_HOME/rdbms/audit directory on the Oracle 10 Gb database server. Check the log file and record all operations performed by sysdba to access the database instance ASM. Www.2cto.com: access the oracle asm instance as sysdba. Whether you enable or disable audit, the system will record the access log in the $ ORACLE_HOME/rdbms/audit directory to generate the *. aud file. Trc code Audit file/u01/app/oracle/product/10.2.0/db/rdbms/audit/ora_2998.aud Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-64bit Production With the Partitioning, OLAP, data Mining and Real Application Testing options ORACLE_HOME =/u01/app/oracle/product/10.2.0/db System name: Linux Node name: db3 Release: 2.6.18-238. el5 Version: #1 SMP Thu Jan 13 15:51:15 EST 2011 Machine: x86_64 In Stance name: + ASM Redo thread mounted by this instance: 0 <none> Oracle process number: 13 Unix process pid: 2998, image: oracle @ db3 (TNS V1-V3) fri Oct 19 09:51:37 2012 LENGTH: '000000' ACTION: [7] 'connect 'database USER: [1] '/'privilege: [6] 'sysdba 'client USER: [6] 'oracle 'client TERMINAL: [0] ''STATUS: [1] '0' www.2cto.com can only use one crontab to automatically clean up these files. 10 *** find/u01/app/oracle/product/10.2.0/db/rdbms/audit/-name "* aud"-exec rm-rf {}\; set to clean up every hour. But then I found a new problem. After cleaning, the log file grew at an astonishing speed. Several files were generated every second, with each file size of 714 bytes. So many files will seriously affect system IO. The connection to the ASM instance cannot be determined.