Oracle® Database Vault

Installation Guide

10g Release 2 (10.2) for IBM: Linux on POWER Systems

B32494-05

April 2013

Oracle Database Vault Installation Guide, 10g Release 2 (10.2) for IBM: Linux on POWER Systems

B32494-05

Copyright © 2006, 2013, Oracle and/or its affiliates. All rights reserved.

Primary Author: Tanaya Bhattacharjee

Contributing Author: Pat Huey, Sumit Jeloka, Reema Khosla

Contributors: Scott Gaetjen, Xiaofang Wang, Jack Brinson, Chi Ching Chui, Kamal Tbeileh, Trivikrama Samudrala, Madhu Velukur, Rahul Joshi

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.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Part I Oracle Database Vault Installation

1 Oracle Database Vault Installation Overview

- 1.1 Database Vault Installation Environment

- 1.2 Database Vault Accounts

- 1.2.1 Database Vault Owner

- 1.2.2 Database Vault Account Manager

- 1.3 Default Audit Policy and Initialization Parameters

- 1.4 Installation Considerations

- 1.4.1 Hardware and Software Certification

- 1.4.2 Multiple Oracle Homes

2 Installing Oracle Database Vault

- 2.1 Preinstallation and Installation Tasks

- 2.1.1 Become Familiar with the Features of Oracle Database Vault

- 2.1.2 Check the Hardware Requirements

- 2.1.3 Check the Operating System Requirements

- 2.1.4 Check Kernel Parameters

- 2.1.5 Check the Database Requirements

- 2.1.5.1 Install Oracle Enterprise Manager Console DB

- 2.1.5.2 Apply Oracle Database Release 10.2.0.5 Patch Set

- 2.1.6 Prepare a Backup Strategy

- 2.1.7 Disable Custom Profiles

- 2.1.8 Verify That Oracle Clusterware Is Running (Oracle RAC Only)

- 2.1.9 Stop Existing Oracle Processes

- 2.1.9.1 Stop the Enterprise Manager Database Control Process

- 2.1.9.2 Stop the iSQL*Plus Process

- 2.1.9.3 Shut Down All Database Instances

- 2.1.10 Configure the Oracle User's Environment

- 2.1.11 Run Oracle Universal Installer to Install Oracle Database Vault

- 2.1.11.1 Downloading the Oracle Database Vault Software

- 2.1.11.2 Installing Oracle Database Vault with Oracle Universal Installer

- 2.2 Postinstallation Tasks

- 2.2.1 Back Up the Database

- 2.2.2 Update Environment Variables After the Upgrade (UNIX Systems Only)

- 2.2.3 Change Passwords for Oracle-Supplied Accounts

- 2.2.3.1 Using SQL*Plus to Unlock Accounts and Reset Passwords

- 2.2.4 Disable Remote SYSDBA Connections (Optional)

- 2.2.5 Start the Database on Other Nodes (Oracle RAC Only)

- 2.2.6 Configure Oracle Database Vault on Oracle RAC Nodes (Oracle RAC Only)

- 2.2.7 Set the Timeout Value for DVA (Optional)

- 2.2.8 Manually Deploy Oracle Database Vault Administrator (Special Cases)

- 2.2.8.1 Deploying Database Vault Administrator to a Standalone OC4J Container

- 2.2.8.2 Deploying Database Vault Administrator to the Database Console OC4J Container

- 2.3 Removing Oracle Software

Part II Appendixes

A How to Stop Processes in an Existing Oracle Real Application Clusters Database

B Using Response Files

- B.1 How Response Files Work

- B.1.1 General Procedure for Using Response Files

- B.2 Installing Database Vault Using a Response File

- B.2.1 Prepare the Response File

- B.2.2 Run Oracle Universal Installer Using the Response File

- B.3 Troubleshooting Silent Mode Installation

C Running DVCA After Creating a Database Vault Database

D Upgrading from a Previous Version of Database Vault

- D.1 Upgrading from a 10.2.0.x Version

E Database Listener Security Recommendations

- E.1 Security Checklist for the Database Listener

F Initialization Parameters

G Enabling Oracle Database Vault Administrator Accessibility

- G.1 Enabling Oracle Database Vault Administrator Accessibility Mode

- G.2 Providing Textual Descriptions of Database Vault Administrator Charts

Index

Preface

The Oracle Database Vault Installation Guide explains how to prepare for, install, and configure Oracle Database Vault with specific instructions for the operating system and Oracle software technology components that Database Vault requires.

Audience

This document is intended for Oracle DBAs as well as System Administrators who are involved in the installation of Oracle Database Vault and its related components.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

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.

Related Documents

For more information, refer to the following documents:

- Oracle Database Vault Release Notes for IBM: Linux on POWER Systems

- Oracle Database Vault Administrator's Guide

- Oracle Database Installation Guide

- Oracle Database Oracle Clusterware and Oracle Real Application Clusters Installation Guide for Linux

- Oracle Database Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Part I

Oracle Database Vault Installation

Part I introduces you to Oracle Database Vault installation concepts, requirements, and steps. This part contains the following chapters:

- Chapter 1, "Oracle Database Vault Installation Overview"

- Chapter 2, "Installing Oracle Database Vault"

1 Oracle Database Vault Installation Overview

Oracle Database Vault enables you to secure business data in ways that were not possible before. Database Vault uses a multifactored and multilayered approach to implementing database security.

This chapter provides an overview of the Database Vault installation process. This chapter includes the following sections:

- Database Vault Installation Environment

- Database Vault Accounts

- Installation Considerations

1.1 Database Vault Installation Environment

Oracle Database Vault can be installed as an option to the following:

- Oracle Database 10g Release 2 (10.2.0.5) standalone installation

- Oracle Database 10g Release 2 (10.2.0.5) with Oracle Real Application Clusters (Oracle RAC)

1.2 Database Vault Accounts

Database Vault prompts for two accounts that you can create during installation. These are the Database Vault Owner and the Database Vault Account Manager accounts. You must supply an account name and password for the Database Vault Owner during installation. Creating a Database Vault Account Manager is optional.

1.2.1 Database Vault Owner

The Database Vault Owner account is granted the DV_OWNER role. This account can manage Database Vault roles and configuration.

The Database Vault Owner user name can be a minimum of 2, and a maximum of 30 characters long. The account password can be a minimum of 8, and a maximum of 30 characters.

The password that you choose for the Database Vault Owner account must be a secure one. The following password restrictions are enforced:

- The password must include at least one alphabet, one digit, and one non alphanumeric character (symbol).

- The password cannot be the same as the account name.

- The password cannot contain any consecutive repeating characters.

1.2.2 Database Vault Account Manager

The Database Vault Account Manager is granted the DV_ACCTMGR role. This account is used to manage database user accounts. The Database Vault Account Manager is created to facilitate separation of duties. If you do not opt to create the Database Vault Account Manager account, then the DV_ACCTMGR role is granted to the Database Vault Owner account by default.

The Database Vault Account Manager user name can be a minimum of 2, and a maximum of 30 characters long. The account password can be a minimum of 8, and a maximum of 30 characters.

The same password restrictions that apply to Database Vault Owner are applicable to Database Vault Account Manager as well.

1.3 Default Audit Policy and Initialization Parameters

Oracle Database Vault installs a baseline database auditing policy. This policy covers the access control configuration information stored in Database Vault database tables, information stored in Oracle Catalog (rollback segments, tablespaces, and so on), the use of system privileges, and Oracle Label Security configuration.

See Also:
Oracle Database Vault Administrator's Guide for more information on the database audit policy

When you install Oracle Database Vault, the security specific database initialization parameters are initialized with default values. These security specific initialization parameters are listed in Appendix F

1.4 Installation Considerations

This section contains information that you should consider before deciding how to install this product. It contains the following sections:

- Hardware and Software Certification

- Multiple Oracle Homes

1.4.1 Hardware and Software Certification

The platform-specific hardware and software requirements included in this installation guide were current at the time this guide was published. However, because new platforms and operating system software versions might be certified after this guide is published, review the certification matrix on the My Oracle Support (formerly OracleMetaLink) Web site for the most up-to-date list of certified hardware platforms and operating system versions. My Oracle Support is available at the following URL:

https://support.oracle.com

1.4.2 Multiple Oracle Homes

This product supports multiple Oracle home, so you can install this release or previous releases of the software multiple times on the same system, in different Oracle home directories.

2 Installing Oracle Database Vault

This chapter includes an overview of the major steps required to install Oracle Database Vault into an existing Oracle Database 10g Release 2 (10.2.0.5) database. These procedures transform an existing Oracle Database system (including associated applications) into an Oracle Database Vault system. Databases upgraded using the procedures described in this chapter can work almost in the same manner as in earlier releases and, optionally, can leverage new Oracle Database Vault functionality. For a list of changes that Database Vault makes, refer to Appendix F, "Initialization Parameters" and Oracle Database Vault Administrator's Guide.

Note:
In order to upgrade a pre-10g Release 2 Oracle Database to Oracle Database Vault, you first must upgrade the database to a 10g Release 2 (10.2.0.5) database.

See Also:
Oracle Database Upgrade Guide for information about upgrading your Oracle Database to Oracle Database 10g Release 2

This chapter covers the following topics:

- Preinstallation and Installation Tasks

- Postinstallation Tasks

- Removing Oracle Software

2.1 Preinstallation and Installation Tasks

This section covers the following topics:

- Become Familiar with the Features of Oracle Database Vault

- Check the Hardware Requirements

- Check the Operating System Requirements

- Check Kernel Parameters

- Check the Database Requirements

- Prepare a Backup Strategy

- Disable Custom Profiles

- Verify That Oracle Clusterware Is Running (Oracle RAC Only)

- Stop Existing Oracle Processes

- Configure the Oracle User's Environment

- Run Oracle Universal Installer to Install Oracle Database Vault

2.1.1 Become Familiar with the Features of Oracle Database Vault

Before you plan the upgrade process, become familiar with the features of Oracle Database Vault. The Oracle Database Vault Administrator's Guide discusses the basic features of Oracle Database Vault.

2.1.2 Check the Hardware Requirements

The system must meet the following minimum hardware requirements:

- At least 1024 MB of physical RAM

- The following table describes the relationship between installed RAM and the configured swap space requirement.

RAM

Swap Space

Between 1024 MB and 2048 MB

1.5 times the size of RAM

Between 2049 MB and 8192 MB

Equal to the size of RAM

More than 8192 MB

0.75 times the size of RAM

- 90 MB of disk space in the /tmp directory

- 40 MB of disk space for the Oracle software

- 1.2 GB of disk space for a preconfigured database that uses file system storage (optional)

