Oracle® Database Vault

1.1 Database Vault Administrator Web Application Fails to Start

Bug 9587181

The Database Vault Administrator (DVA) link does not work after an upgrade from Oracle Database Vault 10.2.0.4 to 10.2.0.5.

Bug 5617850

DVCA fails to deploy the Database Vault Administrator application during the DEPLOY_DVA step. DVCA shows the following error:

Error executing task 
DEPLOY_DVA:java.io.FileNotFoundException: 
D:\ORACLE\PRODUCT\10.2.0\DB_1\oc4j\j2ee\OC4J_DBConsole_wptgjqa07_ORCL\config\server.xml (Specified PATH not found)

You can use the following workaround steps for both Bug 9587181 and Bug 5617850:

1. Set the ORACLE_HOME, ORACLE_SID, and PATH environment variables.

2. Stop the Enterprise Manager Database Control process. Use the following command:

   C:\> ORACLE_HOME\bin\emctl stop dbconsole
   

3. Edit the file, ORACLE_HOME\oc4j\j2ee\OC4J_DBConsole_hostname_SID\config\server.xml. Enter the following line just before the last line that reads, </application-server>:

   <application name="dva" path="ORACLE_HOME\dv\jlib\dva_webapp.ear" auto-start="true" />
   

   Here, ORACLE_HOME needs to be replaced by the path to your Oracle home directory.

   For example:

   <application name="dva" path="C:\oracle\product\10.2.0\db1\dv\jlib\dva_webapp.ear" auto-start="true" />
   

4. Edit the file, ORACLE_HOME\oc4j\j2ee\OC4J_DBConsole_hostname_SID\config\http-web-site.xml. Enter the following line just above the last line that reads, </web-site>:

   <web-app application="dva" name="dva_webapp" root="/dva" />
   

5. Start the Enterprise Manager Database Control process. Use the following command:

   C:\> ORACLE_HOME\bin\emctl start dbconsole
   

1.2 Cannot Install Oracle Database Vault in a Data Guard Environment

Bug 5577503

The Database Vault installer fails to install Database Vault in an existing physical standby database.

You can create a new physical standby database by using the following steps:

1. Install Database Vault on the primary database.

2. Create a physical standby database using a hot backup of the primary database. This backup should include the Oracle home.

3. Set up communications between the primary and the physical standby database. Redo logs communicate changes from the primary database to the standby database.

1.3 Enterprise Manager Does Not Start Automatically

Bug 5623404

Enterprise Manager does not start automatically after installing Database Vault.

The workaround is to restart the process manually using the following commands:

C:\> ORACLE_HOME\bin\emctl stop dbconsole
C:\> ORACLE_HOME\bin\emctl start dbconsole

1.4 Database Instance and Listener Do Not Start Automatically on the Remote Node After Database Vault Installation

Bug 6630191

After you install Database Vault, the database instances and listeners on the remote nodes do not start automatically. You must start these manually.

This is expected behavior. The DVCA utility configures the local node, and starts the database instance and listener processes on the local node. You need to start these processes manually on each of the remote nodes.

1.5 Cloned Database Vault Home Contains Invalid Objects

Bug 6658315 and 6729227

Invalid objects are seen in a cloned Database Vault instance. Invalid objects are also seen when you install Database Vault over a custom database.

The following steps are used to create a cloned Database Vault instance:

1. Install Oracle Database Vault 10g Release 2 (10.2.0.5) in the first Oracle home.

2. Clone the first instance to create a second Oracle home.

3. Run Net Configuration Assistant (NetCA) and Database Configuration Assistant (DBCA) to configure a listener and database for the cloned instance.

4. Run DBCA again to configure Oracle Label Security (OLS) for the cloned instance.

5. Run Database Vault Configuration Assistant (DVCA) as follows:

   C:\> ORACLE_HOME\bin\dvca -action option -oh oracle_home
   -jdbc_str jdbc_connection_string -sys_passwd SYS_password -owner_account
   DV_owner_account_name -owner_passwd DV_owner_account_password 
   -acctmgr_account DV_account_manager_account_name -acctmgr_passwd
   DV_account_manager_password -logfile .\dvca.log -nodecrypt
   

