Oracle Rdb Installation and Configuration Guide
Release 7.1 for OpenVMS Alpha

Part Number A90407-01
Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

2
Installing Oracle Rdb

This chapter describes how to install Oracle Rdb. Table 2-1 summarizes the preparatory tasks described in Chapter 1.

Section 2.1 describes how to obtain copies of the release notes. Section 2.2 contains a step-by-step description of the installation procedure. Section 2.6 presents common installation errors and their solutions.

Table 2-1  Preinstallation Checklist
Task  For More Information ...  

Confirm required operating system components. 

See Section 1.2

Confirm required software and disk space requirements. 

See Section 1.3 and Section 1.5

Back up existing databases. 

See Section 1.8.1

Resolve repository considerations. 

See Section 1.8.4

Confirm adequate account privileges. 

See Section 1.8.5

Confirm account password is unlocked. 

See Section 1.8.6

Confirm adequate account quotas. 

See Section 1.8.7

Confirm system parameter values. 

See Section 1.8.8

Back up your system disk. 

See Section 1.8.9

Disable access to online help. 

See Section 1.8.10

Prevent access to the system. 

See Section 1.8.11

2.1 Accessing the Online Release Notes

The Oracle Rdb installation procedure copies the latest release notes to the SYS$HELP directory. You can specify OPTIONS N when you invoke the VMSINSTAL command procedure to see the release notes before continuing the installation (see Section 2.2.1 and Section 2.2.2). The installation provides text, PostScript, and PDF formats of the release notes:

Printed release notes are not included with the documentation set for Oracle Rdb.

Review the release notes in case they contain any information about changes in the installation procedure.

2.2 Installation Procedure

The Oracle Rdb installation process consists of a series of questions and informational messages.

2.2.1 Invoking VMSINSTAL

To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. The VMSINSTAL command procedure is in the SYS$UPDATE directory. You can use the following syntax to invoke VMSINSTAL:

@SYS$UPDATE:VMSINSTAL variant-name device-name OPTIONS N

Alternatively, you can just type @SYS$UPDATE:VMSINSTAL at the system prompt. VMSINSTAL will prompt you for the variant name, device name, and options parameters. The rest of this section describes these parameters.

variant-name

The variant of Oracle Rdb you want to install. For example, enter the following:

RDBAMV071
device-name

The name of the device on which the media is mounted.

OPTIONS N

An optional parameter that indicates you want to review the release notes. If you include the OPTIONS N parameter, VMSINSTAL displays a menu that lets you choose between printing the release notes or displaying them on your terminal. Review the release notes before proceeding, in case they contain new information about the installation. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. The release notes are automatically copied to SYS$HELP regardless of whether or not you use the OPTIONS N parameter.

You can select several other options when you invoke VMSINSTAL. See the OpenVMS documentation on software installation for information on these options.

The following example displays the command to invoke VMSINSTAL to install Oracle Rdb from the CD-ROM device DUB4: and shows the system response. This example uses the OPTIONS N release note parameter.

$ @SYS$UPDATE:VMSINSTAL RDBAMV071 DUB4:[RDBAMV071] OPTIONS N


        OpenVMS AXP Software Product Installation Procedure V7.2-1


It is 9-APR-2001 at 15:54.

Enter a question mark (?) at any time for help.

2.2.2 Steps of the Installation Procedure

This section discusses the installation process itself, presenting all questions that appear during the installation. This section presumes that you entered the product name, device name, and options parameters on the VMSINSTAL command line. Refer to Appendix B for a sample installation procedure of Oracle Rdb.