Note:
The disk space requirement for databases that use Automatic Storage Management or raw device storage is described later in this chapter.

Additional disk space, either on a file system or in an Automatic Storage Management disk group, is required for the flash recovery area if you choose to configure automated backups.

To ensure that the system meets these requirements:

1. To determine the physical RAM size, enter the following command:

# grep MemTotal /proc/meminfo

If the size of the physical RAM installed in the system is less than the required size, then you must install more memory before continuing.

2. To determine the size of the configured swap space, enter the following command:

# grep SwapTotal /proc/meminfo

If necessary, refer to your operating system documentation for information about how to configure additional swap space.

3. To determine the amount of disk space available in the /tmp directory, enter the following command:

# df -k /tmp

If there is less than 400 MB of free disk space available in the /tmp directory, then complete one of the following steps:

- Delete unnecessary files from the /tmp directory to meet the disk space requirement.

- Set the TMP and TMPDIR environment variables when setting the oracle user's environment.

- Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.

4. To determine the amount of free disk space on the system, enter the following command:

# df -k

5. To determine whether the system architecture can run the software, enter the following command:

# grep "model name" /proc/cpuinfo

Note:
This command displays the processor type. Verify that the processor architecture matches the Oracle software release that you install. If you do not see the expected output, then you cannot install the software on this system.

2.1.3 Check the Operating System Requirements

Depending on the products that you intend to install, verify that the following software is installed on the system. The procedure following the table describes how to verify whether these requirements are addressed.

Note:
Oracle Universal Installer performs checks on your system to verify that it meets the listed requirements. To ensure that these checks pass, verify the requirements before you start Oracle Universal Installer.

Item

Requirement

Operating system

One of the following operating system versions:

- Oracle Linux 4.0

- Oracle Linux 5.0

- Red Hat Enterprise Linux 3.0 (Update 3 or later)

- Red Hat Enterprise Linux 4.0

- Red Hat Enterprise Linux 5.0

- SUSE Linux Enterprise Server 9.0 with SP2 or later

- SUSE Linux Enterprise Server 10

- SUSE Linux Enterprise Server 11.0

- Asianux 2.0

The operating system requirements are the same as those for Oracle Database 10g Release 2. If you have Oracle Database 10g Release 2 installed, then your system automatically meets these requirements.

Kernel version

The system must be running the following kernel version (or a later version):
Oracle Linux 4.0 and Red Hat Enterprise Linux 4.0:

2.6.9-11.EL

Oracle Linux 5.0 and Red Hat Enterprise Linux 5.0:

2.6.18

SUSE Linux Enterprise Server 9:

2.6.5-7.191-pseries64

SUSE Linux Enterprise Server 10:

2.6.16.21

The kernel version requirements are the same as those for Oracle Database 10g release 2. If you have Oracle Database 10g Release 2 installed, then your system automatically meets the kernel version requirements.

Packages

The package requirements are the same as those for Oracle Database 10g Release 2. If you have Oracle Database 10g Release 2 installed, then your system automatically meets the package requirements.

Note:
Oracle Database Vault is installed in an existing Oracle home. All software requirements that were met while installing Oracle Database 10g Release 2 are sufficient for Oracle Database Vault.

To ensure that the system meets these requirements:

1. To determine which distribution and version of Linux is installed, enter the following command:

# cat /etc/issue

Note:
Only the distributions and versions listed in the previous table are supported. Do not install the software on other versions of Linux.

2. To determine whether the required kernel is installed, enter the following command:

# uname -r

The following is sample output displayed by running this command on a Red Hat Enterprise Linux 4.0 system:

2.6.9-11.EL

In this example, the output shows the kernel version (2.6.9) and errata level (11.EL) on the system.

If the kernel version does not meet the requirement specified earlier in this section, then contact your operating system vendor for information about obtaining and installing kernel updates.

3. To determine whether the required packages are installed, enter commands similar to the following:

# rpm -q package_name

If a package is not installed, then install it from your Linux distribution media or download the required package version from your Linux vendor's Web site.

4. If you require a CSD for WebSphere MQ, then refer to the following Web site for download and installation information:

http://www-947.ibm.com/support/entry/portal/Overview/Software/WebSphere/WebSphere_MQ

2.1.4 Check Kernel Parameters

Note:
The kernel parameter and shell limit values shown in the following section are recommended values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. Refer to your operating system documentation for more information about tuning kernel parameters.

Verify that the kernel parameters shown in the following table are set to values greater than or equal to the recommended value shown. The procedure following the table describes how to verify and set the values.

Parameter

Value

File

semmsl
semmns

semopm

semmni

250
32000

100

128

/proc/sys/kernel/sem

shmall

2097152

/proc/sys/kernel/shmall

shmmax

Half the size of physical memory (in bytes)

/proc/sys/kernel/shmmax

shmmni

4096

/proc/sys/kernel/shmmni

file-max

327679

/proc/sys/fs/file-max

ip_local_port_range

Minimum: 9000
Maximum: 65000

/proc/sys/net/ipv4/ip_local_port_range

rmem_default

262144

/proc/sys/net/core/rmem_default

rmem_max

2097152

/proc/sys/net/core/rmem_max

wmem_default

262144

/proc/sys/net/core/wmem_default

wmem_max

1048576

/proc/sys/net/core/wmem_max

Note:
If the current value for any parameter is higher than the value listed in this table, then do not change the value of that parameter.

To view the current value specified for these kernel parameters, and to change them if necessary:

1. Enter the commands shown in the following table to view the current values of the kernel parameters:

Note:

- You require root privileges to run the commands.

- Make a note of the current parameter values and identify any values that you must change.

Parameter

Command

semmsl, semmns, semopm, and semmni

# /sbin/sysctl -a | grep sem
This command displays the value of the semaphore parameters in the order listed.

shmall, shmmax, and shmmni

# /sbin/sysctl -a | grep shm
This command displays the details of the shared memory segment sizes.

file-max

# /sbin/sysctl -a | grep file-max
This command displays the maximum number of file handles.

ip_local_port_range

# /sbin/sysctl -a | grep ip_local_port_range
This command displays a range of port numbers.

rmem_default

# /sbin/sysctl -a | grep rmem_default

rmem_max

# /sbin/sysctl -a | grep rmem_max

wmem_default

# /sbin/sysctl -a | grep wmem_default

wmem_max

# /sbin/sysctl -a | grep wmem_max

2. If the value of any kernel parameter is different from the recommended value, then complete the following procedure:
Using any text editor, create or edit the /etc/sysctl.conf file, and add or edit lines similar to the following:

Note:
Include lines only for the kernel parameter values that you change. For the semaphore parameters (kernel.sem), you must specify all four values. However, if any of the current values are larger than the recommended value, then specify the larger value.

kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 327679
net.ipv4.ip_local_port_range = 9000 65000
net.core.rmem_default = 262144
net.core.rmem_max = 2097152
net.core.wmem_default = 262144
net.core.wmem_max = 1048576

By specifying the values in the /etc/sysctl.conf file, they persist when you restart the system.

On SUSE systems only, enter the following command to ensure that the system reads the /etc/sysctl.conf file when it restarts:

# /sbin/chkconfig boot.sysctl on

Setting Shell Limits for the oracle User

To improve the performance of the software on Linux systems, you must increase the following shell limits for the oracle user:

Shell Limit

Item in limits.conf

Hard Limit

Maximum number of open file descriptors

nofile

65536

Maximum number of processes available to a single user

nproc

16384

To increase the shell limits:

1. Add the following lines to the /etc/security/limits.conf file:

oracle              soft    nproc   2047
oracle              hard    nproc   16384
oracle              soft    nofile  1024
oracle              hard    nofile  65536

2. Add or edit the following line in the /etc/pam.d/login file, if it does not exist:

session    required     pam_limits.so

3. Depending on the oracle user's default shell, make the following changes to the default shell start-up file:

- For the Bourne, Bash, or Korn shell, add the following lines to the /etc/profile file (or the file on SUSE systems)/etc/profile.local):

if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
fi

- For the C shell (csh or tcsh), add the following lines to the /etc/csh.login file (or the file on SUSE systems)/etc/csh.login.local):

if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
endif

2.1.5 Check the Database Requirements

In order to install Oracle Database Vault, you must be running the Enterprise Edition of Oracle Database 10g Release 2 (10.2.0.5). The database should also have Oracle Enterprise Manager Console DB 10.2.0.5.0 installed. In addition, the Database Vault installer requires write access to the files, oratab and oraInst.loc.

A listener must have been configured for the existing database. Oracle Net Configuration Assistant configures the listener when you first install the database. You can also use Oracle Enterprise Manager to administer listeners.

You must have an existing password file for the database. The password file authentication parameter, REMOTE_LOGIN_PASSWORDFILE must have been set to EXCLUSIVE or SHARED.

You can set the REMOTE_LOGIN_PASSWORDFILE parameter in the init.ora file. Use the orapwd utility to create and manage password files.

See Also:
Oracle Database Administrator's Guide for more information on creating and maintaining a password file

The following topics discuss applying the 10.2.0.5 patch set and installing the required components:

- Install Oracle Enterprise Manager Console DB

- Apply Oracle Database Release 10.2.0.5 Patch Set

2.1.5.1 Install Oracle Enterprise Manager Console DB

Before installing Oracle Database Vault, you should ensure that Oracle Enterprise Manager Console DB 10.2.0.5.0 is installed. Oracle Enterprise Manager Console DB is installed using the Oracle Universal Installer (OUI). The following steps summarize installing Oracle Enterprise Manager Console DB:

1. Run Oracle Universal Installer (OUI) and perform a custom installation to install Oracle Enterprise Manager Console DB 10.2.0.1.0. Add Oracle Enterprise Manager Console DB from the list of available product components.

2. Apply the Oracle Database release 10.2.0.5 patch set.

Note:
You can configure the database to use Enterprise Manager Database Control by using Database Configuration Assistant (DBCA). However, configuring Enterprise Manager Database Control is not a prerequisite for installing Oracle Database Vault.

2.1.5.2 Apply Oracle Database Release 10.2.0.5 Patch Set

To install Oracle Database Vault, you must upgrade the database to Oracle Database Release 10.2.0.5. Oracle strongly recommends that you back up your database before performing any upgrade or installation.

See Also:
Oracle Database Backup and Recovery Advanced User's Guide for information on database backups

This section covers the following topics:

Patch Set Overview

You can apply the Oracle Database release 10.2.0.5 patch set to the following Oracle Database 10g Release 2 installations:

- Oracle Database

- Oracle Real Application Clusters

- Oracle Database Client

- Oracle Database Companion CD

- Oracle Clusterware

- Oracle Database Vault

Oracle Universal Installer Version Requirements

