1 person found this helpful
Yes , it is the default value. I wont suggest to increase this value .
You can use DBMS_AUDIT_MGMT package for purging the files.
Please check with Oracle support before changing this value.
Yes, you are right, as i've seen on documentation seems that there are no other solutions.
My definitive decision is to keep the default value and to clean the adump directory more frequently.
By the way, In my opinion this is a bad daemon implementation.....
I dont think it is wrong as CRS needs to check resource status every second. Because in case of database , we cannot have more delays to maintain consistency in case of any issue.
Is not wrong the CRS checking every second, is wrong the logging way; one aud file for every check is too much.
I know we talk about two different systems; database and cluster service and when a database is accessed by a SYSDBA account well... it log!
So every check made up by cluster is done with SYSDBA user and for this reason i say "it's wrong".
How can i know when i've a SYSDBA connection different from the "cluster connection"?
The adump directory become useless...
I won't be polemical, i'm only speaking...
Agreed. By default all connections with SYSDBA/SYSOPR are audited and there is no way to disable it.
As of now there is no separate user for CRS to check Database health and all connection are as sysdba only. Ideal way can be for monitoring it can be without sysdba and for start/stop it can be SYSDBA . This functionality is not present as of now and I am not sure if there is a way to fix it. May be to check with Oracle Support if they have plan to introduce this feature
AUDIT_SYS_OPERATIONS Set To FALSE Yet Audit Files Are Generated (Doc ID 308066.1)
I agree with you.
Thanks for all.