Each question in the installation is marked with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example, [YES]. To use the default response, press the Return key.

  1. Backing up your system disk

    The VMSINSTAL procedure asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press the Return key. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can start the installation again.

    * Are you satisfied with the backup of your system disk [YES]?
    
    
  2. Mounting the media

    Mount the distribution volume on the device you specified. VMSINSTAL confirms the variant you are installing.

    The following products will be processed:
    
      RDBAMV V7.1
    
    
            Beginning installation of RDBAMV V7.1 at 15:54
    
    %VMSINSTAL-I-RESTORE, Restoring product save set A ...
    
    
  3. Reviewing the release notes

    The installation procedure automatically copies the release notes to the following:

  4. Printing the installation guide

    The installation procedure now asks if you want to print the text format of this installation guide, which it copies to SYS$HELP:RDB071.INSTALL_GUIDE.

        The Rdb installation guide will be provided in SYS$HELP.
    
    * Would you like to print the installation guide [NO]?
    
    
  5. Choosing an option

    The following message is displayed:

        *************************************************************
    
        Please select the Oracle Rdb products you are licensed to install.
        Separate multiple choices with commas (Ex: 1,2,4).
    
        *************************************************************
    
    
        (1)  Oracle Rdb
        (2)  Programmer for Rdb (Rdb Compilers)
        (3)  Hot Standby
        (4)  Power Utilities
        (5)  Common Components
    
    
    * Enter the Oracle Rdb products you are licensed to install [ALL]:
    
        You have selected the following Oracle Rdb products:
    
            (1)  Oracle Rdb
            (2)  Programmer for Rdb (Rdb Compilers)
            (3)  Hot Standby
            (4)  Power Utilities
            (5)  Common Components
    
    * Do you want to proceed with the installation [NO]? YES
    
    

    Choose only the options you are licensed to install.

  6. If you have Oracle CDD/Repository or DECdesign installed on your system, you will see the following note.

    
                   IMPORTANT **** PLEASE NOTE ******
    
        The RDB$CONVERT_CDD$DATABASE.COM procedure
        will be provided in SYS$LIBRARY.  This command procedure
        should be used to upgrade each CDD/Repository database and
        DECdesign library on your system.
    
        Please see the Oracle Rdb V7.1 release notes for more details.
    
    
  7. Confirming the installation

    VMSINSTAL confirms the installation and asks if you want to continue.

    
            Installation procedure for: "Oracle Rdb V7.1-0"
    
        You are about to install a multiversion Oracle Rdb kit.
    
        Be sure you have read the section entitled
            "Preparing Your System and the Installing Account"
        in the installation guide before continuing with the installation.
    
    * Do you want to proceed [NO]? Y
    
    
        Checking system requirements ...
    
    
  8. Creating the RDBSERVER object and RDB$REMOTE71 accounts needed for remote database access

        *************************************************************
    
        RDBSERVER object found but RDB$REMOTE71 account is not found.
        To be sure the password for the RDB$REMOTE71 account matches
        the password for the RDBSERVER object, this installation will:
    
               1. First delete the RDBSERVER object from the network
                  database
               2. Create a new RDB$REMOTE71 account and insert a new
                  RDBSERVER object into the network database
    
        **************************************************************
    
    * Please enter carriage return to continue:
    
    
  9. Entering a UIC for the RDB$REMOTE71 account

    If this is the initial installation of Oracle Rdb, the procedure creates an account called RDB$REMOTE71. You must choose a unique user identification code (UIC) for this account, which the installation procedure uses when it creates the RDB$REMOTE71 account. The installation procedure prompts you to enter a UIC.

        *************************************************************
    
        This installation requires the creation of the RDB$REMOTE71
        account.  The installation procedure will not proceed until you
        enter a valid user identification code (UIC) for the RDB$REMOTE71
        account.  The UIC must be unique.  Format [ggg,mmm].
    
        **************************************************************
    
    * Enter UIC to be used for RDB$REMOTE71 account: [300,475]
    
    
  10. Creating the RDMAIJ71 account

    The installation procedure requires the creation of the RDMAIJ71 account. You must choose a unique user identification code (UIC) for this account, which the installation procedure uses when it creates the RDMAIJ71 account. The installation procedure prompts you to enter a UIC.

        *************************************************************
    
        This installation requires the creation of the RDMAIJ71
        account.  The installation procedure will not proceed until you
        enter a valid user identification code (UIC) for the RDMAIJ71
        account.  The UIC must be unique.  Format [ggg,mmm].
    
        **************************************************************
    
    * Enter UIC to be used for RDMAIJ71 account: [250,46]
    
    
  11. Creating the RDMSTT71 account

    The installation procedure requires the creation of the RDMSTT71 account. You must choose a unique user identification code (UIC) for this account, which the installation procedure uses when it creates the RDMSTT71 account. The installation procedure prompts you to enter a UIC.

        *************************************************************
    
        This installation requires the creation of the RDMSTT71
        account.  The installation procedure will not proceed until you
        enter a valid user identification code (UIC) for the RDMSTT71
        account.  The UIC must be unique.  Format [ggg,mmm].
    
        **************************************************************
    
    * Enter UIC to be used for RDMSTT71 account: [250,775]
    
    
  12. Choosing to run the Installation Verification Procedure (IVP)

    The Installation Verification Procedure (IVP) checks that Oracle Rdb is correctly installed. It creates a sample database and processes and runs sample programs against it. The installation asks if you want to run the IVP. Oracle Corporation recommends that you run the IVP.

    * Do you want to run the IVP after the installation [YES]? YES
    
    

    As part of the IVP, Oracle Rdb creates the PERSONNEL sample database in the directory specified by the RDM$DEMO logical name.

    You can also run the IVP independently at any time after Oracle Rdb is installed. See Section 3.12.

  13. Choosing to purge files

    You have the option to purge files from previous versions of Oracle Rdb that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question.

    * Do you want to purge files replaced by this installation [YES]?
    
    
  14. Displaying informational messages

    At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you asked for files to be purged, that work is done now. The following messages are displayed:

        There are no more questions.  The installation takes approximately
            15 minutes
    
    
        Beginning installation ...
    
    
        Installing under VMS V7.2-1   -  9-APR-2001 15:58
    
    
    %VMSINSTAL-I-RESTORE, Restoring product save set B ...
    %VMSINSTAL-I-RESTORE, Restoring product save set C ...
    %VMSINSTAL-I-RESTORE, Restoring product save set D ...
    %VMSINSTAL-I-RESTORE, Restoring product save set E ...
       .
       .
       .
    %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target 
    directories...
    
    
  15. Running the IVP

    If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display:

        **************************************
    
        Oracle Rdb V7.1-0
    
        IVP COMPLETED SUCCESSFULLY
    
        **************************************
    
    
    IVP completed for: Oracle Rdb V7.1-0
    
    
  16. Completing the installation

    The following messages indicate that the entire installation procedure is complete:

            Installation of RDBAMV V7.1 completed at 16:15
    
        Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY
    
        Creating installation data file: VMI$ROOT:[SYSUPD]RDBAMV071.VMI_DATA
    
    
            VMSINSTAL procedure done at 16:15
    