This patch set includes Oracle Universal Installer release 10.2.0.5, which is also installed when you install this patch set. This is to ensure that your Oracle home can be patched in the future. You should not use the Installer from the earlier maintenance release media or Oracle home.

This is not a complete software distribution. You must install it in an existing Oracle Database 10g Release 2 installation.

Patch Set Documentation

There are two documents related to this release of the Oracle Database patch set:

- Oracle Database Patch Set Notes, 10g Release 2 (10.2.0.3) Patch Set for Linux on POWER

- Oracle Database List of Bugs Fixed, 10g Release 2 (10.2.0.3) Patch Set

Both of these documents are included with the patch set. In addition, they are available on the My Oracle Support (formerly OracleMetalink) Web site:

https://support.oracle.com

2.1.6 Prepare a Backup Strategy

Oracle strongly recommends that you back up your database before performing any upgrade or installation. The ultimate success of your upgrade depends heavily on the design and execution of an appropriate backup strategy. To develop a backup strategy, consider the following questions:

- How long can the production database remain inoperable before business consequences become intolerable?

- What backup strategy is necessary to meet your availability requirements?

- Are backups archived in a safe, offsite location?

- How quickly can backups be restored (including backups in offsite storage)?

- Have recovery procedures been tested successfully?

Your backup strategy should answer all of these questions and include procedures for successfully backing up and recovering your database.

See Also:
Oracle Database Backup and Recovery Advanced User's Guide for information on database backups

2.1.7 Disable Custom Profiles

If you have created custom profiles and password complexity checks in your existing database, then you must disable these before performing the installation. You can reenable these after the installation is complete. Use the following steps to achieve this:

1. Extract the profile names and associated settings for each profile that is being used. You can use a script to accomplish this.

Example 2-1 shows a sample script that extracts the profile names and settings to create an output script called, myprofiles.sql. After the installation is complete, you can run myprofiles.sql to restore the profile settings.

Example 2-1 Extracting Profiles

set serverout on size 100000
spool myprofiles.sql
.
declare
l_last varchar2(30) := 'X';
l_count number := 0;
begin
for c in (
select profile, resource_name , limit
from dba_profiles
order by profile, resource_name
) loop
if l_last <> c.profile then
l_last := c.profile;
if l_count > 0 then
dbms_output.put_line(';');
end if;
l_count := l_count + 1;
dbms_output.put_line('create profile ' || c.profile || ' limit ');
else
dbms_output.put_line('    ' || c.resource_name || ' ' || c.limit);
end if;
end loop;
dbms_output.put_line(';');
end;
/
.
spool off

2. Disable the custom profiles and password complexity settings. For example:

SQL> ALTER PROFILE SomeCustomProfile LIMIT
PASSWORD_REUSE_MAX UNLIMITED -- The number of times a password can be reused
PASSWORD_REUSE_TIME UNLIMITED -- The number of days between reuses of a password
PASSWORD_VERIFY_FUNCTION NULL
/

3. After the Oracle Database Vault installation is complete, reenable the profiles by running the script created in Step 1.
SQL>@myprofiles.sql

2.1.8 Verify That Oracle Clusterware Is Running (Oracle RAC Only)

Oracle Clusterware should be running for the Database Vault installer to find the existing Oracle Real Application Clusters (Oracle RAC) instances. If you have stopped Oracle Clusterware, then you should restart it before running Oracle Universal Installer. Use the following command to start Oracle Clusterware:

$CRS_HOME/bin/crsctl start crs

Note:

- You must run the crsctl command as the root user. You must run this command on all cluster nodes.

- The crsctl start crs command also starts the database. You must shut down the database before running Oracle Universal Installer.

2.1.9 Stop Existing Oracle Processes

Stop all processes running in the Oracle home, except the database listener. You must complete this task to enable Oracle Universal Installer to relink certain executables and libraries. For Oracle RAC databases, you must stop the processes on all nodes.

Stop the processes in the following order:

1. Stop the Enterprise Manager Database Control Process

2. Stop the iSQL*Plus Process

3. Shut Down All Database Instances

2.1.9.1 Stop the Enterprise Manager Database Control Process

Stop the Enterprise Manager Database Control process, if it is running. Use the following command:

$ORACLE_HOME/bin/emctl stop dbconsole

2.1.9.2 Stop the iSQL*Plus Process

Stop the iSQL*Plus process, using the following command:

$ORACLE_HOME/bin/isqlplusctl stop

2.1.9.3 Shut Down All Database Instances

Shut down all database instances running from the Oracle home directory into which Oracle Database Vault is to be installed.

sqlplus SYS "AS SYSDBA"
Enter password:
SQL> shutdown immediate

2.1.10 Configure the Oracle User's Environment

Run Oracle Universal Installer (OUI) using the account that owns the Oracle software. This is usually the oracle account.

However, before you start Oracle Universal Installer you must configure the environment of the oracle user. To configure the environment, you must:

- Set the default file mode creation mask (umask) to 022 in the shell startup file.

- Set the DISPLAY environment variable.

Note:
Ensure that the PATH variable contains $ORACLE_HOME/bin before /usr/X11R6/bin.

To set the oracle user's environment:

1. Start a new terminal session, for example, an X terminal (xterm).

2. Enter the following command to ensure that X Window applications can display on this system:

$ xhost fully_qualified_remote_host_name

For example:

$ xhost somehost.us.acme.com

3. If you are not logged in to the system where you want to install the software, then log in to that system as the oracle user.

4. If you are not logged in as the oracle user, then switch user to oracle:

$ su - oracle

5. To determine the default shell for the oracle user, enter the following command:

$ echo $SHELL

6. Open the oracle user's shell startup file in any text editor:

Note:
On Red Hat Linux, .bash_profile is the user startup file for the Bash shell.

- Bourne shell (sh), Bash shell (bash), or Korn shell (ksh):

$ vi .bash_profile

- C shell (csh or tcsh):

% vi .login

7. Enter or edit the following line, specifying a value of 022 for the default file mode creation mask:

umask 022

8. If the ORACLE_SID, ORACLE_HOME, or ORACLE_BASE environment variable is set in the file, then remove the corresponding lines from the file.

9. Save the file, and exit from the editor.

10. To run the shell startup script, enter one of the following commands:

- Bash shell on Red Hat Enterprise Linux:

$ . ./.bash_profile

- Bourne, Bash, or Korn shell:

$ . ./.profile

- C shell:

% source ./.login

11. If you are not installing the software on the local system, then enter a command similar to the following to direct X applications to display on the local system:

- Bourne, Bash, or Korn shell:

$ DISPLAY=local_host:0.0 ; export DISPLAY

- C shell:

% setenv DISPLAY local_host:0.0

In this example, local_host is the host name or IP address of the system that you use to display Oracle Universal Installer (your workstation or PC).

12. If you determined that the /tmp directory has less than 90 MB of free disk space, then identify a file system with at least 90 MB of free space and set the TEMP and TMPDIR environment variables to specify a temporary directory on this file system:

1. Use the df -k command to identify a suitable file system with sufficient free space.

2. If necessary, enter commands similar to the following to create a temporary directory on the file system that you identified, and set the appropriate permissions on the directory:

$ su - root
# mkdir /mount_point/tmp
# chmod a+wr /mount_point/tmp
# exit

3. Enter commands similar to the following to set the TEMP and TMPDIR environment variables:

- Bourne, Bash, or Korn shell:

$ TEMP=/mount_point/tmp
$ TMPDIR=/mount_point/tmp
$ export TEMP TMPDIR

- C shell:

% setenv TEMP /mount_point/tmp
% setenv TMPDIR /mount_point/tmp

13. Enter commands similar to the following to set the ORACLE_BASE and ORACLE_SID environment variables:

- Bourne, Bash, or Korn shell:

$ ORACLE_BASE=/u01/app/oracle
$ ORACLE_SID=sales
$ export ORACLE_BASE ORACLE_SID

- C shell:

% setenv ORACLE_BASE /u01/app/oracle
% setenv ORACLE_SID sales

In these examples, /u01/app/oracle is the Oracle base directory that you created or identified earlier and sales is the name to call the database (typically no more than five characters).

14. Enter the following commands to ensure that the ORACLE_HOME and TNS_ADMIN environment variables are not set:

- Bourne, Bash, or Korn shell:

$ unset ORACLE_HOME
$ unset TNS_ADMIN

- C shell:

% unsetenv ORACLE_HOME
% unsetenv TNS_ADMIN

15. To verify that the environment has been set correctly, enter the following commands:

$ umask
$ env | more

Verify that the umask command displays a value of 22, 022, or 0022 and the environment variables that you set in this section have the correct values.

2.1.11 Run Oracle Universal Installer to Install Oracle Database Vault

This section contains:

- Downloading the Oracle Database Vault Software

- Installing Oracle Database Vault with Oracle Universal Installer

2.1.11.1 Downloading the Oracle Database Vault Software

You can download the Oracle Database Vault software from the following web site:

http://www.oracle.com/technetwork/database/options/database-vault/index-090593.html

2.1.11.2 Installing Oracle Database Vault with Oracle Universal Installer

After you download and extract the Oracle Database Vault software, you can use Oracle Universal Installer (OUI), which is provided in the download, to install Oracle Database Vault into an existing Oracle Database 10g Release 2 (10.2.0.5) database.

To install Oracle Database Vault:

1. Log on as a member of the Administrators group.
If you are installing on a Primary Domain Controller (PDC) or a Backup Domain Controller (BDC), log on as a member of the Domain Administrators group.

2. Insert Oracle Database Vault installation media and navigate to the database directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.
Use the same installation media to install Oracle Database Vault on all supported Windows platforms.

3. Double-click setup.exe to start Oracle Universal Installer.

4. In the Specify Installation Details screen, you need to specify the path to the Oracle home that contains the existing Oracle Database. The Destination Path box lists the Oracle home paths of all Oracle Database 10g Release 2 (10.2.0.5) Enterprise Edition databases registered with the system.
Select the Oracle home corresponding to the database into which you want to install Oracle Database Vault.

Note:

- If an Oracle home does not have an Enterprise Edition of Oracle Database 10g Release 2 (10.2.0.5) installed, then it is not displayed. You must ensure that the Oracle home has an Enterprise Edition of Oracle Database 10g Release 2 (10.2.0.5) installed.

- If an Oracle home does not have Oracle Enterprise Manager Console DB 10.2.0.5.0 installed, then it is not displayed. You must ensure that the Oracle home has Oracle Enterprise Manager Console DB 10.2.0.5.0 installed.

- If an Oracle home contains an Automatic Storage Management (ASM) instance, then it is not displayed. You cannot install Oracle Database Vault into an Oracle home that also contains an ASM instance.

