DEC RdbAccess for_ORACLE_on_VMS____________________________________ Installation Guide AA-PD69A-TE August 1990 This book describes how to install the DEC RdbAccess for ORACLE on VMS Version 1.0 software on a VMS system and run the Installation Verification Procedure (IVP). Operating System: VMS Software Version: DEC RdbAccess for ORACLE on VMS Version 1.0 digital equipment corporation maynard, massachusetts _____________________________________________________ First Printing, August 1990 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1990. All Rights Reserved. Printed in U.S.A. The Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-1, DEC, DECnet, VAX DATATRIEVE, VAX DOCUMENT, VAX Rdb /VMS, Rdb/VMS, VAX TEAMDATA, VIDA, VMS, and the DIGITAL Logo. The following are third-party trademarks: ORACLE[R], SQL*NET[R], and SQL*PLUS[R] are registered trademarks of the ORACLE Corporation. This document is available in printed and CDROM versions. This document was prepared using VAX DOCUMENT, Version 1.2. ________________________________________________________________ Contents Preface.................................................. vii 1 Preparing to Install RdbAccess 1.1 Required Operating System Components............ 1-1 1.2 Prerequisite Software........................... 1-2 1.2.1 Software Requirements for RdbAccess Installation................................. 1-2 1.2.2 Software Requirements for RdbAccess Use ...... 1-2 1.3 Prerequisite Hardware........................... 1-3 1.4 VMS License Management Facility................. 1-3 1.5 VAXcluster Considerations....................... 1-3 1.6 Installation Procedure Requirements............. 1-5 1.6.1 Time ......................................... 1-5 1.6.2 Privileges ................................... 1-5 1.6.3 Disk Space ................................... 1-5 iii 1.6.4 System Parameters ............................ 1-6 1.6.4.1 Checking System Parameter Values........... 1-6 1.6.4.2 Calculating the Values for GBLPAGES and GBLSECTIONS................................ 1-7 1.6.4.3 Changing System Parameter Values with AUTOGEN.................................... 1-7 1.6.5 Process Account Quotas ....................... 1-8 1.6.6 VMSINSTAL Requirements ....................... 1-9 1.6.7 Backing Up Your System Disk .................. 1-9 2 Installing the DEC RdbAccess for ORACLE on VMS Product 2.1 General Information............................. 2-1 2.1.1 Accessing the Online Release Notes ........... 2-1 2.1.2 Determining the Files Added to the System .... 2-2 2.1.3 Running the Installation Verification Procedure (IVP).............................. 2-2 2.1.4 Aborting the Installation .................... 2-2 2.1.5 Verifying the Installation of Prerequisite Software..................................... 2-2 2.2 Installation Procedure.......................... 2-3 2.2.1 Invoking VMSINSTAL ........................... 2-3 2.2.2 Answering Installation Questions ............. 2-4 2.2.3 Understanding Informational Messages ......... 2-13 2.2.4 Running the Installation Verification Procedure.................................... 2-16 2.2.5 Installation Completion ...................... 2-16 2.3 Error Recovery.................................. 2-17 3 After Installing RdbAccess 3.1 Modifying System Parameters..................... 3-1 3.2 User Account Requirements....................... 3-1 3.2.1 Privileges ................................... 3-2 3.2.2 User Account Quotas .......................... 3-2 3.3 Installing Licenses on All Nodes in a Cluster... 3-3 iv 3.4 Executing RDBSERVER_NCP.COM in VAXclusters...... 3-3 3.5 Meeting the ALL-IN-1 Product Requirements....... 3-4 3.6 Ensuring That RdbAccess Works with the VAX Data Distributor..................................... 3-5 3.7 Testing RdbAccess Installation and the Path to ORACLE.......................................... 3-6 3.7.1 Running the Live IVP ......................... 3-6 3.8 Determining and Reporting Problems.............. 3-10 A Sample Installation B Files Installed on Your System B.1 Files Transferred to SYS$SYSTEM................. B-1 B.2 Files Transferred to SYS$HELP................... B-2 B.3 Files Transferred to SYS$SHARE.................. B-2 B.4 Files Transferred to SYS$MESSAGE................ B-3 B.5 Files Transferred to SYS$COMMON:[SYSTEST]....... B-5 B.6 Files Transferred to SYS$MANAGER................ B-7 B.7 List of Product Files........................... B-7 Tables 1-1 Disk Space Requirements......................... 1-6 B-1 Executable Files in SYS$COMMON.................. B-1 B-2 Help Files in SYS$COMMON........................ B-2 B-3 Shareable Image Files in SYS$COMMON............. B-3 B-4 Message Files in SYS$COMMON..................... B-3 B-5 IVP Command Files in SYS$TEST:[SYSTEST]......... B-5 B-6 IVP Command Files in SYS$TEST:[SYSTEST.VIDAO$IVP].................... B-5 B-7 Command Files in SYS$MANAGER.................... B-7 B-8 Product Files................................... B-7 v ________________________________________________________________ Preface The DEC RdbAccess for ORACLE on VMS enables you, as a user of VMS, to retrieve data from an ORACLE Relational Database Management System. The DEC RdbAccess for ORACLE on VMS provides read-only access to ORACLE data tables. References in this manual to DEC RdbAccess for ORACLE on VMS Version 1.0 will be noted as RdbAccess. RdbAccess is an Rdb/VMS-compatible product that uses Rdb /VMS database interface procedures and standards. RdbAccess software must have access to one of the following: VAX Rdb /VMS, VAX DATATRIEVE, VAX TEAMDATA, or VAX Data Distributor. Purpose of This Manual This manual explains how to install RdbAccess. Intended Audience Read this manual if you are responsible for planning the installation, preparing the system, or installing RdbAccess. vii Operating System Information Your VAX system must be running Version 5.2 or higher of the VMS operating system before you can use RdbAccess. Structure This manual contains three chapters and two appendixes: Chapter 1, Preparing to Install RdbAccess, explains how to plan RdbAccess installation and prepare your system. Chapter 2, Installing the DEC RdbAccess for ORACLE on VMS Product, explains how to install RdbAccess software. Chapter 3, After Installing RdbAccess, discusses what to do after installing RdbAccess. Appendix A, Sample Installation, provides a sample RdbAccess installation procedure. Appendix B, Files Installed on Your System, lists the files transferred from the distribution kit to your system. Related Documents You can find additional information about RdbAccess in the following manuals: _ DEC RdbAccess for ORACLE on VMS Handbook This handbook describes how to use RdbAccess to access ORACLE data tables. It also contains information about various VMS products that you can use as interfaces to the ORACLE data. _ DEC RdbAccess for ORACLE on VMS Release Notes The Release Notes discuss restrictions, problems, and workarounds for RdbAccess. viii Conventions Three special symbols are used in this book. _____________________________________________________________ Symbol________Meaning________________________________________ $ The dollar sign is used to indicate the DCL prompt. A different prompt might be used on your system. red text Red text in hardcopy documentation indicates information that you must enter in response to a system prompt. In online documentation, user input is shown in boldface type. . Vertical ellipsis in an example means that . information not directly related to the example ._____________has_been_omitted.______________________________ References to Products The RdbAccess documentation often refers to Digital products by their abbreviated names: _ The DEC RdbAccess for ORACLE on VMS Version 1.0 software is referred to in the manuals as RdbAccess. However, because of certain software used by both RdbAccess and other DEC database products, the installation procedure often refers to RdbAccess as VIDAO or VIDA for ORACLE. _ The VAX CDD/Plus software is referred to as CDD/Plus. _ The VAX Data Distributor software is referred to as Data Distributor. _ The VAX DATATRIEVE software is referred to as DATATRIEVE. _ The VAX Rdb/VMS software is referred to as Rdb/VMS. _ The VAX TEAMDATA software is referred to as TEAMDATA. ix _ The Rdb/VMS SQL facility is referred to as Rdb/VMS SQL or as SQL. x 1 ________________________________________________________________ Preparing to Install RdbAccess This chapter discusses the preparations and requirements necessary for installing RdbAccess. RdbAccess provides access to an ORACLE Relational Database Management System (RDBMS) from a VMS-based environment. RdbAccess provides read-only access to ORACLE data tables. Your bill of materials (BOM) and indented bills report (BIL) specify the number and contents of your media. Be sure to verify the contents of your kit with this information. If your kit is damaged or if parts of it are missing, contact your Digital representative. 1.1 Required Operating System Components The VMS operating system comes with a variety of support options, or classes. Classes include such features as networking and Record Management Services (RMS) journaling. For a complete list of VMS support options or classes, and VMS classes and tailoring, see the Software Support Addendum (SSA) that comes with the VMS Operating System Software Product Description (SPD 25.01.xx). Preparing to Install RdbAccess 1-1 In addition to the base option VMS Version 5.2 classes, RdbAccess requires the following: _ Program development _ Network support _ Secure user environment _ Utilities 1.2 Prerequisite Software This section discusses the software you must have installed on your system before installing RdbAccess. The section also includes information about software that you can use with RdbAccess. Please refer to the System Software Addendum (SSA) for a complete list of compatible products and their required version numbers. The SSA is part of the Software Product Description (SPD) for RdbAccess. 1.2.1 Software Requirements for RdbAccess Installation You can install RdbAccess only after VMS Version 5.2 or higher has been successfully installed. The RdbAccess installation procedure verifies the prerequisite Version 5.2 of VMS software and stops if it has not been installed. 1.2.2 Software Requirements for RdbAccess Use The RdbAccess Distribution Kit does not include a user interface to retrieve data from an ORACLE system. Therefore, the following products are not required for RdbAccess installation. However, you cannot use RdbAccess until you successfully install at least one of the following: _ VAX DATATRIEVE at Version 4.2 or higher. _ VAX Data Distributor at Version 2.0 or higher. _ A programming language supported by the Rdb DML precom- piler. If you use a programming language as your interface to RdbAccess, VAX Rdb/VMS Version 3.0 or higher must be installed on the same system as the programming language software. _ VAX TEAMDATA at Version 1.3 or higher. 1-2 Preparing to Install RdbAccess 1.3 Prerequisite Hardware See the Software Product Description (SPD) for minimum hardware requirements. 1.4 VMS License Management Facility The license registration information you need is contained in the Product Authorization Key (PAK) that is shipped with RdbAccess. The PAK is a paper certificate that contains information about the license you have to run a particular piece of software. You must register your RdbAccess product license before you perform the installation. The installation procedure verifies whether you have registered and loaded the RdbAccess product license. If you have not already done so, answer NO. Once you perform the license registration and load, you can restart the installation. To register a license and for complete information about how to use LMF, see the VMS License Management Utility Manual. 1.5 VAXcluster Considerations The RdbAccess installation procedure defines RDB$REMOTE as the default DECnet account for the RDBSERVER object. RDBSERVER manages remote database access. This definition supersedes any previous assignment you might have made in the Network Control Program (NCP) for RDBSERVER. The RDB$REMOTE account includes a password that you assign during the installation procedure. The system uses the password you provide for the RDB$REMOTE account and in the DECnet NCP object database on your system. Thus the RDB$REMOTE password and the password assigned to the RDBSERVER.EXE image must be the same. After the installation procedure finishes, and if your DECnet object database is not configured to be in the cluster common directory, you must run the RDBSERVER_NCP.COM procedure from the SYS$COMMON:[SYSMGR] account on each of the remaining VAXcluster nodes to insert the RDBSERVER object of your system in the DECnet object database for those nodes. The system assigns the RDB$REMOTE account the correct process quotas and privileges to work with RdbAccess. When you encounter problems with remote database access, it is often because the default DECnet account commonly does not have sufficient process quotas. Preparing to Install RdbAccess 1-3 The RDB$REMOTE account does not require a SYLOGIN.COM procedure in the SYS$MANAGER account. However, if you encounters errors using the RDB$REMOTE account, ensure that the SYS$SYLOGIN logical name (if defined) points to a working SYLOGIN.COM procedure. RDB$REMOTE requires its own login procedure. The login procedure for RDB$REMOTE is RDB$REMOTE_LOGIN.COM and is written to SYS$COMMON:[SYSEXE]. This login procedure includes security checks to ensure that the RDB$REMOTE user is running the RDBSERVER.EXE image. To execute procedures during the RDB$REMOTE account login, you must edit RDB$REMOTE_LOGIN.COM in the SYS$COMMON:[SYSEXE] directory after the installation and insert the appropriate DCL commands. The DECnet product need not be running for a successful installation of RdbAccess. See the VAX DECnet manuals for additional information. 1-4 Preparing to Install RdbAccess 1.6 Installation Procedure Requirements The following sections discuss various requirements for installing RdbAccess. 1.6.1 Time The installation takes approximately ten to twenty minutes, depending on your type of media and your system configu- ration. For example, installing RdbAccess and running the IVP on a standalone VAX 8200 system takes approximately ten minutes. 1.6.2 Privileges To install RdbAccess you must be logged in to an account that has SETPRV or at least the following privileges: _ CMKRNL _ EXQUOTA _ NETMBX _ OPER _ SYSNAM _ SYSPRV _ TMPMBX _ WORLD Note that VMSINSTAL turns off the BYPASS privilege at the start of the installation. 1.6.3 Disk Space Installing RdbAccess requires a certain amount of free disk space on the system disk during the installation. Once RdbAccess is installed, less space is required. Table 1-1 summarizes the disk requirements for RdbAccess. Preparing to Install RdbAccess 1-5 Table 1-1 Disk Space Requirements _____________________________________________________________ Blocks During Blocks After Kit______________Installation__________Installation__________ RdbAccess________4500__________________1900__________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1.6.4 System Parameters Installing RdbAccess requires certain system parameter settings. The parameter settings required are the default parameter settings. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. The following sections show you how to check system parameter values, set the CLISYMTBL dynamic system parameter with the VMS System Generation Utility (SYSGEN), calculate values for the GBLPAGES and GBLSECTIONS system parameters, and change parameter values with the VMS AUTOGEN command procedure. 1.6.4.1 Checking System Parameter Values To check the values of your system parameters, enter the following command at the DCL prompt to invoke the System Generation Utility: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the default system parameter. The following command displays the value for the CLISYMTBL system parameter: SYSGEN> SHOW CLISYMTBL After you finish checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. 1-6 Preparing to Install RdbAccess 1.6.4.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run RdbAccess, you must have sufficient free global pages and global sections. Verify how many free global pages and sections you have on your system. Then use AUTOGEN to increase the GBLPAGES and GBLSECTIONS system parameters, if necessary. Use the WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI ("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI ("FREE_GBLSECTS") 24 If the system displays numbers that are greater than these values, you do not have to increase the values for these parameters. If the number of free global pages or free global sections is less than the previously mentioned values, you must increase the system parameter setting. Section 1.6.4.3, Changing System Parameter Values with AUTOGEN, describes the procedure for increasing these values by using AUTOGEN. Refer to the VMS System Management Subkit for information about how to use AUTOGEN. 1.6.4.3 Changing System Parameter Values with AUTOGEN You use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the ones you reset manually. To change system parameters with AUTOGEN, you must edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. If you must change a param- eter value that is already in the SYS$SYSTEM:MODPARAMS.DAT file, delete the current value associated with that parameter and enter the new value. To add a new value, add a line to the MODPARAMS.DAT file. The line contains the name of the parameter and its value. For example: WSMAX = 1024 Preparing to Install RdbAccess 1-7 You can also modify incremental parameters in the MODPARAMS.DAT file. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 After you have made all your changes, run the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT AUTOGEN performs an automatic system shutdown and reboots when it has finished. Rebooting your system makes the new parameter values active. When you reboot a system under VMS Version 5.2, the Autogen Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the /NOFEEDBACK qualifier on the AUTOGEN command line. For information about using AUTOGEN, see the instructions about how to modify system parameters in the VMS documenta- tion on system management and operations. 1.6.5 Process Account Quotas The account you use to install RdbAccess must have sufficient quotas to enable you to perform the installation. The installation of RdbAccess requires only the default process account quotas. The system stores your account quotas in the file SYSUAF.DAT. Use the VMS Authorize Utility to verify and change your account quotas if required. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the Authorize Utility prompt (UAF>), use the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH 1-8 Preparing to Install RdbAccess To change a quota, use the MODIFY command at the UAF> prompt. MODIFY has the following format: MODIFY account-name /quota-name=nnnn The following example changes the FILLM quota for the SMITH account and then exits from the Authorize Utility: UAF> MODIFY SMITH /FILLM=50 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For information about how to modify account quotas, see the description of the Authorize Utility in the VMS documentation set. 1.6.6 VMSINSTAL Requirements When you invoke VMSINSTAL, it verifies the following: _ Whether you have set your default device and directory to SYS$UPDATE _ Whether you are logged in to a privileged account _ Whether you have adequate quotas for installation _ Whether any users are logged in to the system Note that VMSINSTAL requires that the installation account have the standard (or higher) system default quotas. If VMSINSTAL detects any problems during the installation, it notifies you of the problem and asks whether you want to continue the installation. In some instances, you can enter Yes to continue. To stop the installation process and correct the situation, enter No or press Return. Then correct the problem and restart the installation. 1.6.7 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL verifies whether you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software on top of the operating system. Preparing to Install RdbAccess 1-9 Use the backup procedures that have been established at your site. For details about how to perform a system disk backup, see the section about the BACKUP Utility in the VMS documentation set. 1-10 Preparing to Install RdbAccess 2 ________________________________________________________________ Installing the DEC RdbAccess for ORACLE on VMS Product This chapter describes how to install RdbAccess. Section 2.2, Installation Procedure, contains a step-by-step description of the installation procedure. 2.1 General Information This section includes information about the following topics: _ Accessing release notes _ Determining files added to your system _ Running the Installation Verification Procedure (IVP) _ Aborting the installation _ Verifying the installation of prerequisite software 2.1.1 Accessing the Online Release Notes RdbAccess provides online release notes. You must specify OPTIONS N when you invoke VMSINSTAL to see the question about online release notes. This question comes near the beginning of the installation procedure. You should review the release notes in case they contain any information about changes in the installation procedure. If you are starting the installation over again and have already reviewed the release notes, you need not specify OPTIONS N. Installing the DEC RdbAccess for ORACLE on VMS Product 2-1 You can find the release notes in the following file after the the system installs RdbAccess: SYS$HELP:VIDAO$010.RELEASE_NOTES Online help also directs you to the release notes file. After the installation, you can enter the following command to review the release notes through the Help facility: $ HELP VIDA_ORACLE RELEASE_NOTES 2.1.2 Determining the Files Added to the System The files added to the system during RdbAccess installation are listed and described in Appendix B of this Installation Guide. 2.1.3 Running the Installation Verification Procedure (IVP) During the installation, the system verifies that you want to run the IVP as part of the installation. You can run the IVP procedure at any time. Execute the IVP with the following: $ SET DEF SYS$COMMON:[SYSTEST] $ @VIDAO$IVP The IVP run by the installation merely verifies the presence of the required files and their locations. After installation you may run the Live IVP, which does more thorough testing. 2.1.4 Aborting the Installation To abort the installation procedure and delete associated files at any time, press CTRL/Y. You can then start the installation again. 2.1.5 Verifying the Installation of Prerequisite Software The Live Installation Verification Procedure requires that Rdb/VMS, which contains SQL software, be installed on your system. Ask your system manager to be sure that the Rdb/VMS software is operating before you use the IVP procedure. ORACLE also includes a Demonstration Database as part of its software. The Live IVP will not run if this database is not installed. 2-2 Installing the DEC RdbAccess for ORACLE on VMS Product 2.2 Installation Procedure The RdbAccess 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. VMSINSTAL is in the SYS$UPDATE directory. Use the following syntax to invoke VMSINSTAL: @SYS$UPDATE:VMSINSTAL product-name device-name OPTIONS N product-name The installation name for the component. For RdbAccess use the installation name VIDAO. device-name The name of the device on which you plan to mount the media. For example, MTA0:. If you use the console drive for this installation, replace any media you removed once the installation is complete. OPTIONS N The optional parameter that indicates that you want to see the release notes question. VMSINSTAL does not prompt you for any option. Thus, if you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain new information about the installation procedure. You can select several other options when you invoke VMSINSTAL. See the VMS documentation about software installation in the VMS System Management Subkit for information about these options. The following example displays the command that invokes VMSINSTAL to install RdbAccess from the system disk and shows the system response. This example uses the OPTIONS N release note parameter. $ @VMSINSTAL VIDAO SYS$SYSROOT:[SYSMGR] OPTIONS N VAX/VMS Software Product Installation Procedure V5.2 It is 9-APR-1990 at 14:18. Installing the DEC RdbAccess for ORACLE on VMS Product 2-3 Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. 2.2.2 Answering Installation Questions This section discusses the questions displayed during the installation. Appendix A contains a sample installation procedure and shows how the questions can be answered. The procedure marks each question with an asterisk (*) at the beginning of the line. Some questions show the default response in brackets, for example [YES]. If you want to use the default response, press the RETURN key. 1 System backup VMSINSTAL asks whether 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 RETURN. Otherwise enter No to discontinue the installation. After you back up your system disk you can restart the installation. * Are you satisfied with the backup of your system disk [YES]? 2 Mounting the media You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks where the distribution volumes will be mounted. If you respond YES to indicate that you are ready, VMSINSTAL displays a message stating that the media containing RdbAccess has been mounted on the specified device and that the installation has begun. For example: The following products will be processed: VIDAO V1.0 Beginning installation of VIDAO V1.0 at 14:18 %VMSINSTAL-I-RESTORE, Restoring product saveset A... 2-4 Installing the DEC RdbAccess for ORACLE on VMS Product If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter No in response to the question "Are you ready?" Installing the DEC RdbAccess for ORACLE on VMS Product 2-5 3 Release Notes If you specified OPTIONS N when you started the instal- lation, VMSINSTAL asks a release note question. You have four options when handling the release notes under VMS Version 5.2 and higher versions. The display for VMS Version 5.2 and higher versions is as follows: Release Notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: If you select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing CTRL/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can press RETURN to send the file to the default output print device or you can enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. Select option 4 if you are running VMS Versions 5.2 or 5.3 and have already reviewed the release notes and you are restarting the installation. 4 Continuing the installation The installation procedure now verifies whether you want to continue the installation. To continue, enter Yes. Otherwise press Return. In either case, the installation procedure copies the release notes to a file in the SYS$HELP directory. For example: 2-6 Installing the DEC RdbAccess for ORACLE on VMS Product * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. The release notes are located in the following file: SYS$HELP:VIDAO$010.RELEASE_NOTES Installing the DEC RdbAccess for ORACLE on VMS Product 2-7 5 Checking system requirements While the installation procedure checks several system requirements, the following messages are displayed: ******************************************************* Installation procedures for: VIDAO V1.0-0 ******************************************************* ******************************************************* Checking system requirements ... ******************************************************* The installation procedure displays an error message and aborts if the procedure finds that your system does not have the following software and hardware requirements: _ VMS Version 5.2 or higher _ Adequate disk space _ Adequate free global pages and global sections _ RdbAccess license If you encounter an error at this point, take the steps necessary to meet your system requirements and restart the installation procedure. 6 License registration The installation procedure displays license information about your product and then asks if you have registered and loaded your authorization key for RdbAccess. For example: Product: RDBACCESS-ORACLE Producer: DEC Version: 1.0 Release Date: 20-JUL-1990 * Does this product have an authorization key registered and loaded? If you have not registered and loaded your authorization key, you must answer No to this question. You have to register and load your product authorization key to successfully complete the installation. If you have not done so, stop the installation, register and load 2-8 Installing the DEC RdbAccess for ORACLE on VMS Product your product authorization key, and then restart the installation. If you encounter any LMF error messages, refer to the VMS License Management Utility Manual. Installing the DEC RdbAccess for ORACLE on VMS Product 2-9 7 Entering the UIC and password for the RDB$REMOTE account The installation procedure displays a series of messages and questions about the RDB$REMOTE account if it is not already part of the system: ************************************************************ This installation requires the creation of the RDB$REMOTE account. You MUST choose a UIC and password for this account. PLEASE NOTE that your password for the RDB$REMOTE account and the network object RDBSERVER MUST be exactly the same. The system uses the password you supply for the RDB$REMOTE account for the network object as well if the account is created by this installation. ************************************************************* ************************************************************* The installation procedure will not proceed until you enter a valid user identification code (UIC) for the RDB$REMOTE account. ************************************************************* * Please enter UIC to be used for RDB$REMOTE account (e.g. [ggg,mmm]): You must supply a valid UIC or the installation procedure cannot continue. When a valid UIC has been provided, the installation procedure then displays an informational message about entering password information: ************************************************************* The entire installation will FAIL if you do not enter a valid password for the RDB$REMOTE account. You will be given 3 chances to verify your password. This installation procedure requires at least 6 characters for the RDB$REMOTE password. Valid characters for a password are: A through Z a through z 0 through 9 $ (dollar sign) _ (underscore) 2-10 Installing the DEC RdbAccess for ORACLE on VMS Product As with the DCL SET PASSWORD command, your input will not appear on the terminal. And to protect against typing errors that are not seen when entering the password, you must enter the password twice. ************************************************************** * Please enter PASSWORD to be used for RDB$REMOTE account: * Please verify the PASSWORD entered for RDB$REMOTE: Installing the DEC RdbAccess for ORACLE on VMS Product 2-11 8 Entering the version of ORACLE to be used The installation procedure prompts you to enter the version of ORACLE that your system is using (Version 5 or Version 6). * Please enter the version of Oracle to be used (V5 or V6)?: v6 9 Entering the name of the user command file The installation procedure prompts you to enter the name of the user command file. The command file defines the logical names and symbols necessary for you to access ORACLE. The ORACLE installation procedure creates this command file. * Please enter the name of the oracle user command file (default orauser.com) [ORAUSER.COM]: 10 Entering the location of the user command file * Please enter the location of the above file (disk and directory): user2:[oracle.util] The installation procedure now checks for the existence of the file and if it does not exist, the procedure will ask you to enter the location again. 11 Choosing to purge files VMSINSTAL gives you the option to purge files from previous versions of the product being installed. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. If this is a Version 1 software, enter the default response [YES]. * Do you want to purge files replaced by this installation [YES]? 12 Choosing to run the Installation Verification Procedure (IVP) The installation procedure now verifies whether you want to run the Installation Verification Procedure. Refer to Section Section 2.1.3, Running the Installation Verification Procedure (IVP), and Section Section 3.7.1, Running the Live IVP, for information about the IVP procedure. DIGITAL recommends that you run the IVP. * Do you want to run the IVP after the installation [YES]? 2-12 Installing the DEC RdbAccess for ORACLE on VMS Product 2.2.3 Understanding Informational Messages At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. 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. Installing the DEC RdbAccess for ORACLE on VMS Product 2-13 The following messages are displayed: **************************************************************** There are no more questions. The installation takes ap- proximately 5 minutes on a stand-alone VAX 8200. **************************************************************** **************************************************************** Beginning installation ... **************************************************************** **************************************************************** Installing under VMS V5.2 - 9-APR-1990 14:21 **************************************************************** %VMSINSTAL-I-RESTORE, Restoring product saveset B ... Restoring file: $1$DUA5:[SYS1.SYSUPD.VIDAO010]DSRI_INSTALL.COM;1 Saveset volume:1, saveset block:2 (9216 byte blocks) **************************************************************** The VIDAO IVP has been placed in SYS$COMMON:[SYSTEST]. You may run this procedure separately any time you wish. To execute it, type : $ SET DEF SYS$COMMON:[SYSTEST] $ @VIDAO$IVP ************************************************************* ************************************************************* The Live VIDAO IVP has been placed in SYS$COMMON:[SYSTEST]. You may run this procedure separately after the environment has been set up. To execute it, type : $ SET DEF SYS$COMMON:[SYSTEST] $ @VIDAO$LIVE_IVP ************************************************************* **************************************************************** Adding VIDAO help to the DCL help library **************************************************************** ************************************************************* 2-14 Installing the DEC RdbAccess for ORACLE on VMS Product The qualifier LGICMD for the RDB$REMOTE account in SYSUAF is modified by this installation. ************************************************************* %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ***************************************************************** The VIDA for ORACLE IVP verifies that all files are properly in place. ***************************************************************** Installing the DEC RdbAccess for ORACLE on VMS Product 2-15 ************************************************************* Performing VIDA/ORACLE IVP for: VIDAO V1.0-0 ************************************************************* ************************************************************* VIDAO V1.0-0 IVP completed successfully ************************************************************* Installation of VIDAO V1.0 completed at 14:28 VMSINSTAL procedure done at 14:28 DIGITAL provides some common images with all Rdb/VMS- compatible database products. Thus the installation procedure for RdbAccess may not install some images. For example, if the version on the system is more recent than the image being installed, the typical messages displayed are as follows: %VIDAO-I-NOTINSTALLED, VMI$KWD:RDBSHR.EXE was not installed by this kit %VIDAO-I-REASON, Image ident version of new file is the same as current file RdbAccess displays messages of this type just before the message about moving files to other directories. 2.2.4 Running the Installation Verification Procedure If you chose to run the installation IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: **************************************************** VIDAO 1.0-0 IVP completed successfully **************************************************** 2.2.5 Installation Completion The following messages indicate that the entire installation procedure is complete: Installation of VIDAO V1.0 completed at 09:28 VMSINSTAL procedure done at 09:28 2-16 Installing the DEC RdbAccess for ORACLE on VMS Product Note that VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. $ LOGOUT SYSTEM logged out at 09-APR-1990 at 09:41:36.50 2.3 Error Recovery 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 VIDAO V1.0 has failed. If the IVP fails, you see these messages: The RdbAccess V1.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for RdbAccess V1.0 has failed. Errors can occur during the installation if any of the following conditions exist: _ The operating system version is incorrect or not installed. _ Quotas necessary for successful installation are insufficient. _ System parameter values for successful installation are insufficient. _ The VMS help library is currently in use. _ The product license has not been registered and loaded. For descriptions of the error messages generated by these conditions, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For example, you might need to change a system parameter or increase an authorized quota value. For information about installation requirements, see Chapter 1. Installing the DEC RdbAccess for ORACLE on VMS Product 2-17 3 ________________________________________________________________ After Installing RdbAccess After installing RdbAccess, you must perform the following tasks: _ Modify system parameter settings. _ Set user account quotas. _ Install licenses on all nodes in a cluster. _ Execute RDBSERVER_NCP.COM in VAXclusters. _ Meet the ALL-IN-1 product requirements. _ Ensure that the RdbAccess software works with VAX Data Distributor. This chapter also explains how to run the Installation Verification Procedure (IVP) independently after the software has been installed. 3.1 Modifying System Parameters The installation for RdbAccess requires that you raise the value of the CLISYMTBL system parameter. Once the installation is complete you should lower this value to ensure efficient system performance. 3.2 User Account Requirements To work with RdbAccess, user accounts on your system must have certain privileges and quotas. The next two sections contain information about these requirements. After Installing RdbAccess 3-1 3.2.1 Privileges To use RdbAccess, each account must have at least the TMPMBX and NETMBX privileges. Use the VMS Authorize Utility to determine whether users have the privileges they require. 3.2.2 User Account Quotas In most cases, default values for system quotas are adequate for the RdbAccess users. However, RdbAccess users who submit batch jobs might need a FILLM quota greater than 20. If an RdbAccess user encounters the error "quota exceeded," increase the user's FILLM quota to 30. User account quotas are stored in the file SYSUAF.DAT. You use the VMS Authorize Utility to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the Authorize Utility prompt (UAF>), enter the SHOW command with an account name to check that particular account. For example: UAF> SHOW SMITH To change a quota, use the modify command at the UAF> prompt. Modify has the following syntax: MODIFY account-name /quota-name=nnnn The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /FILLM=30 UAF> EXIT After you exit from the utility, the VMS system displays messages indicating whether or not changes were made. Once you have finished making the changes, the users must log out and log in again for the new quotas to take effect. For more information about modifying account quotas, see the description of the Authorize Utility in the VMS documentation set. 3-2 After Installing RdbAccess 3.3 Installing Licenses on All Nodes in a Cluster A license should be installed on all the nodes in a cluster. If you try to run RdbAccess on a clustered node that does not have the required licenses registered, you receive an error message. Follow these steps to install the licenses on all nodes in your cluster: 1 Install the license on one node by entering the following command: $ @SYS$UPDATE:VMSLICENSE.COM 2 Load the license on the rest of the nodes in the cluster: $ LICENSE LOAD RDBACCESS-ORACLE If you encounter any errors, refer to the VMS License Management Utility Manual. 3.4 Executing RDBSERVER_NCP.COM in VAXclusters If your DECnet object database is not configured to be in the cluster common directory (the default starting in VMS Version 4.4), you must insert the RDBSERVER object in each node's DECnet object database. This action enables remote database access on nodes sharing the cluster common directory. Follow these steps: 1 Log in to each node. 2 Invoke SYS$COMMON:[SYSMGR]RDBSERVER_NCP.COM. The RDBSERVER_NCP.COM procedure prompts for the password to assign to the RDBSERVER object. For remote database access to work, you must assign the password entered during RdbAccess installation procedure. For example, if PASSERBY_WORD was the password you assigned to the RDB$REMOTE account during the installation procedure on a VAXcluster node MOE, you must log in to each remaining node and perform the following procedures: After Installing RdbAccess 3-3 $ SET DEFAULT SYS$COMMON:[SYSMGR] $ @RDBSERVER_NCP Please enter the password for object name RDBSERVER: PASSERBY_WORD Please verify password: PASSERBY_WORD 3.5 Meeting the ALL-IN-1 Product Requirements RdbAccess installation includes images to ensure that ALL- IN-1 works properly. The VMS operating system requires that all image files activated by a privileged image be installed by the VMS Install Utility (INSTALL). The ALL-IN-1 image is a privileged image that activates all the images in the SYS$SHARE directory and the message file images that are subordinate to the images in SYS$SHARE. 3-4 After Installing RdbAccess If you are installing RdbAccess on a system that runs ALL-IN- 1, you should use INSTALL to add any of the following images that were not PREVIOUSLY installed for ALL-IN-1 before you installed RdbAccess: $ RUN SYS$SYSTEM:INSTALL INSTALL> ADD SYS$SHARE:VIDAOSHR.EXE INSTALL> ADD SYS$SHARE:VIDAOS.EXE INSTALL> ADD SYS$SHARE:RDBSHR.EXE INSTALL> ADD SYS$MESSAGE:VIDAO$MESSAGE.EXE INSTALL> ADD SYS$MESSAGE:RDBMSGS.EXE INSTALL> ADD SYS$MESSAGE:RDBBMSGS.EXE INSTALL> ADD SYS$MESSAGE:RDMSMSG.EXE INSTALL> ADD SYS$MESSAGE:VIDA_MESSAGE.EXE You can modify your system startup command file to include an INSTALL command for all of the preceding files. (Your system startup command file might already include INSTALL commands for RDBSHR.EXE and some of the message images if Rdb/VMS or another Rdb/VMS-compatible product is installed on your system.) 3.6 Ensuring That RdbAccess Works with the VAX Data Distributor The RdbAccess installation includes images that you might need to install with INSTALL to be sure that VAX Data Distributor works correctly with RdbAccess. VMS Data Distributor is a privileged image that activates some of the images in the SYS$SHARE directory and also message file images that are subordinate to the images in SYS$SHARE. The VMS operating system requires that all image files activated by a privileged image be installed using INSTALL. If you are installing RdbAccess on a system that runs Data Distributor, you should use INSTALL to add any of the following images that were not previously installed for the Data Distributor: After Installing RdbAccess 3-5 $ RUN SYS$SYSTEM:INSTALL INSTALL> ADD SYS$SHARE:VIDAOSHR.EXE INSTALL> ADD SYS$SHARE:VIDAOS.EXE INSTALL> ADD SYS$MESSAGE:VIDAO$MESSAGE.EXE You can modify your system startup command file to include an INSTALL command for each of these files. 3.7 Testing RdbAccess Installation and the Path to ORACLE The RdbAccess Installation Verification Procedure (IVP) ensures that the files copied during RdbAccess installation reside in the appropriate system directories. The Live IVP invokes a procedure that tests the data access path from the user interface to the ORACLE RDBMS. You can also check the data access path by using Digital user interface software, such as DATATRIEVE or the Relational Database Operator (RDO) utility of Rdb/VMS, to retrieve data from ORACLE. Retrieving data tests the outermost software layers of your VMS to ORACLE link. It verifies that your Digital user interface software works correctly with RdbAccess. The live IVP verifies that the data table definitions and user access to tables are set up correctly. Ask your ORACLE Database Administrator to ensure that the ORACLE SQL*Net is set up to access a remote ORACLE database. For more information refer to the Section entitled "Using the Digital Network" in the DEC RdbAccess for ORACLE on VMS Handbook. 3.7.1 Running the Live IVP The VIDAO$LIVE_IVP procedure first verifies that the RdbAccess software has been installed. VIDAO$LIVE_IVP then invokes another procedure that tests RdbAccess data access path. This procedure sets up the user environment, invokes the Rdb/VMS SQL facility to enter a query, compares the results of the query with expected results and reports the differences, and indicates if the IVP procedure completed successfully. After RdbAccess is installed you must use the SQL*PLUS facil- ity of ORACLE to install the VIDAO Catalog Views. The defini- tions for the VIDAO Catalog Views are in SYS$COMMAND:[SYS$TEST.VIDAO$TEST]. They are called VIDAO_CATV5.SQL (for use with an ORACLE V5 system) and 3-6 After Installing RdbAccess VIDAO_CATV6.SQL (for use with an ORACLE V6 system). The steps you must take are as follows: For ORACLE Version 5: _ Run the ORAUSER.COM file _ Log on to the system account by using SQL*PLUS as follows: $ SQLPLUS SYS/user_password _ Run VIDAO_CATV5.SQL as follows: SQLPLUS> @VIDAO_CATV5 After Installing RdbAccess 3-7 For ORACLE Version 6: _ Run the ORACLE INSTANCE startup file _ Log on to the system account by using SQL*PLUS as follows: $ SQLPLUS SYS/user_password _ Run VIDAO_CATV6.SQL as follows: SQLPLUS> @VIDAO_CATV6 The definitions first try to drop the VIDAO Views. (This is needed to reinstall the Views or to upgrade from an ORACLE V5 to an ORACLE V6 system). Therefore, the message that Views VIDAO_COLUMNS and VIDAO_INDEXES do not exist is a normal message. Because the Live IVP expects to connect to ORACLE on the host node (by using the /NODE=0 qualifier), you should define the task object in NCP as: $ SET OBJECT TASK NUMBER 0 USER oracle_account PASSWORD oracle_password Also, you must follow these steps: _ Place the ORDNDFLT.COM file in the ORACLE_ACCOUNT directory. _ Install the ORACLE demonstration database for user SCOTT. The Live VIDAO IVP has been placed in SYS$COMMON:[SYSTEST]. You may run this procedure separately after the environment has been set up. To execute it, type : $ SET DEF SYS$COMMON:[SYSTEST] $ @VIDAO$LIVE_IVP The following is an example of running the Live IVP. 3-8 After Installing RdbAccess ************************************************************** * * * RdbAccess Live IVP * * * * Note: This procedure must be run from the system test * * directory: SYS$TEST:[SYSTEST]. * * * * The RdbAccess live IVP first verifies that all * * RdbAccess files are in place. The live IVP then * * accesses two tables in an ORACLE (R) RDBMS, executes two * * queries, and compares the results with a supplied * * output file. Any differences in the outputs will cause * * the test to fail and are reported in VIDAO$LIVE_IVP.DIF. * * The results of the queries are in VIDAO$LIVE_IVP.RES. * * * ************************************************************** After Installing RdbAccess 3-9 Press the RETURN key to continue: ************************************************************** The RdbAccess IVP verifies that all files are properly in place. ************************************************************** Performing RdbAccess IVP for: VIDAO V1.0-0 *************************************************************** VIDAO V1.0-0 IVP completed successfully *************************************************************** Press the RETURN key to continue: *************************************************************** Performing VIDAO$LIVE_IVP for: VIDAO V1.0-0 *************************************************************** * Is the environment set up to run RdbAccess (YES/NO)[NO]?: YES ************************************** * * * The following is the Database Name * * * ************************************** "VIDAO_DATABASE" = "/TYPE=VIDAO/CREATOR=SMITH/USER=SCOTT /PASSWORD=TIGER/NODE=0" *************************************************************** VIDAO V1.0-0 Live IVP completed successfully *************************************************************** 3.8 Determining and Reporting Problems If you encounter a problem while using RdbAccess, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: _ Call Digital if your software support contract or warranty agreement entitles you to telephone support. _ Submit a Software Performance Report (SPR). 3-10 After Installing RdbAccess _ Fill out and submit a Reader's Comments form if the problem is related to RdbAccess documentation. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternative instructions provided by Digital for reporting SPD nonconformance problems. After Installing RdbAccess 3-11 A ________________________________________________________________ Sample Installation This sample was run on a system that had no previous version of RdbAccess installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. This sample installation was run under VMS Version 5.2. The sample installation assumes that the DECnet product has been shut down, that no users are logged on to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation. $ SET DEFAULT SYS$UPDATE $ SHOW DEFAULT SYS$SYSROOT:[SYSUPD] $ @VMSINSTAL VIDAO SYS$SYSROOT:[SYSMGR] OPTIONS N VAX/VMS Software Product Installation Procedure V5.2 It is 9-APR-1990 at 14:18. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: ORACLEC$BWR ORACLEC$BIW ORACLEC$CLN ORACLEC$ARH ORA_V6I1_PMON ORA_V6I1_DBWR ORA_V6I1_LGWR ORA_V6I1_SMON Sample Installation A-1 * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? A-2 Sample Installation The following products will be processed: VIDAO V1.0 Beginning installation of VIDAO V1.0 at 14:18 %VMSINSTAL-I-RESTORE, Restoring product saveset A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: 4 * Do you want to continue the installation [NO]? y %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. ************************************************************* Installation procedures for: VIDAO V1.0 ************************************************************* ************************************************************* Checking system requirements ... ************************************************************* Product: RDBACCESS-ORACLE Producer: DEC Version: 1.0 Release Date: 20-JUL-1990 * Does this product have an authorization key registered and loaded? y ************************************************************* This installation requires the creation of the RDB$REMOTE account. You MUST choose a UIC and password for this account. PLEASE NOTE that your password for the RDB$REMOTE account and the network object RDBSERVER MUST be exactly the same. The password you supply for the RDB$REMOTE account will be used for the network object as well IF the account is created by this installation. ************************************************************** ************************************************************* Sample Installation A-3 The installation procedure will not proceed until you enter a valid user identification code (UIC) for the RDB$REMOTE account. ************************************************************** * Please enter UIC to be used for RDB$REMOTE account (e.g. [ggg,mmm]): [200,201] ************************************************************* The entire installation will FAIL if you do not enter a valid password for the RDB$REMOTE account. You will be given 3 chances to verify your password. This installation procedure requires at least 6 characters for the RDB$REMOTE password. Valid characters for a password are: A through Z a through z 0 through 9 $ (dollar sign) _ (underscore) As with the DCL SET PASSWORD command, your input will not appear on the terminal. And to protect against typing errors that are not seen when entering the password, you must enter the password twice. ************************************************************* * Please enter PASSWORD to be used for RDB$REMOTE account: VIDADB * Please verify the PASSWORD entered for RDB$REMOTE: VIDADB * Please enter the version of ORACLE to be used (V5 or V6)?: v6 * Please enter the name of the ORACLE user command file (default orauser.com) [ORAUSER.COM]: * Please enter the location of the above file (disk and directory): user2:[oracle.util] * Do you want to purge files replaced by this installation [YES]? * Do you want to run the IVP after the installation [YES]? ************************************************************* There are no more questions. The installation takes ap- proximately 5 minutes on a stand-alone VAX 8200. ************************************************************* ************************************************************* A-4 Sample Installation Beginning installation ... ************************************************************* ************************************************************* Installing under VMS V5.2 - 9-APR-1990 14:21 ************************************************************* %VMSINSTAL-I-RESTORE, Restoring product saveset B ... Restoring file: $1$DUA5:[SYS1.SYSUPD.VIDAO010]DSRI_INSTALL.COM;1 Saveset volume:1, saveset block:2 (9216 byte blocks) Sample Installation A-5 ************************************************************* The VIDAO IVP has been placed in SYS$COMMON:[SYSTEST.VIDAO$TEST]. You may run this procedure separately any time you wish. To execute it, type : $ SET DEF SYS$COMMON:[SYSTEST] $ @VIDAO$IVP ************************************************************* ************************************************************* The Live VIDAO IVP has been placed in SYS$COMMON:[SYSTEST]. You may run this procedure separately after the environment has been set up. To execute it, type : $ SET DEF SYS$COMMON:[SYSTEST] $ @VIDAO$LIVE_IVP ************************************************************* ************************************************************* Adding VIDAO help to the DCL help library ************************************************************* ************************************************************* The qualifier LGICMD for the RDB$REMOTE account in SYSUAF is modified by this installation. ************************************************************* %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... ***************************************************************** The DEC RdbAccess for ORACLE on VMS IVP verifies that all files are properly in place. ***************************************************************** ************************************************************* Performing RdbAccess for ORACLE IVP for: VIDAO V1.0 ************************************************************* ************************************************************* VIDAO V1.0 IVP completed successfully A-6 Sample Installation ************************************************************* Installation of VIDAO V1.0 completed at 14:28 VMSINSTAL procedure done at 14:28 Sample Installation A-7 B ________________________________________________________________ Files Installed on Your System The following sections list the name of each file transferred to your system when you install RdbAccess. B.1 Files Transferred to SYS$SYSTEM Table B-1 lists the executable files that the installation procedure transfers to the directory SYS$COMMON:[SYSEXE]. Table B-1 Executable Files in SYS$COMMON _____________________________________________________________ File_Name_____________Purpose________________________________ RDB$REMOTE_LOGIN.COM The login command procedure for the RDB$SERVER account. RDBSERVER.EXE Rdb/Remote Server image. RDBSERVER.COM Rdb/Remote Server command file. The command procedure starts the RDB server process to provide remote ______________________database_access_capability.____________ Files Installed on Your System B-1 B.2 Files Transferred to SYS$HELP Table B-2 lists the help files that the installation procedure transfers to the directory SYS$COMMON:[SYSHLP]. Table B-2 Help Files in SYS$COMMON _____________________________________________________________ File_Name_____________Purpose________________________________ RDB_MSG.DOC Documentation file for errors generated by the Rdb/VMS-compatible interface. Error messages use the 3-letter facility code RDB. VIDAO$MESSAGE.DOC Documentation file for errors generated by RdbAccess. RdbAccess error messages use the facility code VIDAO. VIDAO$HELP_DCL.HLP Source file for the DCL help text that the installation procedure inserts into the library SYS$COMMON:[SYSHLP]. To customize the help on your system you can edit this file and build a new help library. VIDAO$010.RELEASE_ The RdbAccess product release notes. NOTES________________________________________________________ B.3 Files Transferred to SYS$SHARE Table B-3 lists the shareable image files that the installa- tion procedure transfers to the directory SYS$COMMON:[SYSLIB]. B-2 Files Installed on Your System Table B-3 Shareable Image Files in SYS$COMMON _____________________________________________________________ File_Name_________Purpose____________________________________ VIDAOSHR.EXE The RdbAccess client shareable image. The bulk of the RdbAccess software resides in this shareable image. VIDAOS.EXE The RdbAccess server shareable image created during installation. This image interfaces with the ORACLE RDBMS. RDBSHR.EXE Generic shared image. This image processes all generic calls to a relational database system and routes them to the appropriate product software (for example, routes calls to either the Rdb/VMS product or RdbAccess). RDMMSGSHR.EXE Rdb/VMS shareable message file. This file is a shareable, nonexecutable image of all Rdb/VMS error messages and is used by Rdb/VMS-compatible database __________________products.__________________________________ B.4 Files Transferred to SYS$MESSAGE Table B-4 lists the message files that the installation procedure transfers to the directory SYS$COMMON:[SYSMSG]. Table B-4 Message Files in SYS$COMMON _____________________________________________________________ File_Name_________Purpose____________________________________ VIDAO$MESSAGE.EXE The RdbAccess message file image. This image is activated along with VIDAOSHR and contains the run-time form of the error message text. VIDA2$MESSAGE.EXE VIDA for DB2 message file image. (continued on next page) Files Installed on Your System B-3 Table B-4 (Cont.) Message Files in SYS$COMMON _____________________________________________________________ File_Name_________Purpose____________________________________ VIDA$MESSAGE.EXE VIDA with IDMS/R message file image. RDBMSGS.EXE Generic message file for Rdb/VMS and Rdb /VMS-compatible products. RDMSMSG.EXE Rdb/VMS message file. RDBBMSGS.EXE______Rdb/ELN_message_file.______________________ B-4 Files Installed on Your System B.5 Files Transferred to SYS$COMMON:[SYSTEST] Table B-5 lists the IVP command files that the installation procedure transfers to the system directory SYS$COMMON:[SYSTEST]. Table B-5 IVP Command Files in SYS$TEST:[SYSTEST] _____________________________________________________________ File_Name________Purpose_____________________________________ VIDAO$IVP.COM The RdbAccess IVP command procedure. You can run the IVP command procedure any time after the RdbAccess is installed to verify that the installation procedure installed the RdbAccess software correctly. VIDAO$LIVE_ The RdbAccess live IVP command procedure. IVP.COM You can run the live IVP command procedure to verify that the communications environ- _________________ment_is_correctly_set_up.___________________ Table B-6 lists the IVP command files that the installation procedure transfers to the system directory SYS$TEST:[SYSTEST.VIDAO$IVP]. Table B-6 IVP Command Files in SYS$TEST:[SYSTEST.VIDAO$IVP] _____________________________________________________________ File_Name________Purpose_____________________________________ VIDAO$IDENT.COM VIDAO command procedure for the current RdbAccess version number. VIDAO$LIVE_ Live IVP benchmark file. IVP.BMK When VIDAO$LIVE_IVP.COM is run, the procedure's result file is compared with this benchmark file. Any differences between the files are reported in VIDAO$LIVE_ IVP.RES. VIDAO_CATV5.SQL For ORACLE V5, defines the views that RdbAccess uses to access ORACLE files. (continued on next page) Files Installed on Your System B-5 Table B-6 (Cont.) IVP Command Files in SYS$TEST:[SYSTEST.VIDAO$IVP] _____________________________________________________________ File_Name________Purpose_____________________________________ VIDAO_CATV6.SQL For ORACLE V6, defines the views that _________________RdbAccess_uses_to_access_ORACLE_files.______ B-6 Files Installed on Your System B.6 Files Transferred to SYS$MANAGER Table B-7 lists the command files that the installation procedure transfers to the directory SYS$MANAGER. Table B-7 Command Files in SYS$MANAGER _____________________________________________________________ File_Name__________________Purpose___________________________ RDBSERVER_NCP.COM Command procedure for RDB server process. The command procedure inserts RDBSERVER objects into the DECnet object database for the node from which it is executed. VAXINFO$NETOBJ_INSERT.COM Command procedure. The command procedure inserts ___________________________objects_into_DECnet_databases.____ B.7 List of Product Files Table B-8 lists the product files that the installation pro- cedure transfers to the directory named SYS$COMMON:[SYSMGR.VAXINFO$PRODUCTS]. Table B-8 Product Files _____________________________________________________________ File_Name______Purpose_______________________________________ VIDAO_ List of all files installed by RdbAccess. FILES.DAT____________________________________________________ Files Installed on Your System B-7