| Oracle® Transparent Gateway for DRDA Installation and User's Guide 10g Release 1 (10.1.0.2.0) for Microsoft Windows Part Number B12010-01 |
|
|
View PDF |
| Oracle® Transparent Gateway for DRDA Installation and User's Guide 10g Release 1 (10.1.0.2.0) for Microsoft Windows Part Number B12010-01 |
|
|
View PDF |
This chapter provides information specific to this release of the Oracle Transparent Gateway for DRDA. It includes the following sections:
The following is a list of the production components that are included on the product CD-ROM:
Oracle Transparent Gateway for DRDA, Release 10.1.0.2.0
Oracle Net, Release 10.1.0.2.0
Following is a list of changes and enhancements that are unique to this release of the gateway.
This release of the gateway adds support for DB2 GRAPHIC and VARGRAPHIC datatypes. Refer to Chapter 12, " Developing Applications".
This release of the gateway adds support for DRDA Servers running on Microsoft Windows and Linux operating systems on Intel hardware.
This release of the gateway adds Oracle data dictionary support for DB2 UDB V7. Refer to "Sample SQL scripts " in Chapter 10, " Configuring the Gateway".
ORA-28500, DRC=-30020, ERRP=GDJMRCCH, ERRMC=124C ON SELECT FROM AS/400
GATEWAY CRASHES WHEN INVALID DATE IS USED IN TO_DATE : ORA-2068, ORA-28511
INVALID DB2 PASSWORD RETURNS BACK ERRNC 124C INSTEAD OF 1245
QA - IN DOUBT TRANSACTION FOR SNA/DRDA WHEN DROPPING AND CREATING TABLES
QA - ORA-1821 CAN NOT INSERT USING TO_DATE() THROUGH GATEWAY
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 Corporation office for information about accessing this online information.
This release of the gateway is not compatible with DB2/UDB V8. Contact Oracle Support Services and request status for bug number 3275652.
During testing of Oracle Transparent Gateway for DRDA Release 9.2 and Release 10, while trying to bind, the following results occurred:
SQL> execute gtw$_bind_pkg@hgolink; BEGIN gtw$_bind_pkg@hgolink; END; * ERROR at line 1: ORA-01403: no data found TG4DRDA v10.1.0.2.0 grc=0, drc=-30020 (839C,0000), errp=GDJMRC, errmc=1245 ORA-06512: at line 1
The SQL*Plus DESCRIBE command cannot be used to access the remote DRDA Server object information.
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 12, " Developing Applications", for information or limitations when developing your applications.
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.
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 11, " Using the Gateway", for more information.
The owner of DD basic tables and views is OTGDB2. This cannot be changed.
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 12, " Developing Applications", for details.
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 character sets that are used by a DRDA Server) is configurable via the gateway Codepage Map Facility. Refer to Appendix D, " National Language Support" for more information.
Refer to "DRDA Datatype to Oracle Datatype Conversion" for detailed information about datatypes.
Oracle Transparent Gateway for DRDA does not support the Oracle command SAVEPOINT.
Null values are not passed into, or returned from, calls to stored procedures through the gateway.
String concatenation of numbers is not allowed in DB2/400, DB2/UDB, and DB2/OS390. For example, 2||2 is not allowed.
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 parameters, HS_DB_DOMAIN and HS_DB_NAME, in the Gateway Initialization Parameter file to match the value of the Oracle server DB_DOMAIN parameter. Refer to Chapter 10, " Configuring the Gateway", for more information.
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 10, " Configuring the Gateway".
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. |
Because of a restriction of the DRDA architecture, rows with aggregate length exceeding 32K bytes in DRDA representation cannot be stored or retrieved.
SQL*Plus cannot fetch LONG columns from the Oracle Transparent Gateway for DRDA.
Currently the Oracle Transparent Gateway for DRDA provides SQL for defining DB2/OS390, 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.
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.
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 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
Oracle Transparent Gateway for DRDA does not support CONNECT BY in SELECT statements.