- If an Oracle home already contains Oracle Database Vault, then it is not displayed. You cannot install Oracle Database Vault into an Oracle home more than once.

- Oracle Clusterware should be running for the Database Vault installer to find the existing Oracle Real Application Clusters (Oracle RAC) databases. Ensure that Oracle Clusterware is running before installing Oracle Database Vault. You can use the crsctl command to start Oracle Clusterware.

5. Enter a user name for the Database Vault Owner account in the Database Vault Owner field. The user name can be a minimum of 2 and maximum of 30 characters long.

6. Enter a password for the Database Vault Owner account in the Database Vault Owner Password field. The password can be a minimum of 8 and a maximum of 30 characters. The password must include at least one alphabet, one digit, and one nonalphanumeric character (symbol). It cannot be the same as the account names for either the Database Vault owner or the Database Vault account manager. It cannot contain any consecutive repeating characters.

7. Reenter the password in the Confirm Password field.

8. Select Create a Separate Account Manager if you want to create a separate Account Manager to manage Oracle Database Vault accounts.

9. In the Database Vault Account Manager field, enter a user name for the Database Vault Account Manager if you have chosen to select the Create a Separate Account Manager check box. The user name can be a minimum of 2 and a maximum of 30 characters.

10. Enter a password for the Database Vault Account Manager account in the Account Manager Password field. The password can be a minimum of 8 and a maximum of 30 characters. The password must include at least one alphabet, one digit, and one nonalphanumeric character (symbol). It cannot be the same as the account names for either the Database Vault owner or the Database Vault account manager. It cannot contain any consecutive repeating characters.

11. Reenter the password in the Confirm Password field. Click Next.

12. The Select Existing Database screen is displayed. A list of all databases running from the selected Oracle home is displayed. Select the database into which you wish to install Oracle Database Vault.

Note:

- Oracle recommends that you install Oracle Database Vault into an Oracle home containing only a single database.
If there are multiple databases in an Oracle home, you must enable Database Vault for all the databases. You cannot have Database Vault enabled databases coexist with non-Database Vault enabled databases in the same Oracle home. In order to enable Database Vault for addtional databases in the same Oracle home, refer to Appendix C, "Running DVCA After Creating a Database Vault Database"

- If a database is not listed, then check to make sure that you have followed the instructions under "Check the Database Requirements".

13. Enter the existing SYS user password for the selected database in the Existing Database SYS Password field.

14. Reenter the SYS password in the Confirm Password field. Click Next.

Note:
At this point, the database requirements are validated.

15. You are prompted to shut down all Oracle processes running from the Oracle home before proceeding. Shut down the Oracle processes, if you have not already done so.

See Also:
"Stop Existing Oracle Processes" for more information on stopping existing Oracle processes

16. Product-specific prerequisite checks are performed. Confirm that all tests have passed. Click Next to continue.

17. The Summary screen is displayed with the installation details. Verify the details and click Install.

18. The Installation screen is displayed. After the installation completes, the Database Vault Configuration Assistant (DVCA) is run automatically. DVCA helps configure the Database Vault installation.

2.2 Postinstallation Tasks

This section lists the tasks to perform after you have completed an upgrade of your database. The following topics are discussed:

- Back Up the Database

- Update Environment Variables After the Upgrade (UNIX Systems Only)

- Change Passwords for Oracle-Supplied Accounts

- Disable Remote SYSDBA Connections (Optional)

- Start the Database on Other Nodes (Oracle RAC Only)

- Configure Oracle Database Vault on Oracle RAC Nodes (Oracle RAC Only)

- Set the Timeout Value for DVA (Optional)

- Manually Deploy Oracle Database Vault Administrator (Special Cases)

2.2.1 Back Up the Database

Make sure you perform a full backup of the production database. Refer to Oracle Database Backup and Recovery Advanced User's Guide for details on backing up a database.

2.2.2 Update Environment Variables After the Upgrade (UNIX Systems Only)

Ensure that the following environment variables point to the correct Oracle Database Vault directories:

- ORACLE_HOME

- PATH

- ORA_NLS10

Note:
The ORA_NLS10 environment variable replaces the ORA_NLS33 environment variable, so you may must unset ORA_NLS33 and set ORA_NLS10.

- LD_LIBRARY_PATH

2.2.3 Change Passwords for Oracle-Supplied Accounts

Oracle strongly recommends that you change the password for each account after installation. You can effectively implement the strong security provided by Oracle Database Vault.

Note:
If you are creating a database using Database Configuration Assistant, you can unlock accounts after the database is created by clicking Password Management before you exit from Database Configuration Assistant.

2.2.3.1 Using SQL*Plus to Unlock Accounts and Reset Passwords

To unlock and reset user account passwords using SQL*Plus:

1. Start SQL*Plus and log in using the Database Vault Account Manager account. If you did not create the Database Vault Account Manager account during installation, then you must log in using the Database Vault Owner account.

2. Enter a command similar to the following, where account is the user account to unlock and password is the new password:

SQL> ALTER USER account [ IDENTIFIED BY password ] ACCOUNT UNLOCK;

In this example:

- The ACCOUNT UNLOCK clause unlocks the account.

- The IDENTIFED BY password clause resets the password.

Note:
If you unlock an account but do not reset the password, then the password remains expired. The first time someone connects as that user, they must change the user's password.
To permit unauthenticated access to your data through HTTP, unlock the ANONYMOUS user account.

See Also:
Oracle Database Administrator's Guide for more information about:

- Unlocking and changing passwords after installation

- Oracle security procedures

- Best security practices

2.2.4 Disable Remote SYSDBA Connections (Optional)

Oracle Database Vault enables you to disable remote logins with SYSDBA privileges, for enhanced security for your database.

To disable remote SYSDBA connections, re-create the password file with the nosysdba flag set to y (Yes). A user can still log in AS SYSDBA locally using Operating System (OS) authentication. However, remote connections AS SYSDBA fails.

Use the following syntax to re-create the password file:

orapwd file=filename password=password [entries=users] force=y nosysdba=y

Where:

- file: Name of password file (mandatory)

- password: Password for SYS (mandatory). Enter at least six alphanumeric characters.

- entries: Maximum number of distinct DBA users

- force: Whether to overwrite the existing file

- nosysdba: Whether to enable or disable the SYS logon
The default is no, so if you omit this flag, the password file is created enabling SYSDBA access for Oracle Database Vault instances.

For example:

orapwd file=$ORACLE_HOME/dbs/orapworcl password=5hjk99 force=y nosysdba=y

Note:
Do not insert spaces around the equal (=) character.

See Also:
Oracle Database Administrator's Guide for more information on using the orapwd utility

When you re-create the password file, any accounts other than SYS that were granted the SYSDBA or SYSOPER privileges have those privileges removed. You must regrant the privileges for these accounts after you have re-created the password file.

You can reenable the ability to connect with the SYSDBA privilege by re-creating the password file with the nosysdba flag set to n (No). You might need to reenable the ability to connect with SYSDBA privileges, if certain products or utilities require it's use.

Enabling or Disabling Connecting with SYSDBA on Oracle Real Application Clusters Systems

Under a cluster file system and raw devices, the password file under $ORACLE_HOME is in a symbolic link that points to the shared storage location in the default configuration. In this case, the orapwd command you issue affects all nodes.

Enabling or Disabling Connecting with SYSDBA on Automatic Storage Management Systems

For Automatic Storage Management systems, you must update each node to enable or disable the SYSDBA connection privilege by using the orapwd utility.

2.2.5 Start the Database on Other Nodes (Oracle RAC Only)

You must start the database on all Oracle RAC nodes other than the one on which the installation is performed. Use the following command to start the database:

Note:
You need SYSDBA privileges to run these commands.

srvctl start instance -d sid -i instance_name

Note:
You must use the Server Control (srvctl) utility to start and stop Oracle Database Vault Oracle RAC instances. Do not use SQL*Plus to start and stop Oracle RAC instances.

2.2.6 Configure Oracle Database Vault on Oracle RAC Nodes (Oracle RAC Only)

After you install Oracle Database Vault for an Oracle Real Application Clusters (Oracle RAC) instance, complete the following procedure for each Oracle RAC node. This procedure assumes that you have a separate Oracle home for each node.

Note:
The dvca -action optionrac option has been deprecated and can no longer be used to configure Oracle RAC nodes.

1. Log in to SQL*Plus as user SYS with the SYSDBA privilege.

sqlplus sys as sysdba
Enter password: password

2. Run the following ALTER SYSTEM statements:

ALTER SYSTEM SET AUDIT_SYS_OPERATIONS=TRUE SCOPE=SPFILE;
ALTER SYSTEM SET OS_ROLES=FALSE SCOPE=SPFILE;
ALTER SYSTEM SET RECYCLEBIN='OFF' SCOPE=SPFILE;
ALTER SYSTEM SET REMOTE_LOGIN_PASSWORDFILE='EXCLUSIVE' SCOPE=SPFILE;
ALTER SYSTEM SET SQL92_SECURITY=TRUE SCOPE=SPFILE;
ALTER SYSTEM SET OS_AUTHENT_PREFIX='' SCOPE=SPFILE;

3. Restart Oracle Database.

$ORACLE_HOME/bin/srvctl stop database -d db_name
$ORACLE_HOME/bin/srvctl start database -d db_name

2.2.7 Set the Timeout Value for DVA (Optional)

Oracle Database Vault Administrator (DVA) is a browser-based graphical user interface console that you can use to manage Oracle Database Vault.

You can modify the length of time that DVA stays connected while inactive. By default, the connection duration is 35 minutes. Your session automatically gets expired after 35 minutes of inactivity.

To set the session time for Oracle Database Vault Administrator:

1. Back up the web.xml file, which by default is in the $ORACLE_HOME/dv/jlib/dva_webapp/dva_webapp/WEB-INF directory.

2. In a text editor, open the web.xml file .

3. Search for the following setting:

<session-config>
<session-timeout>35</session-timeout>
</session-config>

4. Change the <session-timeout> setting to the amount of time in minutes that you prefer.

5. Save and close the web.xml file.

6. Stop and restart the DVA application.
You can use the following command to restart DVA:

emctl stop dbconsole
emctl start dbconsole

2.2.8 Manually Deploy Oracle Database Vault Administrator (Special Cases)

If you have created an Oracle database manually, and have configured Oracle Enterprise Manager Database Control by using Enterprise Manager Configuration Assistant, you must manually deploy Oracle Database Vault Administrator. This procedure deploys Database Vault Administrator in the same OC4J container as the current Enterprise Manager, rather than creating a new application.

This section contains:

- Deploying Database Vault Administrator to a Standalone OC4J Container

- Deploying Database Vault Administrator to the Database Console OC4J Container

2.2.8.1 Deploying Database Vault Administrator to a Standalone OC4J Container

You can manually deploy Database Vault Administrator to the Oracle Application Server Containers for J2EE (OC4J) home, which by default is in the $ORACLE_HOME/oc4j/j2ee/home directory.

To manually deploy Database Vault Administrator:

1. Edit the file $ORACLE_HOME/oc4j/j2ee/home/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" />

For example:

<application name="dva" path="/u00/app/oracle/oracle/product/dv12/dv/jlib/dva_webapp.ear" auto-start="true" />

2. Edit the file $ORACLE_HOME/oc4j/j2ee/home/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" />

3. Edit the file $ORACLE_HOME/oc4j/j2ee/home/config/global-web-application.xml. Search for <servlet-class>oracle.jsp.runtimev2.JspServlet</servlet-class>. Uncomment the following lines after this:

<init-param>
<param-name>main_mode</param-name>
<param-value>justrun</param-value>
</init-param>

4. Create the following directory:

mkdir -p $ORACLE_HOME/dv/jlib/sysman/config

5. Create the database connection configuration file, emoms.properties, in the configuration directory that you just created. Add the following lines to the file:

oracle.sysman.emSDK.svlt.ConsoleMode=standalone
oracle.sysman.eml.mntr.emdRepRAC=FALSE
oracle.sysman.eml.mntr.emdRepDBName=oracle_sid
oracle.system.eml.mntr.emdRepConnectDescriptor=TNS_connection_string

Follow these instructions:

- For an Oracle RAC environment, set oracle.sysman.eml.mntr.emdRepRAC to TRUE.

- For oracle.sysman.eml.mntr.emdRepConnectDescriptor, you can use an alias from $ORACLE_HOME/network/admin/tnsnames.ora. Alternatively, you can use the following syntax:

