Oracle® Database Vault

1.1 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. Set up communications between the primary and the physical standby database. Redo logs communicate changes from the primary database to the standby database.

1.2 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.3 Cloned Database Vault Home Contains Invalid Objects

Bug 6658315

If you have cloned the Database Vault Oracle home and database, after you run the Database Vault Configuration Assistant (DVCA), the database contains invalid objects.

The workaround is to recompile the invalid objects, as follows:

1. Log in to SQL*Plus using the SYSDBA privilege.

   $ SQLPLUS / AS SYSDBA
   

2. Find the number of invalid objects in the database. For example:

   SQL> SELECT COUNT(*) FROM ALL_OBJECTS WHERE STATUS = 'INVALID';
   
       COUNT(*)
     ----------
             45
   

3. Run the utlrp.sql to recompile the invalid objects:

   SQL> @ORA_ROOT:[RDBMS.ADMIN]UTLRP.SQL
   

1.4 Error When Executing LOAD_NLS_FILES During Installation

The following error message may appear during installation:

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

You can safely ignore this error message.

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 Enabling a Realm Fails When a Realm Secured Object Is Invalid

Bug 5582720

Enabling a realm fails with the following error:

ORA-00942: Table or view does not exist

This might happen if you try to enable a realm on an invalid object. The workaround is to make sure that all objects protected by the realm are valid, before trying to enable the realm.

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.

2.4 Enabling and Disabling Oracle Database Vault on hp OpenVMS

The instructions in Appendix B, "Enabling and Disabling Oracle Database Vault," in Oracle Database Vault Administrator's Guide for enabling and disabling Database Vault apply to the UNIX and Microsoft Windows platforms only. However, refer to that appendix for reasons why you may need to disable Database Vault and how to check if Database Vault has been enabled.

This section explains how to disable and then re-enable Database Vault for the hp OpenVMS platform. For Oracle Real Application Clusters, perform the tasks in this section on a single node in the cluster.

This section contains:

• Step 1: Disable Oracle Database Vault

• Step 2: Perform the Required Tasks

• Step 3: Enable Oracle Database Vault

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.

4.3 Language Support in Database Vault

Database Vault supports the following languages:

• de: German

• en: American English

• es: Spanish

• fr: French

• it: Italian

• ja: Japanese

• ko: Korean

• pt_BR: Brazilian Portuguese

• zh_CN: Simplified Chinese

• zh_TW: Traditional Chinese

Make sure that the NLS_LANG parameter in your database corresponds to one of these languages before installing Database Vault. If the language setting in the NLS_LANG parameter is not compatible, then the Database Vault Administrator (DVA) application interface cannot display properly.