Oracle® Database Vault Installation Guide 10g Release 2 (10.2) for Microsoft Windows (32-Bit) Part Number B32384-01 |
|
|
View PDF |
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.3) 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 E, "Initialization Parameters" and the Oracle Database Vault Administrator's Guide.
Note:
In order to upgrade a pre-10g release 2 Oracle Database to Oracle Database Vault, you first need to upgrade the database to a 10g release 2 (10.2.0.3) database.See Also:
Oracle Database Upgrade Guide, 10g Release2 (10.2) for information about upgrading your Oracle Database to Oracle Database 10g release 2.This chapter covers the following topics:
This section covers the following topics:
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.
Table 2–1 discusses the hardware requirements for Oracle Database Vault:
Table 2-1 Hardware Requirements
Requirement | Value |
---|---|
Physical memory (RAM) |
256 MB minimum; 512 MB recommended |
Virtual memory |
Double the amount of RAM |
Disk space |
270 MB of disk space for the Oracle Database Vaultsoftware 400 MB of space in the temp directory 10 MB of additional disk space for the databasefiles |
Video adapter |
256 colors |
Processor |
550 MHz minimum |
To ensure that the system meets these requirements, follow these steps:
Determine the physical RAM size. For a computer using Windows 2003, for example, double-click System in the Windows Control Panel and click the General tab. 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.
Determine the size of the configured virtual memory (also known as paging file size). For a computer using Windows 2003, for example, double-click System in the Control Panel, click the Advanced tab, and click Settings in the Performance section. Then click the Advanced tab. The virtual memory is listed in the Virtual Memory section.
If necessary, see your operating system documentation for information about how to configure additional virtual memory.
Determine the amount of free disk space on the system. For a computer using Windows 2003, for example, double-click My Computer, right-click the drive where the Oracle software is to be installed, and select Properties.
Determine the amount of disk space available in the temp
directory. This is equivalent to the total amount of free disk space, minus what will be needed for the Oracle software to be installed.
If there is less than 400 MB of disk space available in the temp
directory, then first delete all unnecessary files. If the temp disk space is still less than 400 MB, then set the TEMP
or TMP
environment variable to point to a different hard drive. For a computer using Windows 2003, for example, double-click System in the Control Panel, click the Advanced tab, and click Environment Variables.
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.
See Also:
Oracle Database Installation Guide for Microsoft Windows for detailed information on the software requirements for installing Oracle DatabaseTable 2-2 lists the software requirements for Oracle Database Vault.
Table 2-2 Software Requirements
Requirement | Value |
---|---|
Processor: Intel (x86), AMD64, and Intel EM64T The 32-bit Database Vault version, which this installation guide describes, runs on the 32-bit version of Windows on either x86 or x64 hardware. Oracle provides limited certification for 32-bit Oracle Database Vault on 64-bit Windows (x64). For additional information, visit OracleMetaLink at: http://metalink.oracle.com |
|
Oracle Database Vault for 32-bit Windows is supported on the following operating systems:
Windows NT is not supported. Windows Multilingual User Interface Pack is supported on Windows Server 2003 and Windows XP Professional. |
|
Pro*Cobol has been tested and certified with the following two compilers:
Object Oriented COBOL (OOCOBOL) specifications are not supported. The following components are supported with the Microsoft Visual C++ .NET 2002 7.0 and Microsoft Visual C++ .NET 2003 7.1 compilers:
|
|
The Oracle Net foundation layer uses Oracle protocol support to communicate with the following industry-standard network protocols:
|
|
If you plan to connect to Oracle Database Vault from a release of Oracle Database Client that is earlier than 10g release 2 (10.2), you will not be able to do so if the following conditions exist:
To remedy this problem, upgrade Oracle Database Client by using the latest Oracle Database Family patchset (9.2.0.4, or 10.1.0.4 or later). You can download the patchset from the Patches and Updates section of OracleMetaLink at: http://metalink.oracle.com |
In order to install Oracle Database Vault, you must be running the Enterprise Edition of Oracle Database 10g release 2 (10.2.0.3). The database should also have Oracle Enterprise Manager Console DB 10.2.0.3.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 fileThe following topics discuss applying the 10.2.0.3 patch set and installing the required components:
Before installing Oracle Database Vault, you should ensure that Oracle Enterprise Manager Console DB 10.2.0.3.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:
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.
Apply the Oracle Database release 10.2.0.3 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.To install Oracle Database Vault, you need to upgrade the database to Oracle Database release 10.2.0.3. Oracle strongly recommends that you back up your database before performing any upgrade or installation.
See Also:
Oracle Database Backup and Recovery User's Guide for information on database backupsThis section covers the following topics:
Patch Set Overview
The patch set is not a complete software distribution. You must install it in an existing Oracle Database 10g release 2 (10.2.0.1 or 10.2.0.2) installation. You can apply the Oracle Database release 10.2.0.3 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 Universal Installer Version Requirements
This patch set includes Oracle Universal Installer release 10.2.0.3, 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.
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 2 for Microsoft Windows (32-Bit)
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 OracleMetalink Web site:
http://metalink.oracle.com
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.
See Also:
Oracle Database Backup and Recovery User's Guide for information on database backupsOracle Clusterware should be running for the Database Vault installer to find the existing Real Application Clusters (RAC) databases. If you have stopped Oracle Clusterware, then you should restart it before running Oracle Universal Installer. Use the following command to start Oracle Clusterware:
C:/> CRS_HOME/bin/crsctl start crs
Note:
You need to run the crsctl start crs
command on all nodes of the cluster.
The crsctl start crs
command also starts the database. You will need to shut down the database before running Oracle Universal Installer.
Stop all processes running in the Oracle home. You must complete this task to enable Oracle Universal Installer to relink certain executables and libraries. For RAC databases, you need to stop the processes on all nodes.
Stop the processes in the following order:
Stop the Enterprise Manager Database Control process, if it is running. Use the following command:
C:\> ORACLE_HOME\bin\emctl stop dbconsole
Stop the iSQL*Plus process, using the following command:
C:\> ORACLE_HOME\bin\isqlplusctl stop
Shut down all database instances running from the Oracle home directory into which Oracle Database Vault is to be installed.
sqlplus SYS "AS SYSOPER" Enter password: SQL> shutdown immediate
Oracle Universal Installer configures and starts a default Oracle Net listener using TCP/IP port 1521. However, if an existing Oracle Net listener process is using the same port or key value, then Oracle Universal Installer can only configure the new listener, it cannot start it. To ensure that the new listener process starts during the installation, you must shut down any existing listeners before starting Oracle Universal Installer.
Use the following command to stop the listener process:
C:\> ORACLE_HOME\bin\lsnrctl stop listenername
Use the following steps to stop Oracle Database services from the Control Panel:
Access your Windows Services dialog.
See Also:
Your operating system documentation for instructionsSelect Oracle
HOME_NAME
TNSListener
. Click Stop to stop this service. You need to perform this step only if you haven't shut down the listener process using the lsnrctl
command.
Select OracleService
SID
and click Stop.
Note:
If you are installing Database Vault for Oracle Real Application Clusters (RAC), then you need to shut down all Oracle processes on all cluster nodes. See Appendix A, "How to Stop Processes in an Existing Oracle Real Application Clusters Database" for more details.You can use the graphical user interface (GUI) provided by Oracle Universal Installer to install Oracle Database. The following steps discuss installing Database Vault using Oracle Universal Installer:
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.
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.
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 release 2 (10.2.0.3) 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.3 installed, then it is not displayed. You must ensure that the Oracle home has an Enterprise Edition of Oracle Database release 10.2.0.3 installed.
If an Oracle home does not have Oracle Enterprise Manager Console DB 10.2.0.3.0 installed, then it is not displayed. You must ensure that the Oracle home has Oracle Enterprise Manager Console DB 10.2.0.3.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 Real Application Clusters (RAC) databases. Ensure that Oracle Clusterware is running before installing Oracle Database Vault. You can use the crsctl
command to start Oracle Clusterware.
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.
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.
Reenter the password in the Confirm Password field.
Select Create a Separate Account Manager if you want to create a separate Account Manager to manage Oracle Database Vault accounts.
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.
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.
Reenter the password in the Confirm Password field. Click Next.
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:
If the selected Oracle home contains more than one database, then Operating System (OS) authentication is turned off for all the databases in the Oracle home.
Oracle recommends that you install Oracle Database Vault into an Oracle home containing only a single database.
If a database is not listed, then check to make sure that you have followed the instructions under "Check the Database Requirements".
Enter the existing SYS
user password for the selected database in the Existing Database SYS Password field.
Reenter the SYS password in the Confirm Password field. Click Next.
Note:
At this point, the database requirements are validated.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 processesProduct-specific prerequisite checks are performed. Confirm that all tests have passed. Click Next to continue.
The Summary screen is displayed with the installation details. Verify the details and click Install.
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.
This section lists the tasks to perform after you have completed an upgrade of your database. The following topics are discussed:
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.
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.
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.To unlock and reset user account passwords using SQL*Plus:
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 will need to log in using the Database Vault Owner account.
Enter a command similar to the following, where account
is the user account that you want 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
In a default Database Vault installation, the operating system authentication to the database is disabled. In addition, connections to the database using the SYSDBA
privilege (that is, those that use the AS SYSDBA
clause) are disabled. This is a security feature and is implemented to prevent misuse of the SYSDBA
privilege.
If a password file has been created using the orapwd
utility with the nosysdba
flag set to y
(Yes) (the default action of a Database Vault installation), users will not be able to log in to an Oracle Database Vault instance using the SYS
account or any account with SYSDBA
privilege using the AS SYSDBA
clause. 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.
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.
Use the following syntax to run orapwd
:
C:\> ORACLE_HOME\bin\orapwd file=filename password=password [entries=users] force=y/n nosysdba=y/n
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 (optional). Enter y
(for yes) or n
(for no)
nosysdba
: Whether to enable or disable the SYS
logon (optional for Oracle Database Vault only). Enter y
(for yes) or n
(for no)
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:
C:\> oracle\product\10.2.0\db_1\bin\orapwd file=C:\oracle\product\10.2.0\db_1\dbs\orapwORCL password=5hjk99 force=y nosysdba=n
Note:
Do not insert spaces around the equal (=) character.You need to start the listener and database on all RAC nodes other than the one on which the installation is performed. Use the following commands to start the listener and the database:
Note:
You need to enableSYSDBA
connections on all nodes before running these commands. See "Enable or Disable Connections with the SYSDBA Privilege" for more information on enabling SYSDBA
connections.C:\> ORACLE_HOME\bin\lsnrctl start LISTENER_nodename C:\> ORACLE_HOME\bin\srvctl start instance -d sid -i instance_name -c "SYS/password AS SYSDBA"
After installing Database Vault for a Real Application Clusters (RAC) instance, you need to run Database Vault Configuration Assistant (DVCA) with the -action optionrac
switch on all other RAC nodes. This sets instance parameters and disables SYSDBA
operating system authentication.
Note:
Before running DVCA on a remote node, you need to set the correct value for the ORACLE_SID
variable in the ORACLE_HOME
\bin\dvca.bat
file on the remote node. The ORACLE_SID
variable needs to be changed from the local node Oracle System Identifier (SID) to the remote node Oracle System Identifier (SID) on the remote node.
Before running DVCA on a remote node, you need to correct the following Windows registry entry on the remote node:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_ORACLE_HOME_NAME\ORA_instance_name_PWFILE
The instance_name
in the remote node registry should be the database instance name for the remote node, and not the database instance name for the local node.
The value for this key should be the complete path to the password file on the remote node. For example:
C:\ORACLE\PRODUCT\10.2.0\DB_1\dbs\orapwORCL2
You need to run this command on all RAC nodes other than the node on which the Database Vault installation is performed. This step is required to enable the enhanced security features provided by Oracle Database Vault.
Note:
The listener and database instance should be running on the nodes on which you run DVCA.Use the following syntax to run DVCA:
C:\> ORACLE_HOME\bin\dvca -action optionrac -racnode host_name -oh oracle_home -jdbc_str jdbc_connection_string -sys_passwd sys_password [-logfile ./dvca.log] [-silent] [-nodecrypt] [-lockout]
Where:
action
: The action to perform. optionrac
performs the action of updating the instance parameters for the RAC instance and optionally disabling SYSDBA
operating system access for the instance.
racnode
: The host name of the RAC node on which the action is being performed. Do not include the domain name with the host name.
oh
: The Oracle home for the RAC instance.
jdbc_str
: The JDBC connection string used to connect to the database. For example, "jdbc:oracle:oci:@orcl1"
.
sys_password
: The password for the SYS
user.
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.
lockout
: Used to disable SYSDBA
operating system authentication.
Note:
You can reenableSYSDBA
access by re-creating the password file with the nosysdba
flag set to n
(No). The orapwd
utility enables you to do this.Restart Enterprise Manager Database Control by using the following commands:
C:\> ORACLE_HOME\bin\emctl stop dbconsole C:\> ORACLE_HOME\bin\emctl start dbconsole
Note:
Run the above commands on all cluster nodes for a RAC database.Use Oracle Universal Installer (OUI) to remove Oracle software from an Oracle home. The following list summarizes the steps involved:
Log on as a member of the Administrators group.
Shut down all processes running in the Oracle home.
Start Oracle Universal Installer from the Start menu, select Programs, then ORACLE_ HOME_NAME, then Oracle Installation Products, then Oracle Universal Installer. The Welcome screen for Oracle Universal Installer appears.
In the Welcome screen, select Deinstall Products. The Inventory screen appears. This screen lists all the Oracle homes on the system.
Select the Oracle home and the products that you wish to remove. Click Remove.
See Also:
Refer to the Oracle Database Installation Guide for details on removing Oracle softwareNote:
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.