-
Hi,
What purpose does audit_trial=OS serve; any way whether you
set it to OS or not it is going to auditing and generate the os files.....
Could any body guide me...... does this generate any extra information.
Regards
sonia
-
Your audit information is saved in OS, outside the database when you set AUDIT_TRAIL=OS
Sanjay
-
No sanjay.....what i meant to say was whether u set it to
OS or not, anyway ORACLE is going to write into audit file
at the OS level...then what is the use of it ?
[Edited by sonia on 09-18-2002 at 03:16 AM]
-
you know the difference between trace and audit files???
-
Hello,
Auditing option allows you to collect some information related to DML, DLL, connections ... (Suspicious or normal Database Activity). You can store data collect in the database (in SYS.AUD$ table) or in an OS file (OS level).
Hope this help
-
Yes noor,
What i am trying to say is irrespective of setting it to OS or DB, audit files are always generated in the path specified by audit_file_dest.....
So what for is this audit_tria=OS....
-
it´s obvious you have not read the docs
quote:
Events Audited by Default
Regardless of whether database auditing is enabled, Oracle will always audit certain database-related actions into the operating system audit trail. These events include the following:
Instance startup
An audit record is generated that lists the OS user starting the instance, the user's terminal identifier, the date and time stamp, and whether database auditing was enabled or disabled. This is stored in the OS audit trail because the database audit trail is not available until after startup has successfully completed. Recording the state of database auditing at startup also prevents an administrator from restarting a database with database auditing disabled (so they can perform unaudited actions).
Instance shutdown
An audit record is generated that lists the OS user shutting down the instance, the user's terminal identifier, the date and time stamp.
Connections to the database with administrator privileges
An audit record is generated that lists the OS user connecting to Oracle as SYSOPER or SYSDBA, to provide accountability of users with administrator privileges.
-
Originally posted by sonia
No sanjay.....what i meant to say was whether u set it to
OS or not, anyway ORACLE is going to write into audit file
at the OS level...then what is the use of it?
If you set AUDIT_TRAIL=OS whatever auditing you turn on, will be saved to OS files but if you set it to DB, the information will go to sys.aud$ (other than default audit, as pando mentioned)
Sanjay
[Edited by SANJAY_G on 09-18-2002 at 04:27 AM]
-
Originally posted by pando
it´s obvious you have not read the docs
quote:
Events Audited by Default
Regardless of whether database auditing is enabled, Oracle will always audit certain database-related actions into the operating system audit trail. These events include the following:
Instance startup
An audit record is generated that lists the OS user starting the instance, the user's terminal identifier, the date and time stamp, and whether database auditing was enabled or disabled. This is stored in the OS audit trail because the database audit trail is not available until after startup has successfully completed. Recording the state of database auditing at startup also prevents an administrator from restarting a database with database auditing disabled (so they can perform unaudited actions).
I'm starting to understand this aspect of auditing, but I don't see the information about whether auditing was disabled or enabled at startup in the audit file. The only I see in the audit record about the startup is this:
....
Wed Jan 5 12:34:24 2005
ACTION : 'STARTUP'
DATABASE USER: '/'
PRIVILEGE : SYSDBA
CLIENT USER: jsmith
CLIENT TERMINAL: Not Available
STATUS: 0
...
So where's the info about auditing being on or off at startup??
-
Originally posted by dbbyleo
I'm starting to understand this aspect of auditing, but I don't see the information about whether auditing was disabled or enabled at startup in the audit file. The only I see in the audit record about the startup is this:
....
Wed Jan 5 12:34:24 2005
ACTION : 'STARTUP'
DATABASE USER: '/'
PRIVILEGE : SYSDBA
CLIENT USER: jsmith
CLIENT TERMINAL: Not Available
STATUS: 0
...
So where's the info about auditing being on or off at startup??
what your saw is exactly what pando is referring to
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|