| Oracle® Audit Vault Release Notes Patch Set 2 Release 10.2.3.2 Part Number E14466-02 |
|
| View PDF |
| Oracle® Audit Vault Release Notes Patch Set 2 Release 10.2.3.2 Part Number E14466-02 |
|
| View PDF |
Release Notes
Patch Set 2 Release 10.2.3.2
E14466-02
November 2009
These Release Notes contain important information that was not included in the Oracle Audit Vault Patch Set 2 Release 10.2.3.2 documentation.
This document contains the following sections:
Installing the Oracle Audit Vault Patch Set on the Audit Vault Server
Installing the Oracle Audit Vault Patch Set on the Audit Vault Agent
You can download the most current version of this document from the following Web site:
This section describes how to install Oracle Audit Vault Patch Set 2 (Release 10.2.3.2.0) onto the following Oracle Audit Vault releases and products:
Oracle Audit Vault Server Release 10.2.3.0 or 10.2.3.1.0
Oracle Audit Vault Agent Release 10.2.3.0 or 10.2.3.1.0
You must install this patch set on the Oracle Audit Vault Server release before you can upgrade the Agent release installation. This procedure takes approximately an hour and 45 minutes to complete, depending on the speed of your computer.
This section contains:
Step 1: For Oracle RAC, Check the Cluster Ready Services Version
Step 3: Ensure That the NLS_LANG Environment Variable Is Not Set
Step 5: Manually Disable Database Vault on Oracle RAC Instances
Step 6: Install the Oracle Audit Vault Patch Set into the Audit Vault Server Home
If you plan to install the Oracle Audit Vault Server patch set on Oracle Real Application Clusters (Oracle RAC), then ensure that the Cluster Ready Services (CRS) version is Release 10.2.0.4 or later. If the CRS version is not Release 10.2.0.4 or later, then you must first patch CRS to Release 10.2.0.4 before installing the Audit Vault Server patch set.
As a best practice, you should back up your Oracle Audit Vault database, the Audit Vault Server home, and the Audit Vault collection agent home before you begin the upgrade.
You cannot roll back or re-apply the Oracle Audit patch set if the patch set installation fails. Therefore, back up the files before you apply and test the patch upgrade.
Back Up the Database
After cleanly shutting down the instance following the analysis of the database, perform a full backup of the database. Complete the following steps:
Start RMAN:
$ rman target /
Issue the following RMAN commands. In the following example, the tag is named before_upgrade.
BACKUP DATABASE FORMAT 'backup_directory%U' TAG before_upgrade; BACKUP CURRENT CONTROLFILE FORMAT 'save_controlfile_location';
See Also:
Oracle Database Backup and Recovery Basics for more information about backing up a database.Back Up Oracle Audit Vault Server Home
Because the patch set updates files in the Oracle Audit Vault Server home directory, back up or copy these files to another directory until after you have tested the patch set.
Do not set the NLS_LANG environment variable.
To unset the NLS_LANG environment variable for the C shell:
$ unsetenv NLS_LANG
For Bourne, Bash, or Korn:
$ unset NLS_LANG
This section contains:
To stop the collectors:
In the server where you installed the Oracle Audit Vault Server, open a shell.
Set the appropriate environment variables for the Oracle Audit Vault Server.
See "Checking and Setting Environment Variables" in Chapter 2 of Oracle Audit Vault Administrator's Guide.
Run the following command to stop the collectors:
$ avctl stop_collector -collname collector-name -srcname source_name
Leave this shell open.
To stop the agents:
In the shell that you opened in Section 2.4.1, run the following command:
$ avctl stop_agent -agentname agent_name
Leave this shell open.
To stop the Oracle Audit Vault Console:
In the shell that you opened in Section 2.4.1, run the following command:
$ avctl stop_av
Leave this shell open.
From the Oracle Audit Vault Server home, use the following command to shut down the Oracle Audit Vault Database.
$ sqlplus /nolog
SQL> CONNECT SYS/AS SYSOPER
Enter password: password
Connected.
SQL> SHUTDOWN IMMEDIATE
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> EXIT
In an Oracle RAC environment, run the following command from the node on which the Audit Vault Console is running:
$ORACLE_HOME/bin/srvctl stop database –d AVdatabase_name -q Connect string: [/ as sysdba] sys/sys_password as sysdba
From the Oracle Audit Vault Server home, run the following command to stop the listener. The listener name is usually LISTENER. You can run the lsnrctl status command to check the name of the listener.
$ lsnrctl stop listener_name
In an Oracle RAC environment, run this command on all nodes where Oracle Audit Vault Server is installed.
If the Audit Vault Server is running on Oracle RAC, manually disable Database Vault before the installation, as follows:
Ensure that you have shut down the database in the Audit Vault Server home directory to be patched, as described in Section 2.4.
For each Oracle RAC node, relink the oracle executable with the dv_off command.
$ make -f $ORACLE_HOME/rdbms/lib/ins_rdbms.mk dv_off ioracle
Connect to the Audit Vault Server database on the Oracle RAC instance.
$ sqlplus "/ as sysdba"
Start the database instance.
SQL> STARTUP MOUNT
Turn off the archivelog feature.
SQL> ALTER DATABASE NOARCHIVELOG; SQL> ALTER DATABASE OPEN;
Issue the following commands to disable the Oracle Database Vault-related DDL triggers.
SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG DISABLE; SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG DISABLE;
Shut down the database instance.
SQL> SHUTDOWN IMMEDIATE
Stop the listener on that node.
$ lsnrctl stop listener_name
Perform the following steps to install the Oracle Audit Vault Patch Set 2 (Release 10.2.3.2.0) in the Oracle Audit Vault Server home. You must use the same download executable for both the Audit Vault Server and Audit Vault Agent upgrades.
Log in to My Oracle Support (formerly OracleMetaLink) and download Oracle Audit Vault Patch Set 2 (Release 10.2.3.2.0).
You can access My Oracle Support from the following Web site:
Start Oracle Universal Installer (OUI) from the directory that contains the runInstaller program.
$ cd directory-containing-Oracle-Audit-Vault-Patchset-Installation-Files
./runInstaller
Oracle Universal Installer starts. It verifies the operating system version and then presents a summary of the checks it performs.
In the Welcome window, click Installed Products to display the Inventory window.
This window indicates the name of the Oracle Audit Vault Server home installed on your computer. For example, it may be named OraAV10g_home1. The Path field updates to correspond with the Oracle home directory in the Name field.
Click Close to close the Inventory window and return to the Welcome window. Then the click Next.
In the Specify Home Details window, in the Name field, click the down arrow at the end of the field and select the name of the Oracle Audit Vault Server home you found in the previous step (Step 3). Then click Next.
In the next window, optionally, provide your e-mail address and My Oracle Support password if you want to receive Oracle security updates. Then click Next.
For an Oracle RAC installation, a node selection window appears with all fields disabled. This window displays the nodes that this patch set is going to be installed on.
When the Product-Specific Prerequisite Checks window appears, Oracle Universal Installer then performs product-specific prerequisite checks.
In the Summary Page window check the space requirements.
For a single instance installation, 832 MB of space is required to install Patch Set 2, which includes 50 MB of temporary space.
For an Oracle RAC installation, for local node 854 MB of space is required and for remote node 804 MB of space is required to install Patch Set 2, which includes 50 MB of temporary space.
Review each of the items that are about to be installed.
Click Install.
When the installation completes, the Configuration Assistants window appears.
The Configuration Assistants window displays, and the configuration begins. When the configuration completes, the End of Installation window appears and displays the URL for the Oracle Audit Vault Console. It is the same URL used for the previous Oracle Audit Vault installation.
Click Exit to exit the Oracle Universal Installer, and then click Yes in the confirmation window.
When the installation is complete, the Audit Vault Server database and listener are running. You can check them as follows:
To check the status of the database, run the following SELECT statement in SQL*Plus:
SQL> SELECT OPEN_MODE FROM V$DATABASE;
It should return the following output:
READ WRITE
To check the status of the listener:
$ $ORACLE_HOME/bin/lsnrctl status listener_name
Ensure that the processes are running.
$ emctl status dbconsole
In the shell that you opened in Section 2.4.1, run the following command:
$ avctl show_av_status
If the processes are not running, then run the following commands:
$ avctl stop_av $ avctl start_av
The avctl start_av command also starts the Database Console.
If the Patch Set Upgrade Is Not Successful
If the patch set apply is not successful, to abandon the upgrade, perform the following steps:
Copy (Restore) the Audit Vault Server Home files back to their original location.
If you backed up the database, then restore that backup. Complete the following steps:
Log in to the system as the owner of the Oracle home directory of the previous release.
Sign on to RMAN:
$ rman target /
Issue the following RMAN commands. In this example, the name of the tag is before_upgrade:
STARTUP NOMOUNT
RESTORE CONTROLFILE FROM 'save_controlfile_location';
ALTER DATABASE MOUNT;
RESTORE DATABASE FROM TAG before_upgrade RECOVER DATABASE;
ALTER DATABASE OPEN RESETLOGS;
After you complete these steps, for AIX platforms and for Oracle RAC environments, you must restart the Oracle Audit Vault Server. For other platforms, the Audit Vault Server should start. If it does not, then follow the instructions in this section.
To restart the Oracle Audit Vault Server on AIX 5L:
Access the shell that you opened for the Audit Vault Server in Section 2.4.1 and ensure that the ORACLE_SID environment variable is properly set.
Stop the Oracle Audit Vault Server console.
$ avctl stop_av
Log in to SQL*Plus as user SYS with the SYSOPER privilege and shut down the database.
$ sqlplus sys as sysoper
Enter password: password
Connected.
SQL> SHUTDOWN IMMEDIATE
Relink the oracle executable.
$ $ORACLE_HOME/bin/relink oracle
From SQL*Plus, restart the database.
SQL> STARTUP
Restart the Audit Vault Server console.
$ avctl start_av
You can check the status of the Audit Vault Server as follows:
$ avctl show_av_status
To restart the Oracle Audit Vault Server on non-AIX 5L platforms:
Access the shell that you opened for the Audit Vault Server in Section 2.4.1.
Check the status of the Audit Vault Server.
$ avctl show_av_status
If the Audit Vault Server is not running, then run the following command:
$ avctl start_av
To restart the Oracle Audit Vault Server in an Oracle RAC environment:
On each node, run the following command in SQL*Plus:
$ sqlplus / as sysdba SQL> ALTER DATABASE OPEN;
To verify that all database instances are in OPEN mode, select from the GV$INSTANCE view as follows:
SQL> SELECT INST_ID, STATUS FROM GV$INSTANCE;
Access the shell that you opened for the Audit Vault Server in Section 2.4.1.
Run the following commands to restart the Audit Vault Server:
$ avctl stop_av $ avctl start_av
You can check the Audit Vault Server status as follows:
$ avctl show_av_status
Before you begin these instructions, ensure that you have completed the Oracle Audit Vault Server patch set release installation. This procedure takes approximately five-to-fifteen minutes to complete, depending on the speed of your computer.
This section contains:
Step 1: Back Up the Oracle Audit Vault Collection Agent Home
Step 2: Ensure That the NLS_LANG Environment Variable Is Not Set
Step 4: Install Oracle Audit Vault Patch Set 2 in the Audit Vault Collection Agent Homes
Because the patch set updates files in the Oracle Audit Vault collection agent home directory, back up or copy these files to another directory until after you have tested the patch set.
Do not set the NLS_LANG environment variable.
To unset the NLS_LANG environment variable for the C shell:
$ unsetenv NLS_LANG
For Bourne, Bash, or Korn:
$ unset NLS_LANG
This section contains:
To stop the collectors that are running within the context of the agent that you are patching:
Access the Audit Vault Server shell that you opened in Section 2.4.1, "Step 4A: Stop All Collectors."
If you had closed this shell, then you must set the appropriate environment variables for the Oracle Audit Vault Server. See "Checking and Setting Environment Variables" in Chapter 2 of Oracle Audit Vault Administrator's Guide.
Run the following command to stop the collectors:
$ avctl stop_collector -collname collector-name -srcname source_name
Leave this shell open.
To stop the collection agent:
Open a shell for the Audit Vault agent.
Set the appropriate environment variables for the Oracle Audit Vault agent.
See "Checking and Setting Environment Variables" in Chapter 2 of Oracle Audit Vault Administrator's Guide.
Run the following command:
$ avctl stop_oc4j
You can check the status of the agent as follows:
$ avctl show_oc4j_status
Leave this shell open.
Perform the following steps to install the Oracle Audit Vault Patch Set 2 (Release 10.2.3.2.0) in the Oracle Audit Vault collection agent home.
If you have not done so already, log in to My Oracle Support and download Oracle Audit Vault Patch Set 2 (Release 10.2.3.2.0). You can access My Oracle Support from the following Web site:
Start Oracle Universal Installer (OUI) from the directory that contains the runInstaller program.
$ cd directory-containing-Oracle-Audit-Vault-Patchset-Installation-Files
./runInstaller
Run the same Oracle Universal Installer that you used to install the Oracle Audit Vault Server patch set. Oracle Universal Installer starts. It verifies the operating system version and then presents a summary of the checks it performs.
In the Welcome window, click Installed Products to display the Inventory window.
This window indicates the name of the Oracle Audit Vault collection agent home installed on your computer. For example, it may be named OraAV10g_home2 when installed on the same computer as the Oracle Audit Vault Server or OraAV10g_home1 when installed on a different computer from Oracle Audit Vault Server.
Click Close to close the Inventory window and return to the Welcome window. Then the click Next.
In the Specify Home Details window, in the Name field, click the down arrow at the end of the field and select the name of the Oracle Audit Vault collection agent home you determined from the previous step (Step 3).
Once you select the Oracle Audit Vault collection agent home, the Path field should display the correct path to the Oracle Audit Vault collection agent home. Review the path name. Then click Next.
When the Product-Specific Prerequisite Checks window appears, Oracle Universal Installer then performs product-specific prerequisite checks.
In the Summary Page window, check the space requirements.
On Linux, 330 MB of space is required to install Patch Set 2, which includes 25 MB of temporary space.
On Microsoft Windows 32-bit, 223 MB of space is required to install Patch Set 2, which includes 23 MB of temporary space.
Review each of the items that are about to be installed.
Click Install.
The Install window appears. When the installation completes, the Configuration Assistants window appears and then completes the configuration. Then the end of Installation window appears.
Click Exit to exit the Oracle Universal Installer, and then click Yes in the confirmation window.
If the Patch Upgrade Is Not Successful
If the patch set upgrade is not successful, to abandon the upgrade, copy (restore) the Audit Vault collection agent home files back to their original location.
This section contains:
By default, the collection agent should be running. If it is not, follow these steps:
Access the shell that you opened for the Audit Vault Agent in Section 3.3.2.
Run the following command:
$ avctl start_agent
You can check the status of the agent as follows:
$ avctl show_agent_status
Close this shell.
To start the collectors:
In the Audit Vault Server shell that you opened in Section 2.4.1, run the following command:
$ avctl start_collector -collname collecctor_name -srcname source_name
Leave this shell open.
To verify that all Oracle Audit Vault components are running and the system is operational:
In the shell that you opened in Section 2.4.1, run the following command:
$ avctl show_collector_status -collname collector_name -srcname source_name
Close this shell.
After you install Oracle Audit Vault, check if there is a patch set or critical patch update (CPU) available. Before applying any Oracle Audit Vault patch sets, back up your Oracle Audit Vault database, the Oracle Audit Vault Server home, and the Oracle Audit Vault collection agent home. See Section 4.1 for more information.
This section describes the following postinstallation tasks if you need to update this patch:
Back up the files before you begin a critical patch upgrade and keep these files until you have tested the upgrade. See "Step 2: Back Up Oracle Audit Vault" for more information.
A CPU is a collection of patches for security vulnerabilities. It also includes non-security fixes required (because of interdependencies) by those security patches. CPUs are cumulative, and they are provided quarterly on the Oracle Technology Network. Oracle Audit Vault 10.2.3.2.0 does not include the October 2009 RDBMS CPU for the underlying 10.2.0.4 database, therefore, you need to install this RDBMS CPU. If a later RDBMS CPU is available, then install that. For general information about CPUs, see
http://www.oracle.com/security/critical-patch-update.html
For specific information about critical patch updates and security alerts, see
http://www.oracle.com/technology/deploy/security/alerts.htm
Table 1 lists bugs that have been fixed for Oracle Audit Vault Patch Set Release 10.2.3.2.
Table 1 Bugs Fixed in Oracle Audit Vault Patch Set Release 10.2.3.2
| Bug Number | Description |
|---|---|
|
7375174 |
NEED A MECHANISM TO CLEAN OUT THE ARCHIVED AUDIT SETTINGS FOR A SOURCE IN AV |
|
7449916 |
CAN "MARK ALL [OPTIONS] AS NEEDED", BUT CANNOT "UNMARK ALL" / "MARK AS UNNEEDED" |
|
7589154 |
TRANSACTION ID FORMAT IN DATAWAREHOUSE |
|
7599953 |
XML COLLECTOR CRASHES WITH CSDK ERROR |
|
7607999 |
LINK OF "TOP FIVE AUDIT SOURCES BY NUMBER OF ALERTS" IS WRONG |
|
7610793 |
WHEN EXECUTING PROVISION AGAINST 9IR2 DB, ENCOUNTERING ERROR |
|
7636785 |
VERY SLOW AV DATAWAREHOUSE REFRESH |
|
7658670 |
STREAMS COLLECTOR IS FAILING WITH ORA-7445 [STRSTR()] |
|
7693379 |
MSSQL COLLECTOR CRASHES WITH ORA-1461 |
|
7706920 |
MSSQL COLLECTOR IS CRASHING CONSISTENTLY |
|
8197634 |
AV CONSOLE IS SLOW BECAUSE IT POLLS THE STATUS OF ALL THE COLLECTORS |
|
8197950 |
ERROR ADDING AGENT: CONFIGURATION NAME ALREADY EXISTS OAV-46503 |
|
8206426 |
CONTEXT_DIM HAS 3 TIMES MORE ROWS THAN AV$RADS_FLAT |
|
8209426 |
WRONG URL PRINTED BY AVCTL |
|
8235653 |
OSAUD COLLECTOR DIES ON WINDOWS IF IT ENCOUNTERS ERROR WHILE PROCESSING EVTLOG |
|
8323660 |
INCORRECT OS CHECKS IN SYBASE, DB2 AND SQL SERVER COLLECTORS |
|
8370693 |
NEED TO BE ABLE TO SEE ALL THE DATE/TIME IN A PARTICULAR TIMEZONE |
|
8414793 |
THE OS COLLECTOR GETS STUCK INTERMITTENTLY |
|
8468129 |
CANNOT DELETE ALERTS FROM AV GUI |
|
8508268 |
DB COLLECTOR FAILS WITH ORA-06502 ORA-06512 NPSRCUSR.AV_TRUNCATE_CLOB |
|
8634768 |
AUDIT VAULT POLICIES RETRIEVAL PERFORMANCE SLOW |
|
8726158 |
CANNOT START COLLECTOR AFTER UPGRADING TO 10.2.3.1 |
|
8753685 |
OS COLLECTOR GETS DISCONNECTED FROM SOURCE DB FOR 9.2 DATABASES |
|
8782576 |
ALLOW DB_DOMAIN = NULL TO ADD REDO COLLECTOR WHEN GLOBAL_NAMES=FALSE |
|
8868978 |
AUDIT POLICY RETRIEVAL FAILS - LOG SHOWS 'INVALID COLUMN NAME' |
This section contains:
This section describes known issues and workarounds for single instance and Oracle RAC installations on all platforms.
This section contains:
After you install Oracle Audit Vault Server Patch Set 2 Release 10.2.3.2.0, the Oracle Enterprise Manager URL is not secure.
Workaround: Perform the following steps in the Audit Vault Server shell to secure the Oracle Enterprise Manager URL.
Ensure that the ORACLE_SID environment variable is set correctly.
Set the time zone environment variable TZ to UTC.
$ setenv TZ UTC
Stop the Oracle Enterprise Manager console.
$ ORACLE_HOME/bin/emctl stop dbconsole
Configure the Oracle Enterprise Manager key.
$ ORACLE_HOME/bin/emctl config emkey -repos -sysman_pwd password
Secure Oracle Enterprise Manager.
$ ORACLE_HOME/bin/emctl secure dbconsole -sysman_pwd password
Start the Oracle Enterprise Manager console.
$ ORACLE_HOME/bin/emctl start dbconsole
This issue is tracked with Oracle bug 8924450.
Shortly after installing Oracle Audit Vault, you may not be able to access the Audit Vault Console. If you run the emctl status dbconsole and avctl show_av_status commands, then the output indicates that Oracle Audit Vault is running. However, when you try to access the Audit Vault Console, the Web browser page displays a This page cannot be displayed error.
Workaround: Restart the Audit Vault Console. See Step 9 of Section 2.6.
This issue is tracked with Oracle bug 6867972.
This section contains:
While you install Oracle Audit Vault Patch Set 2 release 10.2.3.2.0 over single node Oracle RAC 10.2.3.2 Audit Vault Server, DBUA fails with the following error:
ORA-32001: write to SPFILE requested but no SPFILE specified at startup
Workaround: Perform the following steps before installing the patch set:
Stop the database.
$ ORACLE_HOME/bin/srvctl stop database -d db_name
Start the database with the NOMOUNT option.
$ sqlplus /NOLOG
SQL> CONNECT SYS/SYS_password AS SYSDBA
SQL> STARTUP NOMOUNT
Create the SPFILE from the PFILE by entering the following command where the pfile_location is usually $ORACLE_HOME/admin/db_name/pfile for the Optimal Flexible Architecture compliant database:
SQL> CREATE SPFILE='SHARED_LOCATION/SPFILE.ORA' FROM PFILE='pfile_location/init.ora'
Shut down the database:
SQL> SHUTDOWN IMMEDIATE SQL> EXIT
Clear the contents of the PFILE located at $ORACLE_HOME/dbs/initsid.ora and enter following entry in that file:
SPFILE=SHARED_LOCATION/SPFILE.ORA
Restart the database.
SQL> STARTUP
This issue is tracked with Oracle bug 8493676.
After you patch Audit Vault from Release 10.2.3.0 to 10.2.3.2.0 on Oracle RAC, the Oracle Enterprise Manager URL does not work. If you run the emctl status dbconsole command, it indicates that Enterprise Manager is running, but when you try the URL, the following error appears:
The database status is currently unavailable. It is possible that the database is in mount or nomount state. Click 'Startup' to obtain the current status and open the database. If the database cannot be opened, click 'Perform Recovery' to perform an appropriate recovery operation.
Workaround: See Section 2.7.3.
This issue is tracked with Oracle bug 8924812.
This section contains:
During the installation of Oracle Audit Vault Server on AIX 5L, Audit Vault Configuration Assistant (AVCA) fails to relink the oracle executable with the dv_on option.
An error message similar to the following appears in the $ORACLE_HOME/av/log/avca.log file:
0/12/09 04:44:48 ld: 0706-021 The wait() system call failed.
10/12/09 04:44:48 ld:wait(): There are no child processes.
10/12/09 04:44:48 make: 1254-004 The error code from the last command is
255.
10/12/09 04:44:48
10/12/09 04:44:48
10/12/09 04:44:48 Stop.
Because of this error, Oracle Database Vault is not enabled at the end of the Audit Vault Release 10.2.3.2 installation on AIX 5L.
Workaround: After you complete the Audit Vault Server installation, follow the procedure in Section 2.7.1, "Restarting the Audit Vault Server on AIX 5L." Afterwards, you can install the Audit Vault agent, as described in Section 3, "Installing the Oracle Audit Vault Patch Set on the Audit Vault Agent."
This issue is tracked with Oracle bug 9029325.
There are no known issues for Oracle Audit Vault on the Microsoft Windows platform.
This section contains:
The Data Changes Report in Audit Vault Console fails with the following errors when the before and after values that the report attempts to capture are too large:
ORA-01489: result of string concatenation is too long
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
Workaround: None
This issue is tracked with Oracle bug 9055316.
The Audit Vault reports can fail when you try to apply a simple filter such as the following:
User = username
An error similar to the following appears in the Audit Vault Console:
{"dialog":{"uv":true,"row":[{"V":"Widget FailureORA-06502: PL/SQL: numeric or
value error:character string buffer too small,worksheet"}]}}
The Data Access Report has a similar problem: it fails on the column TARGET if you try to apply a filter similar to the following:
"Target != 'CUSTOMNAME'"
This problem can also occur with NOT filters.
Workaround: Download patch number 7564548 from My Oracle Support (formerly OracleMetaLink), from the following Web site:
This issue is tracked with Oracle bug 7564548.
There are no known source configuration issues at this time.
This section contains:
Intermittently, the OSAUD collector fails with an error similar to the following:
INFO @ '03/06/2009 01:50:01 02:00': File /oracle/admin/mau/adump/mau_ora_17373_1.xml not found in hash table, Adding.. ERROR @ '03/06/2009 01:50:43 02:00': On line 2101; ORA-00600: Interner Fehlercode, Argumente: [], [], [], [], [], [], [], []
Workaround: Restart the collector.
Open a shell and then set the environment variables for the Audit Vault Server.
See "Setting the Audit Vault Server Linux and UNIX Environment Variables" in Oracle Audit Vault Administrator's Guide.
Run the avctl start_collector command.
For example:
$ avctl start_collector -collname OSAUD_Collector -srcname my_db
This issue is tracked with Oracle bug 8645192.
The avorcldb add_collector command for REDO collectors fails on Oracle9i Release 2 (9.2.0.8) source databases. When you try to add a REDO collector type, the following error message appears:
ERROR: ORA-00904: "PLATFORM_NAME": invalid identifier/
Workaround: None
This issue is tracked with Oracle bug 9066182.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Accessibility of Code Examples in Documentation
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
Accessibility of Links to External Web Sites in Documentation
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Deaf/Hard of Hearing Access to Oracle Support Services
To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.
Oracle Audit Vault Release Notes, Patch Set 2 Release 10.2.3.2
E14466-02
Copyright © 2009, Oracle and/or its affiliates. All rights reserved.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.
This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|