Home

Oracle Transparent Gateway for DRDA Installation and User's Guide

1. Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate ENGTHB Yes Yes LN Yes Yes LOG Yes Yes OWER Yes Yes LPAD 5 Hi Yes Yes TRIM s H Yes Yes MAX Yes MIN Yes v MOD z Yes Yes MONTHS BETWEEN H Yes NEW TIME Yes NEXT_DAX Yes NLS_INITCAP s Yes Yes NLS_LOWER Yes Yes NLS_UPPER s Yes Yes NLSSORT gt Yes Yes NVL gt VALUE NVL2 z Yes Yes POWER 5 5 Yes Yes RAWTOHEX E Yes Yes REPLACE 7 Yes Yes REVERSE Yes Yes ROUND z Yes Yes ROWIDTOCHAR Yes RPAD 5 Yes Yes RTRIM E Yes Yes SIGN Yes Yes SIN Yes Yes SINH Yes Yes SOUNDEX Yes SQRT Yes Yes STDDEV Yes v Yes SUBSTR k z Yes Yes SUBSTRB Yes Yes 13 14 Oracle Transparent Gateway for DRDA Installation and User s Guide Oracle Database SQL Construct Processing Table 13 3 Cont DB2 400 SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate SUM Yes SYSDATE E z Yes TAN Yes z Yes TANH Yes Yes TO_CHAR z 7 Yes TO_DATE s Yes z TO_MULTI_BYTE z
2. Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate NVL VALUE NVL2 Yes Yes POWER zi 5 Yes Yes RAWTOHEX 7 Yes Yes REPLACE z A Yes Yes REVERSE 5 Yes Yes ROUND z Yes Yes ROWIDTOCHAR Yes RPAD 7 z Yes Yes RTRIM Yes Yes SIGN s Yes Yes SIN Yes Yes SINH m s Yes Yes SOUNDEX Yes SORT Yes Yes STDDEV H Z Yes Yes SUBSTR E H Yes Yes SUBSTRB Yes Yes SU Yes SYSDATE a Yes TAN A Yes Yes TANH 8 Yes Yes TO_CHAR Yes TO_DATE Yes TO_MULTI_BYTE Yes TO_NUMBER DECIMAL Yes TO_SINGLE_BYTE 3 7 Yes TRANSLATE Yes Yes TRIM gt STRIP Yes Yes TRUNC 5 Yes Yes UID Yes UPPER z Yes Yes USER 5 Yes USERENV 7 5 Yes Developing Applications 13 9 Oracle Database SQL Construct Processing Table 13 1 Cont SQL Compatibility by Oracle SQL function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate VARIANCE a Yes Yes VSIZE Yes Yes 13 5 6 DB2 Universal Database SQL Compatibility The ways that Oracle Database and gateway handle SQL functions for a DB2 UDB database are shown in the following table Table 13 2 DB2 Universal Database SQL Compatibility by Oracle SQL Function
3. Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate ABS Yes Yes ACOS z Yes Yes ADD_MONTHS Yes ASC a Yes Yes ASIN R s Yes Yes ATAN 5 Yes Yes ATAN2 z Yes Yes AVG Yes BITAND Yes Yes CAST s E Yes Yes CEIL CEILING Yes CHARTOROWID Yes CHR Yes Yes CONCAT Yes z CONVERT a 3 Yes Yes cos Yes 4 Yes COSH z Yes Yes COUNT Yes E COUNT DISTINCT Yes z colname COUNT ALL colname Yes s z COUNTCOL COUNT column Yes COUNTCOL DECODE a 7 Yes Yes DUMP a Yes Yes EXP Yes Yes 13 10 Oracle Transparent Gateway for DRDA Installation and User s Guide Oracle Database SQL Construct Processing Table 13 2 Cont DB2 Universal Database SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate FLOOR Yes Yes GREATEST z Yes Yes HEXTORAW 5 Yes Yes NITCAP 7 Yes Yes INSTR z E Yes Yes INSTRB Yes Yes LAST_DAY Yes LEAST 7 5 Yes Yes LENGTH z Yes Yes ENGTHB Yes Yes LN Yes v Yes LOG Yes Yes LOWER LCASE Yes LPAD
4. table DELETE RULE Delete rule for referential constraint STATUS Status of a constraint DEFERRABLE Whether the constraint is deferrable DEFERRED Whether the constraint was initially deferred VALIDATED Whether all data obeys the constraint GENERATED Whether the name of the constraint is user or system generated BAD Constraint specifies a century in an ambiguous manner LAST CHANGE When the constraint was last enabled INDEX OWNER N A INDEX NAME N A A 2 21 USER CONS COLUMNS Information about columns in constraint definitions owned by the user column name description OWNER Owner of the constraint definition CONSTRAINT_NAME Name associated with the constraint definition TABLE_NAME Name associated with table with constraint definition COLUMN_NAME Name associated with column specified in the constraint definition POSITION Original position of column in definition Oracle DB2 Data Dictionary Views A 11 Data Dictionary View Tables A 2 22 USER_INDEXES Description of the user s own indexes column name description INDEX_NAME Name of the index INDEX_TYPE Type of index TABLE_OWNER Owner of the in
5. Determine the user ID and password you will use for recovery Step 4 Determine DRDA location name for DB2 400 instance The DRDA location name is required as a gateway parameter To determine the location name issue the following SQL query from a STRSQL session If SQL is unavailable on the system then use the AS 400 command DSPRDBDIRE to identify your LOCAL DRDA Server SELECT CURRENT SERVER FROM any_table where any table isa valid table with one or more rows If the value returned by this query is blank or null then the DRDA location name has not been established Contact the system administrator to arrange to set a location name for the instance 5 4 DB2 UDB Universal Database Experience with DB2 UDB configuring the communication subsystem of DB2 UDB and the host System Administration tools is required to perform the following steps Step 1 Configure the SNA Communications Server a Step 2 Define the user ID that owns the package u Step 3 Define the recovery user ID a Step 4 Determine DRDA location name for DB2 UDB instance Step 1 Configure the SNA Communications Server If you are using SNA then configure the communications server for the connection from the host Configure DB2 UBD for SNA using the LU defined If you are using TCP IP then configure the TCP IP subsystem Configure DB2 UDB to use TCP IP and assign a Primary and Recovery port number for th
6. Multi byte codepages comprise a single byte codepage and a double byte codepage For example the Korean EBCDIC multi byte codepage CCSID 933 is composed of two codepages codepage 833 for single byte and codepage 834 for double byte The DRDA Server therefore can send data to the gateway in any of these three codepages and the gateway must translate appropriately depending upon which codepage the data is associated with Because CCSID 933 is an EBCDIC based codepage and the gateway must use an ASCII based codepage we identify an equivalent set of codepages which are ASCII based For example the Korean multi byte codepage CCSID 949 which is composed of two codepages codepage 1088 for single byte and codepage 951 for double byte The codepage map facility is used to map these CCSIDs into the equivalent Oracle Database Character Sets Unlike IBM CCSIDs Oracle Database Character Sets are unified in that single byte and double byte character sets have been combined into one set and are identified by one ID instead of three IDs In our previous example the equivalent Oracle Database Character Set for the ASCII Korean codepages would be KO16MSWIN949 and the EBCDIC Korean codepages would be KO16DBCS These are identified to the gateway by using a set of mapping entries in the codepage map file The EBCDIC Korean sets are S 833 gt KO16DBCS 4 Korean Extended single byte EBCDIC D 834 gt KO16DBCS
7. DISPLAY xstation10 us oracle com 0 export DISPLAY xsnaadmin amp Upon startup of xsnaadmin the main screen will open and display the current configuration of the local SNA node See Figure 6 1 Configuring SNAP IX Interfaces 6 3 Creating SNA Definitions for the Gateway Figure 6 1 xsnaadmin Main Screen Ele EVE Configuring the SNA node From the Services menu select Configure Node Parameters In the Node Parameters dialog box see Figure 6 2 enter the APPN support type Control Point Name Control Point Alias and Node ID as needed The Control Point Name is composed of the SNA Network Name and the CP name of the local host Click OK 6 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Creating SNA Definitions for the Gateway Figure 6 2 Node Parameters Dialog Box Adding a Port From the Services menu select Connectivity and New Port In the Add to lt nodename gt dialog box Figure 6 3 select the Port type and click OK Figure 6 3 Add to lt nodename gt Dialog Box In the SAP dialog box see Figure 6 4 enter a Port name and network card number The Port name will be used to logically name the physical network card that you are using and will be used to bind a Service Access Port to the card for SNA protocols Normally you can accept the values provided in the dialog box If a different network card is needed however enter the card number as reported with the
8. column name description TABLE_NAME Name of the object TABLE_TYPE Type of the object COMMENTS Comments on the object A 2 28 USER_USERS Information about the current user column name description USERNAME Name of the user USER_ID N A ACCOUNT_STATUS Indicates if the account is locked expired or unlocked LOCK_DATE Date on which the account was locked EXPIRE_DATE Date of expiration of the account DEFAULT TABLESPACE N A TEMPORARY_TABLESPACE N A CREATED N A A 16 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dictionary View Tables column name description EXTERNAL NAME Name of the external user A 2 29 USER_VIEWS Text of views owned by the user column name description VIEW_NAME Name of the view TEXT_LENGTH Length of the view text TEXT First line of the view text TYPE_TEXT_LENGTH Length of the type clause of the typed view TYPE_TEXT Type clause of the typed view OID_TEXT_LENGTH Length of the WITH OID clause of the typed view OID_TEXT WITH OID clause of the typed view VIEW_TYPE_OWNER Owner of the type of the view if the view is a typed view VIEW_TYPE Type of the view if the view is a typed view SUPERVIEW_NAME N A Oracle DB2 Data Dictionary Views A 17 Data Dictionary View Tables
9. u GTWDEBUG u INCREMENT_CURSORS a DRDA CALLDESC STMT m DRDA CALLDESC PROC 15 4 DRDA Server Considerations A part of the Normal Installation for the gateway involves binding a package and as an option installing data dictionary views on the DRDA Server This release of the gateway 10 2 0 is compatible with version 4 version 8 and version 9 packages that Migration and Coexistence with Existing Gateways 15 3 Oracle Net Considerations have been previously bound The data dictionary views however have changed with the 10 2 release If you plan to utilize the data dictionary views that are provided by the gateway then you must migrate to the new views Oracle recommends that you install the new views as discussed in Chapter 11 Configuring the Gateway If you have changed certain DRDA parameters of the Gateway Initialization parameters as a result of the migration then a rebind of the package will be required 15 5 Oracle Net Considerations The gateway uses the Heterogeneous Services HS facilities of Oracle Database and Oracle Net gateway service name entries in the tnsnames ora need a slight modification so that Oracle Net that the gateway will be using the HS facilities Refer to Configuring Oracle Net on page 10 3 for detailed information 15 4 Oracle Transparent Gateway for DRDA Installation and User s Guide 16 Error Messages Diagnosis and Reporting This cha
10. 13 9 Oracle Data Dictionary Emulation on a DRDA Server The gateway optionally augments the DRDA database catalogs with data dictionary views modeled on the Oracle data dictionary These views are based on the dictionary tables in the DRDA database presenting that catalog information in views familiar to Oracle users The views created during the installation of the gateway automatically limit the data dictionary information presented to each user based on the privileges of that user 13 9 1 Using the Gateway Data Dictionary The gateway data dictionary views provide users with an Oracle like interface to the contents and use of the DRDA database Some of these views are required by Oracle products The gateway supports the DB2 05390 DB2 400 and DB2 UDB catalog views DB2 VM catalog views are not available You can query the gateway data dictionary views to see the objects in the DRDA database and to determine the authorized users of the DRDA database Many Oracle catalog views are supported by the Oracle Transparent Gateway for DRDA Refer to Appendix A for descriptions of Oracle DB2 catalog views These views are completely compatible with the gateway Developing Applications 13 27 Defining the Number of DRDA Cursors 13 9 2 Using the DRDA Catalog Each DRDA database has its own catalog tables and views which you might find useful Refer to the appropriate IBM documentation for descriptions of these catalogs 13 10 Defining
11. A 14 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dictionary View Tables column name description INSTANCES Number of instances across which the table is to be scanned CACHE Whether the cluster is to be cached in the buffer cache TABLE_LOCK Whether table locking is enabled or disabled SAMPLE SIZE Sample size used in analyzing this table LAST_ANALYZED Date on which this table was most recently analyzed PARTITIONED Indicates whether this table is partitioned IOT_TYPE If this is an index organized table TEMPORARY Can the current session only see data that it placed in this object itself SECONDARY N A NESTED If the table is a nested table BUFFER_POOL The default buffer pool for the object ROW_MOVEMENT N A GLOBAL STATS N A USER STATS N A DURATION N A SKIP CORRUPT N A MONITORING N A CLUSTER OWNER N A DEPENDENCIES N A COMPRESSION N A A 2 26 USER TAB COLUMNS Columns of user s tables views and clusters column name description TABLE NAME Name of the table view or cluster COLUMN NAME Name of the column DATA TYPE Data type of column DATA TYPE MOD Data type modifier of the column DATA TYPE OWNER Owner of the data type of the column DATA LENGTH Maximum length of
12. For this option to function properly SNAPlus2 requires that the effective user ID under which the gateway is executing must be a member of the system group In UNIX terms this means that the user ID must be defined with its primary group set to system In addition the owning user ID of the gateway executable must be set to the desired effective user ID and the set uid bit of the executable file permissions must also be set The 1s 1 command shows the owning user ID and the setting of the set uid bit for the executable file The owning user ID can be changed by the root user with the chown command and the set uid bit can be set using the chmod u s command The gateway executable as installed by the Oracle Universal Installer has its set uid bit disabled The simplest way to cause the gateway to execute under an effective user ID that is a member of the system group is to change the owning user ID of the gateway executable to root Another way is to change the primary group for the owning user ID of the gateway executable to system However be careful when choosing 8 12 Oracle Transparent Gateway for DRDA Installation and User s Guide Testing the Connection the user ID Oracle recommends using root and recommends never changing the Oracle dba user ID primary group to system When the effective user ID is not a member of the system group a failure is generated when the gateway attempts to allocate a conversation with the DRDA Serv
13. Program Code UPDATE oratabl oraprocl ename empno sal INSERT oratab2fora2 oraproc2 fo ra2 ename empno sal oraproc2 Oracle Stored Procedure DECLARE BEGIN UPDATE oratabl INSERT oratab2 ora2 To maintain location transparency in the application a synonym can be created CREATE SYNONYM oraproc2 FOR oraproc2 ora2 After this synonym is created the application no longer needs to use the database link specification to call the stored procedure in the remote Oracle instance In Figure 13 1 the second statement in oraproc1 is used to access a table in the ORA2 instance In the same way Oracle stored procedures can be used to access DB2 tables through the gateway 13 3 Using DRDA Server Stored Procedures with the Gateway The procedural feature of the gateway enables invocation of native DRDA Server stored procedures In other words the stored procedure is no longer defined in the Oracle Database but is defined in the DRDA Server for example DB2 0S390 Again standard Oracle PL SQL is used by the Oracle application to run the stored procedure After the stored procedure is defined to the DRDA Server for example DB2 OS390 the gateway is able to use the existing DRDA Server definition to run the procedure The gateway does not require special definitions to call the DB2 stored procedure In Figure 13 2 an Oracle application calls the empproc stored procedure that is
14. The following example creates the table EMP in your local Oracle Database and inserts the rows from the EMP table on the DRDA Server CREATE TABLE EMP AS SELECT FROM scott EMP DRDA Alternatively you can use the SQL Plus COPY command to copy data from a DRDA Server to Oracle Database For more information about the COPY command refer to SQL Plus User s Guide and Reference 12 10 Tracing SQL Statements SQL statements issued through the gateway can be changed before reaching the DRDA database These changes are made to make the format acceptable to the gateway or to make Oracle SOL compatible with DRDA Server SQL Oracle Integrating Server and the gateway can change the statements depending on the situation For various reasons you might need to assess whether the gateway has altered the statement correctly or whether the statement could be rewritten to improve performance SQL tracing is a feature that allows you to view the changes made to a SQL statement by the Oracle Integrating Server or the gateway SOL tracing reduces gateway performance Use tracing only while testing and debugging your application Do not enable SQL tracing when the application is running in a production environment For more information about enabling SQL tracing refer to the section on SQL Tracing and the Gateway on page 16 5 in Chapter 16 Error Messages Diagnosis and Reporting Using the Oracle Transparent Gateway for DRDA 12 7 Tracing SQL S
15. These tables pertinent to inbound sessions have a role in security processing m SYSIBM LUNAMES table The SYSIBM LUNAMES table controls inbound security conduct on an SNA Logical Unit basis affecting all DRDA connections from a particular host system This table also controls whether inbound connection user IDs are subject to translation or mapping m SYSIBM SYSUSERNAMES table When translation is used rows in the SYSIBM SYSUSERNAMES table specify translated user IDs by Logical Unit LU name and inbound user ID Default entries that pertain to all LUs and to all inbound user IDs can be made in both tables The mapping table can also be used simply to indicate which inbound user IDs are permitted from a particular LU or from all LUs whether or not they are mapped This implementation provides a flexible mapping structure You can specify that all connections from a particular LU use a single DB2 user ID or that a particular inbound user ID always be mapped to a particular DB2 user ID regardless of origin A SYSUSERNAMES entry with blank LU name and inbound user ID can designate a single default DB2 user ID for all connections unless a more specific entry by LU name user ID or both exists The CDB tables can be updated by a user with update privilege using a SQL tool such as the DB2 SPUFI utility For example most database administrators systems programmers and security officers can upd
16. A zoned decimal field is described as packed decimal on Oracle Database However an Oracle application such as a Pro C program can insert into a zoned decimal column using any supported Oracle numeric data type The gateway converts this number into the most suitable data type Data can be fetched from a DRDA database into any Oracle data type provided that it does not result in a loss of information 13 8 Passing Native SQL Statements through the Gateway The passthrough SQL feature enables an application developer to send a SQL statement directly to the DRDA Server without the statement being interpreted by Oracle Database DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIATE SQL passthrough statements that are supported by the gateway are limited to nonqueries INSERT UPDATE DELETE and DDL statements and cannot contain bind variables The Developing Applications 13 25 Passing Native SQL Statements through the Gateway gateway can run native SQL statements using DBMS HS PASSTHROUGH EXECUTE IMMEDIATE DBMS HS PASSTHROUGH EXECUTE IMMEDIATE is a built in gateway function This function receives one input argument and returns the number of rows affected by the SOL statement For data definition language DDL statements the function returns Zero DBMS HS PASSTHROUGH EXECUTE IMMEDIATE are reserved names of the gateway and are used specifically for running n
17. DECLARE num rows integer BEGIN num rows DBMS HS PASSTHROUGH EXECUTE IMMEDIATECAblink INSERT INTO SCOTT DEPT VALUES 10 PURCHASING PHOENIX END 2 Create a table in DB2 using DBMS HS PASSTHROUGH EXECUTE IMMEDIATE DECLARE num rows integer BEGIN num rows lt DBMS HS PASSTHROUGH EXECUTE IMMEDIATEGAblink CREATE TABLE MYTABLE COL1 INTEGER COL2 INTEGER COL3 CHAR 14 COL4 VARCHAR 13 END 13 26 Oracle Transparent Gateway for DRDA Installation and User s Guide Oracle Data Dictionary Emulation on a DRDA Server 13 8 2 Retrieving Results Sets Through Passthrough Oracle Transparent Gateway for DRDA provides a facility to retrieve results sets from a SELECT SQL statement entered through passthrough Refer to Oracle Database Heterogeneous Connectivity Administrator s Guide for additional information 13 8 2 1 Example DECLARE CRS binary_integer RET binary_integer VAL VARCHAR2 10 BEGIN CRS DBMS_HS_PASSTHROUGH OPEN_CURSOR gtwlink DBMS_HS_PASSTHROUGH PARSEGgtwlink CRS SELECT NAME FROM PT_TABLE BEGIN RET 0 WHILE TRUE LOOP RET DBMS_HS_PASSTHROUGH FETCH_ROW gtwlink CRS FALSE DBMS_HS_PASSTHROUGH GET_VALUE gtwlink CRS 1 VAL INSERT INTO PT TABLE LOCAL VALUES VAL END LOOP EXCEPTION WHEN NO_DATA_FOUND THEN BEGIN DBMS_OUTPUT PUT_LINE END OF FETCH DBMS_HS_PASSTHROUGH CLOSE_CURSOREgtwlink CRS END END END
18. Following are some of the sophisticated Oracle Database 109 services available through the gateway SQL functions Your application can access all your data using Oracle SQL which is rich in features Advanced Oracle Database 10g server functions such as outer joins are available even if the target data stores do not support them in a native environment The method by which the gateways are integrated with the Oracle Database 10g server ensures that the latest features of each database release are always available immediately to the gateway Distributed capabilities Heterogeneous data can be integrated seamlessly because Oracle distributed capabilities such as JOIN and UNION can be applied against non Oracle data without any special programming or mapping Distributed query optimization The Oracle Database 10g can utilize its advanced query optimization techniques to ensure that SQL statements are executed efficiently against any of your data The data distribution and storage characteristics of local and remote data are equally considered Two phase commit protection The database server two phase commit mechanism provides consistency across data stores by ensuring that a transaction that spans data stores is still treated as a single unit of work Changes are not committed or permanently stored in any data store unless the changes can be committed in all data stores that will be affected Stored procedures and database trig
19. DANN nn na na na na NNN NNNNNN NUNN 278 S8EBCDIC278 Finland Sweden 280 I8EBCDIC280 Italy 284 WE8EBCDIC284 Latin America Spain 285 WE8EBCDIC285 United Kingdom 297 F8EBCDIC297 France S 420 AR8EBCDICX Arabic Bilingual USA English 420 AR8XBASIC Arabic Bilingual USA English 424 IW8EBCDIC424 Israel Hebrew 437 US8PC437 Personal Computer USA 500 WE8EBCDIC500 International 813 EL8IS08859P7 Greek 819 WE8IS08859P1 ISO ANSI Multilingual 838 TH8TISEBCDIC Thai w Low Tone Marks amp Ancient Chars 850 lt USTASCII Multilingual Page Personal Computer 850 WE8PC850 Multilingual Page Personal Computer 864 AR81S08859P6 Arabic Personal Computer 870 EE8EBCDIC870 Latin 2 Multilingual ROECE 871 WE8EBCDIC871 Iceland CECP 875 EL8EBCDIC875 Greece 904 gt USTASCII Traditional Chinese PC Data 912 EE8IS08859P2 Latin 2 8 bit 916 IW8IS08859P8 Israel Hebrew 1025 CL8EBCDIC1025 Cyrillic Multiling 1086 IW8EBCDIC1086 Israel 1252 WE8MSWIN1252 Latin 1 MS Windows 1253 EL8MSWIN1253 Greek MS Windows 28709 gt WE8EBCDIC37 United States Canada CP28709 CP37 Multi byte codepage mappings S 833 gt KO16DBCS 4 Korean Extended single byte D 834 gt KO16DBCS shift Korean double byte M 933 KO16DBCS shift Korean Mixed multi byte MBC 933 833 834 Korean Mixed multi byte S 1088 gt KO16MSWIN949 Korean KS singl
20. 2 4 date arithmetic 2 4 DD basic tables and views 2 3 dictionary views not provided for DB2 VM 2 5 DRDA Server character sets 2 4 GLOBAL_NAMES parameter 2 4 INSERT Oracle SQL command 2 3 LONG datatype in SQL Plus 2 5 null values and stored procedures 2 4 Oracle ROWID column 2 6 row length limitation 2 5 SAVEPOINT 2 4 single gateway instances per DRDA network interface 2 5 string concatenation 2 4 SUBSTR function post processed 2 3 Korn shell setting ORACLE_HOME variable 4 3 L LANGUAGE parameter D 5 languages access through the gateway 1 6 SQL Plus 1 6 lanscan command 6 5 8 5 link station creating 6 6 8 6 parameters 6 8 8 7 testing SNA connection 6 13 8 13 link also see Database Link 13 5 linkage conventions SIMPLE WITH NULLS 13 5 listener B 2 LISTENER keyword B 2 listener ora file 10 3 sample B 2 literal character literals 13 22 date 13 22 specific datatype 13 20 TO_DATE format support 13 24 log file gateway installation 4 4 LOG_DESTINATION parameter defined C 10 file name or path name 16 6 SQL tracing 16 6 with ORACLE_DRDA_TRACE C 11 logging LOG DESTINATION C 10 Logical Unit LU IBM Communication Server product on AIX 7 4 SNAP IX product on Solaris 6 11 SNAPlus2 product on HP UX 8 11 Login as DBA 4 2 LONG datatype 13 21 LONG RAW datatype 13 21 LU dependent additional SNAPlus2 configuration needed 6 2 8 2 Side Information Profiles SNAP IX product on S
21. A 18 Oracle Transparent Gateway for DRDA Installation and User s Guide Sample Files This appendix contains a sample Gateway Initialization files and tnsnames ora and listener ora files of Oracle Net This appendix contains the following sections u Sample Gateway Initialization File ua Sample Oracle Net tnsnames ora File u Sample Oracle Net listener ora File B 1 Sample Gateway Initialization File The following Gateway Initialization File initdrdahoal ora needs customization For information on customizing this file refer to Configuring the Host on page 11 3 in Chapter 11 Configuring the Gateway Also refer to Appendix C HS specific parameters FDS_CLASS TG4DRDA_DB2MVS TRACE_LEVEL 255 LOG_DESTINATION DB2 log ORACLE DRDA TCTL debug tetl HS COMMIT POINT STRENGTH 255 HS NLS DATE FORMAT YYYY MM DD HS LANGUAGE AMERICAN AMERICA WE8ISO8859P1 HS RPC FETCH REBLOCKING off S_RPC_FETCH_SIZE 32767 S_FDS_FETCH_ROWS 20 DRDA specific parameters DA_CONNECT_PARM DRDACON1 DA_REMOTE_DB_NAME DB2V7R1 DA_PACKAGE_COLLID ORACLE DA_PACKAGE_NAME G2DRSQL DA_PACKAGE_CONSTOKEN A92617CB3FE54701 DA_RECOVERY_USERID ORADRDA DA_RECOVERY_PASSWORD ORADRDA DA_ISOLATION_LEVEL CS RDA_PACKAGE_OWNER ORADRDA RDA_DISABLE_CALL TRUE VUVUUUUUUuUY GOR DDD DW dw Sample Files B 1 Sample Oracle Net tnsnames ora File B 2 Sample Oracle Net tnsnames ora File For information on modifying your tnsnames ora file f
22. A 2 24 USER_SYNONYMS The user s private synonyms column name description SYNONYM_NAME Name of the synonym TABLE OWNER Owner of the object referenced by the synonym TABLE NAME Name of the object referenced by the synonym DB_LINK N A A 2 25 USER_TABLES Description of the user s own tables column name description TABLE_NAME Name of the table TABLESPACE NAME Name of the tablespace containing the table CLUSTER NAME N A IOT NAME Name of the index organized table PCT FREE N A PCT USED N A INI_TRANS N A MAX_TRANS N A INITIAL_EXTENT N A NEXT_EXTENT N A MIN_EXTENTS N A MAX EXTENTS N A PCT_INCREASE N A FREELISTS Number of process freelists allocated to a segment FREELIST_GROUPS Number of freelist groups allocated to a segment LOGGING Logging information BACKED_UP N A NUM_ROWS Number of rows in the table BLOCKS N A EMPTY_BLOCKS N A AVG_SPACE N A CHAIN_CNT N A AVG_ROW_LEN Average length of a row in the table in bytes T AVG_SPACE_FR ELIST BLOCKS Average freespace of all blocks on a freelist NUM FREELIST BLOCKS Number of blocks on the freelist DEGREE Number of threads per instance for scanning the table
23. BIND privilege DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 Index 2 bind variables known restrictions SQL limitations 2 6 SQL passthrough 13 25 BINDADD authority 11 5 BINDADD privilege DB2 05390 5 2 DB2 UDB 5 5 DB2 VM 5 6 BINDAGENT privilege DB2 0S390 5 2 DB2 VM 5 6 binding the DRDA package backward compatibility 15 3 configuring the gateway on DB2 UDB 11 4 configuring the gateway on DRDA Server 11 4 DB2 400 5 3 DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 gateway pre binding checklist 11 5 Bourne shell setting ORACLE_HOME variable 4 3 bug debugging debug library 16 6 drc values in the DRDA software 16 2 setting trace parameters 16 5 SQL tracing 12 7 number 205538 known restrictions SOL limitations 2 6 c C shell setting ORACLE_HOME variable 4 3 call a CICS or IMS transaction 13 5 DB2 stored procedure 13 3 13 4 DRDA_DISABLE_CALL 11 5 B 1 empproc stored procedure 13 3 Oracle Call Interfaces 16 1 PL SQL 13 4 stored procedure creating a synonym to maintain location transparency 13 3 using standard Oracle PL SQL 13 2 to stored procedure known restrictions 2 4 capabilities of DRDA Server native semantics 13 18 CCSID 65535 as the default for all tables created C 3 codepage mapping facility D 6 description D 3 external mapping to Oracle character sets supported 1 14 CCSID coded character set identifiers defined D 8 CD ROM drive requirements 3 2 changed parameters 15 2 changes in
24. C 6 DRDA MBCS TO GRAPHIC C 6 DRDA OPTIMIZE OUERY 12 4 C 6 DRDA PACKAGE COLLID 16 3 C 6 DRDA PACKAGE CONSTOKEN C 7 DRDA PACKAGE NAME 16 3 C 7 DRDA PACKAGE OWNER C 7 DRDA PACKAGE SECTIONS C 8 DRDA READ ONLY C 8 Index 13 DRDA RECOVERY PASSWORD C 8 DRDA RECOVERY USERID C 8 DRDA REMOTE DB NAME C 9 DRDA SECURITY TYPE C 9 HS FDS FETCH ROWS C 10 HS LANGUAGE C 10 HS NLS NCHAR C 10 LOG DESTINATION C 10 ORA MAX DATE C 11 ORA NLS33 C 1l ORACLE DRDA TCTL C 11 ORACLE DRDA TRACE C 11 TRACE LEVEL C 11 HS_DB_DOMAIN known restrictions 2 4 HS_NLS_DATE_FORMAT 13 24 HS_RPC_FETCH_REBLOCKING 1 11 13 2 HS_RPC_FETCH_SIZE 1 11 13 2 LOG_DESTINATION C 11 LOG_DESTINATON 16 6 OPEN_LINKS 12 3 USING modifying tnsnames ora file 10 3 partner LU creating on HP UX 8 8 creating on Solaris 6 9 partner LU alias 7 3 passthrough gateway features 1 11 native DB2 SQL 1 5 send SQL statement directly to DRDA Server 13 25 patch set Oracle integrating server requires the latest released patch set 3 3 patches required for IBM Communications Server for AIX 3 3 performance 13 18 performance enhancements with fetch reblocking 13 2 PL SQL call 13 4 DRDA stored procedures 13 3 records 13 5 routine 1 6 standard Oracle 1 6 stored procedure 13 2 port 6 6 8 6 adding for SNA 6 5 8 5 name adding for SNA 6 5 8 5 port number 446 as default for DRDA services TCP IP 9 1 5000 as default for DRDA service
25. Oracle Database and Oracle gateways across different CPUs or operating systems It also supports communication across different Oracle Databases and CPUs providing distributed database and distributed processing capabilities Oracle Net also allows applications to connect to multiple Oracle Database or gateways across a network selecting from a variety of communications protocols and application program interfaces APIs to establish a distributed processing and distributed database environment A communications protocol is a set of implemented standards or rules governing data transmission across a network An API is a set of subroutines providing an interface for application processes to the network environment Distributed Processing Dividing processing between a front end computer running an application and a back end computer used by the application is known as distributed processing Oracle Net enables an Oracle tool or application to connect to a remote computer containing Oracle Database or Oracle Gateway Distributed Database Several databases linked through a network appearing as a single logical database are known as a distributed database An Oracle tool running on a client computer or on Oracle Database running on a host computer can share and obtain information retrieved from other remote Oracle Database Regardless of the number of database information sources you might be aware of only one logical database Terminology
26. SNA Conversation Security 7 6 Oracle Transparent Gateway for DRDA Installation and User s Guide 8 Configuring SNAPlus2 This chapter describes configuring the SNAPlus2 product on HP UX for usage with the Oracle Transparent Gateway for DRDA SNAPlus2 provides SNA connectivity through the APPC LU6 2 protocol between the HP9000 host and the remote DRDA Server This chapter to provide more information creating server profiles This chapter contains the following sections Checklist for Configuring the Communications Interfaces Before You Begin SNAPlus2 Configuration Tool Creating SNAPlus2 Profiles for the Gateway Independent Versus Dependent LUs Creating SNA Definitions for the Gateway Using SNA Session Security Validation Testing the Connection 8 1 Checklist for Configuring the Communications Interfaces The checklists for configuring the communications interfaces are Creating SNAPlus2 Profiles for the Gateway Creating SNA Definitions for the Gateway Testing the Connection 8 2 Before You Begin You need to provide values for parameters unique to your system in order to properly configure SNAPlus2 Refer to Appendix E for a worksheet listing all of the installation parameters you will need to know before you can complete the configuration process Ask your network administrator to provide you with these parameters before you begin 8 3 SNAPlus2 Configuration Tool All SNAPlus2 product configuration is done usi
27. Step 1 Configure the Communications Server ua Step 2 Define the user ID that owns the package u Step 3 Define the recovery user ID m Step 4 Determine DRDA location name for DB2 instance u Step 5 Configure DB2 Distributed Data Facility for Gateway DB2 400 Step 1 Configure the Communications Server u Step 2 Define the user ID that owns the package m Step 3 Define the recovery user ID u Step 4 Determine DRDA location name for DB2 400 instance DB2 UDB Universal Database u Step 1 Configure the SNA Communications Server u Step 2 Define the user ID that owns the package Configuring the DRDA Server 5 1 DB2 05390 Step 3 Define the recovery user ID m Step 4 Determine DRDA location name for DB2 UDB instance DB2 VM u Step 1 Configure the Communications Server m Step 2 Define the user ID that owns the package Step 3 Define the Recovery user ID a Step 4 Determine DRDA location name for DB2 VM Instance 5 2 DB2 0S390 Experience with OS 390 MVS TSO VTAM and DB2 is required to perform the following steps Step 1 Configure the Communications Server If you are using SNA then configure OS 390 MVS VTAM for the SNA LU6 2 connection from the host Configure DB2s DDF for SNA using the LU defined If you are using TCP IP then configure the TCP IP subsystem configure DB2s DDF to use TCP IP and assign a primary and recovery port number for the DB2 server Step 2 Define the user ID that owns the packag
28. TABLE_NAME Table or view name COLUMN_NAME Column name Oracle DB2 Data Dictionary Views A 7 Data Dictionary View Tables column name description DATA_TYPE Data type of the column DATA_TYPE_MOD Data type modifier of the column DATA_TYPE_OWNER Owner of the data type of the column DATA_LENGTH Maximum length of the column in bytes DATA_PRECISION N A DATA_SCALE Digits to the right of decimal point in a number NULLABLE Whether the column permits nulls Value is n if there is a NOT NULL constraint on the column or if the column is part of a PRIMARY key COLUMN_ID Sequence number of the column as created DEFAULT_LENGTH N A DATA_DEFAULT N A NUM_DISTINCT Number of distinct values in each column of the table OW_VALUE For tables with more than three rows the second lowest and second highest values These statistics are expressed in hexadecimal notation for the internal representation of the first 32 bytes of the values HIGH_VALUE N A DENSITY N A NUM_NULLS Number of nulls in the column NUM_BUCKETS Number of buckets in histogram for the column AAST_ANALYZED Date on which this column was most recently analyzed SAMPLE SIZE Sample size used in analyzing this column CHARACTER_SET_NAME Name of the character set CHAR_COL_DECL_LE
29. TO_DATE Yes TO_MULTI_BYTE Yes TO_NUMBER z E Yes Yes TO_SINGLE_BYTE Yes Developing Applications 13 17 Native Semantics Table 13 4 Cont DB2 VM SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate TRANSLATE x Yes Yes TRIM s Yes Yes TRUNC Yes Yes UID Yes UPPER Yes Yes USER z Yes USERENV E Yes VARIANCE Yes Yes VSIZE Yes Yes 13 6 Native Semantics Because some of the advanced SQL constructs that are supported by Oracle Database may not be supported in the same manner by the DRDA database the Oracle Database compensates for the missing or incompatible functionality by post processing the DRDA database data with Oracle Database functionality See Also Oracle Database SQL Construct Processing on page 13 6 for more information This feature provides maximum transparency but may impact performance In addition new versions of a particular DRDA database may implement previously unsupported functions or capabilities or they may change the supported semantics as to make them more compatible with Oracle Database functions Some of DRDA Servers also provide support for user defined functions The user may choose to implement Oracle Database functions natively in the DRDA data
30. Using the Oracle Transparent Gateway for DRDA The DQO capability is useful for optimizing queries that access large amount of data but it can add overhead to small queries This parameter is valid only if the DRDA Server is DB2 OS390 or DB2 VM If the DRDA Server is DB2 400 or DB2 UDB then you must set the value to FALSE C 4 20 DRDA_PACKAGE_COLLID Default value ORACLE C 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Initialization File Parameters Range of values An alphanumeric string 1 to 18 characters in length Syntax DRDA_PACKAGE_COLLID collection_id DRDA_PACKAGE_COLLID specifies the package collection ID Note that in DB2 400 the collection ID is actually the name of an AS 400 library Note Any change to this parameter requires you to rebind the package C 4 21 DRDA_PACKAGE_CONSTOKEN Default value None use the sample provided Range of values A 16 digit hexadecimal number Syntax DRDA_PACKAGE_CONSTOKEN hexnum DRDA_PACKAGE_CONSTOKEN specifies the package consistency token This is a 16 digit hexadecimal representation of an 8 byte token Oracle Corporation recommends that you do not change the consistency token The consistency token used at runtime must match the one used when the package is bound The value depends on the DRDA Server being used Note Any change to this parameter requires you to rebind the packa
31. accessible to all of our customers For more information visit the Oracle Accessibility Program Web site at http www oracle com accessibility Accessibility of Code Examples in Documentation Screen readers may not always correctly read the code examples in this document The conventions for writing code require that closing braces should appear on an otherwise empty line however some screen readers may not always read a line of text that consists solely of a bracket or brace Accessibility of Links to External Web Sites in Documentation This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites TTY Access to Oracle Support Services Oracle provides dedicated Text Telephone TTY access to Oracle Support Services within the United States of America 24 hours a day seven days a week For TTY support call 800 446 2398 Related Documents xiv The Oracle Transparent Gateway for DRDA Installation and User s Guide for UNIX is included as part of your product shipment Also included is Oracle Database Heterogeneous Connectivity Administrator s Guide This guide contains information common to all heterogeneous gateways including important information on functions parameters and error messages Oracle Database Administrator s Guide Oracle Database Concepts Oracl
32. creation in the CREATE DATABASE statement All data columns of type CHAR VARCHAR2 and LONG have their data stored in the database character set For detailed information refer to Client and Oracle Integrating Server Configuration on page D 3 Oracle ORA_NLS10 It is environment variable ORA NLS10 determines where Transparent the gateway loads its character sets and other language Gateway for data For detailed information refer to Gateway DRDA Language Interaction with DRDA Server on page D 4 Oracle NLS_LANG It is environment variable NLS_LANG defines the Transparent character set used for communication between the Gateway for gateway and the Oracle integrating server For detailed DRDA information refer to Gateway Language Interaction with DRDA Server on page D 4 Oracle HS_LANGUAGE It is initialization parameter HS_LANGUAGE defines the Transparent character set used for communications between the Gateway for gateway and the DRDA Server For detailed information DRDA refer to Gateway Language Interaction with DRDA Server on page D 4 D 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Client and Oracle Integrating Server Configuration Table D 1 Cont Parameters Needed for NLS Processing in Your Systems Environments Environment Parameter or Variable Description Oracle HS_NLS_NCHAR It is initialization parameter HS_NLS_NCHAR defines the Transparent NCHAR character set
33. enter the name of the local LU and an alias This name must correspond to the VTAM definitions on the remote DRDA Server host for the HP9000 host Click OK Figure 8 9 Local LU Dialog Box Creating Partner LUs Now define a Partner LU which represents the LU that the DRDA Server is using to communicate From the Services menu select APPC and Add Partner LUs and Partner LU on Remote Node In the dialog box see Figure 8 10 enter the Partner LU name and characteristics The Partner LU name will contain the SNA Network Name as well 8 8 Oracle Transparent Gateway for DRDA Installation and User s Guide Creating SNA Definitions for the Gateway as the LU name of the remote LU Enable parallel session support The location is the name as the Remote Node name Click Location for a list Click OK Figure 8 10 Partner LU Dialog Box Creating Mode and CPI C Profiles After the local and remote LU definitions have been made create the necessary Mode and CPI C definitions From the Services menu select APPC and Modes In the Modes dialog box see Figure 8 11 click Add to add a new mode Figure 8 11 Modes Dialog Box In the Mode dialog box see Figure 8 12 enter the Mode Name and other session parameters The prescribed name for a DRDA mode is IBMRDB Contact your Remote Host system administrator for appropriate mode parameters Click OK Configuring SNAPlus2 8 9 Creating SNA Definitions for the Gateway Figure
34. even though data might be widely distributed If data is moved from a DRDA Application Server database to an Database server then no changes in application design or function are needed The gateway handles all differences in both data types and SQL functions between the application and the database 1 3 Gateway Capabilities Oracle Transparent Gateway for DRDA gives you the power to integrate your heterogeneous system into a single seamless environment This integration enables you to make full use of existing hardware and applications throughout your corporate wide environment You can eliminate the need to rewrite applications for each configuration and you can avoid the tedious error prone process of manual data transfer Together with the Oracle tools networking and data server technology the Oracle Transparent Gateway for DRDA sets a high standard for seamless enterprise wide information access 1 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Capabilities Oracle Transparent Gateway for DRDA enables applications to read and update DB2 data and Oracle data as if all of the data were stored in a single database As a result end users and application programmers are not required to know either the physical location or the storage characteristics of the data This transparency not only enables you to integrate heterogeneous data seamlessly it simplifies your gateway implementation application developm
35. 1 service port number DRDA CONNECT PARM C 3 Service TP 07F6C4C2 6 10 8 10 session authorization 6 11 8 10 connection 13 5 set operators compatibility SQL Set Clauses 13 20 EXCEPT SQL Set Clauses 13 20 INTERSECT SQL Set Clauses 13 20 MINUS SQL Set Clauses 13 20 shift attribute multi byte support D 9 SID also see Gateway System Identifier 11 2 choosing for gateway 11 2 configuring additional DRDA Server instances 11 8 definition 11 2 side information profile communication errors 16 2 creating 6 10 8 10 defining to use dependent LUs 6 2 8 2 description and role 6 2 8 2 profile types 7 3 specifies Local LU profilename 7 2 SIMPLE linkage convention gateway support 13 5 sample DB2 stored procedure G 1 single threaded conversations for dependent LUs 6 2 8 2 site autonomy 1 7 SNA Index 16 APPC 7 1 8 1 configuring DB2 400 5 3 configuring DB2 08390 5 2 configuring DB2 UDB 5 4 configuring DB2 VM 5 6 configuring server profiles 7 1 connectivity via APPC 6 1 conversation security 6 12 7 4 8 11 CPI C error 16 2 definitions 6 3 8 3 creating for SNAP IX 6 3 creating for SNAplus2 8 3 creating for the gateway 6 2 8 2 maintenance 6 2 8 2 facilities 1 12 functions 1 9 LU 7 2 network 6 3 8 3 name in creating partner LUs 6 9 8 8 profile 11 8 profile definitions 7 1 profiles 6 2 8 2 protocol 1 8 6 5 8 5 remote access 1 12 sample profile definitions 7 2 securi
36. 12 3 Accessing AS 400 File Members Nothing specific to DRDA or to the gateway controls the access to AS 400 files and file members However DB2 400 uses a naming convention that implies that the file member name is the same as the name of the file being addressed For example accessing schema table implies that table is the file name and also that table is the file member name being accessed Using the Oracle Transparent Gateway for DRDA 12 3 Using the Synonym Feature To access file members with names that differ from the associated file name you must create a view within the file so that DB2 400 can reference the correct file member One method for creating this view involves issuing the console command Create Logical File CRTLF This action creates a logical association between the file name and the file member name See Also For additional information refer to the AS 400 Command documentation or to the DB2 400 SQL reference document 12 4 Using the Synonym Feature You can provide complete data location and network transparency by using the synonym feature of Oracle Database When a synonym is defined the user need not know the underlying table or network protocol being used A synonym can be public which means it is available to all Oracle users A synonym can also be defined as private available only to the user who created it Refer to Oracle Database Reference for details on the synonym feature The following
37. 127 VARGRAPHIC VARCHAR2 2N IN lt 1000 LONG 1000 lt N lt 16370 13 20 Oracle Transparent Gateway for DRDA Installation and User s Guide DRDA Data type to Oracle Data type Conversion Table 13 6 Cont data type Mapping and Restrictions DRDA Server Oracle External Criteria LONG VARGRAPHIC VARCHAR2 2N IN lt 1000 ILONG 1000 lt N lt 16370 Floating Point Single IFLOAT 21 n a Floating Point Double FLOAT 53 n a Decimal P S NUMBER P S n a 13 7 1 Performing Character String Operations The gateway performs all character string comparisons concatenations and sorts using the data type of the referenced columns and determines the validity of character string values passed by applications using the gateway The gateway automatically converts character strings from one data type to another and converts between character strings and dates when needed Frequently DRDA databases are designed to hold non character binary data in character columns Applications executed on DRDA systems can generally store and retrieve data as though it contained character data However when an application accessing this data runs in an environment that uses a different character set inaccurate data may be returned With the gateway running on the host character data retrieved from a DB2 400 DB2 0S390 or DB2 VM host is translated from EBCDIC to ASCII When character data is sent to DB2 400 DB2 05390 or DB2
38. 3965425 ORA 07445 _MEMCPY 772 REPEATABLE READ ISOLATION LEVEL IS NOT WORKING 3709345 PSR 9 2 0 5 0 BREAKS CALL DB2 STORED PROCEDURE WITH DECIMAL PARM SQLCODE 310 2 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Known Restrictions 3130329 TG4DRDA LOOPS IF QRWTSRVR JOB KILLED WHILE GATEWAY IS IN GDJCRCV 2 5 Known Problems The problems that are documented in the following section are specific to the Oracle Transparent Gateway for DRDA and are known to exist in this release of the product These problems will be fixed in a future gateway release If you have any questions or concerns about these problems contact Oracle Support Services A current list of problems is available online Contact your local Oracle office for information about accessing this online information 2 6 Known Restrictions The following restrictions are known to exist for the products in the 10g release Restrictions are not scheduled to change in future releases Refer to Chapter 13 Developing Applications for information or limitations when developing your applications Accessing DB2 Alias Objects If you need to access DB2 alias objects on a remote DB2 system then you must specify DRDA_DESCRIBE_TABLE FALSE initialization parameter in the Gateway Initialization File Oracle SQL Command INSERT When copying data from an Oracle Database to a DRDA Server the Oracle SQL command INSERT is not sup
39. 4 for information 11 8 Accessing the Gateway from Other Oracle Databases Perform the following steps for each of the Oracle Database servers from which you want to access the gateway 1 Create a database link with which to access the gateway 2 Ifneeded define synonyms and views for tables accessed through the gateway 3 Perform GRANT statements for the synonyms and views you create Provide local or Oracle Net access from the Oracle Database servers to the gateway Configuring the Gateway 11 7 Accessing Other DRDA Servers 11 9 Accessing Other DRDA Servers To access other DRDA Servers from the Oracle integrating server use the following steps 1 Configure another SNA profile set for the DRDA Server Only Side Information and Partner LU Profiles must be new You can point to existing configuration information for other profiles unless you need to modify other aspects of the connection For example if you are using a different network adapter then you must configure an entire SNA profile set No additional profiles need to be configured for TCP IP Configure additional DRDA Server instances To configure an additional instance create new Gateway Initialization Files If you are using Oracle Net then add entries to the Listener ora file and tnsnames ora file with the new SIDs Other components including the gateway ORACLE_HOME directory structure can be shared among multiple gateway instances Bind the D
40. 5 DRDA LOCAL NODE NAME parameter C 6 DRDA MBCS TO GRAPHIC parameter C 6 DRDA OPTIMIZE OUERY parameter defined C 6 DOO capability turned on and off 124 DRDA PACKAGE COLLID parameter defined C 6 errors detected by the server database 16 3 DRDA PACKAGE CONSTOKEN parameter C 7 DRDA PACKAGE NAME parameter binding the DRDA gateway package 11 5 defined C 7 errors detected by the server database 16 3 DRDA PACKAGE OWNER parameter C 7 DRDA PACKAGE SECTIONS parameter defined C 8 defining the number of DRDA cursors 13 28 DRDA READ ONLY parameter 12 5 defined C 8 DRDA RECOVER USERID DB2 400 5 4 DB2 0S390 5 3 DB2 VM 5 6 if the user ID is not specified 5 5 DRDA_RECOVERY_PASSWORD parameter DB2 400 5 4 DB2 0S390 5 3 defined C 8 defining the recovery user ID 5 5 DRDA_RECOVERY_USERID parameter DB2 400 5 4 DB2 0S390 5 2 DB2 VM 5 6 defined C 8 defining the recovery user ID 5 5 DRDA_REMOTE_DB_NAME parameter C 9 DRDA_SECURITY_TYPE parameter C 9 DROP DATABASE LINK statement 12 2 dropold sql script 11 6 DSPRDBDIRE command 5 4 dynamic dictionary mapping 1 5 E EBCDIC character set support D 5 code page D 4 DRDA Server CCSID D 11 sort order 13 19 tables known restrictions 1 14 translated to ASCII 13 21 EMP system wide synonym 12 4 table 12 6 empproc stored procedure 13 3 encryption types for Advanced Security 10 4 environment heterogeneous 12 6 environment variable DISPLAY on HP UX 8
41. 7 Yes TO_NUMBER DECIMAL Yes TO_SINGLE_BYTE Yes TRANSLATE E Yes Yes TRIM z 5 Yes Yes TRUNC Yes Yes UID gt x Yes UPPER TRANSLATE Yes USER gt Yes USERENV 7 Yes VARIANCE 5 VAR Yes VSIZE Yes Yes 13 5 8 DB2 VM SOL Compatibility The ways that Oracle Database and gateway handle SOL functions for a DB2 VM database are shown in the following table Table 13 4 DB2 VM SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate ABS Yes Yes ACOS Yes Yes ADD_MONTHS Yes ASCII gt Yes Yes ASIN z Yes Yes ATAN Yes Yes ATAN2 Yes Yes AVG Yes BITAND E Yes Yes Developing Applications 13 15 Oracle Database SQL Construct Processing Table 13 4 Cont DB2 VM SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate CAST m Yes Yes CEIL 7 z Yes CHARTOROWID z Yes CHR z z Yes Yes CONCAT Yes CONVERT E 5 Yes Yes COS z Yes Yes COSH a 7 Yes Yes COUNT Yes COUNT DISTINCT Yes colname COUNT ALL colname Yes COUNT COLUMN Yes DECODE 5 Yes Yes DUMP E Yes Yes EXP s G
42. A EMPTY_BLOCKS N A AVG_SPACE N A CHAIN_CNT N A AVG_ROW_LEN Average length of a row in the table in bytes AVG_SPACE_FR T ELIST_BLOCKS Average freespace of all blocks on a freelist NUM_FREELIST_BLOCKS Number of blocks on the freelist DEGREE Number of threads per instance for scanning the table INSTANCES Number of instances across which the table is to be scanned CACHE Whether the cluster is to be cached in the buffer cache T TABLE_LOCK Whether the table locking is enabled or disabled SAMPLE_SIZE Sample size used in analyzing this table LAST_ANALYZED Date on which this table was most recently analyzed PARTITIONED Whether this table is partitioned IOT_TYPE Whether the table is an index organized table TEMPORARY Can the current session only see data that it placed in this object itself SECONDARY N A NESTED Whether the table is a nested table BUFFER_POOL Default buffer pool for the object ROW_MOVEMENT N A GLOBAL_STATS N A USER_STATS N A DURATION N A SKIP_CORRUPT N A MONITORING N A CLUSTER_OWNER N A DEPENDENCIES N A COMPRESSION N A A 2 10 ALL_TAB_COLUMNS Columns of all tables views and clusters accessible to the user column name description OWNER Owner of the table or view
43. After the data is moved to the Oracle integrating server the COS function is performed If you are performing operations on large amounts of data that are stored ina DRDA database then keep in mind that some functions require post processing 13 5 4 Native Semantic SQL Functions Some SQL functions that are normally compensated may also be overridden through the Native Semantics facility If a SQL function has been enabled for Native Semantics then the function may be passed on to the DRDA database for processing instead of being compensated post processed If a SQL function is enabled for Native Semantics and is therefore passed on the DRDA database for processing then the SQL function is processed natively in the DRDA database Refer to Native Semantics on page 13 18 for more information 13 5 5 DB2 0S390 SQL Compatibility Table 13 1 describes how Oracle Database and the gateway handles SQL functions for a DB2 05390 Table 13 1 SQL Compatibility by Oracle SQL function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate ABS 7 Yes Yes ACOS Yes Yes ADD_MONTHS Yes ASC E Yes Yes ASIN Yes Yes ATAN Yes Yes ATAN2 Yes Yes AVG Yes z BITAND Yes Yes CAST z Yes Yes CEIL CEILING Yes CHARTOROWID Yes CHR H Yes Yes CONCAT Yes CONVERT 7 Yes Yes COS gt Yes
44. C 11 D National Language Support D 1 Overview of NES Interactions nerea aae AAA O o oai D 1 D 2 Client and Oracle Integrating Server Configuration aaa D 3 D 3 Gateway Language Interaction with DRDA Server D 4 D 3 1 Gateway Co fisuration zamian aiw dns wan naa AAA GN D 4 D 3 2 NLS Parameters in the Gateway Initialization File aaa D 5 D 4 Gateway Codepage Map Facility D 6 D 5 Multi Byte and Double Byte Support in the Gateway ocononcocoinonnnonenennnrinnnnnnarannirananannaa D 8 D 6 Message Availability so i OWA da AO A ENE ches D 10 D 7 Example of NLS Configuration ee D 11 E Configuration Worksheet F Quick Reference to Oracle SQL Functions G Sample Applications G 1 DIN A POE Es ON G 1 G 2 ORAIND naaa NPM W ck Deh eae ot daca wade a e ae a dach ln G 2 Index Send Us Your Comments Oracle Transparent Gateway for DRDA Installation and User s Guide 10g Release 2 10 2 for UNIX Part No B16217 01 Oracle welcomes your comments and suggestions on the quality and usefulness of this publication Your input is an important part of the information used for revision a Did you find any errors u Is the information clearly presented u Do you need more information If so where u Are the examples correct Do you need more examples u What features did you like most about this manual If you find any errors or have any other suggestions for improvement please indicate the title and part number of the
45. D National Language Support for more information Data type Limitations Refer to DRDA Data type to Oracle Data type Conversion on page 13 20 for detailed information about data types SAVEPOINT Command Is Not Supported Oracle Transparent Gateway for DRDA does not support the SQL SAVEPOINT Null Values and Stored Procedures Null values are not passed into or returned from calls to stored procedures through the gateway String Concatenation of Numbers String concatenation of numbers is not allowed in DB2 400 DB2 UDB and DB2 0S390 For example 2 2 is not allowed GLOBAL NAMES Initialization Parameter If GLOBAL NAMES is set to TRUE in the Oracle Database INIT ORA file then in order to be able to connect to the gateway you must specify the Heterogeneous Services HS initialization parameter HS_DB_DOMAIN in the Gateway Initialization Parameter file to match the value of the DB_DOMAIN parameter of the Oracle Database Refer to Chapter 11 Configuring the Gateway for more information Binding the DRDA Package on DB2 UDB The DRDA gateway package must be bound on the DRDA Server before the gateway can perform any SQL operations Because of a DB2 UDB restriction the ORACLE2 PC table must be created in the DB2 UDB database before the package can be bound For details refer to Chapter 11 Configuring the Gateway Date Arithmetic In general the following types of
46. DB2 0S390 5 2 column date columns TO_DATE function 13 24 Oracle ROWID known restrictions 2 6 supported in a result set 1 12 commands AGW ADD USERID 14 4 AGW DELETE USERID 14 4 CHECKSUM 1 5 10 4 COPY known restrictions 2 3 Oracle Database server to DRDA Server 12 6 SQL Plus command 12 6 CREATE DATABASE LINK DB2 VM 5 6 EXECUTE 1 6 EXPLAIN PLAN 16 5 INSERT known restrictions 2 3 not supported 12 6 lanscan on HP UX 8 5 on Solaris 6 5 commit confirm protocol 1 7 Communication Database CDB tables DDF 5 3 communications requirements 3 3 Communications Server configuring server profiles on AIX 7 1 creating profiles on AIX 7 1 compatible SQL set operators and clauses 13 20 concatenation restrictions string concatenation of numbers 2 4 concurrent connections APPC 3 1 TCP IP 3 2 configuring additional DRDA servers 11 8 AS 400 communications 5 3 AVS 5 6 binding DRDA package 11 5 checklist communications interfaces for SNAP IX product on Solaris 6 1 for SNAPlus2 product on HP UX 8 1 for DRDA Server 5 1 for installation overview 4 2 for the gateway 11 1 IBM Communication Server product on AIX 7 1 Oracle Net 10 1 checklist for gateway 11 1 DB2 400 5 3 5 4 DB2 05390 5 2 host workstation for gateway 11 3 MVS VTAM 5 2 Oracle integrating server 11 7 Oracle Net 10 3 Index 3 other Oracle Database servers 11 7 SNA server creating profiles 7 1 testing connection 7 3 SNA
47. E Yes Yes TRIM A Yes Yes MAX Yes 5 MIN Yes z MOD Yes Yes MONTHS_BETWEEN Yes NEW_TIME Yes NEXT_DAY Yes Yes NLS_INITCAP a Yes Yes NLS LOWER a Yes Yes NLS UPPER Yes Yes NLSSORT Yes Yes NVL VALUE NVL2 H Yes Yes POWER Yes Yes RAWTOHEX gt E Yes Yes REPLACE Yes Yes REVERSE Yes Yes ROUND Yes Yes ROWIDTOCHAR Yes RPAD Yes Yes Developing Applications 13 11 Oracle Database SQL Construct Processing Table 13 2 Cont DB2 Universal Database SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate RTRIM z a Yes Yes SIGN Yes Yes SIN Yes Yes SINH Yes Yes SOUNDEX z Yes SQRT Yes Yes STDDEV Yes Yes SUBSTR Yes Yes SUBSTRB Yes Yes SUM Yes SYSDATE Yes H TAN Yes Yes TANH z Yes Yes TO_CHAR 5 Yes TO DATE H Yes 5 TO MULTI BYTE s Yes TO_NUMBER DECIMAL Yes TO_SINGLE_BYTE z Yes TRANSLATE z gt Yes Yes TRIM a Yes Yes TRUNC Yes Yes UID Yes UPPER UCASE v Yes USER Yes USERENV g Yes VARIANCE s 5 Yes Yes VSIZE Yes Yes 13 5 7 DB2 400 SQL Compatibility The ways that Oracle Databa
48. ER IR ES 2 3 2 6 KNOWN ReStrictlONS iiss ix senja dni ei AEO opu delki ka di enih 2 3 2 6 1 DBZ Considerations iii innata 2 3 2 6 2 SOL O A a a 2 5 System Requirements 3 1 Hardware ReqiiifementS ed da A O vedl E 3 1 3 2 Software Requirements sea asics izol AA Daaih 3 2 3 3 Documentation ReguirementS saa A 3 3 Installing the Gateway 4 1 TOO UCA A APO ORAWA eis 4 1 4 2 Before YOU BESINE ek R tractors O O W tebe 4 1 4 3 Checklist for Gateway Installation ee 4 2 4 4 Installation OVervi Winston o biba naka e iona aa aa iki 4 2 4 5 Before Beginning Installation swa O A delka 4 2 4 6 Installing the Gateway from CD ROM ee 4 2 4 7 installation Complete aannkkaa bol das SA 4 4 4 8 REMOVING the Gateway vee wwo a a ri R A a Ar 4 5 Configuring the DRDA Server 5 1 Checklists for Configuring the DRDA Server u eee 5 1 5 2 DBZ OS EEN 5 2 5 3 DBZ A00 ZEP able a a ni 5 3 5 4 DB2 UDB Universal Database omita ooo des 5 4 5 5 DJ 9227 AANA E EN aCe Nea Gi S NU NU VS a A IS 5 5 Configuring SNAP IX Interfaces 6 1 Checklist for Configuring the Communications Interfaces uee ee 6 1 6 2 Betote Y u Beget vii AA AO anton AE AO WAGA a E UAE 6 1 6 3 SNAP IX Configuration TOOL A A al 6 1 6 4 Creating SNAP IX Profiles for the Gateway nena 6 2 6 5 Independent Versus Dependent LUS natan 6 2 6 6 Creating SNA Definitions for the Gateway 6 2 6 6 1 Sample SNAP I
49. FUNCCALL MASK u DRDA GRAPHIC CHAR SIZE 15 3 2 Parameters That Have Been Changed in Usage The usage of the following parameter has changed in version 9 of the gateway 15 2 Oracle Transparent Gateway for DRDA Installation and User s Guide DRDA Server Considerations u DRDA CONNECT PARM 15 3 3 Parameters That Have Been Renamed The following table lists the parameters whose names have been changed in version 9 of the gateway and their corresponding old names Refer to Oracle Database Heterogeneous Connectivity Administrator s Guide for more detailed information about these parameters New Name Old Name HS_COMMIT_STRENGTH_POINT COMMIT_STRENGTH_POINT HS_DB_DOMAIN DB_DOMAIN HS_DB_INTERNAL_NAME DB_INTERNAL_NAME HS_DB_NAME DB_NAME HS_DESCRIBE_CACHE_HWM DESCRIBE_CACHE_HWM HS_LANGUAGE ANGUAGE HS_NLS_DATE_FORMAT NLS_DATE_FORMAT HS_NLS_DATE_LANGUAGE NLS_DATE_LANGUAGE HS_OPEN_CURSORS OPEN_CURSORS HS_ROWID_CACHE_SIZE ROWID_CACHE_SIZE 15 3 4 Obsolete Parameters The following parameters are obsolete for the 10g version Remove them from your configuration files m MODE u SERVER_PATH m DRDA_OVERRIDE_FROM_CODEPAGE m DRDA OVERRIDE TO CODEPAGE ERROR LOGGING u ERROR REPORTING ERRORTAG u gateway SID GROUP BY OFF
50. Oracle Character Sets that are mapped to CCSIDs refer to Gateway Codepage Map Facility on page D 6 Note that it is not necessary for the gateway character set to be the same as the Oracle Database server character set In many cases it is not feasible to set the gateway character set equal to the Oracle Database character set because the DRDA Server does not have a valid translation for it Instead choose a character set that haves the complete intersection with the character set that is used by the DRDA Server The Oracle Net facility do as any translation between the gateway character set and the Oracle Database server character set Figure D 2 Gateway Language Interaction with DRDA Server Logon Request CCSID 819 Oracle Transparent Gateway for DRDA Logon Response CCSID 500 D 3 1 Gateway Configuration After the gateway is installed there are several parameters that you must change to customize for NLS support D 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Language Interaction with DRDA Server D 3 2 NLS Parameters in the Gateway Initialization File There are four parameters in the Gateway Initialization File initsid ora which affect NLS m HS_LANGUAGE m HS_NLS_NCHAR m HS NLS DATE FORMAT a HS NLS DATE LANGUAGE D 3 2 1 HS LANGUAGE HS LANGUAGE defines the character set that is used for communication between the gateway and the DRDA S
51. Read Only Support The 10 2 release enables the gateway to be configured as a read only gateway In this mode no modifying of user data will be allowed For more information refer to DRDA READ ONLY on page C 8 Support for Graphic and Multi byte Data The 10 2 release of the gateway adds support for DB2 GRAPHIC and VARGRAPHIC data types Refer to Chapter 13 Developing Applications Support for DB2 UDB on Intel Hardware The 10 2 release of the gateway adds support for DRDA Servers running on Microsoft Windows and Linux on Intel hardware Data Dictionary Support for DB2 UDB The 10 2 release of the gateway adds Oracle data dictionary support for DB2 UDB V7 Refer to Sample SQL scripts on page 11 6 1 14 Oracle Transparent Gateway for DRDA Installation and User s Guide 2 Release Information This chapter provides information specific to the 10g release of the Oracle Transparent Gateway for DRDA It includes the following sections u Product Set u Changes and Enhancements u Bugs Fixed in Release 10 2 0 u Known Problems u Known Restrictions 2 1 Product Set The following production components are included on the product CD ROM u Oracle Transparent Gateway for DRDA release 10 2 0 1 0 a Oracle Net release 10 2 0 1 0 2 2 Changes and Enhancements The following are the changes and enhancements unique to the 10g release of the gateway Desupport of SunLink Peer to Peer SNA Support for Sun Microsystems Su
52. Relationship between SNAP IX Definitions and Host VTAM Definitions Side Information Local LU Definition Local LU Alias Local LUAlias Local LU Namie Partner LU Alias or Fully qualified Mode Definition Partner LU Name Mode Name Remote TP Name U Definiti Partner LU Definition VTAMLST Fully qualified APPL Definition Partner LU Name pluname APPL netname pluname MODETAB mtname Connection Definition Partner LU Alias ATCSTROO NETWORK netname SSCPNAME cpname Connection Name Connection VTAM Mode Table ratnarne MODETAB MODEENT LOGMODEzmode name 6 14 Oracle Transparent Gateway for DRDA Installation and User s Guide Configuring IBM Communication Server This chapter describes configuring the IBM Communication Server product on AIX and Linux for usage with the Oracle Transparent Gateway for DRDA IBM Communication Server provides SNA connectivity through the APPC LU6 2 protocol between the host and the remote DRDA Server This chapter provides information about creating server profiles The following topics are included u Checklist for Configuring the Communications Interfaces u Using SNA Session Security Validation SNA Conversation Security 7 1 Checklist for Configuring the Communications Interfaces The checklists for configuring communications interfaces are as follows u Step 1 Configuring Communication Ser
53. Single Gateway Instance per DRDA Network Interface When installing the gateway a proper DRDA Network Interface must be chosen Only one DRDA Network Interface may be chosen and installed per gateway instance If the gateway product is reinstalled and if a Network Interface different from the previous installation is chosen then the new choice will overlay the current installation Reconfiguration of the Gateway Initialization Parameters must occur at this point in order to ensure proper gateway operation If you wish to have both SNA and TCP IP DRDA Network Interfaces installed then you must install two separate gateway homes Stored Procedures and Transaction Integrity IBM DB2 has introduced a feature called Commit on Return for stored procedures This feature allows DB2 to perform an automatic commit after a stored procedure runs successfully This feature is enabled when the procedure is created To ensure data integrity this feature is not supported by the Oracle Transparent gateway for DRDA in a heterogeneous environment When attempting to call a stored procedure which has this feature enabled through the gateway the gateway will return an error ORA 28526 or PLS 00201 identifier must be declared Note This restriction applies to DB2 for MVS or z OS as of V5 1 and DB2 UDB as of V8 1 2 6 2 SQL Limitations The SQL limitations are descibed as follows Release Information 2 5 Known Restrictions Oracle ROWID
54. VM from the host ASCII data is translated to EBCDIC When the characters are binary data in a character column this translation causes the application to receive incorrect information or errors To resolve these errors character columns on DB2 400 DB2 Oe or DB2 VM that hold non character data must be created with the FOR BIT DATA option In the application the character columns holding non character data should be processed using the Oracle data types RAW and LONG RAW The DESCRIBE information for a character column defined with FOR BIT DATA on the host always indicates RAW or LONG RAW 13 7 2 Converting Character String Data types The gateway binds character string data values from host variables as fixed length character strings The bind length is the length of the character string data value The gateway performs this conversion on every bind The DRDA VARCHAR data type can be from 1 to 32740 bytes in length This data type is converted to an Oracle VARCHAR2 data type if it is between 1 and 2000 characters in length If it is between 2000 and 32740 characters in length then it is converted to an Oracle LONG data type The DRDA VARCHAR data type can be no longer than 32740 bytes which is much shorter than the maximum size for the Oracle LONG data type If you define an Oracle LONG data type larger than 32740 bytes in length then you receive an error message when i
55. Yes Developing Applications 13 7 Oracle Database SQL Construct Processing Table 13 1 Cont SQL Compatibility by Oracle SQL function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate COSH z z Yes Yes COUNT Yes COUNT DISTINCT Yes colname COUNT ALL colname Yes COUNTCOL COUNT column Yes COUNTCOL DECODE H Yes Yes DUMP s Yes Yes EXP 5 H Yes Yes FLOOR Yes Yes GREATEST 3 Yes Yes HEXTORAW 7 Yes Yes NITCAP s Yes Yes INSTR 5 Yes Yes NSTRB Yes Yes LAST_DAY s Yes LEAST s 5 Yes Yes LENGTH 5 z Yes Yes ENGTHB Yes Yes LN s Yes Yes LOG 7 3 Yes Yes OWER z S Yes Yes LPAD Yes Yes TRIM z E Yes Yes MAX Yes MIN Yes s MOD Yes Yes MONTHS_BETWEEN 7 a Yes NEW_TIME Yes NEXT_DAY Yes si NLS INITCAP H a Yes Yes NLS_LOWER 7 Yes Yes NLS_UPPER F Yes Yes NLSSORT E a Yes Yes 13 8 Oracle Transparent Gateway for DRDA Installation and User s Guide Oracle Database SQL Construct Processing Table 13 1 Cont SQL Compatibility by Oracle SQL function
56. a ZAW dabas 13 18 13 6 1 SQL Functions That Can Be Enabled ane 13 19 13 6 2 SQL Functions That Can Be Disabled ene 13 19 13 6 3 SOL Set Operators and Clauses aken 13 20 13 7 DRDA Data type to Oracle Data type Conversion eee 13 20 13 7 1 Performing Character String Operations wezwana 13 21 13 7 2 Converting Character String Data types zew 13 21 13 7 3 Performing Graphic String Operations 13 21 13 7 4 Performing Date and Time Operations Leese 13 22 13 7 5 Mates ete ere A in Sa A NE NA SA A VS NE Re PEZET 13 23 13 7 6 HS NLS DATE FORMAT Support ee 13 24 13 7 7 Oracle TO DATE Function 13 24 13 7 8 Performing Numeric data type Operations aaa 13 25 13 7 9 Mapping the COUNT Function aaa 13 25 13 7 10 Performing Zoned Decimal Operations 13 25 13 8 Passing Native SQL Statements through the Gateway 13 25 13 8 1 Using DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIATE ee 13 26 13 8 2 Retrieving Results Sets Through Passthrough ou aa 13 27 13 9 Oracle Data Dictionary Emulation on a DRDA Server 13 27 13 9 1 Using the Gateway Data Dictionary ee 13 27 13 9 2 Using the DRDA Catalina 13 28 13 10 Defining the Number of DRDA Cursors 13 28 Security Considerations 14 1 Security Overview wasi aaa wiazanie dee 14 1 14 2 Authenticating Application LOgONS aaa 14 1 14 3 Defining and Controlling Database Links 14 2 14 3 1 Link Accessibility ei Eere io bai dA 14
57. between each of the components The application can use the Oracle client server capability to connect to a remote Oracle integrating server through Oracle Net The Oracle integrating server can connect to a remote gateway using a database link The gateway connects to DRDA Server through SNA or TCP IP network facilities The benefits of remote access are m Provides a means to allocate the appropriate resource to a given task 1 12 Oracle Transparent Gateway for DRDA Installation and User s Guide Features You can for example move application development off expensive processors and onto cost efficient workstations or microcomputers u Expands the number of available data sources Without remote access you are limited to the data available in the local environment With remote access your data sources are limited only by your networks m Provides a means to tailor an application environment to a given user For example some users prefer a block mode terminal environment while others prefer a bit mapped graphics driven terminal environment Remote access can satisfy both because you are not constrained by the interface environment imposed by the location of your data Support for Distributed Applications Because the gateway gives your application direct access to DRDA data you eliminate the need to upload and download large quantities of database data to other processors Instead you can access data where it is when you wa
58. cannot be passed as parameters when invoking a DB2 stored procedure u The gateway supports the SIMPLE linkage convention of DB2 stored procedures The SIMPLE linkage convention means that the parameters that are passed to and from the DB2 stored procedure cannot be null 13 4 Database Link Behavior A connection to the gateway is established through a database link when it is first used in an Oracle Database session In this context a connection refers to both the connection between the Oracle Integrating Server and the gateway and to the DRDA network connection between the gateway and the target DRDA database The connection remains established until the Oracle Database session ends Another session or user can access the same database link and get a distinct connection to the gateway and DRDA database Connections to the DRDA database can be limited in an advanced program to program communication APPC configuration in a parallel session limit or by other factors such as memory gateway parameters or DRDA Server resources Ina TCP IP configuration only resource limits such as memory or limits on the number of connections by the DRDA Server will limit the number of connections between the gateway and the DRDA Server Developing Applications 13 5 Oracle Database SQL Construct Processing 13 5 Oracle Database SQL Construct Processing One of the most important features of the Oracle Open Gateways products is providing SQL t
59. colname have been disabled by default and will be post processed If the gateway is to be used with one of the releases of DRDA servers then it may be necessary to disable the default usage of this form of COUNT Refer to Chapter 13 7 9 Mapping the COUNT Function and Chapter 13 6 Native Semantics for details on how to disable or enable compatibility for these forms of COUNT 2 6 Oracle Transparent Gateway for DRDA Installation and User s Guide 3 System Requirements This chapter provides information about hardware and software requirements specific to this release of the Oracle Transparent Gateway for DRDA It includes the following sections u Hardware Requirements m Software Requirements u Documentation Requirements 3 1 Hardware Requirements The Hardware requirements includes processor memory network attachment and drives Processors Refer to the Oracle Database Installation Guide 10g for UNIX Systems and to the certification matrix on Oracle MetaLink for the most up to date list of certified hardware platforms and operating system version requirements to operate the gateway for your Linux AIX Based HP UX or Solaris system The Oracle MetaLink web site can be found at the following URL http metalink oracle com The gateway processor requirements for your platform are as follows u For Linux 32 bit Intel Pentium based processors u For Linux 64 bit Intel Itanium 2 based 64 bit systems u For Li
60. configuring 5 2 data dictionary views supported by gateway A 1 DRDA_ISOLATION_LEVEL C 5 DRDA_OPTIMIZE QUERY C 6 user ID mapping 14 3 V6 V7 and V8 stored procedures supported 1 14 DB2 UDB binding packages 11 4 binding the gateway package 11 6 catalog view 13 27 configuring 5 4 data dictionary views not supported A 1 DRDA ISOLATION LEVEL C 5 DRDA OPTIMIZE OUERY C 6 known restrictions 2 4 supported 1 14 user ID mapping 14 4 DB2 VM catalog view 13 27 configuring 5 5 data dictionary views not supported A 1 database and SQL functions 13 15 DRDA_ISOLATION_LEVEL C 5 DRDA_OPTIMIZE QUERY C 6 DRDA_PACKAGE_OWNER C 7 instance DRDA location name 5 6 server machine 14 4 user ID mapping 14 4 DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIAT E function 13 25 DD basic tables known restrictions 2 3 DDF DB2 Distributed Data Facility 5 3 subsystem 5 2 DDL statement 13 25 debug gateway 16 5 Index 5 library 16 6 debugging error codes 16 2 SQL tracing 16 5 your application 12 7 default port number for DRDA TCP IP configuration 9 1 default TP name for DRDA Server SNAP IX product on Solaris 6 10 SNAPlus2 product on HP UX 8 10 de installing the gateway 4 4 DELETE known restrictions SQL limitations 2 6 operation 13 2 read only gateway 12 6 SQL clause 13 24 statement 13 25 DESCRIBE character string operations 13 21 Destination Hostname or IP Address same as DRDA Server Hostname or IP Address configur
61. connection request must be a valid user ID on the DB2 UDB host 14 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Passwords in the Gateway Initialization File After the application has completed the DRDA connection to the DB2 host it is subject to all authorities and GRANTs associated with the user ID in use The user ID must have execute authority on the gateway DRDA package to execute any SQL statements 14 6 Passwords in the Gateway Initialization File The gateway uses userids and passwords to access the information in the remote database on the DRDA Server Some userids and passwords must be defined in the Gateway Initialization File to handle functions such as resource recovery In the current security conscious environment having plain text passwords that are accessible in the Initialization File is deemed insecure An encryption feature has been added as part of Hetergeneous Services generic connectivity to help make this more secure This feature is accessible by this gateway With it Initialization parameters which contain sensitive values might be stored in an encrypted form Refer to the manual Oracle Database Hetergeneous Connectivity Administrator s Guide Chapter 4 Encrypting Initialization Parameters for information about how to use the feature See Also the parameters DRDA_RECOVERY_USERID and DRDA_RECOVERY_PASSWORD in Appendix C as examples for more information Securit
62. defined to the DRDA Server for example DB2 O0S390 Developing Applications 13 3 Using DRDA Server Stored Procedures with the Gateway Figure 13 2 Running DRDA Server Stored Procedures DB2 empproc Stored Oracle Procedure Server Programtode Program Code j i fla Oracle Application empproc db2 emp pj act emt ems erre type code Oracle Transparent i EXEC SQL UPDATE Gateway for DRDA f r EXEC SQL INSERT DRDA Server for example DB2 MVS Progr amCode Programlode From the perspective of the application running the DB2 stored procedure is no different from invoking a stored procedure at a remote Oracle Database instance 13 3 1 Oracle Application and DRDA Server Stored Procedure Completion If an Oracle Application attempts to invoke a stored procedure in a DB2 0S390 database For an Oracle application to call a DB2 stored procedure it is first necessary to create the DB2 stored procedure on the DB2 system by using the procedures documented in the IBM reference document for DB2 for OS 390 SOL After the stored procedure is defined in DB2 the gateway is able to access the data using a standard PL SQL call For example an employee name John Smythe is passed to the DB2 stored procedure REVISE SALARY The DB2 stored procedure retrieves the salary value from the DB2 database in order to calculate a new yearly salary for John Smythe The revised salary that is ret
63. destination column in the database For example if PRICE is an integer column of the PRODUCT table in an IBM DRDA database then the update shown in the following example inaccurately sets the price of an ice cream cone to 1 00 because the IBM DRDA Server automatically converts a floating point to an integer UPDATE PRODUCT SET PRICE 1 50 WHERE PRODUCT NAME ICE CREAM CONE A Because PRICE is an integer the IBM DRDA Server automatically converts the decimal data value of 1 50 to 1 13 7 9 Mapping the COUNT Function Oracle Database supports the following four operands for the COUNT function a COUNT m COUNT DISTINCT colname m COUNT ALL colname ua COUNT colname Some DRDA servers do not support all forms of COUNT specifically COUNT colname and COUNT ALL colname In those cases the COUNT function and its arguments are translated into COUNT This may not yield the desired results especially if the column being counted contains NULLs For those DRDA servers that do not support the above forms it may be possible to achieve equivalent functionality by adding a WHERE clause For example SELECT COUNT colname FROM table dblink WHERE colname IS NOT NULL or SELECT COUNT ALL colname FROM table dblink WHERE colname IS NOT NULL Refer to Chapter 2 6 2 SQL Limitations for known DRDA servers which do not support all forms of COUNT 13 7 10 Performing Zoned Decimal Operations
64. documentation and the chapter section and page number if available You can send comments to us at the following e mail address a Electronic mail infodev_us oracle com u FAX 650 506 7227 Attn Server Technologies Documentation Manager m Postal service Oracle Corporation Server Technologies Documentation Manager 500 Oracle Parkway Mailstop 4op11 Redwood Shores CA 94065 USA If you would like a reply please give your name address telephone number and electronic mail address optional If you have problems with the software please contact your local Oracle Support Services xi xii Preface The Oracle Transparent Gateway for DRDA provides users with transparent access to DRDA databases as if they were Oracle databases Intended Audience This guide is intended for anyone responsible for installing configuring and administering the gateway and also for application developers Read this guide if you are responsible for tasks such as u Installing and configuring the Oracle Transparent Gateway for DRDA u Configuring the SNA and TCP IP Products m Setting up gateway security u Diagnosing gateway errors Using the gateway to access tables in DRDA databases ua Writing applications that access DRDA databases through the gateway You must understand the fundamentals of transparent gateways and the UNIX operating systems before using this guide to install or administer the gateway Processors Refer
65. double byte and multi byte data you must configure the codepage map facility with proper multi byte maps and as an option can set the following gateway configuration parameters m DRDA GRAPHIC LIT CHECK m DRDA GRAPHIC TO MBCS DRDA MBCS TO GRAPHIC m DRDA GRAPHIC PAD SIZE m DRDA GRAPHIC CHAR SIZE Refer to Appendix C DRDA Specific Parameters for the values of these parameters Configuring the codepage map reguires knowledge of the codepages that have been configured in the DRDA Server database as well as knowledge of compatible Oracle Database Character Sets IBM coded character set identifiers CCSIDs are used to indicate which codepage is configured as the primary codepage for the database as well as any translation character sets loaded into the database Some DRDA Servers such as with DB2 have a translation facility in which character set transforms are mapped between two compatible character sets For DB2 OS390 these transforms are stored in the table D 8 Oracle Transparent Gateway for DRDA Installation and User s Guide Multi Byte and Double Byte Support in the Gateway SYSIBM SYSSTRINGS and transform on the CCSID codepage to another CCSID codepage In SYSSTRINGS IN and OUT columns specify the CCSIDs that are used in the transform Typical transforms are from ASCII to EBCDIC and back Two transforms are therefore used for two given CCSIDs
66. error on INSERT nSQLCODE d n code goto sqlerror Ftkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkikkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Verify row insertion Query the data just inserted Ftkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkj EXEC SQL SELECT deptno dname loc INTO dept_no dept_name location FROM SCOTT DEPT GTWLINK WHERE deptno 10 printf nData INSERTed was n printf ndeptno d dname s loc s n dept_no dept_name location arr ERRRREREERER RARE RRE RRE RRA RARE RE RAR RARE RE RE RRA RE EER ER EERE KEEREKREREREREEERERE Logoff from Oracle Su FtkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkJ EXEC SQL COMMIT RELEASE printf NninHave a good day n n exit 0 sqlerror printf n 70s In sqlca sqlerrm sqlerrmc EXEC SQL WHENEVER SQLERROR CONTINUE EXEC SQL ROLLBACK RELEASE exit 1 Sample Applications G 3 ORAIND G 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Symbols DISPLAY environmental variables on HP UX 8 3 on Solaris 6 3 ORACLE HOME on HP UX 8 3 on Solaris 6 3 Numerics 22421 H1 Head1 Migrating existing Gateway Instance to New Release 15 1 A accessing DRDA servers 11 8 gateway 11 7 main topic 12 3 Advanced Program to Program Communication APPC LU6 2 protocol IBM Communication Server product on AIX 7 1 SNAP
67. errors detected 16 2 features main topic 1 10 how to access 12 3 installation log file 4 4 steps via Oracle Universal Installer 4 4 steps from CD ROM 4 2 interface 1 9 local date exit 13 24 logging LOG DESTINATION C 10 migration problems 15 2 parameter 5 6 performance enhancements 1 11 performance versus transparency 13 18 performing distributed gueries 12 4 read only option 12 5 service name entries in the tnsnames ora 15 4 settings for security options on AIX 7 4 on HP UX 8 11 on Solaris 6 12 SOL differences 1 10 supported languages D 6 tracing LOG DESTINATION C 10 SOL statements 12 7 using 12 1 with other Oracle products SOL Plus 1 6 Gateway Initialization File backup and recovery of gateway configuration 11 7 configuring for binding the DRDA gateway package 11 4 if errors are reported 11 4 modifying C 1 parameters DRDA_READ_ONLY 12 5 list C 2 LOG_DESTINATION 16 6 new since V4 gateway 15 2 ORACLE DRDA TCTL 16 6 stored in initsid ora C l TRACE LEVEL 16 6 sample B 1 Gateway System Identifier SID 11 2 GCS virtual machine 14 4 GLOBAL_NAMES known restrictions 2 4 GRANT statement DB2 VM access 14 4 synonyms and views 11 7 granting authority to a package for DB2 11 7 GRAPHIC datatype 13 21 graphic string operations unsupported 13 21 grc error code 16 2 GROUP BY clause SQL Set Clauses 13 20 GTW _BIND_PKG internal stored procedure 11 5 stored procedure 11 4 H
68. for Oracle Net The following terms are used to explain the architecture of Oracle Net u host is the computer the database resides on and that runs Oracle Database or gateway u client task is the application using a Oracle Net driver to communicate with Oracle Database or gateway a protocol is a set of standards or rules governing the operation of a communication link m driver is the part of Oracle Net supporting a given network protocol or communication method u network is a configuration of devices and software connected for information interchange 10 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Configuring Oracle Net 10 4 Configuring Oracle Net The gateway must be defined to the TNS listener and a service name must be defined for accessing the gateway Step 1 Modify listener ora file Add an entry for the gateway to the Listener ora file For example SID_DESC SID_NAME sidname ORACLE_HOME oracle tg4drda 10 2 0 PROGRAM g4drsrv Refer to Appendix B Sample Files for a sample listener ora file Note The PROGRAM g4drsrv parameter is required It specifies to the listener the name of the gateway executable Step 2 Modify tnsnames ora file Add a gateway service name to the tnsnames ora file on the system where your Oracle integrating server resides Specify the service name in the USING parameter of the database link defined for accessing the gateway from th
69. function 13 18 known restrictions 2 3 with Native Semantics known restrictions 2 4 synonym feature 12 4 for location transparency 13 3 how the gateway works 1 9 system privileges BINDADD and BINDAGENT DB2 0S390 5 2 DB2 VM 5 6 T table create a table in DB2 13 26 insert a row into a DB2 table 13 26 TABLE_PRIVILEGES view A 10 tables EXPLAIN_PLAN 1 12 ORACLE2PC 12 5 DB2 UDB 11 6 scripts to create Data Dictionary tables and view 11 7 ORADRDA ORACLE2PC 12 5 TCP IP adapter B 2 concurrent connections 3 2 configuring DB2 400 5 3 DB2 0S390 5 2 DB2 VM 5 6 Index 18 configuring under Solaris 9 1 DRDA_CONNECT_PARM C 3 facilities 1 12 format gateway initialization file parameter C 3 functions 1 9 modifying tnsnames ora in Oracle Net 10 3 network attachment 3 2 number of database link connections 13 5 protocol gateway architecture 1 8 gateway transparency 1 3 implicit protocol conversion 1 5 remote access 1 12 security 14 3 security validation 14 3 support 1 12 terminology defined 1 7 tg4drda directory also known as ORACLE_HOME 4 2 TIME datatype 13 22 time operations 13 22 TIMESTAMP datatype 13 22 TNSNAMES ORA changes to during migration problems 15 2 tnsnames ora connect descriptor 12 2 file adding a gateway service name 10 3 configuring additional DRDA Server instances 11 8 modifying for Oracle Net 15 4 sample file B 2 TO_DATE function main topic 13 24 Token Rin
70. gateway migration problems 15 2 Heterogeneous Services HS facility 10 2 replaced by Oracle Net 10 2 SOL Plus connecting to gateway 10 5 COPY command 12 6 extending gateway uses 1 10 moving data 1 6 sglstate mapped errors 16 3 stability of cursor DRDA ISOLATION LEVEL C 5 standard port number for DRDA TCP IP configuration 9 1 Startup Shell Script parameter tailoring to configure the host 11 3 statement CREATE DATABASE client server configuration D 3 statements CREATE DATABASE LINK 12 2 DB2 CREATE TABLE 1 5 DDL 13 25 13 26 DELETE 13 24 13 25 DROP DATABASELINK 12 2 GRANT 11 7 INSERT 13 25 PREPARE TRANSACTION 12 5 SELECT 13 2 13 27 read only gateway 12 5 SOL DB2 13 26 JOIN 13 2 SELECT 13 27 UPDATE 13 24 13 25 Index 17 stored definitions Side Information Profile needed for SNAP IX 6 2 Side Information Profile needed for SNAplus2 8 2 stored procedure creating on DB2 13 4 DB2 13 5 native DB2 1 6 Oracle and non Oracle 1 6 Oracle Database Server local instance 13 2 Oracle Database server PL SQL 13 2 remote instance 13 2 Oracle Server using 13 2 Oracle description 1 6 restriction 2 4 usage C 4 using DRDA Server 13 3 stored procedures 1 4 DB2 12 6 13 3 GTW _BIND_PKG 11 4 REVISE SALARY 13 4 using with the gateway 13 2 string concatenation known restrictions 2 4 string index with Native Semantics 13 18 Structured Query Language also see SQL 1 2 SUBSTR SQL
71. in AAA EEE e 8 3 8 7 Using SNA Session Security Validation esa 8 11 8 7 1 SNA Conversation Security a do dno dubai 8 11 8 8 Testing the COMME CO miana nid ka aa cacka aaa 8 13 Configuring TCP IP 9 1 Before YOU Besim nasi pni ti A OOO O PO IS Ee 9 1 9 2 Configuring TCP IP under UND saa kiaad kB AA ali ka 9 1 Oracle Net 10 1 Checklists tor Oracle Neta aa a OK lila lle eri RM As 10 1 10 1 1 Configuring Oracle Net an A O OE pI OE 10 1 10 1 2 Advanced Security Encryption 10 1 10 2 Oracle Net Introduction A A ee DJ di i a 10 2 10 3 Oracle Net Overview snngo cani ete deiaciedhalateciseetctalacudalaneselin 10 2 10 4 Configuring Oracle Nets sev wa eles dessa ah O OW ss Se ANA AW A AA 10 3 10 5 Advanced Security Encryption 10 4 10 6 Setting Up Advanced Security Encryption for Test 10 4 10 7 Testing Advanced Security Encryptions eee 10 5 11 12 13 vi Configuring the Gateway 11 1 11 2 11 2 1 11 3 11 4 11 4 1 11 4 2 11 5 11 5 1 11 5 2 11 6 11 7 11 7 1 11 7 2 11 8 11 9 11 10 Configuration Checklists ataca ono a a eae eieiei 11 1 Choosing a Gateway System Identifier e nena 11 2 Enter the SID on the Worksheet cccccccssesscsscessessceseseecesceeeesseeeeecsecssesaecaeceseceeseseeeeses 11 3 Configurating the Gateways onra diodo da dei boda dedo da dada cda cda dad actas 11 3 Configuring the Host ee ri di On adn 11 3 Binding the DRDA Gateway Package 11 4 Binding Packag
72. information for the Oracle Transparent Gateway for DRDA This supplements the general Oracle NLS information found in the Oracle Database Application Developer s Guide Fundamentals National Language Support enables Oracle applications to interact with users in their native language using their conventions for displaying data The Oracle NLS architecture is datadriven enabling support for specific languages and character encoding schemes to be added without any changes in the source code There are a number of different settings in the gateway DRDA Server Oracle Database 10g and client that affect NLS processing For translations to take place correctly character settings of these components must be compatible This appendix contains the following sections u Overview of NLS Interactions u Client and Oracle Integrating Server Configuration u Gateway Language Interaction with DRDA Server m Gateway Codepage Map Facility u Multi Byte and Double Byte Support in the Gateway u Message Availability u Example of NLS Configuration D 1 Overview of NLS Interactions Figure D 1 illustrates NLS interactions within your computer including each component of your computer and the parameters of each component that affect NLS processing in a distributed environment National Language Support D 1 Overview of NLS Interactions Figure D 1 Architecture of NLS Interactions with Your System Components Oracle Oracle Transparent DRDA Int
73. kept in the database ua Operating system authentication With operating system authentication the servers underlying operating system is responsible for authentication An Oracle user ID that is created with the IDENTIFIED EXTERNALLY attribute instead of a password is accessed with operating system authentication To log into sucha user ID the application supplies a forward slash for a user ID and does not supply a password To perform operating system authentication the server determines the requester s operating system user ID optionally adds a fixed prefix to it and uses the result as the Oracle user ID The server confirms that the user ID exists and is IDENTIFIED EXTERNALLY but no password checking is done The underlying assumption is that users were authenticated when they logged into the operating system Operating system authentication is not available on all platforms and is not available in some Oracle Net client server and multi threaded server configurations Refer to the Oracle Database Installation Guide 10g for UNIX Systems and Oracle Net documentation to determine the availability of this feature For more information about authenticating application logons refer to the Oracle Database Reference 14 3 Defining and Controlling Database Links The information here is specific to the gateway For additional information on database links refer to the Oracle Database Refere
74. new dependent LUs Oracle Transparent Gateway for IBM DRDA instances should be created and configured to use these new Side Information Profiles 8 6 Creating SNA Definitions for the Gateway SNAPlus2 definitions are stored in the following two files located in the directory etc opt sna u sna_node cfg SNA node definitions a sna_domn cfg SNA domain definitions These files are created and maintained with the xsnapadmin tool Maintenance of SNA definitions is normally done by a user with administrative authority You should 8 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Creating SNA Definitions for the Gateway have some knowledge of SNA before reading this section The following information is intended for the person creating SNA definitions for the gateway they are u Sample SNAPlus2 Definitions u Configuring SNAPlus2 u Invoking xsnapadmin SNA Conversation Security 8 6 1 Sample SNAPlus2 Definitions The SORACLE_HOME tg4drda sna snaplus subdirectory contains a set of sample SNAPlus2 definitions for the gateway created with the xsnapadmin SNA definitions are very specific to the HP9000 host and SNA network As such the sample definitions that are provided will not work without being tailored for the local host and SNA network 8 6 2 Configuring SNAPlus2 This section describes the process of creating your SNA definitions for SNAPlus2 using xsnapadmin All of the tasks described in this section a
75. overview 10 2 purpose 1 9 requirements 3 3 sample files B 1 sample listener ora file B 2 support for CHECKSUM and encryption 10 4 terminology 10 2 client 10 2 driver 10 2 host 10 2 network 10 2 protocol 10 2 TNS connect descriptor specification 12 2 Oracle ROWID column known restrictions 2 6 Oracle server copying data from DRDA Server 12 7 to DRDA Server 12 6 relationship to host 1 8 services database triggers 1 4 distributed capabilities 1 4 distributed query optimization 1 4 extended database services 1 4 SQL 1 4 stored procedures 1 4 two phase commit protection 1 4 triggers 12 6 Oracle Universal Installer removing the gateway 4 5 starting 4 4 steps to install the gateway 4 4 upgrading for installation 4 4 ORACLE _DRDA_TCTL parameter defined C 11 SOL tracing in the gateway 16 6 ORACLE DRDA TRACE parameter defined C 11 ORACLE HOME environmental variable 4 3 for the gateway 4 2 ORACLE2PC table binding packages on DB2 UDB 11 4 DB2 400 5 4 DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 distributed DRDA transactions 12 5 DRDA PACKAGE OWNER C 7 ORADRDA ORACLE2PC table 12 5 oraprocl stored procedure 13 2 oraproc2 stored procedure 13 2 ORARECOV user ID DB2 400 5 4 DB2 0S390 5 3 DB2 UDB 5 5 DB2 VM 5 6 DRDA_RECOVERY_USERID C 8 ORDER BY clause SQL Set Clauses 13 20 OS 390 MVS configuring DB2 0S390 5 2 P package collection id DRDA_PACKAGE_COLLID C 7 consistency tok
76. pair can exist we directly map the multi byte sets And because the single byte and double byte CCSIDs are ostensibly subsets of KO16MSWIN949 we map them as one way entries Note that there is no shift attribute in any of these mappings This is because ASCII based sets do not use shift out in encapsulation Instead ASCII based sets use a different method which does not use a shift out in protocol to identify double byte characters National Language Support D 9 Message Availability The above entries supply the necessary codepage mappings for the gateway To complete the example we need to specify the correct character set in the HS_LANGUAGE and HS_NLS_NCHAR parameters in the Gateway Initialization file The Gateway Initialization parameters would look as follows HS_LANGUAGE AMERICAN_AMERICA KO16MSWIN949 HS_NLS_NCHAR KO16MSWIN949 Note that the specified character set must be ASCII based This takes care of the configuration of the gateway The last step is to set up transforms between the EBCDIC codepages and the ASCII codepages in the DRDA Server database Normally the gateway would use a total of six transforms one of each pair in both directions You may save some table space by installing only the ASCII to EBCDIC transforms because the DRDA Server needs to translate only the ASCII data that is sent by the gateway but the DRDA Server does not need to send ASCII data The gateway will receives the EBCDIC data and
77. refer to the Oracle Database Installation Guide 10g for UNIX Systems 4 5 Before Beginning Installation Before installing the gateway confirm that all hardware and software requirements are met Refer to Chapter 3 System Requirements to verify these requirements 4 6 Installing the Gateway from CD ROM The Oracle Transparent Gateway for DRDA is completely self contained and must be installed in its own directory The following are the steps that are required to install the gateway Step 1 Log on to the host Log on to your host as the database administrator DBA user Refer to your platform release notes Step 2 Create the Product Installation Directory When you create a new directory we recommend that you use the version number as part of the pathname Doing so allows different versions of the same Oracle product to be installed under one Oracle directory tree The product installation directory is also known as the Oracle Home for the gateway and it has also been called the tg4drda directory For example enter mkdir oracle mkdir oracle tg4drda mkdir oracle tg4drda 10 2 0 chown oracle dba oracle tg4drda 10 2 0 chmod 755 oracle tg4drda 10 2 0 4 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Installing the Gateway from CD ROM Step 3 Set the ORACLE_HOME environment variable ORACLE_HOME must point to the directory that you created in Step 2 Set the ORACLE_HOME environment
78. the Oracle Transparent Gateway to run applications such as Oracle Database tools that read and write data that is stored in DRDA databases While the Oracle Transparent Gateway for DRDA provides no new application or development facilities it extends the reach of existing Oracle Database tools to include data in non Oracle databases that support DRDA Using the Oracle Transparent Gateway for DRDA with other Oracle products can greatly extend the capabilities of the stand alone gateway 1 8 1 SQL Plus Use SQL Plus and the Oracle Transparent Gateway for DRDA to create a distributed database system providing an easy to use transfer facility for moving data between the distributed databases One possible use is to distribute the data in your corporate Oracle Database to departmental DRDA databases You can also distribute data in your corporate DRDA database to departmental Oracle Databases 1 9 Features Following is a list of important features that characterize release of the Oracle gateway The features are u Heterogeneous Services Architecture u Performance Enhancements u Fetch Reblocking Oracle Database 10g Passthrough Supported u Retrieving Result Sets Through Passthrough u Support for TCP IP a Native Semantics u Columns Supported in a Result Set u EXPLAIN_PLAN Improvement u Heterogeneous Database IntegrationMinimum Impact on Existing Systems 1 10 Oracle Transparent Gateway for DRDA Installation and User s Guide F
79. the column in bytes DATA PRECISION N A DATA SCALE Digits to the right of a decimal point in a number NULLABLE Whether the column permits nulls Value is n if there is a NOT NULL constraint on the column or if the column is part of a PRIMARY key COLUMN_ID Sequence number of the column as created DEFAULT_LENGTH N A Oracle DB2 Data Dictionary Views A 15 Data Dictionary View Tables column name description DATA_DEFAULT N A NUM_DISTINCT Number of distinct values in each column of the table LOW_VALUE For tables with more than three rows the second lowest and second highest values These statistics are expressed in hexadecimal notation for the internal representation of the first 32 bytes of the values HIGH_VALUE N A DENSITY N A NUM_NULLS Number of nulls in the column NUM_BUCKETS Number of buckets in histogram for the column AST_ANALYZED Date on which this column was most recently analyzed SAMPLE_SIZE Sample size used in analyzing this column CHARACTER_SET_NAME Name of the character set CHAR_COL_DECL_LENGTH Length of the character set GLOBAL_STATS N A USER_STATS N A AVG_COL_LEN Average length of the column in bytes CHAR_LENGTH Length of the column in characters CHAR_USED N A A 2 27 USER_TAB_COMMENTS Comments on the tables and views owned by the user
80. the data source The result is that the Oracle Database server technology is non intrusive providing coexistence and an easy migration path 1 3 16 Security 1 4 Terms The gateway does not bypass existing security mechanisms gateway security coexists with the security mechanisms already used in the operating environment of the data source Functionally gateway security is identical to that of an Oracle Database as described in the Oracle Database Administrator s Guide Oracle Database security is mapped to the data dictionary of the data source The terms used in this guide do not necessarily conform to the IBM terminology The following list presents several terms and their meanings as used within this guide DRDA data is generically any database data accessed through DRDA DRDA database is the collection of data that belongs to a DRDA Server DRDA server is a database server that can be accessed through DRDA IBM terminology for a DRDA Server is a DRDA Application Server or AS DRDA Server type is a specific database product or program that can act as a DRDA Server Oracle integrating server is any Oracle Database 10g server instance that communicates with the Oracle Transparent Gateway for DRDA to distribute database access operations to a DRDA Server The Oracle integrating server can also be used for non gateway applications DB2 Universal Database is a generic name for the UNIX based or Windows based implementations of
81. this parameter is missing then the gateway attempts to connect to a user ID of ORARECOV For more information refer to Two Phase Commit Processing on page 12 5 C 8 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Initialization File Parameters C 4 28 DRDA_REMOTE_DB_NAME Default value DB2V2R3 Range of values An alphanumeric string 1 to 18 characters in length Syntax DRDA_REMOTE_DB_NAME name DRDA REMOTE DB NAME specifies the DRDA Server location name This is an identifying name that is assigned to the server for DRDA purposes A technique for determining this name by using a SOL SELECT statement is discussed in each of the server specific installation sections in Chapter 5 Configuring the DRDA Server C 4 29 DRDA_SECURITY_TYPE Default value PROGRAM Range of values PROGRAM SAME Syntax DRDA_SECURITY_TYPE PROGRAM SAME DRDA_SECURITY_TYPE specifies the type of security used for SNA communications For more information about types of security and about setting DRDA_SECURITY_TYPE refer to Chapter 14 Security Considerations Also refer to Chapter 15 for information on security and encrypting passwords C 4 30 FDS_CLASS Default value TG4DRDA_DB2MVS Range of values Refer to the list below for valid values Syntax FDS_CLASS TG4DRDA_DB2MVS FDS_CLASS specifies the capability classification used
82. this release IBM DB2 Version 5 1 EBCDIC and ASCII Tables 1 14 IBM DB2 UDB supported 1 14 read only support 1 14 CHARACTER SET clause client server configuration D 3 parameter description D 2 character sets and codepage map facility D 6 ASCII 1 14 CCSID D 3 codepage C 3 EBCDIC 1 14 supported 1 14 character string converting datatypes 13 21 performing operations 13 21 checklist configuring the communications interfaces on AIX 7 1 on HP UX 8 1 on Solaris 6 1 configuring the DRDA Server 5 1 gateway configuration 11 1 gateway installation 4 2 installation overview 4 2 Oracle Net installation and configuration 10 1 CHECKSUM command 10 4 extended advanced networking 1 5 CICS transaction 13 5 clause CHARACTER SET client server configuration D 3 clauses CONNECT TO 12 2 GROUP BY SQL Set Clauses 13 20 HAVING SQL Set Clauses 13 20 ORDER BY SQL Set Clauses 13 20 SQL DELETE 13 24 INSERT 13 24 SELECT WHERE 13 24 UPDATE 13 24 USING 12 2 VALUES functions not allowed by DB2 13 24 WHERE known restrictions SQL limitations 2 6 SQL Set Clauses 13 20 WHERE CURRENT OF CURSOR known restrictions SQL limitations 2 6 code tracing C 12 codepage map facility configuring support for character sets known restrictions 2 4 for data translation D 6 supported by gateway 1 14 coercion of data 13 18 collection privilege CREATE IN DB2 0S390 5 2 DB2 VM 5 6 collection privilege CREATETAB
83. to the Oracle Database Installation Guide 10g for UNIX Systems and to the certification matrix on Oracle MetaLink for the most up to date list of certified hardware platforms and operating system version requirements to operate the gateway for your Linux AIX Based HP UX or Solaris system The Oracle MetaLink web site can be found at the following URL http metalink oracle com The gateway processor requirements for your platform are as follows a for Linux 32 bit Intel Pentium based processors a for Linux 64 bit Intel Itanium 2 based 64 bit systems u for Linux S 390 Any processor that can run Linux S 390 m for AIX Based Systems IBM pSeries u for HP UX HP 9000 Series HP UX that can run the required version of HP UX xiii ua for Solaris A Solaris Operating System SPARC 64 bit that can run the required version of Solaris with 64 bit architecture Documentation Accessibility Our goal is to make Oracle products services and supporting documentation accessible with good usability to the disabled community To that end our documentation includes features that make information available to users of assistive technology This documentation is available in HTML format and contains markup to facilitate access by the disabled community Accessibility standards will continue to evolve over time and Oracle is actively engaged with other market leading technology vendors to address technical obstacles so that our documentation can be
84. translate as needed This one sided data transfer methodology is called receiver makes right meaning that the receiver must translate whatever character set the sender uses In our example the DRDA Server is EBCDIC based so it will send all data in EBCDIC The server therefore does not need to have an EBCDIC to ASCII transform because the server never use the transform In our previous example the DRDA Server database is assumed to be EBCDIC which is likely to be true for a DB2 0S390 database For a DB2 UDB database however this is not likely to be true Because most DB2 UDB databases run on ASCII based computers they will likely be created with ASCII based codepages In such cases the gateway needs to have only one set of codepage map definitions which are for the ASCII set Also because both the DRDA Server and the gateway will be using the same codepages no character set transforms need to be loaded into the DB2 database This can help reduce the amount of CPU overhead that is associated with character translation Be aware that some multi byte codepages may be composed of single byte CCSIDs that are already defined in the codepage map file that is provided with the product If you are adding a new set of entries to support a multi byte set then comment out the provided entries so that your new entries will be used correctly Additional codepage mappings which are not already provided are possible You may construct entries such
85. 0g release if problems are encountered then it is always possible to revert to the previous version Assuming a working version 4 gateway instance exists simply change the TNSNAMES ORA entries from using the Oracle Database 10g gateway instance to the older version 4 instance Remember to remove the HS entry from the SQL Net connect definition Oracle recommends that you keep the old gateway home and instance configurations intact and operational when you are installing a new release of the gateway and upgrading the existing instances in case you have problems with the upgrade This will ensure minimal downtime between changes to different gateway instances 15 3 New and Changed Parameters When Migrating to Release 10g The 10 2 release of the Oracle Transparent Gateway for DRDA introduces new and changed initialization parameters if you are migrating from a version 4 version 8 or version 9 gateway to the Oracle Database 109 gateway 15 3 1 New Parameters Parameters introduced in the 10 2 release of the gateway listed in the following table may be added to the Gateway Initialization File m DRDA_CACHE TABLE DESC m DRDA GRAPHIC LIT CHECK u DRDA GRAPHIC PAD SIZE DRDA GRAPHIC TO MBCS DRDA MBCS TO GRAPHIC m DRDA_PROCDESC_STMT m DRDA PROCDESCPARMS STMT m DRDA PROCCALL MASK a DRDA FUNCDESC SIMT DRDA FUNCDESCPARMS STMT m DRDA
86. 1 creating SNAP IX profiles 6 2 creating SNAPlus2 profiles 8 2 DB2 VM 14 4 number of database link connections 13 5 password length 16 4 user ID length 16 4 APPC VTAM Support AVS also see AVS 14 4 known restrictions 2 4 Index 1 APPC LU6 2 parallel session limits on AIX 7 2 protocol on HP UX 8 1 on Solaris 6 1 side information profile on AIX 7 3 APPEND command supported by COPY 12 6 application authenticating logons 14 1 portability 1 12 server support 1 4 application development on the gateway 1 13 application program interface API 10 2 APPN node advanced peer to peer networking node on AIX 7 3 support requires VTAM Version 4 on AIX 7 3 architecture of the gateway 1 7 array size fetch reblocking 1 11 how determined 13 2 AS 400 command DSPRDBDIRE 5 4 communications configuring 5 3 files and file members accessing 12 3 library name DRDA_PACKAGE_COLLID C 7 ASCII code page D 4 sort order 13 19 tables known restrictions 1 14 translated from EBCDIC 13 21 US7ASCII D 5 US7ASCII as default D 3 authority CONNECT 14 4 execute 14 4 autonomy site 1 7 available products menu 4 4 AVS also see APPC VTAM Support 2 4 configuring 5 6 DB2 VM 14 4 mapping user IDs 2 4 14 4 mapping user IDs DB2 VM known restrictions 2 4 mapping user IDs with DB2 VMT 14 4 binary data non character 13 21 Bind Package Stored Procedure DB2 400 5 3 DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6
87. 17 DRDA_LOCAL_NODE_NAME Default value AIX RS6K Range of values any alphanumeric string 1 to 8 characters in length Syntax DRDA_LOCAL_NODE_NAME name DRDA_LOCAL_NODE_NAME specifies the name by which the gateway will be known to the DRDA Server This name is used internally by the DRDA Server to identify the local node C 4 18 DRDA MBCS TO GRAPHIC Default value FALSE Range of values TRUE FALSE Syntax DRDA_MBCS_TO_GRAPHIC TRUE FALSE DRDA_MBCS_TO_GRAPHIC directs the gateway to convert multi byte data that has been sent from Oracle to the DRDA database into pure double byte characters This parameter is primarily intended to be used with bind variables in order to ensure that the data is properly formatted and will therefore be acceptable to the DRDA Server It applies only to INSERT SQL statements that are using bind variables When used in combination with the DRDA_GRAPHIC_LIT_CHECK parameter this parameter can help ensure that data that is being inserted into a Graphic column is handled correctly by the target DRDA Server C 4 19 DRDA_OPTIMIZE_QUERY Default value TRUE Range of values TRUE FALSE Syntax DRDA_OPTIMIZE_QUERY TRUE FALSE DRDA_OPTIMIZE_QUERY enables or disables the distributed query optimizer DQO capability Refer to Performing Distributed Queries on page 12 4 in Chapter 12
88. 2 14 3 2 Links and CONNECT Clausen iia 14 2 4d BECP 7 LP SOCUri by pcre testes A eine fierce a E O ENE NE neue 14 3 14 5 Processing Inbound Connections aaa 14 3 14 5 1 User LD Map pings wii i a aa ot r d 14 3 14 6 Passwords in the Gateway Initialization File u ue eee 14 5 Migration and Coexistence with Existing Gateways 15 1 Migrating Existing V4 V8 or V9 Gateway Instances to New Release 15 1 15 2 Backout Considerations When Migrating to New Releases 1 11 11 141411111111111 15 2 15 3 New and Changed Parameters When Migrating to Release 108 15 2 vii 16 viii 15 3 1 ENNA ET NE tE INEA KET RELATES IA A A ai 15 2 15 3 2 Parameters That Have Been Changed in Usage aaa 15 2 15 3 3 Parameters That Have Been Renamed cccccessssssessesssescesecssceseecsecssesaeceecsecneseseeeeses 15 3 15 3 4 Obsolete Parametros 15 3 15 4 DRDA Server Considerations cuotas AUE a EA elit bojev ii 15 3 15 5 Oracle Net Considerations e nana 15 4 Error Messages Diagnosis and Reporting 16 1 Interpreting Gateway Error MessageS aaa ener neanenenena 16 1 16 1 1 Errors Detected by the Oracle Integrating Server 16 1 16 1 2 Errors Detected by the Gateway 16 2 16 1 3 Errors Detected in the DRDA Software 16 2 16 1 4 C mmiunicatoRtEFofS s wa A A i SONIA 16 2 16 1 5 Errors Detected by the Server Dat
89. 2 0S390 DB2 400 or DB2 UDB then run data dictionary scripts If your DRDA Server is DB2 05390 DB2 400 or DB2 UDB then run the following scripts to create the Data Dictionary tables and view Step 1a Upgrading from a previous gateway version If you are upgrading from a previous version of the gateway then run the dropold sql script to drop the old data dictionary definitions Step 1b Creating the Data Dictionary tables and views Run the g4ddtab sql and g4ddvwXX sql scripts to create the Data Dictionary tables and views u g4ddvwr7 sql DB2 08390 V7 RACFsecurity U g4ddvws7 sql DB2 08390 V7 DB2 security u g4ddvwr8 sql DB2 0S390 V8 RACFsecurity U g4ddvws8 sql DB2 08390 v8 DB2 security g4ddvw51 sql DB2 400 V5 1 g4ddvw52 sql DB2 400 V5 2 g4ddvwu7 sql DB2 UDB V7 g4ddvwu8 sql DB2 UDB V8 Step 2 DB2 UDB or other server Depending on your DRDA Server perform one of the following steps 11 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Accessing the Gateway from Other Oracle Databases Step 2a If server is DB2 UDB grant authority to package If your DRDA Server is DB2 UDB then the ORACLE2PC table has already been created see the previous sections For all users to be able to use the table run o2pcg sql granting authority to all users Step 2b If server is not DB2 UDB create the ORACLE2PC table If your
90. 2 UDB 5 4 DB2 VM 5 5 considerations for binding packages 15 3 copying data from Oracle server 12 6 to Oracle server 12 7 database link behavior 13 5 default port number for TCP IP configuration 9 1 default TP name on HP UX 8 10 on Solaris 6 10 functions 13 18 Hostname or IP Address configuring TCP IP worksheet E 3 languages and character sets in configuration D 6 Logical Unit LU IBM Communication Server product on AIX 7 4 SNAP IX product on Solaris 6 11 SNAPlus2 product on HP UX 8 11 partner LU on HP UX 8 8 on Solaris 6 9 port number TCP IP 9 1 Service Port Number configuring TCP IP worksheet E 3 stored procedures 13 3 VTAM definitions and local LU names on HP UX 8 8 on Solaris 6 8 DRDA_CAPABILITY parameter 13 19 DRDA_CMSRC_CM_IMMEDIATE parameter C 3 DRDA_CODEPAGE_MAP parameter D 6 DRDA_COMM_BUFLEN parameter C 2 DRDA_CONNECT_PARM SNA format parameter C 3 DRDA_CONNECT_PARM TCP IP format parameter C 3 DRDA_CONNECT_PARM parameter communication errors 16 2 DRDA_DEFAULT_CCSID parameter C 3 DRDA_DESCRIBE_TABLE parameter defined C 4 known restrictions 2 3 DRDA_DESCRIBE_TABLE FALSE initialization parameter known restrictions 2 3 DRDA_DISABLE_CALL parameter binding the DRDA gateway package 11 5 defined C 4 DRDA_FLUSH_CACHE parameter C 4 DRDA_GRAPHIC_LIT_CHECK parameter C 5 DRDA_GRAPHIC_PAD_SIZE parameter C 4 DRDA_GRAPHIC_TO_MBCS parameter C 5 DRDA_ISOLATION_LEVEL parameter C
91. 2 UDB INTERSECT is compatible and MINUS is translated to EXCEPT 13 7 DRDA Data type to Oracle Data type Conversion To move data between applications and the database the gateway binds data values from a host variable or literal of a specific data type to a data type understood by the database Therefore the gateway maps values from any version of the DRDA Server into appropriate Oracle data types before passing these values back to the application or Oracle tool The following table lists the data type mapping and restrictions The DRDA Server data types that are listed in the table are general Refer to documentation for your DRDA database for restrictions on data type size and value limitations Table 13 6 datatype Mapping and Restrictions DRDA Server Oracle External Criteria CHAR N CHAR N N 255 VARCHAR N VARCHAR2 N N 2000 LONG 2000 lt N 32740 LONG VARCHAR N VARCHAR2 N N 2000 LONG VARCHAR N LONG 2000 lt N lt 32740 CHAR N FOR BIT DATA RAW N N 255 VARCHAR N FOR BIT IRAW N 1 N 255 DATA VARCHAR N FOR BIT LONG RAW N 255 lt N 32740 DATA LONG VARCHAR N RAW N 1 N 255 FOR BIT DATA LONG VARCHAR N LONG RAW N 255 lt N 32740 FOR BIT DATA DATE DATE Refer to Performing Date and Time Operations TIME CHAR 8 See Performing Date and Time Operations TIMESTAMP CHAR 26 See Performing Date and Time Operations GRAPHIC CHAR 2N IN lt
92. 3 Oracle servers distributed database 10 2 procedure 1 6 table 1 5 transaction program creating communication server profiles 7 1 hardware memory requirements 3 2 userid and password 12 2 remote node definition creating a link station SNAP IX on Solaris 6 6 SNAPlus2 on HP UX 8 6 renamed parameters 15 3 REPLACE command supported by COPY 12 6 replication 12 6 requirements hardware 3 1 software 3 2 RESULT 13 4 result sets columnsin 1 12 retrieving result sets through passthrough 1 11 REVISE SALARY stored procedure 13 4 ROWID Oracle column known restrictions 2 6 S sample files B 1 listener ora file B 2 SQL scripts 11 6 tnsnames ora file B 2 SAP dialog box 6 5 8 5 number 6 7 8 7 SAVEPOINT known restrictions 2 4 schema privileges CREATEIN 5 5 scripts dropold sql 11 6 Index 15 g4ddtab 11 6 g4ddview sql 11 6 SDLC Coaxial network attachment 3 2 security Advanced Security 1 5 DRDA_SECURITY_TYPE C 9 encryption 10 4 for session use 6 11 8 10 overview 14 1 siteautonomy 1 7 validation forSNA 6 11 7 4 8 11 for TCP IP 14 3 SELECT and array size 1 11 SELECT operation 13 2 SELECT statement fetch reblocking 13 2 read only gateway 12 5 retrieving results sets 13 27 SELECT WHERE SQL clause 13 24 semantics 13 18 server database error 16 3 server profiles IBM Communication Server product on AIX 7 1 SNAP IX product on Solaris 6 1 SNAPlus2 product on HP UX 8
93. 3 on Solaris 6 3 NLS_LANG client character set D 3 description of use D 2 ORA NLS33 D 2 ORACLE HOME 4 3 errd mapped error example 16 4 errmc CPI C routine 16 2 errmc field lists any error tokens 16 2 error tokens 16 3 mapped error example 16 4 errp errp field indicates program that detected error 16 2 error 12660 test error for Advanced Security 10 4 array errd 16 3 basic description 16 1 change ORA 09100 to ORA 28500 16 2 change ORA 09101 to ORA 28501 16 2 codes drc 16 2 grc 16 2 communication 16 2 date D 5 detected by Oracle integrating server 16 1 by server database 16 3 by the gateway 16 2 in DRDA software 16 2 drc field 300xx 16 5 7xx 16 4 HGO 00706 16 2 Index 7 interpreting error messages 16 1 mapped sqlstate 16 3 messages Oracle LONG datatype is toolong 13 21 SNA Security Option IBM Communication Server product on AIX 7 5 SNAP IX product on Solaris 6 13 SNAPlus2 product on HP UX 8 13 messages amp codes 16 1 obsolete parameters 15 3 ORA 00001 index constraint violated 16 3 ORA 00942 mapped error example 16 4 object name too long 16 3 ORA 01017 logon denied 16 3 ORA 01031 insufficient privileges 16 3 ORA 01460 invalid CCSID 16 3 ORA 01476 divide by zero 16 3 ORA 02019 16 2 ORA 2025 when using INSERT command 12 6 ORA 28500 was ORA 09100 16 2 ORA 28501 communication error 16 2 was ORA 09101 16 2 ORA 9100 to ORA 9199 16 2 Oracle map
94. 8 12 IBMRDB Mode Dialog Box Now that the Mode has been defined create the CPI C Side Information Profile which the gateway will use as a connection name From the menu select APPC and CPI C In the CPI C destination names dialog box see Figure 8 13 click Add to add a new profile Figure 8 13 CPI C Destination Names Dialog Box In the CPI C destination dialog box see Figure 8 14 enter the Profile name Partner TP Partner LU mode and Security option The default TP name of the mode DRDA Server will typically be a Service TP named 07F6C4C2 For the Partner LU enter either the full LU name or the alias created previously Enter IBMRDB for the mode name Lastly choose the type of security these sessions will use This will affect how session authorization is done Click OK 8 10 Oracle Transparent Gateway for DRDA Installation and User s Guide Using SNA Session Security Validation Figure 8 14 CPI C Destination Dialog Box 8 7 Using SNA Session Security Validation When the database link request for the gateway begins the gateway attempts to start an APPC conversation with the DRDA Server Before the conversation can begin a session must start between the HP9000 host LU and the DRDA Server LU SNA and its various access method implementations including SNAPlus2 and VTAM provide security validation at session initiation time allowing each LU to authenticate its partner This is carried out entirely by net
95. ACF can be used This is not always the case however because each of the IBM DRDA Servers can be configured to process inbound user IDs in other ways 6 8 2 SNA Security Option SECURITY SAME If DRDA_SECURITY_TYPE SAME is specified then the gateway allocates the conversation with SNA option SECURITY SAME and the following information is sent to the DRDA Server u If the database link has explicit CONNECT information then the specified user ID is sent u If the database link has no CONNECT clause and if the application has logged into the Oracle integrating server with an explicit user ID and password then the Oracle user ID is sent u Ifthe application logs in to the Oracle integrating server with operating system authentication and if the database link lacks explicit CONNECT information then no user ID is sent If no user ID is sent and if the DRDA Server is not configured to assign a default user ID then the connection fails For this option to function properly SNAP IX requires that the effective user ID under which the gateway is executing must be a member of the system group In UNIX terms this means that the user ID must be defined with its primary group set to system In addition the owning user ID of the gateway executable must be set to the desired effective user ID and the set uid bit of the executable file permissions must 6 12 Oracle Transparent Gateway for DRDA Installation and User s Guide
96. ARS and HGAXMSOL The string after HGAPARS will be the incoming statement from the Oracle Database 10g Relationsl database Mangement System RDBMS The string after HGAXMSQL will be the outgoing statement after any date substitution is done This is the actual SQL statement which will be given to the DRDA Server When you have developed your application revert the PROGRAM value in the listener ora to its previous value and reload the listener to use the production gateway again You should also comment out the trace parameters in the Gateway Initialization Files Error Messages Diagnosis and Reporting 16 7 SQL Tracing and the Gateway 16 8 Oracle Transparent Gateway for DRDA Installation and User s Guide A Oracle DB2 Data Dictionary Views This appendix covers the Oracle Transparent Gateway for DRDA data dictionary views accessible to all users of Oracle Database Most of the views can be accessed by any user with SELECT privileges for DB2 catalog tables N A is used in the tables to denote that the column is not valid for the gateway This appendix contains the following sections Supported Views m Data Dictionary View Tables A 1 Supported Views The following is a list of Oracle data dictionary views that are supported by the gateway for DB2 05390 DB2 400 and DB2 UDB DRDA Servers The 10 2 release of the gateway does not have data dictionary view support for DB2 VM servers a AL CA
97. Also the value for DRDA_PACKAGE_NAME must be unique if you have any older versions of the gateway installed New packages replace any old packages with the same name causing versions of the gateway that use the old package to fail Refer to Appendix C for information on the parameters and their settings Configuring the Gateway 11 5 DRDA Gateway Package Considerations 11 5 1 2 Step 2 If using DB2 UDB then create ORACLE2PC table If your DRDA Server is DB2 UDB then create your ORACLE2PC table Refer to Binding Packages on DB2 Universal Database DB2 UDB on page 11 4 for information on creating the table 11 5 2 Sample SQL scripts SQL scripts are provided to perform steps such as creating the ORACLE2PC table removing obsolete tables and views using previous releases and creating tables and views to provide Data Dictionary support Choose the appropriate subdirectory for your DRDA Server platform from the following list u for DB2 OS390 choose tg4drda install db2 u for DB2 400 choose tg4drda install as400 m for DB2 VM choose tg4drda install db2vm u for DB2 UDB choose tg4drda install db2udb These scripts must be run on the DRDA Server platform using a database native tool such as SPUFI on DB2 08390 because no tool is provided with the gateway to execute these scripts Note that when running these scripts the user ID used must be suitably authorized 11 5 2 1 Step 1 If server is DB
98. CT USERENV language FROM DUAL USERENV LANGUAGE AMERICAN AMERICA WE8IS08859P1 Oracle Database server and Client Environment Variables NLS LANG lt GERMAN GERMANY WE8IS08859P1 National Language Support D 11 Example of NLS Configuration D 12 Oracle Transparent Gateway for DRDA Installation and User s Guide E Configuration Worksheet The table below is a worksheet that lists all of the parameter names and the reasons that you will need them for configuring the gateway and the Communications Interfaces SNA and TCP IP Use the worksheet to gather the specific information that you need before you begin the configuration process Table E 1 List of Parameters Needed to Configure the Gateway Reason Name of Parameter Needed Your Specific Parameters Here Oracle Home of the gateway ORACLE_HOME System ID of the gateway ORACLE_SID Primary Service Definition SNA Network Name Primary Service Definition Control Point Name Connection Properties Address Remote Network Address Connection Properties Address Remote SAP Address System Identification Local Node Name and Remote Node Name For Each Network Name System Identification Local Node Name and Remote Node Name Control Point Name System Identification Local Node Name and Remote Node Name Local No
99. Column The DB2 ROWID column is not compatible with the Oracle ROWID column Because the ROWID column is not supported the following restrictions apply u UPDATE and DELETE are not supported with the WHERE CURRENT OF CURSOR clause To update or delete a specific row through the gateway a condition style WHERE clause must be used Bug No 205538 When UPDATE and DELETE statements are used in precompiler and PL SQL programs they rely internally on the Oracle ROWID function Snapshots between Oracle Database and DB2 are not supported Snapshots rely internally on the Oracle ROWID column Oracle Bind Variables Oracle bind variables become SQL parameter markers when used with the gateway Therefore the bind variables are subject to the same restrictions as SQL parameter markers For example the following statements are not allowed WHERE x IS NULL WHERE X y CONNECT BY Is Not Supported Oracle Transparent gateway for DRDA does not support CONNECT BY in SELECT statements COUNT Function Compatibility The following DRDA servers do not support all forms of the COUNT function specifically COUNT colname and COUNT ALL colname DB2 OS 390 V6 DB2 VM V6 and V7 The default for all DRDA server platforms except DB2 VM is for all forms of COUNT to be passed to the DRDA server as it is For DB2 VM the forms COUNT colname and COUNT ALL
100. DB2 DB2 UDB is frequently used as an abbreviation for DB2 Universal Database 1 5 Architecture The Oracle Transparent Gateway for DRDA works with the Oracle Database 10g Introduction 1 7 Architecture to shield most of the differences of the non Oracle database from Oracle applications This means that the Oracle applications can access the Oracle Database 10g data and the DRDA database data as if it were Oracle Database data located at the Oracle integrating server The architecture consists of the following main components u Client The client is an Oracle application or tool u Oracle integrating server The Oracle integrating server is an Oracle Database instance accessed by an Oracle Database 10g with procedural and distributed options Usually the Oracle integrating server is installed on the same host as the gateway but this is not a requirement The Oracle integrating server and the gateway communicate in the normal Oracle Database to server manner If the Oracle integrating server is not on the host where the gateway resides then you must install the correct Oracle networking software on the platform where the server resides For Oracle Database 10g you must install Oracle Net on the Oracle Database 10g machine ua Oracle Transparent Gateway for DRDA The gateway must be installed on hosts that are running the appropriate operating system If the Oracle integrating server is not on the same host then you must als
101. DB2 VM Step 3 Define the Recovery user ID m Step 4 Determine DRDA location name for DB2 VM Instance Step 1 Configure the Communications Server If you are using SNA then configure VM VTAM and AVS for the SNA connection from the host If you are using TCP IP then configure the TCP IP Service Step 2 Define the user ID that owns the package During gateway configuration you will need to execute the Bind Package Stored Procedure to bind the gateway package on the DRDA Server To properly bind the package the user ID and password used when the procedure is executed either implied as the current Oracle user or explicitly defined in the CREATE DATABASE LINK command must have proper authority on the DRDA Server to create the package This user ID should be used to create and own the ORACLE2 PC two phase commit table The user ID that is used to bind or rebind the DRDA package must have the following privileges on the DRDA Server u Package privileges of BIND COPY and EXECUTE a Collection privilege of CREATE IN u System privileges of BINDADD and BINDAGENT Choose a user ID now that will own the package and ORACLE2PC table Ensure that this user ID is defined to DB2 VM and VM Step 3 Define the Recovery user ID During gateway configuration the recovery user ID and password are specified in the Gateway Initialization File using the DRDA_RECOVERY_USERID and DRDA_RECOVERY_PA
102. DEXES unicas loas id A 12 A 2 23 USER OBJECTS cuasi iia dile vj Sidi IH ETA a A 13 A 2 24 USER SYNONYMS e ata RI Mm nei aoe A 14 A 2 25 A 2 26 A 2 27 A 2 28 A 2 29 USER TABLES ia Sin nena epa dn WON oh NA AE anni A 14 USER TAB COLUMNS wama rite EEA a OOO A 15 USER TAB COMMENTS owak i NBA EA WEW A 16 USER USERS cun iaa A 16 USER VIEWS yere brani Sebe a vole te avti ina iii ady A 17 Sample Files B 1 B 2 B 3 Sample Gateway Initialization File ene B 1 Sample Oracle Net tnsnames ora File nee ennnaa B 2 Sample Oracle Net listener ora File B 2 DRDA Specific Parameters C 1 C 2 C 3 C 4 C 4 1 C 4 2 C 4 3 C 4 4 C 4 5 C 4 6 C 4 7 C 4 8 C 4 9 C 4 10 C 4 11 C 4 12 C 4 13 C 4 14 C 4 15 C 4 16 C 4 17 C 4 18 C 4 19 C 4 20 C 4 21 C 4 22 C 4 23 C 4 24 C 4 25 C 4 26 C 4 27 C 4 28 C 4 29 C 4 30 Modifying the Gateway Initialization File C 1 Setting Parameters in the Gateway Initialization File oconconicincncononenennonnnnnncnrenernrnereroso C 1 Syntaxand Us tai ae C 1 Gateway Initialization File Parameters ea C 2 DRDA CACHE TABLE DESE dci zn ady wia iia adi C 2 DRDA CAPABIE TINE ona A A E A edhe C 2 DRDA CODEPAGE MAP aaa C 2 DRDA COMM BUFLEN occ ME th ee I pli C 2 DRDA CONNECT PARM SNA format C 3 DRDA CONNECT PARM TCP IP format nana C 3 DRDA CMSRC CM IMMEDIATE aaa C 3 PRDA DEFAULCESID x az Addi Badia aeons C 3 DRDA DESCRIBE TABLE a
103. DRDA Server is not DB2 UDB then the ORACLE2PC table must be created Run o2pc sql 11 6 Backup and Recovery of Gateway Configuration The configuration of the gateway is stored in the Gateway Initialization File This file is stored in the ORACLE HOME tg4drda admin directory The Gateway Initialization File is a simple text file You may back up this file by using an archiving tool of your choice 11 7 Configuring the Oracle Integrating Server 11 7 1 Step 1 11 7 2 Step 2 Configure the Oracle integrating server regardless of the platform on which it is installed It can be on the host but this is not required Create a database link To access the DRDA Server you must create a public database link A public database link is the most common of database links Refer to Processing a Database Link on page 12 1 for information on creating database links In the following example Oracle Database and the gateway are on the same host CREATE PUBLIC DATABASE LINK DB2 USING tns name entry Note The user ID creating the public database link must have the CREATE PUBLIC DATABASE LINK privilege Create synonyms and views To facilitate accessing data using the gateway define synonyms and views for the DRDA data tables If needed perform GRANT statements to ensure that the synonyms and views are accessible to the appropriate groups of users Refer to Using the Synonym Feature on page 12
104. ECT_PARM specifies the Side Information name Refer to Chapter 6 Chapter 6 Chapter 7 and Chapter 8 for details C 4 6 DRDA CONNECT PARM TCP IP format Default value DRDACON1 446 Range of values Any alphanumeric string 1 to 255 characters in length Syntax DRDA CONNECT PARM hos tname ip address port DRDA CONNECT PARM specifies the TCP IP hostname or IP Address of the DRDA Server and as an option the Service Port number on which the DRDA Server is listening For more information about the port number refer to Port Number on page 9 1 C 4 7 DRDA_CMSRC_CM_IMMEDIATE Default value FALSE Range of values TRUE FALSE Syntax DRDA_CMSRC_CM_IMMEDIATE TRUE FALSE DRDA_CMSRC_CM_IMMEDIATE sets the SNA session allocation mode A setting of FALSE causes the gateway to wait for a free session if no free sessions exist A setting of TRUE causes the gateway to fail the allocation immediately if no free sessions exist C 4 8 DRDA_DEFAULT_CCSID Default value None Range of values Any supported DRDA Server CCSID Syntax DRDA_DEFAULT_CCSID ccsid DRDA_DEFAULT_CCSID specifies the default CCSID or character set codepage for character set conversions when the DRDA Server database indicates that a character string has a CCSID of 65535 DRDA Servers use CCSID 65535 for columns specified as FOR BIT DATA In most cases this parameter sho
105. GOVERNMENT RIGHTS Programs software databases and related documentation and technical data delivered to U S Government customers are commercial computer software or commercial technical data pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication disclosure modification and adaptation of the Programs including documentation and technical data shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement and to the extent applicable the additional rights set forth in FAR 52 227 19 Commercial Computer Software Restricted Rights June 1987 Oracle Corporation 500 Oracle Parkway Redwood City CA 94065 The Programs are not intended for use in any nuclear aviation mass transit medical or other inherently dangerous applications It shall be the licensee s responsibility to take all appropriate fail safe backup redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes and we disclaim liability for any damages caused by such use of the Programs Oracle JD Edwards PeopleSoft and Retek are registered trademarks of Oracle Corporation and or its affiliates Other names may be trademarks of their respective owners The Programs may provide links to Web sites and access to content products and services from third parties Oracle is not responsible for the availability o
106. IBMRDB mode dialog box 8 9 DRDA mode on Solaris CPI C destination dialog box 6 11 IBMRDB mode dialog box 6 10 implementation 1 9 implicit data conversion 13 18 implicit protocol conversion 1 4 IMS transaction 13 5 IN and OUT columns multi byte support D 9 inbound connections processing 14 3 initdrdahoal ora sample B 1 initialization parameters new since V4 gateway 15 2 initsid gtwboot file migrating 15 1 initsid ora file communication errors 16 3 migrating 15 1 NLS parameters D 5 input bind variables 13 23 INSERT known restrictions 2 3 operation 13 2 Oracle SQL command known restrictions 2 3 read only gateway 12 6 SQL clause 13 24 Index 10 statement dates 13 24 passthrough SQL feature 13 25 INSERT command known restrictions 2 3 not supported 12 6 supported by COPY 12 6 installation checklist for gateway installation 4 2 checklists 4 2 10 1 installing the gateway from CD 4 2 overview 4 2 internal tracing C 11 Internet support 1 4 INTERSECT SQL set operators and clauses 13 20 IPC adapter B 2 ISO standard 1 5 isolation level DRDA_ISOLATION_LEVEL C 5 J JOIN capability 1 4 JOIN SQL statement 13 2 K keywords LISTENER B 2 known restrictions accessing DB2 alias objects 2 3 AVS mapping user IDs 2 4 bind variables become SQL parameter markers 2 6 binding the DRDA gateway package on DB2 UDB 2 4 CONNECT BY not supported SQL limitations 2 6 datatype limitations
107. IX product on Solaris 6 1 SNAPlus2 product on HP UX 8 1 Advanced Security CHECKSUM command 10 4 encryption 10 4 international version types supported 10 4 resetting configuration parameters on gateway 10 5 setting test parameters for gateway 10 4 setting test parameters for Oracle integrating server 10 4 setting up for test 10 4 testing gateway and Oracle integrating server 10 5 export encryption algorithms 10 4 function of the gateway 1 5 purpose 1 5 testerror 10 5 12660 10 4 AGW ADD USERID command 14 4 AGW DELETE USERID command 14 4 Index AIX AIX_RS6K default value for DRDA LOCAL NODE NAME C 6 alias CPI C destination on HP UX 8 10 on Solaris 6 11 DB2 C 4 Ethernet parameters 8 8 local LU alias 6 8 partner LU 7 3 alias objects DB2 known restrictions 2 3 ALL_CATALOG view A 2 ALL COL COMMENTS view A 2 ALL CON COLUMNS view A 2 ALL CONSTRAINTS view A 3 ALL DB LINKS data dictionary view 12 3 ALL INDEXES view A 3 ALL OBJECIS view A 5 ALL SYNONYMS view A 6 ALL TAB COMMENTS view A 8 ALL TABLES view A 6 ALL USERS view A 9 ALL VIEWS view A 9 allocation mode SNA session DRDA CMSRC CM IMMEDIATE C 3 ALTER session statement 12 2 ANSI standard SOL 1 5 1 12 API application program interface 10 2 APPC concurrent connections 3 1 configuring IBM Communication Server on AIX 7 1 configuring SNAP IX on Solaris 6 1 configuring SNAPlus2 on HP UX 8 1 conversations on AIX 7
108. Logon to Oracle AREARERRRERE RRA AER RRE RARE RRA RARE RE RRA RRE RRA E RARE REE RARA REA RR RRA RARA RARAS EXEC SQL CONNECT username IDENTIFIED BY password printf InConnected to ORACLE as user s n username arr Delete any existing rows from DB2 table EXEC SQL DELETE FROM SCOTT DEPTEGTWLINK EXEC SOL COMMIT Pre eae aaa Sass SE App begin pl sql block sy RRR BREE RRRER RRR E EKER EK EKER EKER EERE ERE RARA RARE RRE RE EERE RE REE kok ERE REE ERERREEEEREE Insert 1 row into DB2 table SCOTT DEPT by invoking DB2 stored procedure DB2INS The DB2 stored procedure will perform the INSERT bj E SCOTT DEPT table is defined on DB2 as 7 ky za DEPTNO INTEGER 37 JE DNAME CHAR 14 af 7 LOC VARCHAR 13 p AERERRARERER ERE ERK ERE EEE ERE RE RARE RR RARA RARA ARE RE RE RE RE ERE RK ER EKER ERE EREREREE EXEC SQL EXECUTE BEGIN dept_no 10 dept_name gateway location ORACLE DB2INSEGTWLINK dept_no dept_name location code END END EXEC Seca A ee end pl sql block y Ftkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Check the SQLCODE returned from the stored procedures INSERT y FkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkJ if code 0 printf DB2INS reports successful INSERT n else printf DB2INS reports
109. NGTH Length of the character set GLOBAL_STATS N A USER_STATS N A AVG_COL_LEN Average length of the column in bytes CHAR_LENGTH Displays the length of the column in characters CHAR_USED N A A 2 11 ALL TAB COMMENTS Comments on tables and views accessible to the user column name description OWNER Owner of the object TABLE_NAME Name of the object TABLE_TYPE Type of the object COMMENTS Comments on the object A 8 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dictionary View Tables A 2 12 ALL_USERS Information about all users of the database column name description USERNAME Name of the user USER_ID N A CREATED N A A 2 13 ALL VIEWS Text of views accessible to the user column name description OWNER Owner of the view VIEW NAME Name of the view TEXT LENGTH Length of the view text TEXT View text Only the first row of text is returned even if multiple rows exist TYPE TEXT LENGTH Length of the type clause of the typed view TYPE TEXT Type clause of the typed view OID TEXT LENGTH Length of the WITH OID clause of the typed view OID TEXT WITH OID clause of the typed view VIEW_TYPE_OWNER Owner of the type of the view if the view is a typed view VIEW_TYPE Type of the view
110. Networking Internet and Intranet Support 1 4 1 3 4 Dynamic Dictionary Mapping seen 1 5 1 3 5 SOL nmre na Ai EME SNS NENA OD KAD V ROE SER SEIN eas 1 5 1 3 6 Data Definition Lan uae ua iona tepe Hane aaa 1 5 1 3 7 Data Control Language sissies iesnas baitda kiiin 1 5 1 3 8 Passthrough and Native DB2 SOL aken 1 5 1 3 9 Stored Procedures nati an ia Sith Ra pali ie fined 1 6 1 3 10 ATI SUA BESE EEA wini aaa aka wadia a dat ta AAA 1 6 1 3 11 Oracle Database Technology and Tools aaa 1 6 1 3 12 SOL PluS wena aka OWA OZGA BE We EA ee 1 6 1 3 13 Two Phase Commit and Multi Site Transactions s sssassu asa aaa aaa aaa nawa aaa ni aa nawa 1 6 1 3 14 Site AUTONOMY wada AW EGA S E A OOO BO OOOO A 1 7 1 3 15 Migration and Coexistence kake 1 7 1 3 16 A odkod Ned SNE o R o ANA NA DOW AAAA 1 7 14 TEMS tesi abd iki 1 7 1 5 Arehitecture a spiti nite iu ea bla navija kane dlaki eb 1 7 1 6 Implementation isin hs PS eb do AA DA eve ii edi OW 1 9 1 7 How the Gateway WorkS aaa anawa 1 9 1 8 Oracle Tools and the Gateway aaa A 1 10 1 8 1 SOLR PIUSA Re ARONA WA ORA WOW A OWO 1 10 1 9 PeatuUreS nana RR 1 10 Release Information 2 1 Product Set mek i OZ W AA a lid OC NC NASE A NO 2 1 2 2 Changes anid Enhancements aiii ida NW AGA 2 1 2 3 Product Migration seeda asadas ca labo 2 1 2 4 Bugs Fixedin Release TO Dioni ii ei dit 2 2 2 5 Known Problems cialis Tala A AD
111. ON logpath LOG_DESTINATION specifies the destination for gateway logging and tracing This parameter should specify a file If the file already exists it will be overwritten After any failure to open the logpath a second attempt to open the default is made C 10 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Initialization File Parameters Usually LOG_DESTINATION should specify a directory If it is specified as a file and if two or more users simultaneously use the same instance of the gateway then they are writing to the same log The integrity of this log is not guaranteed If you do not specify this parameter then the default is assumed C 4 37 ORA_MAX_DATE Default value 4712 12 31 Range of values Any valid date less than 4712 12 31 Syntax ORA MAX DATE yyyy mm dd ORA MAX DATE specifies the gateway maximum date value If the fetched date value is larger than 4712 12 31 the gateway replaces the date value with the value defined by the ORA MAX DATE parameter Any date between January 1 4712 BC and December 31 4712 AD is valid C 4 38 ORA NLS10 Default value SORACLE HOME nls data Range of values Any valid NLS directory path Syntax SET ORA_NLS10 nlspath ORA NLS10 specifies the directory to which the gateway loads its character sets and other language data Normally this parameter does not need to be set Some configurations however may require th
112. ORACLE Oracle Transparent Gateway for DRDA Installation and Users Guide 10g Release 2 10 2 for UNIX B16217 01 June 2005 Oracle Transparent Gateway for DRDA Installation and User s Guide 10g Release 2 10 2 for UNIX B16217 01 Copyright 2005 Oracle All rights reserved Primary Author Maitreyee Chaliha Contributing Author Peter A Castro The Programs which include both the software and documentation contain proprietary information they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright patent and other intellectual and industrial property laws Reverse engineering disassembly or decompilation of the Programs except to the extent required to obtain interoperability with other independently created software or as specified by law is prohibited The information contained in this document is subject to change without notice If you find any problems in the documentation please report them to us in writing This document is not warranted to be error free Except as may be expressly permitted in your license agreement for these Programs no part of these Programs may be reproduced or transmitted in any form or by any means electronic or mechanical for any purpose If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government the following notice is applicable U S
113. ORA_NLS33 parameter C 11 description D 2 ORA 00001 error index constraint violated 16 3 ORA 00942 error mapped error example 16 4 object name too long 16 3 ORA 01017 error logon denied 16 3 ORA 01031 error insufficient privileges 16 3 ORA 01460 error invalid CCSID 16 3 ORA 01476 error divide by zero 16 3 ORA 02019 error 16 2 ORA1 Oracle instance 13 2 ORA2 Oracle instance 13 2 ORA 2025 error when using INSERT command 12 6 ORA 28500 error Index 12 was ORA 09100 16 2 ORA 28501 error communication error 16 2 ORA 9100 to ORA 9199 errors 16 2 Oracle directory tree 4 2 mapped error codes 16 3 products compatibility 1 10 RAW datatype C 3 snapshots 12 6 Oracle Database stored procedure defined 13 2 Oracle integrating server accessing gateway from other Oracle Database servers 11 7 accessing other DRDA servers 11 8 accessing the gateway 12 3 architecture 1 8 configuration 11 7 definition 1 7 errors detected 16 1 requirements 3 3 using in application development 13 1 Oracle Net 15 4 and application development 1 13 and distributed processing 10 2 and remote data access 1 12 and server coexistence 1 8 API 10 2 compatibility with SQL Net 10 2 configuring 10 3 distributed database 10 2 processing 10 2 editing to set up security test 10 4 Heterogeneous Services HS facility 10 2 integrated with Oracle Database server 1 6 introduction 10 2 operating system authentication 14 2
114. Oracle9i server release 9 2 Oracle Networking Products If the Oracle integrating server is not on the same host as the gateway then Oracle Net is required to support communication between the host and the Oracle integrating server The following Oracle networking products are required on the same system as Oracle Database 10g m Oracle Net Client 10 2 0 1 0 ua Oracle Adapter version 10 2 0 1 0 Oracle Net software is included in this Oracle Transparent Gateway for DRDA release Your gateway license includes a license for Oracle Net and an adapter of your choice This license restricts the use of Oracle Net for gateway access 3 3 Documentation Requirements In addition to the documentation provided with the Oracle Transparent Gateway for DRDA distribution kit the following Oracle documentation is recommended m Oracle Database Administrator s Guide m Oracle Database Application Developer s Guide Fundamentals a Oracle Database Heterogeneous Connectivity Administrator s Guide m Oracle Database Advanced Security Administrator s Guide a Oracle C Call Interface Programmer s Guide m Oracle Call Interface Programmer s Guide u SQL Plus User s Guide and Reference a PL SQL User s Guide and Reference System Requirements 3 3 Documentation Requirements u Oracle Database SOL Reference m Oracle Net Services Administrator s Guide m Oracle Net Services Reference Guide In addition to the Oracle documentation ensure that you h
115. Plus2 on HP UX 8 1 TCP IP DB2 400 5 3 DB2 0S390 5 2 DB2 VM 5 6 under Solaris 9 1 VM VTAM 5 6 CONNECT authority DB2 UDB 11 5 DB2 VM 14 4 CONNECT BY not supported known restrictions SQL limitations 2 6 CONNECT privilege DB2 UDB 5 5 CONNECT TO clause 12 2 contact information in configuring SNAplus2 6 7 8 7 convert character string 13 21 datatypes DRDA to Oracle datatypes 13 20 DATE 13 22 floating point to integer 13 25 inbound user ID 14 4 into most suitable datatype 13 25 SQL 1 10 to the numeric datatype 13 25 converter protocol 1 4 COPY command Oracle Database server to DRDA Server 12 6 COPY privilege DB2 0S390 5 2 DB2 VM 5 6 COPY SOL Plus command 12 6 substituted for INSERT known restrictions 2 3 copying data from the DRDA Server 12 7 from the Oracle server to DRDA Server 12 6 COS SQL function 13 7 COUNT function 13 25 CP Control Point for the Node 6 2 8 2 CPI C communication error messages 16 2 16 5 create Side Information Profile 6 10 8 10 profiles creating 6 9 8 9 routine 16 2 side information profile 6 10 8 10 CREATE command supported by COPY 12 6 CREATE DATABASE LINK command 12 2 DB2 VM 5 6 CREATE DATABASE statement client server configuration D 3 CREATE IN privilege DB2 0S390 5 2 DB2 VM 5 6 Index 4 CREATE PUBLIC DATABASE LINK privilege 11 4 11 7 CREATE TABLE statement 1 5 CREATEIN privilege DB2 UDB 5 5 CREATETAB authority 11 5 CREATE
116. RDA package to your DRDA Server 11 10 Gateway Installation and Configuration Complete The Oracle Transparent Gateway for DRDA installation and configuration process is now complete The gateway is ready for use 11 8 Oracle Transparent Gateway for DRDA Installation and User s Guide 12 Using the Oracle Transparent Gateway for DRDA Using the Oracle Transparent Gateway for DRDA involves connecting to the corresponding gateway system and the remote DRDA database associated with the gateway It is important to understand how to process and use database links Database links are discussed in detail in the Oracle Database Reference Read the database link information in that guide to understand database link processing Then proceed to read this chapter to understand how to set up a database link to a remote DRDA database This chapter contains the following sections u Processing a Database Link m Accessing the Gateway m Accessing AS 400 File Members u Using the Synonym Feature u Performing Distributed Queries u Read Only Gateway u Replicating in a Heterogeneous Environment u Copying Data from Oracle Database 10g to DRDA Server u Copying Data from DRDA Server to Oracle Database 10g Server m Tracing SQL Statements 12 1 Processing a Database Link The database and application administrators of a distributed database system are responsible for managing the database links that define paths to the DRDA database The tasks are
117. S view A 11 SER DB LINKS data dictionary view 12 3 SER INDEXES view A 12 SER OBJECTS view A 13 SER SYNONYMS view A 14 SER TAB COLUMNS view A 15 SER TAB COMMENTS view A 16 SER TABLES view A 14 SER USERS view A 16 SER VIEWS view A 17 SING clause 12 2 SING parameter modifying tnsnames ora file 10 3 sing the gateway 12 1 ENEE EEC CE Ca E El V VALUES clause functions not allowed by DB2 13 24 VARCHAR datatype 13 21 variable bind SQL passthrough 13 25 input bind 13 23 view catalog DB2 400 13 27 DB2 0S390 13 27 DB2 UDB 13 27 DB2 VM 13 27 creating 11 7 data dictionary emulation on DRDA Server 13 27 VM VTAM configuring 5 6 VSAM file 13 5 VTAM configuring DB2 08390 5 2 definitions relationship to SNAplus2 definitions 6 13 8 13 same local LU name as on remote DRDA Server 6 8 8 8 security validation 6 11 7 4 8 11 w WHERE clause known restrictions SQL limitations 2 6 SQL Set Clauses 13 20 WHERE CURRENT OF CURSOR clause known restrictions SQL limitations 2 6 wireless communication 1 5 X xsnaadmin creating SNA definitions 6 3 invoking 6 3 SNAP IX definitions 6 3 tool to configure SNAP IX 6 1 tool to create SNAP IX definitions 6 2 xsnapadmin creating SNA definitions 8 3 invoking 8 3 tool to configure SNAplus2 8 1 tool to create SNAplus2 definitions 8 2 X Windows 6 1 8 1 Z zoned decimal operations 13 25 Index 19 Ind
118. SOL expression forms do not work correctly with the gateway because of DRDA Serve limitations date number number date date number datel date2 DRDA Server does not allow number addition or subtraction with date data types The date and number addition and subtraction date number number 2 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Known Restrictions date date number forms are sent through to the DRDA Server where they are rejected Also DRDA Server does not perform date subtraction consistently When you subtract two dates datel date2 differing interpretations of date subtraction in the DRDA Server cause the results to vary by server Note Avoid date arithmetic expressions in all gateway SQL until date arithmetic problems are resolved Row Length Limitation Because of a restriction of the DRDA architecture rows with aggregate length exceeding 32KB in DRDA representation cannot be stored or retrieved LONG Data type in SQL Plus SOL Plus cannot fetch LONG columns from the Oracle Transparent Gateway for DRDA Dictionary Views Are Not Provided for DB2 VM Currently the Oracle Transparent Gateway for DRDA provides SQL for defining DB2 05390 DB2 400 and DB2 UDB views that emulate parts of the Oracle Database dictionary These are required for certain applications and tools that query dictionary tables View definitions for DB2 VM are not provided in this release
119. SSWORD parameters If a distributed transaction fails then the recovery process connects to the remote database using the user ID and password defined in these parameters This user ID must have execute privileges on the package and must be defined to the DRDA database If the user ID is not specified in DRDA_RECOVER_USERID then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt Determine the user ID and password you will use for recovery Step 4 Determine DRDA location name for DB2 VM Instance The DRDA location name is required as a gateway parameter To determine the location name issue thefollowing SQL query from an ISQL session SELECT CURRENT SERVER FROM any table where any table isa valid table with one or more rows If the value returned by this query is blank or null then the DRDA location name has not been established Contact the system administrator to set a location name for the instance 5 6 Oracle Transparent Gateway for DRDA Installation and User s Guide 6 Configuring SNAP IX Interfaces This chapter describes configuring the SNAP IX product on Solaris for usage with the Oracle Transparent Gateway for IBM DRDA SNAP IX provides SNA connectivity through the APPC LU6 2 protocol between the Sun host and the remote DRDA Server Read this chapter to provide information about creating server profiles This chapter con
120. Solaris 64 bit requires 1 25 GB u AIX5L requires 1 4 GB u HP UX 11 0 64 bit requires 1 2 GB a Linux Intel 32 bit and 64 bit requires 1 GB u Linux for S 390 requires 1 2 GB 3 2 Software Requirements The system software configuration that is described in this section is supported by Oracle as long as the underlying system software products are supported by their respective vendors Verify the latest support status with your system software vendors Operating System The operating systems that can be used are u Linux for Intel Pentium based 32 bit systems u Linux for Intel Itanium 2 based 64 bit systems u Linux for S 390 u Solaris 5 8 or later a AIX5L u HP UX 11 0 64 bit DRDA Databases You must have at least one of the following DRDA servers at a supported release level a DB2 OS390 su DB2 VM a DB2 400 3 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Documentation Requirements a DB2 Universal Database Communication Server Supported SNA network software are m Solaris SNAP IX Version 7 u AIX IBM Communications Server for AIX Version 6 0 u HP HPUX SNAPlus2 Link Release 11 x and HPUX SNAPlus2 API Release 11 x or higher are required m Linux 32 bit IBM Communications Server for Linux Version 6 2 Oracle Database The Oracle Database which is to act as the Oracle integrating server requires the latest released patch set for Oracle Database 10g release 10 2 0 10 1 0 or
121. Step 1 Choose the initsid ora file The initsid ora Gateway Initialization file defines the operating parameters for the gateway Samples tailored for each type of DRDA Server are provided as a starting point for tailoring to your particular installation The samples are stored in the SORACLE_HOME tg4drda admin directory The following is a list of the initialization files for various DRDA Server platforms a For DB2 OS390 initDB2 ora m For DB2 UDB initDB2UDB ora m For DB2 400 initAS400 ora m For DB2 VM initDB2VM ora Choose a sample initialization file and copy it within the same directory to the name of the gateway SID using the following naming convention initSID ora where SID is the chosen gateway SID For example if the chosen gateway SID were DRDA then the initialization file would benamed initDRDA ora Step 2 Tailor the initsid ora file After you have copied the sample initialization file you will need to tailor it to your installation While many parameters can be left to their defaults some parameters must be changed for correct operation of the gateway Attention should be given to the following DRDA and HS parameters Attention should also be given to the security aspects of the initialization file Chapter 14 Security Considerations contains details concerning encryption of passwords that would otherwise be embedded in the initialization file See Appendix C DRDA Specific P
122. TAB privilege DB2 0S390 5 2 DB2 UDB 5 5 creating anew directory 4 2 CPI C and mode definitions 6 9 8 9 database link 12 2 link station 6 6 8 6 local LU names 6 8 8 8 partner LUs 6 9 8 8 remote node definition 6 6 8 6 SNA definitions for the gateway 6 2 8 2 SNAplus2 profiles 6 2 8 2 cursor defining the number of 13 28 number of cursors DRDA PACKAGE SECTIONS C 8 stability DRDA ISOLATION LEVEL C 5 D data coercion 13 18 data control language DCL 1 5 DATA datatype 13 22 data definition language DDL 1 5 data dictionary support 11 6 using 13 27 views ALL DB LINKS 12 3 considerations for migration from previous releases 15 3 emulation on DRDA Server 13 27 for DB2 VM and DB2 UDB not supported A 1 list and descriptions A 2 supported for DB2 05390 and DB2 400 servers A 1 USER_DB_LINKS 12 3 database authorities CONNECT BINDADD and CREATETAB 5 5 catalogs 13 27 link behavior 13 5 binding the gateway package 11 4 creating 12 2 defining and controlling 14 2 dropping links 12 2 examining 12 3 guidelines 12 2 limits 12 3 processing 12 1 public 11 7 suffix 13 1 to identify the gateway 1 9 triggers 1 4 datatype character string 13 21 column ALL_TAB_COLUMNS A 8 column USER_TAB_COLUMNS A 15 conversion DRDA to Oracle datatypes 13 20 no control over 13 25 converting character string 13 21 data and time 13 22 differences between Oracle server and DRDA databas
123. TAI 0G m ALL COL COMMENTS L_CONS_COLUMNS iL CONSTRAINTS NDEXES ND_COLUMNS 1 OBJECTS L_ SYNONYMS 1 TAB COMMENTS TABLES TAB COLUMNS 1 USERS gt v v PP p p p p D P 1 VIEWS m COL PRIVILEGES u DICTIONARY u DUAL m TABLE_PRIVILEGES Oracle DB2 Data Dictionary Views A 1 Data Dictionary View Tables u USER_CATALOG u USER COL COMMENTS USER CONSTRAINTS a USER CONS COLUMNS u USER_INDEXES u USER_OBJECTS u USER_SYNONYMS u USER_TABLES u USER_TAB_COLUMNS m USER_TAB_COMMENTS u USER_USERS u USER_VIEWS A 2 Data Dictionary View Tables This section contains tables that describes describing data dictionary views In the following descriptions all are supported for DB2 OS390 and DB2 400 A 2 1 ALL_CATALOG All tables views synonyms and sequence accessible to the user column name description OWNER Owner of the object TABLE_NAME Name of the object TABLE_TYPE Type of object A 2 2 ALL COL COMMENTS Comments on columns of accessible tables and views column name description OWNER Owner of the object TABLE NAME Object name COLUMN NAME Column name COMMENTS Comments on column A 2 3 ALL CONS COLUMNS Information about a
124. Testing the Connection also be set The 1s 1 command shows the owning user ID and the setting of the set uid bit for the executable file The owning user ID can be changed by the root user with the chown command and the set uid bit can be set using the chmod u s command The gateway executable as installed by the Oracle Universal Installer has its set uid bit disabled The simplest way to cause the gateway to execute under an effective user ID that is a member of the system group is to change the owning user ID of the gateway executable to root Another way is to change the primary group for the owning user ID of the gateway executable to system However be careful when choosing the user ID Oracle recommends using root and recommends never changing the Oracle dba user ID primary group to system When the effective user ID is not a member of the system group a failure is generated when the gateway attempts to allocate a conversation with the DRDA Server and an error message is sent to the gateway user 6 9 Testing the Connection Before proceeding with the gateway configuration tasks in Chapter 11 Configuring the Gateway ensure that your connection is working Do this by starting the SNAP IX Node and then starting the individual link stations Figure 6 15 shows the relationship between SNAP IX definitions and the VTAM definitions on the remote host Configuring SNAP IX Interfaces 6 13 Testing the Connection Figure 6 15
125. UM services of Advanced Security m Wireless communication Oracle Mobile Agents an Oracle industry leading mobile technology enables wireless communication to Oracle Database 10g or to any databases that are accessible through the gateways This gives your field personnel direct access to enterprise data from mobile laptop computers 1 3 4 Dynamic Dictionary Mapping 1 3 5 SQL The simple setup of the gateway does not require any additional mapping Before an application can access any information the application must be told the structure of the data such as the columns of a table and their lengths Many products require administrators to manually define that information in a separate data dictionary stored in a hub Applications then access the information using the hub dictionary instead of the native dictionaries of each database This approach requires a great deal of manual configuration and maintenance on your part As administrators you must update the data dictionary in the hub whenever the structure of a remote table is changed Inefficient duplication is not necessary with Oracle Transparent Gateway for DRDA The gateway uses the existing native dictionaries of each database Your applications access data using the dictionaries designed specifically for each database which means no redundant dictionary ever needs to be created or maintained Oracle Transparent gateways ease your application development and maintenance by allo
126. US N A DOMIDX_OPSTATUS N A FUNCIDX_STATUS N A JOIN_INDEX N A IOT_REDUNDANT_PKEY_ELIM N A A 2 6 ALL_IND_COL UMNS ALL IND COLUMNS describes the columns of indexes on all tables that are accessible to the current user column names description INDEX_OWNER Owner of the index INDEX_NAME Name of the index TABLE_OWNER Owner of the table or cluster TABLE NAM ad Name of the table or cluster COLUMN NAME Column name or attribute of object type column COLUMN POSITION Position of a column or attribute within the index COLUMN LENGTH Indexed length of the column CHAR LENGTH Maximum codepoint length of the column DESCEND Whether the column is sorted in descending order Y N A 2 7 ALL OBJECTS Objects accessible to the user column name description OWNER Owner of the object OBJECT NAME Name of object SUBOBJECT NAM LEJ Name of the subobject OBJECT_ID Object number of the object DATA_OBJECT_ID Dictionary object number of the segment that contains the object OBJECT_TYPE Type of object CREATED N A LAST DDL TIME N A Oracle DB2 Data Dictionary Views A 5 Data Dictionary View Tables column name description TIMESTAMP N A STATUS State of the o
127. X Definitions icon ito didactica 6 3 6 6 2 Eonfiguring SNABP TD ee mae ia ca Ot dE A 6 3 10 6 7 Using SNA Session Security Validation ee 6 11 6 8 SNA Conversation SOCULILY ad do oto dO 6 12 6 8 1 SNA Security Option SECURITY lt PROGRAM ene 6 12 6 8 2 SNA Security Option SECURITY SAME aaa 6 12 6 9 Testing the ConneGHio sadza wa tad zaa ak AE 6 13 Configuring IBM Communication Server 7 1 Checklist for Configuring the Communications Interfaces 00 0 0 aa 7 1 7 1 1 Step 1 Configuring Communication Server Profiles 7 1 7 1 2 Step 2 Creating Communication Server Profiles for the Gateway 7 1 7 1 3 Step 3 Testing the Connection 7 3 7 2 Using SNA Session Security Validation i bassiner nEri 7 4 7 3 SNA Conversation Security ane natancna nanananana 7 4 7 3 1 SNA Security Option SECURITY PROGRAM ena 7 4 7 3 2 SNA Security Option SECURITY lt SAME ena ene 7 4 Configuring SNAPlus2 8 1 Checklist for Configuring the Communications Interfaces ene 8 1 8 2 Before YOU BEY eat ii SINE NANA a ONA 8 1 8 3 SNAPlus2 Configuration Tool 8 1 8 4 Creating SNAPlus2 Profiles for the Gateway 8 2 8 5 Independent Versus Dependent LUS eaa nee 8 2 8 6 Creating SNA Definitions for the Gate Way 8 2 8 6 1 Sample SNAPlus2 Definitions ee 8 3 8 6 2 Corifisuiring SNAPIU escoria AA A AO ao dia 8 3 8 6 3 Invoking
128. Y Whether an enabled constraint is enforced or unenforced LAST_CHANGE When the constraint was last enabled INDEX_OWNER N A INDEX_NAME N A A 2 5 ALL_INDEXES Description of indexes on tables accessible to the user column name description OWNER Owner of the index INDEX_NAME Name of the index INDEX_TYPE Type of the index TABLE_OWNER Owner of the indexed object TABLE_NAME Name of the indexed object TABLE TYPE Type of the indexed object UNIOUENESS Unigueness status of the index Oracle DB2 Data Dictionary Views A 3 Data Dictionary View Tables column name description COMPRESSION N A PREFIX LENGTH 0 TABLESPACE NAME Name of the tablespace containing the index INI TRANS N A MAX TRANS N A INITIAL EXTENT N A NEXT EXTENT N A MIN EXTENTS N A MAX EXTENTS N A PCT_INCREASE N A PCT_THRESHOLD Threshold percentage of block space allowed per index entry INCLUDE_COLUMN Column ID of the last column to be included in an index organized table FREELISTS Number of process freelists allocated to this segment FREELIST_GROUPS Number of freelist groups allocated to this segment PCT_FREE N A LOGGING Logging information BLEVEL Depth of the index from its
129. abase 16 3 16 2 Mapped EMOTS udac W AO ad Av R A OAI 16 3 16 3 Gateway Error Codes i eaten Mao undies tdi AC te 16 4 16 4 SQL Tracing and the Gateway aken 16 5 16 4 1 SQL Tracing in the Oracle Database 16 5 16 4 2 SOL Tracing in the Gateway zwa a oi ay iii 16 6 Oracle DB2 Data Dictionary Views A 1 5upp rted MIEWS iia A 1 A 2 Pata Dictionary View Tabl s swoi i O ANI O ada A 2 A 2 1 ALL CATALOG meria a nia ee a adi ada aaa A e PDA seasons A 2 A 2 2 Abb COF COMMENTS end A Ban Gate ie NA A 2 A 2 3 AEE CONS COLUMNIS uct ind a EE O A O eed A 2 A 2 4 ACLL CONSTRAINTS ad zde aid CZ ASA Ea dO eet A 3 A 2 5 ANO ESIANI BJ 4 OPERA A 3 A 2 6 ALE IND lt COEUMNS etz ie MI kil seine a jel edi A 5 A 2 7 ALL OBJECTS zt wawa nn wid ia a O Wh a hau eens ieee Ee oe A 5 A 2 8 ATEESYANONAM San A anar A 6 A 2 9 ALL TABLES paid dl ici ed A 6 A 2 10 ALI TAB COLUMNS A i oon She ted ee A SEE ee A 7 A 2 11 ALL TAB COMMEN TS conocia iaa deis A 8 A 2 12 ALESUSERS sire ove ENA OAZA dine iar Sin Ae A 9 A 2 13 ALLVIEW S A a o ici A 9 A 2 14 COLUMN PRIVILEGES Gees aa OO CAE A AE A ee A 9 A 2 15 DICTIONARY zeta o Boo OWE ot in k Stab kih ubrati A 10 A 2 16 BLO WERONA A 10 A 2 17 T BEE PRIVILEGES a5 Gozo EA tra ic AA ee ee A 10 A 2 18 USER CATALOG zna a M cece tes dy edi Se dani R Pe BRONIE A 10 A 2 19 USER COL COMMENTS 0000004 tE ee A 10 A 2 20 USER CONSTRATNTS 0 AE das NA DRE ee A 11 A 2 21 USER CONS COLUMNS iii eiii A 11 A 2 22 USER IN
130. able and if you would be examining it within the same transaction C 4 2 DRDA_CAPABILITY Default value None Range of values Refer to Native Semantics on page 13 18 Syntax DRDA_CAPABILITY FUNCTION ON OFF DRDA_CAPABILITY specifies which mapped functions of Oracle Database will be treated natively In other words no special pre processing or post processing will be done for these functions They will be passed through to the DRDA Server unmodified C 4 3 DRDA_CODEPAGE_MAP Default value codepage map Range of values Any valid file path Syntax DRDA_CODEPAGE_MAP codepage map DRDA_CODEPAGE_MAP specifies the location of the codepage map You may specify only the filename which will be searched for within the ORACLE_HOME tg4drda admin directory or you may specify the full path name of the file C 4 4 DRDA_COMM_BUFLEN Default value 32767 Range of values 512 through 32767 Syntax DRDA_COMM_BUFLEN num DRDA_COMM_BUFLEN specifies the communications buffer length This is a number indicating the size of the SNA send or receive buffer in bytes C 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Initialization File Parameters C 4 5 DRDA_CONNECT_PARM SNA format Default value DRDACON1 Range of values Any alphanumeric string 1 to 8 characters in length Syntax RDA_CONNECT_PARM name DRDA_CONN
131. acle Database 10g Because the gateway does not have background processes and does not need a management utility such as Oracle Enterprise Manager you do not need to start the gateway product Each Oracle Database 10g user session that accesses a particular gateway creates an independent process on the host This process runs the gateway session and executes SNA or TCP IP functions to communicate with a DRDA Server 1 7 How the Gateway Works The gateway has no database functions of its own Instead it provides an interface by which an Oracle Database 10g can direct part or all of a SOL operation to a DRDA database The gateway that is supporting the DRDA Server is identified to the Oracle integrating server using a database link The database link is the same construct that is used to identify other Oracle Database 10g databases Tables on the DRDA Server are referenced in SOL as table nameadblink name OT owner table_name dblink_name If you create synonyms or views in the Oracle integrating server database then you can refer to tables on the DRDA Server by using simple names as though the table were local to the Oracle integrating server When the Oracle integrating server encounters a reference to a table that is on the DRDA Server the applicable portion of the SQL statement is sent to the gateway for processing Any host variables that are associated with the SQL statement are bound to the gateway and therefore to the DRDA Se
132. actually sent to the gateway and thus sent to the DRDA Server However certain SQL statement form have post processing performed on them in the gateway Error Messages Diagnosis and Reporting 16 5 SQL Tracing and the Gateway 16 4 2 SQL Tracing in the Gateway The production gateway does not have built in tracing built into it for the purpose of enhancing its speed The product ships with a debug library that can be used to build a debug gateway for the purposes of tracing and debugging applications First login as the Admin user ID of the gateway and setup the environment su lt gateway Admin User gt Next build the debug gateway cd SORACLE_HOME tg4drda lib make f tg4drda mk ORACLE_HOME your_oracle_home g4drsrvd Note ORACLE_HOME is the location of your gateway installation That is to say your_oracle_home is the ORACLE HOME of the gateway as set in Step 3 Set the ORACLE HOME environment variable on page 4 3 in Chapter 4 Installing the Gateway This will create the debug gateway and store itin ORACLE HOME bin g4drsrvd Next change the listener ora to invoke the debug gateway Using our example from Appendix B Sample Files Change the PROGRAM parameter to specify the debug program name SID DESC lt SID NAME drdahoal ORACLE_HOME oracle tg4drda 10 2 0 PROGRAM g4drsrvd The listener will need to be reloaded for this change to take effect Next edit th
133. al node ID and optionally remote node ID Then specify the Contact Information Figure 6 7 Link Station Dialog Box Contact information contains the MAC address of the remote host as well as the SAP number Click Advanced for additional parameters of the Link Station Configuring SNAP IX Interfaces 6 7 Creating SNA Definitions for the Gateway The Token Ring Parameters dialog box shows additional parameters of the Link Station see Figure 6 8 These parameters effect initial XID contact and retransmission times and limits The defaults are normally sufficient Click OK Figure 6 8 Token Ring Parameters Dialog Box Create Local LUs After the remote node definitions have been made create the Local LU names for the local host From the Services menu select APPC and New Local LU In the dialog box see Figure 6 9 enter the name of the local LU and an alias This name must correspond to the VTAM definitions on the remote DRDA Server host for the UNIX host Click OK Figure 6 9 Local LU Dialog Box 6 8 Oracle Transparent Gateway for DRDA Installation and User s Guide Creating SNA Definitions for the Gateway Create Partner LUs Now define a Partner LU which represents the LU that the DRDA Server is using to communicate From the Services menu select APPC and New Partner LUs and Partner LU on Remote Node In the dialog box see Figure 6 10 Enter the Partner LU name and characteristics The Partner LU n
134. alling the Gateway 4 3 Installation Complete Step 6 Start the Oracle Universal Installer The Oracle Universal Installer is provided on the distribution CD ROM with the gateway If you are installing over an older gateway instance then you must upgrade the Oracle Universal Installer to this version by selecting the new Oracle Universal Installer from the Available Products menu For general information about installing Oracle products and how to use the Oracle Universal Installer refer to the Oracle Database Installation Guide 10g for UNIX Systems Start the Installer with the following command runInstaller Step 7 Step through the Oracle Universal Installer Oracle Universal Installer is a menu driven utility that guides you through installing the gateway by prompting you with action items The action items and the sequence in which they appear depend on your platform Use the following list as a guide to the installation The prompts that Oracle Universal Installer offers are listed in bold face font Respond to the prompts by implementing the responses that follow the prompts Prompt Welcome Response Click Next Prompt Specify Home Details Response Check that the Destination Path points to your ORACLE_HOME Prompt Installation Types Response Select Custom Click Next Prompt Available Products Components Response Open the Oracle Transparent gateways product group and select Ora
135. ame will contain the SNA Network Name as well as the LU name of the remote LU Enable parallel session support The location is the name as the remote node name You may click Location for a list Then click OK Figure 6 10 Partner LU Dialog Box Create Mode and CPI C Profiles After the local and remote LU definitions have been made create the necessary Mode and CPI C definitions From the Services menu select APPC and Modes In the Modes dialog box see Figure 6 11 click New to add a new mode Figure 6 11 Modes Dialog Box Configuring SNAP IX Interfaces 6 9 Creating SNA Definitions for the Gateway In the Mode dialog box see Figure 6 12 enter the mode name and other session parameters The prescribed name for a DRDA mode is IBMRDB Contact your remote host system administrator for appropriate mode parameters Click OK Figure 6 12 IBMRDB Mode Dialog Box Now that the mode has been defined create the CPI C Side Information Profile which the gateway will use as a connection name From the menu select APPC and CPI C In the CPI C destination names dialog box see Figure 6 13 click New to add a new profile Figure 6 13 CPI C destination Names Dialog Box In the CPI C destination dialog box see Fi gt 6 14 enter the profile name local LU name partner TP partner LU and mode and security option The default TP name of the mode DRDA Server will typically be a service TP named 07F6C4C2 For the loca
136. arameters for a description of the following parameters a DRDA CONNECT PARM u DRDA_PACKAGE_COLLID a DRDA_PACKAGE NAME u DRDA PACKAGE OWNER u DRDA REMOTE DB NAME a HS DB NAME su HS DB DOMAIN Configuring the Gateway 11 3 Configuring the Host u FDS_CLASS 11 4 1 Binding the DRDA Gateway Package The product requires a package to be bound on the DRDA Server The gateway has an internal stored procedure that must be used to create this package The internal stored procedure is invoked from an Oracle integrating server Refer to Configuring Oracle Net on page 10 3 Also refer to Configuring the Oracle Integrating Server in this chapter on page 11 7 Before this package can be bound on the DRDA Server the Gateway Initialization File must be correctly configured refer to Appendix C DRDA Specific Parameters 1 Log on to an Oracle integrating server Use either SQL Plus or Server Manager sqlplus system manager 2 Create a Database link Create a Database link with a user ID and with a password that has proper authority on the DRDA Server to create packages SQL gt CREATE PUBLIC DATABASE LINK dblink 2 CONNECT TO userid IDENTIFIED BY password 3 USING tns name entry Note The user ID that is creating the public database link must have the CREATE PUBLIC DATABASE LINK privilege Refer to Configuring the Oracle Integrating Server on page 11 7 for more information 3 Execute the s
137. as follows m Creating Database Links u Dropping Database Links u Examining Available Database Links u Limiting the Number of Active Database Links Using the Oracle Transparent Gateway for DRDA 12 1 Processing a Database Link 12 1 1 Creating Database Links To create a database link and define a path to a remote database use the CREATE DATABASE LINK statement The CONNECT TO clause specifies the remote user ID and password to use when creating a session in the remote database The USING clause points to a tnsnames ora connect descriptor Note If you do not specify a user ID and a password in the CONNECT TO clause then the Oracle Database user ID and password are used See Also Chapter 14 Security Considerations for more information The following example creates a database link to access information in the DRDA Server database CREATE PUBLIC DATABASE LINK dblink CONNECT TO userid IDENTIFIED BY password USING tns name entry where dblink is the complete database link name user id is the user ID used to establish a session in the remote database This user ID must be a valid DRDA Server user ID It must be authorized to any table or file on the DRDA Server that is referenced in the SOL commands The user ID must be lesser than eight characters password is the password used to establish a session in the remote database This password must be a valid DRDA Server password The pass
138. as those in our examples given knowledge of the IBM CCSIDs and the Oracle Database Character Sets Because this can be complex and quite confusing given the IBM documentation of codepage definitions and Oracle Database Character Set definitions please thoroughly test your definitions for all desired character data values before putting them into production If you are uncertain then contact Oracle Support Services to request proper codepage mapping entries D 6 Message Availability Whether a language message module is available depends on which modules are installed in the Oracle product set that is running on the server If message modules for a particular language set are not installed then specifying that language with a language parameter does not display messages in the requested language D 10 Oracle Transparent Gateway for DRDA Installation and User s Guide Example of NLS Configuration D 7 Example of NLS Configuration Following is an example of all the settings that are needed to configure the gateway DRDA Server Oracle Database and client so that a language and character set are working compatibly across the system In this example the settings enable a customer in Germany to interact with the gateway in German gateway initsid ora file HS LANGUAGE AMERICAN AMERICA WE8ISO8859P1 HS NLS DATE FORMAT YYYY MM DD DRDA Server CCSID 273 D8EBCDIC273 Oracle Database server and Client Setting for Database SELE
139. at it be set C 4 39 ORACLE_DRDA_TCTL Default value None Range of values Any valid file path Syntax ORACLE_DRDA_TCTL tracecontrolpath ORACLE_DRDA_TCTL specifies the path to the DRDA internal trace control file This file contains module tracing commands A sample file is stored in ORACLE_HOME tg4drda admin debug tctl This parameter is used for diagnostic purposes C 4 40 ORACLE_DRDA_TRACE Default value value specified for LOG_DESTINATION Range of values any valid file path Syntax ORACLE_DRDA_TRACE logpath ORACLE_DRDA_TRACE is used to specify a different log path for DRDA internal tracing This tracing is separate from the rest of the gateway tracing as specified by the LOG_DESTINATION parameter By default this parameter will append the DRDA internal trace to the gateway trace This parameter is used for diagnostic purposes C 4 41 TRACE_LEVEL Default Value 0 Range of values 0 255 Syntax TRACE_LEVEL number DRDA Specific Parameters C 11 Gateway Initialization File Parameters TRACE_LEVEL specifies a code tracing level This value determines the level of detail which is logged to the gateway logfile during execution This parameter is primarily used for diagnostics C 12 Oracle Transparent Gateway for DRDA Installation and User s Guide D National Language Support This appendix discusses the National Language Support NLS
140. ate 7 byte binary format The gateway recognizes such values as dates 13 7 4 3 Performing Date Arithmetic The following forms of SQL expression generally do not work correctly with the gateway date number number date date number datel date2 The date and number addition and subtraction date number number date date number forms are sent through to the DRDA Server where they are rejected The supported servers do not permit number addition or subtraction with dates Because of differing interpretations of date subtraction in the supported servers subtracting two dates datel date2 gives results that vary by server Note Avoid date arithmetic expressions in all gateway SQL until date arithmetic problems are resolved Date handling has two categories u Two digit year dates which are treated as occurring 50 years before or 50 years after the year 2000 u Four digit year dates which are not ambiguous with regard to the year 2000 Oracle recommends that you set the Oracle Database 10g server and gateway default HS_NLS_DATE_FORMAT parameter to a format including a four digit year Use one of the following methods to enter twenty first century dates m The TO DATE function Developing Applications 13 23 DRDA Data type to Oracle Data type Conversion Use any date format including a four character year field Refer to the Oracle Database SQL Reference for the available date format st
141. ate CDB tables The DB2 DDF component must be stopped and restarted for CDB changes to take effect Security Considerations 14 3 Processing Inbound Connections The DB2 non DRDA specific security features are also involved in DRDA connections User IDs are subject to normal DB2 or SAF RACF validation in addition to connection or sign on exit processing Passwords are also subject to validation After the connection is established all normal authorizations or GRANTs associated with the user ID are in effect The user ID must have execute privilege on the gateway DRDA package to process any SQL statements 14 5 1 2 DB2 VM Under a Virtual Machine VM DRDA sessions are managed by APPC VTAM Support AVS which runs as a disconnected GCS virtual machine AVS receives incoming APPC connection requests both DRDA and non DRDA and routes the connection to an appropriate server virtual machine AVS user ID mapping is controlled by internal AVS data structures that are updated with the AGW ADD USERID and AGW DELETE USERID commands A user ID mapping entry converts the inbound user ID before making the DB2 VM connection The user ID mapping consists of u Originating LU name u Inbound user ID m The new user ID You can create default entries that apply to any LU name and to any inbound user ID and an entry can indicate that the inbound user ID is to be used without mapping AVS user ID mapping is functionally s
142. ation of the Oracle Open gateways Release 10g which will deliver enhanced integration capabilities by exploiting Oracle Database 10g Heterogeneous Services Heterogeneous Services is a component of Oracle Database 10g Oracle Database 10g provides the common architecture for future generations of the gateways For detailed information on Oracle Heterogeneous Services refer to Oracle Database Heterogeneous Connectivity Administrator s Guide The version 10 gateways are even more tightly integrated with Oracle Database 10 than previous versions enabling improved performance and enhanced functionality while still providing transparent integration of Oracle and non Oracle data For example connection initialization information is available in the local Oracle Database 10g server reducing the number of round trips and the amount of data sent over the network SQL execution is also faster because statements issued by an application are parsed and translated once and can then be reused by multiple applications Version 10 gateways leverage any enhancements in Oracle Database 10g and you can quickly extend those benefits to your non Oracle data Advantages of Oracle Transparent Gateway for DRDA Oracle Transparent Gateway for DRDA enables Oracle applications to access the DRDA Application Servers such as DB2 for MVS through SQL The gateway and Oracle Database 10g together create the appearance that all data resides on a local Oracle Database 10g
143. ative SOL The 10 2 release of Oracle Transparent Gateway for DRDA enables retrieval of result sets from gueries issued with passthrough The syntax is different from the DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIATE function Refer to Retrieving Results Sets Through Passthrough on page 13 27 for more information 13 8 1 Using DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIATE To run a passthrough SQL statement using DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIATE use the following syntax number of rows DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIATE dblink native DRDA sgl where number of rows isa variable that is assigned the number of rows affected by the passthrough SOL completion For DDL statements a zero is returned for the number of rows affected dblink is the name of the database link used to access the gateway native DRDA sgl isa valid nonguery SOL statement except CONNECT COMMIT and ROLLBACK The statement cannot contain bind variables Native SOL statements that cannot be dynamically prepared are rejected by the DRDA Server The SOL statement passed by the DBMS HS PASSTHROUGH EXECUTE IMMEDIATE function must be a character string For more information regarding valid SOL statements refer to the SOL Reference for the particular DRDA Server 13 8 1 1 Examples 1 Inserta row into a DB2 table using DBMS HS PASSTHROUGH EXECUTE IMMEDIATE
144. ave appropriate documentation for your platform for your operating system and DRDA Server DB2 05390 DB2 400 DB2 Universal Database or DB2 server for VM The IBM publications regarding a distributed relational database might also be useful 3 4 Oracle Transparent Gateway for DRDA Installation and User s Guide 4 Installing the Gateway This chapter provides general information about gateway installation that is specific to this release of the Oracle Transparent Gateway for DRDA It contains the following sections a Introduction u Before You Begin m Checklist for Gateway Installation u Installation Overview a Installing the Gateway from CD ROM u Installation Complete 4 1 Introduction The complete Oracle Transparent Gateway for DRDA installation process is divided into installation and configuration tasks This process is described in Chapters 4 through 12 If this is the first time that the gateway has been installed on your host then you must perform all of the steps that are documented in these chapters The installation tasks include u Ensuring that your hardware and software requirements are met u Loading and installing the gateway software from the distribution medium into your system u Determining your gateway system identifier u Reconfiguring your network Yu can use the checklist in Checklist for Gateway Installation to check each completed step in the process 4 2 Before You Begin This chapte
145. base This enables the DRDA Server to pass the function to the underlying database implementation for example DB2 Native Semantics provides a method of enabling specific capabilities to be processed natively by the DRDA Server Various considerations must be taken into account when enabling the Native Semantic feature of a particular function because Native Semantics has advantages and disadvantages which are typically a trade off between transparency and performance One such consideration is the transparency of data coercions Oracle Database provides coercion implicit data conversion for many SQL functions This means that if the supplied value for a particular function is not correct then Oracle Database will coerce the value change it to the correct value type before processing it However with the Native Semantic feature enabled the value exactly as provided will be passed to the DRDA Server for processing In many cases the DRDA Server will not be able to coerce the value to the correct type and will generate an error Another consideration involves the compatibility of parameters to a particular SQL function For instance Oracle Database implementation of SUBSTR allows negative values for the string index whereas most DRDA Server implementations of SUBSTR do not allow negative values for the string index However if the application is implemented to invoke SUBSTR in a manner that is compatible with the DRDA Server then the fun
146. bject TEMPORARY Whether the object is temporary GENERATED Whether the name of this object system is generated SECONDARY N A A 2 8 ALL_SYNONYMS All synonyms accessible to the user column name description OWNER Owner of the synonym SYNONYM_NAME Name of the synonym TABLE_OWNER Owner of the object referenced by the synonym TABLE_NAME Name of the object referenced by the synonym DB_LINK N A A 2 9 ALL_TABLES Description of tables accessible to the user column name description OWNER Owner of the table TABLE_NAME Name of the table TABLES PACE_NAME Name of the tablespace containing the table CLUSTER_NAME N A IOT_NAME Name of the index organized table PCT_FREE N A PCT_USED N A INI_TRANS N A MAX_TRANS N A INITIAL_EXTENT N A NEXT_EXTENT N A MIN_EXTENTS N A MAX EXTENTS N A PCT_INCREASE N A FREELISTS Number of process freelists allocated to this segment FREELIST_GROUPS Number of freelist groups allocated to this segment LOGGING Logging attribute BACKED_UP N A NUM_ROWS Number of rows in the table A 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dictionary View Tables column name description BLOCKS N
147. buffer from the gateway to the Oracle Database 10g The buffer may contain one or more qualified rows from the DRDA Server This feature can provide significant performance enhancements depending on your application design installation type and workload The array size between the client and the Oracle Database 10g is determined by the Oracle application Refer to Chapter 11 Configuring the Gateway for more information 13 2 Using Oracle Stored Procedures with the Gateway The gateway stored procedure support is an extension of Oracle stored procedures An Oracle stored procedure is a schema object that logically groups together a set of SQL and other PL SQL programming language statements to perform a specific task Oracle stored procedures are stored in the database for continued use Applications use standard Oracle PL SQL to call stored procedures Oracle stored procedures can be located in a local instance of Oracle Database and in a remote instance Figure 13 1 illustrates two stored procedures oraprocl isa procedure stored in the ORA1 Oracle instance and oraproc2 is a procedure stored in the ORA2 Oracle instance 13 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Using DRDA Server Stored Procedures with the Gateway Figure 13 1 Calling Oracle Stored Procedures in a Distributed Oracle Environment oraproc1 Oracle Stored Procedure DECLARE Oracle Application Oracle Server BEGIN
148. by Oracle Database and the gateway These values may change from release to release depending on whether the gateway capabilities change The valid default values for FDS_CLASS are as follows For a DB2 OS390 database TG4DRDA_DB2MVS For a DB2 VM database TG4DRDA_DB2VM For a DB2 400 database TG4DRDA_DB2400 For a DB2 UDB database TG4DRDA_DB2UDB C 4 31 FDS CLASS VERSION Default value 10 1 0 2 0 Range of values 10 1 0 2 0 Syntax FDS_CLASS_VERSION 1 FDS CLASS VERSION specifies the version of the FDS_CLASS capabilities Do not specify this parameter unless directed to do so by Oracle Support Services C 4 32 FDS_INSTANCE Default value DRD1 Range of values the name of the gateway SID Syntax FDS_INSTANCE drdahoa1 DRDA Specific Parameters C 9 Gateway Initialization File Parameters FDS_INSTANCE specifies a subset of the FDS_CLASS capabilities that may be modified by the user based on initialization file parameters If you do not specify this parameter then its value will be the Oracle SID that is defined in the TNS Listener entry C 4 33 HS FDS FETCH ROWS Default value 20 Range of values Any integer between 1 and 1000 Syntax HS_FDS_FETCH_ROWS num HS_FDS_FETCH_ROWS specifies the fetch array size This is the number of rows to be fetched from the DRDA Server and to return to Oracle Database at one time This parameter will be affected
149. by the HS_RPC_FETCH_SIZE and HS_RPC_FETCH_REBLOCKING parameters For further information on these parameters refer to the section Controlling the Array Fetch Between Agent and Non Oracle Database in the Oracle Database Heterogeneous Connectivity Administrator s Guide C 4 34 HS LANGUAGE Default value none Range of values any valid language specification Syntax HS_LANGUAGE language _territory character_set HS_LANGUAGE specifies the language and the character set that the gateway will use to interact with the DRDA Server Care must be taken in choosing the value of these parameters especially when the gateway will be accessing GRAPHIC data For additional details refer to Appendix D and to the Oracle Database Heterogeneous Connectivity Administrator s Guide C 4 35 HS_NLS_NCHAR Default value None Range of values Any valid character set specification Syntax HS_NLS_NCHAR character_set Hs_nls_nchar specifies the character set that the gateway will use to interact with the DRDA Server when accessing Graphic data Set this parameter to the same value as the character set component of the HS_LANGUAGE parameter For additional details refer to Appendix D and to the Oracle Database Heterogeneous Connectivity Administrator s Guide C 4 36 LOG_DESTINATION Default value SORACLE_HOME tg4drda log gateway sid_pid log Range of values Any valid file path Syntax LOG_DESTINATI
150. ca AAAA AAAA C 4 DRDA DISAB BeiGA Dl a dada ends ida C 4 DRDASFEUSH CA CHE Sci a W WA AAAA C 4 DRDA GRAPHIC CHAR SIZE cata idsa C 4 DRDA GRAPHIC PAD SIZE cenital a da AL AWZ ACO C 4 PRDA lt GRAPHIE ITTEEHECK ta oi EU AJ Maki C 5 DRDA GRAPHIC TO MBGS seen kk sia C 5 DRDA ISOLATION REVELL esa ai EN ie vnik C 5 PRDA LOCAL NODEVNAME rea waw A O YE C 6 DRDA MBCS TO GRAPHIC aaa C 6 DRDA OPTIMIZE QUERY i ze EME je Bh No le as C 6 DRDA PACKAGE COLLID aaa C 6 DRDA PACKAGE CONSTOKEN aaa C 7 PDRDA PAGKAGE NAME iii a bea C 7 DRDA PACKAGE OWNER aaa C 7 DRDA PACKAGE SECTIONS s siv ie iin SD dic C 8 PRDAREAD ONEN nn ap ei NE Rea eki oh Own C 8 DRDA RECOVERY PASSWORD oia Bina A A A Ne rns C 8 DRDA RECOVERY USERID aaa C 8 DRDA REMOTE DB NAME aaa C 9 DRP SECURITY TYPE tpe aiii C 9 FDS ERA SS vasi iin iki EN ciation a OO OWA ee eee eee GR lean i n C 9 C 4 31 EDS CLASS VERSION ii iN Re RA NI OE C 9 C 4 32 FDS INSTANCE tido did AA OOOO A AAA E C 9 C 4 33 H EDS FETEH ROW Sheane eie adi ado no oo ONE AE C 10 C 4 34 HS LANGUAGE cuca a RZA C 10 C 4 35 HS NES NE HA Ri sunek n ih ara nia ollas idad C 10 C 4 36 LOG DESTINATIO N esses ica re O O W OE C 10 C 4 37 ORA MAX DATE Genil a OOO TARA AE C 11 C 4 38 ORA NES O Za a i ON a dE O OT C 11 C 4 39 ORACLE DRDA TCT E add o odd O O AE C 11 C 4 40 ORACLE DRDALTRA CE is ze e AAA AA W tec C 11 C 4 41 TRACE LEVEL zzo go R AREA RA ROG AA ROWE
151. ccessible columns in constraint definitions column name description OWNER Owner of the constraint definition CONSTRAINT NAME Name of the constraint definition A 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dictionary View Tables column name description TABLE_NAME Name of the table with a constraint definition COLUMN_NAME Name of the column specified in the constraint definition POSITION Original position of column in definition A 2 4 ALL_CONSTRAINTS Constraint definitions on accessible tables column name description OWNER Owner of the constraint definition CONSTRAINT_NAME Name of the constraint definition CONSTRAINT_TYPE Type of the constraint definition TABLE_NAME Name of the table with constraint definition SEARCH_CONDITION Text of the search condition for table check R_OWNER Owner of the table used in referential constraint R_CONSTRAINT_NAME Name of the unique constraint definition for referenced table DELETE_RULE Delete rule for a referential constraint STATUS Status of a constraint DEFERRABLE Whether the constraint is deferrable DEFERRED Whether the constraint was initially deferred VALIDATED Whether all data obeys the constraint GENERATED Whether the name of the constraint is user or system generated BAD Constraint specifies a century in an ambiguous manner REL
152. ce The DRDA_CONNECT_PARM must be configured correctly for the chosen Networking Interface The rest of the DRDA specific parameters are unrelated to the communications protocol and may be set the same for either SNA or TCP IP installations as illustrated Example 1 Configuration for a DRDA Server on a host named mvs01 domain com or IP address of 192 168 1 2 with a Service Port number of 446 DRDA_CONNECT_PARM mvs01 domain com 446 or DRDA_CONNECT_PARM 192 168 1 2 446 Example 2 Configuration for a DRDA Server on the same host as the gateway with a Service Port number of 446 DRDA_CONNECT_PARM localhost 446 or DRDA_CONNECT_PARM 127 0 0 1 446 For additional information about configuring TCP IP for a particular host operating system refer to the appropriate platform and operating system installation and configuration guides 9 2 Oracle Transparent Gateway for DRDA Installation and User s Guide 10 Oracle Net Oracle Net is an Oracle product providing network communication between Oracle applications Oracle Database and Oracle Gateways across different systems This chapter contains the following sections a Checklists for Oracle Net m Oracle Net Introduction ua Oracle Net Overview u Configuring Oracle Net Advanced Security Encryption m Setting Up Advanced Security Encryption for Test Testing Advanced Security Encryptions 10 1 Checklists for Oracle Net This section provides
153. checklists to be used when installing and configuring Oracle Net 10 1 1 Configuring Oracle Net The steps to conigure Oracle Net are m Step 1 Modify listener ora file m Step 2 Modify tnsnames ora file 10 1 2 Advanced Security Encryption Verifying if CHECKSUM and the Export encryption algorithms are used at your site To set up advanced security encryption are 10 1 2 1 Setting Up Advanced Security Encryption for Test Step 1 Set Advanced Security Encryption Parameters for the Gateway m Step 2 Set Advanced Security Encryption Parameters for Oracle Server 10 1 2 2 Testing Advanced Security Encryptions a Step 1 Connect Gateway and Oracle Integrating Server ua Step 2 Reset Configuration Parameters on the Gateway Oracle Net 10 1 Oracle Net Introduction 10 2 Oracle Net Introduction Oracle Net provides connectivity to the gateway through the use of Protocol Adapters SQL Net and the TNS Listener Configuration of Oracle Net is backward compatible with past versions of SQL Net A new facility called Heterogeneous Services HS has been added to both Oracle Net and the gateway to improve the throughput of data For additional information refer to Oracle Net Services Administrator s Guide Oracle Net Services Reference Guide and Oracle Database Heterogeneous Connectivity Administrator s Guide 10 3 Oracle Net Overview Oracle Net is a required Oracle product supporting network communications between Oracle applications
154. cksize and the block fetch between the Oracle integrating server and the gateway are controlled by two Heterogeneous Services initialization parameters HS_RPC_FETCH_SIZE and HS_RPC_FETCH_REBLOCKING These parameters are specified in the Gateway Initialization File Refer to Oracle Database Heterogeneous Connectivity Administrator s Guide for more information Oracle Database 10g Passthrough Supported You can use the Oracle Database 10g DBMS_HS_PASSTHROUGH EXECUTE_IMMEDIATE method to pass commands or statements available in your DRDA database through the gateway Retrieving Result Sets Through Passthrough Oracle Transparent gateway for DRDA provides a facility to retrieve result sets from a select SQL statement issued with passthrough Refer to Retrieving Results Sets Through Passthrough on page 13 27 for additional information Introduction 1 11 Features Support for TCP IP This release of the gateway supports the TCP IP communication protocol between the gateway and the DRDA Server Refer to Chapter 9 Configuring TCP IP for further information Native Semantics This release of the gateway supports the ability to selectively enable or disable post processing of various SQL functions by the DRDA Server Refer to Native Semantics on page 13 18 for further information Columns Supported in a Result Set Oracle Transparent gateway for DRDA supports up to 1000 columns in a
155. cle Transparent Gateway for DRDA Open the Oracle Transparent gateway for DRDA product group if not already open and select one protocol from the list of supported protocols Remove selection from everything else for a standalone gateway installation Click Next Prompt DRDA Network Interface Product Software Response If the SNA protocol was selected choose the network interface software appropriate for this installation of the gateway Click Next If the SNA protocol was not selected this panel does not appear Prompt Summary Response Verify the products to be installed Click Next Step 8 Verify installation success After the Oracle Universal Installer confirms that the installation has ended verify that the installation was successful To do this check the contents of the installation log file located in the Oracle inventorys log directory The default file name is installActions lt DATE gt log Ignore the instruction to run the root sh script if applicable 4 7 Installation Complete Your gateway installation is now complete Proceed with the configuration tasks described in Chapters 5 through 8 4 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Removing the Gateway 4 8 Removing the Gateway Removing the Oracle Transparent Gateway for DRDA requires the use of the Oracle Universal Installer To remove the gateway do the following 1 To restart the Oracle Universal I
156. cribe a basic method of verifying this feature if it is used at your site The easiest way to determine if Advanced Security encryption is attempting to work is to deliberately set wrong configuration parameters and attempt a connection between the server and client Incorrect parameters cause the connection to fail After receiving the expected failure message set the configuration parameters to the correct settings and try the connection again Encryption is working properly if you receive no further error messages 10 6 Setting Up Advanced Security Encryption for Test The following procedures test Advance Security encryption by the above method The incorrect parameter settings produce error 12660 1 Step 1 Set Advanced Security Encryption Parameters for the Gateway 2 Step 2 Set Advanced Security Encryption Parameters for Oracle Server Note The international or export version of Advanced Security encryption supports the following encryption types m des40 u rc4_40 Step 1 Set Advanced Security Encryption Parameters for the Gateway Edit the Oracle Net configuration file on the host system gateway system to add the following parameters and values SOLNET CRYPTO CHECKSUM SERVER REJECTED SOLNET ENCRYPTION SERVER lt REJECTED SOLNET CRYPTO CHECKSUM TYPES SERVER SHA1 SOLNET ENCRYPTION TYPES SERVER DES40 RC4 40 SOLNET CRYPTO SEED abcdefg123456789 The value shown for SOLNET CRYPTO SEED is o
157. ction will behave the same in either Oracle Database or the DRDA Server 13 18 Oracle Transparent Gateway for DRDA Installation and User s Guide Native Semantics Another consideration is that the processing of a function at the DRDA Server may not be desirable due to resource constraints in that environment Refer to the DRDA_CAPABILITY parameter on page C 2 for details on enabling or disabling these capabilities Refer to the Oracle Database SQL Reference for Oracle Database format of the following capabilities 13 6 1 SQL Functions That Can Be Enabled The following list contains SQL functions that are disabled OFF by default They can be enabled turned ON as an option Table 13 5 List of SQL Functions That Can Be Enabled Function Name Function Name Function Name Function Name ABS ACOS ASCII ASIN ATAN ATAN2 BITAND CAST CEIL CHR CONVERT cos COSH COUNTCOL DECODE DUMP EXP FLOOR GREATEST HEXOTRAW INITCAP INSTR INSTRB EAST LENGTH ENGTHB LN LOG OWER LPAD LTRIM MOD NLS_INITCAP NLS_UPPER NLS_LOWER NLSSORT NVL2 POWER RAWTOHEX REPLACE REVERSE ROUND RPAD RTRIM SIGN SIN SINH SORT STDDEV SUBSTR SUBSTRB TAN TANH TO_NUMBER TRANSLATE TRIM TRUNC UPPER VARIANCE VSIZE 13 6 2 SQL Functions That Can Be Disabled The following SQL functions are enabled ON by default
158. ctions The gateway can participate as a partner in multi site transactions and two phase commit How this occurs depends on the capabilities of the underlying data source meaning that the gateway can be implemented as any one of the following u Full two phase commit partner u Commit point site m Single site update partner u Read only partner The deciding factors for the implementation of the gateway are the locking and transaction handling capabilities of your target database 1 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Architecture Oracle Transparent Gateway for DRDA by default is configured as a commit point site that is commit confirm protocol Optionally you can configure the gateway as read only if you choose to enforce read only capability through the gateway Other protocols are not supported Refer to Read Only Gateway on page 12 5 in Chapter 12 Using the Oracle Transparent Gateway for DRDA 1 3 14 Site Autonomy All Oracle Database products including gateways supply site autonomy For example administration of a data source remains the responsibility of the original system administrator Site autonomy also functions such that gateway products do not override the security measures established by the data source or operating environment 1 3 15 Migration and Coexistence The integration of a data source through the gateway does not require any changes to be made to applications at
159. ctions are those SQL functions that are not recognized by the DRDA Server If a SELECT statement containing one of these functions is passed from the Oracle Integrating Server to the gateway then the gateway removes the function before passing the SQL statement to the DRDA Server The gateway passes the selected DRDA database rows to Oracle Integrating Server Oracle Integrating Server applies the function 13 5 3 1 Post Processing Oracle Database can compensate for a missing or incompatible function by automatically excluding the incompatible SQL construct from the SQL request that is forwarded to the DRDA database Oracle Database then retrieves the necessary data from the DRDA database and applies the function This process is known as post processing The gateway attempts to pass all SOL functions to DRDA databases However when a DRDA database does not support a function that is represented in the computation the gateway changes that function For example if a program runs the following query against a DB2 05390 database SELECT COS X_COOR FROM TABLE_X 13 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Oracle Database SQL Construct Processing Beacuse the database does not support many of the COS functions the gateway changes the query to the following SELECT X_COOR FROM TABLE_X All data in the X_COOR column of TABLE_X is passed from the DB2 05390 database to the Oracle integrating server
160. de ID System Identification Lara Node Name and Remote Node TD Creating a Local LU Definition LU Alias Configuration Worksheet E 1 Table E 1 Cont List of Parameters Needed to Configure the Gateway Reason Name of Parameter Needed Your Specific Parameters Here Creating a Local LU Definition LU Name General APPC Mode Definition Mode Name APPC Mode Limits Parallel Session Limit APPC Mode Limits Minimum Contention Winner Limit APPC Mode Limits Partner Min Contention Winner Limit APPC Mode Limits Automatic Activation Limit APPC Mode Characteristics Pacing Send Count APPC Mode araci noes Pacing Receive Count APPC Mode Characteristics Max Send RU Size Definition General Properties Appropriate Connection name Remote LU Definition General Properties LU ALias Remote LU Definition General Properties Network Name Remote LU Definition General Properties Uninterpreted Network Name Remote LU Properties Options Any Security Options needed Remote collection ID DRDA_PACKAGE_COLLID Remote package name DRDA_PACKAGE_NAME Creating CPI C Symbolic Destination Names Side Information Profiles general information Appropriate Name for each Side Information Profile Creating CPI C Symbolic Destination Names Side Information Profiles general
161. dexed object TABLE_NAME Name of the indexed object TABLE TYPE Type of the indexed object UNIQUENESS Uniqueness status of the index COMPRESSION N A PREFIX LENGTH 0 TABLESPACE NAME Name of the tablespace containing the index INI TRANS N A MAX TRANS N A INITIAL EXTENT N A NEXT EXTENT N A MIN EXTENTS N A MAX EXTENTS N A PCT INCREASE N A PCT THRESHOLD Threshold percentage of block space allowed per index entry INCLUDE_COLUMN Column ID of the last column to be included in index organized table FREELISTS Number of process freelists allocated to a segment FREELIST_GROUPS Number of freelist groups allocated to a segment PCT_FREE N A LOGGING Logging information BLEVEL Depth of the index from its root block to its leaf blocks A depth of 1 indicates that the root and leaf block are the same JEAF BLOCKS Number of leaf blocks in the index DISTINCT_KEYS Number of distinct indexed values For indexes that enforce UNIQUE and PRIMARY KEY constraints this value is the same as the number of rows in the table AVG LEAF BLOCKS PER KEY N A AVG DATA BLOCKS PER KEY N A CLUSTERING FACTOR N A STATUS State of the indexes VALID NUM_ROWS Number of rows in the index SAMPLE_SIZE Size of the sample used to analyze the index LAST_ANALYZED Date on which the index was most recently analyzed A 12 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dicti
162. dmesg command Click OK Configuring SNAP IX Interfaces 6 5 Creating SNA Definitions for the Gateway Figure 6 4 Token ring SAP Dialog Box Create a Link Station After the Port has been defined you need to create a Link Station The Link Station represents the SNA node of the remote host of the DRDA Server But before you can create the Link Station you must create a Remote Node definition From the Services menu select APPC and Add Remote Node In the dialog box see Figure 6 5 enter the SNA CPNAME of the remote node and click OK Figure 6 5 Add Remote Node Dialog Box Now you are ready to create the Link Station From the Services menu select Connectivity and New Link Station In the dialog box see Figure 6 6 select the Port previously defined and click OK 6 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Creating SNA Definitions for the Gateway Figure 6 6 Add Link Station Dialog Box In the Link Station dialog box see Figure 6 7 enter a name for the Link Station choose the SNA Port name and choose the type of link activation Choose the LU Traffic type For maximum flexibility choose the Any option For Independent LU traffic specify the Remote Node name Click Remote node and select the node you previously created Click OK Choose the type of the Remote node typically a network node For Dependent LU traffic specify the role of the remote node typically host the loc
163. e During gateway configuration you will need to execute the Bind Package Stored Procedure to bind the gateway package on the DRDA Server To properly bind the package the user ID and password that are used when the procedure is executed either implied as the current Oracle user or explicitly defined in the CREATE DATABASE LINK command must have proper authority on the DRDA Server to create the package This user ID should be used to create and own the ORACLE2 PC two phase commit table The user ID that is used to bind or rebind the DRDA package must have one or more of the following privileges on the DRDA Server u Package privileges of BIND COPY and EXECUTE for example GRANT BIND ON PACKAGE drdal TO userid GRANT COPY ON PACKAGE drdal TO userid GRANT EXECUTE ON PACKAGE drdal TO PUBLIC u Collection privilege of CREATE IN for example GRANT CREATE IN ON PACKAGE drdal TO USER userid a System privileges of BINDADD and BINDAGENT for example GRANT BINDADD TO USER userid GRANT BINDAGENT TO USER userid u Database privilege of CREATETAB for example GRANT CREATETAB ON DATABASE database TO USER userid Choose a user ID that will own the package and the ORACLE2 PC table Ensure that this user ID is defined to both DB2 and OS 390 MVS Step 3 Define the recovery user ID During gateway configuration the recovery user ID and password are specifi
164. e Gateway Initialization File and add the following parameters TRACE_LEVEL and ORACLE_DRDA_TCTL You may optionally add the LOG_DESTINATION parameter but it is not required The following is a fragment of a Gateway Initialization File with the parameters set TRACE_LEVEL 255 ORACLE_DRDA_TCTL debug tctl The above example provides full tracing of both gateway and DRDA In many cases only the gateway tracing is desirable To obtain only gateway tracing remove or comment out the ORACLE_DRDA_TCTL parameter If you specify a LOG_DESTINATION then you may specify only the file name for example drda trc in which case the log will be written to the log directory of the gateway ORACLE HOME tg4drda log Or you may specify a fully qualified path name If you do not specify a LOG_DESTINATION then a unique log file in a default format will be generated The logfile name will be of the form gatewaysid_pid trc where 16 6 Oracle Transparent Gateway for DRDA Installation and User s Guide SQL Tracing and the Gateway gatewaysid is the SID of the gateway The value of this is determined by the setting of the FDS_INSTANCE parameter and pid is the process identifier PID of the gateway process An example log file name would be drdahoal 3875 trc When searching for the SOL statements that are passed to the DRDA Server look for the strings HGAP
165. e following information is intended for the person creating SNA definitions for the gateway You should have some knowledge of SNA before reading this section To create the SNA definitions use the following information 6 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Creating SNA Definitions for the Gateway 6 6 1 Sample SNAP IX Definitions The SORACLE_HOME tg4drda sna snapix subdirectory contains a set of sample SNAP IX definitions for the gateway created with the xsnaadmin SNA definitions are very specific to the host and SNA network As such the sample definitions provided will not work without being tailored for the local host and SNA network 6 6 2 Configuring SNAP IX This section describes the process of creating your SNA definitions for SNAP IX using xsnaadmin All of the tasks described in this section are performed from within xsnaadmin All configuration is done using the various pull down menus and panels in xsnaadmin The following configuration descriptions follow the samples provided Please tailor the various SNA values for your local host and SNA network Invoking xsnaadmin Use the following commands to invoke xsnaadmin The DISPLAY environmental variable must be set appropriately If you are running xsnaadmin from the local console then DISPLAY should already be set If you are running xsnaadmin from a remote X display then set DISPLAY to the host name or IP address of that display
166. e DB2 server 5 4 Oracle Transparent Gateway for DRDA Installation and User s Guide DB2 VM Step 2 Define the user ID that owns the package During gateway configuration you will need to execute the Bind Package Stored Procedure to bind the gateway package on the DRDA Server To properly bind the package the user ID and password used when the procedure is executed either implied as the current Oracle user or explicitly defined in the CREATE DATABASE LINK command must have proper authority on the DRDA Server to create the package This user ID should be used to create and own the ORACLE2PC two phase commit table The user ID that is used to bind or rebind the DRDA package must have one or more of the following privileges on the DRDA Server u Package privileges of BIND and EXECUTE for example GRANT BIND ON PACKAGE drdal g2drsql TO USER userid GRANT EXECUTE ON PACKAGE drdal g2drsql TO PUBLIC u Schema privileges of CREATEIN for example GRANT CREATEIN ON SCHEMA otgdb2 TO USER userid GRANT CREATEIN ON SCHEMA drdal TO USER userid m Database authorities of CONNECT UJ NDADD and CREATETAB for example GRANT CONNECT ON DATABASE TO USER userid GRANT BINDADD ON DATABASE TO USER userid GRANT CREATETAB ON DATABASE TO USER userid Choose a user ID now that will own the package and ORACLE2PC table Ensure that this user ID is defined in both the DB2 instance ID and the ope
167. e Database Error Messages Oracle Database Performance Tuning Guide Oracle Database Security Guide Oracle Database Heterogeneous Connectivity Administrator s Guide Conventions Examples of input and output for the gateway and Oracle environment are shown in a special font mkdir ORACLE your_name All output is shown as it actually appears For input refer to the following list example text Words or phrases such as mkdir and ORACLE must be entered exactly as spelled and in the letter case shown In this example mkdir must be entered in lowercase letters and ORACLE must be entered in uppercase letters italic text Italicized uppercase and lowercase such as your_name indicates that you must substitute a word or phrase such as an actual directory name BOLD text or bold italic TEXT Bold words or phrases refer to a file directory structure such as a directory path or file ID Curly braces indicate that one of the enclosed arguments is required Do not enter the curly braces themselves Brackets enclose optional clauses or arguments from which you can choose one or more Do not enter the brackets themselves Ellipses indicate that the preceding item can be repeated You can enter an arbitrary number of similar items The vertical line separates choices SQL Plus Prompts The SOL Plus prompt SQL gt appears in SQL statements and SOL Plus command examples Enter your response at the prompt Do not ente
168. e Oracle Database 109 server linknamel DESCRIPTION ADDRESS PROTOCOL 1PC KEY ORAIPC CONNECT DATA lt SID sidname HS You can use the IPC protocol only if the Oracle integrating server and the gateway reside on the same computer If you use the IPC protocol adapter then add an entry like thisto tnsnames ora where linknamel is the name used to define the database link referencing the gateway ORAIPC is the IPC key defined in the listener ora file for the IPC protocol sidname is your gateway SID the same SID that you used for the entry in your listener ora file If you are using the TCP IP protocol adapter then add the following entry to tnsnames ora linkname2 is the name used to define the database link referencing the gateway where linkname2 DESCRIPTION ADDRESS PROTOCOL TCP PORT port HOST hostname CONNECT DATA SID sidname HS Oracle Net 10 3 Advanced Security Encryption port isthe TCP IP port number on which the Oracle listener is listening default is 1541 hostname is the name of your host system sidname is your gateway SID Refer to Sample Oracle Net tnsnames ora File on page B 2 for a sample tnsnames ora file For more information about configuring Oracle Net refer to Oracle Net Services Administrator s Guide 10 5 Advanced Security Encryption Oracle Net supports the CHECKSUM command and the Export encryption algorithms The following sections des
169. e byte PC Data D 951 gt KOL6MSWIN949 Korean KS double byte PC Data M 949 KO16MSWIN949 Korean KS multi byte PC Data MBC 949 1088 951 Korean KS multi byte PC Data S 891 gt KO16KSC5601 Korean single byte S 1040 gt KO16KSC5601 Korean single byte D 926 gt KO16KSC5601 Korean double byte M 934 KO16KSC5601 Korean multi byte M 944 gt KO16KSC5601 Korean multi byte MBC 934 891 926 Korean multi byte MBC 944 1040 926 Korean multi byte Extended S 28709 gt ZHT16DBCS Traditional Chinese single byte D 835 gt ZHT16DBCS shift Traditional Chinese double byte M 937 ZHT16DBCS shift 4 Traditional Chinese multi byte MBC 937 28709 835 Traditional Chinese multi byte S 1114 gt ZHT16MSWIN950 Traditional Chinese single byte D 947 gt ZHT16MSWIN950 Traditional Chinese double byte M 950 ZHT16MSWIN950 Traditional Chinese multi byte MBC 950 1114 947 Traditional Chinese multi byte National Language Support D 7 EBCDIC EBCDIC EBCDIC EBCDIC EBCDIC EBCDIC EBCDIC EBCDIC ASCII EBCDIC ASCII ASCII EBCDIC ASCII ASCII ASCII EBCDIC EBCDIC EBCDIC ASCII ASCII ASCII EBCDIC EBCDIC ASCII ASCII EBCDIC EBCDIC EBCDIC EBCDIC EBCDIC ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII ASCII EBCDIC EBCDIC EBCDIC EBCDIC ASCII ASCII ASCII ASCII Multi Byte and Double Byte Support in the Gateway S 836 gt ZHS16DBCS Simplified Chinese sing
170. e gateway and the DRDA Server specify that parallel sessions are supported in this profile Partner LU Location Profile The Partner LU Location profile is only required when the target OLTP resides on a non APPN advanced peer to peer networking node The profile is also required if the owning node of the network connection to the target OLTP system is a non APPN node In the mainframe environment APPN support requires VTAM Version 4 Prior releases of VTAM are not APPN enabled In configurations where the Partner LU Location Profile is required the fully qualified partner owning CP name in the profile should be set to the value specified in the VTAM SSCPNAME start parameter The Partner LU Location Profile name is specified as the alias in the Partner LU profile Side Information Profile The Side Information Profile is the top of the hierarchy for APPC LU6 2 conversations The name of the Side Information Profile is specified with DRDA_CONNECT_PARM in the Gateway Initialization file Enter the following information in the Side Information Profile fields ma Local LU Name LU Name as specified in local LU profile u Fully Qualified Partner LU Name or Partner LU Alias LU Name specified in Partner LU profile or Partner LU location profile u Mode Name Mode Name specified in Mode profile u Remote Transaction Program Name Remote TPN Remote TPN in hexadecimal Yes The Remote Transaction Program Name TPN generally identifies
171. e syntax of the NLS_DATE_FORMAT parameter is HS_NLS_DATE_FORMAT date_format where date_format must be YYYY MM DD the ISO date format If this parameter is set to any other value or is omitted then you receive an error when updating deleting from selecting from or inserting into a table with date columns D 3 2 4 HS_NLS_DATE_LANGUAGE HS_NLS_DATE_LANGUAGE specifies the language used by the DRDA Server for day and month names and for date abbreviations Because ISO date format contains numbers only this parameter has no effect on gateway date processing and should be omitted National Language Support D 5 Gateway Codepage Map Facility D 4 Gateway Codepage Map Facility The gateway has a user specifiable facility to map IBM Coded Character Set Identifiers CCSIDs to Oracle Character Sets for the purpose of data translation The default map name is codepage map and is located in the ORACLE_HOME tg4drda admin directory Refer to Appendix C DRDA Specific Parameters for more detailed information about the DRDA_CODEPAGE_MAP parameter The map has two different forms of syntax The first form of syntax defines a mapping between a CCSID and an Oracle Database Character Set S D M CCSID direction Oracle_CharacterSet shift Where S designates a single byte character set D designates a double byte character set M designates a multi byte character set CCSID is the IBM coded character
172. eatures u Large Base of Data Access Application Portability u Remote Data Access u Support for Distributed Applications Application Development and End User Tools m Password Encryption Utility u Support for DB2 05390 V6 V7 and V8 Stored Procedures u Codepage Map Facility u IBM DB2 Universal Database Support a IBM DB2 Version 5 1 ASCII Tables u Read Only Support u Support for Graphic and Multi byte Data u Support for DB2 UDB on Intel Hardware u Data Dictionary Support for DB2 UDB Heterogeneous Services Architecture ThE 10 2 release of the Oracle Transparent Gateway for DRDA utilizes the Oracle Heterogeneous Services component within the Oracle Database 10g Heterogeneous Services is the building block for the next generation of Oracle Open Gateways For detailed information about heterogeneous services refer to Oracle Database Heterogeneous Connectivity Administrator s Guide Performance Enhancements Oracle Transparent Gateway for DRDA contains several internal performance enhancements This product has shown major improvements in response time and CPU utilization for all relevant address spaces for a variety of workloads compared to version 9 gateways The actual performance improvement at your site might vary depending on your installation type and workload Fetch Reblocking The array size of the application for SELECT is effective between the application and the Oracle integrating server However the array blo
173. ed in the Gateway Initialization File using the DRDA_RECOVERY_USERID and 5 2 Oracle Transparent Gateway for DRDA Installation and User s Guide DB2 400 DRDA_RECOVERY_ PASSWORD parameters If a distributed transaction fails then the recovery process connects to the remote database using the user ID and password defined in these parameters This user ID must have execute privileges on the package and must be defined in the DRDA database If the user ID is not specified in DRDA_RECOVER_USERID then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt Determine the user ID and password you will use for recovery Step 4 Determine DRDA location name for DB2 instance The DRDA location name is required as a gateway parameter To determine the location name issue the following SQL query from a DB2 SPUFI session SELECT CURRENT SERVER FROM any_table where any table isa valid table with one or more rows If the value returned by this query is blank or null then the DRDA location name has not been established Contact the system administrator to arrange to set a location name for the instance Step 5 Configure DB2 Distributed Data Facility for Gateway DB2 Distributed Data Facility DDF is the component of DB2 that manages all distributed database operations both DRDA and non DRDA If your site uses DB2 distributed operations then DDF is probably operational on
174. ee Figure 8 6 select the Port previously defined and click OK Figure 8 6 Add Link Station Dialog Box 8 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Creating SNA Definitions for the Gateway In the Link Station dialog box see Figure 8 7 enter a name for the Link Station choose the SNA Port name and choose the type of link activation Choose the LU Traffic type For maximum flexibility choose the Any option For Independent LU traffic specify the Remote Node name Click Remote Node and select the node you previously created Click OK For Dependent LU traffic specify the Local Node ID and optionally Remote Node ID Then specify the Contact Information Figure 8 7 Link Station Dialog Box Contact information contains the MAC address of the remote host as well as the SAP number Click the Advanced for additional parameters of the Link Station The Ethernet Parameters dialog box shows additional parameters of the Link Station see Figure 8 8 These parameters effect initial XID contact and retransmission times and limits The defaults are normally sufficient Click OK Configuring SNAPlus2 8 7 Creating SNA Definitions for the Gateway Figure 8 8 Ethernet Parameters Dialog Box Creating Local LUs After the Remote Node definitions have been made create the Local LU names for the local host From the Services menu select APPC and Add Local LU In the dialog box see Figure 8 9
175. egrating Gateway for DRDA Server Server CHARACTER SET ORA_NLS11 CCSID NLS_LANG NLS LANG HS_LANGUAGE HS_NLS_DATE_FORMAT HS_NLS_DATE_LANGUAGE HS_NLS_NCHAR Table D 1 describes the architecture illustrated in Figure D 1 The table discusses describes in detail the parameters and variables needed for NLS processing within each of your computer s environments the client environment the Oracle integrating server the gateway and the DRDA Server Parameters Needed for NLS Processing in Your System s Environments Table D 1 Parameters Needed for NLS Processing in Your Systems Environments Environment Parameter or Variable Description Client NLS_LANG It is environment variable NLS_LANG sets the NLS environment used by the database both for the server session and for the client application This ensures that the language environments of both the database and client application are automatically the same Because NLS_LANG is an environment variable it is read by the client applications at startup The client communicates the information defined in NLS_LANG to the server when it connects For detailed information refer to Client and Oracle Integrating Server Configuration on page D 3 Oracle CHARACTER SET This option is set during the creation of the database integrating CHARACTER SET determines the character encoding server scheme used by the database and is defined at database
176. elease of the gateway in a separate directory as discussed in Chapter 4 Installing the Gateway Caution Do not install the gateway over a previously existing gateway installation This corrupts the existing installation Step 2 Transferring initsid gtwboot Gateway Boot Initialization parameters In previous releases the gateway used two Gateway Initialization files initsid gtwboot and initsid ora or it used a Startup Shell Script drdaDB2 sh and one initialization file initsid ora In this release all parameters have been migrated into a single Gateway Initialization file initsid ora Migrating a previous release involves copying the parameters from the Migration and Coexistence with Existing Gateways 15 1 Backout Considerations When Migrating to New Releases initsid gtwboot or Startup Shell Script into the initsid ora The format of the parameters can be found in Appendix C DRDA Specific Parameters Step 3 Transferring initsid ora Gateway Initialization File parameters Copy the initsid ora from the old gateway instance to the new instance The formats of the parameters in the initsid ora Gateway Initialization File have changed Refer to Gateway Initialization File Parameters on page C 2 in Appendix C DRDA Specific Parameters 15 2 Backout Considerations When Migrating to New Releases During the migration from version 4 version 8 or version 9 gateway instances to the latest Oracle Database 1
177. en DRDA_PACKAGE_CONSTOKEN C 7 privileges BIND and EXECUTE DB2 UDB 5 5 privileges BIND COPY and EXECUTE DB2 0S390 5 2 DB2 VM 5 6 packed decimal 13 25 parameter changed 15 2 checking settings 11 5 diagnostic C 11 gateway 5 6 link station on HP UX 8 7 on Solaris 6 8 Native Semantics SQL Set Clauses 13 20 new since V4 gateway 15 2 obsolete since V4 gateway 15 3 renamed since V4 gateway 15 3 setting up trace parameters 16 5 parameter file tailoring to configure the host 11 3 parameters DB_DOMAIN known restrictions 2 4 DRDA_CAPABILITY 13 19 DRDA_CODEPAGE MAP defined C 2 mapping IBM CCSID D 6 DRDA_DESCRIBE_TABLE known restrictions 2 3 DRDA DISABLE CALL 11 5 DRDA PACKAGE NAME 11 5 DRDA PACKAGE SECTIONS 13 28 DRDA READ ONLY 12 5 DRDA RECOVERY PASSWORD DB2 400 5 4 DB2 0S390 5 3 DB2 UDB 5 5 DRDA RECOVERY USERID DB2 400 5 4 DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 FDS_CLASS C 9 FDS_CLASS_VERSION C 9 FDS_INSTANCE C 9 Gateway Initialization File DRDA_CACHE_TABLE_DESC C 2 DRDA_CAPABILITY C 2 DRDA_CMSRC_CM_IMMEDIATE C 3 DRDA_CODEPAGE_MAP C 2 DRDA COMM BUFLEN C 2 DRDA CONNECT PARM 16 2 DRDA CONNECT PARM SNA format C 3 DRDA CONNECT PARM TCP IP format C 3 DRDA DEFAULT CCSID C 3 DRDA DESCRIBE TABLE C 4 DRDA DISABLE CALL C4 DRDA FLUSH CACHE C 4 DRDA GRAPHIC LIT CHECK C 5 DRDA GRAPHIC PAD SIZE C 4 DRDA GRAPHIC TO MBCS C 5 DRDA ISOLATION LEVEL C 5 DRDA LOCAL NODE NAME
178. ent and maintenance The gateway capabilities are as follows Transparency at All Levels Extended Database Services Extended Advanced Networking Internet and Intranet Support Dynamic Dictionary Mapping SOL Data Definition Language Data Control Language Passthrough and Native DB2 SOL Stored Procedures Languages Oracle Database Technology and Tools SOL Plus Two Phase Commit and Multi Site Transactions Site Autonomy Migration and Coexistence Security 1 3 1 Transparency at All Levels The Oracle Transparent Gateway for DRDA gives you transparency at every level within your enterprise Oracle Transpatent gateway gives you transparency at the following levels Location End users can access tables by name without needing to understand the physical location of the tables Network The gateways exploit the Oracle Net technology to allow users to access data across multiple networks without concern for the network architecture TCP IP protocol is supported Operating system You can access data stored under multiple operating systems without being aware of the operating systems that hold the data Data storage Data can be accessed regardless of the database or file format Access method Introduction 1 3 Gateway Capabilities You can utilize a single dialect of SQL for any data store eliminating the need to code for database specific access methods or SQL implementations 1 3 2 Extended Database Services
179. ent Gateway for DRDA Installation and User s Guide Quick Reference to Oracle SQL Functions The following table lists the Oracle SQL functions in alphabetic order Table F 1 Oracle SQL Functions in Alphabetic Order Function Name Function Name Function Name Function Name ABS ACOS ADD_MONTHS ASIN ASCII ATAN ATAN2 CEIL CHAR_TO_ROWID CHR CONVERT cos COSH DECODE DUMP EXP FLOOR GREATEST HEXTORAW INITCAP INSTR INSTRB LAST_DAY EAST LENGTH ENGTHB LN LOG LOWER LPAD LTRIM MOD MONTHS_BETWEEN NEW_TIME NEXT_DAY NLS_INITCAP NLS_LOWER NLS_UPPER NLSSORT POWER RAWTOHEX REPLACE ROUND ROWIDTOCHAR RPAD RTRIM SIGN SIN SINH SOUNDEX SQRT STDDEV SUBSTR SUBSTRB SYSDATE TAN TANH TO_CHAR TO_DATE TO_LABEL TO_MULTI_BYTE TO_NUMBER TO_SINGLE_BYTE TRANSLATE TRUNC UID UPPER USER USERENV VARIANCE VSIZE BITAND Quick Reference to Oracle SQL Functions F 1 F 2 Oracle Transparent Gateway for DRDA Installation and User s Guide G Sample Applications This appendix containsthe code for sample applications that can be used with the gateway The application contains the following a DB2INS a ORAIND G 1 DB2INS DB2 INS is a sample DB2 stored procedure that inserts a row into a DB2 table This procedure uses the SIMPLE linkage convention jkkkkkkkkkkkkkkk
180. ent Gateway for DRDA Installation and User s Guide Processing Inbound Connections 14 4 TCP IP Security TCP IP does not have any additional configurable security mechanism The gateway supports a validation mechanism which requires a user ID and a valid password The security information is passed to the DRDA Server for validation This type of validation is equivalent to the SNA Security Option SECURITY PROGRAM Refer to the discussion of this option in Chapter 6 Chapter 7 or Chapter 8 The difference between the two methods is that in the SNA configuration the security validation is performed by the SNA network facilities and in the TCP IP configuration the DRDA Server manually performs the validation 14 5 Processing Inbound Connections Current DRDA Servers provide options for manipulating the security conduct of an inbound client DRDA session request Refer to Documentation Requirements on page 3 3 for a list of IBM documentation 14 5 1 User ID Mapping The most useful DRDA Server security capability is user ID mapping User ID mapping refers to changing the user ID associated with an incoming DRDA request to some other user ID known to that server This is a useful feature if your Oracle Transparent Gateway installation does not have a uniform user ID structure across all systems and databases 14 5 1 1 DB2 0S390 The DB2 DDF Communication Database CDB stores inbound DRDA session security options
181. ent behavior defaults for the server as well as for the client that overrides these defaults For a complete description of NLS parameters refer to the NLS chapter in the Oracle Database Administrator s Guide These parameters do not directly affect gateway processing However you must ensure that the client character set which is specified by the Oracle Database server NLS LANG environment variable is compatible with the character sets that you specify on the gateway and on the DRDA Server When you create an Oracle Database the character set that is used to store data is specified by the CHARACTER SET clause of the CREATE DATABASE statement After the database is created the database character set cannot be changed unless you re create the database Normally the default for CHARACTER SETis US7ASCII which supports only the 26 Latin alphabetic characters If you have specified 8 bit character sets on the gateway and the DRDA Server then you must have a compatible 8 bit character set defined on your database To check the character set of an existing database issue the command SELECT USERENV LANGUAGE FROM DUAL For more information refer to Specifying Character Sets in the Oracle Database Administrator s Guide Note that this does not mean that the gateway character set must be the same as the Oracle Database server character set The Oracle Net facility performs implicit conversion be
182. ent encryption 1 5 two phase commit 12 5 protocols IPC 10 3 SNA 1 8 TCP IP DRDA Server architecture 1 8 gateway transparency 1 3 implicit protocol conversion 1 5 public database link 11 7 Q queries distributed 12 4 R RAW datatype caution with DRDA_DEFAULT_CCSID C 3 performing character string operations 13 21 read only gateway option improved performance and security 12 5 set with DRDA READ ONLY C 8 read only support 1 14 rebind required with any change to DRDA_DISABLE_CALL C 4 DRDA_ISOLATION_LEVEL C 6 DRDA_PACKAGE_COLLID C 7 DRDA_PACKAGE_CONSTOKEN C 7 DRDA PACKAGE NAME C 7 DRDA PACKAGE OWNER C 8 DRDA PACKAGE SECTIONS C 8 recovery port number DB2 400 5 3 DB2 0S390 5 2 recovery user ID and password DB2 400 5 4 DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 remote computer 10 2 connections 12 3 data 1 4 data access 1 12 database copying data 12 6 creating database links 12 2 DB2 400 5 4 DB2 0S390 5 3 DB2 UDB 5 5 DB2 VM 5 6 defining a path 12 2 DRDA gateway package considerations privileges 11 5 DRDA PACKAGE SECTIONS C 8 errors detected by the Oracle integrating server 16 2 gateway error code 30061 16 5 privileges of user ID E 3 DB2 system 2 3 DRDA database DRDA ISOLATION LEVEL C 5 instance and Oracle stored procedures 13 2 LU 7 3 Oracle instance using DRDA Server stored procedures with the gateway 13 4 using Oracle stored procedures with the gateway 13
183. er and an error message is sent to the gateway user 8 8 Testing the Connection Before proceeding with the gateway configuration tasks in Chapter 11 Configuring the Gateway ensure that your connection is working Do this by starting the SNAPlus2 Node and then starting the individual link stations Figure 8 15 shows the relationship between SNAPlus2 definitions and the VTAM definitions on the remote host Figure 8 15 Relationship between SNAPlus2 Definitions and Host VTAM Definitions Side Information Local LU Definition Local LU Alias Partner LU Alias or Local LU Alias Local LU Name Pully qualified Mode Definition Partner LU Name Mode Name Mode Name Remote TP Name U Definiti Partner LU Definition VTAMLST Pully qualified APPL Definition gt i REM Partner LU Name pluname APPL Connection Definition netname pluname MODETAB rntnarne Partner LU Alias Connection Name ATCSTROO Connection NETWORK netname SSCPNAME cpname VTAM Mode Table mitname MODETAB MODEENT LOGMODE mode name DEH EE EEE gt ERA AAA e ERA EE EE EE gt HE A gt gt EE EE EE E A gt Configuring SNAPlus2 8 13 Testing the Connection 8 14 Oracle Transparent Gateway for DRDA Installation and User s Guide 9 Configuring TCP IP This chapter describes configuring TCP IP for the various Unix platforms supported by the Oracle Transparent Gat
184. ers o EMP e projects p WHERE o projno p projno AND p empno e empno GROUP BY o custname p projno e ename The following SQL statement retrieves information from these three data stores in one command 12 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Read Only Gateway SELECT FROM DETAILS The results of this command are CUSTNAME PROJNO ENAME SPEND ABC Co 1 Jones 400 ABC Co 1 Smith 180 XYZ Inc 2 Jones 400 XYZ Inc 2 Smith 180 12 5 1 Two Phase Commit Processing To fully participate in a two phase commit transaction a server must support the PREPARE TRANSACTION statement The PREPARE TRANSACTION statement ensures that all participating databases are prepared to COMMIT or to ROLLBACK a specific unit of work Oracle Database supports the PREPARE TRANSACTION statement Any number of Oracle DatabaseS can participate in a distributed two phase commit transaction The PREPARE TRANSACTION statement is performed automatically when a COMMIT is issued explicitly by an application or implicitly at the normal end of the application The gateway does not support the PREPARE TRANSACTION statement This limits the two phase commit protocol when the gateway participates in a distributed transaction The gateway becomes the commit focal point site of a distributed transaction The gateway is configured as commit confirm so it is always the commit point s
185. ersation and process conversation level security data If session level security is used then correct password information must be established in the host Connection Profile and in similar parameter structures in the DRDA Server system that is to be accessed Refer to the appropriate SNA server product documentation for detailed information 7 3 SNA Conversation Security SNA conversation security is determined by the setting of the Gateway Initialization parameter DRDA_SECURITY_TYPE This parameter determines whether SNA security option SECURITY is set to PROGRAM or to SAME Generally the gateway operates under SNA option SECURITY PROGRAM but it can also be set to operate under SNA option SECURITY SAME 7 3 1 SNA Security Option SECURITY PROGRAM If DRDA_SECURITY_TYPE PROGRAM is specified then the gateway allocates the conversation with SNA option SECURITY PROGRAM and sends the following information to the DRDA Server u If the database link has explicit CONNECT information then the specified user ID and password are sent m If the database link has no CONNECT clause and if the application has logged in to the Oracle integrating server with an explicit user ID and password then the Oracle user ID and password are sent u Ifthe application logs in to the Oracle integrating server with operating system authentication and if the database link lacks explicit CONNECT information then no use
186. erver It specifies the conventions such as the language used for messages from the target system names of days and months symbols for AD BC AM and PM and default language sorting mechanism The syntax of the HS LANGUAGE parameter is HS LANGUAGE language territory character set where language can be any valid language territory is optional and defaults to AMERICA character set is optional and defaults to US7ASCII This must be an ASCII base character set name and it should match a character set listed in the gateway codepage map Refer to Gateway Codepage Map Facility on page D 6 for the list of supplied character set mappings If you omit the HS LANGUAGE parameter from initsid ora then the default setting is AMERICAN AMERICA US7ASCII EBCDIC character sets are not supported The values for language and territory such as AMERICAN AMERICA must be valid but they have no effect on translations D 3 2 2 HS NLS NCHAR HS NLS NCHAR specifies the character set that is used by the gateway to interchange GRAPHIC data For correct compatibility set it to the same character set name that is specified in the HS LANGUAGE parameter If it is set to a character set other than that specified in HS LANGUAGE or if it is omitted then translation errors will occur D 3 2 3 HS_NLS_DATE_FORMAT HS_NLS_DATE_FORMAT specifies the format for dates used by the DRDA Server Th
187. es 13 1 DRDA Server datatypes list 13 20 mapping 13 20 numeric 13 25 operations numeric 13 25 Oracle datatypes RAW and LONG RAW 13 21 restrictions 13 20 size and value limitations 13 20 datatypes DATE 13 22 GRAPHIC 13 21 LONG 13 21 LONG RAW 13 21 Oracle and IBM DATE 13 22 Oracle DATE 13 22 RAW character string operations 13 21 DRDA DEFAULT CCSID C 3 TIME 13 22 TIMESTAMP 13 22 VARCHAR 13 21 date date columns TO_DATE function 13 24 DELETE statement 13 24 HS_NLS_DATE_FORMAT parameter 13 24 INSERT statement 13 24 operations 13 22 SELECT statement 13 24 TO_DATE function 13 23 UPDATE statement 13 24 date arithmetic known restrictions 2 4 DATE datatype 13 22 DB_DOMAIN parameter known restrictions 2 4 DB2 02pcg sql granting authority 11 7 alias objects known restrictions 2 3 aliases C 4 CICS 13 5 configuring DB2 0S390 5 2 data access 1 6 Distributed Data Facility DDF 5 3 DRDA_DESCRIBE_TABLE compatibility C 4 IBM DB2 Version 5 1 ASCII Tables 1 14 IMS 13 5 native SQL 1 5 native stored procedures 1 6 procedural feature considerations 13 5 SPUFI utility 5 3 SQL statements 13 26 statements CREATE TABLE 1 5 stored procedures 13 5 DB2 400 catalog view 13 27 configuring 5 3 data dictionary views supported by gateway A 1 DRDA_DEFAULT_CCSID C 3 DRDA_ISOLATION_LEVEL C 5 DRDA_OPTIMIZE QUERY C 6 DRDA PACKAGE COLLID C 7 user ID mapping 14 4 DB2 05390 catalog view 13 27
188. es on DB2 Universal Database DB2 UDB oconicicicicocicicinininanincones 11 4 DRDA Gateway Package Considerations ea 11 5 Before Binding the DRDA Gateway Package 11 5 sampIeSOFSCEPIS Z i A dai A A A AA 11 6 Backup and Recovery of Gateway Configuration ane 11 7 Configuring the Oracle Integrating Server 11 7 Step 1 Create a database link 11 7 Step 2 Create synonyms and VvieWS natan 11 7 Accessing the Gateway from Other Oracle Databases u euaaaa aaa 11 7 Accessing Other DRDA Servers isinisisi deet assisia eai iondan i daeh 11 8 Gateway Installation and Configuration Complete 11 8 Using the Oracle Transparent Gateway for DRDA 12 1 12 1 1 12 1 2 12 1 3 12 1 4 12 2 12 3 12 4 12 5 12 5 1 12 5 2 12 6 12 7 12 8 12 9 12 10 Processing a Database Link wz z iti iaa adan 12 1 Creating Database Links vive ii a a E A PSE 12 2 Dropping Database Links sio O ooo orei 12 2 Examining Available Database LinkS aaa 12 3 Limiting the Number of Active Database LinkS aaa 12 3 Accessing the Gateway irnos oda A ii 12 3 Accessing AS 400 File Members siniri od Ea 12 3 Using the Synonym Feature aii Sasa ta ine istih acritud lia ies iii 12 4 Performing Distributed Queries e A 12 4 Two Phase Commit Processing nana 12 5 Distributed DRDA Transactions cccccccessessesscesseesceseeesecscessecssesaecsecsseesesessseseeeeeeeeeeees 12 5 Read Only Gateway
189. es program that detected error 16 2 file member accessing AS 400 files 12 3 name 12 3 files initsid ora communication errors 16 3 gateway error 700 16 4 listener ora 10 3 sample listener ora B 2 tnsnames ora B 2 sna_domn cfg on HP UX 8 2 on Solaris 6 2 sna_node cfg on HP UX 8 2 on Solaris 6 2 tnsnames ora configuring additional DRDA Server instances 11 8 modifying 10 3 VSAM 13 5 FOR BIT DATA DRDA DEFAULT CCSID C 3 option 13 21 free session DRDA CMSRC CM IMMEDIATE C 3 functions COS 13 7 COUNT 13 25 DBMS HS PASSTHROUGH EXECUTE IMMEDI ATE 13 26 DRDA Server 13 18 SOL SUBSTR 13 18 SUBSTR known restrictions 2 3 TO_DATE DB2 ISO format 13 24 processing DATE data 13 22 twenty first century dates 13 23 TO_DATE main topic 13 24 G g4ddtab sql script 11 6 g4ddview sql script 11 6 gateway accessing from other Oracle servers 11 7 main topic 12 3 advantages main topic 1 2 migration and coexistence 1 7 multi site transactions 1 6 security 1 7 server technology and tools 1 6 site autonomy 1 7 two phase commit 1 6 and Oracle tools 1 10 and stored procedures Oracle and non Oracle 1 6 application tools 1 13 architecture 1 7 authenticating logons 14 1 benefits of integration with Oracle Database server 1 4 binding DRDA packages 11 4 components 1 9 configuration 11 3 definition of terms 1 7 de installing 4 4 4 5 DRDA package considerations 11 5 error codes 16 4
190. eway for DRDA TCP IP is a communication facility that is already part of the operating system No third party protocol software is required This chapter provides more information about configuring TCP IP This chapter contains the following sections u Before You Begin u Configuring TCP IP under UNIX 9 1 Before You Begin You need values for to enter parameters that are unique to your system in order to properly configure TCP IP Refer to Appendix E for a worksheet listing all of the installation parameters that you will need to know about before you can complete the configuration process Ask your network administrator to provide you with these parameters before you begin Port Number The DRDA standard specifies that port 446 be used for DRDA services However if several DRDA Servers are operating on the same system then they will need to provide service on different ports Therefore the port number that is used by each DRDA Server will need to be extracted from the configuration of each individual DRDA Server DB2 for OS 390 and DB2 400 typically use the DRDA standard port number 446 whereas DB2 UDB typically uses 50000 as the port number Refer to IBM DB2 Administrator and Installation guides for locating and changing these port numbers for your DRDA Server For additional information consult your DB2 DBA or System Administrator 9 2 Configuring TCP IP under UNIX Basic configuration consists of assigning a Hostname an IP Addre
191. eway must convert the date to an IBM DRDA compatible format The gateway does not automatically recognize when a character value is being processed against an IBM DATE column Applications are required to distinguish character date values by enclosing them with Oracle TO_DATE function notation For example if EMP is a synonym or view that accesses data on an IBM DRDA database then you should notb use the following SQL statement SELECT FROM EMP WHERE HIREDATE 03 MAR 81 you should use the following 13 22 Oracle Transparent Gateway for DRDA Installation and User s Guide DRDA Data type to Oracle Data type Conversion 13 7 5 Dates SELECT FROM EMP WHERE HIREDATE TO_DATE 03 MAR 81 In a programmatic interface program that uses a character bind variable for the qualifying date value you must use this SQL statement SELECT FROM EMP WHERE HIREDATE TO_DATE 1 The above SQL notation does not affect SQL statement semantics when the statement is executed against an Oracle Database table The statement remains portable across Oracle and IBM DRDA accessed data stores The TO_DATE function is not required for dates in any of the following formats u YYYY MM DD ISO JIS u DD MM YYYY European D YYYY USA m MM U For example SELECT FROM EMP WHERE HIREDATE 1981 03 03 The TO_DATE requirement also does not pertain to input bind variables that are in Oracle d
192. ex 20
193. f or any content provided on third party Web sites You bear all risks associated with the use of such content If you choose to purchase any products or services from a third party the relationship is directly between you and the third party Oracle is not responsible for a the quality of third party products or services or b fulfilling any of the terms of the agreement with the third party including delivery of products or services and warranty obligations related to purchased products or services Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party Contents Send Us Your Comments aaa xi o nadana ENE EVE NE TIKA ENE RINE RE EAEE A Crete xiii Intended Audienc es s s nani ti lai vo endo A ecos io xiii PLOCESSOLS inu a ta c tenes Desens bh dengue ia io xiii Documentation Accessibility e eta xiv Related Documents i A A tha Dike Sacco bev ve A SNE oes Bato xiv CONVENIOS nara MO A NOSOWA AA E NEEE EE EN NE ad XV SOLPIUS Prompts awa Re sabes O a wii A A ETARE XV Storage Measurement n e O r tras PENO aj deo ison Zo oba bno ah le a XV 1 Introduction 1 1 Introduction to the Oracle Transparent Gateway uses 1 1 1 2 Release 10 Gate Ways aa ay iii aa 1 2 1 3 Gateway CapabilitiES u wzi nt O A telice neda kwi dida pct 1 2 1 3 1 Transparency at AU Levels ninia RO Sa 1 3 1 3 2 Extended Database Services 1 4 1 3 3 Extended Advanced
194. figuring using xsnapadmin program 8 1 definitions for the gateway 8 3 stored in directory 8 2 Side Information Profiles required 8 2 testing the connection 8 13 version required 3 3 snapshots known restrictions SOL limitations 2 6 Oracle Snapshot feature 12 6 software requirements 3 2 sort order with ORDERBY 13 19 SPUFI a database native tool 11 6 SQL ANSI standard 1 5 clause compatibility 13 20 clauses DELETE 13 24 INSERT 13 24 SELECT WHERE 13 24 UPDATE 13 24 constructs Oracle processing 13 6 differences in the gateway 1 10 errors mapped to Oracle error codes 16 3 functions SUBSTR 13 18 functions and Native Semantics 13 18 functions list F 1 gateway architecture 1 2 gateway transparency 1 5 ISO standard 1 5 native DB2 1 5 passthrough 13 25 13 26 13 27 statements 13 2 DB2 13 26 issued through the gateway 12 7 passing through gateway 13 25 statements DRDA_ISOLATION_LEVEL C 5 syntax 13 25 tracing not to be used in production environment 12 7 SQL functions column functions 13 6 compatible defined 13 6 compensated defined 13 6 DB2 400 13 12 DB2 0S390 13 7 DB2 UDB 13 10 DB2 VM 13 15 post processing defined 13 6 that can be disabled 13 19 that can be enabled 13 19 translated defined 13 6 with Native Semantics 13 19 SQL tracing in Oracle Database 16 5 in the gateway 16 6 LOG_DESTINATION 16 6 ORACLE DRDA TCTL parameter 16 6 TRACE LEVEL parameter 16 6 SOL Net
195. formance by minimizing network traffic Instead of sending individual SQL statements across the network an application can send a single EXECUTE command to begin an entire PL SQL routine Native DB2 Stored Procedures The gateway can execute DB2 stored procedures using standard Oracle PL SQL The Oracle application executes the DB2 stored procedure as if it were an Oracle remote procedure 1 3 10 Languages Any application or tool that supports the Oracle Database 10g can access over thirty different data sources through the Oracle gateways A wide variety of open system tools from Oracle Corporation and third party vendors can be used even if the data is stored in legacy proprietary formats Hundreds of tools are supported including ad hoc query tools Web browsers turnkey applications and application development tools 1 3 11 Oracle Database Technology and Tools The gateway is integrated into the Oracle Database technology which provides global query optimization transaction coordination for multi site transactions support for all Oracle Net configurations and so on Tools and applications that support the Oracle Database server can be used to access heterogeneous data through the gateway 1 3 12 SQL Plus You can use SQL Plus for moving data between databases This product gives you the ability to copy data from your department databases to corporate Oracle Database instances 1 3 13 Two Phase Commit and Multi Site Transa
196. g 3 2 token package consistency DRDA PACKAGE CONSTOKEN C 7 tools and the gateway 1 10 TP name TPN 6 10 7 3 8 10 trace control C 11 trace parameters setting 16 5 TRACE LEVEL parameter defined C 11 SOL tracing in the gateway 16 6 tracing code C 12 LOG DESTINATION C 10 ORACLE DRDA TRACE C 11 SOL statements 12 7 trade off Native Semantics 13 18 transaction mode read only DRDA READ ONLY C 8 transaction program name remote 7 3 transactions CICS 13 5 IMS 13 5 transform character set transforms with multi byte support D 8 transform not reguired for DRDA Server D 10 transparency main topic gateway transparency 1 3 native semantics 13 18 triggers for Oracle Server 12 6 TSO configuring DB2 0S390 5 2 two phase commit ORACLE2PC table DB2 400 5 4 DB2 UDB 5 5 DB2 VM 5 6 ORACLE2PC table DB2 05390 5 2 processing transactions 12 5 protection 1 4 unsupported statement 12 5 U UNION capability 1 4 operator SOL Set Clauses 13 20 SQL set operators and clauses 13 20 UNION ALL operator SOL Set Clauses 13 20 SQL set operators and clauses 13 20 UPDATE known restrictions SQL limitations 2 6 operation 13 2 read only gateway 12 6 SQL clause 13 24 statement 13 25 user ID mapping AVS 144 DB2 400 14 4 DB2 0S390 14 3 DB2 VM 14 4 user ID translation DB2 14 4 user privileges 13 27 SER_CATALOG view A 10 SER COL COMMENTS view A 10 SER CONS COLUMNS view A 11 SER CONSTRAINT
197. g server with operating system authentication and if the database link lacks explicit CONNECT information then no user ID and password are sent If no user ID and password are sent and if the DRDA Server is not configured to assign a default user ID then the connection fails In general SECURITY PROGRAM tells the DRDA Server to authenticate the user ID password combination using whatever authentication mechanisms are available For example if DB2 05390 is the DRDA Server then RACF can be used This is not always the case however because each of the DRDA Servers can be configured to process inbound user IDs in other ways SNA Security Option SECURITY SAME If DRDA_SECURITY_TYPE SAME is specified then the gateway allocates the conversation with SNA option SECURITY SAME and the following information is sent to the DRDA Server u If the database link has explicit CONNECT information then the specified user ID is sent u If the database link has no CONNECT clause and if the application has logged into the Oracle integrating server with an explicit user ID and password then the Oracle user ID is sent u Ifthe application logs into the Oracle integrating server with operating system authentication and if the database link lacks explicit CONNECT information then no user ID is sent If no user ID is sent and if the DRDA Server is not configured to assign a default user ID then the connection fails
198. ge C 4 22 DRDA_PACKAGE_NAME Default value G2DRSQL Range of values An alphanumeric string 1 to 18 characters in length Syntax DRDA_PACKAGE_NAME name DRDA_PACKAGE_NAME specifies the package name Note that the package is stored in the DRDA Server under this name as a SOL resource Refer to the DRDA Server documentation for length limitations package names Many typical implementations restrict the length to 8 characters Note Any change to this parameter requires that you rebind the package C 4 23 DRDA_PACKAGE_OWNER Default value None Range of values Any valid user ID Syntax DRDA_PACKAGE_OWNER userid DRDA_PACKAGE_OWNER specifies the database user ID that owns the package This enables the owner to be a user other than the connected user ID when the package is created The package owner must be the same user as the owner of the ORACLE2 PC table This is not valid for DB2 VM DRDA Specific Parameters C 7 Gateway Initialization File Parameters Note Any change to this parameter requires you to rebind the package C 4 24 DRDA_PACKAGE SECTIONS Default value 100 Range of values Any integer between 1 and 65535 Syntax DRDA_PACKAGE_SECTIONS num DRDA_PACKAGE_ SECTIONS specifies the number of cursors declared at the remote database when the package is bound This is the maximum number of open cursors permitted at any one time Change this paramete
199. ger than 8 characters Action A user ID of length of 8 or less must be used Refer to Chapter 14 Security Considerations for a discussion of user IDs 705 Password length greater than maximum Cause The password being used for the allocation of an APPC conversion by the gateway is longer than 8 characters Action A password of length of 8 or less must be used Refer to Chapter 14 Security Considerations for a discussion of passwords 777 DRDA Server RDBMS SQL Error Cause Server database detected an application level SQL error Action Refer to Interpreting Gateway Error Messages on page 16 1 sqlcode and for more information to fix your application 16 4 Oracle Transparent Gateway for DRDA Installation and User s Guide SQL Tracing and the Gateway 30060 Invalid UserID Password DRDA Server RDBMS Authorization Cause You have used a user ID or password that is not accepted by the DRDA Server database Action Refer to Chapter 14 Security Considerations for user ID password considerations 30061 RDB not found Cause The remote database specified with the DRDA_REMOTE_DB_NAME parameter is not a valid database in the DRDA Server Action Correct the value of the DRDA_REMOTE_DB_NAME parameter in the initsid ora file 30080 Communication Error Cause The gateway encountered a CPI C communication error Action Try processing the received error If it persists then
200. gers The same Oracle stored procedures and database triggers can be used to access all of your data thereby ensuring uniform enforcement of your business rules across the enterprise 1 3 3 Extended Advanced Networking Internet and Intranet Support The gateway integration with the Oracle Database 10 extends to non Oracle data the benefits of the Oracle Internet and Oracle Net software and extends the benefits of the Oracle client server and server server connectivity software These powerful features include Application server support Any Internet or intranet application that can access data in Oracle Database can also incorporate information from data stores accessible through the gateways Web browsers can connect to the Oracle Database using any application server product that supports Oracle software Implicit protocol conversion Oracle and Oracle Net can work together as a protocol converter allowing applications to transparently access other data stores on platforms that do not 1 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Capabilities support the clients network protocol An Oracle Database 10g can use TCP IP to communicate with the gateway and another data store ua Advanced Security Non Oracle data can be protected from unauthorized access or tampering during transmission to the client This is done by using the hardware independent and protocol independent encryption and CHECKS
201. hardware requirements 3 1 HAVING clause SQL Set Clauses 13 20 heterogeneous database integration 1 12 Heterogeneous Services HS see HS 1 2 HGO 00706 error 16 2 host DRDA Server SNA and TCP IP protocols 1 8 Logical Unit LU on AIX 7 4 on HP UX 8 11 on Solaris 6 11 networking needs 3 3 performing character string operations on 13 21 relationship to gateway and Oracle Server 1 8 security validation required to begin database link on AIX 7 4 on HP UX 8 11 on Solaris 6 11 SNAP IX definitions 6 3 variable 13 20 HP9000 host Index 9 creating local LUs 8 8 invoking xsnapadmin 8 3 sample SNAPlus2 definitions 8 3 HS Heterogeneous Services architecture features 1 11 Oracle Net considerations 15 4 HS TNSNAMES parameter for Oracle Net gateway migration problems 15 2 modify tnsnames ora file 10 3 HS_DB_DOMAIN parameter known restrictions 2 4 HS_FDS_FETCH_ROWS parameter C 10 HS_LANGUAGE parameter C 10 HS_NLS_DATE_FORMAT for dates used by the DRDA Server D 5 four date patterns 13 24 HS_NLS_DATE_LANGUAGE D 5 HS_NLS_NCHAR character set to interchange GRAPHIC data D 5 defined C 10 HS_RPC_FETCH_REBLOCKING parameter controlling array blocksize and the block fetch 1 11 Oracle Database server support 13 2 HS_RPC_FETCH_SIZE parameter specified in the Gateway Initialization File 1 11 value determines array size 13 2 IBMRDB DRDA mode on HP UX CPI C destination dialog box 8 10
202. he gateway will apply those naming rules when searching for a procedure name in the catalog The matching rules will first search for a public definition and then an owner qualified procedure name For more detailed information refer to the IBM reference document for DB2 for OS 390 SQL 13 3 2 Procedural Feature Considerations with DB2 The following are special considerations for using the procedural feature with the gateway u DB2 stored procedures do not have the ability to coordinate commit and rollback activity on recoverable resources such as IMS or Customer Information Control System CICS transactions Therefore if the DB2 stored procedure calls a CICS or IMS transaction then it is considered a separate unit of work and does not affect the completion of the stored procedure This means that if you are running a DB2 stored procedure from an Oracle application and if this procedure calls a CICS or IMS transaction then the gateway cannot recover data from any activity that occurred within the CICS or IMS transaction For example the CICS transaction could roll back a unit of work but this does not prevent the gateway from committing other DB2 work contained within the DB2 stored procedure Likewise if the DB2 stored procedure updated an irrecoverable resource such as a video surveillance and monitoring VSAM file then the gateway would consider this activity separate from its own recoverable unit of work u PL SQL records
203. his option to function properly IBM Communications Server requires that the effective user ID under which the gateway is executing must be a member of the system group In UNIX terms this means that the user ID must be defined with its primary group set to system In addition the owning user ID of the gateway executable must be set to the desired effective user ID and the set uid bit of the executable file permissions must also be set The 1s 1 command shows the owning user ID and the setting of the set uid bit for the executable file The owning user ID can be changed by the root user with the chown command and the set uid bit can be set using the chmod u s command The gateway executable as installed by the Oracle Universal Installer has its set uid bit disabled The simplest way to cause the gateway to execute under an effective user ID that is a member of the system group is to change the owning user ID of the gateway executable to root Another way is to change the primary group for the owning user ID of the gateway executable to system However be careful when choosing the user ID Oracle recommends using root and recommends never changing the Oracle dba user ID primary group to system When the effective user ID is not a member of the system group a failure is generated when the gateway attempts to allocate a conversation with the DRDA Server and an error message is sent to the gateway user Configuring IBM Communication Server 7 5
204. i Yes Yes FLOOR H Yes GREATEST 5 z Yes Yes HEXTORAW gt Yes Yes NITCAP z Yes Yes INSTR 3 Yes Yes INSTRB Yes Yes LAST_DAY z Yes LEAST Yes Yes LENGTH s H Yes Yes ENGTHB Yes Yes LN A Yes Yes LOG H a Yes Yes OWER Yes Yes LPAD 5 Yes Yes TRIM Yes Yes MAX Yes MIN Yes MOD m a Yes Yes 13 16 Oracle Transparent Gateway for DRDA Installation and User s Guide Oracle Database SQL Construct Processing Table 13 4 Cont DB2 VM SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate MONTHS_ BETWEEN Yes NEW_TIME z Yes NEXT DAY s Yes NLS INITCAP H Yes Yes NLS LOWER E Yes Yes NLS_UPPER z Yes Yes NLSSORT E Yes Yes NVL H VALUE NVL2 Yes Yes POWER 5 Yes Yes RAWTOHEX Yes Yes REPLACE Yes Yes REVERSE s z Yes Yes ROUND 5 Yes Yes ROWIDTOCHAR s z Yes s RPAD 5 Yes Yes RTRIM z Yes Yes SIGN 2 Yes Yes SIN a Yes Yes SINH Yes Yes SOUNDEX z H Yes SORT Yes Yes STDDEV Yes Yes SUBSTR Yes Yes SUBSTRB Yes Yes SU Yes SYSDATE Yes TAN Yes Yes TANH gt E Yes Yes TO_CHAR Yes
205. if the view is a typed view SUPERVIEW_NAME N A A 2 14 COLUMN PRIVILEGES Grants on columns for which the user is the grantor grantee or owner or PUBLIC is the grantee column name description GRANTEE Name of the user to whom access was granted OWNER Username of the owner of the object TABLE NAME Name of the object COLUMN NAME Name of the column GRANTOR Name of the user who performed the grant INSERT PRIV Permission to insert into the column UPDATE PRIV Permission to update the column REFERENCES PRIV Permission to reference the column CREATED Timestamp for the grant Oracle DB2 Data Dictionary Views A 9 Data Dictionary View Tables A 2 15 DICTIONARY List or data dictionary tables column name description TABLE_NAME Table name COMMENTS Description of the table A 2 16 DUAL List of Dual tables column name description DUMMY A dummy column A 2 17 TABLE_PRIVILEGES Grants on objects for which the user is the grantor grantee or owner or PUBLIC is the grantee column name description GRANTEE Name of the user to whom access is granted OWNER Owner of the object TABLE_NAME Name of the object GRANTOR Name of the user who performed the grant SELECT_PRIV Permission to se
206. ific errors that are documented in Gateway Error Codes on page 16 4 u grc specifies generic gateway errors detected in the DRDA layer These errors are documented in the Oracle Database Error Messages Note Error code ORA 28500 was error code ORA 09100 prior to gateway version 8 Error code ORA 28501 was listed as ORA 09101 prior to gateway version 8 The values in parentheses that follow the drc values are used for debugging by Oracle Support Services The errp field indicates the program client or server that detected the error If present errmc lists any error tokens For example the following error message is returned when the database name specified with the DRDA_REMOTE_NAME parameter in the initsid ora file is not defined at the DRDA Server ORA 28500 connection from ORACLE to a non Oracle system returned the message TG4DRDA v10 2 0 1 0 grc 0 drc 30061 839C 0000 errp GDJRFS2E errmc XNAME 16 1 4 Communication Errors Communication errors are reported with an ORA 28501 followed by a gateway specific expanded error message with drc 30080 SNA CPI C error where CPI is Common performing Interface or drc 30081 lost session errmc indicates which CPI C routine encounters the error followed by the CPI C error code and error number For example the following error message is returned when there is a failure to establish a session because DRDA_CONNECT_PARM in the initsid ora file specifies a Side Informa
207. ight be necessary if parameters from the Startup Shell Script are moved into the Gateway Initialization File If the private keyword is present then the parameter and its value will not be uploaded to Oracle Database In general Oracle recommends that the private keyword unless the parameter contains sensitive information a userID or password DRDA Specific Parameters C 1 Gateway Initialization File Parameters For further information on Heterogeneous Services and Initialization Parameters refer to the section Setting Initialization Parameters in the Oracle Database Heterogeneous Connectivity Administrator s Guide C 4 Gateway Initialization File Parameters The following sections list gateway specific initialization file parameters and their descriptions In addition to these parameters generic Heterogeneous Services initialization file parameters may be set Refer to the Oracle Database Heterogeneous Connectivity Administrator s Guide for a list of additional parameters C 4 1 DRDA_CACHE_TABLE_DESC Default value TRUE E Range of values TRUE FALSI Syntax DRDA_CACHE_TABLE_DESC TRUE FALSE DRDA_CACHE_TABLE_DESC directs the gateway to cache table descriptions once per transaction This can reduce the number of table lookups requested by Oracle Database and can speed up the execution of SQL statements You may wish to disable this option if you would be altering the structure of a remote t
208. imilar to the DB2 user ID translation mechanism and can be used to work around a variety of incongruities among user IDs on different systems and databases After any indicated user ID mapping has been done inbound DRDA connection requests are forwarded to the specified DB2 VM server machine DB2 VM confirms only that the user ID has CONNECT authority and if so that the connection is complete At this point the applications access to DB2 VM objects is controlled by the normal authorities and GRANTs for the connected user ID The user ID must have execute authority on the gateway DRDA package to process any SQL statements 14 5 1 3 DB2 400 DB2 400 does not provide a user ID mapping capability comparable to that in DB2 0S390 and DB2 VM Normally the user ID in an incoming DRDA connection request must be a valid user ID on that DB2 400 The DB2 400 subsystem communications entry for the gateway should specify that the gateway is not a secure location and should include a default user ID of NONE After the application has completed the DRDA connection to the DB2 400 it is subject to all authorities and GRANTS associated with the user ID in use The user ID must have execute authority on the gateway DRDA package to execute any SQL statements 14 5 1 4 DB2 Universal Database DB2 Universal Database DB2 UDB does not provide a user ID mapping capability comparable to that in DB2 05390 and DB2 VM Normally the user ID in an incoming DRDA
209. information Appropriate Mode E 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Table E 1 Cont List of Parameters Needed to Configure the Gateway Reason Name of Parameter Needed Your Specific Parameters Here Partner Information in CPI C Name Properties TP Name Partner Information in CPEC Name Properties Partner LU Name Alias Configuring TCP IP Local Hostname Domain Name Configuring TCP IP IP Address Configuring TCP IP Network Mask Configuring TCP IP Name Server IP Address Configuring TCP IP DRDA Server Hostname or IP Address Configuring TCP IP DRDA Server Service Port Number Recovery user ID DRDA_RECOVERY_USERID Recovery Password DRDA_RECOVERY_PASSWORD Remote Database Name DRDA REMOTE DB NAME Connection Parameter DRDA CONNECT PARM Owner ID of DRDA package DRDA_PACKAGE_OWNER DB Name used with Oracle Database server HS_DB_NAMI LEI DB Domain used with Oracle Database server HS_DB_DOMAIN Note The user ID that is used to bind or rebind the DRDA package must have the appropriate privileges on the remote database as described in Chapter 5 Configuring the DRDA Server Your database administrator will need to provide these privileges Configuration Worksheet E 3 E 4 Oracle Transpar
210. ing TCP IP worksheet E 3 Destination Service Port Number same as DRDA Server Service Port Number configuring TCP IP worksheet E 3 diagnostic parameter C 11 dictionary mapping 1 5 tables 13 27 DICTIONARY view A 10 disk space requirements 3 2 distributed applications support for 1 13 data facility DDF 5 3 database 10 2 distributed query optimizer DQO DRDA specific parameters C 6 performing distributed queries 12 4 DRDA transactions 12 5 operations DB2 5 3 processing 10 2 queries two phase commit 12 5 transaction DRDA_RECOVERY_USERID C 8 dmesg 6 5 double byte support D 8 DQO also see distributed query optimizer 12 4 DRDA specific parameters C 6 drc error code 16 2 DRDA catalog 13 28 database requirements 3 2 defining number of cursors 13 28 DRDA Application Server Function 1 12 gateway package considerations 11 5 location name for DB2 UDB instance 5 5 for DB2 VM instance 5 6 mode IBMRDB Index 6 on HP UX 8 9 on Solaris 6 10 session security options 14 3 DRDA Server accessing 11 8 and dependent LUs on HP UX 8 2 on Solaris 6 2 and independent LUs on HP UX 8 2 on Solaris 6 2 and Side Information Profiles on HP UX 8 2 on Solaris 6 2 architecture 1 8 capabilities native semantics 13 18 character sets known restrictions 2 4 client applications initiate conversations using dependent LUs on HP UX 8 2 on Solaris 6 2 configuring DB2 400 5 3 DB2 0S390 5 2 DB
211. initions provided will not work without being tailored for the local host and SNA network Before building the SNA profiles examine these files to determine requirements The export file format is text oriented and each field of each profile is labeled You can print a copy of the export file to use while working with your profiles 7 1 2 2 Profile Types There are different types of Communications Server profiles relevant to gateway APPC LU6 2 operation Create and edit profiles using the SNA administration tool The profiles relevant to the gateway are presented here in hierarchical order Those profile types that are lowest in the hierarchy are discussed first This matches the logical sequence for creating the profiles Mode Profile The Mode Profile specifies parameters that determine u APPC LU6 2 parallel session limits a Send and receive pacing values a SNA RU size m The mode name that is sent to the server at session initiation The mode name that you specify must be defined in the DRDA Servers communication software DRDA Servers use the mode name IBMRDB in many DRDA examples but this is not required Choose the mode name and the other mode parameters after consulting the person responsible for configuring the DRDA Server side communications software The parameters related to parallel session limits play a role in determining the maximum number of concurrent conversations allowed between a gateway instance and the DRDA Ser
212. ite regardless of the commit point strength setting The gateway commits the unit of work after verifying that all Oracle Databases in the transaction have successfully committed their work The gateway must coordinate the distributed transaction so only one gateway can participate in an two phase commit transaction Two phase commit transactions are recorded in the ORADRDA ORACLE2 PC table which is created during installation This table is created when the o2pc sql script is run The owner of this table also owns the package Refer to DRDA Gateway Package Considerations on page 11 5 for more information 12 5 2 Distributed DRDA Transactions Because the ORACLE2PC table is used to record the status of a gateway transaction this table must be in at the database where the DRDA update takes place Therefore all updates that take place over the gateway must be local to the IBM database Note Updates to the ORACLE2PC table cannot be part of an IBM distributed transaction For additional information about the two phase commit process refer to Oracle Database Administrator s Guide 12 6 Read Only Gateway The read only option can provide improved performance and security This improved performance depends on your configuration and parameter selections A Gateway Initialization Parameter DRDA_READ_ONLY controls whether the gateway is enabled in this mode If you enable the read only option the
213. ith SUBSTR function known restrictions 2 4 network attachment 3 2 Oracle Net configuration 10 3 requirements 3 2 NLS National Language Support DRDA Server character sets D 6 initsid ora parameters D 5 parameters configuration on client and Oracle servers D 3 NLS_LANG environmental variable D 2 server side parameter D 2 NLS_LANG environment variable D 3 non character binary data 13 21 null rows mapping the COUNT function 13 25 values Index 11 mapping the COUNT function 13 25 number of cursors DRDA_PACKAGE SECTIONS C 8 numbers concatenation restrictions 2 4 numeric datatype zoned decimal column 13 25 O o2pc sql ORACLE2PC table 11 7 two phase commit transactions 12 5 obsolete parameters since V4 gateway 15 3 open cursors at the IBM database 13 28 OPEN_LINKS parameter 12 3 operating system user ID for DB2 UDB 5 5 operating system requirements 3 2 operations DELETE 13 2 INSERT 13 2 SELECT 13 2 UPDATE 13 2 operators UNION ALL SQL Set Clauses 13 20 UNION SQL Set Clauses 13 20 option binding packages 11 5 data dictionary views 13 27 date format string 13 24 DRDA session security 14 3 FOR BIT DATA 13 21 Oracle server 1 8 read only gateway configuration 1 7 replicating 12 6 security conduct 14 3 service port number DRDA CONNECT PARM C 3 SNA security 6 12 7 4 8 11 SQL functions 13 19 SQL Plus COPY command 12 6 ORA_MAX_DATE parameter C 11
214. itions called Side Information Profiles to support connections between the gateway and DRDA Servers Each profile consists of a profile name and a profile type which is a set of fields describing the profile The fields in a given profile type are generally a mixture of operating parameter values and names of other SNA profiles relevant to the profile Each functional part of APPC such as the Mode Remote Transaction Program name and LU is described by a distinct profile type 6 5 Independent Versus Dependent LUs The gateway configuration can accommodate either independent LUs or dependent LUs If you choose to use dependent LUs or are restricted to using dependent LUs the gateway will function properly if a dependent LU is correctly defined then you will need to make no alterations to the configuration of the Oracle Transparent Gateway for IBM DRDA nor should any changes be needed to the DRDA Server However Oracle recommends using independent LUs for the Oracle Transparent Gateway for IBM DRDA because they support multiple parallel sessions or conversations This means that multiple Oracle client applications can be active simultaneously with the same DRDA Server through the independent LU In contrast to independent LUs dependent LUs support only a single active session The Control Point for the Node CP queues each additional conversation request from the gateway behind an already active conversation In other words conversations a
215. kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk qe w This DB2 stored procedure inserts values for the DNAME and LOC columns of DB2 user table SCOTT DEPT w po E The SCOTT DEPT table is defined to DB2 as JE DEPTNO INTEGER DNAME CHAR 14 LOC VARCHAR 13 qa y This procedure receives 3 input parameters from the calling program which contain the values to insert for DEPTNO DNAME and LOC i tili The linkage convention used for this stored procedure is SIMPLE po The output parameter for this procedure contains the SQLCODE from the INSERT operation SZ qa W The entry in the DB2 catalog table SYSIBM SYSPROCEDURES for this L stored procedure might look like this AY INSERT INTO SYSIBM SYSPROCEDURES SJ JE PROCEDURE AUTHID LUNAME LOADMOD LINKAGE COLLID LANGUAGE x je ASUTIME STAYRESIDENT IBMREOD RUNOPTS PARMLIST VALUES DB2INS DB2INS DB2DEV C 0 x N A INT IN B CHAR 14 IN C VARCHAR 13 IN D INT OUT E CHAR 10 OUT ay FERERRERERER e ERE RE ERK RR ERE RE He He He He He He ERRE RE RRE RE RA AAA RRE RARA RE RRA ARA RAE RARAS pragma runopts plist os include lt stdlib h gt include lt stdlib h gt EXEC SQL INCLUDE SQLCA RRR RRR RRR ER RARA RARE KR EERE RR ERR EKER EKER EERE ARRE ARRE RE RARE RRA RA ARA RARAS Declare C variables for SQL operations on the parame
216. l 6 10 Oracle Transparent Gateway for DRDA Installation and User s Guide Using SNA Session Security Validation LU you may specify a specific LU or choose the default LU For the Partner LU enter either the full LU name or the alias created previously Enter IBMRDB for the mode name Choose the type of security these sessions will use This will affect how session authorization is done Click OK Figure 6 14 CPI C destination Dialog Box 6 7 Using SNA Session Security Validation When the database link request for the gateway begins the gateway attempts to start an APPC conversation with the DRDA Server Before the conversation can begin a session must start between the host LU and the DRDA Server LU SNA and its various access method implementations including SNAP IX and VTAM provide security validation at session initiation time allowing each LU to authenticate its partner This is carried out entirely by network software before the gateway and server application programs begin their conversation and process conversation level security data If session level security is used then correct password information must be established in the host Connection Profile and in similar parameter structures in the Configuring SNAP IX Interfaces 6 11 SNA Conversation Security DRDA Server system that is to be accessed Refer to the appropriate SNA server product documentation for detailed information 6 8 SNA Conversation Securit
217. le Transparent Gateway for DRDA Installation and User s Guide C DRDA Specific Parameters This appendix contains the DRDA specific parameters that are defined in the Gateway Initialization File The appendix contains the following sections a Modifying the Gateway Initialization File m Setting Parameters in the Gateway Initialization File u Syntax and Usage Gateway Initialization File Parameters C 1 Modifying the Gateway Initialization File If you change any parameters in the Gateway Initialization File then you must stop and restart the gateway in order for them to take effect If you change certain parameters then you must also rebind the DRDA package Any parameters that affect the DRDA package have a note in their description that rebinding is required C 2 Setting Parameters in the Gateway Initialization File Parameters that are specific to the gateway are stored in the Gateway Initialization File initsid ora C 3 Syntax and Usage Parameters and their values are specified according to the syntax rules that are specified by Heterogeneous Services The general form is set private drda_parameter drda_parameter_value where drda_parameter is one of the DRDA parameters drda_parameter_value is a character string with contents depending drda_parameter The set and private keywords are optional If the set keyword is present then the parameter and its value will be passed to the process environment This m
218. le byte EBCDIC D 837 gt ZHS16DBCS shift Simplified Chinese double byte EBCDIC M 935 ZHS16DBCS shift Simplified Chinese multi byte EBCDIC MBC 935 836 837 Simplified Chinese multi byte EBCDIC S 1027 gt JA16DBCS Japanese single byte EBCDIC D 300 gt JA16DBCS shift Japanese double byte EBCDIC D 4396 gt JA16DBCS shift Japanese double byte EBCDIC M 939 JA16DBCS shift Japanese multi byte EBCDIC M 5035 gt JA16DBCS shift Japanese multi byte EBCDIC MBC 939 1027 300 Japanese multi byte EBCDIC MBC 5035 1027 4396 Japanese multi byte EBCDIC S 290 gt JA16EBCDIC930 Japanese single byte EBCDIC D 300 gt JA16EBCDIC930 shift Japanese double byte EBCDIC D 4396 gt JA16EBCDIC930 shift Japanese double byte EBCDIC M 930 JA16EBCDIC930 shift Japanese multi byte EBCDIC M 5026 gt JA16EBCDIC930 shift Japanese multi byte EBCDIC MBC 930 290 300 Japanese multi byte EBCDIC MBC 5026 290 4396 Japanese multi byte EBCDIC Refer to the following list to check the character set of an existing database u For DB2 OS390 Ask your system administrator There is no single command you use u For DB2 400 Issue the command DSPSYSVAL SYSVAL QCCSID u For DB2 UDB Ask your system administrator There is no single command you use u For DB2 VM Issue the statement ID This shows you the default CCSIDs used at startup D 5 Multi Byte and Double Byte Support in the Gateway To enable the gateway to properly handle
219. lect data from an object INSERT_PRIV Permission to insert data into an object DELETE_PRIV Permission to delete data from an object UPDATE_PRIV Permission to update an object REFERENCES_PRIV N A ALTER_PRIV Permission to alter an object INDEX_PRIV Permission to create or drop an index on an object CREATED Timestamp for the grant A 2 18 USER_CATALOG Tables views synonyms and sequences owned by the use column name description TABLE_NAME Name of the object TABLE_TYPE Type of the object A 2 19 USER_COL_COMMENTS Comments on columns of user s tables and views A 10 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dictionary View Tables column name description TABLE_NAME Name of the object COLUMN NAM Name of the coloumn E COMMENTS Comments on the column A 2 20 USER_CONSTRAINTS Constraint definitions on user s tables column name description OWNER Owner of the constraint definition CONSTRAINT_NAME Name associated with the constraint definition CONSTRAINT_TYPE Type of the constraint definition TABLE_NAME Name associated with the table with constraint definition SEARCH_CONDITION Text of the search condition for table check R_OWNER Owner of table used in referential constraint E R CONSTRAINT NAMI Name of the unigue constraint definition for referenced
220. m that calls a DB2 stored procedure DB2 a row into a DB2 table LFE K K k kk k k k dek k k k k ke kkk k k k k k e k k deke ke ke k k kk k kk k kk k k k k k k ke k k kk k k k k kk k kk kk kkk kkk k kk kk kk This sample ProC program calls DB2 stored procedure DB2INS to sela insert values into the DB2 user table SCOTT DEPT This calling MJ program uses embedded PL SQL to call the stored procedure A AA kkk kkk k kkk kk kkk kkk kk k kk k kk kk k k k k kk k kkk kk kkk kkk kk k kkk kkk kkk kkk kkk kk kkk kkk kkk J include lt stdio h gt EXEC SQL BEGIN DECLARE SECTION VARCHAR username 20 VARCHAR password 20 int dept_no char dept_name 14 VARCHAR location 13 int code char buf 11 int X EXEC SQL END DECLARE SECTION EXEC SQL INCLUDE SQLCA main tkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkikkkkkkkkkkkkkkkkkkkkk Setup Oracle userid and password ttkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkikkkkkkkkkkkkkkkkkkkkk strcpy username arr SCOTT copy the username username len strlen username arr strcpy password arr TIGER copy the password password len strlen password arr G 2 Oracle Transparent Gateway for DRDA Installation and User s Guide NS to insert ORAIND EXEC SQL WHENEVER SQLERROR GOTO sqlerror RRRRRRR EERE RRR EER EER EKER ER ERE ER ER ERE EEK EERE EE ERR ER ERE RRA RRA RARA RARA RA RARA RAS
221. mmends using independent LUs for the Oracle Transparent Gateway for IBM DRDA because they support multiple parallel sessions or conversations This means that multiple Oracle client applications can be active simultaneously with the same DRDA Server through the independent LU In contrast to independent LUs dependent LUs support only a single active session The Control Point for the Node CP queues each additional conversation request from the gateway behind an already active conversation In other words conversations are single threaded for dependent LUs The operational impact of dependent LUs is that the first client application can initiate a conversation through the gateway with the DRDA Server but while that session is active which could be seconds minutes or hours depending on how the client application and transaction are designed any other client application initiating a session with the same DRDA Server appears to hang as it waits behind the previous session If a production application really uses only a single conversation at any one time then there should be no problem However at some point you might require additional concurrent conversations for testing or for other application development Having more than one conversation requires that additional dependent LUs be defined on the remote host Additional configuration entries will need to be added to SNAPlus2 Additional Side Information Profiles should be defined to use the
222. n only queries SELECT statements are allowed by the gateway The capabilities that control whether updates are allowed by the Using the Oracle Transparent Gateway for DRDA 12 5 Replicating in a Heterogeneous Environment gateway are disabled These capabilities include INSERT UPDATE DELETE and stored procedure support pass through SQL and DB2 stored procedures Statements attempting to modify records on the DRDA Server are rejected Oracle recommends that you should not routinely switch between settings of the DRDA_READ_ONLY parameter If you need both the update and DRDA_READ_ONLY functionality then you should create two separate instances of the gateway with different read only settings 12 7 Replicating in a Heterogeneous Environment Oracle Transparent Gateway for DRDA provides a number of options for replicating Oracle and non Oracle data throughout the enterprise Oracle Database 10g Triggers When updates are made to Oracle Database synchronous copies of Oracle and non Oracle data can be maintained automatically by using Oracle Database 10 triggers Oracle Snapshots Oracle Transparent Gateway for DRDA can use the Oracle snapshot feature to automatically replicate non Oracle data into Oracle Database The complete refresh capability of Oracle snapshot can be used to propagate a complete copy or a subset of the non Oracle data into Oracle Database at user defined inter
223. nLink SNA Peer to Peer has been removed SunLink SNA Peer to Peer has been desupported by the vendor Gateway Password Encryption Tool The Gateway Password Encryption tool g4drpwd has been replaced by a generic feature which is now part of Heterogenous Services Refer to Chapter 14 Security Considerations 2 3 Product Migration Refer to Chapter 15 Migration and Coexistence with Existing Gateways for information on migrating product configurations from previous releases for additional changes or requirements Release Information 2 1 Bugs Fixed in Release 10 2 0 2 4 Bugs Fixed in Release 10 2 0 The following bugs are fixed in this release 4013463 GARBAGES CONTAINED IN ERROR MESSAGE FROM TG4DRDA 3882675 TG4DRDA SELECT FOR UPDATE ERROR WITH G4DRSRVD 3650803 MEMORY LEAK IN G4DRSRV DOING SELECT STATEMENT 3640384 ORA 28500 ON SELECT FOR UPDATE FROM TG4DRDA 3610131 INDEX STATS MAY NOT BE QUERIED CORRECTLY 3514233 SETTING DRDA_OPTIMIZE_QUERY TRUE DOES NOT GENERATE TABLE STATS 3429017 LINKING ERROR FOR G4DRSRV WHEN USING REDHAT AS V3 3421215 IU GUIDE DIDN T SAY HOW TO CONFIG DRDA_CONNECT_PARM IN LINUX 3287626 ENGLISH NAME OF TAIWAN DOESN T SEEM TO BE APPROPRIATE 3143686 QA 10G CAN NOT SELECT FROM DATA DICTIONARY TABLES 4218317 COUNT COLNAME NOT TRANSLATED TO COUNT 4260112 ORA 1001 WITHOUT THE DETAIL RETURNS FROM TG4DRDA 4065600 GARBAGES CONTAINED IN ORA 1 ERROR MESSAGE FROM TG4DRDA
224. nce 14 3 1 Link Accessibility The database link should be accessible to a given user A public database link can be used by any user ID A private database link can be used only by the user who created it The server makes no distinction regarding the type of use such as read only versus update or write or accessibility of remote objects The DRDA database which is accessed is responsible for these distinctions 14 3 2 Links and CONNECT Clauses The CONNECT clause is another security related attribute of a database link You can use the CONNECT clause to specify an explicit user ID and password which can differ from the user s Oracle Database user ID and password This CONNECT user ID and password combination is sent to the gateway when the database link connection is first opened Depending on gateway options the gateway might send that user ID and password to the DRDA Server for validation If a database link is created without a CONNECT clause then the user s Oracle Database user ID and password are sent to the gateway when the connection is opened If the user logs into the Oracle integrating server with operating system authentication then the gateway does not receive any user ID or password from the Oracle Integrating Server In this case user ID mapping facilities at the DRDA Server can be used to make such a connection possible if all users on the same host can use the same DRDA database user ID 14 2 Oracle Transpar
225. nd complete information Company growth and diversification often mean functioning with a collage of applications and geographically scattered data that may be using incompatible networks platforms and storage formats Diverse application standards and storage formats can make integration of information difficult Oracle offers integration technologies to overcome these technical barriers Oracle Open Gateways simplify complex systems and remove obstacles to information providing your company the opportunity to focus on business Introduction 1 1 Release 10g Gateways Protection of Current Investment Oracle Transparent Gateway for DRDA gives your company the ability to develop its information systems without forfeiting its investments in current data and applications The gateway gives you access to your Oracle data and DB2 data witha single set of applications while you continue to use existing IBM applications to access your DB2 data You can also use more productive database tools and move to a distributed database technology without giving up access to your current data If you choose to migrate to Oracle Database technology then the gateway enables you to control the pace of your migration As you transfer applications from your previous technology to the Oracle Database you can use the gateway to move the DB2 data into Oracle Databases 1 2 Release 10g Gateways The Oracle Database 10g provides the foundation for the next gener
226. ng the xsnapadmin program This tool is an X Windows application which provides a graphical interface so that you can view and modify the current SNAPlus2 configuration and the current running state of Configuring SNAPlus2 8 1 Creating SNAPlus2 Profiles for the Gateway the host SNA node Refer to the HP UX SNAPlus2 administrators guide for more information on using xsnapadmin 8 4 Creating SNAPlus2 Profiles for the Gateway The Oracle Transparent Gateway for IBM DRDA requires a stored set of definitions called Side Information Profiles to support connections between the gateway and DRDA Servers Each profile consists of a profile name and a profile type which is a set of fields describing the profile The fields in a given profile type are generally a mixture of operating parameter values and names of other SNA profiles relevant to the profile Each functional part of APPC such as the Mode Remote Transaction Program name and Logical Unit LU is described by a distinct profile type 8 5 Independent Versus Dependent LUs The gateway configuration can accommodate either independent LUs or dependent LUs If you choose to use dependent LUs or are restricted to using dependent LUs the gateway will function properly if a dependent LU is correctly defined then you will need to make no alterations to the configuration of the Oracle Transparent Gateway for IBM DRDA nor should any changes be needed to the DRDA Server However Oracle reco
227. ngle byte characters where possible C 4 16 DRDA ISOLATION LEVEL Default value CHG for DB2 400 CS for DB2 05390 DB2 UDB DB2 VM Range of values CHGICSIRR ALL NC Syntax DRDA_ISOLATION_LEVEL CHG CS RR ALL NC DRDA_ISOLATION_LEVEL specifies the isolation level that is defined to the package when it is created All SOL statements that are sent to the remote DRDA database are executed with this isolation level Isolation level seriously affects performance of applications Use caution when specifying an isolation level other than the default For information on isolation levels refer to your IBM database manuals The following table lists the isolation levels and their descriptions The levels are specified in ascending order of control with CHG having the least reliable cursor stability and RR having the most Note that higher stability uses more resources on the server and can lock those resources for extended periods Table C 1 Isolation Levels and Their Descriptions Level Description CHG Change default for DB2 400 cs Cursor Stability default for DB2 UDB DB2 0S390 and DB2 VM DRDA Specific Parameters C 5 Gateway Initialization File Parameters Table C 1 Cont Isolation Levels and Their Descriptions Level Description RR Repeatable Read ALL ALL NC No Commit Note Any change to this parameter requires you to rebind C 4
228. nly an example Set it to the value you want Refer to the Advanced Security Administrator s Guide for more information Step 2 Set Advanced Security Encryption Parameters for Oracle Server Set the advanced security encryption parameters for the Oracle integrating server Edit the Oracle Net configuration file on the Oracle integrating server system to add the following parameters 10 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Testing Advanced Security Encryptions SOLNET CRYPTO_CHECKSUM_CLIENT REQUIRED SQLNET ENCRYPTION CLIENT REQUIRED SOLNET CRYPTO CHECKSUM TYPES CLIENT SHA1 SOLNET ENCRYPTION TYPES CLIENT DES40 RC4_40 SOLNET CRYPTO SEED abcdefg123456789 LIJ T The value shown for SQLNET CRYPTO_SEED is only an example 10 7 Testing Advanced Security Encryptions After completing Steps 1 and 2 to set up Advanced Security encryption you are ready to test the operation of the Advanced Security encryption by using the following steps 1 Step 1 Connect Gateway and Oracle Integrating Server 2 Step 2 Reset Configuration Parameters on the Gateway Step 1 Connect Gateway and Oracle Integrating Server Use SQL Plus to logon to the Oracle integrating server Access the gateway through a database link You should receive the following error ORA 12660 Encryption or crypto checksumming Step 2 Reset Configuration Parameters on the Gateway Change the following Ad
229. non Oracle system returned the message TG4DRDA v10 2 0 1 0 grc 0 drc 30020 839C 0000 errp GDJMRCM sqlcode 805 sqlstate 51002 errd FFFFFF9C 0 0 FFFFFFFF 0 0 errmc 124c 16 2 Mapped Errors Some SQL errors are returned from the DRDA Server database and are translated to an Oracle error code This is needed when the Oracle instance or gateway provides special handling of an error condition The following table lists the mapped SQLstate error numbers descriptions and their corresponding Oracle error codes Table 16 1 Mapped sqlstate Errors Description sqlstate error Oracle error No rows selected 02000 0 Unique index constraint violated 23505 ORA 00001 Object does not exist 52004 or ORA 00942 42704 Object name too long more than 18 characters and 54003 or ORA 00942 therefore object does not exist 42622 Insufficient privileges 42501 ORA 01031 Invalid CCSID unimplemented character set conversion 22522 ORA 01460 Invalid username password logon denied N A ORA 01017 Divide by zero error 01519 or ORA 01476 01564 Error Messages Diagnosis and Reporting 16 3 Gateway Error Codes The following is an example of a translated object does not exist error ORA 00942 table or view does not exist TG4DRDA v10 2 0 1 0 grc 0 drc 942 839C 0001 errp DSNXEDST sqlcode 204 sqlstate 52004 errd 32 0 0 FFFFFFFF 0 0 errmc AJONES CXDCX 16 3 Gateway Error Codes Listed belo
230. nstaller refer to the installation process followed earlier in this chapter in Installing the Gateway from CD ROM on page 4 2 and repeat the following steps steps 1 3 4 and 6 of the installation startup process a Step 1 Log on to the host m Step 3 Set the ORACLE HOME environment variable a Step 4 Mount the Installation Media a Step 6 Start the Oracle Universal Installer When the Welcome panel appears click the Deinstall Products button In the list of installed products select the gateway product and any other products you wish to remove and then click Remove Installing the Gateway 4 5 Removing the Gateway 4 6 Oracle Transparent Gateway for DRDA Installation and User s Guide 5 Configuring the DRDA Server The steps for configuring your remote DRDA Server cover the following DRDA Servers u DB2 0S390 u DB2 400 u DB2 UDB Universal Database u DB2 VM Configuring a DRDA database to enable access by the gateway requires actions on the DRDA database and on certain components of the host operating system Although no Oracle software is installed on the host system access to and some knowledge of the host system and DRDA database are required during the configuration Refer to the vendor documentation for complete information about your host system and DRDA database 5 1 Checklists for Configuring the DRDA Server This section provides the checklists for configuring the DRDA Server DB2 0S390
231. nt it without having to move the data between machines and risk unsynchronized and inconsistent data Avoiding massive data replication can also reduce aggregate disk storage requirements over all your systems However if your system design requires moving data among the machines in a network SQL Plus and the gateway can simplify the data transfer With a single SQL Plus command you can move entire sets of data from one node of the network to another and from one database to another You can pass commands and statements specific to your DRDA database through the gateway to be executed by the DRDA database For example you can pass DB2 05390 commands through the gateway for DB2 to execute You can also execute stored procedures defined in non Oracle databases Application Development and End User Tools Through the gateway Oracle extends the range of application development and end user tools you can use to access your IBM databases These tools increase application development and user productivity by reducing prototype development and maintenance time Current Oracle Database users do not have to learn a new set of tools to access data stored in DRDA databases Instead they can access Oracle Database and DRDA data with a single set of tools With the gateway and the application development tools available from Oracle you can develop a single set of applications to access Oracle Database and DRDA data Users can use the decision support t
232. nux S 390 Any processor that can run Linux S 390 For AIX Based Systems IBM pSeries u For HP UX HP 9000 Series HP UX that can run the required version of HP UX u For Solaris A Solaris Operating System SPARC 64 bit that can run the required version of Solaris with 64 bit architecture Memory For most installations a minimum of 256 MB of real memory is recommended for the first user to support the Oracle Transparent Gateway for DRDA The total real memory requirement for each concurrent use of the gateway depends on the following factors u Number of concurrent APPC connections open by each user System Requirements 3 1 Software Requirements u Number of concurrent TCP IP connections open by each user u Number of data items being transferred between the gateway and the remote transaction program Additional factors such as configured network buffer size Network Attachment The hardware requires any network attachment that is supported by either SNA server networking for SNA communication or TCP IP Networking Facility for TCP IP communication The network attachment for SNA is typically a Token Ring or SDLC Coaxial attachment If you want concurrent SNA access then the hardware must support independent LUs The network attachment for TCP IP is typically an Ethernet attachment CD ROM Drive An internal or external CD ROM drive is required for installation Disk Space Disk space required for installation are u
233. o install Oracle Net so that the gateway and Oracle Database 10g server can communicate m DRDA Server The DRDA Server must be a DRDA Server database on a system accessible to the host and using either the SNA or TCP IP protocols Multiple Oracle Database 10g servers can access the same gateway A single host gateway installation can be configured to access more than one DRDA Server Figure 1 1 illustrates the gateway architecture Figure 1 1 The Gateway Architecture Oracle Net SNA local Oracle Client V connection Transparent DRDA Gateway for 4 gt Server Oracle Integrating Server Oracle E Transparent DRDA Gateway for DRDA Server 1 8 Oracle Transparent Gateway for DRDA Installation and User s Guide How the Gateway Works 1 6 Implementation When the gateway is installed on your host it has some of the same components as an Oracle Database instance on your host The gateway has the following components A base file directory similar to the one associated with an Oracle instances ORACLE_HOME environment variable A gateway system identifier SID comparable to an Oracle instances ORACLE SID Oracle Net to support communication between the Oracle integrating server and the Oracle Transparent Gateway for DRDA The gateway does not have a Control redo log or database files u The full set of subdirectories and ancillary files that are associated with an installed Or
234. olaris 6 2 SNAPlus2 product on HP UX 8 2 SNAP IX product on Solaris 6 2 SNAPlus2 product on HP UX 8 2 independent vs dependent SNAP IX product on Solaris 6 2 SNAPlus2 product on HP UX 8 2 local LU alias CPI C destination on HP UX 8 10 CPI C destination on Solaris 6 11 create Local LU names on Solaris 6 8 Ethernet parameters on HP UX 8 8 local names creating on HP UX 8 8 creating on Solaris 6 8 names 6 11 8 10 partner creating 6 9 8 8 SNAP IX profiles 6 2 SNAPlus2 profiles 8 2 traffic type in configuring SNAplus2 6 7 8 7 LU name 14 3 LU6 2 local LU profile 7 2 profile types 7 2 side information profile 7 3 SNA APPC IBM Communication Server product on AIX 7 1 SNAP IX product on Solaris 6 1 SNAPlus2 product on HP UX 8 1 MAC address in SNA configuration Solaris 6 7 in SNAplus2 configuration HP UX 8 7 mapped sqlstate errors 16 3 mapping user IDs AVS 14 4 known restrictions 2 4 migrating the gateway instance 15 4 migration problems 15 2 MINUS set operator SQL Set Clauses 13 20 SQL set operators and clauses 13 20 Mobile Agents 1 5 mode name HP UX 8 10 name Solaris 6 10 profiles creating on HP UX 8 9 profiles creating on Solaris 6 9 Mode Profile SNA Server profile on AIX 7 2 multi byte support D 8 MVS VTAM configuring DB2 0S390 5 2 N National Language Support NLS overview D 1 Native Semantics gateway architecture 1 12 parameters SQL Set Clauses 13 20 w
235. onary View Tables column name description DEGREE Number of threads per instance for scanning the index INSTANCES Number of instances across which the index is to be scanned PARTITIONED Whether the index is partitioned TEMPORARY Whether the index is on a temporary table GENERATED Whether the name of the index is system generated SECONDARY N A BUFFER_POOL Whether the index is a secondary object USER_STATS N A DURATION N A PCT_DIRECT_ACCESS N A ITYP_OWNER N A ITYP_NAME N A PARAMETERS N A GLOBAL_STATS N A DOMIDX_STATUS N A DOMIDX_OPSTATUS N A FUNCIDX_STATUS N A JOIN_INDEX N A IOT REDUNDANT PKEY ELIM N A A 2 23 USER OBJECTS Objects owned by the user column name description OBJECT NAME Name of the object SUBOBJECT NAME Name of the subobject OBJECT ID Object number of the object DATA OBJECT ID Dictionary object number of the segment that contains the object OBJECT TYPE Type of object CREATED N A LAST DDL TIME N A TIMESTAMP N A STATUS State of the object VALID TEMPORARY Whether the object is temporary GENERATED Was the name of this object system generated SECONDARY N A Oracle DB2 Data Dictionary Views A 13 Data Dictionary View Tables
236. ools available from Oracle to access Oracle Database and DRDA data These tools can run on remote machines connected through Oracle Net to the Oracle integrating server When designing applications keep in mind that the gateway is designed for retrieval and relatively light transaction loads The gateway is not currently designed to be a heavy transaction processing system Password Encryption Utility The 10 2 release of the gateway includes a utility to support encryption of plain text passwords in the Gateway Initialization File Refer to Chapter 14 Security Considerations for details Introduction 1 13 Features Support for DB2 0S390 V6 V7 and V8 Stored Procedures The 10 2 release of the gateway supports the native stored procedure catalogs in DB2 V6 V7 and V8 SYSIBM SYSROUTINES and SYSIBM SYSPARMS Codepage Map Facility This release of the gateway supports external mapping of IBM CCSIDs to Oracle Character Sets Refer to Gateway Codepage Map Facility on page D 6 in Appendix D National Language Support IBM DB2 Universal Database Support The 10 2 release supports IBM DB2 Universal Database IBM DB2 Version 5 1 ASCII Tables IBM DB2 Version 5 1 supports ASCII and EBCDIC character sets The character set selection is defined during table creation The Oracle Transparent gateway for DRDA supports access to EBCDIC tables and ASCII tables Refer to Appendix D National Language Support
237. or the gateway refer to the instructions for Configuring Oracle Net on page 10 3 ipc ora DESCRIPTION ADDRESS PROTOCOL IPC KEY ORAIPC CONNECT_DATA SID ORA102 ipc gtw DESCRIPTION ADDRESS PROTOCOL IPC KEY ORAIPC CONNECT DATA SID drdahoal HS B 3 Sample Oracle Net listener ora File For information on modifying your listener ora file for the gateway refer to the instructions for Configuring Oracle Net on page 10 3 Sample listener ora file for the Transparent gateway for IBM DRDA Version Date Jan 01 2002 Filename Listener ora LISTENER ADDRESS_LIST ADDRESS PROTOCOL IPC KEY ORAIPC SID_LIST_LISTENER SID LIST SID DESC lt SID NAME drdahoal ORACLE HOMEz oracle tg4ddrda 10 2 0 PROGRAM g4drsrv STARTUP WAIT TIME LISTENER lt 0 CONNECT TIMEOUT LISTENER 10 TRACE LEVEL LISTENER lt OFF This sample listener ora file isolated at the SORACLE_HOME network admin directory If the listener uses the Oracle Net TCP IP adapter instead of the IPC adapter then replace the following lines under the LISTENER keyword ADDRESS PROTOCOL IPC B 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Sample Oracle Net listener ora File KEY ORAIPC with ADDR ESS PROTOCOL TCP HOST your_IP_node_name PORT your_port_number Sample Files B 3 Sample Oracle Net listener ora File B 4 Orac
238. ote databases with the parameter OPEN_LINKS This parameter controls the number of remote connections that any single user process can concurrently use with a single SQL statement Refer to Oracle Database Reference for additional information about limiting the number of active database links 12 2 Accessing the Gateway To access the gateway complete the following steps on the Oracle integrating server 1 Step 1 Login to the Oracle Integrating Server 2 Step 2 Creating a database Link to the DRDA Database 3 Step3 Retrieve data from the DRDA Database Step 1 Login to the Oracle Integrating Server Log in to the Oracle Integrating Server to access the gateway Step 2 Creating a database Link to the DRDA Database For example use CREATE PUBLIC DATABASE LINK DRDA CONNECT TO ORADRDA IDENTIFIED BY oracle pw USING tns name entry Step 3 Retrieve data from the DRDA Database This guery fetches the TABLE file in the library SECURE using the name ORACLE as the DRDA Server user profile The ORACLE user profile must have the appropriate privileges on the DRDA Server to access the SECURE TABLE files SELECT FROM SECURE TABLEEDRDA The following is an example of the error messages that are displayed if insufficicent privileges are displayed ORA 1031 insufficient privileges TG4DRDA V10 2 0 1 0 grc 0 drc 777 83TC 0000 errp ARIXO sqlcode 551 sqlstate 42501 errd FFFFFF9C 0 0 0 0 0 errmc USER SELECT SECURE TABLE
239. ped error codes 16 3 specific gateway error codes 16 4 tokens 16 2 translation 13 21 while binding the gateway package 11 4 with Native Semantics 13 18 errp mapped error example 16 4 EXCEPT set operator SQL Set Clauses 13 20 execute authority 14 4 EXECUTE command 1 6 EXECUTE privilege DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 exits gateway local date 13 24 EXPLAIN PLAN command 16 5 EXPLAIN_PLAN table 1 12 export encryption algorithms 10 4 F FDS_CLASS parameter C 9 FDS_CLASS_VERSION parameter C 9 FDS_INSTANCE parameter C 9 features of the gateway application development and end user tools 1 13 application portability 1 12 columns supported in a result set 1 12 distributed applications supported 1 13 EXPLAIN_PLAN improvement 1 12 fetch reblocking 1 11 heterogeneous database integration 1 12 Index 8 heterogeneous services architecture 1 11 large base of data access 1 12 main topic 1 10 minimum impact on existing systems 1 12 Native Semantics 1 12 Oracle Database passthrough supported 1 11 Oracle snapshots 12 6 performance enhancements 1 11 remote data access 1 12 retrieving result sets through passthrough 1 11 support for TCP IP 1 12 fetch array size with HS_FDS_FETCH_ROWS C 10 fetch reblocking controlled by two Heterogeneous Services initialization parameters 1 11 supported by Oracle Database server 13 2 fetched date C 11 fields errmc lists any error tokens 16 2 errp indicat
240. ported The SQL Plus COPY command must be used Refer to Chapter 12 Using the Oracle Transparent Gateway for DRDA for more information The following are the considerations and limitations Stored Procedure and User Defined Function Support The gateway supports execution of stored procedures and user defined functions through the following DRDA Servers DB2 0S390 V4 1 or later DB2 400 V3 1 or later DB2 UDB V7 1 or later 2 6 1 DB2 Considerations The following considertaions are exist in the 10g release DD Basic Tables and Views The owner of DD basic tables and views is OTGDB2 This cannot be changed SUBSTR Function Post Processed The SUBSTR function can be used with the Oracle Database in ways that are not compatible with a DRDA Server database such as DB2 05390 Therefore the SUBSTR function is post processed However it is possible to allow the server to process it Release Information 2 3 Known Restrictions natively using the Native Semantics feature Refer to Chapter 13 Developing Applications for details AVS Mapping User IDs DB2 VM APPC VTAM Support AVS has problems mapping user IDs that are sent using lowercase letters or special characters Contact your IBM representative for additional information about this problem Support for DRDA Server Character Sets Support for character sets used by a DRDA Server is configurable through the gateways Codepage Map Facility Refer to Appendix
241. pter provides information about error messages and error codes This data is specific to the 10 2 release of the Oracle Transparent Gateway for DRDA This chapter contains the following sections u Interpreting Gateway Error Messages u Mapped Errors m Gateway Error Codes u SQL Tracing and the Gateway 16 1 Interpreting Gateway Error Messages The gateway architecture consists of different components Any component may detect and report an error condition while processing SQL statements that refer to one or more DRDA database tables This means that errors can be complex involving error codes and supporting data from multiple components In all cases however the application ultimately receives a single error code or a return code As most gateway messages exceed the 70 character message area in the Oracle SQL Communications Area SQLCA the programmatic interfaces and Oracle Call Interfaces that you use to access data through the gateway should use SQLGLM or OERHMS to view the entire text of messages Refer to the programmer s guide to the Oracle precompilers for additional information about SQLGLM and refer to the Oracle C Call Interface Programmer s Guide for additional information about OERHMS The error messages listed apply to both TCP IP and SNA networking communications products on the gateway Errors encountered when using the gateway can originate from many sources as follows m Errors detected by the Oracle integrating se
242. r This is sometimes necessary depending upon the character set of the DRDA database and Oracle Database If the Oracle database is based on EBCDIC and the DRDA database is based on ASCII then a pad size of 2 may be needed C 4 14 DRDA_GRAPHIC_LIT_CHECK Default value FALSE Range of values TRUE FALSE Syntax DRDA_GRAPHIC_LIT_CHECK TRUE FALSE DRDA GRAPHIC LIT CHECK directs the gateway to evaluate string literals within INSERT SQL statements in order to determine if they need to be converted to double byte format for insertion into a Graphic column at the DRDA Server database This is done by querying the column attributes of the table in the SQL statement to determine if a string literal is being applied to a column with a Graphic data type If the table column is Graphic and if this parameter is TRUE then the gateway will rewrite the SQL statement with the literal converted to double byte format Existing double byte characters in the string will be preserved and all single byte characters will be converted to double byte characters C 4 15 DRDA_GRAPHIC_TO_MBCS Default value FALSE Range of values TRUE FALSE Syntax DRDA GRAPHIC TO MBCS 4 TRUE FALSE DRDA GRAPHIC TO MBCS directs the gateway to convert graphic data that has been fetched from the DRDA Server into Oracle multi byte data translating double byte characters into si
243. r ID and password are sent If no user ID and password are sent and if the DRDA Server is not configured to assign a default user ID then the connection fails In general SECURITY PROGRAM tells the DRDA Server to authenticate the user ID password combination using whatever authentication mechanisms are available For example if DB2 05390 is the DRDA Server then RACF can be used This is not always the case however because each of the DRDA Servers can be configured to process inbound user IDs in other ways 7 3 2 SNA Security Option SECURITY SAME If DRDA_SECURITY_TYPE SAME is specified then the gateway allocates the conversation with SNA option SECURITY SAME and the following information is sent to the DRDA Server a If the database link has explicit CONNECT information then the specified user ID is sent 7 4 Oracle Transparent Gateway for DRDA Installation and User s Guide SNA Conversation Security u If the database link has no CONNECT clause and if the application has logged into the Oracle integrating server with an explicit user ID and password then the Oracle user ID is sent u Ifthe application logs into the Oracle integrating server with operating system authentication and if the database link lacks explicit CONNECT information then no user ID is sent If no user ID is sent and if the DRDA Server is not configured to assign a default user ID then the connection fails For t
244. r only if an application needs more than 100 open concurrent cursors Note Any change to this parameter requires you to rebind the package C 4 25 DRDA_READ_ONLY Default value FALSE Range of values TRUE FALSE Syntax DRDA READ ONLY 4 TRUE FALSE DRDA READ ONLY specifies whether the gateway runs in a read only transaction mode In this mode SQL statements that modify data are not permitted C 4 26 DRDA RECOVERY PASSWORD Default value none Range of values any valid password Syntax DRDA RECOVERY PASSWORD passwd DRDA RECOVERY PASSWORD is used with the DRDA RECOVERY USERID The recovery user connects to the IBM database if a distributed transaction is in doubt For more information refer to Two Phase Commit Processing on page 12 5 Also refer to Chapter 14 for information about security and encrypting passwords C 4 27 DRDA_RECOVERY_USERID Default value ORARECOV Range of values Any valid user ID Syntax DRDA_RECOVERY_USERID userid DRDA_RECOVERY_USERID specifies the user ID that is used by the gateway if a distributed transaction becomes in doubt This user ID must have execute privileges on the package and must be defined to the IBM database If a distributed transaction becomes in doubt then the Oracle integrating server determines the status of the transaction by connecting to the IBM database using the DRDA_RECOVERY_USERID If
245. r requires you to set parameters that are unique to your system in order to properly configure the gateway Refer to Appendix E Configuration Worksheet for a worksheet listing all of the installation parameters that you will need to know in order to complete the configuration process Ask your network administrator to provide these parameters before you begin You will also need to confirm that all hardware and software requirements have been met Refer to Chapter 3 System Requirements to verify these requirements Installing the Gateway 4 1 Checklist for Gateway Installation 4 3 Checklist for Gateway Installation Use the following checklist for installing the gateway Step 1 Log on to the host m Step 2 Create the Product Installation Directory m Step 3 Set the ORACLE HOME environment variable a Step 4 Mount the Installation Media m Step 5 Set the DISPLAY Variable m Step 6 Start the Oracle Universal Installer m Step 7 Step through the Oracle Universal Installer Step 8 Verify installation success 4 4 Installation Overview The primary installation tasks assume that you configure the gateway with a single Oracle integrating server and a single DRDA database The steps for expanding the configuration to multiple integrating servers and multiple DRDA databases are described in Chapter 11 Configuring the Gateway For general information about installing Oracle products and how to use the Oracle Universal Installer
246. r the text of the prompt SQL gt in your response Storage Measurements Storage measurements use the following abbreviations u KB for kilobyte which equals 1 024 bytes u MB for megabyte which equals 1 048 576 bytes u GB for gigabyte which equals 1 073 741 824 bytes XV xvi 1 Introduction The Oracle Transparent Gateway for Distributed Relational Database Architecture DRDA enables you to u Integrate heterogeneous database management systems so that they appear as a single homogeneous database system u Read and write data from Oracle applications to data in DB2 0S390 DB2 400 DB2 Universal Database DB2 VM and IBM SOL DS on VM databases in addition to any Oracle Database server data This chapter provides information about the architecture uses and features of the Oracle Transparent Gateway for DRDA This chapter contains the following sections m Introduction to the Oracle Transparent Gateway u Release 10g Gateways m Gateway Capabilities u Terms m Architecture u Implementation u How the Gateway Works a Oracle Tools and the Gateway a Features 1 1 Introduction to the Oracle Transparent Gateway In todays global economy information is the most valuable resource o a company Whether you need to analyze new markets tailor your products to meet local demands increase your ability to handle complex customer information or streamline operations your company requires instant access to current a
247. rally the system with the strictest security requirements dictates and rules the system gateway security involves two groups m Users and applications that are permitted access to a given gateway instance and DRDA database server m Server database objects that users and applications are able to query and update You can control access in the gateway architecture at several points Control over database object access is provided by each DRDA database server with GRANTS and related native authorization mechanisms based on user ID When the gateway is involved in a SQL request security mechanisms are in effect for each DRDA system component encountered by the gateway The first system component encountered is the application tool or 3GL program The last system component encountered is the DRDA database 14 2 Authenticating Application Logons An application must connect to an Oracle integrating server before using the gateway The type of logon authentication that you use determines the resulting Oracle user ID and can affect gateway operation There are two basic types of authentication m Oracle authentication With Oracle authentication each Oracle user ID has a password known to Oracle Database When an application connects to the server Security Considerations 14 1 Defining and Controlling Database Links it supplies a user ID and password Oracle Database confirms that the user ID exists and that the password matches the one
248. ransparency to the user and to the application programmer Foreign SQL constructs can be categorized into four areas u Compatible u Translated u Compensated m Native semantics 13 5 1 Compatible SQL Functions Oracle Integrating Server automatically forwards compatible SQL functions to the DRDA database Where SQL constructs with the same syntax and meaning are on both Oracle Database and the DRDA database These SQL constructs are forwarded unmodified All of the compatible functions are column functions Functions that are not compatible are either translated to an equivalent DRDA SQL function or are compensated post processed by Oracle Database after the data is returned from the DRDA database 13 5 2 Translated SQL Functions Translated functions have the same meaning but different names between the Oracle Integrating Server and the DRDA database But all applications must use the Oracle function name These SQL constructs that are supported with different syntax different function names by the DRDA database are automatically translated by the Oracle Database and then forwarded to the DRDA database Oracle Integrating Server changes the function name before sending it to the DRDA database in a manner that is transparent to your application 13 5 3 Compensated SQL Functions Some advanced SQL constructs that are supported by Oracle Database may not be supported in the same manner if at all by the DRDA database Compensated fun
249. rating system Step 3 Define the recovery user ID During gateway configuration the recovery user ID and password are specified in the Gateway Initialization File using the DRDA_RECOVERY_USERID and DRDA_RECOVERY_PASSWORD parameters If a distributed transaction fails then the recovery process connects to the re mote database using the user ID and password defined in these parameters This user ID must have execute privileges on the package and must be defined to the DRDA database If the user ID is not specified in DRDA_RECOVER_USERID then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt Determine the user ID and password you will use for recovery Step 4 Determine DRDA location name for DB2 UDB instance The DRDA location name is required as a gateway parameter To determine the location name issue the following SQL query from a DB2 CLI session SELECT CURRENT SERVER FROM any table where any table isa valid table with one or more rows If the value returned by this query is blank or null then the DRDA location name has not been established Contact your system administrator to set a location name for the instance 5 5 DB2 VM Experience with VM AVS and DB2 VM is required to perform the following steps a Step 1 Configure the Communications Server u Step 2 Define the user ID that owns the package Configuring the DRDA Server 5 5
250. re single threaded for dependent LUs The operational impact of dependent LUs is that the first client application can initiate a conversation through the gateway with the DRDA Server but while that session is active which could be seconds minutes or hours depending on how the client application and transaction are designed any other client application initiating a session with the same DRDA Server appears to hang as it waits behind the previous session If a production application really uses only a single conversation at any one time then there should be no problem However at some point you might require additional concurrent conversations for testing or for other application development Having more than one conversation requires that additional dependent LUs be defined on the remote host Additional configuration entries will need to be added to SNAP IX Additional Side Information Profiles should be defined to use the new dependent LUs Oracle Transparent Gateway for IBM DRDA instances should be created and configured to use these new Side Information Profiles 6 6 Creating SNA Definitions for the Gateway SNAP IX definitions are stored in the following two files located in the directory etc opt sna u sna_node cfg SNA node definitions u sna_domn cfg SNA domain definitions These files are created and maintained with the xsnaadmin tool Maintenance of SNA definitions is normally done by a user with administrative authority Th
251. re performed from within xsnapadmin All configuration is done using the various pull down menus and panels in xsnapadmin The following configuration descriptions follow the samples provided Please tailor the various SNA values for your local host and SNA network 8 6 3 Invoking xsnapadmin The DISPLAY environmental variable must be set appropriately If you are running xsnapadmin from the local HP9000 console then DISPLAY should already be set If you are running xsnapadmin from a remote X display then set DISPLAY to the host name or IP address of that display Use the following commands to invoke xsnapadmin DISPLAY xstation10 us oracle com 0 export DISPLAY xsnapadmin amp Upon startup of xsnapadmin the main screen will open and display the current configuration of the local SNA node See Figure 8 1 Configuring SNAPlus2 8 3 Creating SNA Definitions for the Gateway Figure 8 1 xsnapadmin Main Screen A il 4 m m m SEE EE e gt gt gt EE gt gt EEE gt EE gt gt gt AE DE EE EE EEE gt EE EE Configuring the SNA Node From the Services menu select Configure Node Parameters In the Node Parameters dialog box see Figure 8 2 enter the APPN support type Control Point Name Control Point Alias and Node ID as needed The Control Point Name is composed of the SNA Network Name and the CP name of the local host Click OK 8 4 Oracle Transparent Gateway for DRDA Ins
252. refer to Interpreting Gateway Error Messages on page 16 1 and report to your system administrator 30081 Communication Error lost session Cause The current DRDA CPI C session was disconnected Action Try processing the received error If it persists then refer to Interpreting Gateway Error Messages on page 16 1 and report it to your system administrator 16 4 SQL Tracing and the Gateway When developing applications it is often useful to be able to see the exact SQL statements that are being passed through the gateway This section describes setting appropriate trace parameters and setting up the debug gateway 16 4 1 SQL Tracing in the Oracle Database Oracle Database has a command for capturing the SQL statement which is actually sent to the gateway This command is called EXPLAIN PLAN EXPLAIN PLAN is used to determine the execution plan that Oracle Database follows to execute a specified SQL statement This command inserts a row describing each step of the execution plan into a specified table If you are using cost based optimization then this command also determines the cost of executing the statement The syntax of the command is EXPLAIN PLAN SET STATEMENT ID text INTO schema table dblink FOR statement For detailed information on this command refer to the Oracle Database SQL Reference Note In most cases EXPLAIN PLAN should be sufficient to extract the SQL statement that is
253. result lists are not preprocessed The TO DATE function is often needed to provide values to update or compare with date columns Therefore the gateway replaces the information included in the TO DATE clause with an acceptable value before the SOL statement is sent to DB2 Except for the SELECT result list all TO DATE functions are preprocessed and turned into values that are the result of the TO DATE function Only TO DATE literal or TO DATE bind variable is permitted Except in SELECT result lists the TO DATE column name function format is not supported The preprocessing of the Oracle TO DATE functions into simple values is useful in an INSERT VALUES clause because DB2 does not allow functions in the VALUES clause In this case DB2 receives a simple value in the VALUES list All forms of the TO_DATE function with one two or three operands are supported 13 24 Oracle Transparent Gateway for DRDA Installation and User s Guide Passing Native SQL Statements through the Gateway 13 7 8 Performing Numeric data type Operations IBM versions of the DRDA Server perform automatic conversions to the numeric data type of the destination column such as integer double precision floating point or decimal The user has no control over the data type conversion and this conversion can be independent of the data type of the
254. result set EXPLAIN_PLAN Improvement The EXPLAIN_PLAN table contains the actual SQL statements passed to the DRDA Server from the Oracle Database 10 through the gateway Heterogeneous Database Integration The gateway support for ANSI standard SQL enables read write access to DRDA databases Even if your data exists on different platforms in different applications new applications can use all data regardless of location Minimum Impact on Existing Systems The gateway does not require installation of additional Oracle software on your OS 390 MVS AS 400 VM or UNIX target system The database interface that it uses is provided by IBM and is built into the DRDA database products and SNA or TCP IP facilities that already exist on these platforms Configuring an IBM system for DRDA access typically consists of defining the SNA or TCP IP resources involved and establishing access security definitions specific to the target database Large Base of Data Access DRDA Application Server Function is supported by most IBM DB2 database products Application Portability The gatewa s ability to interface with heterogeneous databases makes it possible to develop a single set of portable applications that can be used against both Oracle and IBM databases and any other databases for which Oracle Corporation provides gateways Remote Data Access Location flexibility is maximized because the gateway architecture permits network connections
255. ring options For example TO_DATE 2008 07 23 YYYY MM DD can be used in any SELECT INSERT UPDATE or DELETE statement u The HS_NLS_DATE_FORMAT parameter The HS_NLS_DATE_FORMAT parameter defines a default format for Oracle Database explicit TO_DATE functions without a pattern and for implicit string to date conversions For example with HS_NLS_DATE_FORMAT defined as YYYY MM DD 2008 07 23 can be used in any SELECT INSERT UPDATE or DELETE statement 13 7 6 HS_NLS_DATE_FORMAT Support The following table lists the four patterns that can be used for the HS_NLS_DATE_FORMAT DB2 Date Format Pattern Example EUR DD MM YYYY 30 10 1994 ISO YYYY MM DD 1994 10 30 JIS YYYY MM DD 1994 10 30 USA MM DD YYYY 10 30 1994 The Oracle Database default format of DD MON YY is not permitted with DB2 The following example demonstrates how to enter and select date values in the twenty first century ALTER SESSION SET HS_NLS_DATE_FORMAT YYYY MM DD INSERT INTO EMP HIREDATE VALUES 2008 07 23 SELECT FROM EMP WHERE HIREDATE 2008 07 23 UPDATE EMP SET HIREDATE 2008 07 24 WHERE HIREDATE 2008 07 23 DELETE FROM EMP WHERE HIREDATE 2008 07 24 13 7 7 Oracle TO DATE Function The Oracle TO DATE function is preprocessed in SOL INSERT UPDATE DELETE and SELECT WHERE clauses TO DATE functions in SELECT
256. root block to its leaf blocks A depth of 1 indicates that the root block and the leaf block are the same EAF_BLOCKS Number of leaf blocks in the index DISTINCT_KEYS Number of distinct indexed values For indexes that enforce UNIQUE and PRIMARY KEY constraints this value is the same as the number of rows in the table AVG_LEAF_BLOCKS_PER_KEY N A AVG_DATA_BLOCKS_PER_KEY N A CLUSTERING_FACTOR N A STATUS State of the index VALID NUM_ROWS Number of rows in the index SAMPLE_SIZE Size of the sample used to analyze the index LAST_ANALYZED Date on which an index was most recently analyzed DEGREE Number of threads per instance for scanning the index INSTANCES Number of instances across which the index is to be scanned PARTITIONED Whether the index is partitioned TEMPORARY Whether the index is on a temporary table GENERATED Whether the name of the index is system generated SECONDARY N A BUFFER_POOL Whether the index is a secondary object USER_STATS N A A 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Data Dictionary View Tables column name description DURATION N A PCT_DIRECT_ACCESS N A ITYP_OWNER N A ITYP_NAME N A PARAMETERS N A GLOBAL_STATS N A DOMIDX_STAT
257. rver The gateway is responsible for sending these SQL statements to the DRDA Server for execution and for fielding and returning responses The responses are either data or messages Any conversions between Oracle data types and DRDA data types are performed by the gateway Both the Oracle integrating server and the application read and process only Oracle data types Introduction 1 9 Oracle Tools and the Gateway SQL Differences Not all SQL implementations are the same The Oracle Database 10g supports a larger set of built in functions than the databases that are currently accessed through the gateway The Oracle integrating server and the gateway work together to convert SQL to a form that is compatible with the specific DRDA Server During this conversion an Oracle Database 10g function can be converted to a function that is recognizable to the specific DRDA Server For example the Oracle Database 10g NVL function is converted to the DB2 VALUE function Alternatively the Oracle integrating server withholds functions that are not executable by the DRDA Server and performs them after rows are fetched from the DRDA database This processing generally applies to SELECT statements The Oracle integrating server and the gateway cannot perform this kind of manipulation on UPDATE INSERT or DELETE statements because doing so changes transaction semantics 1 8 Oracle Tools and the Gateway Use
258. rver u Errors detected by the gateway m Errors detected in the DRDA software either on the client or server side a Communication errors a Errors detected by the server database 16 1 1 Errors Detected by the Oracle Integrating Server Errors detected by the Oracle integrating server are reported back to the application or tool with the standard ORA type message Refer to Oracle Database Error Messages for Error Messages Diagnosis and Reporting 16 1 Interpreting Gateway Error Messages descriptions of these errors For example the following error occurs when an undefined database link name is specified ORA 02019 connection description for remote database not found Errors in the ORA 9100 to ORA 9199 range are reserved for the generic gateway layer components of the gateway that are not specific to DRDA Messages in this range are documented in Oracle Database Error Messages 16 1 2 Errors Detected by the Gateway Errors detected by the generic gateway are prefixed with HGO and are documented in Oracle Database Error Messages A sample error message is HGO 00706 HGO Missing equal sign for parameter in initialization file 16 1 3 Errors Detected in the DRDA Software Errors detected in the DRDA gateway on the client or server side are usually reported with error ORA 28500 followed by a gateway specific expanded error message There are two return codes reported in the expanded message a drc specifies DRDA spec
259. s TCP IP 9 1 for DRDA Server TCP IP 9 1 Primary 5 2 DB2 400 5 3 Recovery 5 2 DB2 400 5 3 post processed SQL functions overview 13 6 Index 14 post processing native semantics 13 18 SQL tracing in the gateway 16 5 PREPARE TRANSACTION statement 12 5 primary port number DB2 400 5 3 DB2 0S390 5 2 privileges BIND DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 BINDADD DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 BINDAGENT DB2 0S390 5 2 DB2 VM 5 6 CONNECT DB2 UDB 5 5 COPY DB2 0S390 5 2 DB2 VM 5 6 CREATE IN DB2 0S390 5 2 DB2 VM 5 6 CREATE PUBLIC DATABASE LINK 11 4 11 7 CREATEIN DB2 UDB 5 5 CREATETAB DB2 0S390 5 2 DB2 UDB 5 5 data dictionary emulation 13 27 EXECUTE DB2 0S390 5 2 DB2 UDB 5 5 DB2 VM 5 6 procedure stored read only gateway 12 6 using DRDA Server 13 3 processing time with GROUPBY HAVING WHERE 13 19 product installation directory 4 2 profile CPI C side information 6 10 8 10 creating CPI C and Mode profiles 6 9 8 9 name creating SNAP IX profiles 6 2 creating SNAPlus2 profiles 8 2 set 11 8 types communication server profiles 7 2 protocol APPC LU6 2 IBM Communication Server product on AIX 7 1 SNAP IX product on Solaris 6 1 SNAPlus2 product on HP UX 8 1 commit confirm 1 7 communications protocols 10 2 converter 1 4 definition 10 2 implicit protocol conversion 1 4 network 12 4 Oracle Net Protocol Adapters 10 2 PROTOCOL IPC sample B 2 protocol independ
260. se and gateway handle SOL functions for a DB2 400 database are shown in the following table 13 12 Oracle Transparent Gateway for DRDA Installation and User s Guide Oracle Database SQL Construct Processing Table 13 3 DB2 400 SQL Compatibility by Oracle SQL Function Native Semantics Oracle SQL Function Compatible Translated Compensated Candidate ABS ABSVAL Yes ACOS z s Yes Yes ADD_MONTHS 5 Yes ASC Yes Yes ASIN Yes Yes ATAN H Yes Yes ATAN2 a Yes Yes AVG Yes H z BITAND z Yes Yes CAST Yes Yes CEIL CEILING Yes CHARTOROWID Yes CHR Yes Yes CONCAT Yes CONVERT 5 Yes Yes COS Yes Yes COSH Yes Yes COUNT Yes COUNT DISTINCT Yes colname COUNT ALL colname Yes COUNTCOL COUNT column Yes COUNTCOL DECODE 7 Yes Yes DUMP Yes Yes EXP Yes Yes FLOOR Yes Yes GREATEST Yes Yes HEXTORAW z z Yes Yes NITCAP s Yes Yes INSTR Yes Yes INSTRB gt Yes Yes LAST_DAY 5 s Yes LEAST z Yes Yes LENGTH z Yes Yes Developing Applications 13 13 Oracle Database SQL Construct Processing Table 13 3 Cont DB2 400 SQL Compatibility by Oracle SQL Function
261. set identifier direction is one of the following u mapping is bidirectional lt mapping is one way Oracle Character Set to CCSID gt mapping is one way CCSID to Oracle Character Set Oracle_CharacterSet is the name of a valid Oracle Character Set shift indicates a character set that requires Shift OUT IN processing Set this attribute only for EBCDIC based double byte and multi byte mappings The second form of syntax defines a mapping of a multi byte CCSID to its single byte and double byte CCSID equivalents MBC multi single double Where multi is the multi byte CCSID single is the single byte CCSID double is the double byte CCSID This facility is intended for mapping CCSIDs which were not previously mapped as shipped with the gateway You must contact Oracle Support Services before modifying this map The following are the contents of the map as shipped with the Oracle Transparent Gateway for DRDA Copyright c 2001 2003 Oracle Corporation All rights reserved Transparent gateway for IBM DRDA CodePage Oracle CharacterSet Map S Single byte D Double byte M Multi byte MBC SBC DBC mapping Single byte codepage mappings S 37 WE8EBCDIC37 United States Canada EBCDIC S 273 D8EBCDIC273 4 Austria Germany EBCDIC S 277 DK8EBCDIC277 Denmark Norway EBCDIC D 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Codepage Map Facility nu a nn mn He
262. shift Korean double byte EBCDIC M 933 KO16DBCS shift Korean Mixed multi byte EBCDIC MBC 933 833 834 Korean Mixed multi byte EBCDIC Notice that the multi byte set is a bidirectional map to KO16DBCS However the single and double codepages are mapped one way to KO16DBCS Because only one bidirectional CCSID to Oracle Database Character Set entry for a given pair can exist you directly map the multi byte sets Because the single byte and double byte CCSIDs are ostensibly subsets of KO16DBCS you map them as one way entries Note that double byte and multi byte maps are tagged with the shift attribute This is required for EBCDIC double byte and multi byte codepages as part of the shift out in encapsulation of data The single byte map is not marked because single byte sets are not permitted to contain double byte data and thus will never use shift encapsulation Note that the MBC entry ties the codepages together The ASCII Korean sets are similarly mapped and are S 1088 gt KO16MSWIN949 Korean KS single byte PC Data ASCII D 951 gt KO16MSWIN949 Korean KS double byte PC Data ASCII M 949 KO16MSWIN949 Korean KS multi byte PC Data ASCII MBC 949 1088 951 Korean KS multi byte PC Data ASCII Notice that the multi byte set is a bidirectional map to KO16MSWIN9 49 However the single and double codepages are mapped one way to KO16MSWIN9 49 Because only one bidirectional CCSID to Oracle Database Character Set entry for a given
263. siii late ares ees tens 12 5 Replicating in a Heterogeneous Environment ete 12 6 Copying Data from Oracle Database 10g to DRDA Server 12 6 Copying Data from DRDA Server to Oracle Database 10g Server 12 7 Tracing SQL StatementS ene nena nenenana aea e aE ene 12 7 Developing Applications 13 1 13 1 1 13 2 13 3 13 3 1 13 3 2 13 4 13 5 Gateway Appearance to Application Program5 anat 13 1 Fetch Rebloch ing tan sei a O ton Paget a o a ka AE tka be dete 13 2 Using Oracle Stored Procedures with the Gateway 13 2 Using DRDA Server Stored Procedures with the Gateway ene 13 3 Oracle Application and DRDA Server Stored Procedure Completion 13 4 Procedural Feature Considerations with DB2 ue uses anawa 13 5 Database Link Behavior e ai nA A A A A AO A AA AO ri lia casita 13 5 Oracle Database SOL Construct Processing 13 6 14 15 13 5 1 Compatible SQL Funct Oris w a a A AA ten deeds at AO ots 13 6 13 5 2 Translated SOL Functions A A ete tee een res 13 6 13 5 3 Compensated SQL Functions e enem 13 6 13 5 4 Native Semantic SQL Functions e eseuuse ea ea nana 13 7 13 5 5 DB2 05390 50L Compatibility asian ii area 13 7 13 5 6 DB2 Universal Database SOL Compatibility 13 10 13 5 7 DB2 400 SQL Compatibility aken 13 12 13 5 8 DB2 VM SOL Compatibility isss eee owsa 13 15 13 6 Native Semantics aaa dd OECD A
264. ss and a Network Mask to a given network interface This basic configuration should have been completed already by the System Administrator If not contact your System Administrator to have this configuration completed before you continue Additional configuration consists of defining a Name Server IP Address or creating entries in the Hosts file on the local machine Name Servers translate hostnames into IP Addresses when queried on a particular host name The Hosts file provides this same functionality but in a non network participating manner Configuring TCP IP 9 1 Configuring TCP IP under UNIX For local configuration the gateway and the DRDA Server are on the same computer it may be desirable to use the loop back address The IP address is 127 0 0 1 and is typically given the local name localhost or loopback in the hosts file Using the loop back address reduces the amount of network overhead by handling the traffic internally without actually talking to the network The gateway is configured for TCP IP using the DRDA CONNECT PARM initialization file parameter In an SNA configuration this parameter would be set to the Side Information profile name In a TCP IP configuration this parameter should be set to the IP address or Host name of the DRDA Server which should be followed by the Service Port number of that server Note When installing the gateway you must choose either SNA or TCP IP for the Networking Interfa
265. statement creates a ads synonym for the EMP file in the DRDA Server with ownership of ORACLI ki CREATE PUBLIC SYNONYM EMP FOR ORACLE EMPEDRDA 12 5 Performing Distributed Queries The Oracle Transparent gateway technology enables the execution of distributed gueries that join Oracle Database and DRDA Servers and any other data store for which Oracle provides a gateway These complex operations can be completely transparent to the users reguesting the data The distributed guery optimizer DOO capability can provide better performance of distributed gueries Statistical data regarding tables from DRDA Server is retrieved and passed to the Oracle Integrating Server The DOO capability is enabled or disabled by the DRDA OPTIMIZE OUERY parameter Refer to DRDA OPTIMIZE QUERY on page C 6 for more information The following example joins data between an Oracle Database DB2 OS390 and a DRDA Server SELECT o custname p projno e ename sum e rate p hours FROM orders DB2 o EMP ORACLE7 e projects DRDA p WHERE o projno p projno AND p empno e empno GROUP BY o custname p projno e ename A combination of views and synonyms using the following SQL statements keeps the process of distributed queries transparent to the user CREATE SYNONYM orders for orders DB2 CREATE SYNONYM PROJECTS for PROJECTS DRDA CREATE VIEW details custname projno ename spend AS SELECT o custname p projno e ename sum e rate p hours FROM ord
266. t is mapped to the DRDA VARCHAR data type 13 7 3 Performing Graphic String Operations DB2 GRAPHIC data types store only double byte string data Sizes for DB2 GRAPHIC data types typically have maximum sizes that are half that of their Character Developing Applications 13 21 DRDA Data type to Oracle Data type Conversion counterparts For example the maximum size of a CHAR may be 255 characters whereas the maximum size of a GRAPHIC may be 127 characters Oracle Database does not have a direct matching data type and the gateway therefore converts between Oracle character data types to DB2 Graphic data types Oracle Database character data types may contain single mixed or double byte character data The gateway converts the string data into appropriate double byte only format depending upon whether the target DB2 column is a Graphic type and whether Gateway Initialization parameters are set to perform this conversion For more configuration information refer to Appendix C DRDA Specific Parameters and Appendix D National Language Support 13 7 4 Performing Date and Time Operations The implementation of date and time data differs significantly in IBM DRDA databases and Oracle Database Oracle Database has a single date data type DATE that can contain both calendar date and time of day information IBM DRDA databases support the following three distinct date and time data types DATE is the calendar da
267. tains the following sections u Checklist for Configuring the Communications Interfaces u SNAP IX Configuration Tool u Creating SNAP IX Profiles for the Gateway u Independent Versus Dependent LUs m Creating SNA Definitions for the Gateway u Using SNA Session Security Validation u SNA Conversation Security a Testing the Connection 6 1 Checklist for Configuring the Communications Interfaces The checklists for configuring the communication interfaces are u Creating SNAP IX Profiles for the Gateway m Creating SNA Definitions for the Gateway a Testing the Connection 6 2 Before You Begin This chapter requires you to provide values for parameters unique to your system in order to properly configure SNAP IX Refer to Appendix E for a worksheet listing all of the installation parameters you will need to know before you can complete the configuration process Ask your network administrator to provide you with these parameters before you begin 6 3 SNAP IX Configuration Tool All SNAP IX product configuration is done using the xsnaadmin program This tool is an X Windows application which provides a graphical interface so that you can view and modify the current SNAP IX configuration and the current running state of the host SNA node Configuring SNAP IX Interfaces 6 1 Creating SNAP IX Profiles for the Gateway 6 4 Creating SNAP IX Profiles for the Gateway The Oracle Transparent Gateway for IBM DRDA requires a stored set of defin
268. tallation and User s Guide Creating SNA Definitions for the Gateway Figure 8 2 Node Parameters Dialog Box Adding a Port From the Services menu select Connectivity and Add Port In the Add to lt nodename gt dialog box Figure 8 3 select the Port type and click OK Figure 8 3 Add to lt nodename gt Dialog Box In the SAP dialog box see Figure 8 4 enter a Port name and network card number The Port name will be used to logically name the physical network card that you are using and will be used to bind a Service Access Port to the card for SNA protocols Usually you can accept the values provided in the dialog box If a different network card is needed however enter the card number as reported with the lanscan command Click OK Configuring SNAPlus2 8 5 Creating SNA Definitions for the Gateway Figure 8 4 Ethernet SAP Dialog Box Creating a Link Station After the Port has been defined you need to create a Link Station The Link Station represents the SNA node of the remote host of the DRDA Server But before you can create the Link Station you must create a Remote Node definition From the Services menu select APPC and Add Remote Node In the dialog box see Figure 8 5 enter the SNA CPNAME of the remote node and click OK Figure 8 5 Add Remote Node Dialog Box Now you are ready to create the Link Station From the Services menu select Connectivity and Add Link Station In the dialog box s
269. tatements 12 8 Oracle Transparent Gateway for DRDA Installation and User s Guide 13 Developing Applications Oracle Transparent Gateway for DRDA allows applications written for Oracle Database to access tables ina DRDA Database This access can be virtually transparent by using synonyms or views of the DRDA tables accessed by a database link However fundamental SQL data type and semantic differences exist between the Oracle Database and DRDA Databases This chapter provides information that is specific to the 10 2 release of the Oracle Transparent Gateway for DRDA This chapter contains the following sections Gateway Appearance to Application Programs Using Oracle Stored Procedures with the Gateway Using DRDA Server Stored Procedures with the Gateway Database Link Behavior Oracle Database SQL Construct Processing Native Semantics DRDA Data type to Oracle Data type Conversion Passing Native SQL Statements through the Gateway Oracle Data Dictionary Emulation on a DRDA Server Defining the Number of DRDA Cursors 13 1 Gateway Appearance to Application Programs An application that is written to access information in a DRDA Database interfaces with an Oracle Integrating Server When developing applications keep the following information in mind You must define the DRDA Database to the application by using of a database link that is defined in the Oracle Integrating Server Your application should specify tables that e
270. te the table and create the package For more information refer to DB2 UDB Universal Database on page 5 4 4 Create the ORACLE2PC table db2 tf o2pc sql 5 Commit the transaction db2 COMMIT 6 Verify that the table was created Optionally verify the table was created under the correct user ID db2 LIST TABLES FOR USER db2 COMMIT 7 Disconnect from the session db2 DISCONNECT CURRENT 11 5 DRDA Gateway Package Considerations The DRDA package must be bound with the internal Stored Procedure GTW _BIND_PKG You must perform this bind step if this release is the first time the gateway has been installed on this system If you are upgrading from version 9 of the gateway then a rebind is not necessary unless the initialization parameters have been changed The user ID used to bind or rebind the DRDA package must have the appropriate privileges on the remote database as described in Chapter 5 Configuring the DRDA Server 11 5 1 Before Binding the DRDA Gateway Package Check DRDA parameter settings and create your ORACLE2PC table before binding the DRDA gateway package 11 5 1 1 Step 1 Check all DRDA parameter settings Check all DRDA parameter settings to be sure that they are set correctly before you start the bind For example the default for DRDA_DISABLE_CALL only works if your DRDA database supports stored procedures If not then you must change the setting
271. te only TIME is the time of day only TIMESTAMP is a numerical value combining calendar date and time of day with microsecond resolution in the internal format of the IBM DRDA database 13 7 4 1 Processing TIME and TIMESTAMP Data There is no built in mechanism that translates the IBM TIME and TIMESTAMP data to Oracle DATE data An application must process TIME data types to the Oracle CHAR format with a length of eight bytes An application must process the TIMESTAMP data type in the Oracle CHAR format with a length of 26 bytes An application reads TIME and TIMESTAMP functions as character strings and converts or subsets portions of the string to perform numerical operations TIME and TIMESTAMP values can be sent to an IBM DRDA database as character literals or bind variables of the appropriate length and format 13 7 4 2 Processing DATE Data Oracle and IBM DATE data types are mapped to each other If an IBM DATE is queried then it is converted to an Oracle DATE with a zero midnight time of day If an Oracle DATE is processed against an IBM DATE column then the date value is converted to the IBM DATE format and any time value is discarded Character representations of dates are different in Oracle format and IBM DRDA format When an Oracle application SQL statement contains a date literal or conveys a date using a character bind variable the gat
272. tements for the synonyms and views you create Accessing Other DRDA Servers u Step 1 Configure another SNA profile set for the DRDA Server u Step 2 Configure additional DRDA Server instances a Step 3 Bind the DRDA package to your DRDA Server 11 2 Choosing a Gateway System Identifier The Gateway System Identifier SID is a string of alphabetic and numeric characters that identifies a gateway instance The SID is used in the filenames of gateway parameter files and in the connection information associated with the Oracle Database database links that access the gateway A separate SID is required for each DRDA Server to be accessed You might also have multiple SIDs for one DRDA Server to use different gateway parameter settings with that server Refer to Accessing Other DRDA Servers on page 11 8 for information on configuring additional SIDs 11 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Configuring the Host 11 2 1 Enter the SID on the Worksheet Enter the SID in your Appendix E Configuration Worksheet 11 3 Configurating the Gateway The information in this chapter describes the configuration process for the gateway All gateway parameters are kept in the initsid ora Gateway Initialization file which is stored in the gateway admin directory 11 4 Configuring the Host To configure the host for the Oracle Transparent Gateway for DRDA you tailor the parameter files for your installation
273. tep 1 Log on to an Oracle integrating server m Step 2 Create a Database link u Step 3 Execute the stored procedure GTW BIND PKG Binding Packages on DB2 Universal Database DB2 UDB m Step 1 Log into the machine where DB2 UDB is running Configuring the Gateway 11 1 Choosing a Gateway System Identifier Step 2 Copy files from ORACLE HOME tg4drda install db2udb m Step 3 Connect to the database a Step 4 Create the ORACLE2PC table a Step 5 Commit the transaction Step 6 Verify that the table was created m Step 7 Disconnect from the session Before Binding the DRDA Gateway Package Step 1 Check all DRDA parameter settings a Step 2 If using DB2 UDB then create ORACLE2PC table Sample SQL scripts u Step 1 Ifserver is DB2 OS390 DB2 400 or DB2 UDB then run data dictionary scripts ua Step la Upgrading from a previous gateway version m Step lb Creating the Data Dictionary tables and views a Step 2 DB2 UDB or other server a Step 2a If server is DB2 UDB grant authority to package m Step 2b If server is not DB2 UDB create the ORACLE2PC table Configuring the Oracle Integrating Server m Step 1 Create a database link m Step 2 Create synonyms and views Accessing the Gateway from Other Oracle Databases a Step 1 Create a database link with which to access the gateway u Step 2 If needed define synonyms and views for tables accessed through the gateway u Step 3 Perform GRANT sta
274. ters These Sample Applications G 1 ORAIND are local variables to the C program which you must copy to and L from the parameter list provided to the stored procedure AEARERRARE RRE RARE RE RARE RE RARA RE RAR RR RARA RRA RRA ERE RARE RE RARE RAR A ARRE RAR EXEC SQL BEGIN DECLARE SECTION long dno input parm DEPTNO char dname 15 input parm DNAME char locale 14 input parm LOC EXEC SQL END DECLARE SECTION main argc argv int argc char argv tkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkikkkkkkkkkkkkkkkkkkkkikkkkkkkk Copy the input parameters into the area reserved in the local program for SQL processing tkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk dno int argv 1 strcpy dname argv 2 strcpy locale argv 3 tkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkikkkkkkkkkkkkkkkkkkkkkkkkkkkkk Issue SQL INSERT to insert a row into SCOTT DEPT Fkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk EXEC SQL INSERT INTO SCOTT DEPT VALUES dno dname locale tkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkikkkkkkkkkkkkkkkkkkkkkkkkkkkkk Copy SQLCODE to the output parameter list El FZ H H H k He He Heke RRE ke he RARE RARE RARA RARA RARE RR RR EER EKER ERE EERE RRE RARA RARA A RARA AREAS int argv 4 SQLCODE 1 G 2 ORAIND ORAIND is a sample host progra
275. teway package on the DRDA Server To properly bind the package the user ID and password used when the procedure is executed either Configuring the DRDA Server 5 3 DB2 UDB Universal Database td implied as the current Oracle user or explicitly defined in the CREATE DATABAS LINK command must have proper authority on the DRDA Server to create the package This user ID should be used to create and own the ORACLE2PC two phase commit table The user ID that is used to bind or rebind the DRDA package must have the following privileges on the DRDA Server m Use authority on the CRTSOLPKG command u Change authority on the library the package will be created in Choose a user ID now that will own the package and ORACLE2PC table Ensure that this user ID is defined in DB2 400 and AS 400 Step 3 Define the recovery user ID During gateway configuration the recovery user ID and password are specified in the Gateway Initialization File using the DRDA RECOVERY USERID and DRDA RECOVERY PASSWORD parameters If a distributed transaction fails then the recovery process connects to the remote database using the user ID and password defined in these parameters This user ID must have execute privileges on the package and must be defined to the DRDA database If the user ID is not specified in DRDA RECOVER USERID then the gateway attempts to connect to a user ID of ORARECOV when a distributed transaction is in doubt
276. that is used for communications Gateway for between the gateway and the DRDA Server This DRDA parameter is required when the gateway accesses GRAPHIC or multi byte data on the DRDA Server Set this parameter to the same value as the character set component of the HS_LANGUAGE parameter For detailed information refer to Gateway Language Interaction with DRDA Server on page D 4 Oracle HS NLS DATE FORMAT It is initialization parameter HS NLS DATE FORMAT Transparent specifies the format for dates used by the DRDA Server Gateway for For detailed information refer to Gateway Language DRDA Interaction with DRDA Server on page D 4 Oracle HS NLS DATE LANGUAGE It is initialization parameter Transparent HS NLS DATE LANGUAGE specifies the language used by Gateway for the DRDA Server for day and month names and for date DRDA abbreviations For detailed information refer to Gateway Language Interaction with DRDA Server on page D 4 DRDA Server CCSID CCSID is the server character set that is mapped in the gateway to the eguivalent Oracle Character Set The CCSID specifies the character set that the DRDA database uses to store data It is defined when you create a database For detailed information refer to Gateway Codepage Map Facility on page D 6 D 2 Client and Oracle Integrating Server Configuration A number of NLS parameters control NLS processing between the Oracle Database and client You can set language depend
277. the DB2 instance you plan to access through the gateway If DDF is not operational then you must configure it and start it as described in the appropriate DB2 documentation Even if DDF is operational on the DB2 instance it might be necessary to make changes to the DDF Communication Database CDB tables to specify the authorization conduct of DRDA sessions from the gateway This can be done by properly authorized users with a utility like the DB2 SPUFI utility If you make changes to CDB tables then you must stop and restart DDF for the changes to take effect Refer to Chapter 14 Security Considerations for additional CDB tables and security information 5 3 DB2 400 Experience with DB2 400 and AS 400 is required to perform the following steps Step 1 Configure the Communications Server u Step 2 Define the user ID that owns the package m Step 3 Define the recovery user ID m Step 4 Determine DRDA location name for DB2 instance Step 1 Configure the Communications Server If you are using SNA then configure AS 400 communications for the SNA LU6 2 connection from the host Configure DB2 400 for SNA using the LU defined If you are using TCP IP then configure the TCP IP subsystem configure DB2 400 to use TCP IP and assign a Primary and Recovery port number for the DB2 server Step 2 Define the user ID that owns the package During gateway configuration you will need to execute the Bind Package Stored Procedure to bind the ga
278. the Number of DRDA Cursors You can define any number of cursors depending on your application requirements Oracle recommends that you use the default value of 100 However if the default is not appropriate for your application there are two points to consider when defining the number of cursors for your installation u Each cursor requires an additional amount of storage and additional management u Ifyou change DRDA PACKAGE SECTIONS you must rebind the package The parameter DRDA PACKAGE SECTIONS is specific to the DRDA package This parameter defines the number of sections open cursors at the IBM database Refer to Appendix C DRDA Specific Parameters for more information about setting the DRDA_PACKAGE_SECTIONS parameter 13 28 Oracle Transparent Gateway for DRDA Installation and User s Guide 14 Security Considerations The gateway architecture involves multiple computer setups that have distinct security capabilities and limitations This chapter provides information for planning and implementing your security system The chapter provides information that is specific to the 10 2 release of the Oracle Transparent Gateway for DRDA It contains the following sections m Security Overview u Authenticating Application Logons u Defining and Controlling Database Links u Processing Inbound Connections m Passwords in the Gateway Initialization File 14 1 Security Overview When you connect several different systems gene
279. the program to be executed on the server side of an APPC conversation IBM DRDA uses a special reserved TPN called an SNA Service Transaction Program that is expressed in hexadecimal because it contains non printable characters The TPN is X 07F6C4C2 Specify this TPN for DB2 MVS and DB2 400 DRDA Servers For DB2 VM the DRDA Server does not use the standard DRDA TPN Instead the TPN identifies the VM Resource ID RESID of the target DB2 VM server virtual machine and can be entered in non hexadecimal characters The RESID is specified when DB2 VM is configured 7 1 3 Step 3 Testing the Connection Before proceeding with the gateway configuration tasks in Chapter 11 Configuring the Gateway ensure that your connection is working This can be done using SMIT Configuring IBM Communication Server 7 3 Using SNA Session Security Validation 7 2 Using SNA Session Security Validation When the database link request for the gateway begins the gateway attempts to start an APPC conversation with the DRDA Server Before the conversation can begin a session must start between the host Logical Unit LU and the DRDA Server LU SNA and its various access method implementations including IBM Communication Server and VTAM provide security validation at session initiation time allowing each LU to authenticate its partner This is carried out entirely by network software before the gateway and server application programs begin their conv
280. tion Profile that is not defined 16 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Mapped Errors ORA 28501 communication error on heterogeneous database link TG4DRDA v10 2 0 1 0 grc 0 drc 30081 839C 0001 errp file or directory 2 errmc Initialize Conversation CMINIT CM PROGRAM PARAMETER CHECK 24 No such gt file or directory 2 Refer to the appropriate host operating system or SNA server documentation for more information 16 1 5 Errors Detected by the Server Database Errors detected by the server database are reported with an ORA 28500 followed by a gateway specific expanded error message with drc 777 sqlcode follows This is followed by another line that contains the sqlcode sqlstate errd error array and errmc error tokens returned from the DRDA Server database Refer to IBM documentation for the specific database being used Also refer to Mapped Errors in this chapter for some SQL errors that get translated Note Error code ORA 28500 was error code ORA 09100 prior to gateway version 8 Error code ORA 28501 was listed as ORA 09101 prior to gateway version 8 For example the following error message indicates that the DRDA Server database did not recognize the collection ID or package name specified with the DRDA_PACKAGE_COLLID or DRDA_PACKAGE_NAME parameters in the initsid ora file ORA 28500 connection from ORACLE to a
281. to control how the package is bound on the target database This parameter should be set to FALSE only for supported target DRDA servers and should be set to TRUE otherwise See Section 2 6 1 DB2 Considerations for supported target servers Note Any change to this parameter requires you to rebind C 4 11 DRDA_FLUSH_CACHE Default value SESSION Range of values SESSION COMMIT Syntax DRDA_FLUSH_CACHE SESSION COMMIT DRDA_FLUSH_CACHE specifies when the cursor cache is to be flushed With DRDA_FLUSH_CACHE COMMIT the cursor cache is flushed whenever the transaction is committed With DRDA_FLUSH_CACHE SESSION the cache is not flushed until the session terminates C 4 12 DRDA_GRAPHIC_CHAR_SIZE Default value 4 Range of values 1 through 4 Syntax DRDA_GRAPHIC_CHAR_SIZE num DRDA_GRAPHIC_CHAR_SIZE is used to define the character conversion size to be used for GRAPHIC data types It is a tuning parameter which affects the maximum size Of a GRAPHIC data type when the column is described C 4 13 DRDA_GRAPHIC_PAD_SIZE Default value 0 Range of values 0 through 127 C 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Gateway Initialization File Parameters Syntax DRDA_GRAPHIC_PAD_SIZE num DRDA_GRAPHIC_PAD_SIZE is used to pad the size of a Graphic column as described by the DRDA Serve
282. tored procedure GIW _BIND_PKG SQL gt exec GTW BIND PKGedblink SOL gt COMMIT This creates and commits the package If any errors are reported then correct the Gateway Initialization File parameters as needed and re execute the bind procedure above 11 4 2 Binding Packages on DB2 Universal Database DB2 UDB If you are connecting to a DB2 UDB DRDA Server then DB2 UDB requires that you create the ORACLE2 PC table before binding the DRDA package Other DRDA Servers allow you to bind the package before the ORACLE2 PC table exists To create the ORACLE2PC table 1 Log into the machine where DB2 UDB is running Check that you have the ability to address the DB2 UDB instance where the ORACLE2PC table will reside 2 Copy files from SORACLE_HOME tg4drda install db2udb Copy the following files from the ORACLE HOME tg4drda install db2udb directory o2pc sh Sample shell script for performing the table creation 11 4 Oracle Transparent Gateway for DRDA Installation and User s Guide DRDA Gateway Package Considerations o2pc sql SQL script for creating the table o2pcg sql SQL script for granting package access to PUBLIC 3 Connect to the database Connect to the database using the user ID that you will use for binding the package db2 CONNECT TO database USER userid USING password Note The user ID must have CONNECT CREATETAB and BINDADD authority to be able to connect to the database crea
283. tween the Oracle Database character set and the gateway character set National Language Support D 3 Gateway Language Interaction with DRDA Server D 3 Gateway Language Interaction with DRDA Server During logon of the gateway to the DRDA Server initial language information is exchanged between the gateway and the server First the gateway sends to the DRDA Server the CCSID in which it will be conversing In the following example the Oracle Character Set WE81508859P1 is mapped to CCSID 819 an ASCII Code Page This CCSID is sent to the DRDA Server The DRDA Server responds with the CCSID in which it will be conversing This will be the CCSID with which the DB2 database was generated Also in the following example this is CCSID 500 an EBCDIC Code Page Figure D 2 Gateway Language Interaction with DRDA Server illustrates this process A DB2 instance maps unknown CCSIDs using the SYSIBM SYSSTRINGS table This table has different names for the various DB2 versions It is possible to add additional character set mappings to this table by using DB2 utilities Refer to the DB2 Installation documentation for details The setting of the HS_LANGUAGE parameter in the gateway initsid ora determines which CCSID is used by the gateway for the conversation Similarly the setting of the HS_NLS_NCHAR parameter determines which CCSID is used by the gateway for GRAPHIC data interchange For the list of supported ASCII based
284. ty DRDA SECURITY TYPE C 9 option with IBM Communication Server product on AIX 7 4 option with SNAP IX product on Solaris 6 12 option with SNAPlus2 product on HP UX 8 12 validation in SNA network versus TCP IP 14 3 validation with IBM Communication Server product on AIX 7 4 validation with SNAP IX product on Solaris 6 11 validation with SNAPlus2 product on HP UX 8 11 SECURITY PROGRAM 6 12 7 4 8 12 SECURITY SAME 6 12 7 4 8 12 send receive buffer C 2 session allocation mode DRDA CMSRC CM IMMEDIATE C 3 TPN 7 3 SNA LU6 2 configuring DB2 400 5 3 configuring DB2 0S390 5 2 SNA node 6 1 6 3 6 6 8 2 8 3 8 6 configuring 6 4 8 4 SNA security option IBM Communication Server product on AIX 7 4 SNAP IX product on Solaris 6 12 SNAPlus2 product on HP UX 8 12 SNA Server Link Profile 7 2 Local LU Profile 7 2 Partner LU Location Profile 7 3 Partner LU Profile 7 3 profiles creating 7 1 sample profile definitions 7 2 Side Information Profile 7 3 SNA server network requirements 3 2 sna_domn cfg file 6 2 8 2 sna_node cfg file 6 2 8 2 SNAP IX configuring 6 1 configuring using xsnaadmin program 6 1 configuring using xsnapadmin 6 3 definitions for the gateway 6 3 stored in directory 6 2 Side Information Profiles required 6 2 testing the connection 6 13 SNAPlus2 configuring 8 1 configuring using xsnapadmin 8 3 SNAplus2 additional configuration needed for multiple dependent LUs 6 2 8 2 con
285. u GROUPBY a HAVING u ORDERBY a WHERE ORDERBY controls sort order which may differ at various sort locations For example with ORDERBY ON a DB2 sort would be based on Extended Binary Coded Decimal Interchange Code EBCDIC sorting order whereas with ORDERBY OFF an Oracle Database sort would be based on ASCII sorting order The other three functions GROUPBY HAVING and WHERE can take additional processing time If you need to minimize the use of expensive resources then you should choose the settings of these functions so that the processing is performed with cheaper resource The above listed functions can also be disabled Developing Applications 13 19 DRDA Data type to Oracle Data type Conversion 13 6 3 SQL Set Operators and Clauses The WHERE and HAVING clauses are compatible for all versions of the DRDA Server This means that these clauses are passed unchanged to the DRDA Server for processing Whether clauses GROUP BY and ORDER BY are passed to the DRDA Server or compensated by Oracle Database is determined by the Native Semantics Parameters see the previous section The set operators UNION and UNION ALL are compatible for all versions of the DRDA Server meaning that they are passed unchanged to the DRDA Server for processing The set operators INTERSECT and MINUS are compensated on all versions of the DRDA Server except DB2 UDB For DB
286. uld not be specified allowing CCSID 65535 to be treated as an Oracle RAW data type This parameter is for supporting databases in particular DB2 400 that use CCSID 65535 as the default for all tables created Allowing CCSID 65535 to be treated as another CCSID can save such sites from having to modify every table Warning Specifying any value for DRDA_DEFAULT_CCSID causes all FOR BIT DATA columns to be handled as text columns that need character set conversion and therefore any binary data in these columns can encounter conversion errors ORA 28527 DRDA Specific Parameters C 3 Gateway Initialization File Parameters C 4 9 DRDA_DESCRIBE_TABLE Default value TRUE Range of values TRUE FALSE Syntax DRDA_DESCRIBE_TABLE TRUE FALSE DRDA_DESCRIBE_TABLE directs the gateway to use the DRDA operation Table Describe to return the description of tables This is an optimization that reduces the amount of time and resources that are used to look up the definition of a table Note This feature is not compatible with DB2 Aliases or Synonyms If you use DB2 aliases then be sure to disable this option C 4 10 DRDA_DISABLE_CALL Default value TRUE Range of values TRUE FALSE Syntax DRDA_DISABLE_CALL TRUE FALSE DRDA_DISABLE_CALL controls stored procedure usage and is also used
287. urned as result is used to update the EMP table of Oracle Database DECLARE INPUT VARCHAR2 15 RESULT NUMBER 8 2 BEGIN INPUT JOHN SMYTHE REVISE_SALARY DB2 INPUT RESULT UPDATE EMP SET SAL RESULT WHERE ENAME INPUT END When the gateway receives a call to run a stored procedure on the DRDA Server for example DB2 08390 it first does a lookup of the procedure name in the server catalog The information that defines a stored procedure is stored in different forms on each DRDA Server For example DB2 O05390 V5 0 uses the table SYSIBM SYSPROCEDURES while DB2 05390 V6 1 uses the table SYSIBM SYSROUTINES and SYSIBM SYSPARMS and DB2 400 uses the table OSYS2 SYSPROCS and QSYS2 SYSPARMS The gateway has a list of known catalogs to search depending on the DRDA Server that is being accessed The search order of the catalogs is dependent on whether the catalogs support Location designators such as LUNAME in SYSIBM SYSPROCEDURES and authorization or owner IDs such as AUTHID in SYSIBM SYSPROCEDURES or OWNER in SYSIBM SYSROUTINES 13 4 Oracle Transparent Gateway for DRDA Installation and User s Guide Database Link Behavior Some DRDA Servers allow blank or public authorization qualifiers If the DRDA Server that is currently connected supports which form of qualification then t
288. vals 12 8 Copying Data from Oracle Database 10g to DRDA Server The COPY command enables you to copy data from Oracle Database toa DRDA Server database The Oracle SQL command INSERT is not supported If you use the INSERT command INSERT INTO DRDA_table SELECT FROM local_table then the following message is displayed ORA 2025 All tables in the SQL statement must be at the remote database To copy data from your Oracle database to the DRDA Server use COPY FROM username password connect_identifier INSERT destination_table USING query For example to select all rows from the local Oracle EMP table insert them into the EMP table on the DRDA Server and commit the transaction use COPY FROM scott tiger ORACLE INSERT scott EMP DRDA USING SELECT FROM EMP The SQL Plus COPY command supports APPEND CREATE INSERT and REPLACE commands However INSERT is the only command supported when copying to the DRDA Server For more information about the COPY command refer to SQL Plus User s Guide and Reference 12 6 Oracle Transparent Gateway for DRDA Installation and User s Guide Tracing SQL Statements 12 9 Copying Data from DRDA Server to Oracle Database 10g Server The CREATE TABLE command enables you to copy data from a DRDA Server to Oracle Database To create a table on your Oracle database and to insert rows from a DRDA Server table use CREATE TABLE table_name AS query
289. vanced Security encryption parameters on the gateway to SOLNET CRYPTO CHECKSUM SERVER REQUIRED SOLNET ENCRYPTION SERVER REQUIRED Attempt the connection between the gateway and the Oracle integrating server again If no error message is returned and the connection completes then you can assume Advanced Security encryption is working properly Oracle Net 10 5 Testing Advanced Security Encryptions 10 6 Oracle Transparent Gateway for DRDA Installation and User s Guide 11 Configuring the Gateway After you have installed the gateway configured your DRDA Server and configured your SNA or TCP IP software then you must configure the gateway Some of these tasks involve customizing the Gateway Initialization File This chapter includes the following sections u Configuration Checklists u Choosing a Gateway System Identifier u Configurating the Gateway u Configuring the Host u DRDA Gateway Package Considerations u Backup and Recovery of Gateway Configuration u Configuring the Oracle Integrating Server u Accessing the Gateway from Other Oracle Databases m Accessing Other DRDA Servers m Gateway Installation and Configuration Complete 11 1 Configuration Checklists The checklist for configuring gateway are Configuring the Gateway u Choosing a Gateway System Identifier Configuring the Host u Step 1 Choose the initsid ora file m Step 2 Tailor the initsid ora file Binding the DRDA Gateway Package S
290. variable to point to this directory The command that you enter depends on the shell that you are using For example if you are a Bourne or Korn shell user then enter ORACLE_HOME oracle tg4drda 10 2 0 export ORACLE_HOME If you are a C shell user then enter setenv ORACLE_HOME oracle tg4drda 10 2 0 Step 4 Mount the Installation Media Place the installation media and follow the steps as per your operating system Step 4a on Solaris Most Solaris installations will have the auto mounter running in which case the installation media will be mounted automatically Typically the mount point will be cdrom To manually mount the installation media enter su root mkdir cdrom mount r F hsfs dev dsk c0t6d0s0 cdrom exit cd cdrom Step 4b on AIX to mount the installation media enter su root mkdir cdrom mount rv cdrfs dev cd0 cdrom exit cd cdrom Step 4c on hp ux to mount the installation media enter su root nohup usr sbin pfs_mountd amp nohup usr sbin pfsd amp usr sbin pfs_mount SD_CDROM exit cd cdrom Step 4d on Linux to mount the installation media enter su root mkdir cdrom mount dev hdb cdrom exit cd cdrom Step 5 Set the DISPLAY Variable For example if you are using a Bourne or Korn shell then enter DISPLAY machine 0 export DISPLAY If you are using a C shell then enter setenv DISPLAY machine 0 Inst
291. ver This equates to the maximum number of open database links using the gateway instance Local LU Profile The Local LU Profile describes the SNA LU through which the gateway communicates The LU type field must be LU6 2 The network name is an established name for your SNA network An LU name must be assigned to the gateway The LU name assigned to the gateway might be required elsewhere in the SNA network Contact the person responsible for your SNA network to determine the correct network and LU name to specify in the profile Set the dependent LU field to no Setting the dependent LU field to yes prevents more than one instance of the gateway from running at the same time The Local LU Profile name is specified in the Side Information profile Link Profiles The Link profiles describe and control the connection of the host to the network The gateway does not impose special requirements on these profiles 7 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Checklist for Configuring the Communications Interfaces The Link Profile name is specified in the Local LU Profile Partner LU Profile The Partner LU profile identifies the name of the remote or partner LU associated with the DRDA Server In addition to specifying the fully qualified partner LU name you can also specify a partner LU alias to identify a Partner LU Location Profile if required To allow more than one concurrent conversation between th
292. ver Profiles m Step 2 Creating Communication Server Profiles for the Gateway m Step 3 Testing the Connection 7 1 1 Step 1 Configuring Communication Server Profiles Configure the profiles to define APPC conversations with DRDA databases 7 1 2 Step 2 Creating Communication Server Profiles for the Gateway Communications Server requires a stored set of definitions called profiles to support connections between the gateway and DRDA Servers Each profile consists of a profile name and a profile type a set of fields describing the profile The fields in a given profile type are generally a mixture of operating parameter values and names of other SNA profiles relevant to the profile Each functional part of APPC such as the Mode Remote Transaction Program name and LU is described by a distinct profile type SNA profile definitions are created and modified in two ways u Directly with shell commands u Using SNA administration tools Maintenance of SNA profiles is normally done by a user with root authority To create server profiles do the following Configuring IBM Communication Server 7 1 Checklist for Configuring the Communications Interfaces 7 1 2 1 Sample Profile Definitions The SORACLE_HOME tg4drda sna commsvr subdirectory contains a set of sample IBM Communication Server definitions for the gateway created with the administration tool SNA definitions are very specific to the host and SNA network As such the sample def
293. w are the common Oracle Transparent Gateway for DRDA error codes that appear in the drc field of the expanded error messages If you obtain a drc value that does not appear here then contact Oracle Support Services 700 Invalid ORA_MAX_DATE specified Cause An invalid value was specified for ORA_MAX_ DATE in the initsid ora file Action Correct the value of ORA_MAX_ DATE The correct format is ORA_MAX_DATE YYYY MM DD where MM is in the range of 1 to 12 and DD is in the range of 1 to 31 and must be valid for the month 701 Default CCSID value not supported Cause The value specified for DRDA_DEFAULT_CCSID in the ini tsid ora file is not supported by the Oracle Transparent Gateway for DRDA Action Refer to Appendix D National Language Support for a list of supported DRDA Server character sets 702 Application Host bind variable exceeds 32K Cause An application program specified a host variable with length greater than the DRDA allowed maximum of 32K Action The application must be modified to take into account DRDA limits 703 Local character set not supported Cause The character set specified for the LANGUAGE parameter in the initsid ora file is not supported Action Refer to Appendix D National Language Support for a list of supported character sets 704 UserID length greater than maximum Cause The user ID used for the allocation of an APPC conversion by the gateway is lon
294. wing you to access any data using a uniform set of SQL Changes to the location storage characteristics or table structure do not require any changes to your applications ANSI and ISO standard SQL are supported along with powerful Oracle extensions 1 3 6 Data Definition Language Oracle Applications can create tables in target data stores by using native data definition language DDL statements 1 3 7 Data Control Language You can issue native data control language DCL statements from an Oracle environment allowing central administration of user privileges and access levels for heterogeneous data stores 1 3 8 Passthrough and Native DB2 SQL Execution of native DB2 SQL can be passed through the gateway for execution directly against DB2 This enables applications to send statements such as a DB2 CREATE TABLE to the gateway for execution on a target DB2 system Introduction 1 5 Gateway Capabilities 1 3 9 Stored Procedures The gateway enables you to exploit both Oracle and non Oracle stored procedures leveraging your investments in a distributed multi database environment Oracle stored procedures can access multiple data stores easily without any special coding for the heterogeneous data access Oracle Stored Procedures Oracle stored procedures enable you to access and update DB2 data using centralized business rules stored in the Oracle Database 10g Using Oracle stored procedures can increase your database per
295. word must be lesser than eight characters tns name entry specifies the Oracle Net TNS connect descriptor used to identify the gateway Guidelines for Database Links Database links are active for the duration of a gateway session If you want to close a database link during a session then use the ALTER session statement 12 1 2 Dropping Database Links You can drop a database link with the DROP DATABASE LINK statement For example to drop the public database link named DBLINK use the statement DROP PUBLIC DATABASE LINK dblink Note A database link should not be dropped if it is reguired to resolve an in doubt distributed transaction Refer to Oracle Database Administrator s Guide for additional information about dropping database links See Also Oracle Database Administrator s Guide for additional information about dropping database links 12 2 Oracle Transparent Gateway for DRDA Installation and User s Guide Accessing AS 400 File Members 12 1 3 Examining Available Database Links The data dictionary of each database stores the definitions of all the database links in that database The USER_DB_LINKS data dictionary view shows the defined database links The ALL_DB_LINKS data dictionary views show all accessible public and private database links 12 1 4 Limiting the Number of Active Database Links You can limit the number of connections from a user process to rem
296. work software before the gateway and server application programs begin their conversation and process conversation level security data If session level security is used then correct password information must be established in the HP9000 host Connection Profile and in similar parameter structures in the DRDA Server system that is to be accessed Refer to the appropriate SNA server product documentation for detailed information 8 7 1 SNA Conversation Security SNA conversation security is determined by the setting of the Gateway Initialization parameter DRDA_SECURITY_TYPE This parameter determines whether SNA security option SECURITY is set to PROGRAM or to SAME Generally the gateway operates Configuring SNAPlus2 8 11 Using SNA Session Security Validation under SNA option SECURITY PROGRAM but it can also be set to operate under SNA option SECURITY SAME SNA Security Option SECURITY PROGRAM If DRDA_SECURITY_TYPE PROGRAM is specified then the gateway allocates the conversation with SNA option SECURITY PROGRAM and sends this information to the DRDA Server u If the database link has explicit CONNECT information then the specified user ID and password are sent u Ifthe database link has no CONNECT clause and if the application has logged into the Oracle integrating server with an explicit user ID and password then the Oracle user ID and password are sent u Ifthe application logs in to the Oracle integratin
297. xist on a DRDA database by using the name that is defined in the database link For example assume that a database link is defined so that it names the DRDA database link DRDA and also assume that an application needs to retrieve data from an Oracle Database and from the DRDA database Use the following SQL statement joining two tables together in your application SELECT EMPNO SALARY FROM EMP L EMPS DRDA R WHERE L EMPNO R EMPNO Developing Applications 13 1 Using Oracle Stored Procedures with the Gateway In this example EMP is a table on an Oracle Database and EMPS is a table on a DRDA Server You can also define a synonym or a view on the DRDA Server table and access the information without the database link suffix m You can read and write data to a defined DRDA database SELECT INSERT UPDATE and DELETE are all valid operations u A single transaction can write to one DRDA database and to multiple Oracle Databases u Single SQL statements using JOINs can refer to tables in multiple Oracle Databases in multiple DRDA databases or in both 13 1 1 Fetch Reblocking Oracle Database supports fetch reblocking with the HS_RPC_FETCH_REBLOCKING parameter When the value of this parameter is set to ON the default the array size for SELECT statements is determined by the HS_RPC_FETCH_SIZE value The HS_RPC_FETCH_SIZE parameter defines the number of bytes sent with each
298. y SNA conversation security is determined by the setting of the Gateway Initialization parameter DRDA_SECURITY_TYPE This parameter determines whether SNA security option SECURITY is set to PROGRAM or to SAME Generally the gateway operates under SNA option SECURITY PROGRAM but it can also be set to operate under SNA option SECURITY SAME 6 8 1 SNA Security Option SECURITY PROGRAM If DRDA_SECURITY_TYPE PROGRAM is specified then the gateway allocates the conversation with SNA option SECURITY PROGRAM and sends information to the DRDA Server a If the database link has explicit CONNECT information then the specified user ID and password are sent u If the database link has no CONNECT clause and if the application has logged in to the Oracle integrating server with an explicit user ID and password then the Oracle user ID and password are sent u Ifthe application logs in to the Oracle integrating server with operating system authentication and if the database link lacks explicit CONNECT information then no user ID and password are sent If no user ID and password are sent and if the DRDA Server is not configured to assign a default user ID then the connection fails In general SECURITY PROGRAM tells the DRDA Server to authenticate the user ID password combination using whatever authentication mechanisms are available For example if DB2 OS390 is the DRDA Server then R
299. y Considerations 14 5 Passwords in the Gateway Initialization File 14 6 Oracle Transparent Gateway for DRDA Installation and User s Guide 15 Migration and Coexistence with Existing Gateways Migration to new instances of Oracle Transparent Gateway for DRDA from an existing installation is straightforward provided some guidelines This chapter covers how to make these new installations as easy as possible This chapter provides information that is specific to 10 2 release of the Oracle Transparent Gateway for DRDA This chapter contains the following sections u Migrating Existing V4 V8 or V9 Gateway Instances to New Release u Backout Considerations When Migrating to New Releases m New and Changed Parameters When Migrating to Release 10g u DRDA Server Considerations a Oracle Net Considerations 15 1 Migrating Existing V4 V8 or V9 Gateway Instances to New Release Migration is the process of converting an installed version of an Oracle Database into a later version This migration generally involves running the Oracle Migrate MIG utility to modify Oracle Database control file structures from the format of one version to the format of another version Upgrading is the process of converting an Oracle Database from an installed release into a later release of the same version For example transforming patch release 8 0 3 into patch release 8 0 4 is called upgrading Step 1 Install the New Release Install the new r

Oracle Transparent Gateway for DRDA Installation and User's Guide

Contents

Download Pdf Manuals

Related Search

Related Contents