Oracle® Audit Vault Administrator's Guide Release 10.2.3.2 Part Number E14459-11 |
|
|
PDF · Mobi · ePub |
Use the Audit Vault Oracle Database (AVORCLDB
) command-line utility to manage the relationship between Oracle Audit Vault and an Oracle source database and collector. When you run these commands, remember the following:
Enter the command in lowercase letters. The commands are case-sensitive.
On UNIX systems, when you open a new shell to run a command, first set the appropriate environment variables. See Section 2.2.2 and Section 2.2.3 for more information.
On Microsoft Windows systems, do not set any environment variables. Instead, run the command from the Audit Vault Server or collection agent ORACLE_HOME
\bin
directory.
Oracle Audit Vault creates a log file of AVORCLDB command activity. See Section A.1 and Section A.2 for more information.
Table 8-1 describes the AVORCLDB
commands and where each is used, whether on the Audit Vault Server, on the Audit Vault collection agent, or in both places.
Table 8-1 AVORCLDB Commands
Command | Where Used? | Description |
---|---|---|
Server |
Adds a collector to Oracle Audit Vault |
|
Server |
Registers an audit source with Oracle Audit Vault |
|
Server |
Alters the attributes of a collector |
|
Server |
Alters the attributes of a source |
|
Server |
Drops a collector from Oracle Audit Vault |
|
Server |
Drops a source database from Oracle Audit Vault |
|
Both |
Displays help information for the |
|
Collection agent |
Adds the source user credentials to the wallet, creates a database alias in the wallet for the source user, verifies the connection to the source using the wallet, and updates the |
|
Both |
Verifies that the source is compatible with the collectors that are specified for setup |
The AVORCLDB
command-line utility, which you use to configure an Oracle database with Oracle Audit Vault.
Syntax
avorcldb command -help avorcldb command [options] arguments
Arguments
Argument | Description |
---|---|
command |
Enter one of the commands listed in Table 8-1. |
arguments |
Enter one or more of the AVORCLDB command arguments. |
-help |
Displays help information for the AVORCLDB commands. |
Usage Notes
Issuing an AVORCLDB
command generates the following log file: $ORACLE_HOME/av/log/avorcldb.log
.
The avorcldb add_collector
command adds a collector for the given Oracle source database to Audit Vault. Oracle Audit Vault verifies the source database for the collector requirements.
Where to Run This Command
Audit Vault Server:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2.
Microsoft Windows: Go to the Audit Vault Server ORACLE_HOME
\bin
directory.
Syntax
avorcldb add_collector -srcname srcname -agentname agentname -colltype [OSAUD,DBAUD,REDO] [-collname collname] [-desc desc] [-av host:port:service] [-instname instname] [-orclhome orclhome]
Arguments
Argument | Description |
---|---|
-srcname srcname |
Enter the source database name for which the collector is to be added. This source name was displayed after you ran the avorcldb add_source command.
Remember that the source database name is case-sensitive. |
-agentname agentname |
Enter the name of the collection agent that was created when you ran the avca add_agent command. (In most cases, this is the agent that you created when you installed the Audit Vault collection agent, as described in Oracle Audit Vault Collection Agent Installation Guide.)
If you are not sure of the agent name, then you can find it as follows: Log in to the Audit Vault Console, click the Configuration tab, and then click the Agent tab to display the Agents page. The name of the agent is displayed in the Agent column. |
-colltype colltype |
Enter the collector type to be added.
See Table 1-5 for more information about the collector types. |
-collname collname |
Create a name for the collector. Optional. If you do not create a name, Oracle Audit Vault names the collector colltype _Collector (for example, OSAUD_Collector for the OSAUD collector type). |
-desc desc |
Enter a brief description of the collector. Optional. |
-av host : port : service |
Enter the connection information for Oracle Audit Vault used for the database link from the source database to Oracle Audit Vault. You must include this argument if the -colltype argument is REDO; otherwise, this argument is optional. |
-instname instname |
Enter the instance name of Audit Vault Oracle RAC installation. You must include this argument if you are adding multiple OSAUD collectors, that is, one collector for each database instance. |
-orclhome orclhome |
Enter the Oracle home of the source database.You must include this argument if the -colltype argument is OSAUD; otherwise, this argument is optional. See the usage notes. |
Usage Notes
Run any collector-specific preparation scripts before you run the avca add_collector
command.
On Microsoft Windows systems, specifying the OSAUD collector type automatically includes the event log and XML audit trails.
When specifying the value for the -orclhome
argument, enter the value as either a quoted string using a backslash. For example:
-orclhome "c:\app\oracle\product\10.2.3\av_1"
Alternatively, enter it as a nonquoted string using a slash. For example:
-orclhome c:/app/oracle/product/10.2.3/av_1
There is a 2 gigabyte audit file size limit for the OSAUD collector to be able to collect audit records from audit trails stored in files, which includes the SYSLOG
, .AUD
, and .XML
files. If the file size is greater than 2 gigabytes, then the OSAUD collector ignores all audit records beyond 2 gigabytes. To control the size of the operating system audit trail and select the audit trail type to set, set the DBMS_AUDIT_MGMT.OS_FILE_MAX_SIZE
property and the DBMS_AUDIT_MGMT.AUDIT_TRAIL_TYPE
type by using the DBMS_AUDIT_MGMT.SET_AUDIT_TRAIL_PROPERTY
PL/SQL procedure. See Oracle Database Security Guide for more information.
You can create a collection agent to remotely collect from a source database on a different server, but this collection agent cannot collect audit data from users who have logged in with the SYSDBA
or SYSOPER
privilege.
To configure collection agents to listen to Oracle Real Application Clusters (Oracle RAC) nodes, see Section 4.7.
To modify the collector, use the avorcldb alter_collector
command (Section 8.4).
Example
The following example shows how to add an OSAUD collector to Oracle Audit Vault on Linux and UNIX platforms in an Oracle Real Application Clusters (Oracle RAC) installation using the -instname
argument.
avorcldb add_collector -srcname orcl -agentname kuksagruvin_os -colltype OSAUD -collname OSAUD_Collector -instname av01 -orclhome /u01/app/oracle/product/10.2.0/db_1 source hr_db verified for OS File Audit Collector collector Adding collector... Collector added successfully. collector successfully added to Audit Vault remember the following information for use in avctl Collector name (collname): OSAUD_Collector
This example shows how to add a DBAUD collector to Oracle Audit Vault:
avorcldb add_collector -srcname source1db.example.com -agentname kuksagruvin_dbuaud -colltype DBAUD source hr_db verified for Aud$/FGA_LOG$ Audit Collector collector Adding collector... Collector added successfully. collector successfully added to Audit Vault remember the following information for use in avctl Collector name (collname): DBAUD_Collector
The next example shows how to add a REDO collector to Oracle Audit Vault.
avorcldb add_collector -srcname source1db.example.com -agentname kuksagruvin_redo -colltype REDO -av system1.example.com:1521:av source hr_db verified for REDO Log Audit Collector collector Adding collector... Collector added successfully. collector successfully added to Audit Vault remember the following information for use in avctl Collector name (collname): REDO_Collector initializing REDO Collector setting up APPLY process on Audit Vault server setting up CAPTURE process on source database
The avorcldb add_source
command registers an Oracle source database with Oracle Audit Vault for audit data consolidation. Run this command on the Audit Vault Server.
Where to Run This Command
Audit Vault Server:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2.
Microsoft Windows: Go to the Audit Vault Server ORACLE_HOME
\bin
directory.
Syntax
avorcldb add_source -src host:port:service [-srcname srcname] [-desc desc] [-agentname agentname]
Arguments
Argument | Description |
---|---|
-src host : port : service |
Enter the source database connection information: host name, port number, and service ID (SID), separated by a colon.
If you are unsure of this connection information, run the |
-srcname srcname |
Enter the name of the source database. Remember that the source database name is case-sensitive. Optional.
If you do not specify this argument, then Oracle Audit Vault uses the global database name.You can check this name by querying the SQL> SELECT * FROM GLOBAL_NAME; |
-desc desc |
Enter a brief description of the source database. Optional. |
-agentname agentname |
Enter the name of the agent. If you omit this name, then Oracle Audit Vault uses the name of the agent that you created during the agent installation process. Optional. |
Usage Notes
The global database name of the source database is used as the default source name in Oracle Audit Vault. You can provide a different name if you want.
The avorcldb add_source
command prompts for the source user name and password. This user account must exist on the source database.
To find this user, query the SESSION_PRIVS
and SESSION_ROLES
data dictionary views. The source user should have the privileges and roles that are listed in the zarsspriv.sql
file, such as the CREATE DATABASE LINK
privilege and DBA
role.
If the AVORCLDB_SRCUSR
environment variable is set to this user account and password, then you can bypass the Enter Source user name
and Enter Source password
prompts. If you do specify these values, they override the environment variable.
You must specify the -agentname
agentname
parameter so that auditors can configure policy management using the Audit Vault Console.
Example
The following example shows how to register a source database with Oracle Audit Vault.
avorcldb add_source -src hrdb.example.com:1521:orcl -srcname hr_db -agentname agent1 Enter Source user name: username Enter Source password: password Adding source... Source added successfully. source successfully added to Audit Vault remember the following information for use in avctl Source name (srcname): hr_db Credential stored successfully Mapping Source to Agent...
The avorcldb alter_collector
command modifies the attributes of an Oracle Database collector.
Where to Run This Command
Audit Vault Server:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2.
Microsoft Windows: Go to the Audit Vault Server ORACLE_HOME
\bin
directory.
Syntax
avorcldb alter_collector -srcname srcname -collname collname [attrname=attrvalue...attrname=attrvalue]
Arguments
Argument | Description |
---|---|
-srcname srcname |
Enter the name of the source database to which this collector belongs. Remember that the source database name is case-sensitive. |
-collname collname |
Enter the name of the collector to be modified. |
attrname = attrvalue |
Enter the attribute pair (attribute name, new attribute value) for mutable collector attributes for this collector type. This argument is optional.
Enclose the attribute value in double quotation marks. For multiple values, enclose the entire set in double quotation marks and separate each value with a space. For example: ...="value1 value2 value3" |
Usage Notes
You can modify one or more collector attributes at a time. The following tables list the collector attributes (parameters) by collector type, whether the parameter is mutable, and its default value. See Section 3.3 for a description of these attributes.
Note the following case-sensitivity guidelines for specifying attributes:
Except for the AGENTNAME
attribute, the attribute names are case sensitive. Enter them in upper-case letters.
All the attribute values, including the AGENTNAME
attribute value, are case sensitive. Enter them in the case shown the following tables.
To configure collection agents to listen to Oracle Real Application Clusters (Oracle RAC) nodes, see Section 4.7.
See also the Usage Notes for the avorcldb add_collector
command (Section 8.2).
Table 8-2 describes the DBAUD collector attributes.
Table 8-2 DBAUD Collector Attributes
Attribute | Description | Mutable | Default Value |
---|---|---|---|
|
Name of an agent to replace the agent that was specified by the After you replace the agent, you must run the |
Yes |
|
|
The amount of active sleep time (in milliseconds) for the DBAUD process when the last retrieval actually did retrieve records. |
Yes |
1000 milliseconds |
|
The alias name for the Audit Vault Server. The value you enter is not case sensitive. |
No |
|
|
The amount of delay time (in seconds) for the DBAUD process. |
Yes |
20 seconds |
|
The maximum number of records after which the collector commits records to the raw audit data store and generates minor recovery context. In fine-grained auditing ( |
Yes |
1000 records |
|
The amount of sleep time (in milliseconds) for the DBAUD process. For example, if it is now 10:00:00 AM, the collector will retrieve the records with the timestamps that are less than 9:59:40. However, the next time the collector will only retrieve records with the timestamps of 9:59:40 or higher. The assumption is that within 20 seconds after the timestamp is assigned to the record, the record would be visible (retrievable). This attribute is used only for time-based retrieval in fine-grained auditing ( |
Yes |
5000 milliseconds |
|
The audit data sort policy. This attribute is not implemented. It was deprecated for Oracle Audit Vault Release 10.2.3. |
Yes |
|
|
The alias name for the audit data source. The value you enter is not case sensitive. |
No |
|
Table 8-3 describes the OSAUD collector attributes.
Table 8-3 OSAUD Collector Attributes
Attribute | Description | Mutable | Default Value |
---|---|---|---|
|
The alias name for the Audit Vault Server. The value you enter is not case sensitive. |
No |
|
|
The channel type being used by the collector This attribute is not implemented. It was deprecated in Oracle Audit Vault Release 10.2.3. |
No |
|
|
The default directory for Oracle Database operating system audit files. This directory contains mandatory audit record files. The value you enter is not case sensitive. |
Yes |
|
|
The directory for the Oracle Database operating system audit files. This directory contains |
Yes |
|
|
The maximum number of records to be processed during each call to process the collector. A valid value is an integer value from 10 to 10000. |
Yes |
|
|
The maximum processing time for each call to process the collector (in centiseconds). A valid value is an integer value from 10 to 10000. |
Yes |
600 centiseconds |
|
The NLS character set of the data source. The value you enter is not case sensitive. |
Yes |
|
|
The NLS language of the data source. The value you enter is not case sensitive. |
Yes |
|
|
The NLS territory of the data source. The value you enter is not case sensitive. |
Yes |
|
|
The Oracle SID name on Microsoft Windows systems. The value you enter is not case sensitive. |
Yes |
|
|
The instance ID in an Oracle RAC environment |
Yes |
|
|
The alias or connection string to the source database. The value you enter is not case sensitive. |
Yes |
|
|
The |
Yes |
|
Footnote 1 To avoid collecting duplicate operating system audit trail records, do not set the attribute value for the OSAUDIT_DEFAULT_FILE_DEST
attribute and the OSAUDIT_FILE_DEST
attribute such that the values, although different, resolves to the same directory.
Table 8-4 describes the REDO collector attributes.
Table 8-4 REDO Collector Attributes
Attribute | Description | Mutable | Default Value |
---|---|---|---|
|
The Oracle Audit Vault database name. The value you enter is not case sensitive. |
No |
|
|
The port number of the audit data Oracle source database |
Yes |
|
|
The service name of the audit data Oracle source database. The value you enter is not case sensitive. |
No |
|
|
The time, in seconds, between events for monitoring the status of the Audit Vault REDO collection system |
Yes |
60 seconds |
|
The alias name for the audit data source. The value you enter is not case sensitive. |
No |
|
|
The name of the audit data source database. The value you enter is not case sensitive. |
No |
|
On Microsoft Windows systems, if the path value for the OSAUDIT_DEFAULT_FILE_DEST
attribute is set incorrectly using backslashes, use the Audit Vault Console to log in as the Audit Vault administrator and connect as AV_ADMIN
, click Configuration, click Collector, select the OSAUD_Collector name, then click Edit and edit the value for this attribute using slashes instead of backslashes. When finished, click OK to save your changes.
Examples
The following example shows how to alter the AUDAUDIT_DELAY_TIME
attribute for the DBAUD_Collector
collector in Oracle Audit Vault:
avorcldb alter_collector -srcname hrdb.example.com -collname DBAUD_Collector AUDAUDIT_DELAY_TIME="60" Collector altered successfully.
The following sequence of commands demonstrate how to move a collector from one collection agent to another agent:
From the Audit Vault Server, configure two agents, A and B, on two separate hosts.
For example:
avca add_agent -agentname A -agenthost host1.example.com Adding agent... Enter agent user name: agent_user_name Enter agent user password: agent_user_pwd Re-enter agent user password: agent_user_pwd avca add_agent -agentname B -agenthost host2.example.com ...
Configure collector L to run under agent A and collect from source S.
For example:
avorcldb add_collector -collname L -srcname S -agentname A
The node that runs agent A fails.
Move the collector L from agent A to agent B.
For example:
avorcldb alter_collector -collname L -srcname S agentname=B
From the Audit Vault collection agent home, configure agent B to connect to source S.
For example:
avorcldb setup -srcname S Enter Source user name: source_user_name Enter Source password: password ...
From the Audit Vault Server, restart the collector.
For example:
avctl start_collector -collname L -srcname S Starting Collector... Collector started successfully.
The avorcldb alter_source
command modifies the attributes of an Oracle source database.
Where to Run This Command
Audit Vault Server:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2.
Microsoft Windows: Go to the Audit Vault Server ORACLE_HOME
\bin
directory.
Syntax
avorcldb alter_source -srcname srcname [attrname=attrvalue...attrname=attrvalue]
Arguments
Argument | Description |
---|---|
-srcname srcname |
Enter the name of the source database to be modified. Remember that the source database name is case-sensitive. |
attrname = attrvalue |
Enter the pair (attribute name, new attribute value) for the mutable source attributes of this source to be modified. Optional. Separate multiple pairs by a space on the command line. |
Usage Notes
Table 8-5 lists source attributes that you can specify for the attrname
=
attrvalue
argument.
Table 8-5 Source Attributes
Parameter | Description | Mutable | Default Value |
---|---|---|---|
|
The Internet protocol address of the host system on which the source database resides |
Yes |
|
|
The source database version |
Yes |
|
|
The description for this source database |
Yes |
|
|
A new audit data source database service name |
Yes |
|
|
A new port number for this system where the source database audit data resides |
Yes |
|
|
The new global database name |
Yes |
|
Example
The following example shows how to alter the PORT
attribute for the source database named hr_db
in Oracle Audit Vault:
avorcldb alter_source -srcname hr_db PORT=1522 Altering source... Source altered successfully.
The avorcldb drop_collector
command disables (but does not remove) a collector from Oracle Audit Vault.
Where to Run This Command
Audit Vault Server:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2.
Microsoft Windows: Go to the Audit Vault Server ORACLE_HOME
\bin
directory.
Syntax
avorcldb drop_collector -srcname srcname -collname collname
Arguments
Argument | Description |
---|---|
-srcname srcname |
Enter the name of the source database to which the collector (specified in the -collname argument) belongs. Remember that the source database name is case-sensitive. |
-collname collname |
Enter the name of the collector to be dropped from Oracle Audit Vault. |
Usage Notes
The drop_collector
command does not delete the collector from Oracle Audit Vault. It only disables the collector. The collector metadata is still in the database after you run the drop_collector
command. If you want to recreate the collector, create it with a different name.
Example
avorcldb drop_collector -srcname hrdb.example.com -collname DBAUD_Collector Dropping collector... Collector dropped successfully.
The avorcldb drop_source
command disables (but does not remove) a source database from Oracle Audit Vault.
Where to Run This Command
Audit Vault Server:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2.
Microsoft Windows: Go to the Audit Vault Server ORACLE_HOME
\bin
directory.
Syntax
avorcldb drop_source -srcname srcname
Arguments
Argument | Description |
---|---|
-srcname srcname |
Enter the name of the source database to be dropped from Oracle Audit Vault. Remember that the source database name is case-sensitive. |
Usage Notes
The drop_source
command does not delete the source database from Oracle Audit Vault. It only disables the source database definition in Oracle Audit Vault. The source database metadata is still in the database after you run the drop_source
command. If you want to re-create the source database definition, create it with a different name.
You cannot drop a source database if there are any active collectors for this source. You must drop all collectors associated with the source database before you can run the drop_source
command on it.
Example
The following example shows how to drop the source named hrdb.example.com
from Oracle Audit Vault:
avorcldb drop_source -srcname hrdb.example.com Dropping source... Source dropped successfully.
The avorcldb -help
command displays help information for the AVORCLDB
commands. Run this command on either the Audit Vault Server and the Audit Vault collection agent.
Where to Run This Command
Either Audit Vault Server and collection agent:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2 for Audit Vault Server or Section 2.2.3 for the collection agent.
Microsoft Windows: Go to the Audit Vault Server or collection agent ORACLE_HOME
\bin
directory.
Syntax
avorcldb -help
avorcldb command -help
Arguments
Argument | Description |
---|---|
command |
Enter the name of an AVORCLDB command for which you want help to appear |
Usage Notes
None
Example
The following example shows how to display general AVORCLDB
utility help in Oracle Audit Vault:
avorcldb -help
The following example shows how to display specific AVORCLDB
help for the add_source
command in the Audit Vault Server home.
avorcldb add_source -help avorcldb add_source command add_source -src <host:port:service> [-srcname <srcname>] [-desc <desc>] [-agentname <agentname>] Purpose: The source is added to Audit Vault. The global DB Name of the source database is used as the Source Name in Audit Vault The user specified in -srcusr argument must exits on the source DB Arguments: -src : Source DB connection information -srcname : Optional name of source, default : <global_dbname> -desc : Optional description of the source -agentname : Optional agent name to configure policy management Examples: avorcldb add_source -src lnxserver:4523:hrdb.domain.com -desc 'HR Database'
The avorcldb setup
command adds the source user credentials to the wallet, creates a database alias in the wallet for the source user, verifies the connection to the source using the wallet, and updates the tnsnames.ora
file. You also can use this command to change the source user credentials in the wallet after these credentials have been changed in the source database.
Where to Run This Command
Audit Vault collection agent:
UNIX: Set the appropriate environment variables, as described in Section 2.2.3.
Microsoft Windows: Go to the Audit Vault collection agent ORACLE_HOME
\bin
directory.
Syntax
avorcldb setup -srcname srcname
Arguments
Argument | Description |
---|---|
-srcname srcname |
Enter the name of the source database. Remember that the source database name is case-sensitive. |
Usage Notes
If you installed the collection agent on a Microsoft Windows computer, run the avorcldb setup
command from the ORACLE_HOME
\bin
directory. For UNIX or Linux installations, set the appropriate environment variables before running this command. See Section 2.2 for more information.
The avorcldb setup
command prompts for the source user name and password. This user account must exist on the source database.
To find the privileges and roles granted to this user, query the SESSION_PRIVS
and SESSION_ROLES
data dictionary views. The source user should have the privileges and roles that are listed in the zarsspriv.sql
file, such as the CREATE DATABASE LINK
privilege and DBA
role.
If the AVORCLDB_SRCUSR
environment variable is set to this user account and password, then you can bypass the Enter Source user name
and Enter Source password
prompts. If you do specify these values, they override the environment variable.
Example
The following example configures the REDO and OSAUD collectors.
avorcldb setup -srcname hrdb.example.com
Enter Source user name: srcuser_ora
Enter Source password: password
adding credentials for user srcuser_ora for connection [SRCDB1]
Credential stored successfully.
updated tnsnames.ora with alias [SRCDB1] to source database
verifying SRCDB1 connection using wallet
To change the source user name password in the wallet in the Audit Vault collection agent home, use the following setup command, where the source name is orcl1
and the source user name is srcuser_ora
.
avorcldb setup -srcname orcl
Enter Source user name: srcuser_ora
Enter Source password: password
adding credentials for user srcuser_ora for connection [SRCDB1]
Credential stored successfully.
updated tnsnames.ora with alias [SRCDB1] to source database
verifying SRCDB1 connection using wallet
The avorcldb verify
command verifies that the source is compatible for setting up the specified collectors.
Where to Run This Command
Either Audit Vault Server and collection agent:
UNIX: Set the appropriate environment variables, as described in Section 2.2.2 for Audit Vault Server or Section 2.2.3 for the collection agent.
Microsoft Windows: Go to the Audit Vault Server or collection agent ORACLE_HOME
\bin
directory.
Syntax
avorcldb verify -src host:port:service -colltype [OSAUD,DBAUD,REDO,ALL]
Arguments
Argument | Description |
---|---|
-src host : port : service |
Enter the source database connection information: host name, port number, and service name, separated by a colon.
Typically, the host is the fully qualified domain name or IP address of the server on which the source database is running, and the port number is 1521. If you are unsure of the host and port number, run the |
-colltype colltype |
Enter one of the following collector types:
See Table 1-5 for more information about the collector types. |
Usage Notes
If you installed the collection agent on a Microsoft Windows computer and want to run the avorcldb verify
command from there, run it from the ORACLE_HOME
\bin
directory. For UNIX or Linux installations, set the appropriate environment variables before running this command. See Section 2.2 for more information.
The avorcldb verify
command prompts for the source user name and password. This user account must exist on the source database. To find this user, query the SESSION_PRIVS
and SESSION_ROLES
data dictionary views. The source user should have the privileges and roles that are listed in the zarsspriv.sql
file, such as the CREATE DATABASE LINK
privilege and DBA
role.
If the AVORCLDB_SRCUSR
environment variable is set to this user account, then you can bypass the Enter Source user name
and Enter Source password
prompts. If you do specify these values, they override the environment variable.
Example
The following example verifies that the source is compatible with the OSAUD, DBAUD, and REDO collectors on a Linux or UNIX system.
avorcldb verify -src hrdb.example.com:1521:orcl -colltype ALL Enter Source user name: username Enter Source password: password source HRDB.EXAMPLE.COM verified for OS File Audit Collector collector source HRDB.EXAMPLE.COM verified for Aud$/FGA_LOG$ Audit Collector collector source HRDB.EXAMPLE.COM verified for REDO Log Audit Collector collector