2
Release Information

This chapter provides information specific to this release of the Oracle Transparent Gateway for IBM DRDA. It includes the following sections:

Product Set

The following table lists the production components that are included on the product CD-ROM:

Product	Release number
Oracle Transparent Gateway for IBM DRDA	9.2.0.1.0
Oracle Net	9.2.0.1.0

Changes and Enhancements, Release 9.2.0.1.0

Following is a list of changes and enhancements unique to this release of the gateway.

Password Encryption Utility

This release of the gateway includes a utility to support encryption of plain-text passwords in the gateway Initialization File. Refer to Chapter 15, "Security Considerations" for details.

Linux/390 support

This release of the gateway supports the Linux/390 platform. The supported DRDA network protocol is TCP/IP only.

Enhancements in Release 9.0.1

Enhancements

Support for DB2/OS390 V6 and V7 Stored Procedures

This release of the gateway supports the native stored procedure catalogs in DB2 V6 and DB2 V7 (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" in Appendix D, "National Language Support".

Improved Oracle Data Dictionaries

This release of the gateway ships with a set of improved data dictionary tables and views which help the gateway better integrate with the Oracle9i server.

Changes in Release 9.0.1

Following is a list of changes unique to release 9.0.1 of the gateway.

Oracle Server Dependencies

This release of the Oracle Transparent Gateway for IBM DRDA requires the latest released patch set for Oracle9i server release 9.2 or release 9.0.1, or Oracle8i server release 8.1.7.

Gateway Parameters

The syntax of initsid.ora has been simplified. Refer to Appendix C, "DRDA-Specific Parameters" for details.

Refer to the "Heterogeneous Services" section of Oracle9i Heterogeneous Connectivity Administrator's Guide for complete information about heterogeneous services.

TNSNAMES.ORA

The service name definition (from the Oracle integrating server to the gateway) must contain an extra parameter, (HS=). Refer to Chapter 11, "Configuring the Gateway", for additional information.

IBM DB2 Universal Database Support

This 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 IBM DRDA supports access to EBCDIC tables and ASCII tables. Refer to Appendix D, "National Language Support".

Read-Only Support

This release allows 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".

Table 2-1 Bugs Fixed in Release 9 of the Gateway

Bug Number	Description
1947548	QA - IN DOUBT TRANSACTION FOR SNA/DRDA WHEN DROPPING AND CREATING TABLES
1941672	QA - ORA-1821 CAN NOT INSERT USING `TO_DATE()` THROUGH GATEWAY
1927573	QA - COMMENTS IN `O2PC.SQL` ARE INCORRECT
1901348	QA - SELECT USING BIND VARIABLE IN `TO_DATE` FUNCTION FAILS WITH ORA-28511
1891118	ADD SUPPORT FOR DATA CONNECTION' SNAP-IX SNA PRODUCT
1878053	QA - ORA-28522 ERROR INITIALIZING HETEROGENEOUS CAPABILITIES
1806810	ORA-28511 on `SELECT TO_DATE` with bind variable
1755771	ORA-2057 in alert log when gateway connection fails
1755080	ORA-00942 and ORA-28506 querying data dictionary views
1729291	Support for character set EL8ISO8859P7 required for TG4DRDA for Solaris
1665037	ORA-04053 When `DRDA_DISABLE_CALL=FALSE` using oracle stored procedure
1422130	Support for character set AR8ISO8859P6 required for the Transparent Gateway for IBM DRDA on NT.
1376928	TG4DRDA does not support drda servers using code page 1252 (WE8MSWIN1252)
1366454	There was a Kernel core dump when running consecutive stored procedures to DB2/OS390.
1358377	ORA-28500 and DB2 error -301 received when using gateway with microfocus cobol.
1353699	Gateway debug version returned `errmc=124c`.
1336994	DB2 threads remained and TCP connection was still established after exiting Plus.
1255848	FDS_CLASS in `DRDAAS400.sh`
1255698	Binding FDRDA gateway package
1211368	-30020 Trying to connect to AS/400 using TCP/IP with DRDA
1149824	Deinstalling Oracle Transparent Gateway for IBM DRDA.
1033074	Port of base bug 661051 to Oracle Transparent Gateway for IBM DRDA product.
992511	Any statement hangs on SQL*Plus via tg4drda
940538	Oracle Transparent Gateway for IBM DRDA would hang when executing `GTW$_BIND_PKG bind` package.
917951	Unsuccessful execution deadlock or timeout
903732	Update to table in fds with large number
887219	Insert NULL to DB2

Known Problems

The problems documented in the following section are specific to the Oracle Transparent Gateway for IBM 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 Corporation office for information about accessing this online information.

Compatibility with DB2/UDB

This release of the gateway is not compatible with DB2/UDB for Microsoft Windows or DB2/UDB for Linux.

Known Restrictions

The following restrictions are known to exist for the products in this release. Restrictions are not scheduled to change in future releases. Also refer to Chapter 14, "Developing Applications", for information or limitations when developing your applications.

SQL*Plus DESCRIBE command

The SQL*Plus DESCRIBE command cannot be used to access the remote DRDA server object information.

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 server to a DRDA server, the Oracle SQL command INSERT is not supported. The SQL*Plus COPY command must be used. Refer to Chapter 13, "Using the Gateway", for more information.

DB2 Considerations

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 Server in ways that are not compatible with a DRDA server database, such as DB2/OS390. Therefore, the SUBSTR function is post-processed. However, it is possible to allow the server to process it natively using the "Native Semantics" feature. Refer to Chapter 14, "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 via the gateway's Codepage Map Facility. Refer to Appendix D, "National Language Support" for more information.

Character Set Limitation

Oracle Transparent Gateway for IBM DRDA does not support access to double-byte character set (DBCS) data.

Datatype Limitations

Refer to "DRDA Datatype to Oracle Datatype Conversion" for detailed information about datatypes.

SAVEPOINT Command Is Not Supported

Oracle Transparent Gateway for IBM DRDA does not support the Oracle command 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/OS390. For example, 2||2 is not allowed.

GLOBAL_NAMES Initialization Parameter

If GLOBAL_NAMES is set to TRUE in the Oracle server 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 Oracle server's DB_DOMAIN parameter. 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 ORACLE2PC 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 SQL expression forms do not work correctly with the gateway because of DRDA server limitations:

date + number 
number + date 
date - number 
date1 - date2

DRDA servers do not allow number addition or subtraction with date datatypes. 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.

Also, DRDA servers do not perform date subtraction consistently. When you subtract two dates (date1 - date2), differing interpretations of date subtraction in the DRDA servers 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 32K bytes in DRDA representation cannot be stored or retrieved.

LONG Datatype in SQL*Plus

SQL*Plus cannot fetch LONG columns from the Oracle Transparent Gateway for IBM DRDA.

Dictionary Views Are Not Provided for DB2/VM or DB2/UDB

Currently the Oracle Transparent Gateway for IBM DRDA provides SQL for defining DB2/OS390 and DB2/400 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 and DB2/UDB are not provided in this release.

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 re-installed, 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's Initialization Parameters must occur at this point to ensure proper gateway operation. If you wish to have both SNA and TCP/IP DRDA Network Interfaces installed, then you must create two separate gateway homes and installations.

SQL Limitations

Oracle ROWID Column

DB2 does not have a column equivalent to the Oracle ROWID column. Because the ROWID column is not supported, the following restrictions apply:

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 servers 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 IBM DRDA does not support CONNECT BY in SELECT statements.

2 Release Information