The following SQL statement shows that the cloned Database Vault instance contains invalid objects:

SQL> select count(*) from all_objects where status = 'INVALID';
 
  COUNT(*)
----------
        45 

The workaround is to run the utlrp.sql script. This script recompiles all PL/SQL modules that might be in an invalid state, including packages, procedures, and types. Use the following commands to run the utlrp.sql script:

sqlplus SYS "AS SYSDBA"
Enter password:
SQL> @?\rdbms\admin\utlrp.sql

1.6 Error Log Created After Database Vault Installation

Bug 6692032

After you install Database Vault for an Oracle database that has Enterprise Manager configured, an error file containing the following error gets generated:

load(error):java.sql.SQLException: ORA-12541: TNS:no listener

You can safely ignore this error.

1.7 Additional Steps Required When Cloning an Oracle Real Application Clusters Node

After creating a cloned Oracle Real Application Clusters (Oracle RAC) node, and before running DVCA (dvca -action option) manually on the cloned node, you need to set the correct values for the ORACLE_HOME and ORACLE_SID variables in the ORACLE_HOME\bin\dvca.bat file on the cloned node.

If you are using the lockout option with the dvca command, then to successfully lockout SYSDBA connections, you also need to add the following values to your Microsoft Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_ORACLE_HOME_NAME:

1.8 Incorrect Registry Entry on Remote Node

Bug 5663098

When installing Database Vault for an Oracle Real Application Clusters (Oracle RAC) database, the following registry entry needs to be corrected on the remote node before configuring Oracle Database Vault security on the remote node:

HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_ORACLE_HOME_NAME\ORA_instance_name_PWFILE

The instance_name in the remote node registry should be the database instance name for the remote node, and not the database instance name for the local node.

The value for this key should be the complete path to the password file on the remote node. For example:

C:\ORACLE\PRODUCT\10.2.0\DB_1\dbs\orapwORCL2

1.9 iSQL*Plus Error Encountered When DVCA Is Run

Bug 6743410

When you run Database Vault Configuration Assistant (DVCA) with the action -option switch after adding a new database into an existing Database Vault home on Windows Vista, iSQL*Plus service related errors are generated.

You can safely ignore these error messages. Alternatively, turn off the iSQL*Plus related Windows Service (OracleOracleHomeNameiSQL*Plus) before running the dvca command.

1.10 DVCA Log Files Show Errors After Database Vault Upgrade

Bug 6742694

When upgrading from Oracle Database Vault 10g Release 2 (10.2.0.4) to Oracle Database Vault 10g Release 2 (10.2.0.5), you need to run the Database Vault Configuration Assistant (DVCA) to reconfigure Database Vault. You might see the following error in the DVCA log file:

Executing task ACCOUNT_CREATE_OWNER
01/10/08 06:37:06 Error executing task
ACCOUNT_CREATE_OWNER:java.sql.SQLException: ORA-01920: user name 'MACSYS'
conflicts with another user or role name
01/10/08 06:37:06 Executing task GRANT_CONNECT_OWNER
*******
01/10/08 06:37:06 Executing task ACCOUNT_CREATE_MANAGER
01/10/08 06:37:06 Error executing task
ACCOUNT_CREATE_MANAGER:java.sql.SQLException: ORA-01920: user name 'MACAUTH'
conflicts with another user or role name
01/10/08 06:37:06 Executing task GRANT_CONNECT_MANAGER

These errors can be safely ignored.

1.11 Swap Space Requirement Prerequisite Test Fails

Bug 7506215

The Database Vault installer swap space requirement test may fail in some cases even when enough swap space is available.

The swap space required for installation should not exceed 16GB. In case the required swap space is shown as more than 16 GB, this warning can be safely ignored.

