2 Installing 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 want to 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.

gcc-3.4.4-2
gcc-c++-3.4.4-2
libgcc-3.4.4-2
libstdc++-devel-3.4.4-2
compat-libgcc-295-2.95.3-81
compat-libstdc++-33-3.2.3-47.3
glibc-2.3.4-2.13
libaio-0.3.103-3
libaio-devel-0.3.103-3
libstdc++-devel 3.4.4-2

gcc-3.3.3-43.34
gcc-c++-3.3.3-43.34
glibc-2.3.3-98.47
glibc-2.3.3-98.28 (64-bit)
libgcc-3.3.3-43.34
libgcc (64 bit) unknown
libstdc++-3.3.3-43.34
libstdc++-devel-3.3.3-43.34
libaio-0.3.102-1.2
libaio-0.3.98-18.3 (64-bit)
libaio-devel-0.3.102-1.2
libaio-devel-0.3.98-18.3 (64-bit)
Gmake-3.80-184.1

binutils-2.16.91.0.5
compat-libstdc++-5.0.7
gcc-4.1.0
glibc-2.4-31.2
glibc-devel-2.4-31.2
ksh-93r-12.9
libaio-0.3.104
libaio-devel-0.3.104
libelf-0.8.5
libgcc-4.1.0
libstdc++-4.1.0
libstdc++-devel-4.1.0
make-3.80
sysstat-6.0.2
unixODBC-2.2.11
unixODBC-devel-2.2.11

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-22.EL
   

   In this example, the output shows the kernel version (2.6.9) and errata level (22.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-306.ibm.com/software/integration/wmq/support
   

2.1.4 Check 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.

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:

   Make a note of the current 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 want to 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 = 65536
   net.ipv4.ip_local_port_range = 1024 65000
   net.core.rmem_default = 1048576
   net.core.rmem_max = 1048576
   net.core.wmem_default = 262144
   net.core.wmem_max = 262144
   

   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:

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 already exist:

   session    required     /lib/security/pam_limits.so
   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.

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

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 should be used 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.

2.1.7 Disable Custom Profiles

If you have created custom profiles and password complexity checks in your existing database, then you need to 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

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 need to 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

$ORACLE_HOME/bin/emctl stop dbconsole

$ORACLE_HOME/bin/isqlplusctl stop

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.

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 already 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 want to use to display Oracle Universal Installer (your workstation or PC).

12. If you determined that the /tmp directory has less than 400 MB of free disk space, then identify a file system with at least 400 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 that you want 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

Run Oracle Universal Installer (OUI) to install Oracle Database Vault into an existing Oracle Database 10gRelease 2 (10.2.0.5) database. You should run the installer as the software owner account that owns the current ORACLE_HOME environment. This is normally the oracle account.

Log in as the oracle user. Alternatively, switch user to oracle using the su command. Change your current directory to the directory containing the installation files. Start Oracle Universal Installer.

./runInstaller

The following steps discuss the options you need to select:

1. 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 release 10.2.0.5 installed, then it is not displayed. You must ensure that the Oracle home has an Enterprise Edition of Oracle Database release 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.

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

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

4. Reenter the password in the Confirm Password field.

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

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

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

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

9. 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".

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

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

    Note:

    At this point, the database requirements are validated.

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

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

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

15. 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.1 Back Up the Database

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

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

Make sure 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 need to 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. This enables you to effectively implement the strong security provided by Oracle Database Vault.

2.2.4 Disable Remote SYSDBA Connections (Optional)

Oracle Database Vault allows you to disable remote logins with SYSDBA privileges. This enables 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 will fail.

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 will be created enabling SYSDBA access for Oracle Database Vault instances.

For example:

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

When you re-create the password file, any accounts other than SYS that were granted the SYSDBA or SYSOPER privileges will have those privileges removed. You will need to 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 need to 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 need to 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:

srvctl start instance -d sid -i instance_name

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.

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

http://hostname:8888/dva

https://hostname:port/dva

https://myserver:1158/dva

2.3.1 Step 1: Deconfigure Oracle Database Vault

1. Disable Oracle Database Vault, as described under "Step 1: Disable Oracle Database Vault" in Oracle Database Vault Administrator's Guide.

2. In SQL*Plus, connect as user SYS with the SYSDBA privilege.

   CONNECT SYS/AS SYSDBA
   Enter password: password
   

3. Disable the recycle bin.

   To check if the recycle bin is enabled, enter the following command:

   SHOW PARAMETER RECYCLEBIN
   

   If it is enabled, then run the following SQL statement:

   ALTER SYSTEM SET RECYCLEBIN = OFF SCOPE=SPFILE;
   

   Disabling the recycle bin does not purge or otherwise affect objects that are already in the recycle bin.

4. Run the following SQL script:

   @$ORACLE_HOME/rdbms/admin/dvremov.sql
   

5. Manually drop the DV_OWNER and DV_ACCTMGR user accounts.

   For example:

   DROP USER dbv_owner CASCADE;
   DROP USER dbv_acctmgr CASCADE;
   

6. Restart the database.

   For example:

   SHUTDOWN IMMEDIATE
   STARTUP
   

2.3.2 Step 2: Deinstall Oracle Database Vault

1. Start OUI by invoking runInstaller from the $ORACLE_HOME/oui/bin directory.

2. In the Welcome window, select Deinstall Products.

3. Navigate to the correct directory and then select Database Vault 10.2.0.5 from the list.

4. In the confirmation window, select Yes.

5. Exit OUI.

Afterward, you can double-check that Oracle Database Vault is truly deinstalled by logging in to SQL*Plus and entering the following statement:

SELECT * FROM V$OPTION WHERE PARAMETER = 'Oracle Database Vault';

If Oracle Database Vault is deinstalled, the following output appears:

PARAMETER                     VALUE
----------------------------- -----------------------
Oracle Database Vault         FALSE