10g Release 2 (10.2.0.5) for IBM: Linux on System z
These Release Notes describe issues you may encounter with Oracle Database Vault 10g Release 2 (10.2.0.5). The Oracle Database Vault installation is covered in detail in Oracle Database Vault Installation Guide for IBM: Linux on System z.
This document may be updated after it is released. To check for updates to this document and to view other Oracle documentation, see the Documentation section on the Oracle Technology Network (OTN) Web site:
This document contains the following sections:
This section describes the known issues pertaining to installation. It also provides the workarounds that you can use.
Oratab entries get deleted on all node during instance deletion.
The workaround is take backup of the oratab file across the nodes, before instance deletion. After instance deletion completes restore the oratab file on the remaining nodes.
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:
Install Database Vault on the primary database.
Create a physical standby database using a hot backup of the primary database. This backup should include the Oracle home.
Set up communications between the primary and the physical standby database. Redo logs communicate changes from the primary database to the standby database.
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.
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 16 GB. In case the required swap space is shown as more than 16 GB, this warning can be safely ignored.
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.
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=
There may be invalid objects in the database after you install Oracle Database Vault.
Log into SQL*Plus as a user who has been granted the
SYSDBA administrative privilege. For example:
sqlplus sys as sysdba Enter password: password
In SQL*Plus, perform the following query to find invalid objects.
SELECT COUNT(*) FROM ALL_OBJECTS WHERE STATUS = 'INVALID';
If there are invalid objects, then run the
utlrp.sql script, which by default is located in the
$ORACLE_HOME/rdbms/admin directory, to recompile the invalid objects.
utlrp.sql script provides any instructions, follow them, and then run the script again. If the script terminates abnormally without giving any instructions, then run it again.
Oracle Bug: 7631281
This section discusses usage issues that you may encounter with Database Vault. It also provides the workarounds for these issues.
Accounts with the
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:
Disable the Database Vault command rule for the
ALTER USER command.
ALTER USER command.
Re-enable the Database Vault command rule for the
ALTER USER command.
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.
This section covers some of the frequently asked questions related to Database Vault installation. Oracle Database Vault installation is covered in detail in Oracle Database Vault Installation Guide for IBM: Linux on System z.
To allow the installer to find the database instance information, you should check the following:
The database home has Oracle Enterprise Manager Console DB 10.2.0.4.0 installed.
/etc/oratab has an entry for the database.
All database names listed in
/etc/oratab have unique system identifier (SID) names.
The oraInventory location is set in the
The oraInventory location set in
/var/opt/oracle/oraInst.loc is the same as the 10.2.0.5 Enterprise Edition database's oraInventory location.
The 10.2.0.5 database home does not have Oracle Database Vault in it.
The 10.2.0.5 database home does not contain an Automatic Storage Management (ASM) instance.
You would need to run Database Vault Configuration Assistant (DVCA) manually on the other databases. Refer to Oracle Database Vault Installation Guide for IBM: Linux on System z for detailed instructions.
You need to run DVCA manually on the other Oracle RAC nodes. Refer to Oracle Database Vault Installation Guide for IBM: Linux on System z for detailed instructions.
This section contains miscellaneous notes not covered in the Oracle Database Vault documentation.
SNAPSHOT is supported in place of
MATERIALIZED VIEW for backward compatibility.
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.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
Oracle customers have access to electronic support through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
Oracle Database Vault Release Notes 10g Release 2 (10.2.0.5) for IBM zSeries Based Linux
Copyright © 2008, 2013, 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 is software or related documentation that 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 END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
This software or hardware 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware 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.