Oracle® Database Vault

1.1 Installing a Custom Database in an Existing Database Vault Home Fails

Bug 5334101

When installing a new custom database in an existing Database Vault home using Database Configuration Assistant (DBCA), the installation fails with the following error:

ORA-00604: error occurred at recursive SQL level 1 
ORA-01031: insufficient privileges 
ORA-06512: at "XDB.DBMS_XDB", line 73 
ORA-06512: at line 319

The workaround is to disable Database Vault before installing a custom database in an existing Database Vault home. Reenable Database Vault after installing the database.

1.2 DVCA Fails If the SID Is Longer than 8 Characters

Bug 5258820

Running Database Vault Configuration Assistant (DVCA) manually, after creating a new database in the Database Vault home, fails if the Oracle System Identifier (SID) for the database is longer than 8 characters.

The following steps reproduce the bug:

1. Use Database Configuration Assistant (DBCA) to create a new database in an existing Database Vault home.

2. Run DVCA on the newly created database:

   $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] [-silent] [-nodecrypt][-lockout] [-languages {["en"],["de"],["es"],["fr"],["it"],["ja"],\
   ["ko"],["pt_BR"],["zh_CN"],["zh_TW"]}]
   
   

The reason for the bug is that the Oracle Net service name in the tnsnames.ora ($ORACLE_HOME/network/admin/tnsnames.ora) file is truncated to 8 characters.

The workaround for the bug is to change the truncated Net service name in the tnsnames.ora file to it's correct value. For example, say the SID for the database is ORACLEDB90, and the entry in tnsnames.ora appears as:

ORACLEDB = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST ....

Replace the truncated entry in the tnsnames.ora file with the correct entry:

ORACLEDB90 = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST ....

1.3 Special Characters Not Allowed in User Name

Bug 5590346

The Database Vault installer does not allow you to use special characters, like the underscore ( _ ) character, for the Database Vault Owner and the Database Vault Account Manager user names.

The workaround is to use only alphanumeric characters for the Database Vault Owner and Account Manager user names.

1.4 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.5 Database Vault Installer Returns an Error When Installing for a German Locale

Bug 5646888

The Database Vault installer returns an error message when it is run for a German Locale. The Negative Time error message is displayed.

This error occurs if some of the files accompanying the installer have a timestamp earlier than 1st January, 1970. In most cases, these files are under the Disk1/stage or Disk1/stage/properties directory. The workaround is to open and save these files again so that their timestamps are updated.

1.6 Enterprise Manager Does Not Start Automatically

Bug 5613521

After installing Database Vault on a Real Application Clusters (RAC) database, and running the postinstallation steps on the nodes, you get an error when trying to access Enterprise Manager.

Also, when you try to check the status of dbconsole using the emctl status dbconsole command, you get a message saying that the EM daemon is not running even though the process is running.

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

$ORACLE_HOME/bin/emctl stop dbconsole
$ORACLE_HOME/bin/emctl start dbconsole

1.7 Enterprise Manager Does Not Start Automatically on the Remote Nodes

Bug 5654876

After installing Database Vault on a Real Applications Cluster (RAC) database, and running the dvca -action optionrac command on the remote nodes, Enterprise Manager does not start automatically on the remote nodes.

The workaround is to set the correct value for the ORACLE_SID variable in the $ORACLE_HOME/bin/dvca.bat file on the remote node. The ORACLE_SID variable needs to be changed from the local node SID to the remote node SID on the remote node. You can then run DVCA on the remote node.

Alternatively, you can manually restart the dbconsole process using the following commands:

$ORACLE_HOME/bin/emctl stop dbconsole
$ORACLE_HOME/bin/emctl start dbconsole

1.8 Silent Installation of Database Vault Fails If SID Is Not Specified in Correct Case

Bug 5679164

The Database Vault installer fails to detect the database during a silent installation. The following error is displayed:

OUI-10155:Error while setting variable s_dbSIDSelectedForUpgrade: The 10.2.0.3.0 database with the SID
you have specified does not exist in the system or does not run in the Oracle Home you have specified.

The workaround is to ensure that the value specified for the s_dbSIDSelectedForUpgrade variable in the response file uses the correct case. The s_dbSIDSelectedForUpgrade variable is used to provide the system identifier (SID) of the existing 10.2.0.3 database to the Database Vault installer. You should ensure that the SID is specified in the correct case. You can find the SID value for the existing database in the /etc/oratab file.

In case the installation fails again, use the uppercase value for SID.

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 Command Rule SELECT Not Found for SYSADM.%

Bug 5508407

The following error is displayed when you try to update the owner or the rule set for the SELECT command rule:

Command Rule SELECT not found for schema.%

After the update has failed, you are not allowed to delete the command rule. You can use the following workaround steps:

1. Login to SQL*Plus using the SYSTEM account. Run the following command:

   SQL>ALTER SYSTEM FLUSH SHARED_POOL;
   
   

2. Delete the command rule.

3. If you were trying to update the command rule, then re-create the command rule with the new parameters.

4. Repeat Step 1 for the new command rule to take effect.

2.4 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.

5.1 Snapshots and Materialized Views

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

5.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.