2.3 Overview of Multiple-Version Support in Oracle Rdb

Oracle Rdb allows you to install and run multiple versions of Oracle Rdb software on a single OpenVMS system.

This capability facilitates the process of upgrading to new versions of the software. You can now install the newest version of Oracle Rdb, use the RMU Convert command with the Nocommit qualifier to convert a database from an earlier version, and test your applications using this converted database. If you need to return to the previous version, use the RMU Convert command with the Rollback qualifier. Each database can be converted independently, but each database can be accessed by only one version of Oracle Rdb.

Multiple-version (multiversion) support is implemented by appending the Oracle Rdb software release number to Oracle Rdb file and image names. For example, the version of RDMSHR.EXE specific to Oracle Rdb release 7.1 is named RDMSHR71.EXE; the image for interactive SQL is named SQL$71.EXE.

Because the multiversion files have the variant in the image name, installing the multiversion kit does not replace standard version files. Three files, RDBINTSHR.EXE, RDBSHR.EXE, and SQL$INT.EXE, are not varianted in either the standard version or the multiversion variant of Oracle Rdb. These files are guaranteed to be compatible with all versions of Oracle Rdb and are replaced only when a higher version of Oracle Rdb is installed on your system.

2.3.1 General Multiversion Support Considerations

Consider the following factors when deciding whether or not to install multiple versions of Oracle Rdb:

2.3.2 Layered Product Considerations

You must also consider layered product and third-party software requirements.