1.12 Errors Generated by catmac.sql When Upgrading Database Vault

Bug 9888841

The Oracle Database Vault Installation Guide includes instructions to upgrade a previous version of Oracle Database Vault to Oracle Database Vault 10.2.0.5. One of the upgrade steps requires the user to run the catmac.sql script. The Oracle Database Vault Installation Guide advises the user to spool the output of this script into a file in order to look for errors.

The spooled output file may include the following errors:

ORA-01920: user name 'DVSYS' conflicts with another user or role name
ORA-01920: user name 'DVF' conflicts with another user or role name
SP2-0310: unable to open file catmaca.sql
ORA-01952: system privileges not granted to 'DBA'
ORA-00955: name is already used by an existing object
ORA-02260: table can have only one primary key

You can safely ignore these error messages.

1.13 DVCA Error During Database Vault Installation

Bug 10033496

An ORA-01031: insufficient privileges error may be generated during the Lock DVSYS phase of the Database Vault installation process. This may be caused by a low shared pool size.

The workaround is to increase the shared pool size to a larger value. To set the shared pool size, use the following SQL statement:

ALTER SYSTEM SET SHARED_POOL_SIZE=VALUE;

2.1 Accounts with DV_OWNER, DV_ADMIN, or DV_SECANALYST Role Cannot Use the ALTER USER Command

Bug 5161953

Accounts with the DV_OWNER, DV_ADMIN, or DV_SECANALYST role cannot run the following command:

ALTER USER user QUOTA UNLIMITED ON tablespace

The workaround is to REVOKE the role from the account, run the ALTER USER command, and then GRANT back the role to the account. This works if the account is not the DV_OWNER account that was created during installation. If the account is the DV_OWNER account created during installation, then you would need to use the following steps:

1. Disable the Database Vault command rule for the ALTER USER command.

2. Run the ALTER USER command.

3. Re-enable the Database Vault command rule for the ALTER USER command.

2.2 Adding Languages Using DVCA Results in Error Messages

Bug 9851682

Adding language support using the -languages option of the Database Vault Configuration (DVCA) utility may cause constraint violation or user creation errors.

For example, using the following command might result in errors:

C:\> dvca -action option -oh ORACLE_HOME -hostname HOST_NAME 
-owner_account OWNER_ACC -acctmgr_account ACCTMGR_ACC -sys_passwd SYS_PASSWD 
-jdbc_str jdbc:oracle:oci:@SID -nodecrypt 
-languages {"en,de,es,fr,it"}

You may see errors like the following:

Executing task LOAD_NLS_FILES

java.sql.SQLException: ORA-00001: unique constraint
(DVSYS.FACTOR_TYPE_T$_UK1) violated
:Fattori basati sull'organizzazione,10,i,Organizzazione

Error executing task ACCOUNT_CREATE_OWNER:java.sql.SQLException: ORA-01920:
user name 'MACSYS' conflicts with another user or role name
Error during post-installation processing. java.sql.SQLException: ORA-01920:
user name 'MACSYS' conflicts with another user or role name
Error during post-installation processing. java.sql.SQLException:
ORA-01920: user name 'MACSYS' conflicts with another user or role name

You can safely ignore these errors.

2.3 CREATE SESSION Privilege Is Controlled by the Data Dictionary Realm

Use the following steps to grant the CREATE SESSION privilege:

1. Temporarily disable the data dictionary realm.

2. Log in as the SYSTEM user.

3. Grant the CREATE SESSION privilege.

4. Enable the data dictionary realm.

4.1 Snapshots and Materialized Views

The keyword SNAPSHOT is supported in place of MATERIALIZED VIEW for backward compatibility.

4.2 JOB_QUEUE_PROCESSES Initialization Parameter

The JOB_QUEUE_PROCESSES initialization parameter specifies the maximum number of processes that can be created for the execution of jobs. It specifies the number of job queue processes per instance.

This parameter must have a non-zero value. The default value for JOB_QUEUE_PROCESSES is 10.