oracle.sysman.eml.mntr.emdRepConnectDescriptor=
(DESCRIPTION\=
(ADDRESS_LIST\=(ADDRESS\=(PROTOCOL\=TCP) (HOST\=HOSTNAME)(PORT\=PORT)))
(CONNECT_DATA\=
(SERVICE_NAME\=ORACLE_SID))

6. Ensure that the correct environment variables are set.
For example:

ORACLE_SID=orcl
export ORACLE_SID
ORACLE_HOME=/u00/app/oracle/product/11.1/dv
export ORACLE_HOME
LD_LIBRARY_PATH=$ORACLE_HOME/bin:$ORACLE_HOME/lib32:$ORACLE_HOME/lib:$ORACLE_HOME/jdbc/lib
export LD_LIBRARY_PATH
PATH=$ORACLE_HOME/bin:$ORACLE_HOME/jdk/bin:$PATH
export PATH

Ensure that you set the LD_LIBRARY_PATH variable to use the OCI-based JDBC libraries.

7. Start OC4J using the following syntax:

$ORACLE_HOME/jdk/bin/java -Djava.awt.headless=true -DEMDROOT=$ORACLE_HOME/dv/jlib -jar $ORACLE_HOME/oc4j/j2ee/home/oc4j.jar -userThreads -config $ORACLE_HOME/oc4j/j2ee/home/config/server.xml

After you complete these steps, you can start Database Vault Administrator. The HTTP port defaults to 8888 for this environment. Use the following syntax for the URL:

http://hostname:8888/dva

2.2.8.2 Deploying Database Vault Administrator to the Database Console OC4J Container

To manually deploy Database Vault Administrator to the Database Console OC4J container:

1. Stop Oracle Database Console.

- UNIX: Go to the $ORACLE_HOME/bin directory and run the following command:

./emctl stop dbconsole

- Microsoft Windows: In the Administrative Services, select the Services utility, and then right-click the OracleDBConsolesid service. Select Stop from the menu.

2. Create a backup copy and then open the $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_service_name/config/server.xml file.

3. Add the following line before the </application-server> element:

<application name="dva" path="$ORACLE_HOME/dv/jlib/dva_webapp.ear" parent="default" start="true" />

On Windows systems, replace $ORACLE_HOME with the absolute path to your Oracle Database home.

4. Create a backup copy and then open the $ORACLE_HOME/oc4j/j2ee/OC4J_DBConsole_service_name/config/http-web-site.xml file.

5. Add the following line before the </web-site> element:

<web-app application="dva" name="dva_webapp" load-on-startup="true" root="/dva" shared="true"/>

6. Restart Oracle Database Console.

- UNIX: Go to the $ORACLE_HOME/bin directory and run the following command:

./emctl start dbconsole

- Windows: In the Administrative Services, select the Services utility, and then right-click the OracleDBConsolesid service. Select Start from the menu.

After you complete these steps, you can start Oracle Database Vault Administrator by using the following URL:

https://hostname:port/dva

For example:

https://myserver:1158/dva

If you are unsure of the port number, open the ORACLE_HOME/host_sid/sysman/config/emd.properties file and search for REPOSITORY_URL. In most cases, the host name and port number are the same as Oracle Enterprise Manager Database Control.

2.3 Removing Oracle Software

Use Oracle Universal Installer (OUI) to remove Oracle software from an Oracle home. The following list summarizes the steps involved:

1. Log in as the user that owns the Oracle software. This is usually the oracle user.

2. Shut down all processes running in the Oracle home.

3. Start Oracle Universal Installer as follows:

$ $ORACLE_HOME/oui/bin/runInstaller

4. In the Welcome screen, select Deinstall Products. The Inventory screen appears. This screen lists all the Oracle homes on the system.

5. Select the Oracle home and the products to remove and click Remove.

See Also:
Refer to the Oracle Database Installation Guide for details on removing Oracle software

Note:
You cannot remove or uninstall the Database Vault option. However, you can disable Oracle Database Vault. Refer to Oracle Database Vault Administrator's Guide for more details.
You can also remove the entire Oracle home, as discussed earlier in this section.

Part II

Appendixes

Part II includes the appendixes. The contents of this part are:

- Appendix A, "How to Stop Processes in an Existing Oracle Real Application Clusters Database"

- Appendix B, "Using Response Files"

- Appendix C, "Running DVCA After Creating a Database Vault Database"

- Appendix D, "Upgrading from a Previous Version of Database Vault"

- Appendix E, "Database Listener Security Recommendations"

- Appendix F, "Initialization Parameters"

- Appendix G, "Enabling Oracle Database Vault Administrator Accessibility"

A How to Stop Processes in an Existing Oracle Real Application Clusters Database

This appendix describes how to stop all processes in an Oracle Real Application Clusters (Oracle RAC) database, in preparation for installing Database Vault.

Note:
Before you make any changes to the Oracle software, Oracle recommends that you create a backup of the Oracle Database installation.

To stop all processes in an Oracle Real Application Clusters (Oracle RAC) database, use the following steps:

Note:
You must perform these steps in the order listed.

1. Ensure that the environment variables, ORACLE_HOME, ORACLE_SID, and PATH are correctly set.

2. Shut down any processes in the Oracle home on each node that can access a database. For example, you must shut down Oracle Enterprise Manager Database Control.

$ORACLE_HOME/bin/emctl stop dbconsole

Note:

- You must run the preceding command on all nodes.

- Before you shut down any processes that are monitored by Enterprise Manager Grid Control, set a blackout in Grid Control for the processes that you intend to shut down. This is necessary so that the availability records for these processes indicate that the shutdown was planned downtime, rather than an unplanned system outage.

3. Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database:

$ORACLE_HOME/bin/srvctl stop database -d db_name

B Using Response Files

This appendix describes how to install Oracle Database Vault using a response file. It includes the following topics:

- How Response Files Work

- Installing Database Vault Using a Response File

- Troubleshooting Silent Mode Installation

B.1 How Response Files Work

You can automate the installation and configuration of Oracle software by specifying a response file when you start Oracle Universal Installer. Oracle Universal Installer uses the values contained in the response file to provide answers to some or all of Oracle Universal Installer prompts.

Typically, Oracle Universal Installer runs in interactive mode, which means that it prompts you to provide information in graphical user interface (GUI) screens. When you use response files to provide this information, you run Oracle Universal Installer at a command prompt using the silent mode.

During a silent mode installation, Oracle Universal Installer does not display any screens. Instead, it displays progress information in the terminal that you used to start it.

You define the settings for a silent mode installation by entering values for the variables listed in the response file. For instance, to specify the Oracle home, you would supply the appropriate value for the ORACLE_HOME variable, as in the following example:

ORACLE_HOME = "/home/Oracle/OraDBHome1"

Another way of specifying the response file's variable settings is to pass them as command line arguments when you run Oracle Universal Installer. For example:

$ /directory_path/runInstaller -silent "ORACLE_HOME=/home/Oracle/OraDBHome1" ...

In this command, directory_path is the path to the database directory on the DVD or the path to the Disk1 directory on the hard drive.

This method is particularly useful if you do not want to embed sensitive information, such as passwords, in the response file. For example:

$ /directory_path/runInstaller -silent "s_ownerPasswd=binks342" ...

Ensure that you enclose the variable and its setting in double quotation marks (" ").

See Also:
Oracle Universal Installer and OPatch User's Guide for Windows and UNIX for more information about response file formats

B.1.1 General Procedure for Using Response Files

The following are the general steps to install and configure Oracle products using Oracle Universal Installer in silent mode:

Note:
You must complete all required preinstallation tasks on a system before running Oracle Universal Installer in silent mode.

1. Verify that the oraInst.loc file exists in the /etc directory.

2. Prepare a response file.

3. Run Oracle Universal Installer in silent mode.

B.2 Installing Database Vault Using a Response File

Use the following steps to install Database Vault using a response file:

Note:
The oraInst.loc file should be present in the /etc directory, by default. This is because Oracle Database Vault is installed into an existing Oracle Database installation.

1. Prepare the Response File

2. Run Oracle Universal Installer Using the Response File

B.2.1 Prepare the Response File

Oracle Database Vault comes with a response file template (dv.rsp) that you can edit to customize your installation. You can use this response file for silent mode installations.

The dv.rsp file is located in the response directory on the installation media. Use the following steps to copy and modify the response file:

1. Copy the response file from the response directory to a directory on your system.

$ cp /directory_path/response/dv.rsp local_directory

In this example, directory_path is the path to the database directory on the installation media. local_directory is the path to a directory on your disk.

2. Open the response file in a text editor:

$ vi local_directory/dv.rsp

The response file contains variables that store information required by Oracle Universal Installer. You must set these variable values in the file. For example, you must specify values for the Oracle home location, Database Vault owner name, and other such information required by Oracle Universal Installer.

The response file contains two parts. You should edit the variables only in the first part. The second part of the file contains preset variables, which must not be edited. This instruction is also provided in the response file.

Some of the variables are mandatory while others are optional. The mandatory variables must be supplied for a successful installation. Each variable is explained within the response file. Examples are also provided within the response file.

The following excerpt from the response file shows instructions related to setting the Oracle home variable:

#-----------------------------------------------------------------------------
--
#Name       : ORACLE_HOME
#Datatype   : String
#Description: Complete path of the existing 10.2.0.5.0 database Oracle
#             Home into which Oracle Database Vault will be installed.
#
#Requirement: 1) Must have Oracle Database Enterprise Edition release
#                10.2.0.5.0 installed.
#             2) Must have Oracle Enterprise Manager Console DB version
#                10.2.0.5.0 installed.
#             3) Cannot contain an Oracle Automatic Storage Management(Oracle ASM) instance.
#             4) Cannot contain Oracle Database Vault.
#
#Example: ORACLE_HOME = "C:\OHOME1"
#-----------------------------------------------------------------------------
--
ORACLE_HOME=Value Required

Lines starting with a pound sign (#) are comment entries. If you want to omit an optional variable, you can comment it by adding a pound sign (#) at the beginning of the line. You cannot comment lines containing mandatory variables, like ORACLE_HOME.

Remember that you can specify sensitive information, such as passwords, at the command line rather than within the response file. "How Response Files Work" explains this method.

See Also:
Oracle Universal Installer and OPatch User's Guide for detailed information on creating response files.

3. Follow the instructions in the file to edit it. Save and close the file.

Note:
Oracle Universal Installer fails if you do not correctly configure the response file. Refer to the "Troubleshooting Silent Mode Installation" section for more information about troubleshooting a failed silent mode installation.

4. Change the permissions on the file to 700:

$ chmod 700 /local_dir/response_file.rsp

Caution:
A fully specified response file for an Oracle Database Vault installation contains the passwords for database administrative accounts. Ensure that only the Oracle software owner user can view or modify response files or consider deleting them after the installation succeeds.

B.2.2 Run Oracle Universal Installer Using the Response File

Now, you are ready to run Oracle Universal Installer at the command line, specifying the response file you created, to perform the installation. The Oracle Universal Installer executable, runInstaller, provides several options. For help information on the full set of these options, run runInstaller with the -help option. For example:

$ directory_path/runInstaller -help

To run Oracle Universal using a response file:

1. Complete the preinstallation tasks listed in Chapter 2, "Installing Oracle Database Vault".

See Also:
Frequently Asked Questions in the Oracle Database Vault Release Notes for Linux x86 for a checklist of the preinstallation requirements

2. Log in as the Oracle software owner user (typically oracle).

3. To start Oracle Universal Installer in silent mode, enter a command similar to the following:

Note:
Do not specify a relative path to the response file. If you specify a relative path, Oracle Universal Installer fails.

- $ /directory_path/runInstaller -silent -responseFile responsefilename

In this example:

- directory_path is the path to the database directory on the DVD or the path to the Disk1 directory on the hard disk.

- -silent indicates that you want to run Oracle Universal Installer in silent mode.

- responsefilename is the full path and file name of the installation response file that you configured.

Note:
For more information about other options for the runInstaller command, enter the following command:

$ /directory_path/runInstaller -help

B.3 Troubleshooting Silent Mode Installation

To determine whether a silent mode installation succeeds or fails, refer to the following log file:

/oraInventory_location/logs/silentInstalldate_time.log

The oraInventory_location can be found in the /etc/oraInst.loc file. The inventory_loc parameter in the oraInst.loc file specifies the location of the oraInventory directory.

A silent installation fails in the following conditions:

- You do not specify a response file

- You specify an incorrect or incomplete response file

- Oracle Universal Installer encounters an error, such as insufficient disk space

- The Database Vault installation prerequisites have not been met

Oracle Universal Installer or configuration assistant validates the response file at run time. If the validation fails, the silent mode installation or configuration process ends. Oracle Universal Installer treats values for parameters that are of the wrong context, format, or type as if no value was specified in the file.

C Running DVCA After Creating a Database Vault Database

You should run Database Vault Configuration Assistant (DVCA) after creating a new Oracle Database Vault database, if any of the following conditions is true:

- Database Vault is installed into an Oracle home that has multiple database. You must run DVCA on the other databases in the Oracle home. This enables Database Vault security for those databases. The databases should meet the prerequisites for installing Oracle Database Vault, as discussed in "Preinstallation and Installation Tasks" .

- Database Configuration Assistant (DBCA) is used to create a new Database Vault database in an Oracle home that has a Database Vault database. DVCA loads the Database Vault schema objects into the new database, creates the DV_OWNER and optional DV_ACCTMGR accounts, and deploys the Database Vault Administrator application for the database.

Use the following syntax to run the DVCA utility:

$ORACLE_HOME/bin/dvca -action option [-racnode host_name] -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]"}]

Where:

- action: The action to perform. option creates the Database Vault schema objects, creates the DV_OWNER account and the optional DV_ACCTMGR account, and deploys the Database Vault Administrator application.

- racnode: The host name of the Oracle Real Application Clusters (Oracle RAC) node on which the action is being performed. Do not include the domain name with the host name. Use this option if this is Oracle RAC database.

- oh: The Oracle home for the database.

- jdbc_str: The JDBC connection string used to connect to the database. For example, jdbc:oracle:oci:@orcl1, where orcl1 is the net service name in the tnsnames.ora file ($ORACLE_HOME/network/admin/tnsnames.ora).

- sys_passwd: Password for user SYS. The command prompts for the password, if you do not enter it on the command line.

- owner_account: Oracle Database Vault Owner account name

- owner_passwd: Oracle Database Vault owner account password. The command prompts for the password, if you do not enter it on the command line.

- acctmgr_account: (Optional) Oracle Database Vault Account Manager user

- acctmgr_passwd: Oracle Database Vault Account Manager password (if a user name has been specified). The command prompts for the password, if you do not enter it on the command line.

- logfile: Optionally, specify a log file name and location. You can enter an absolute path or a path that is relative to the location of the $ORACLE_HOME/bin directory

- silent: Required if you are not running DVCA in an xterm window

- nodecrypt: Reads plaintext passwords as passed on the command line. You must use this option if you are passing plaintext passwords to the command.

- lockout: Disables SYSDBA operating system authentication

- languages: Declares the language content to load, defaults to "en" (English). You can specify multiple languages. Include each language in quotation marks with commas separating different languages. Enclose the list of languages in braces. For example, -languages {"en","fr","ja"}.
The following lists the language key:

- de: German

- en: English

- es: Spanish

- fr: French

- it: Italian

- ja: Japanese

- ko: Korean

- pt_BR: Brazilian Portuguese

- zh_CN: Simplified Chinese

- zh_TW: Traditional Chinese

Note:

- If the Oracle system identifier (SID) of the database is more than 8 characters, then update the Net service name in the tnsnames.ora file before running DVCA. Refer to Oracle Database Vault Release Notes for Linux x86 for more information.

- DVCA should also be run before and after installing database options like Spatial, Java, and Intermedia. Refer to Oracle Database Vault Administrator's Guide for more details.

D Upgrading from a Previous Version of Database Vault

If you have Oracle Database Vault 10g Release 2 (10.2.0.2), Oracle Database Vault 10g Release 2 (10.2.0.3), or Oracle Database Vault 10g Release 2 (10.2.0.4) installed, then you can upgrade it to Oracle Database Vault 10g Release 2 (10.2.0.5) without uninstalling the existing instance.

D.1 Upgrading from a 10.2.0.x Version

Use the following steps to upgrade an Oracle Database Vault 10.2.0.x installation to Oracle Database Vault 10g Release 2 (10.2.0.5):

1. Re-create the password file with the nosysdba=n and force=y flags, to allow the SYS user to connect AS SYSDBA. Use the following syntax:

orapwd file=$ORACLE_HOME/dbs/orapwSID password=password force=y nosysdba=n

Here SID is the Oracle system identifier (SID) of the database and password is the password for the SYS account.

2. Shut down the database.
To stop a single-instance database, use the following commands:

$ sqlplus SYS "AS SYSDBA"
Enter password:
SQL> shutdown immediate

For an Oracle Real Application Clusters (Oracle RAC) database, use the following command:

$ ORACLE_HOME/bin/srvctl stop database -d db_name

Here db_name is the name of the database.

Note:
You must use the Server Control (srvctl) utility to start and stop Oracle RAC instances. Do not use SQL*Plus to start and stop Oracle RAC instances. You must enable SYSDBA connections before you can use the srvctl command.

3. Relink the Oracle executable to turn off the Oracle Database Vault option. Use the following commands:

$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk dv_off
$ cd $ORACLE_HOME/bin
$ relink oracle

Note:
For an Oracle Real Application Clusters (Oracle RAC) database, you must repeat the preceding commands on all nodes.

4. Start the database.
For a single-instance database, use the following commands:

$ sqlplus SYS "AS SYSDBA"
Enter password:
SQL> startup

For an Oracle Real Application Clusters (Oracle RAC) database, use the following command:

$ ORACLE_HOME/bin/srvctl start database -d db_name

5. Unlock the DVSYS account as the SYS user:

$ sqlplus SYS "AS SYSDBA"
Enter password:
SQL> ALTER USER DVSYS ACCOUNT UNLOCK;

6. Disable the Oracle Database Vault triggers. Log into SQL*Plus as SYS using the SYSDBA privilege, and then run the following ALTER TRIGGER statements:

$ sqlplus SYS "AS SYSDBA"
Enter password: password
Connected.
SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG DISABLE;
SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG DISABLE;

7. Shut down the database.
To stop a single-instance database, use the following commands:

$ sqlplus SYS "AS SYSDBA"
Enter password:
SQL> shutdown immediate

For an Oracle Real Application Clusters (Oracle RAC) database, use the following command:

$ ORACLE_HOME/bin/srvctl stop database -d db_name

Here db_name is the name of the database.

Note:
You must use the Server Control (srvctl) utility to start and stop Oracle RAC instances. Do not use SQL*Plus to start and stop Oracle RAC instances. You must enable SYSDBA connections before you can use the srvctl command.

8. Install the Oracle Database Release 10.2.0.5 Patch Set and run DBUA to upgrade the database.

See Also:
"Apply Oracle Database Release 10.2.0.5 Patch Set" for more information about installing the patch set

9. Shut down the database if it is running.
For a single-instance database, use the following commands:

$ sqlplus SYS "AS SYSDBA"
Enter password: SYS_password
SQL> SHUTDOWN

For an Oracle Real Application Clusters (Oracle RAC) database, use the following command:

$ ORACLE_HOME/bin/srvctl stop database -d db_name

Here db_name is the name of the database.

Note:
You must use the Server Control (srvctl) utility to start and stop Oracle RAC instances. Do not use SQL*Plus to start and stop Oracle RAC instances. You must enable SYSDBA connections before you can use the srvctl command.

10. Relink the Oracle executable to turn on the Oracle Database Vault option. Use the following commands:

$ cd $ORACLE_HOME/rdbms/lib
$ make -f ins_rdbms.mk dv_on
$ cd $ORACLE_HOME/bin
$ relink oracle

Note:
For an Oracle Real Application Clusters (Oracle RAC) database, you must repeat the preceding commands on all nodes.

11. Start the database.
For a single-instance database, use the following commands:

$ sqlplus SYS "AS SYSDBA"
Enter password:
SQL> startup

For an Oracle Real Application Clusters (Oracle RAC) database, use the following command:

$ ORACLE_HOME/bin/srvctl start database -d db_name

12. Create the DV_PATCH_ADMIN and DV_MONITOR roles. This is a one-time task. Use the following statements:

SQL> CONNECT DVSYS
Enter password:
SQL> CREATE ROLE DV_PATCH_ADMIN;
SQL> GRANT DV_PATCH_ADMIN TO DV_OWNER WITH ADMIN OPTION;
SQL> GRANT DV_PATCH_ADMIN TO SYS;
SQL> CREATE ROLE DV_MONITOR;

13. Connect AS SYSDBA and run the following SQL statements:

SQL> CONNECT SYS "AS SYSDBA"
Enter password:
SQL> @?/rdbms/admin/prvtstas.plb
SQL> @?/rdbms/admin/prvtstat.plb
SQL> @?/rdbms/admin/catols.sql -- Ignore any errors generated by this script
SQL> STARTUP
SQL> CONNECT SYS "AS SYSDBA"
Enter password:
SQL> DECLARE
CURSOR stmt IS
select u.name, o.name, r.pname
from user$ u, obj$ o, rls$ r
where u.user# = o.owner#
and r.obj# = o.obj#
and bitand(r.stmt_type,65536) > 0;

object_schema VARCHAR2(32) := NULL;
object_name VARCHAR2(32) := NULL;
policy_name VARCHAR2(32) := NULL;

BEGIN
OPEN stmt;
LOOP
FETCH stmt INTO object_schema, object_name, policy_name;
EXIT WHEN stmt%NOTFOUND;
dbms_rls.drop_policy('"'||object_schema||'"',
'"'||object_name||'"',
'"'||policy_name||'"');
END LOOP;
Close stmt;
END;
/
SQL> spool catmac.log -- please check catmac.log for errors
SQL> @?/rdbms/admin/catmac.sql DVSYS_user_tablespace TEMP_TABLESPACE
SYS_PASSWORD DVSYS_PASSWORD
SQL> INSERT INTO DVSYS.RULE_SET_T$ VALUES (8,
'Allow Datapump Operation',
'Rule set that controls the objects that can be exported or imported by the datapump user.',
' ', 'us');
SQL> COMMIT;
SQL> EXEC DVSYS.DBMS_MACADM.SYNC_RULES;

14. Run the following script as SYSDBA:

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

15. Enable the Oracle Database Vault triggers:

SQL> CONNECT SYS "AS SYSDBA"
Enter password:
SQL> ALTER TRIGGER DVSYS.DV_BEFORE_DDL_TRG ENABLE;
SQL> ALTER TRIGGER DVSYS.DV_AFTER_DDL_TRG ENABLE;

16. Lock the DVSYS account. Use the following SQL statements:

SQL> CONNECT SYS "AS SYSDBA"
Enter password:
SQL> ALTER USER DVSYS ACCOUNT LOCK;

17. Revoke the DV_PATCH_ADMIN role from SYS as the DV_OWNER user:

SQL> CONNECT DV_OWNER
Enter password:
SQL> REVOKE DV_PATCH_ADMIN FROM SYS;
SQL> QUIT

E Database Listener Security Recommendations

This appendix lists the security recommendations for protecting the database listener.

E.1 Security Checklist for the Database Listener

The following configuration guidelines help enhance the security for your database listener:

- The database listener configuration file, listener.ora, and the supporting OracleNet configuration file, tnsnames.ora, should have the ADMIN_RESTRICTIONS_LISTENER_SID=ON protection enabled.

- The database listener configuration file, listener.ora, and the supporting OracleNet configuration file, tnsnames.ora, should have the PLSExtProc listener disabled.

- The listener should be configured to listen on a nonstandard port, which indicates that the default port (1521) should be changed.

- The listener should be password protected or leverage operating system (OS) authentication based on the organizational security policy.

- The listener should use a unique name, which should be different from the default name.

- The listener.ora file should have the following parameter set:

INBOUND_CONNECT_TIMEOUT_ListenerName = 10

- The sqlnet.ora file should have the following parameters set:

SQLNET.INBOUND_CONNECT_TIMEOUT  = 12
SQLNET.EXPIRE_TIME = 10

- The listener should have logging enabled as follows:

LOGGING_LISTENER = ON
LOG_STATUS = ON
LOG_DIRECTORY_ListenerName = Directory_owned_by_Oracle_account
LOG_FILE_ListenerName = File_owned_by_Oracle_account

Note:
Only the owner and the DBA group should have permissions over the LOG_DIRECTORY.The owner should have read and write access to the LOG_DIRECTORY and the DBA group should have read access to it.
Only the owner and the DBA group should have read and write permissions over the LOG_FILE.

- The listener should have tracing enabled as follows:

TRACE_DIRECTORY_ListenerName = Directory_owned_by_Oracle_account
TRACE_FILE_ListenerName = File_owned_by_Oracle_account
TRACE_LEVEL = user
TRACE_FILELEN_ListenerName = 512
TRACE_FILENO_ListenerName = 1000
TRACE_TIMESTAMP_ListenerName = dd-mon-yyyy hh:mi:ss:mil

Note:
Only the owner and the DBA group should have read and write permissions over the TRACE_DIRECTORY.
Only the owner and the DBA group should have read and write permissions over the TRACE_FILE.

F Initialization Parameters

When you install Oracle Database Vault, the security specific database initialization parameters are initialized with default values. The following list shows the default values for these security specific initialization parameters:

REMOTE_LOGIN_PASSWORDFILE = default, EXCLUSIVE
AUDIT_SYS_OPERATIONS = TRUE
REMOTE_OS_AUTHENT = FALSE
REMOTE_OS_ROLES = FALSE
OS_ROLES = FALSE
OS_AUTHENT_PREFIX = ''
SQL92_SECURITY = TRUE
O7_DICTIONARY_ACCESSIBILITY = FALSE

G Enabling Oracle Database Vault Administrator Accessibility

As part of the effort to make Oracle products, services, and supporting documentation accessible and usable to the disabled community, Oracle Database Vault Administrator offers several features that make management data available to users of assistive technology. To enable these features and provide for full accessibility, you must modify two configuration settings, which are described in the following sections:

- Enabling Oracle Database Vault Administrator Accessibility Mode

- Providing Textual Descriptions of Database Vault Administrator Charts

G.1 Enabling Oracle Database Vault Administrator Accessibility Mode

Oracle Database Vault Administrator takes advantage of user interface development technologies that improve the responsiveness of some user operations. For example, when you navigate to a new record set in a table, Oracle Database Vault Administrator does not redisplay the entire HTML page. However, this performance-improving technology is generally not supported by screen readers. To disable this feature, and therefore, make the Database Vault Administrator HTML pages more accessible for disabled users, use the following procedure.

To enable the display of an entire HTML page:

1. Locate the uix-config.xml configuration file.
To locate the uix-config.xml file in an Oracle Database 10g installation, change directory to the following location in the Oracle home:

$ORACLE_HOME/dv/jlib/dva_webapp/dva_webapp/WEB-INF/

2. Open the uix-config.xml file using a text editor and locate the following entry:

<!-- An alternate configuration that disables accessibility features  -->
<default-configuration>
<accessibility-mode>inaccessible</accessibility-mode>
</default-configuration>

3. Change the value of the accessibility-mode property from inaccessible to accessible.

4. Save and close the uix-config.xml file.

5. Restart Database Vault Administrator.

See Also:
For more information on starting Oracle Database Vault Administrator, refer to Oracle Database Vault Administrator's Guide

G.2 Providing Textual Descriptions of Database Vault Administrator Charts

In the Monitor page of the Database Vault Administrator, a chart is used to display security policy data. However, charts do not convey information in a manner that can be read by a screen reader. To remedy this problem, you can configure Database Vault Administrator to provide a complete textual representation of each chart. By default, support for the textual representation of charts is disabled. When textual description for charts is enabled, Database Vault Administrator displays a textual representation of the chart data.

To enable the textual representation of charts:

1. Locate the web.xml configuration file.
To locate the web.xml file in Oracle Database 10g installation, change directory to the following location in the Oracle home:

$ORACLE_HOME/dv/jlib/dva_webapp/dva_webapp/WEB-INF/

2. Open the web.xml file with your favorite text editor and locate the following six lines of the file:

<!-- Uncomment this to enable textual chart descriptions
<context-param>
<param-name>enableChartDescription</param-name>
<param-value>true</param-value>
</context-param>
-->

3. Remove comments from this section by deleting the first line and the last line of this section so that the section consists of only these four lines:

<context-param>
<param-name>enableChartDescription</param-name>
<param-value>true</param-value>
</context-param>

4. Save and exit the web.xml file.

5. Restart Database Vault Administrator.

See Also:
For more information on starting Oracle Database Vault Administrator, refer to Oracle Database Vault Administrator's Guide

Index
A  B  C  D  E  F  H  I  K  L  M  O  P  R  S  T  U  W

Numerics

10.2.0.4 patch set, 2.1.5.2

A

accessibility features, G

Account Manager, 2.1.11.2

accounts

Database Vault Account Manager, 1.2.2

Database Vault Owner, 1.2.1

unauthenticated access to, 2.2.3.1

Administrators group, 2.1.11.2 ANONYMOUS user

unauthenticated account access with, 2.2.3.1

applying 10.2.0.4 patch set, 2.1.5.2 architecture

checking system architecture, 2.1.2

ASM. See Automatic Storage Management (ASM) assistive technology, G audit policy, 1.3 Automatic Storage Management (ASM)

SYSDBA privilege, impact on, 2.2.4

B

backups

after upgrading, 2.2.1

importance, 2.1.6

preparing a strategy, 2.1.6

Bash shell

default user startup file, 2.1.10

.bash_profile file, 2.1.10 Bourne shell

default user startup file, 2.1.10

C

C shell

default user startup file, 2.1.10

certification, hardware and software, 1.4.1 change passwords

for oracle-supplied accounts, 2.2.3

checking

database requirements, 2.1.5

hardware requirements, 2.1.2

operating system distribution and version, 2.1.3

software requirements,operating system requirements, 2.1.3

configuring

kernel parameters, 2.1.4

oracle user environment, 2.1.10

crsctl command, 2.1.8 CSD

download location for WebSphere MQ, 2.1.3

csh.login file, 2.1.4 csh.login.local file, 2.1.4 custom profiles, disable, 2.1.7

D

database (RAC)

starting, 2.2.5

database requirements, 2.1.5 Database Vault

accounts, 1.2

audit policy, 1.3

initialization parameters, 1.3

Database Vault Account Manager account, 1.2.2

password, 1.2.2

user name, 1.2.2

Database Vault Administrator (DVA) application

timeout value, 2.2.7

Database Vault Owner, 2.1.11.2 Database Vault Owner account, 1.2.1

password, 1.2.1

user name, 1.2.1

default file mode creation mask

setting, 2.1.10

disk space

checking, 2.1.2

DISPLAY environment variable

setting, 2.1.10, 2.1.10

DV_ACCTMGR role, 1.2.2 DV_OWNER role, 1.2.1 dvca command, C

E

Enterprise Manager Console DB

installing, 2.1.5.1

env command, 2.1.10 environment

checking settings, 2.1.10

configuring for oracle user, 2.1.10

environment variables

DISPLAY, 2.1.10, 2.1.10

ORACLE_BASE, 2.1.10

ORACLE_HOME, 2.1.10, 2.1.10

ORACLE_SID, 2.1.10

PATH, 2.1.10

removing from shell startup file, 2.1.10

SHELL, 2.1.10

TEMP and TMPDIR, 2.1.10

TMP and TMPDIR, 2.1.2

TNS_ADMIN, 2.1.10

errata

Linux kernel errata, 2.1.3

errors

silent mode, B.3

/etc/csh.login file, 2.1.4 /etc/csh.login.local file, 2.1.4 /etc/oraInst.loc file, B.1.1, B.3 /etc/pam.d/login file, 2.1.4 /etc/profile file, 2.1.4 /etc/profile.local file, 2.1.4 /etc/security/limits.so file, 2.1.4

F

file mode creation mask

setting, 2.1.10

file-max file, 2.1.4 files

.bash_profile, 2.1.10

default shell startup file, 2.1.4

editing shell startup file, 2.1.10

/etc/csh.login, 2.1.4

/etc/csh.login.local, 2.1.4

/etc/oraInst.loc, B.3

/etc/pam.d/login, 2.1.4

/etc/profile, 2.1.4

/etc/profile.local, 2.1.4

/etc/security/limits.so, 2.1.4

/etc/sysctl.conf, 2.1.4

limits.conf, 2.1.4

.login, 2.1.10

/proc/sys/fs/file-max, 2.1.4

/proc/sys/kernel/sem, 2.1.4

/proc/sys/kernel/shmall, 2.1.4

/proc/sys/kernel/shmmax

shmmax file, 2.1.4

/proc/sys/kernel/shmmni, 2.1.4 /proc/sys/net/core/rmem_default, 2.1.4 /proc/sys/net/core/rmem_max, 2.1.4 /proc/sys/net/core/wmem_default, 2.1.4 /proc/sys/net/core/wmem_max, 2.1.4 /proc/sys/net/ipv4/ip_local_port_range, 2.1.4 .profile, 2.1.10 profile.local, 2.1.4 response files, B.2.1

H

hardware and software certifications, 1.4.1

hardware certification, 1.4.1

hardware requirements, 2.1.2

I

initialization parameters, 1.3, F

installation

considerations, 1.4

errors

silent mode, B.3

response files, B, B.2.1

preparing, B.2.1

silent mode, B.3

templates, B.2.1

silent mode, B.2.2

error handling, B.3

installing

Enterprise Manager Console DB, 2.1.5.1

Oracle Universal Installer, using, 2.1.11

instance

instance identifier (SID), 2.1.10

ip_local_port_range file, 2.1.4

K

kernel

Linux errata, 2.1.3

kernel parameters

changing, 2.1.4

configuring, 2.1.4

Korn shell

default user startup file, 2.1.10

L

limit command, 2.1.4

limits.conf file, 2.1.4

limits.so file, 2.1.4

Linux

kernel errata, 2.1.3

listener, 2.1.5

security checklist, E.1

logging on

SYSDBA privilege connections, disabling, 2.2.4

login file, 2.1.4, 2.1.10

M

mask

setting default file mode creation mask, 2.1.10

memory requirements, 2.1.2 mode

setting default file mode creation mask, 2.1.10

monitoring

accessibility features, enabling, G.2

textual representation in charts, enabling, G.2

multiple Oracle homes, 1.4.2

O

operating system requirements, 2.1.3

Oracle Clusterware

starting, 2.1.8

Oracle Database

setting ORACLE_SID environment variable, 2.1.10

Oracle Database Vault

audit policy, 1.3

initialization parameters, 1.3, F

Oracle Database Vault Administrator

accessibility features, enabling, G

Oracle Database Vault Administrator (DVA)

deploying manually

to Database Console OC4J container, 2.2.8.2

to standalone OC4J container, 2.2.8.1

Oracle homes,multiple, 1.4.2 Oracle Real Application Clusters (RAC)

SYSDBA privilege, impact on, 2.2.4

Oracle Real Applications Clusters

configuring Database Vault on Oracle RAC nodes, 2.2.6

Oracle software owner user

configuring environment for, 2.1.10

determining default shell, 2.1.10

setting shell limits for, 2.1.4

Oracle Universal Installer, 2.1.5.1, 2.1.5.2, 2.1.11, 2.3

response files, B

oracle user

configuring environment for, 2.1.10

determining default shell, 2.1.10

setting shell limits for, 2.1.4

ORACLE_BASE environment variable

removing from shell startup file, 2.1.10

setting, 2.1.10

ORACLE_HOME environment variable

removing from shell startup file, 2.1.10

unsetting, 2.1.10

ORACLE_SID environment variable

removing from shell startup file, 2.1.10

setting, 2.1.10

oracle-supplied accounts

change passwords, 2.2.3

orapwd utility, 2.2.4 OUI, 2.1.5.2

P

packages, checking, 2.1.3

password file, 2.1.5

passwords

Database Vault Account Manager, 1.2.2

Database Vault Owner, 1.2.1

password files, 2.2.4

resetting

with SQL*Plus, 2.2.3.1

specifying for response files, B.1 unlocking

with SQL*Plus, 2.2.3.1

See alsosecurity patch set

applying, 2.1.5.2

documentation, 2.1.5.2

PATH environment variable

setting, 2.1.10

process

stopping existing, 2.1.9

processor

checking system architecture, 2.1.2

profile file, 2.1.4, 2.1.10 profile.local file, 2.1.4, 2.1.4

R

RAM requirements, 2.1.2

Red Hat

operating system requirements, 2.1.3

Red Hat Package Manager

See RPM

remote SYSDBA connections

disabling, 2.2.4

REMOTE_LOGIN_PASSWORDFILE parameter, 2.1.5 removing, Oracle Software, 2.3 requirements

database, 2.1.5

hardware, 2.1.2

listener, 2.1.5

Oracle Database 10.2.0.4 patch set, 2.1.5.2

Oracle Enterprise Manager Console DB 10.2.0.4, 2.1.5

password file, 2.1.5

software, operating system, 2.1.3

response files

about, B.1

general procedure, B.1.1

passing values at command line, B.1

passwords, B.1

security, B.1

specifying with Oracle Universal Installer, B.2.2

See also silent mode, B.1

response files installation

about, B

rmem_default file, 2.1.4 rmem_max file, 2.1.4 roles

DV_ACCTMGR, 1.2.2

DV_OWNER, 1.2.1

RPM

checking, 2.1.3

rpm command, 2.1.3

S

screen

Specify Installation Details, 2.1.11.2

security

See alsopasswords

security checklist

database listener, E.1

sem file, 2.1.4 setup.exe file, 2.1.11.2 shell

default shell startup file, 2.1.4

determining default shell for oracle user, 2.1.10

SHELL environment variable

checking value of, 2.1.10

shell limits

setting, 2.1.4

shell startup file

editing, 2.1.10

removing environment variables, 2.1.10

shmall file, 2.1.4 shmmni file, 2.1.4 SID

setting ORACLE_SID environment variable, 2.1.10

silent mode installation, B.2.2 software and hardware certifications, 1.4.1 software certification, 1.4.1 software requirements,operating system requirements, 2.1.3 specifying installation details, 2.1.11.2 srvctl command, 2.2.5 startup file

default shell startup file, 2.1.4

for shell, 2.1.10

stopping

Oracle processes, 2.1.9

SUSE

operating system requirements, 2.1.3

swap space

checking, 2.1.2

requirements, 2.1.2

sysctl command, 2.1.4 sysctl.conf file, 2.1.4 SYSDBA remote connections

disabling, 2.2.4

system architecture

checking, 2.1.2

T

TEMP environment variable

setting, 2.1.10

temporary disk space

requirements, 2.1.2

TMP environment variable, 2.1.2 TMPDIR environment variable, 2.1.2

setting, 2.1.10

TNS_ADMIN environment variable

unsetting, 2.1.10

U

ulimit command, 2.1.4

umask, 2.1.10

umask command, 2.1.10, 2.1.10

UNIX commands, 2.1.10

env, 2.1.10

limit, 2.1.4

rpm, 2.1.3

sysctl, 2.1.4

ulimit, 2.1.4

umask, 2.1.10

unset, 2.1.10

unsetenv, 2.1.10

unset command, 2.1.10 unsetenv command, 2.1.10 upgrading

after upgrading, 2.2

backup strategy, 2.1.6

post upgrade actions, 2.2

previous Database Vault version, D.1

user names

Database Vault Account Manager, 1.2.2

Database Vault Owner, 1.2.1

users

Database Vault Account Manager, 1.2.2

Database Vault Owner, 1.2.1

W

WebSphere MQ

CSD download location, 2.1.3

Windows

Administrators group, 2.1.11.2

wmem_default file, 2.1.4 wmem_max file, 2.1.4

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

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.

License Restrictions Warranty/Consequential Damages Disclaimer

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.

Warranty Disclaimer

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.

Restricted Rights Notice

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.

Hazardous Applications Notice

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.

Third-Party Content, Products, and Services Disclaimer

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.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.