DEC DB Integrator Gateway for_ORACLE[[R]]_for_OpenVMS___________________ Installation and Configuration Guide Part Number: AA-Q2C9B-TE November 1994 This guide describes how install the DEC DB Integrator Gateway for ORACLE software. Revision/Update Information: This is a revised guide and supersedes previous versions. Operating System: OpenVMS VAX OpenVMS AXP Software Version: DEC DB Integrator Gateway for ORACLE Version 3.1 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1994. All rights reserved. The following are trademarks of Digital Equipment Corporation: ACMS, ALL-IN-1, AlphaGeneration, AXP, Bookreader, CDD/Plus, CDD/Repository, CI, DEC, DEC Rdb, DEC TCP/IP, DECdecision, DECdtm, DECforms, DECintact, DECnet, DECnet-DOS, DECplan, DECpresent, DECtp, DECtrace, DECwindows, Digital, HSC, MASSBUS, MicroVAX, OpenVMS, PATHWORKS, RA, Rdb Language Translator, Rdb/VMS, SPM, ULTRIX, UNIBUS, VAX, VAX Ada, VAX BASIC, VAX C, VAX CDD, VAX COBOL, VAX DATATRIEVE, VAX DBMS, VAX DOCUMENT, VAX FMS, VAX FORTRAN, VAX MACRO, VAX Pascal, VAX Performance Advisor, VAX RALLY, VAX Rdb/ELN, VAX RMS, VAX SCAN, VAX 6000, VAX TEAMDATA, VAX Xway, VAXcluster, VAXELN, VAXset, VAXstation, VIDA, VMS, VMScluster, and the DIGITAL logo. The following are third-party trademarks: PostScript is a registered trademark of Adobe Systems Incorporated. Apple is a registered trademark of Apple Computer, Inc. CA-ACF2 is a trademark of Computer Associates International, Inc. Interbase is a registered trademark of Borland International, Inc. Cincom is a registered trademark of Cincom Systems, Inc. SequeLink is a trademark and is licensed by Digital Equipment Corporation, Maynard, Massachusetts, from GnOsIs NV 1990, and TechGnosis Incorporated 1991. TechGnosis is a registered trademark of GnOsIs NV. All rights reserved. HP and HP-UX are registered trademarks of Hewlett-Packard Company. API/SQL, EDA/Link, EDA/SQL, Enterprise Data Access, and Enterprise Data Access/SQL are trademarks of Information Builders, Inc. INFORMIX is a registered trademark of Informix Software, Inc. INGRES is a registered trademark of Ingres Corporation. IBM is a registered trademark of International Business Machines Corporation. DB2, CICS, CICS/ESA, CICS/MVS, MVS/ESA, MVS/XA, RACF, and VTAM are trademarks of International Business Machines Corporation. ACCESS, Microsoft, MS, and MS-DOS are registered trademarks of Microsoft Corporation. Windows is a trademark of Microsoft Corporation. OSF and OSF/1 are registered trademarks of the Open Software Foundation, Inc. ORACLE, SQL*Net, and SQL*Plus are registered trademarks of the Oracle Corporation. Pro*C is a trademark of Oracle Corporation. Powersoft is a registered trademark of Powersoft Corporation. PowerBuilder is a trademark of Powersoft Corporation. PROGRESS is a registered trademark of Progress Software Corp. GemBase is a registered trademark of Ross Systems. SmartStar is a registered trademark of SmartStar Corporation. ADABAS is a registered trademark of Software AG of North America, Inc. SYBASE is a registered trademark of Sybase, Inc. DB-Library, Open Client, SYBASE Open Server, and SYBASE SQL Server are trademarks of Sybase, Inc. UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Ltd. All other trademarks and registered trademarks are the property of their respective holders. This document is available on CD-ROM. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Send Us Your Comments.................................... vii Preface.................................................. xi 1 Configuring DEC DB Integrator Gateway for ORACLE 1.1 Components of a Gateway System............... 1-1 1.1.1 User Interface........................... 1-2 1.1.2 Rdb/Dispatch Interface................... 1-2 1.1.3 Gateway for ORACLE....................... 1-3 1.1.4 SQL*Net or the OpenVMS Mailbox Driver.... 1-3 1.1.5 ORACLE RDBMS............................. 1-3 1.2 Possible Configurations for Access to ORACLE Data......................................... 1-3 1.2.1 Local Access............................. 1-4 1.2.2 Network Access........................... 1-4 1.2.3 Remote Access............................ 1-6 1.2.4 Accessing Multiple ORACLE Instances...... 1-7 1.3 Coordination with the ORACLE System.......... 1-8 1.3.1 Gateway Coordinator...................... 1-9 1.3.2 ORACLE Database Administrator............ 1-9 1.4 OpenVMS System Setup......................... 1-10 2 Preparing for DEC DB Integrator Gateway for ORACLE Installation 2.1 License Registration......................... 2-1 2.2 Prerequisite Hardware........................ 2-2 2.3 Prerequisite and Optional Software........... 2-2 iii 2.3.1 Common Components Installation Requirement.............................. 2-3 2.3.1.1 Why You Must Install Common Components............................. 2-4 2.3.1.2 Checking for Common Components......... 2-4 2.4 Installation Procedure Requirements.......... 2-5 2.4.1 Privileges and Disk Space................ 2-5 2.4.2 System Parameters........................ 2-7 2.4.2.1 System Parameters Required............. 2-7 2.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS............................ 2-9 2.4.2.3 Changing System Parameter Values with AUTOGEN................................ 2-9 2.4.3 VMSINSTAL Requirements................... 2-11 2.4.4 System Disk Backup....................... 2-12 3 Installing DEC DB Integrator Gateway for ORACLE 3.1 Access to Online Release Notes and Installation Guide........................... 3-1 3.2 Location of ORACLE Software Libraries........ 3-2 3.3 Installation Procedure....................... 3-2 3.3.1 Invoking VMSINSTAL....................... 3-3 3.3.2 Steps of the Installation Procedure...... 3-5 3.4 Error Recovery............................... 3-12 4 After Installing DEC DB Integrator Gateway for ORACLE 4.1 Running the Installation Verification Procedure.................................... 4-1 4.1.1 Invoking the IVP......................... 4-2 4.1.2 Sample IVP Log........................... 4-2 4.2 Editing the System Startup Files............. 4-3 4.3 Editing the System Shutdown File............. 4-4 4.4 Determining User Account Privileges.......... 4-4 4.5 Installing Licenses on All Nodes in a VMScluster................................... 4-4 4.6 Setting Up the SQL*Net Connection............ 4-5 4.7 Using the OpenVMS Mailbox Driver............. 4-7 4.8 Linking the Gateway Image.................... 4-8 4.8.1 Determining the Cause of a Link Failure.................................. 4-9 4.8.2 Relinking the Gateway Image.............. 4-10 iv 4.8.3 Running the Startup Command File......... 4-10 4.9 Determining and Reporting Problems........... 4-10 A Prerequisite Installation of Common Components A.1 Common Components............................ A-1 A.1.1 Media Required........................... A-2 A.1.2 Version Variants and Existing Databases................................ A-2 A.2 Disk Space Required.......................... A-3 A.3 OpenVMS Privileges Required.................. A-3 A.4 Unlocking the Process Account Password....... A-5 A.5 Installing Common Components................. A-6 A.6 Installing Common Components Images as Shared....................................... A-8 A.6.1 Editing the Startup and Shutdown Procedures for Shared Images............. A-10 A.6.2 Verifying Global Pages and Sections...... A-12 A.6.3 Removing Installed Images................ A-14 A.7 Installing SQL Images for Privileged Applications................................. A-17 A.7.1 Editing the Startup and Shutdown Procedures for Privileged Applications... A-18 A.8 Using Different Versions of the Common Components................................... A-19 A.9 Deleting Versions of the Common Components... A-21 B Sample Installation C Files and Logical Names Installed on Your System C.1 File Names................................... C-1 C.2 Logical Name................................. C-2 D How to Order Additional Documentation v Index Examples 1-1 Attaching to Two ORACLE Instances........ 1-7 Figures 1-1 Components of the ORACLE Gateway System................................... 1-2 1-2 Local Access to an ORACLE Database....... 1-4 1-3 Network Access to an ORACLE Database..... 1-5 1-4 Remote Access to an ORACLE Database...... 1-6 Tables 2-1 Disk Space Requirements.................. 2-6 2-2 Minimum Required System Parameter Values................................... 2-7 A-1 Global Pages and Sections Required for Common Components OpenVMS VAX Images .... A-13 A-2 Global Pagelets and Sections Required for Common Components OpenVMS AXP Images .... A-14 vi ________________________________________________________________ Send Us Your Comments We welcome your comments on this manual or any DEC DB Integrator product manual. If you have suggestions for improvement or find any errors, please indicate the chapter, section, and page number (if available). Your input is valuable in improving future releases of our documentation. You can send comments to us in the following ways: o Electronic mail - DATABASE_DOC@WEORG.ENET.DEC.COM o FAX - 603-881-0120 Attn: DBI Documentation o Postal service Digital Equipment Corporation DEC DB Integrator Products Documentation 110 Spit Brook Road, ZKO2-1/R34 Nashua, NH 03062-2698 USA You can use the following questionnaire to give us information. vii Name _____________________________Title_______________________ Company __________________________Department ________________ Mailing Address __________________Telephone_Number __________ ________________________________________________________________________ Book Title _______________________Version_Number ____________ viii 1. How does the DBI documentation compare to documentation from other vendors that you have used? What do you like about other vendors' documentation that you would like the DBI documentation to implement? 2. What other topics or examples would you like to see included in this documentation set? 3. Do you use the online help for the DBI products? Are there other topics you would like to see included in the online help? 4. Interviews, telephone surveys, user observation, questionnaires, and other similar activities help us to improve our documentation. May we contact you about participating in future efforts? 5. If you have suggestions for improving particular sections or find any errors, please indicate the title of the manual and include the section number. 6. Please include any other comments or suggestions you have. ix ________________________________________________________________ Preface DEC DB Integrator Gateway for ORACLE allows you to access data stored in ORACLE databases from SQL or SQL-based applications. This guide describes how to install DEC DB Integrator Gateway for ORACLE on an OpenVMS VAX or OpenVMS AXP system. Who Should Use This Guide This guide is intended for system managers or others who are responsible for preparing for installing the DEC DB Integrator Gateway for ORACLE software. Structure of This Guide This guide contains the following chapters and appendixes: Chapter 1 Describes the DEC DB Integrator Gateway for ORACLE configuration. Chapter 2 Describes preparations you must make before installing the software. Chapter 3 Describes how to install the software. Chapter 4 Describes any tasks you must perform after installing the software. Appendix A Describes how to install the Common Components software, which must be installed if you do not have DEC Rdb installed. Appendix B Contains a sample installation. Appendix C Lists the files installed by DEC DB Integrator Gateway for ORACLE. xi Appendix D Describes how to order additional documenta- tion from Digital Equipment Corporation. Conventions In examples, an implied carriage return occurs at the end of each line, unless otherwise noted. You must press the Return key at the end of each input line. Often in examples, the prompts are not shown. Generally, they are shown where it is important to depict an interactive sequence exactly; otherwise, they are omitted in order to focus full attention on the statements or commands themselves. This section explains the conventions used in this guide: . . . Horizontal ellipsis points in statements or commands mean that parts of the statement or command not directly related to the example have been omitted. . Vertical ellipsis points in an example mean . that information not directly related to the . example has been omitted. italic Italic text indicates emphasis and complete text manual titles. boldface Boldface text indicates the first instance of text terms defined in the text. In online versions, bold is used to show user input. UPPERCASE Uppercase text indicates the name of an SQL TEXT statement or an SQL logical name. lowercase Lowercase text indicates an operating system text command or the name of a file. input entered by the user. DBADM References to DBADM, unless specifically qualified, refer to that database privilege having been granted or received either with or without the WITH GRANT OPTION clause. xii monospaced Monospaced text indicates example programs and text examples of user interfaces. $ Dollar signs represent the default DIGITAL Command Language (DCL) prompt. This symbol indicates that the system is ready for input. The OpenVMS icon denotes the beginning of information specific to the OpenVMS VAX and OpenVMS AXP operating systems. The DEC OSF/1 icon denotes the beginning of information specific to the DEC OSF/1 AXP operating system. The VAX icon denotes the beginning of information specific to the OpenVMS VAX operating system. The AXP icon denotes the beginning of information specific to the OpenVMS AXP operating system. The diamond symbol (<>) denotes the end of information specific to an operating system. For More Information This section describes where to find information about the DEC DB Integrator product family, RdbAccess products, and SQL. For each of the products listed in the section, the following information is available: o Before You Install Lists hardware and software required to install the product. o Software Product Description (SPD) Provides information on the compatibility of other software products. Use the SPD to verify which versions of your operating system are compatible with which versions of the DEC DB Integrator (DBI) product family software. o Release Notes Provide information about a specific release of the product. Available in online format only. xiii DEC DB Integrator Product Family Information Information about the DEC DB Integrator product family is available in the following manuals: o DEC DB Integrator Product Family User's Guide Describes how to use the DBI Gateway software and DEC DB Integrator software to access and integrate data stored in relational and nonrelational databases. o DEC DB Integrator Handbook Describes how to use DEC DB Integrator to set up and maintain a multidatabase management system. The system provides the capability to access and update data stored in multiple databases, in distributed locations, and with multiple data formats. o DEC DB Integrator for OpenVMS Installation Guide Provides detailed software installation instructions for hardware systems that support DEC DB Integrator on OpenVMS VAX and OpenVMS AXP operating systems. Also provides detailed information about the hardware, operating system versions, and software packages that are compatible with this version of DBI. o DEC DB Integrator Gateway installation and configura- tion guides for the following gateway products: - DEC DB Integrator Gateway for DB2 - DEC DB Integrator Gateway for DSM - DEC DB Integrator Gateway for EDA/SQL - DEC DB Integrator Gateway for ORACLE - DEC DB Integrator Gateway for SequeLink - DEC DB Integrator Gateway for SYBASE o DEC DB Integrator Gateway for DBMS Accessing DEC DBMS Data with SQL Describes how to use the DEC DBMS data driver with the Non-SQL Data Server to access DEC DBMS data. o DEC DB Integrator Gateway for RMS Accessing RMS and VSAM Files with SQL xiv Describes how to use the RMS data driver with the Non- SQL Data Server to access nonrelational files. o Accessing Nonrelational Data with SQL Describes how to use SQL with the Non-SQL Data Server to access nonrelational files. o DEC DB Integrator Gateway for Custom Drivers Driver Development Guide Describes how to write data and metadata drivers to handle data and metadata sources that are not explicitly supported by DEC DB Integrator Gateway for RMS. o DEC DB Integrator Gateway for Custom Drivers/DEC DB Integrator Gateway for RMS Installation Guide Describes how to install and maintain DEC DB Integrator Gateway for Custom Drivers and DEC DB Integrator Gateway for RMS software on the OpenVMS operating system. RdbAccess Information Information about RdbAccess products is available from the following guides: ________________________Note ________________________ The following guides have been superseded by the corresponding DEC DB Integrator Gateway guides. The information is provided for the benefit of users who have not upgraded their RdbAccess software products. _____________________________________________________ o DEC RdbAccess Client for DB2 User's Guide o DEC RdbAccess Server for DB2 Installation and Administration Guide o DEC RdbAccess Client for DB2 Installation Guide o DEC RdbAccess for ORACLE User's Guide o DEC RdbAccess for ORACLE Installation Guide xv SQL Information Information about SQL is available in the following manuals: o DEC Rdb SQL Reference Manual Provides reference material and a complete description of the statements, the interactive, dynamic, and module language interfaces, and the syntax for SQL. o DEC Rdb Introduction to SQL Introduces the interactive and programming components of ANSI/ISO SQL and presents a tutorial of the SQL language elements for designing, creating, modifying, and retrieving data through interactive SQL. o DEC Rdb Guide to SQL Programming Describes how to write database application programs that use ANSI/ISO SQL. o DEC Rdb Guide to Distributed Transactions Describes the two-phase commit protocol and distributed transactions, and explains how to use DEC Rdb with distributed transactions. References to Products The DBI documentation set often refers to the following Digital products by their abbreviated names: o The CDD/Repository for OpenVMS AXP and CDD/Repository for OpenVMS VAX products are referred to as CDD/Repository, the data dictionary, dictionary, or, more commonly, repository. o The DEC Data Distributor for OpenVMS AXP and DEC Data Distributor for OpenVMS VAX products are referred to as Data Distributor. o The DEC DATATRIEVE for OpenVMS AXP and DEC DATATRIEVE for OpenVMS VAX products are referred to as DATATRIEVE. o The DEC DB Integrator product is referred to as DBI. It is available on the OpenVMS AXP, OpenVMS VAX, and DEC OSF/1 AXP systems. xvi o The DEC DB Integrator Gateway for DB2, DEC DB Integrator Gateway for EDA/SQL, DEC DB Integrator Gateway for ORACLE, DEC DB Integrator Gateway for SequeLink, and DEC DB Integrator Gateway for SYBASE, products are referred to as the relational gateways. o The DEC DB Integrator Gateway for Custom Drivers, DEC DB Integrator Gateway for DBMS, DEC DB Integrator Gateway for DSM, and DEC DB Integrator Gateway for RMS products are referred to as the nonrelational gateways. o The DEC DB Integrator Gateway family of data access products is often referred to as DBI Gateway. The DEC DB Integrator Gateway family is made up of the following products. Each product is often referred to as the gateway for [identifying product name]. For example, the DEC DB Integrator Gateway for Custom Drivers is often referred to as the gateway for Custom Drivers. - DEC DB Integrator Gateway for Custom Drivers[1] - DEC DB Integrator Gateway for DB2 Client[1], [2] - DEC DB Integrator Gateway for DB2 Server[3] - DEC DB Integrator Gateway for DBMS[1] - DEC DB Integrator Gateway for DSM[1] - DEC DB Integrator Gateway for EDA/SQL[1], [2] - DEC DB Integrator Gateway for ORACLE[1], [2] - DEC DB Integrator Gateway for RMS[1] - DEC DB Integrator Gateway for SequeLink[1], [2] - DEC DB Integrator Gateway for SYBASE[1], [2] o The DEC RdbExpert for OpenVMS AXP and DEC RdbExpert for OpenVMS VAX products are referred to as RdbExpert. ___________________ [1]This product is available on the OpenVMS AXP and OpenVMS VAX systems. [2]This product is available on the DEC OSF/1 AXP system. [3]This product is only available on the IBM system. xvii o The Digital gateways to SNA networks are referred to as the DEC SNA gateway products. These products include: - OpenVMS SNA - DECnet SNA Gateway for Channel Transport - DECnet SNA Gateway for Synchronous Transport - DEC SNA Domain Gateway - DEC SNA Peer Server o The DECnet/SNA Data Transfer Facility product is referred to as DTF. o The DECtrace for OpenVMS AXP and DECtrace for OpenVMS VAX products are referred to as DECtrace. o The DEC Rdb for OpenVMS AXP and DEC Rdb for OpenVMS VAX products are both referred to as DEC Rdb. Prior to DEC Rdb Version 5.0, this product was called VAX Rdb/VMS. o The OpenVMS RMS (Record Management Services) product is referred to as RMS. o SQL refers to the SQL interface to DEC Rdb and to the DBI family of products. SQL is Digital Equipment Corporation's implementation of the SQL standard ANSI X3.135-1992, ISO 9075:1992, commonly referred to as ANSI/ISO SQL. xviii 1 ________________________________________________________________ Configuring DEC DB Integrator Gateway for ORACLE DEC DB Integrator Gateway for ORACLE enables Digital OpenVMS users to have read/write access to data stored in ORACLE databases. Programmers and end users can use one of many Digital or third-party tools with the gateway to access the ORACLE data. The gateway for ORACLE works with SQL*Net or the OpenVMS Mailbox Driver to provide access to data. This chapter describes how the gateway for ORACLE works and describes what you must do to configure the gateway for ORACLE. 1.1 Components of a Gateway System The following software products or components are needed to obtain access to ORACLE data. o User interface, which can be a Digital or third-party product o Rdb/Dispatch, which is provided with DEC Rdb or Common Components (you must have DEC Rdb or Common Components installed to use the gateway for ORACLE) o Gateway for ORACLE o For network access: SQL*Net o For local access: OpenVMS Mailbox Driver o ORACLE relational database management system (RDBMS) Figure 1-1 shows the components of a gateway system. Configuring DEC DB Integrator Gateway for ORACLE 1-1 Figure 1-1 Components of the ORACLE Gateway System The following sections describe the function of each of these components. Section 1.2 describes the possible configurations of these components. 1.1.1 User Interface Users or programmers can use any of the supported Digital tools, such as SQL, or third-party tools described in the DEC DB Integrator Product Family User's Guide. These tools are installed separately from the gateway for ORACLE. With any user interface, users provide a set of attach specification qualifiers that determine what database is accessed and how the database is accessed. The qualifiers are described in the DEC DB Integrator Product Family User's Guide. The user interface provides the means for a user to submit a request, which is passed to Rdb/Dispatch. The user interface also returns responses from Rdb/Dispatch to the user. 1.1.2 Rdb/Dispatch Interface All data requests made from user interfaces are routed through Rdb/Dispatch. Rdb/Dispatch processes these requests and sends them to the DEC DB Integrator (DBI) engine for further processing. When the DBI engine returns a response, Rdb/Dispatch sends that response back to the user interface. Rdb/Dispatch is installed as part of the DEC Rdb installation, or as part of the Common Components installation. You must have DEC Rdb or Common Components installed to use the gateway for ORACLE. Appendix A describes how to install Common Components. 1-2 Configuring DEC DB Integrator Gateway for ORACLE 1.1.3 Gateway for ORACLE The gateway for ORACLE contains a component called the DBI engine. The DBI engine receives the request from Rdb/Dispatch and optimizes it before sending the request to the gateway for ORACLE. The gateway for ORACLE receives the request from the DBI engine and translates it to a request that the ORACLE RDBMS can understand. It then passes the request to the ORACLE RDBMS through SQL*Net or the OpenVMS Mailbox Driver. When a response is returned from the ORACLE RDBMS, it is passed back through the gateway to the user interface. 1.1.4 SQL*Net or the OpenVMS Mailbox Driver The ORACLE SQL*Net product provides access to remote ORACLE databases on the network from the gateway for ORACLE. If SQL*Net is not installed, you can only access local databases and must do so using the OpenVMS Mailbox Driver, which is part of the ORACLE RDBMS software. If you are using the OpenVMS Mailbox Driver, the user command file, which is supplied by ORACLE, must be executed. 1.1.5 ORACLE RDBMS The ORACLE RDBMS software includes the ORACLE server and is the source of the data being accessed. It also includes the OpenVMS Mailbox Driver, which allows the gateway for ORACLE to communicate with the ORACLE RDBMS. 1.2 Possible Configurations for Access to ORACLE Data The following sections describe the possible configura- tions for data access. In each section, a sample attach specification is provided. For more information about the qualifiers in the attach specification, refer to the DEC DB Integrator Product Family User's Guide. Configuring DEC DB Integrator Gateway for ORACLE 1-3 1.2.1 Local Access In local access, all the components in the gateway system are located on the same node, as shown in Figure 1-2. You can use the OpenVMS Mailbox Driver to access the ORACLE RDBMS. Figure 1-2 Local Access to an ORACLE Database The following attach specification attaches to a local ORACLE RDBMS: SQL> ATTACH 'FILENAME/TYPE=ORACLE/NODE=2:/USER=MAUSER' The NODE qualifier in the attach specification corresponds to an ORACLE SQL*Net connect string. A value of 2: indicates that you are using the OpenVMS Mailbox Driver to attach to the ORACLE RDBMS. 1.2.2 Network Access The OpenVMS Mailbox Driver is only used for local access. If you need to access an ORACLE RDBMS that is on a different node than the gateway for ORACLE, you must use a SQL*Net connection. The SQL*Net client software must be installed before you install the gateway for ORACLE. In network access, the user interface, Rdb/Dispatch, the gateway for ORACLE, and the SQL*Net client are on one node, and the SQL*Net server and ORACLE database are on a different node. The SQL*Net client and the SQL*Net server communicate through a DECnet or TCP/IP connection, as shown in Figure 1-3. 1-4 Configuring DEC DB Integrator Gateway for ORACLE Figure 1-3 Network Access to an ORACLE Database The network driver you configured with SQL*Net determines the network protocol linked with the gateway for ORACLE. Refer to the SQL*Net documentation for specific information on selecting SQL*Net drivers and configuring SQL*Net on your system. The following attach specification attaches to an ORACLE server across the network: SQL> ATTACH 'FILENAME/TYPE=ORACLE/USER=BURKE- cont> /NODE=D:TROUPE"""ORACLE PASSWORD"""::"""TASK=ORDNDFLT"""'; The NODE qualifier in the attach specification corresponds to an ORACLE SQL*Net connect string. In the previous attach specification, the NODE qualifier includes the following pieces: o The D: prefix indicates that DECnet is used as the network transport (a prefix of T: indicates that TCP/IP is used as the network transport). o The string TROUPE"""ORACLE PASSWORD""":: consists of the following pieces: - TROUPE is the ORACLE server node name. - ORACLE is the name of the system account used to log into the system where the ORACLE RDBMS resides. - PASSWORD is the password of the system account used to log into the system where the ORACLE RDBMS resides. o """TASK=ORDNDFLT""" is the DECnet task and associated ORACLE SQL*Net server startup command file. Configuring DEC DB Integrator Gateway for ORACLE 1-5 1.2.3 Remote Access In remote access, the user interface and Rdb/Dispatch are located on a node remote from the system where Rdb/Dispatch, the gateway for ORACLE, and SQL*Net are installed. The user interface uses the local Rdb/Dispatch software to communicate with the remote Rdb/Dispatch software on the system where the gateway and other components are installed, as shown in Figure 1-4. Figure 1-4 Remote Access to an ORACLE Database For remote access, the user must provide, in the attach specification, the name of the remote node on which the gateway for ORACLE is running. In the following example, the gateway for ORACLE is running on the node named SEESAW: SQL> ATTACH 'FILENAME SEESAW::/TYPE=ORACLE/USER=CJONES- cont> /NODE=D:NASHUA-DBS'; The NODE qualifier in the attach specification corresponds to an ORACLE connect string. In the previous attach specification, the NODE qualifier includes the following pieces: o The D: prefix indicates that DECnet is used as the network transport. o NASHUA is the ORACLE server node name. ORDNDBS is the DECnet object. -DBS is the ORACLE short form of DECnet object identification, which can be used if the first four letters of the DECnet object name are ORDN. Refer to the SQL*Net documentation for information about setting up the ORACLE short form of DECnet object identification. 1-6 Configuring DEC DB Integrator Gateway for ORACLE 1.2.4 Accessing Multiple ORACLE Instances It is possible for two ORACLE RDBMSs to be resident on the same AXP or VAX computer. You can specify which database you want to access by using a different network object. See the SQL*Net documentation for information on setting up connections for multiple instances. Although multiple ORACLE databases can be resident on one computer, users of the gateway for ORACLE can access only one ORACLE database per request. However, the gateway for ORACLE supports up to five multiple attachments to ORACLE. Example 1-1 shows two attachments. Example 1-1 Attaching to Two ORACLE Instances SQL> ATTACH 'ALIAS ATTACH1 FILENAME/TYPE=ORACLE/USER=CJONES- cont> /NODE=D:TROUPE-DFLT'; SQL> ATTACH 'ALIAS ATTACH2 FILENAME/TYPE=ORACLE/USER=CJONES- cont> /NODE=D:TROUPE-BROD'; (continued on next page) Configuring DEC DB Integrator Gateway for ORACLE 1-7 Example 1-1 (Cont.) Attaching to Two ORACLE Instances SQL> SHOW TABLES; User tables in database with alias ATTACH1 ATTACH1.COLLEGES ATTACH1.CURRENT_INFO ATTACH1.CURRENT_JOB ATTACH1.CURRENT_SALARY ATTACH1.DEGREES ATTACH1.DEPARTMENTS ATTACH1.EMPLOYEES ATTACH1.JOBS ATTACH1.JOB_HISTORY ATTACH1.SALARY_HISTORY ATTACH1.WORK_STATUS User tables in database with alias ATTACH2 ATTACH2.CARGO ATTACH2.EMPLOYEE ATTACH2.EXPORTER ATTACH2.LAYOVER ATTACH2.MANIFEST ATTACH2.MATCOST ATTACH2.PORT ATTACH2.SHIP ATTACH2.VOYAGE 1.3 Coordination with the ORACLE System Each site should have a gateway coordinator. This person is responsible for managing the gateway for ORACLE software. The gateway coordinator must work with the database administrator (DBA) for the ORACLE database to ensure that gateway users have access to the ORACLE data. The following sections describe the tasks the coordinator and DBA must perform. 1-8 Configuring DEC DB Integrator Gateway for ORACLE 1.3.1 Gateway Coordinator The gateway coordinator must provide information to gateway users about the data gateway users will be accessing and how they will access it. Gateway users need this information so they know which qualifiers to use in an attach specification. The gateway coordinator might have to obtain some of this information from the DBA. The gateway coordinator must tell the gateway users the following: o The ORACLE user name and password used to access the ORACLE data o The names of the ORACLE tables that users will be accessing o If users will be using the OpenVMS Mailbox Driver or TCP/IP or DECnet network transport o On which node the ORACLE server and RDBMS reside o Which instance identifier gateway users will use In addition, the gateway coordinator must know if the proper privileges have been granted to the ORACLE tables for read/write access. The attach specification qualifiers used to access an ORACLE database are described in the DEC DB Integrator Product Family User's Guide. The coordinator must be familiar with these qualifiers in order to provide information to gateway users. 1.3.2 ORACLE Database Administrator The ORACLE DBA maintains the ORACLE database system. The DBA often has the best understanding of the ORACLE database, and can help the gateway coordinator determine which information gateway users will be accessing. The DBA tells the gateway coordinator which ORACLE user name and password will be used to access data. The DBA also knows which tables gateway users will be accessing so he or she can determine if users have the proper ORACLE privileges to access data. Refer to the ORACLE documentation for information about required privileges and granting privileges. Configuring DEC DB Integrator Gateway for ORACLE 1-9 In addition, the DBA must confirm that the SQL*Net configuration is properly set up. Any public synonyms that the DBA defines are available to users of the gateway for ORACLE. When users specify the TABLE qualifier as part of the attach specification, they can use a synonym or a qualified or unqualified table name. 1.4 OpenVMS System Setup Before using the gateway for ORACLE, you must ensure that: o DEC Rdb or Common Components have been installed on the node on which the gateway for ORACLE is installed. o The gateway for ORACLE has been installed. o All post-installation procedures have been performed. o The Installation Verfication Procedure (IVP) has run successfully. o For remote access, SQL*Net is installed and configured properly. Digital recommends that SQL*Net connections be verified by connecting to an ORACLE database using the ORACLE SQL*Plus utility. Every component of the connection string used with SQL*Plus has a corresponding qualifier in the attach specification used to attach to a database through the gateway for ORACLE. The remainder of this guide describes how to install the gateway for ORACLE and Common Components, and how to perform the post-installation procedures and run the IVP. Refer to the ORACLE documentation for information about SQL*Net or the ORACLE RDBMS. 1-10 Configuring DEC DB Integrator Gateway for ORACLE 2 ________________________________________________________________ Preparing for DEC DB Integrator Gateway for ORACLE Installation This chapter discusses the preparations and requirements necessary for installing DEC DB Integrator Gateway for ORACLE. 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 you find that parts of it are missing, contact your Digital representative. The gateway for ORACLE provides online release notes. Digital strongly recommends that you read the release notes before proceeding with the installation. For information on accessing the online release notes, see Section 3.1. 2.1 License Registration Before you install and run the gateway for ORACLE Version 3.1 on a newly licensed node or cluster, you must first register a Product Authorization Key (PAK) using the License Management Facility (LMF). The PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. If you are installing the gateway for ORACLE as an update on a node or cluster already licensed for this software, you have previously completed the PAK registration requirements. If you are installing prerequisite or optional software along with the gateway for ORACLE, review the PAK status and install the PAKs for any prerequisite or optional software before you install the gateway for ORACLE. Preparing for DEC DB Integrator Gateway for ORACLE Installation 2-1 You must register and load your license for the gateway for ORACLE before you can use the software. To register a license under OpenVMS, first log in to the system manager's account, SYSTEM. You then have a choice of two ways to perform the registration: o Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your PAK. o At the DCL prompt, enter the LICENSE REGISTER command with the appropriate qualifiers that correspond to PAK information. If you plan to use the gateway for ORACLE on more than one node in a VMScluster, you will need to load a license on the other nodes after you complete this installation. See Section 4.5 for more information about loading licenses on a cluster. For complete information on using the LMF, see the OpenVMS License Management Utility Manual. 2.2 Prerequisite Hardware The gateway for ORACLE works with all AXP and VAX hardware. 2.3 Prerequisite and Optional Software You must have the following software installed on the same node on which you will install the gateway for ORACLE Version 3.1, and it must be installed before you install the gateway for ORACLE: o For VAX: OpenVMS Version 5.5-2 o For AXP: OpenVMS Version 6.1 o For both VAX and AXP: SQL*Net Version 1.2 for network access o Common Components-refer to Section 2.3.1 for instruc- tions Optionally, you can have DEC DB Integrator Version 3.1 installed and use it with the gateway for ORACLE. 2-2 Preparing for DEC DB Integrator Gateway for ORACLE Installation You must have the following software installed on the system that will be the server system for the ORACLE client: o ORACLE V7 The Software Product Description (SPD) contains a complete list of prerequisite and optional software and their required version numbers. 2.3.1 Common Components Installation Requirement The Common Components are software components that provide relational database functions for several Digital products. The Common Components consist of: o SQL interface o SQL/Services server o Rdb/Dispatch interface and Rdb/Remote server The Common Components are required in order to use the following products: o DEC DB Integrator (DBI) o DEC DB Integrator Gateway products o DEC Rdb DBI requires Common Components in the following ways: o Any process that runs the DBI software or that accesses a DBI logical database, locally or remotely, requires Rdb/Dispatch. For example, if a DBI application is running on a local node and attaches to a DBI logical database on a remote node, both nodes must have Rdb/Dispatch installed. o Creating a DBI logical database requires SQL. A Common Components kit is provided with each product. The Common Components kit is part of the DEC Rdb media kit and the Common Components have the same version number as DEC Rdb. However, you can install the Common Components separately from the other components of DEC Rdb and they do not require a DEC Rdb license. Preparing for DEC DB Integrator Gateway for ORACLE Installation 2-3 2.3.1.1 Why You Must Install Common Components Each product that requires Common Components requires a specific version of Common Components. In the case of DEC Rdb, the product installation automatically includes the Common Components installation. For DBI or a DBI gateway installation, however, you must separately install the Common Components. If the required version of Common Components is not installed on your system, you can install DBI or a DBI gateway, but you cannot successfully use the product. The DBI or gateway installation procedure prints a warning and completes, but the Installation Verification Procedure (IVP) fails. Because each product requires a specific version of Common Components, you may need to have more than one version of Common Components installed on a system at any given time. For example, suppose you want to install DBI on a system running VAX Rdb/VMS Version 4.2 with a critical set of databases and applications. The Version 4.2 Common Components cannot be disturbed. However, to use DBI Version 3.1, you must install Common Components Version 6.0. The solution is to install the multiversion variant of Common Components Version 6.0, as described in Section A.1.2. This variant allows multiple versions of Common Components, or DEC Rdb itself, to coexist on the same system without affecting each other, and does not significantly add to the tasks of system or database administration. 2.3.1.2 Checking for Common Components It is not necessary to install a single version of Common Components more than once per system. Use the following procedure to determine whether or not the correct version of Common Components has already been installed on a system. If Version 6.0 has not been installed, you must perform the procedure described in Appendix A in order to use Version 3.1 of DBI or any DBI gateway product. 2-4 Preparing for DEC DB Integrator Gateway for ORACLE Installation To find out if the Common Components have been installed on your OpenVMS system, enter: $ DIR SYS$LIBRARY:SQL$SETVER.COM If the file SYS$LIBRARY:SQL$SETVER.COM does not exist, you must install Common Components. If the file does exist, enter: $ @SYS$LIBRARY:SQL$SETVER 6.0 If you see any of the following messages, you must install Common Components: %SQL-E-SETVER SQL Version 6.0 does not exist on your system. %SQL-E-SETVER SYS$COMMON:[SYSLIB]SQL$SHR.EXE Image Ident Problem %SQL-E-SETVER IMAGE IDENT = n.n, VERSION = 6.0 The last two messages indicate that standard (nonmul- tiversion) DEC Rdb software has been installed on the system. If you see the following messages, with or without the word MULTIVERSION, Common Components have already been installed. You do not need to install the Common Components software again. Current PROCESS SQL environment is version V6.0-nn (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V6.0-nn (MULTIVERSION) 2.4 Installation Procedure Requirements This section and those that follow discuss various requirements for installing the gateway for ORACLE. The installation takes approximately 5 to 10 minutes. The actual time depends on the type of media, the processor type, and the system configuration. 2.4.1 Privileges and Disk Space To install the gateway for ORACLE, you must be logged in to an account that has the SETPRV privilege or at least the following privileges: o CMKRNL o WORLD Preparing for DEC DB Integrator Gateway for ORACLE Installation 2-5 o SYSPRV The VMSINSTAL procedure turns off the BYPASS privilege at the start of the installation. Table 2-1 summarizes the storage requirements for the gateway for ORACLE during installation and after installation. Table_2-1_Disk_Space_Requirements_________________________ Blocks_During_Installation_Blocks_After_Installation______ _____________________For_AXP_systems______________________ 30,600 29,500 __________________________________________________________ _____________________For_VAX_systems______________________ 31,500_____________________29,500_________________________ To determine the number of available disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 2-6 Preparing for DEC DB Integrator Gateway for ORACLE Installation 2.4.2 System Parameters The following sections discuss system parameters. 2.4.2.1 System Parameters Required Installing the gateway for ORACLE requires certain system parameter settings. Table 2-2 lists the minimum required system parameter values for the installation. Depending on the kinds of programs and applications running at your site, you might need higher values for some settings. Table 2-2 lists some parameters whose units are specified in pages. On OpenVMS AXP systems, the size of a page can differ on different CPUs. Read the values in Table 2-2 as 512-byte pagelets, which are not CPU-specific. Table_2-2_Minimum_Required_System_Parameter_Values________ Image_File______________________GBLPAGES[1]_GBLSECTIONS[1] _____________________For_AXP_systems______________________ SYS$SHARE:LDRV$ORACLE_SHR.EXE 2955 2 SYS$MESSAGE:LDRV_MSG.EXE 28 1 SYS$SHARE:DBI$SHR.EXE 5482 1 SYS$MESSAGE:DBI_MSG.EXE 38 1 Totals:[2] 8503 5 __________________________________________________________ _____________________For_VAX_systems______________________ SYS$SHARE:LDRV$ORACLE_SHR.EXE 1688 1 [1]The_values_listed_for_these_system_parameters_represent the number of available global pages and global sections required for the installation, not the total number you need to run your system and other software. [2]If you already have DEC DB Integrator installed, then you will need enough global pages and sections for both the LDRV$ORACLE_SHR.EXE and LDRV_MSG.EXE images. If you have neither DEC DB Integrator nor any DEC DB Integrator gateway product already installed, then you will need the sum of all four images. (continued on next page) Preparing for DEC DB Integrator Gateway for ORACLE Installation 2-7 Table 2-2 (Cont.) Minimum Required System Parameter __________________Values__________________________________ Image_File______________________GBLPAGES[1]_GBLSECTIONS[1] _____________________For_VAX_systems______________________ SYS$MESSAGE:LDRV_MSG.EXE 28 1 SYS$SHARE:DBI$SHR.EXE 1 2 SYS$MESSAGE:DBI_MSG.EXE 38 1 Totals:[2] 1755 5 [1]The_values_listed_for_these_system_parameters_represent the number of available global pages and global sections required for the installation, not the total number you need to run your system and other software. [2]If you already have DEC DB Integrator installed, then you will need enough global pages and sections for both the LDRV$ORACLE_SHR.EXE and LDRV_MSG.EXE images. If you have neither DEC DB Integrator nor any DEC DB Integrator gateway product already installed, then you will need the sum of all four images. __________________________________________________________ 2-8 Preparing for DEC DB Integrator Gateway for ORACLE Installation The following sections show you how to: o Calculate values for the GBLPAGES and GBLSECTIONS system parameters o Change parameter values with the OpenVMS AUTOGEN utility 2.4.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run the gateway for ORACLE, you must have sufficient available global pages or pagelets and global sections. You must first find out how many available global pages or pagelets and sections you have on your system. Then, use the AUTOGEN utility if you need to increase the GLBPAGES and GBLSECTIONS system parameters. To calculate how many unused global pages and global sections your system has, use the WRITE command with the F$GETSYI lexical function to find the number of available 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 values displayed by the system are greater than the values in Table 2-2, you do not need to increase the values for these parameters. If the values of available global pages or pagelets or global sections are less than the values in Table 2-2, you must increase the system parameter setting. Section 2.4.2.3 describes the procedures for increasing these values using the AUTOGEN utility. 2.4.2.3 Changing System Parameter Values with AUTOGEN Use the AUTOGEN utility to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT Preparing for DEC DB Integrator Gateway for ORACLE Installation 2-9 Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. 2-10 Preparing for DEC DB Integrator Gateway for ORACLE Installation To add a new parameter, add a line to the file that includes both the name of the parameter and its value, for example: WSMAX = 1024 To modify incremental parameters such as GBLPAGES and GBLSECTIONS, use the prefix ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 When you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. After you make all your changes, exit from the editor and execute the AUTOGEN utility to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT When you specify REBOOT, the AUTOGEN utility performs an automatic system shutdown and then restarts (reboots) the system. Any users logged in to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. 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 more information about using AUTOGEN, see the OpenVMS System Management documentation. 2.4.3 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o If you are logged in to a privileged account o If you have adequate quotas for installation o If DECnet is running o If any users are logged in to the system Preparing for DEC DB Integrator Gateway for ORACLE Installation 2-11 If VMSINSTAL detects any problems during the installation, it notifies you and asks if 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 the Return key. Then, correct the problem and restart the installation. 2.4.4 System Disk Backup At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup utility in the OpenVMS System Management documentation. 2-12 Preparing for DEC DB Integrator Gateway for ORACLE Installation 3 ________________________________________________________________ Installing DEC DB Integrator Gateway for ORACLE This chapter explains how to install the gateway for ORACLE. Section 3.3 contains a step-by-step description of the installation procedure. The following topics are discussed: o Accessing the installation guide and release notes o Locating the ORACLE software libraries o The installation procedure 3.1 Access to Online Release Notes and Installation Guide The gateway for ORACLE provides online release notes, DEC DB Integrator Gateway for ORACLE[[R]] 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. 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. After the system installs the gateway for ORACLE, the release notes are in the following files: SYS$HELP:LORA031.RELEASE_NOTES SYS$HELP:LORA031_RELEASE_NOTES.PS Installing DEC DB Integrator Gateway for ORACLE 3-1 During the installation you are also asked if you want to print the DEC DB Integrator Gateway for ORACLE[[R]] for OpenVMS Installation and Configuration Guide. After the system installs the gateway for ORACLE, the installation and configuration guide is available in the following files: SYS$HELP:LORA031.INSTALL_GUIDE SYS$HELP:LORA031_INSTALL_GUIDE.PS 3.2 Location of ORACLE Software Libraries The gateway for ORACLE links with the ORACLE software libraries on your system. The installation procedure will ask you where these libraries are located. The installation procedure will ask you for the name and location of the ORAUSER command file on your system. The ORAUSER command file defines all the process logical names that are needed for ORACLE or ORACLE SQL*Net users. ________________________Note ________________________ This file name may have been changed on your system. Ask your ORACLE database administrator (DBA) or ORACLE SQL*Net installer for the name and location of the ORACLE user command file prior to installation. _____________________________________________________ 3.3 Installation Procedure The gateway for ORACLE installation procedure consists of a series of questions and informational messages. See Appendix B for a sample installation. To abort the installation procedure at any time, press the Ctrl/Y keys. When you press Ctrl/Y, the installation procedure deletes all files it has created up to that point and exits. You can then start the installation again. 3-2 Installing DEC DB Integrator Gateway for ORACLE Before invoking VMSINSTAL, mount the media (for VAX installations) or place the CD-ROM media into the CD-ROM drive (for AXP installations). When the system prompts you with a question during the installation, the default answer, if there is one, is listed in brackets ([]). 3.3.1 Invoking VMSINSTAL Before invoking VMSINSTAL, log in to a privileged account and set your default device and directory to SYS$UPDATE. The VMSINSTAL procedure is located in SYS$UPDATE. To invoke VMSINSTAL use the following command: @VMSINSTAL saveset-name device-name OPTIONS N If you do not specify the parameters to the VMSINSTAL com- mand, you are prompted for them during the installation. The parameters to the VMSINSTAL command are as follows: saveset-name The installation name for the component. For the gateway for ORACLE, use the following installation name: LORA031 device-name The name of the device on which you plan to mount the media. o If the device is a magnetic tape drive, you need to specify only the device name, such as MTA0:. o If the device is a disk drive, such as a CD-ROM reader, you also need to specify a directory. For CD-ROM distribution, the directory name is the same as the saveset name, for example: DKA400:[LORA031.KIT] For AXP installations, to determine the directory location of the gateway for ORACLE save set on the CD-ROM, see the OpenVMS AXP Layered Products Compact Disc User's Guide booklet that accompanies the CD-ROM distribution kit. Installing DEC DB Integrator Gateway for ORACLE 3-3 OPTIONS N An optional parameter that indicates you want to see the question on release notes. 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 additional information about the installation. If you are restarting the installation and have already reviewed the release notes, you do not need to specify OPTIONS N. Whether or not you specify OPTION N, the VMSINSTAL procedure copies the release notes to the SYS$HELP directory. There are several other options you can select when you invoke VMSINSTAL. If you specify more than one option, separate the options with commas (OPTIONS A,N). o Auto_answer option (A): Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). o Get saveset option (G): Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L): Logs all activity to the terminal during installation. o Alternate root option (R): Lets you install the product to a system root other than that of the operating system. This option makes it possible to test a new product without disturbing the operating system. See the OpenVMS operating system documentation for detailed information on these options. The following example invokes VMSINSTAL to install the gateway for ORACLE from directory DKA400:[LORA031.KIT] and shows the system response. This example uses the OPTIONS N release notes parameter. The example is a sample installation on an AXP system. An installation on a VAX system would be similar. 3-4 Installing DEC DB Integrator Gateway for ORACLE $ @SYS$UPDATE:VMSINSTAL LORA031 DKA400:[LORA031.KIT] OPTIONS N OpenVMS ALPHA Software Product Installation Procedure V1.5 It is 17-JAN-1994 at 14:53. 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. The VMSINSTAL procedure does not prompt you for any options, so be sure to include OPTIONS N on the VMSINSTAL command line to access the release notes during the installation. 3.3.2 Steps of the Installation Procedure The following steps describe the installation procedure: 1. Note processes that are still running. %VMSINSTAL-W-ACTIVE, The following processes are still active: SQLSRV$SERVER _RTA3: * Do you want to continue anyway [NO]? YES The installation procedure notes which processes are still active and asks if you want to continue. 2. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? 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 restart the installation. 3. Mount the media. Installing DEC DB Integrator Gateway for ORACLE 3-5 The following products will be processed: LORA V3.1 Beginning installation of LORA V3.1 at 14:53 %VMSINSTAL-I-RESTORE, Restoring product save set A... You should now mount the first media volume on the device you specified when you invoked VMSINSTAL. The VMSINSTAL procedure confirms which products will be installed. 4. Select a release notes option. If you specified OPTIONS N when you started the installation, VMSINSTAL asks a question on release notes. You have four options for handling the release notes. 3-6 Installing DEC DB Integrator Gateway for ORACLE You see the following display: 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 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: * Queue name [SYS$PRINT]: You can press the Return key 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 terminal and then prompts you for a queue name for the printed version. Select option 4 if you have already reviewed the release notes and are restarting the installation. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press the Return key. In either case, the release notes are copied to the following files in the SYS$HELP directory: Installing DEC DB Integrator Gateway for ORACLE 3-7 SYS$HELP:LORA031.RELEASE_NOTES SYS$HELP:LORA031_RELEASE_NOTES.PS ________________________Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product facility code (LORA) and version number (031). _____________________________________________________ 5. Note the copyright notice. ************************************************************** The installation procedure for DEC DB Integrator Gateway for ORACLE V3.1-00 for OpenVMS AXP © Digital Equipment Corporation 1994. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ************************************************************** 6. Print the installation guide. * Would you like to print the LORA installation guide [NO]? If you want to print the installation guide, answer YES to this question. If you answer YES and you want to use a print queue other SYS$PRINT for printing the installation guide, enter the queue name after the following prompt: * Enter the printer queue name [SYS$PRINT]: * Do you want to continue? [YES]: Y To continue the installation, enter YES or press the Return key. In either case, the installation guide 3-8 Installing DEC DB Integrator Gateway for ORACLE is copied to the following files in the SYS$HELP directory: SYS$HELP:LORA031.INSTALL_GUIDE SYS$HELP:LORA031_INSTALL_GUIDE.PS 7. Respond to license registration queries. Product: DB-GATEWAY-ORACLE Producer: DEC Version: 3.1 Release Date: 01-SEP-1994 * Does this product have an authorization key registered and loaded? Y The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAK to successfully complete the installation. If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. 8. Enter the name of the ORACLE user command procedure. Please enter the name and location of the Oracle user command procedure. For example, ORA_ROOT:[UTIL]ORAUSER.COM. It will be necessary to invoke this command procedure in order to define logical names pointing to the Oracle libraries. These libraries are required in order to link the DEC DB Integrator Gateway for Oracle driver. If you are unsure of the name and location of this command procedure ask your ORACLE database administrator (DBA) or ORACLE SQL*Net installer. * Enter the name of the ORACLE user command file: DSK:[ORACLE7.UTIL]ORAUSER.COM 9. Purge files. * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous versions of the product. Digital recommends that you save files. Enter NO in response to the question to save previous versions of files. 10.Read messages. Installing DEC DB Integrator Gateway for ORACLE 3-9 At this point, the installation procedure displays a number of messages that report on the progress of the installation. One of the messages indicates that because the IVP is interactive, it is not run during installation. However, you can run the IVP after installation by executing the file @SYS$TEST:LORA$IVP. There are no further questions in the installation procedure. 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 chose to have files purged, that work is done now. The following messages are displayed: ************************************************************** There are no more questions. The installation takes approximately 5 to 10 minutes depending on the processor type. Because the Installation Verification Procedure is interactive, it will not be run as part of the installation. You may run the IVP separately any time you wish. To execute it, type: $ @SYS$TEST:LORA$IVP ************************************************************** ************************************************************** Beginning installation of DEC DB Integrator Gateway for ORACLE V3.1-00 ************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... %LORA-I-LNKGWYSHR, linking LDRV$ORACLE_SHR gateway shareable image... - Linking LDRV$ORACLE_SHR.EXE ************************************************************** LORA$STARTUP.COM has been placed in SYS$STARTUP. The following line should be place in your system startup file. $ @SYS$STARTUP:LORA$STARTUP.COM ************************************************************** 3-10 Installing DEC DB Integrator Gateway for ORACLE ************************************************************** LORA$SHUTDOWN.COM has been placed in SYS$MANAGER. The following line should be place in your system shutdown file. $ @SYS$MANAGER:LORA$SHUTDOWN.COM ************************************************************** ************************************************************** The IVP has been placed in SYS$TEST. You may run this procedure separately any time you wish. To execute it type: $ @SYS$TEST:LORA$IVP.COM ************************************************************** ************************************************************** Finishing installation of DEC DB Integrator Gateway for ORACLE V3.1-00 ************************************************************** %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of LORA V3.1 completed at 14:56 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]LORA031.VMI_DATA VMSINSTAL procedure done at 14:56 The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 17-JAN-1994 14:56:41.22 The VMSINSTAL procedure 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 must log out and log in again. Installing DEC DB Integrator Gateway for ORACLE 3-11 3.4 Error Recovery If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message followed by more information: %VMSINSTAL-E-CANT-INSTALL, Error installing LORA. The installation failed for the following reasons: Errors can occur during the installation if any of the following conditions exists: o The operating system version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The OpenVMS Help Library is currently in use. For descriptions of the error messages generated by these conditions, see the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. If you are notified that any of these conditions exists, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 2. 3-12 Installing DEC DB Integrator Gateway for ORACLE 4 ________________________________________________________________ After Installing DEC DB Integrator Gateway for ORACLE The following tasks take place after installing DEC DB Integrator Gateway for ORACLE: o Running the Installation Verification Procedure o Editing the system startup and shutdown files o Ensuring users have sufficient privileges o Installing licenses on all nodes in a cluster o Setting up SQL*Net o Using the OpenVMS Mailbox Driver o Linking the gateway image o Reporting problems 4.1 Running the Installation Verification Procedure The Installation Verification Procedure (IVP) connects to an ORACLE database based on information you supply, and executes an SQL SHOW TABLES statement. Because the IVP is interactive, it is not run during installation. You can run the IVP separately to ensure the integrity of installed files and to ensure that the gateway for ORACLE can connect to an ORACLE database. The IVP takes approximately 1 to 2 minutes to run. The actual time depends on the processor type. Before you run the IVP, you must complete all the other post-installation tasks described in this chapter. You must provide the following information in the form of an attach specification (attach string) after starting the IVP: o The gateway name, TYPE=ORACLE After Installing DEC DB Integrator Gateway for ORACLE 4-1 o The ORACLE user name, for example, USER=CJONES o The SQL*Net connect string, for example, NODE=TRSTAN- DFLT Optionally, you can provide an ORACLE password or a list of tables to which you want to connect. The following is an example of an attach specification: /TYPE=ORACLE/USER=CJONES/PASSWORD=STAR/NODE=TRSTAN-DFLT Refer to the DEC DB Integrator Product Family User's Guide for more information about attach specification qualifiers. 4.1.1 Invoking the IVP To invoke the IVP, enter: $ @SYS$TEST:LORA$IVP.COM 4.1.2 Sample IVP Log The following is a sample IVP log from a VAX system. Running the IVP on an AXP system would produce a similar log. $ @sys$test:lora$ivp ***************************************************************** Installation Verification Procedure (IVP) for DEC DB Integrator Gateway for ORACLE V3.1-00 for OpenVMS VAX Copyright Digital Equipment Corporation 1993,1994. All rights reserved. This IVP verifies that all the gateway images are in place and a simple query can be executed. ***************************************************************** 4-2 After Installing DEC DB Integrator Gateway for ORACLE Enter a SQL attach string terminated by a semi-colon. Example: /TYPE=ORACLE/USER=SCOTT/PASSWORD=TIGER/NODE=NODE1-V7P/TABLE=COLLEGES; attach string:/type=oracle _: /user=scott _: /password=tiger _: /node=portit-axp7 _: /table=emp; The current string is: /type=oracle/user=scott/password=tiger/node=portit-axp7/table=emp Are you satisfied with that? (Y/N): y Current PROCESS SQL environment is version V6.0-nn (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version V6.0-nn (MULTIVERSION) User tables in database with filename SQL$DATABASE EMP IVP completed successfully. To abort the IVP at any time, press Ctrl/Y. When you press Ctrl/Y, the IVP stops running and aborts. 4.2 Editing the System Startup Files You may want to edit the system startup files to provide for automatic startup of the gateway for ORACLE when your system is restarted. The installation procedure adds the following command file to the SYS$STARTUP directory: SYS$STARTUP:LORA$STARTUP.COM This command file starts the gateway for ORACLE. You must add this command to the system startup file, SYS$MANAGER:SYSTARTUP_V5.COM. The command file installs the gateway images as shared images. This reduces system overhead and memory requirements when running the gateway for ORACLE. You must position this new command line after the line that invokes the network startup command procedure. The following example shows the network startup command line followed by the gateway for ORACLE startup command line: After Installing DEC DB Integrator Gateway for ORACLE 4-3 $ @SYS$MANAGER:STARTNET.COM . . . $ @SYS$STARTUP:LORA$STARTUP.COM 4.3 Editing the System Shutdown File The installation procedure adds the following command file to the SYS$MANAGER directory: LORA$SHUTDOWN.COM. This command file can be used to remove the images installed by the LORA$STARTUP.COM file. Add the following line to the system shutdown file, SYS$MANAGER:SYSHUTDOWN.COM: $ @SYS$MANAGER:LORA$SHUTDOWN.COM 4.4 Determining User Account Privileges To use the gateway for ORACLE, each account must have at least the TMPMBX and NETMBX privileges. Use the OpenVMS Authorize utility to determine whether or not users have the privileges they require. 4.5 Installing Licenses on All Nodes in a VMScluster A license should be installed on all the nodes in a VMScluster. If you try to run the gateway for ORACLE on a cluster 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 VMScluster: 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 VMScluster: $ LICENSE LOAD DB-GATEWAY-ORACLE If you encounter any errors, refer to the OpenVMS License Management Utility Manual. 4-4 After Installing DEC DB Integrator Gateway for ORACLE 4.6 Setting Up the SQL*Net Connection If users of the gateway for ORACLE will be accessing ORACLE databases on a remote node, you must configure the ORACLE RDBMS system with SQL*Net. Refer to the ORACLE SQL*Net documentation for information about configuring SQL*Net. SQL*Net may have already been configured. If so, contact your ORACLE DBA to find the name of the DECnet object for your connection. SQL*Net connections are made using standard DECnet task object connections. A network object is defined for the server task. The gateway for ORACLE, through SQL*Net, connects to the defined DECnet object. The following example uses the Network Control Program (NCP) utility to define the DECnet object. You must execute these commands from a privileged account. $ RUN SYS$SYSTEM NCP NCP> DEFINE OBJECT ORDNV634 NUMBER 0 USER ORACLE_RDBMS_ACCOUNT- PASS ACCOUNT_PASSWORD FILE DISK$ORA:[ORACLEV634]ORDNDFLT.COM NCP> LIST OBJECT ORDNV634 Object Permanent Summary as of 11-NOV-1993 10:35:50 Object = ORDNV634 Number = 0 File id = DISK$ORA:[ORACLEV634]ORDNDFLT.COM User id = ORACLE_RDBMS_ACCOUNT Password = ACCOUNT_PASSWORD The object name in the example has been defined using the default prefix ORDN, which is supported by ORACLE's SQL*Net. If this ORDN prefix is used, the shortened form of the NODE attach specification qualifier can be used, as described in Chapter 1. In the following example, a network connection will be made to the node TROUPE to the DECnet object ORDNV634 using the DECnet protocol. The DECnet object will execute the command file named ORDNDFLT.COM in the directory DISK$ORA:[ORACLEV634] and start the SQL*Net server. After Installing DEC DB Integrator Gateway for ORACLE 4-5 $ SQL SQL> ATTACH 'FILE/TYPE=ORACLE/USER=SCOTT/PASS=TIGER- cont> /NODE=TROUPE-V634'; SQL> SHOW TABLES; User tables in database with filename /TYPE=ORACLE/USER=SCOTT/PASS=TIGER BONUS DEPT EMP SALGRADE Please refer to your ORACLE SQL*Net documentation for complete instructions. Digital recommends that you test the connection by using SQL*Plus to verify object names and SQL*Net connections, for example: SQL> CONNECT SCOTT/TIGER@d:TROUPE"ORACLE password"::TASK=ORDNV634"; If the object is not defined or is not defined correctly, the gateway for ORACLE will display a series of error messages, which includes the following ORACLE error message: Error during Connect - 6031 4-6 After Installing DEC DB Integrator Gateway for ORACLE For further explanation of the ORACLE error, see the error message description provided by ORACLE, for example: $ SEARCH ORA_RDBMS:ERROR.MSG 6031/WINDOW=10 ORA_ROOT:[RDBMS]ERROR.MSG;1 06031, 00000, "NETDNT: connect failed, unrecognized object name" // *Cause: Host string contains reference to object (which doesn't exist): // @d:- => object is ORDN; when is // VMS the object is ORDN.COM // @d:::"task=" => object is ; when // is VMS the object is .COM 4.7 Using the OpenVMS Mailbox Driver If you are using the gateway for ORACLE without SQL*Net, you must install the gateway for ORACLE on the ORACLE RDBMS system. You are still required to use the NODE qualifier. Use a value of 2: with the NODE qualifier to indicate you are using the OpenVMS Mailbox, as shown in the following example: $ SQL SQL> ATTACH 'FILENAME/TYPE=ORACLE/USER=SCOTT- cont>/NODE=2:/PASSWORD=TIGER'; SQL> SHOW TABLES; User tables in database with filename /TYPE=ORACLE/USER=SCOTT/NODE=2:/PASSWORD=TIGER BONUS DEPT EMP SALGRADE In this example, the ORA_RDBMS:ORASRV2.COM file will be activated. After Installing DEC DB Integrator Gateway for ORACLE 4-7 4.8 Linking the Gateway Image The installation of the ORACLE gateway usually success- fully links the gateway image. However, this is not always the case. All the files you need to link a gateway image are provided. If the link fails, you have the necessary files for input to the linker and you need not re-install the product. 4-8 After Installing DEC DB Integrator Gateway for ORACLE If the installation fails to create an image, the installation continues to completion, but displays the following message near the end of installation: ************************************************************** * N O T E *** N O T E *** N O T E *** N O T E *** N O T E * A problem was detected while attempting to link the image. The installation will continue, but you will be unable to run the product. See SYS$LIBRARY:LDRV$ORACLE_LINK.LOG for the specific cause of the link failure. Also see the Installation Guide for hints on how to discover and fix the problem. You can relink by typing the following: $ @SYS$LIBRARY:LDRV$ORACLE_LINK * N O T E *** N O T E *** N O T E *** N O T E *** N O T E * ************************************************************** If you see this message, you will need to determine what is causing the link failure, correct your environment, relink, and run the ORACLE gateway startup command file. 4.8.1 Determining the Cause of a Link Failure The ORACLE gateway is an ORACLE Pro*C application including embedded SQL and Oracle Call Interface (OCI) calls. It is linked using the following command files: SYS$LIBRARY:LDRV$ORACLE_LINK.COM SYS$LIBRARY:LDRV$ORACLE_LINK_V7.COM The ORACLE gateway also uses SYS$LIBRARY:LDRV$ORACLE_LINK_ V7_xxx.OPT as input to the linker, where xxx is either VAX or AXP depending on your operating system. The preceding command files use the ORACLE LOUTL.COM procedure to issue the actual link command. If your ORACLE environment is improperly configured or if there is an error in any of the preceding command files, the link will be unsuccessful. A log file from the link is output to SYS$LIBRARY:LDRV$ORACLE_LINK.LOG, which contains the error detected during the link. After Installing DEC DB Integrator Gateway for ORACLE 4-9 4.8.2 Relinking the Gateway Image When you have corrected the environment and wish to relink, first invoke the ORACLE user command file, then enter: $ @SYS$LIBRARY:LDRV$ORACLE_LINK Error output is directed to both the terminal and SYS$LIBRARY:LDRV$ORACLE_LINK.LOG. 4.8.3 Running the Startup Command File To invoke the startup command file, enter: $ @SYS$STARTUP:LORA$STARTUP 4.9 Determining and Reporting Problems If you encounter a problem while using the gateway for ORACLE, 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: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Send Us Your Comments form if the problem has to do with the gateway for ORACLE documentation. These forms are at the front of each manual. Use the form from the manual in which you found the error. Include the section and page number. 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 previously or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. 4-10 After Installing DEC DB Integrator Gateway for ORACLE A ________________________________________________________________ Prerequisite Installation of Common Components This chapter describes how to install the Common Components, a prerequisite for installation of DEC DB Integrator (DBI) and the DEC DB Integrator Gateway products (DB Integrator Gateways, also referred to as the gateway products). Please note the following requirements: o If you have an existing DEC Rdb kit on your system, you must install the Common Components or install DEC Rdb Version 6.0 before you can use any member of the DBI product family. o If you choose not to upgrade to DEC Rdb Version 6.0, Digital recommends that you install the multiversion Common Components. Installing the multiversion Common Components will not break applications or production systems that require previous versions of DEC Rdb. For more information, see Section A.1.2. o If you do not have DEC Rdb on your system, and do not plan to install it, you must install the Common Components before you can use the DBI product family. A.1 Common Components The Common Components provides support for relational database functions for Digital database products. These components are common to DBI, the DBI gateway products, and DEC Rdb. The Common Components are: o SQL interface o SQL/Services server Prerequisite Installation of Common Components A-1 o Rdb/Dispatch and Rdb/Remote server These components must be present on a system in order to run SQL applications. A.1.1 Media Required When you purchase any of the Digital database access products (DBI, DB Integrator Gateways, or DEC Rdb), you receive the kit for that product, plus an entire DEC Rdb software kit, which contains the Common Components. You only need to install the Common Components from the DEC Rdb kit, not the entire kit to use the Common Components with DBI or the gateway products. Install the Common Components using the DEC Rdb installation procedure by choosing the Common Components option during the installation. The Common Components must be present on your system before you can install DBI or a gateway product. A.1.2 Version Variants and Existing Databases If you have a version of DEC Rdb prior to Version 6.0 installed, you do not need to upgrade DEC Rdb in order to install members of the DBI product family, but you must install the Common Components from the DEC Rdb media. Digital recommends that you install the multiversion Common Components if you expect to maintain more than one version of Rdb. The Common Components have two possible variants: o Standard Use when you have only one version of DEC Rdb on your system. o Multiversion Use when you have multiple versions of DEC Rdb or a version DEC Rdb that is different from the version of the Common Components being installed. Installing the multiversion variant will not write over any existing DEC Rdb images from previous versions, such as the Online Help. If you install the multi- version variant of Common Components, you can use the SYS$LIBRARY:SQL$SETVER.COM procedure to control the A-2 Prerequisite Installation of Common Components version of Common Components whenever your database environment requires a particular version of SQL or Rdb/Dispatch. For more information about SQL$SETVER, see Section A.8. A.2 Disk Space Required The following tables summarize the storage requirements for installing the Common Components. The values in the lists are approximate. The disk space requirements for OpenVMS AXP are: __________________________________________________________ Needed for Used After Kit______________Installation_________Installation________ Full Development 62,000 62,000 Run-Time_________62,000_______________39,000<>____________ The disk space requirements for OpenVMS VAX are: __________________________________________________________ Used After Kit______________Needed_for_Installation_Installation_____ Full Development 40,000 40,000 Run-Time_________40,000__________________28,000<>_________ A.3 OpenVMS Privileges Required The VMSINSTAL command procedure is located in SYS$UPDATE, which is a restricted directory. To install the Common Components, you must use an account that has the SETPRV privilege authorized. As one of its first actions, the VMSINSTAL command procedure grants all privileges except BYPASS to the process that invokes it. The VMSINSTAL command succeeds only if the installing account has SETPRV privilege. To check the default privileges of the installing account, log in and enter this DCL command: $ SHOW PROCESS/PRIVILEGES Prerequisite Installation of Common Components A-3 If the installing account lacks the SETPRV privilege, you cannot install the Common Components. You have two options: o Ask your system manager to use the OpenVMS Authorize utility (AUTHORIZE) to modify the default privileges of the account to include the SETPRV privilege. A-4 Prerequisite Installation of Common Components o Run AUTHORIZE and make the changes yourself, if the installing account has the SYSPRV privilege: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> MODIFY /PRIVILEGES=(SETPRV) UAF> EXIT To activate the change in privileges, you must log out and then log in. ________________________Note ________________________ When installing the Common Components on systems with DECnet/OSI, the installing account must also have the NET$MANAGE identifier. _____________________________________________________ A.4 Unlocking the Process Account Password The installing account cannot have a locked password. If this is the initial installation of the Common Components, the installation procedure creates an account called RDB$REMOTE, or RDB$REMOTEnn for a multiversion installation. If the installing account has a locked password, the installation procedure will be unable to automatically generate a password for this account, and will abort with the following message: ************************************************************* Error generating password for remote account. ************************************************************** To modify an account with a locked password, enter: $ MCR AUTHORIZE UAF> MODIFY /FLAGS=NOLOCKPWD Prerequisite Installation of Common Components A-5 A.5 Installing Common Components To install Common Components: 1. Invoke the VMSINSTAL command procedure from a privileged account, using the following syntax: @SYS$UPDATE:VMSINSTAL variant-name device-name OPTIONS N Supply the appropriate name for the variant you want to install from the following table: _______________________________________________________ Name_____________Variant__________OpenVMS______________ DECRDBA060 standard AXP DECRDBAMV060 multiversion AXP DECRDB060 standard VAX DECRDBMV060______multiversion_____VAX__________________ Digital recommends that you install the multiversion kit. This avoids possible problems in writing over existing files and images for a different version of the Common Components or DEC Rdb. For example, to install the Common Components OpenVMS AXP multiversion kit on device ddcu, enter: $ @SYS$UPDATE:VMSINSTAL decrdbamv060 ddcu: OPTIONS N To install the Common Components OpenVMS VAX standard kit on device ddcu, enter: $ @SYS$UPDATE:VMSINSTAL decrdb060 ddcu: OPTIONS N 2. Type CC (for COMMON COMPONENTS) when prompted for the kit type to install. The menu and response should appear as follows: *********************************************************************** From the following menu, please select the type of DEC Rdb kit to install. Choice CC (COMMON COMPONENTS) is included in all 3 DEC Rdb installations and should only be selected when installing a product, other than DEC Rdb, that requires the common components. *********************************************************************** A-6 Prerequisite Installation of Common Components Please select the type of DEC Rdb kit you wish to install: Enter DEV for DEC Rdb DEVELOPMENT (the default) Enter INT for DEC Rdb INTERACTIVE Enter RTO for DEC Rdb RUNTIME-ONLY Enter CC for COMMON COMPONENTS * Enter the kit type to install [DEV]: CC Prerequisite Installation of Common Components A-7 When you enter CC, only the Common Components save set (B) will be restored. The following submenu will be displayed: *********************************************************************** The COMMON COMPONENTS option should be selected only when installing a product other than Rdb. It is not intended for use with any Rdb installation. *********************************************************************** Please select the type of COMMON COMPONENTS kit you wish to install: Enter DEV for DEVELOPMENT Enter RTO for RUNTIME-ONLY (the default) * Enter the type of COMMON COMPONENTS to install [RTO]: 3. Press the Return key to select the default option, RUNTIME-ONLY. Do not select the DEVELOPMENT option unless you have purchased one of the following development licenses: o DEC SQL development license o DEC Rdb development license o DEC DB Integrator (DBI) development license Selecting the DEVELOPMENT option provides the addi- tional SQL files needed for development: SQL$PREnn.EXE, SQL$MODnn.EXE; a small number of related files; and all the Rdb/Dispatch and SQL files installed with the RTO default. A.6 Installing Common Components Images as Shared The Common Components installation procedure does not install any images as shared. If you expect Common Components images to be used extensively on your system, you can reduce the system overhead and memory requirements by installing images as shared. When images are not installed as shared, multiple users who access the images at the same time must each have his or her own copy of those images in memory. When the images are installed as shared, everyone uses the same copy of the image, A-8 Prerequisite Installation of Common Components eliminating duplicate copies of an image and improving performance. Prerequisite Installation of Common Components A-9 A.6.1 Editing the Startup and Shutdown Procedures for Shared Images The separate startup and shutdown procedures, which are provided to install and remove the SQL and Rdb/Dispatch images, are as follows: o SYS$STARTUP:SQL$STARTUP.COM o SYS$MANAGER:SQL$SHUTDOWN.COM DBI and the DBI Gateways will call these procedures from their own startup and shutdown procedures. The following Rdb/Dispatch images are automatically installed by the SQL$STARTUP.COM procedure: o SYS$LIBRARY:RDBSHR.EXE o SYS$LIBRARY:RDB$SHARE.EXE o SYS$MESSAGE:RDBMSGS.EXE o SYS$MESSAGE:COSIMSG.EXE SQL files are not currently installed by the SQL$STARTUP.COM procedure. However, subroutines to install or to remove these images are included in the SQL$STARTUP.COM proce- dure. To activate the subroutines for the installation and/or removal of SQL images, remove the comment character (!) from the following lines in the SQL$STARTUP.COM and SQL$SHUTDOWN.COM procedures: $ ! GOSUB INSTALL_SQL_IMAGES $ ! GOSUB REMOVE_SQL_IMAGES If you invoke the INSTALL_SQL_IMAGES subroutine, the SQL$STARTUP.COM procedure installs the following SQL images: o SYS$LIBRARY:SQL$INT.EXE o SYS$LIBRARY:SQL$SHR.EXE o SYS$MESSAGE:SQL$MSG.EXE The INSTALL_SQL_IMAGES subroutine also includes code to install the SQL$UTL_SHARE60.EXE image and the development images, SQL$.EXE, SQL$MOD.EXE, and SQL$PRE.EXE. To execute the installations, remove the comment character preceding the code. The SQL$STARTUP.COM procedure provides an A-10 Prerequisite Installation of Common Components explanation why these images are not included in the default installations. Prerequisite Installation of Common Components A-11 Because SQL$UTL_SHAREnn.EXE is a variant image for both standard and multiversion Common Components, you must add additional lines of code to install images for each Common Components version you install as shared. Development images are not typically installed as shared images. A.6.2 Verifying Global Pages and Sections Table A-1 and Table A-2 show the remaining Common Components images not installed as shared on your system. SQL images not installed as shared during Common Components installation are also included in these tables to show the global page and global section requirements. If you install some or all of these images as shared, you must verify that you have enough global pages and global sections to accommodate the shared images. Use the following DCL F$GETSYI lexical function to determine the number of available global pages and global sections: $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") If the number of unused global pages or global sections is less than the number specified in Table A-1 and Table A-2, increase the value using the AUTOGEN utility. Table A-1 lists the approximate number of global pages and global sections required for each Common Components OpenVMS VAX image that you install as shared. <> Table A-2 lists the approximate number of global pagelets and global sections required for each Common Components OpenVMS AXP image that you install as shared. On OpenVMS AXP systems, the size of a page can differ on different systems. Pagelets are 512 bytes and correspond to OpenVMS VAX pages; they are not system-specific. <> A-12 Prerequisite Installation of Common Components Table A-1 Global Pages and Sections Required for Common __________Components_OpenVMS_VAX_Images_________________________ GlobalGlobal Component_____________Image_Name[1]___________________Pages[Sections[2] SQL images SYS$LIBRARY:SQL$INT.EXE[3] 3 2 * SYS$LIBRARY:SQL$SHR.EXE 16 2 SYS$LIBRARY:SQL$UTL_ 142 3 SHARE60.EXE * SYS$MESSAGE:SQL$MSG.EXE 329 1 * SYS$SYSTEM:SQL$.EXE 1635 2 * SYS$SYSTEM:SQL$PRE.EXE 4911 3 * SYS$SYSTEM:SQL$MOD.EXE 4768 3 [1]If_you_have_installed_the_multiversion_variant_of_the_Common_ Components, some images have the version number added to the end of the image name. Those images are marked with an asterisk next to the image name. [2]Values supplied are approximate. If you have installed the multiversion variant of the Common Components, multiply the supplied values by the number of versions of the Common Components running on your system. [3]SQL$INT calls either SQL$SHR, or a version-specific variant (such as SQL$SHR60), depending on what version you have specified. ________________________________________________________________ Prerequisite Installation of Common Components A-13 Table A-2 Global Pagelets and Sections Required for Common __________Components_OpenVMS_AXP_Images_________________________ GlobalGlobal Component_____________Image_Name[1]___________________PageleSections[2] SQL images SYS$LIBRARY:SQL$INT.EXE[3] 65 1 * SYS$LIBRARY:SQL$SHR.EXE 2394 2 SYS$LIBRARY:SQL$UTL_ 431 2 SHARE60.EXE * SYS$MESSAGE:SQL$MSG.EXE 329 1 * SYS$SYSTEM:SQL$.EXE 3237 1 * SYS$SYSTEM:SQL$PRE.EXE 8461 2 * SYS$SYSTEM:SQL$MOD.EXE 8166 2 [1]If_you_have_installed_the_multiversion_variant_of_the_Common_ Components, some images have the version number added to the end of the image name. Those images are marked with an asterisk next to the image name. [2]Values supplied are approximate. If you have installed the multiversion variant of the Common Components, multiply the supplied values by the number of versions of the Common Components running on your system. [3]SQL$INT calls either SQL$SHR, or a version-specific variant (such as SQL$SHR60), depending on what version you have specified. ________________________________________________________________ A.6.3 Removing Installed Images The SQL$SHUTDOWN.COM procedure removes Common Components images that have been installed. By default, the SQL$SHUTDOWN.COM procedure removes only the images installed by Rdb/Dispatch. However, a subroutine is included that removes the SQL images. To activate this subroutine, remove the comment character (!) from the following line in the SQL$SHUTDOWN.COM procedure where this subroutine is invoked: $ ! GOSUB REMOVE_SQL_IMAGES ! In SQL$SHUTDOWN.COM A-14 Prerequisite Installation of Common Components The SQL$SHUTDOWN.COM procedure only removes images when no other client requiring the Common Components is installed on the system. Consequently, it requires that you pass a calling-client parameter, which is also referred to as P1, to determine if any other clients are still present on the system. You must execute the SQL$SETVER.COM procedure before you execute the SQL$SHUTDOWN.COM procedure. Otherwise, you receive an error message indicating that the logical names were not set. For more information about SQL$SETVER.COM, see Section A.8. The syntax for using the SQL$SHUTDOWN.COM procedure is as follows: $ @SYS$LIBRARY:SQL$SETVER $ @SYS$MANAGER:SQL$SHUTDOWN In the preceding example, is the Common Components version shipped with the client, and is one of the following: o DBI-use for DBI and the relational gateway products o NSDS-use for the nonrelational gateway products o RDBB-use for Rdb/ELN o RDM-use for DEC Rdb o VIDA-use for VIDA for IDMS/R o VIDA2-use for RdbAccess for DB2 Version 1.0 or Version 2.0 o VIDAO-use for RdbAccess for ORACLE Version 1.0 or Version 2.0 The relational gateway products are: o DEC DB Integrator Gateway for DB2 o DEC DB Integrator Gateway for EDA/SQL o DEC DB Integrator Gateway for ORACLE o DEC DB Integrator Gateway for SequeLink o DEC DB Integrator Gateway for SYBASE Prerequisite Installation of Common Components A-15 The nonrelational gateway products are: o DEC DB Integrator Gateway for Custom Drivers o DEC DB Integrator Gateway for DBMS o DEC DB Integrator Gateway for DSM o DEC DB Integrator Gateway for RMS The following example sets the Common Components to Version 6.0, then removes the images for the nonrelational gateway products: $ @SYS$LIBRARY:SQL$SETVER 6.0 $ @SYS$MANAGER:SQL$SHUTDOWN NSDS By default, the removal of images from the INSTALL utility is triggered by the logical names SQL$VERSION_VARIANT and RDB$DISPATCH_VERSION_VARIANT, which are defined by the SYS$LIBRARY:SQL$SETVER.COM procedure. ________________________Note ________________________ It is possible to set these logical names to different versions for the process, job, group, and system tables, if necessary. However, be very careful to avoid creating incompatibilities if you do so. Do this only when advised that it is absolutely necessary to solve a particular problem. _____________________________________________________ You can override the SQL$VERSION_VARIANT and RDB$DISPATCH_ VERSION_VARIANT logical names by passing a valid calling- client name as parameter P1, and the Common Components version to remove as P2. To override the use of the logical names to determine which Common Component images to remove, pass the version as P2. The following command removes Version 6.0 images: $ @SYS$MANAGER:SQL$SHUTDOWN DBI 6.0 If the DEC Rdb multiversion Version 6.0 software is installed, only the Version 6.0 images will be removed; otherwise the standard images, if they are Version 6.0 images, will be removed. A-16 Prerequisite Installation of Common Components A.7 Installing SQL Images for Privileged Applications Applications that use SQL and are installed with privileges require that you install the following images: o SYS$LIBRARY:SQL$INT.EXE o SYS$LIBRARY:SQL$SHR.EXE (or SYS$LIBRARY:SQL$SHR60.EXE) None of the SQL images supplied as part of the Common Components is installed unless you modify the SQL$STARTUP.COM procedure to permit it. Unless you install these images, applications installed with privileges will encounter the following error: %SQL-F-NOENTRYPT, Older SQL version not compatible with compiled SQL It is not necessary to install the SQL images as shared or with privileges to avoid this error. Installing in any manner will avoid the error. The separate startup and shutdown procedures, which are provided to install and remove the SQL and Rdb/Dispatch images, are as follows: o SYS$STARTUP:SQL$STARTUP.COM o SYS$MANAGER:SQL$SHUTDOWN.COM DBI and the DBI Gateways will call these procedures from their own startup and shutdown procedures. The following Rdb/Dispatch images are automatically installed by the SQL$STARTUP.COM procedure: o SYS$LIBRARY:RDBSHR.EXE o SYS$LIBRARY:RDB$SHARE.EXE o SYS$MESSAGE:RDBMSGS.EXE o SYS$MESSAGE:COSI$MSG.EXE Prerequisite Installation of Common Components A-17 A.7.1 Editing the Startup and Shutdown Procedures for Privileged Applications SQL files are not currently installed by the SQL$STARTUP.COM procedure. However, a subroutine to install these images is included in the SQL$STARTUP.COM procedure. To activate the installation and/or removal of SQL images, remove the comment character (!) from the following lines in the SQL$STARTUP.COM and SQL$SHUTDOWN.COM procedures: $ ! GOSUB INSTALL_SQL_IMAGES $ ! GOSUB REMOVE_SQL_IMAGES The INSTALL_SQL_IMAGES subroutine in the SQL$STARTUP.COM procedure installs the following SQL images: o SYS$LIBRARY:SQL$INT.EXE o SYS$LIBRARY:SQL$SHR.EXE (or SYS$LIBRARY:SQL$SHR60.EXE) o SYS$MESSAGE:SQL$MSG.EXE (or SYS$MESSAGE:SQL$MSG60.EXE) The subroutine also includes code to install the development images SQL$.EXE, SQL$MOD.EXE, and SQL$PRE.EXE, and the internal SQL utilities image SQL$UTL_SHARE60.EXE. To execute the installations, you must remove the comment character that precedes the code. The SQL$STARTUP.COM procedure provides an explanation of why these images are not included in the default installations. Because the SQL$UTL_SHAREnn.EXE image is a variant image for both standard and multiversion Common Components, you must add additional lines for each Common Components version you install as shared. Development images are not typically installed as shared images. If you install some or all of these images as shared, you must verify that you have enough global pages and global sections to accommodate the shared images. Table A-1 lists the approximate number of global pages and global sections required for each Common Components for OpenVMS VAX image that you install as shared.<> Table A-2 provides the global pagelets and sections required for the Common Components for OpenVMS AXP images. On OpenVMS AXP systems, the size of a page can differ on A-18 Prerequisite Installation of Common Components different CPUs. Pagelets are 512 bytes and correspond to OpenVMS VAX pages; they are not CPU-specific. <> A.8 Using Different Versions of the Common Components Certain environments may require a specific version of the Common Components, or may need to set each component to a different version. The SYS$LIBRARY:SQL$SETVER.COM and SYS$LIBRARY:SQL$SHOVER.COM procedures are provided with the Common Components installation to set up the logical names and symbols necessary for using a particular version of SQL and/or Rdb/Dispatch. ________________________Note ________________________ To use the DBI Gateway products or DEC DB Integrator, the Common Components' environment must be set to 6.0. This can be done at the system, group, or process level, as described in the following section. _____________________________________________________ The SQL$SETVER.COM procedure will accept the following three parameters: o P1 = (REQUIRED) version (that is, S for STANDARD, 6.0 for MULTIVERSION) or RESET to reset SQL symbols or REMOVE to remove SQL and DISPATCH logical names. o P2 = (OPTIONAL) Logical name table qualifier (PROCESS, GROUP, JOB, or SYSTEM). The default is PROCESS. o P3 = (OPTIONAL) Common Components logical names to set (SQL, DISPATCH, or ALL). The default is ALL. This can go in P2 or P3 as the last parameter. The following example sets both SQL and Rdb/Dispatch to multiversion Version 6.0. If multiversion Version 6.0 is not installed and a standard version is found, the standard version will be set. $ @SYS$LIBRARY:SQL$SETVER 6.0 Current PROCESS SQL environment is version 6.0-0 (MULTIVERSION) Current PROCESS Rdb/Dispatch environment is version 6.0-0 (MULTIVERSION) Prerequisite Installation of Common Components A-19 The following examples show other possible parameters: ! To set only Rdb/Dispatch $ @SYS$LIBRARY:SQL$SETVER 6.0 DISPATCH ! To set only SQL $ @SYS$LIBRARY:SQL$SETVER 6.0 SQL ! To set only SQL in group table $ @SYS$LIBRARY:SQL$SETVER 6.0 /GROUP SQL ! To set both SQL and Rdb/Dispatch to standard version $ @SYS$LIBRARY:SQL$SETVER S ! To set only Rdb/Dispatch to standard version $ @SYS$LIBRARY:SQL$SETVER S DISPATCH ! To set only SQL to standard version $ @SYS$LIBRARY:SQL$SETVER S SQL The SQL$SHOVER.COM procedure has the following two functions: o To show the current settings for each logical name table: $ @SYS$LIBRARY:SQL$SHOVER Current PROCESS SQL environment is version 6.0-0 (MULTIVERSION) Current PROCESS DISPATCH environment is version 6.0-0 (MULTIVERSION) o To show all the versions installed on the system. You can use this to determine what the highest version of Rdb/Dispatch or SQL is installed on the system. $ @SYS$LIBRARY:SQL$SHOVER VERSIONS "SQL$INSTALLED_VERSIONS" = "*6.0-0" (LNM$PROCESS_TABLE) "RDB$DISPATCH_INSTALLED_VERSIONS" = "V4.0-5" (LNM$PROCESS_TABLE) "*6.0-0" The * in the preceding output indicates a multiversion kit. The following examples show other possible parameters: ! To show only Rdb/Dispatch $ @SYS$LIBRARY:SQL$SHOVER VERSIONS DISPATCH ! To show only SQL $ @SYS$LIBRARY:SQL$SHOVER VERSIONS SQL ! To show only 6.0 Rdb/Dispatch $ @SYS$LIBRARY:SQL$SHOVER VERSIONS DISPATCH 6.0 ! To show only 6.0 SQL and suppress output $ @SYS$LIBRARY:SQL$SHOVER VERSIONS SQL 6.0 NOSHOW A-20 Prerequisite Installation of Common Components A.9 Deleting Versions of the Common Components For your convenience, the Common Components kit provides a command procedure, SYS$MANAGER:SQL$DEINSTALL_DELETE.COM, to delete current or previous versions of the Common Components. You must run this command procedure from an account that has SETPRV privileges, or from an account that has SYSPRV, CMKRNL, SYSNAM, and WORLD privileges. You can use this command file to delete previous versions of the Common Components when you have installed a newer version and determine that prior versions are no longer needed. ________________________Note ________________________ The SQL$DEINSTALL_DELETE.COM procedure will not execute if multiple products requiring Common Components are found on the system or DEC Rdb of the same version is found on the system. _____________________________________________________ When you run the command procedure, you may choose to pass a single parameter that indicates the output location for all messages generated while the command procedure processes. This parameter can either be the name of a file (for example, SQL$DEINSTALL_DELETE.LOG) or the logical name SYS$OUTPUT (which displays messages on your screen). To run the SQL$DEINSTALL_DELETE command procedure and have messages sent to a file named SQL$DEINSTALL_DELETE.LOG, enter: $ @SYS$MANAGER:SQL$DEINSTALL_DELETE.COM SQL$DEINSTALL_DELETE.LOG The command procedure checks for the existence of the different versions of the Common Components on your system, and then displays a menu listing each version found (standard first, and then the oldest to the most current multiversion): Prerequisite Installation of Common Components A-21 SQL versions currently installed on your system * Version 5.1 (Multiversion) 1 Version 6.0 (Multiversion) 0 Quit (* This version cannot be deinstalled by this procedure) Enter Choice to deinstall (0...1) : 0 If the command procedure displays an asterisk (*) next to a version entry on the menu, it means that version cannot be deleted by the SQL$DEINSTALL_DELETE.COM procedure because it is prior to Version 6.0. Enter the menu number for the version you want to delete. For example, to delete Version 6.0 multiversion, enter the following: Enter Choice to deinstall (0...1) : 1 The command procedure displays the following message: You are about to deinstall SQL 6.0 (Multiversion) If your system is a cluster member, this procedure creates the SYS$SCRATCH:SQL$CLUSTER_DEINSTALL60.COM procedure. Use this command procedure to remove the Common Components Version 6.0 (multiversion) from other nodes in the cluster. You must either run this command procedure on each node that has Common Components Version 6.0 (multiversion) installed, or use the SYSMAN utility to run it clusterwide. Next, the command procedure asks you to confirm that you want to continue with the deinstallation (whether or not your system is part of a cluster): Enter Y(ES) to continue to deinstall SQL 6.0 (Multiversion): YES The final prompt asks you whether or not you want to delete the RDB$REMOTE account for the version you specified (keep this account if, for example, you plan to use it as a template to build other accounts): Do you want to delete RDB$REMOTE60? [N]: YES A-22 Prerequisite Installation of Common Components When the command procedure completes the deletion of the appropriate files, it displays the following message: %SQL-I-END Deinstallation of SQL 6.0 (Multiversion) now complete Prerequisite Installation of Common Components A-23 B ________________________________________________________________ Sample Installation This appendix contains a sample installation of DEC DB Integrator Gateway for ORACLE on OpenVMS VAX. The procedure on OpenVMS AXP is similar. The Installation Verification Procedure (IVP) runs at the end of the installation. $ @sys$update:vmsinstal lora031 SYS$SYSROOT:[SYSMGR.LORA] OPTIONS N VAX/VMS Software Product Installation Procedure V5.5-2 It is 02-NOV-1994 at 12:38. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: SQLSRV$SERVER * Do you want to continue anyway [NO]? y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: LORA V3.1 Beginning installation of LORA V3.1 at 12:39 %VMSINSTAL-I-RESTORE, Restoring product save set 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 Sample Installation B-1 * Select option [2]: 4 * Do you want to continue the installation [NO]? y %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. ************************************************************** The installation procedure for DEC DB Integrator Gateway for Oracle V3.1-00 for OpenVMS VAX © Digital Equipment Corporation 1994. All rights reserved. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, or copying of this software and media is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. ************************************************************** * Would you like to print the LORA Installation Guide [NO]? * Do you want to continue [YES]? Product: DB-GATEWAY-ORACLE Producer: DEC Version: 3.1 Release Date: 02-NOV-1994 * Does this product have an authorization key registered and loaded? y Please enter the name and location of the Oracle user command procedure. For example, ORA_ROOT:[UTIL]ORAUSER.COM. It will be necessary to invoke this command procedure in order to define logical names pointing to the Oracle libraries. These libraries are required in order to link the DEC DB Integrator Gateway for Oracle driver. If you are unsure of the name and location of this command procedure ask your ORACLE database administrator (DBA) or ORACLE SQL*Net installer. * Enter the name of the ORACLE user command file: $111$dua225:[sqlnetv12.util]or auser.com * Do you want to purge files replaced by this installation [YES]? B-2 Sample Installation ************************************************************** There are no more questions. The installation takes approximately 5 to 10 minutes depending on the processor type. Because the Installation Verification Procedure is interactive, it will not be run as part of the installation. You may run the IVP separately any time you wish. To execute it, type: $ @SYS$TEST:LORA$IVP ************************************************************** ************************************************************** Beginning installation of DEC DB Integrator Gateway for Oracle V3.1-00 ************************************************************** %VMSINSTAL-I-RESTORE, Restoring product save set B ... %LORA-I-LNKGWYSHR, linking LDRV$ORACLE_SHR gateway shareable image... - Linking LORA_EXE$:LDRV$ORACLE_SHR.EXE.exe ************************************************************** LORA$STARTUP.COM has been placed in SYS$STARTUP. The following line should be place in your system startup file. $ @SYS$STARTUP:LORA$STARTUP.COM ************************************************************** ************************************************************** LORA$SHUTDOWN.COM has been placed in SYS$MANAGER. The following line should be place in your system shutdown file. $ @SYS$MANAGER:LORA$SHUTDOWN.COM ************************************************************** ************************************************************** The IVP has been placed in SYS$TEST. You may run this procedure separately any time you wish. To execute it type: $ @SYS$TEST:LORA$IVP.COM ************************************************************** Sample Installation B-3 ************************************************************** Finishing installation of DEC DB Integrator Gateway for Oracle V3.1-00 ************************************************************** %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of LORA V3.1 completed at 12:47 VMSINSTAL procedure done at 12:47 B-4 Sample Installation C ________________________________________________________________ Files and Logical Names Installed on Your System The DEC DB Integrator Gateway for ORACLE installation procedure installs files on your system and defines some logical names. Section C.1 lists the files installed. Section C.2 lists the logical name defined. C.1 File Names DEC DB Integrator Gateway for ORACLE installs the following files on your system: o SYS$HELP:DBI_MSG.DOC o SYS$HELP:LDRV_MSG.DOC o SYS$HELP:LORA031.INSTALL_GUIDE o SYS$HELP:LORA031_INSTALL_GUIDE.PS o SYS$HELP:LORA031.RELEASE_NOTES o SYS$HELP:LORA031_RELEASE_NOTES.PS o SYS$LIBRARY:LDRV$ORACLE_LINK.COM o SYS$LIBRARY:LDRV$ORACLE_LINK_V634.COM o SYS$LIBRARY:LDRV$ORACLE_LINK_V7.COM o SYS$LIBRARY:LDRV$ORACLE$SHR_IDENT.OPT o SYS$LIBRARY:LDRV$LO_ORA.OLB o SYS$LIBRARY:LDRV$LO_PROC_V7.OLB o SYS$LIBRARY:LDRV_MESSAGE_PTR.OBJ o SYS$LIBRARY:LDRV$LG_GENERIC.OLB o SYS$LIBRARY:LDRV$ORACLE_LINK_V634_VAX.OPT (VAX only) o SYS$LIBRARY:LDRV$ORACLE_LINK_V7_VAX.OPT (VAX only) o SYS$LIBRARY:LDRV$LO_PROC.OLB (VAX only) Files and Logical Names Installed on Your System C-1 o SYS$LIBRARY:LDRV$ORACLE_LINK_V634_AXP.OPT (AXP only) o SYS$LIBRARY:LDRV$ORACLE_LINK_V7_AXP.OPT (AXP only) o SYS$MANAGER:DBI$SHUTDOWN_COMMON.COM o SYS$MANAGER:LORA$SHUTDOWN.COM o SYS$MESSAGE:DBI_MSG.EXE o SYS$MESSAGE:LDRV_MSG.EXE o SYS$SHARE:DBI$SHR.EXE o SYS$SHARE:LDRV$ORACLE_SHR.EXE o SYS$STARTUP:DBI$STARTUP_COMMON.COM o SYS$STARTUP:LORA$STARTUP.COM o SYS$TEST:LORA$IVP.COM C.2 Logical Name The installation also defines the following logical name: o LORA$V31_ORACLE_VERSION C-2 Files and Logical Names Installed on Your System D ________________________________________________________________ How to Order Additional Documentation Technical Support If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825) and press 2 for technical assistance. Electronic Orders If you wish to place an order through your account at the Electronic Store, dial 800-234-1998, using a modem set to 2400- or 9600-baud. You must be using a VT terminal or terminal emulator set at 8 bits, no parity. If you need assistance using the Electronic Store, call 800-DIGITAL (800-344-4825) and ask for an Electronic Store specialist. Telephone and Direct Mail Orders __________________________________________________________ From__________Call______________Write_____________________ U.S.A. DECdirect Digital Equipment Phone: 800- Corporation DIGITAL P.O. Box CS2008 (800-344-4825) Nashua, New Hampshire FAX: (603) 884- 03061 5597 Puerto Rico Phone: (809) Digital Equipment 781-0505 Caribbean, Inc. FAX: (809) 749- 3 Digital Plaza, 1st 8377 Street Suite 200 Metro Office Park San Juan, Puerto Rico 00920 How to Order Additional Documentation D-1 __________________________________________________________ From__________Call______________Write_____________________ Canada Phone: 800-267- Digital Equipment of 6215 Canada Ltd. FAX: (613) 592- 100 Herzberg Road 1946 Kanata, Ontario, Canada K2K 2A6 Attn: DECdirect Sales International -- Local Digital subsidiary or approved distributor Internal DTN: 264-3030 U.S. Software Supply Orders[1] (603) 884-3030 Business (SSB) (for Digital Equipment software Corporation and hardware 10 Cotton Road documentation) Nashua, New Hampshire 03063-1260 [1]Call_to_request_an_Internal_Software_Order_Form_(EN-___ 01740-07).________________________________________________ D-2 How to Order Additional Documentation ________________________________________________________________ Index A Coordinator ___________________________ See Gateway coordinator Accessing COSIMSG image, A-17 multiple databases, 1-7 ORACLE instances, 1-7 D__________________________ Accessing data, 1-2 DBA Attach specification, 1-2 for IVP, 4-1 See ORACLE database for local access, 1-4 DBI engine, 1-3 for network access, 1-5 DECnet/OSI for remote access, 1-6 NET$MANAGE identifier, qualifiers, 1-2, 1-9 A-5 Authorize utility, A-5 DECnet transport, 1-4 AUTOGEN utility Disk space requirements, changing system 2-6 parameters, 2-9 Displaying installation guide, 3-8 B__________________________ Displaying release notes, Blocks required, 2-6 3-6 ___________________________ E__________________________ Common Components, 1-10 Editing system files deleting version, A-21 shutdown, 4-4 required, 1-2 startup, 4-3 Components of gateway for ORACLE system, 1-1 F__________________________ function, 1-2 Files installed, C-1 Configurations of the gateway for ORACLE, 1-3 local access, 1-4 network access, 1-4 remote access, 1-6 Index-1 IVP (cont'd) G__________________________ invoking, 4-2 Gateway coordinator, 1-8 running, 4-1 providing information to time required, 4-1 users, 1-9 sample log, 4-2 Gateway for ORACLE L See DBI Gateway for ___________________________ ORACLE Logical name, C-2 Global pagelets LORA$IVP.COM command file, required for Common 4-2 Components for OpenVMS LORA$SHUTDOWN.COM command AXP file, 4-4 table, A-13 LORA$STARTUP.COM command Global pages file, 4-3 required for Common LORA$V31_ORACLE_VERSION Components for OpenVMS logical name, C-2 VAX table, A-13 M__________________________ Global sections Mounting media, 3-3 required for Common Multiple database access, Components for OpenVMS 1-7 VAX table, A-13 N__________________________ I NET$MANAGE identifier ___________________________ DECnet/OSI, A-5 Images installing as shared, A-8 O__________________________ Installation OpenVMS Authorize utility, mounting media, 3-3 steps of procedure, 3-5 A-4 Installation guide OpenVMS privileges displaying, 3-8 required, A-3 printing, 3-8 Optimization of requests, Installation Verification 1-3 Procedure ORACLE database, 1-3 See IVP accessing multiple, 1-7 Instances administrator, 1-8 multiple access, 1-7 providing information Invoking IVP, 4-2 to gateway Invoking VMSINSTAL, 3-3 coordinator, 1-9 IVP, 1-10 attach specification qualifiers, 4-1 Index-2 SQL$DEINSTALL_DELETE P__________________________ command procedure, A-21 Post-installation SQL$ image, A-18 IVP, 4-1 SQL$INT image, A-18 Printing installation guide SQL$MOD image, A-18 , 3-8 SQL$MSG image, A-18 Printing release notes, SQL$PRE image, A-18 3-6 SQL$SHR image, A-18 Privileges SQL$UTL_SHARE60 image, required for OpenVMS, A-3 A-18 SQL$UTL_SHAREnn image, Q A-18 ___________________________ SQL*Net, 1-10 Qualifiers to attach System privileges required specification, 1-2 for user accounts, 4-4 System shutdown files R__________________________ editing, 4-4 RDB$REMOTE account, A-22 System startup files RDB$SHARE image, A-17 editing, 4-3 Rdb/Dispatch, 1-2 RDBMSGS image, A-17 T__________________________ RDBSHR image, A-17 TCP/IP transport, 1-4 Release notes displaying, 3-6 U__________________________ printing, 3-6 User accounts Required software, 1-1 system privileges Running IVP, 4-1 attach specification required, 4-4 qualifiers, 4-1 User interface, 1-2 time required, 4-1 V__________________________ S__________________________ VMSINSTAL command procedure Sample installation, B-1 , A-3 SETPRV privilege, A-3 invoking, 3-3 Setting up OpenVMS system, example, 3-4 1-10 parameters, 3-3 Software required to run steps, 3-5 gateway for ORACLE, 1-1 terminating, 3-11 Space requirements, 2-6 SQL$CLUSTER_DEINSTALL60 command procedure, A-22 Index-3