Products that use Oracle Rdb as their underlying database management system check to see if Oracle Rdb is installed, usually by analyzing the image header. If the product looks for RDMSHRP, and instead finds RDMSHRP71, the layered product will not install correctly.

2.3.3 Oracle CDD/Repository Considerations

Oracle CDD/Repository release 7.0.1 does not install the Oracle Rdb installation kit, but does check to see that the RDMSHR logical name is defined. If it is not defined, RDMSHR is defined to be RDMSHR.EXE.

To install Oracle CDD/Repository release 7.0.1 in a multiversion environment, take some or all of the following steps, depending on the combination of Oracle Rdb versions:

If you install Oracle CDD/Repository on a multiversion Oracle Rdb system and do not perform the installation from the SYSTEM account, you must use the RDB$SETVER command procedure to reset Oracle Rdb logical names. For example, if you have Oracle Rdb release 7.1 set up as your environment and you install Oracle CDD/Repository from your process account, VMSINSTAL removes all process logical names. To redefine the Oracle Rdb release 7.1 logical names, execute the following command:

$ @SYS$LIBRARY:RDB$SETVER 7.1

Section 2.4 provides instructions for installing and using multiple versions of Oracle Rdb.

2.4 Accessing Multiple Versions of Oracle Rdb

This section describes how to:

2.4.1 Changing the Default Oracle Rdb Environment

After Oracle Rdb release 7.1 is installed, you must run the RDB$SETVER.COM command procedure located in the SYS$LIBRARY directory. This procedure sets up logical names and symbols that establish a new Oracle Rdb environment.

If Oracle Rdb release 7.1 is the only version of Rdb installed on the system, it is sufficient to execute the following command in the system startup procedure:

@SYS$LIBRARY:RDB$SETVER 7.1 /SYSTEM

Individual users are not required to execute the RDB$SETVER command in their login procedures nor in the systemwide login procedure.

The RDB$SETVER command procedure accepts a parameter and a qualifier. The parameter specifies which version of Oracle Rdb you want to run (or reset, see Section 2.4.2). The qualifier specifies at which level the procedure defines logical names. For example:

$ @SYS$LIBRARY:RDB$SETVER 7.1 /SYSTEM

If you do not specify the parameter, the procedure prompts you for a version number:

$ @SYS$LIBRARY:RDB$SETVER
Enter MULTIVERSION version number (n.n) or S (for STANDARD) : release 7.1
Current PROCESS Oracle Rdb environment is version V7.1-0 (MULTIVERSION)
Current PROCESS SQL environment is version V7.1-0 (MULTIVERSION)
Current PROCESS Rdb/Dispatch environment is version V7.1-0 (MULTIVERSION)

The previous example sets the multiversion variant of Oracle Rdb release 7.1 as the environment for the process that executed the RDB$SETVER command procedure. If you specify a version number for which no multiversion variant is available, the system verifies whether a standard version is available. If the standard version is available, the version is set to standard. If neither multiversion variant nor standard version is available, the system displays the following message:

$ @SYS$LIBRARY:RDB$SETVER 6.0
%Oracle Rdb, Version 6.0 does not exist on your system.

The RDB$SETVER command procedure can operate on the process, job, group, or system level. The default is /PROCESS. You can use RDB$SETVER.COM to establish the multiversion variant of Oracle Rdb as your default system environment by adding the @SYS$SYSTEM:RDB$SETVER.COM 7.1 command to SYSTARTUP_VMS.COM and specifying the /GROUP or /SYSTEM qualifier. You must have privileges to define group or system logical names to run RDB$SETVER.COM with the /GROUP or /SYSTEM qualifier.

The following list shows the logical names defined by the RDB$SETVER command procedure:

2.4.2 Setting Symbols with RDB$SETVER RESET

The RESET parameter of the RDB$SETVER command procedure sets symbols to invoke RMU and other Oracle Rdb images that correspond to the version number last set.

This is important for RMU users who run the RDB$SETVER command procedure with the /GROUP or /SYSTEM qualifiers. In that case, other users' process-level symbols for RMU may not invoke the image corresponding to the version set by RDB$SETVER.COM. The procedure displays this informational message as a reminder:

$ @SYS$LIBRARY:RDB$SETVER 7.1 /SYSTEM
%You have changed the default Oracle Rdb Version at a level other
%than /PROCESS. The RMU symbol may have to be set by users
%using Oracle Rdb at this level. This can be done with the
%following DCL command: @SYS$LIBRARY:RDB$SETVER RESET
Current SYSTEM Oracle Rdb environment is version V7.1-0 (MULTIVERSION)

A user can determine if this incompatibility exists by examining the equivalence string for the logical name RDMS$VERSION_VARIANT and then executing the RMU Show Version command. The following example shows incompatibility between versions of Oracle Rdb and RMU:

$ SHOW LOGICAL RDMS$VERSION_VARIANT
   "RDMS$VERSION_VARIANT" = "71" (LNM$SYSTEM_TABLE)
$ RMU/SHOW VERSION
Executing RMU for Oracle Rdb V6.0A

In the preceding example, a user can either change the version of RMU to release 7.1, or change the version of Oracle Rdb to release 6.0A. Either way, a user must run the RDB$SETVER command procedure at the process level:

In addition to setting up the appropriate symbol for RMU, RDB$SETVER RESET also creates symbols to invoke other Oracle Rdb interfaces:

$ SQL$ == "$SQL$"
$ SQL$PRE == "$SQL$PRE"
$ SQL$MOD == "$SQL$MOD"
$ RDML == "$RDML"
$ RDO == "$RDO"
$ RDBPRE == "$RDBPRE"

Note that image-invocation symbol definitions should not specify directories. For instance, users should not use either of the following symbol formats:

SQL == "RUN SYS$SYSTEM:SQL$"
SQL == "$SYS$SYSTEM:SQL$"

Both of these formats force the use of a specific image, and do not allow the use of variants.

2.4.3 Matching Environment and Database Versions

The RDB$SETVER command procedure sets logical names and symbols for most Oracle Rdb images to point to varianted file names. Thus, the symbol SQL$ points to SQL$71.EXE, and SQL$PRE points to SQL$PRE71.EXE, if you have set the version to release 7.1.

The following example shows how to determine your Oracle Rdb environment:

$ RMU/SHOW VERSION
Executing RMU for Oracle Rdb V7.1-00
$ RUN SQL$
SQL> ATTACH 'FILENAME PERSONNEL';
SQL> SHOW VERSIONS
Current version of SQL is: SQL V7.1-0
Underlying versions are:
    Database with filename PERSONNEL
        Oracle Rdb V7.1-0
        Rdb/Dispatch V7.1-0
SQL> DISCONNECT ALL;
SQL> EXIT;

To identify the version of Oracle Rdb associated with a database, use the RMU Show Version command, as follows:

$ RMU /SHOW VERSION MF_PERSONNEL
Executing RMU for Oracle Rdb V7.1
Database DUA0:[MFP]MF_PERSONNEL.RDB;1 requires version 7.0

The following example shows the error messages displayed if you try to attach to a database with the incorrect version of Oracle Rdb:

SQL> ATTACH 'FILENAME PERSONNEL';  ! This is a 6.0 database
%SQL-F-ERRATTDEC, Error attaching to database personnel
-RDB-F-WRONG_ODS, the on-disk structure of database filename is not supported
by version of facility being used
-RDMS-F-ROOTMAJVER, database format 60.0 is not compatible with software
version 71.0
SQL> SHOW VERSION
Current version of SQL is: Oracle Rdb SQL V7.1-0

2.4.4 Identifying Environment Versions with RDB$SHOVER

Layered and third-party products can determine which version or versions of Oracle Rdb are installed on their systems by using the RDB$SHOVER command procedure. Previously, these products usually read the version number from the header of one of the standard Oracle Rdb images, such as RDMSHRP. If you install the multiversion variant of Oracle Rdb release 7.1, the old image names may not be available to determine the version number.

The RDB$SHOVER.COM procedure (located in SYS$LIBRARY) allows four optional parameters. If you set P1 to VERSIONS, the process logical name RDBVMS$INSTALLED_VERSIONS is defined as a list of the Oracle Rdb versions. Each installed version has the following format:

[*]AM.N[U]-cc

The following example shows how to run the RDB$SHOVER command procedure interactively:

$ @SYS$LIBRARY:RDB$SHOVER.COM VERSIONS
   "RDBVMS$INSTALLED_VERSIONS" = "V6.0-0" (LNM$PROCESS_TABLE)
        = "*V7.1-0"

In this example, V6.0-0 indicates that Oracle Rdb release 6.0 is installed; *V7.1-0 indicates that the multiversion variant of Oracle Rdb release 7.1 is installed.

The following example shows a command procedure you can use to determine which versions of Oracle Rdb are available:

$ x=0
$ start:
$ y=f$trnlnm("RDBVMS$INSTALLED_VERSIONS",,x)
$ if y .eqs. "" then goto finish
$ show symbol y
$ x=x+1
$ goto start
$ finish:

If you set P1 to VERSIONS and P2 to a specific version, for example, release 7.1, the logical names show only the information of the version indicated.

$ @SYS$LIBRARY:RDB$SHOVER.COM VERSIONS 7.1
   "RDBVMS$INSTALLED_VERSIONS" = "V7.1-0" (LNM$PROCESS_TABLE)

If you set P1 to VERSIONS and P2 to ALL, process logical names listing SQL and Rdb/Dispatch versions are also displayed.

$ @SYS$LIBRARY:RDB$SHOVER.COM VERSIONS ALL
   "RDBVMS$INSTALLED_VERSIONS" = "V6.0-0" (LNM$PROCESS_TABLE)
        = "*V7.1-0"
   "SQL$INSTALLED_VERSIONS" = "V6.0-0" (LNM$PROCESS_TABLE)
        = "*V7.1-0"
   "RDB$DISPATCH_INSTALLED_VERSIONS" = "V6.0-0" (LNM$PROCESS_TABLE)
        = "*V7.1-0"

To suppress the display of the logical names, set the last parameter to NOSHOW.

$ @SYS$LIBRARY:RDB$SHOVER.COM VERSIONS NOSHOW
$ @SYS$LIBRARY:RDB$SHOVER.COM VERSIONS ALL NOSHOW
$ @SYS$LIBRARY:RDB$SHOVER.COM VERSIONS 7.1 ALL NOSHOW

2.4.5 Linking Programs

The RDB$SETVER command procedure defines the logical name SQL$USER. The translation of SQL$USER depends on which version of Oracle Rdb you have selected with RDB$SETVER.COM. For example, if you have specified release 6.0, SQL$USER translates to the SQL user library SQL$USER60.OLB; if you have specified release 7.1, SQL$USER translates to SQL$USER71.OLB.

The RDB$SETVER command procedure does not define the logical name LNK$LIBRARY, which enables users to link embedded SQL programs without explicitly specifying an SQL library. By defining LNK$LIBRARY as SQL$USER, users can automatically link SQL programs to the version of the SQL library established by RDB$SETVER.COM.

You can define LNK$LIBRARY as a system logical by using the following command:

$ DEFINE/SYSTEM/EXECUTIVE/NOLOG LNK$LIBRARY SQL$USER

Section 3.2.3 provides additional information about LNK$LIBRARY and SQL$USER.

2.4.6 Using LSE Templates in SQL

The LSE (Language-Sensitive Editor) templates allow users of interactive SQL and SQL module language to develop programs quickly and accurately.


Note:

The LSE templates provided with Oracle Rdb only provide support for SQL syntax through release 4.2. The templates do not provide support for new and changed syntax after release 4.2.  


With the multiversion variant of Oracle Rdb, LSE templates for each installed version of Oracle Rdb are available. After you have established a default Oracle Rdb environment using the RDB$SETVER command procedure, you must define a logical name to point to the appropriate LSE environment (.ENV) file. As you toggle between versions of Oracle Rdb, you must set the LSE environment accordingly.

LSE templates for Oracle Rdb release 7.1 are located in SYS$LIBRARY:LSE$SQL71MV_ENVIRONMENT.ENV. To access the SQL syntax, you must use one of the following methods:

2.4.7 Accessing Remote Databases

