Installation Verification Procedure for Oracle Database Provider for DRDA

Transcription

1 Installation Verification Procedure for Oracle Database Provider for DRDA

2 Disclaimer The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle s products remains at the sole discretion of Oracle.

3 Table of Contents Disclaimer... 2 Installation Verification Procedure... 4 Software Installation and Configuration... 5 Oracle Database Preparation... 7 DB2 Panels and SPUFI... 9 DB2 Communications Database Preparation SPUFI Package Binding Query Execution Conclusion INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

4 Installation Verification Procedure Installation of a new product often requires verification of it's configuration and operation with client application and network settings. This paper describes a simple procedure for validation of the Oracle Database Provider for DRDA. A complete example of configuration of the product, Oracle Database and DB2 for z/os client is provided. This example will utilize IBM's DB2 for z/os interactive SQL utility (SPUFI) as the client verification tool. This example assumes the following: Oracle Database Provider for DRDA and Oracle Database V or later, on a supported platform and operating system. IBM's DB2 V11.1 for z/os database system, on a supported z/series hardware and a supported release of z/os. From this paper you will take away the following key points: DRDA server configuration An understanding of key configuration parameters. DRDA users in the Oracle Database An understanding of the roles of a DRDA Administrator and a DRDA User. DB2 Communication Database A understanding of the basic networking parameters involved with a DB2 client application. Application Packages An understanding of what application Packages are and how the relate to the client applications using them. 4INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

5 Software Installation and Configuration Installation of Oracle Database Provider for DRDA software is performed using the Oracle Universal Installer. Refer to Chapter 3 (Installation and Configuration of Oracle Database Provider for DRDA) for details and example installation values. This example assumes installation is done in a stand-alone Oracle Home, separate from any existing Oracle Home. If, instead, the product is installed into an existing Oracle Database Home, then certain aspects of this example may be omitted. The following installation values are assumed: DRDA instance name drdaas This is a unique name used to address and manage a DRDA server. Host Name host.example.com Port Number 1446 RDB Map Name DRDAAS This is a database name used by DB2 clients to refer to the Oracle database. Connection Descriptor TNS(orcl) For the purposes of this example, the host name is assumed to be "host.example.com". Substitute with the correct host name. In some environments that support IPv6 networks, it maybe necessary to use the IPv4 address (eg: ) of the host machine instead of the host name. Host machines configured with deference to IPv6 may present a connectivity issue for DB2 client systems. If you are unsure whether your host and network are configured for IPv6, use the host's IPv4 address instead. Apply this value consistently in place of host.example.com throughout the rest of this example. To help simplify this example, it is assumed that both the Oracle Database Provider for DRDA instance and the Oracle Database reside on the same host, referred to as host.example.com. The Oracle Database may, of course, reside on a different host. In such a case, host.example.com would be associated with the DRDA instance only. Also, for the purposes of this example, there is an assumed TNS Names descriptor defined by the name orcl. This TNS entry connects to a valid Oracle Database on the same host as the DRDA instance, using the IPC protocol. Example of a TNS Descriptor entry defined in tnsnames.ora: orcl = (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=orcl)) (CONNECT_DATA=(SERVICE_NAME=orcl.example.com))) 5INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

6 Example of testing the TNS entry using tnsping: % tnsping orcl TNS Ping Utility for Linux: Version Production on 17-MAR :39:46 Copyright (c) 1997, 2016, Oracle. All rights reserved. Used parameter files: /odp4drdahome/oracle/network/admin/sqlnet.ora Used TNSNAMES adapter to resolve the alias Attempting to contact (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=orcl)) (CONNECT_DATA=(SERVICE_NAME=orcl.example.com))) OK (10 msec) Common errors you may encounter: TNS-12541: TNS:no listener This error typically means the database or it's listener are not up, or that something is incorrectly specified in the TNS descriptor. Review and confirm it's definition, paying attention to spelling. TNS-03505: Failed to resolve name This error typically means the spelling of the TNS entry is not consistent with the naming of the entry or that the TNSNAMES adapter has not been configured. Refer to the Oracle Database Net Services Administrator's Guide for additional information on defining TNS entries and naming adapter configuration. Please remember to create the TNS entry and test it via tnsping before proceeding. The resulting configuration file ($ORACLE_HOME/drdaas/admin/drdaas.ora) is as follows: drdaas.data_port=host.example.com:1446 drdaas.rdb_map=rdb(drdaas)->tns(orcl) drdaas.protoproc_trace="all/error/notimestamp" drdaas.identity=zos Start the DRDA server: $ drdactl start drdaas CMD> start drdaas Listening on port: (ADDRESS=(PROTOCOL=TCP)(HOST=host.example.com)(PORT=1446)) OK 6INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

