Are there any limitations with statement/privilege auditing in VigilEnt Audit Manager/VigilEnt Secur (NETIQKB30035)

goal
Are there any limitations with statement/privilege auditing in VigilEnt Audit Manager/VigilEnt Security Agent for Oracle?

fact
VigilEnt Audit Manager for Oracle 3.2 SP1

fact
VigilEnt Audit Manager for Oracle 3.2 SP6

fact
VigilEnt Audit Manager for Oracle 4.0 SR2

fact
VigilEnt Audit Manager for Oracle 4.0 SP3

fact
VigilEnt Security Agent for Oracle 1.0

fact
VigilEnt Security Agent for Oracle 1.0 SR1

fact
VigilEnt Security Agent for Oracle 1.0 SR2

fact
VigilEnt Security Agent for Oracle 1.0 SP3

fact
VigilEnt Security Agent for Oracle 1.0 SP4

fix
The native Oracle auditing options for statements and privileges are sometimes limited to one type of auditing. In some cases, the auditing will be either By Session or By Access. Therefore, if Oracle native auditing only supports "By Session" auditing for a specific statement or privilege, and an attempt is made with VigilEnt Audit Manager for Oracle to set it to "By Access," then the default "By Session" auditing would be used.

note
Reference the Oracle documentation for more information on auditing or whether a specific statement or privilege is limited to one type of auditing.

Formerly known as NETIQKB30035