You can access a release 7.1 database on a remote node, even if your node is currently running an earlier version.

2.4.7.1 Using DECnet Transport

The LOGIN.COM command procedure for the RDB$REMOTE71 account defines the appropriate RDBSERVER and RDB$SHARE images to run. Users must specify the RDB$REMOTE71 account when they access a remote database. For example, to access the PERSONNEL database on node RAILS, enter the following command:

SQL> ATTACH 'FILENAME RAILS"RDB$REMOTE71 password"::DISK1:[DBASES]PERSONNEL';

To avoid displaying the password on the terminal screen, you can define proxies for appropriate users. See the Oracle Rdb7 Guide to SQL Programming for information about using proxies for remote access.

If you use a proxy account instead of using the RDB$REMOTE71 account, you must add the following lines to the account's LOGIN.COM file:

$ DEFINE RDBSERVER SYS$SYSTEM:RDBSERVER71.EXE
$ DEFINE RDMS$VERSION_VARIANT 71

2.4.7.2 Using TCP/IP Transport

You can define your own UCX service to access an earlier version of a database when using the TCP/IP transport. You must define this service to have a user name that is set up for the earlier version of Oracle Rdb. For example, to access a release 6.1 database, you can create a UCX service called rdbsrv61 that uses the user name rdb$remote61. Then add the following line to your client configuration file to use the UCX service:

SQL_ALTERNATE_SERVICE_NAME rdbsrv61

For more details on how to set up UCX services, see Section 4.1.3. For more information about configuration files, see Section 4.3.1 and Section 4.3.2.

In this example, if you choose to use a different user name than rdb$remote61 to access a release 6.1 database, the LOGIN.COM file of that user must contain the following lines:

$ DEFINE RDBSERVER SYS$SYSTEM:RDBSERVER61.EXE
$ DEFINE RDMS$VERSION_VARIANT 61

2.4.8 Accessing Online Help

After you install Oracle Rdb, users can access online help from the command line for each installed version of Oracle Rdb. The following is a list of varianted online help topics:

To access help on any multiversion variant installed on the system, type HELP and the topic name with a two-digit suffix representing the version. For example, to access the release 7.1 help on any of the varianted topics in the previous list, type HELP and the topic name with a "71" suffix:

$ HELP SQL71

You can invoke help on SQL statements while you are in interactive SQL by typing the following:

SQL> HELP

2.5 How Applications Access Multiple Versions of Oracle Rdb

The following images are installed in SYS$COMMON:[SYSLIB] by VMSINSTAL:

Many layered products and third-party products call RDBSHR.EXE at image activation time. With the multiversion variant of Oracle Rdb, more than one version of Oracle Rdb is available to an application. The version required depends on the parameter set by RDB$SETVER.COM.

Applications still call RDBSHR.EXE, but RDBSHR.EXE checks only what version the application wants to use by examining the logical name RDMS$VERSION_VARIANT. If RDMS$VERSION_VARIANT is not defined, RDBSHR.EXE calls RDB$SHARE.EXE, which contains the current released version code. If RDMS$VERSION_VARIANT translates to 60, RDBSHR.EXE calls RDB$SHARE60.EXE, which contains the release 6.0 code.

2.6 Errors That Cause the Installation or IVP to Fail

If errors occur during the installation itself or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message:

%VMSINSTAL-E-INSFAIL, The installation of RDB V7.1 has failed.

If the IVP fails, you see these messages:

The RDB V7.1 Installation Verification Procedure failed.

%VMSINSTAL-E-IVPFAIL, The IVP for RDB V7.1 has failed.

Errors can occur during the installation if any one of the following conditions exists:

2.7 Japanese Rdb Kit Included with the Oracle Rdb Release 7.1 Media

The Oracle Rdb release 7.1 media also contains the Japanese Rdb kit. After installing Oracle Rdb, you can use the VMSINSTAL command procedure to install the Japanese Rdb kit.

The save set name for the Japanese Rdb kit is:

JRDBAMV071


Go to previous page Go to next page
Oracle
Copyright © 2001 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Library
Go To Product List
Product
Go To Table Of Contents
Contents
Go To Index
Index