7 Check the status of the DRDA server: $ drdactl status drdaas CMD> status drdaas Instance: drdaas (pid:12054) --Trace-- DPS_ADR_BASE = /odp4drdahome/oracle/log --Listen-- Cmd: [CMD] - (ADDRESS=(PROTOCOL=IPC)(KEY=dps_drdaas)) {Accepted 2} Port: [DATA_PORT#1] - (ADDRESS=(PROTOCOL=TCP)(HOST=host.example.com)(PORT=1446)) {Accepted 0} --Command-- Client: [CMD] - (@ ) --Ports-- --Workers-- --Sessions-- Session: [drdaas][cmd] -> Worker [CMD] OK Oracle Database Preparation Refer to Chapter 3 (Installation and Configuration of Oracle Database Provider for DRDA) for details. The following userids will be created in the Oracle database for this example: DRDADM DRDA Administrator DRDAUSR DRDA User The customer may substitute other names for these users as long as they are applied consistently to the rest of the example. Copy the following files from the Oracle Database Provider for DRDA Home to the Oracle Database Home under the same path: rdbms/admin/catdrdaas.sql rdbms/admin/prvtdpsadrda.plb rdbms/admin/prvtdpsadzoscat.plb rdbms/admin/prvtdpsadzossqlfun.plb drdaas/admin/drdapkg_db2.sql Setup the Oracle Database for DRDA usage: $ sqlplus /nolog SQL> connect SYS as SYSDBA Enter password: Connected. SQL> create tablespace SYSIBM datafile 'sysibm01.dbf' size 70M reuse extent management local segment space management auto online; 7INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

8 Create the DRDA Administrator: $ sqlplus /nolog SQL> connect SYS as SYSDBA Enter password: Connected. SQL> GRANT CONNECT, RESOURCE, UNLIMITED TABLESPACE, DRDAAS_ADMIN_ROLE TO DRDADM IDENTIFIED BY manager ; Create the DRDA User: $ sqlplus /nolog SQL> connect SYS as SYSDBA Enter password: Connected. SQL> GRANT CONNECT, RESOURCE, UNLIMITED TABLESPACE, DRDAAS_USER_ROLE TO DRDAUSR identified by drdausr ; Grant DRDA package binding & execute privileges: $ sqlplus /nolog SQL> connect DRDADM/manager Connected. Enter the OracleID under which the initial package BINDs will be made Use quotes (') if needed. DRDAUSR Enter default collection ID for package binding (usually NULLID) Use quotes (') if needed. NULLID Note: The Collection Id 'NULLID' used here is a default for this userid. The actual example uses two other Collection Ids for by SPUFIs packages (DSNESPCS and DSNESPRR), which the above script will grant explicit package privileges to. Once the verification procedure has been completed you may wish to remove specific privileges to these Collection Ids for security reasons. 8INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

9 DB2 Panels and SPUFI The remainder of this example involves using the DB2 ISPF panels and utilities. In many environments the logon proc will start ISPF automatically. In other environments the session begins in TSO and you must start ISPF manually. Logon to z/os with a userid that has access to a DB2 subsystem and start ISPF using which ever method is appropriate for your environment. Once ISPF is running, select the option to enter the DB2 interactive panels. Eg: ISPF Primary Option Menu Option ===> 0 Settings Terminal and user parameters User ID. : DB2USR1 1 View Display source data or listings Time... : 14:07 2 Edit Create or change source data Terminal. : Utilities Perform utility functions Screen.. : 1 4 TSO Commands Saved TSO Commands Language. : ENGLISH 5 Batch Submit job for language processing Appl ID. : ISR 6 Command Enter TSO or Workstation commands TSO logon : $ISPFUSR 7 Dialog Test Perform dialog testing TSO prefix: DB2USR1 8 SDSF Spool Search and Display Facility System ID : DB2SY 9 DB2 Options Select from Several DB2 Products MVS acct. : PS01 Release. : ISPF 6.3 S Secondary Additional Functions and Tools T Tech Technical Services Only R Racf Racf Commands In this example, you would select option #9 (DB2 Options). Next, select the DB2 environment to use for the test. Eg: DB2 Related Functions and Products OPTION ===> Omegamon - Version DB2I DB2 Interactive Functions (SPUFI) for V8.1 5 DB2I DB2 Interactive Functions (SPUFI) for V9.1 6 DB2I DB2 Interactive Functions (SPUFI) for V DB2I DB2 Interactive Functions (SPUFI) for V Quick Backup - Enter the Quick Backup and Restore Facility 9 Admin. Tool - Use the DB2 Administration Tool (DB2 v9.1 & v10.1 only) 10 Gateway - Issue Commands for Oracle Gateway Testing In this example, you would select option #7 (DB2I 11.1). 9INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

10 You would then be taken to the DB2 Primary Options Menu. Eg: DB2I PRIMARY OPTION MENU SSID: DSNB COMMAND ===> Select one of the following DB2 functions and press ENTER. 1 SPUFI (Process SQL statements) 2 DCLGEN (Generate SQL and source language declarations) 3 PROGRAM PREPARATION (Prepare a DB2 application program to run) 4 PRECOMPILE (Invoke DB2 precompiler) 5 BIND/REBIND/FREE (BIND, REBIND, or FREE plans or packages) 6 RUN (RUN an SQL program) 7 DB2 COMMANDS (Issue DB2 commands) 8 UTILITIES (Invoke DB2 utilities) D DB2I DEFAULTS (Set global parameters) X EXIT (Leave DB2I) Take note of the SSID at the top right of the screen. Contact your DB2 Admin to obtain the SSID of a DB2 subsystem you have authorization to use. If you need to change this to a different subsystem, use option #D to set the DB2 NAME before continuing. When instructed, you will invoke option #1, SPUFI to execute SQL against the DB2 system. The SPUFI start panel will look something like this: SPUFI SSID: DSNB ===> Enter the input data set name: (Can be sequential or partitioned) 1 DATA SET NAME... ===> DB2.SQL(IVP) 2 VOLUME SERIAL... ===> (Enter if not cataloged) 3 DATA SET PASSWORD ===> (Enter if password protected) Enter the output data set name: 4 DATA SET NAME... ===> DB2.OUTPUT (Must be a sequential data set) Specify processing options: 5 CHANGE DEFAULTS ===> YES (Y/N - Display SPUFI defaults panel?) 6 EDIT INPUT... ===> YES (Y/N - Enter SQL statements?) 7 EXECUTE... ===> YES (Y/N - Execute SQL statements?) 8 AUTOCOMMIT... ===> YES (Y/N - Commit after successful run?) 9 BROWSE OUTPUT... ===> YES (Y/N - Browse output data set?) For remote SQL processing: 10 CONNECT LOCATION ===> PRESS: ENTER to process END to exit HELP for more information You will need two datasets, pre-allocated. One to use with the editor to enter SQL statements. This is item #1, the input DATA SET NAME. In this example, this is a PDS named 'DB2.SQL' which is allocated under the users primary prefix (eg: DB2USR1). This data set is generally Org PO, Recfm FB and Recl 80. The member name 'IVP' will be the file used to edit SQL statements for this session. The other dataset will be used to contain the output from query execution. This is item #4, the output DATA SET NAME. In this example, this is a sequential dataset named 'DB2.OUTPUT'. This dataset is generally Org PS, Recfm VB and Recl INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

11 If you do not have suitable datasets for input and output available, please allocate them before proceeding. This can be accomplished using the top-level ISPF option 3 (Utilities) sub-option 2 (Data Set Utilities). DB2 Communications Database Preparation Execute the following DB2 SQL statements to insert the following records into the DB2 CDB. This should be done via SPUFI using a DB2 userid that has appropriate insert/update access to the CDB tables. Invoke SPUFI via the DB2 Option #1, fill in the dataset names and press enter to bring you to the Editor. Enter the following SQL statements: INSERT INTO SYSIBM.IPNAMES (LINKNAME,SECURITY_OUT,USERNAMES,IPADDR) VALUES ('DRDAHOST','P','O','host.example.com'); INSERT INTO SYSIBM.LOCATIONS (LOCATION,LINKNAME,PORT) VALUES ('DRDAAS','DRDAHOST','1446'); INSERT INTO SYSIBM.USERNAMES(TYPE,AUTHID,LINKNAME,NEWAUTHID,PASSWORD) VALUES ('O',' ','DRDAHOST','DRDAUSR', 'drdausr' ); The LOCATION name, 'DRDAAS', is the RDB Map Name of the Oracle Database. You will use it to address package Binding and SQL Statement execution later. Note that the LINKNAME, 'DRDAHOST' is arbitrary here, and used only within the context of the CDB entries here. You may choose any other name for this value, as long as you use it consistently in all three places above, it does not conflict with any already existing entries within the CDB tables, and as long as it meets the value constraints for the CDB table column (a VARCHAR(24) as of this writing). Remember to substitute any values as needed for the above. Exit the editor (usually by pressing F3 or using the EXIT command), and press enter to execute the statements. Once executed you should see successful output displayed showing the number of rows inserted for each statement. There should be 3 in total. If your userid does not have access to the CDB tables, you will see an error executing the INSERT statements. Contact your DB2 Admin and request insert/update/select access to the above table names. 11INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

12 SPUFI Package Binding Now, bind the following packages for SPUFI to the remote database: DSNESPCS.DSNESM68 DSNESPRR.DSNESM68 This will also validate the CDB entries, by making a connection to the DRDA server and performing the remote binding of the packages, as well as confirming that the remote user has been granted proper package privileges. This can be done via JCL running program IKJEFT01 with the following input: DSN SYSTEM(DSNB) BIND PACKAGE (DRDAAS.DSNESPCS) MEMBER(DSNESM68) - ACTION(ADD) ISOLATION(CS) LIB('DSNB10.GA.SDSNDBRM') BIND PACKAGE (DRDAAS.DSNESPRR) MEMBER(DSNESM68) - ACTION(ADD) ISOLATION(RR) LIB('DSNB10.GA.SDSNDBRM') Alternatively, these packages can be bound using the DB2 Option #5, BIND, sub-option #4, BIND PACKAGE. Here is an example panel for binding the first package: DSNESPCS.DSNESM68 COMMAND ===> BIND PACKAGE SSID: DSNB Specify output location and collection names: 1 LOCATION NAME... ===> DRDAAS (Defaults to local) 2 COLLECTION-ID... ===> DSNESPCS > Specify package source (DBRM or COPY): 3 DBRM: COPY: ===> DBRM (Specify DBRM or COPY) 4 MEMBER or COLLECTION-ID ===> DSNESM68 > 5 PASSWORD or PACKAGE-ID.. ===> > 6 LIBRARY or VERSION... ===> 'DSNB10.GA.SDSNDBRM' (Blank, or COPY version-id) OPTIONS... ===> (COMPOSITE or COMMAND) Enter options as desired: 8 CHANGE CURRENT DEFAULTS?.. ===> YES (NO or YES) 9 ENABLE/DISABLE CONNECTIONS? ===> NO (NO or YES) 10 OWNER OF PACKAGE (AUTHID).. ===> > (Leave blank for primary ID) 11 QUALIFIER... ===> > (Leave blank for OWNER) 12 ACTION ON PACKAGE ===> ADD (ADD or REPLACE) 13 INCLUDE PATH?... ===> NO (NO or YES) 14 REPLACE VERSION... ===> (Replacement version-id) PRESS: ENTER to process END to save and exit HELP for more information 12INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

13 COMMAND ===> DEFAULTS FOR BIND PACKAGE Top of data Change default options as necessary: Use the UP/DOWN keys to access all options More: + 1 ISOLATION LEVEL... ===> CS (CS, RR, RS, UR, or NC) 2 VALIDATION TIME... ===> (RUN or BIND) 3 RESOURCE RELEASE TIME... ===> (COMMIT, DEALLOCATE, or INHERITFROMPLAN) 4 EXPLAIN PATH SELECTION.. ===> (NO, YES, or ONLY) 5 DATA CURRENCY... ===> (NO or YES) 6 PARALLEL DEGREE... ===> (1 or ANY) 7 SQLERROR PROCESSING... ===> (NOPACKAGE or CONTINUE) 8 REOPTIMIZE FOR INPUT VARS ===> (ALWAYS, NONE, ONCE, or AUTO) 9 DEFER PREPARE... ===> (NO, YES, INHERITFROMPLAN) 10 KEEP DYN SQL PAST COMMIT. ===> (NO or YES) 11 APPLICATION ENCODING... ===> (Blank,ASCII,EBCDIC,UNICODE, or ccsid) 12 OPTIMIZATION HINT... ===> > (Blank or 'hint-id') 13 IMMEDIATE WRITE... ===> (NO, YES, INHERITFROMPLAN) 14 DYNAMIC RULES... ===> (RUN, BIND, DEFINE, or INVOKE) 15 DBPROTOCOL... ===> DRDA (blank, DRDA, or DRDACBF) 16 ACCESS PATH REUSE... ===> NONE (ERROR, NONE, or WARN) 17 ACCESS PATH COMPARISON.. ===> NONE (ERROR, NONE, or WARN) 18 SYSTEM_TIME SENSITIVE... ===> (blank, NO, or YES) 19 BUSINESS_TIME SENSITIVE. ===> (blank, NO, or YES) 20 ARCHIVE SENSITIVE... ===> (blank, NO, or YES) 21 APPLICATION COMPATIBILITY ===> (blank, V10R1, or V11R1) PRESS: ENTER to continue UP/DOWN to scroll RETURN to EXIT Output of execution should be: DSNT232I -NT SUCCESSFUL BIND FOR PACKAGE = DRDAAS.DSNESPCS.DSNESM68.(UK92200) *** 13INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

14 Common errors you may encounter during bind execution: DSNT408I SQLCODE = , ERROR: TCP/IP:SOCKETS::: :CONNECT:1128 : :0000: COMMUNICATIONS ERROR DETECTED. API=, LOCATION=, FUNCTION= The remote host name, IP Address or port number are not correctly configured in either the drdaas.ora or the DB2 CDB entries. Review both and correct as needed. ORA-06550: line 1, column 22::PLS-00201: identifier 'DBMS_DRDAAS' must be declared:ora-06550: line 1, column 7::PL/SQL: Statement ignored The remote Oracle DRDA user was not granted DRDAAS_USER_ROLE, or was not granted as a Default Role. Review the Oracle Database Preparation described earlier. DSNT408I SQLCODE = -551, ERROR: DRDAUSR DOES NOT HAVE THE PRIVILEGE TO PERFORM OPERATION BIND ON OBJECT <collid>.<package> The remote Oracle user was not granted bind privileges for the specific package or collection-id. Review the Oracle Database Preparation described earlier. Repeat the process to bind the second package, DSNESPRR.DSNESM68, using the same BIND PACKAGE panels, substituting the following values BIND PACKAGE SSID: DSNB 1 LOCATION NAME... ===> DRDAAS (Defaults to local) 2 COLLECTION-ID... ===> DSNESPRR > 3 DBRM: COPY: ===> DBRM (Specify DBRM or COPY 4 MEMBER or COLLECTION-ID ===> DSNESM68 > 6 LIBRARY or VERSION... ===> 'DSNB10.GA.SDSNDBRM' 8 CHANGE CURRENT DEFAULTS?.. ===> YES (NO or YES) 9 ENABLE/DISABLE CONNECTIONS? ===> NO (NO or YES) 12 ACTION ON PACKAGE ===> ADD (ADD or REPLACE) 13 INCLUDE PATH?... ===> NO (NO or YES) DEFAULTS FOR BIND PACKAGE 1 ISOLATION LEVEL... ===> RR (CS, RR, RS, UR, or NC) 15 DBPROTOCOL... ===> DRDA (blank, DRDA, or DRDACBF) 16 ACCESS PATH REUSE... ===> NONE (ERROR, NONE, or WARN) 17 ACCESS PATH COMPARISON.. ===> NONE (ERROR, NONE, or WARN) Output of execution should be: DSNT232I -NT SUCCESSFUL BIND FOR PACKAGE = DRDAAS.DSNESPRR.DSNESM68.(UK92200) *** 14INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

15 Query Execution The final step of verification is to execute a test query using SPUFI. Start SPUFI via DB2 Option #1. Specify 'DRDAAS' for option #10 (CONNECTION LOCATION). This is the RDB Map Name previously defined in the drdaas.ora file and in the DB2 CDB entries. Specifying this parameter tells SPUFI to execute an initial SQL CONNECT TO statement using this value for the location. Enter the following SQL and execute it: select NAME from ALL_DRDAASPACKAGE Output will look similar to this: NAME DSNESM68 DSNESM68 DSNE610I NUMBER OF ROWS DISPLAYED IS 2 DSNE616I STATEMENT EXECUTION WAS SUCCESSFUL, SQLCODE IS Successful execution of this query completes testing of end-to-end communication from DB2 to Oracle. The customer may wish to execute additional queries against tables in Oracle, that user DRDAUSR has select access to as further validation. Common errors you may encounter during query execution: DSNT408I SQLCODE = -805, ERROR: DBRM OR PACKAGE NAME DRDAAS..DSNESM68.149EEA9-01A79FE48 NOT FOUND IN PLAN DSNESPCS. REASON 02 DSNT418I SQLSTATE = SQLSTATE RETURN CODE DSNT415I SQLERRP = DSNXEPM SQL PROCEDURE DETECTING ERROR DSNT416I SQLERRD = SQL DIAGNOSTIC INFORMATION DSNT416I SQLERRD = X'FFFFFEA2' X' ' X' ' X'FFFFFFFF' X' ' X' ' SQL DIAGNOSTIC INFORMATION This error can occur if the DB2 subsystem instance was not initially installed with DDF support. Consult DB2 installation job DSNTIJSG. The plans for SPUFI need to be rebound with the Package List (PKLIST) specifying the wildcard ( * ) location qualifier on the packages so that DB2 may refer to any remote locations resources for these packages without restriction. Example commands: BIND PLAN(DSNESPCS) PKLIST(*.DSNESPCS.DSNESM68) - ISOLATION(CS) ACTION(REPLACE) BIND PLAN(DSNESPRR) PKLIST(*.DSNESPRR.DSNESM68) - ISOLATION(RR) ACTION(REPLACE) You may need to contact your DB2 Admin to update the SPUFI plans. Refer to IBM Technote swg , titled: SQLCODE805 when running SPUFI to SELECT data from a remote system 15INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

16 Conclusion This concludes the installation verification procedure for the Oracle Database Provider for DRDA. With this example in hand, customers can adapt the procedure to verify conversion of individual applications for remote processing against Oracle. 16INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

17 Oracle Corporation, World Headquarters Worldwide Inquiries 500 Oracle Parkway Phone: Redwood Shores, CA 94065, USA Fax: INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA

18 Author: Peter Castro Contributing Author: Roger Ford Date: May, INSTALLATION VERIFICATION PROCEDURE FOR ORACLE DATABASE PROVIDER FOR DRDA