This chapter describes how to configure Oracle Database and Oracle software on HP OpenVMS. It contains the following sections:
Section 3.1, "Configuring the Database for Additional Oracle Products"
Section 3.2, "Using Configuration Assistants as Standalone Tools"
If you install additional Oracle products after the initial installation, then use Oracle Database Configuration Assistant to configure the database for the new products, as follows.
Start the database, if necessary.
Before you start Oracle Database Configuration Assistant, set up the VNCSERVER and enter the following commands on HP OpenVMS:
$ SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=XXXXXX/SERVER=n $ dbca
Select Configure Database Options.
From the list of available databases, select the database that you want to configure.
Choose the products that you want to enable from the list, and then click Finish.
Configuration Assistants are usually run during an installation session, but you can also run them in standalone mode. As with Oracle Universal Installer, you can run each of the assistants noninteractively using a response file. This section contains the following topics:
When Oracle Net Server or Oracle Net Client is installed, Oracle Universal Installer automatically launches Oracle Net Configuration Assistant.
If you choose to perform a separate Oracle Database Client installation, then Oracle Net Configuration Assistant automatically creates a configuration that is consistent with the selections made during the installation. Oracle Universal Installer automatically runs Oracle Net Configuration Assistant to set up a net service name in the local naming file located in the ORA_ROOT:[network.admin] directory of the client installation.
Before you start Oracle Net Configuration Assistant, set up the VNCSERVER and then enter the following commands on HP OpenVMS:
$ SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=XXXXXX/SERVER=n $ netca
Note:
When you use Oracle Database Configuration Assistant to create a database, this assistant automatically updates the network configuration files to include information for the new database.You can use Oracle Database Configuration Assistant to:
Create a default or customized database
Configure an existing database to use Oracle products
Generate a set of DCL and SQL scripts that you can inspect, modify, and run at a later time to create a database
Before you start Oracle Database Configuration Assistant, set up the VNCSERVER and then enter the following commands on HP OpenVMS:
$ SET DISPLAY/CREATE/TRANSPORT=TCPIP/NODE=XXXXXX/SERVER=n $ dbca
For information about the command line options available with Oracle Database Configuration Assistant, use the -help or -h command line arguments, as follows:
$ dbca -help
Oracle recommends that you run the utlrp.sql script after creating or upgrading a database. This script recompiles all PL/SQL modules that may be in an invalid state, including packages, procedures, and types. Although it is optional, Oracle recommends that you perform this step when you create the database and not later.
To run the utlrp.sql script, follow these steps:
Log in as the oracle user.
Set up the Oracle environment for the Oracle home by running ORAUSER.COM with the required sid parameter.
Start SQL*Plus, as follows:
$ sqlplus / as sysdba
If necessary, start the database:
SQL> STARTUP
Run the utlrp.sql script:
SQL> @ORA_ROOT:[RDBMS.ADMIN]UTLRP.SQL
Product executables can be re-linked using the ORA_ROOT:[BIN]RELINK.COM command procedure. It is necessary to relink after an operating system upgrade and after most Oracle software patches. Some operating system patches may also require relinking of Oracle products. Firstly, shut down the database (SHUTDOWN NORMAL), any listeners, and other processes linked to this installation. Then, use the following commands to complete the relink:
$ REMORACLE $ @ORA_ROOT:[BIN]RELINK ALL $ @ORA_ROOT:[BIN]RELINK DEPLOY $ INSORACLE
The relink script manually relinks Oracle product executables, depending on the products that have been installed in the ORACLE_HOME directory.
Starting with Oracle9i Release 2 (9.2.0.2), support for shared libraries in Recovery Manager (RMAN) has been available. If you want to change the specified Media Management Library (MML), then you need not perform a relink. You can explicitly override the specified MML by using the ALLOCATE CHANNEL command as follows:
RUN
{
ALLOCATE CHANNEL c1 DEVICE TYPE sbt PARMS='SBT_LIBRARY=mymml';
}
In this example, mymml is the full path for the shared library that is provided by the third-party vendor.
RMAN on HP OpenVMS defaults to the Serial Backup Tape (SBT) disk implementation (which is statically linked), unless it is explicitly overridden with the SBT_LIBRARY parameter on the ALLOCATE CHANNEL command.
Since the shared library is called into the server, third-party vendors who are supplying their own MML must ensure that their library is compiled 64-bit. The Oracle Database 10g code was compiled by using the qualifier /NAMES=AS_IS, and the symbol vector must exactly match the entry point names as indicated in the SBT API specification. The compilation qualifiers /FLOAT=IEEE/IEEE_MODE=DENORM/GRANULARITY=BYTE should also be used.