Skip Headers
Oracle® Application Server for DRDA User's Guide
12c Release 1 (12.1) for Linux x86-64

E27316-06
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

12 Restrictions on Using Oracle Application Server for DRDA

This section discusses restrictions and workarounds that can be used when customizing or maintaining in Oracle Database applications that were originally designed for IBM DB2.

This chapter contains these topics:

Resynch Manager

Oracle Application Server for DRDA supports Sync Point Manager services for Distributed Units of Work. It also supports Resynchronization Manager services for resynchronization during migrations that use a source Sync Point Manager without a log.

This release of Oracle Application Server for DRDA does not support active in-doubt transaction resolution services. Transactions that have been migrated and are in-doubt require manual resolution between the client system and Oracle Database. See Oracle Database Administrator's Guide for information on manual resolution of in-doubt transactions.

Cursor HOLD Attribute Semantics

Cursors marked with the HOLD attribute have the following restrictions:

  1. Under Remote Unit of Work (RUOW), cursors that have been prepared with the FOR UPDATE clause are implicitly closed on COMMIT or ROLLBACK.

  2. Under Distribute Unit of Work (DUOW), all cursors are implicitly closed if any updates occur to the server containing the open cursor on COMMIT or ROLLBACK.

DB2 Password Blank Padding

When passwords are encrypted and sent through DRDA, DB2 for z/OS inserts blank spaces into passwords that have less than 8 characters. This results in a log-on failure, error ORA-01017. Oracle recommends that user account passwords be at least 8 characters long.

DATE Data Type

Oracle DATE data type contains a time component that DRDA DATE data type does not support. Operating on Oracle DATE data may not yield expected results if the DATE data contains a time component. For consistency, do not store a time component when inserting DATE data using Oracle native DATE syntax. Alternatively, remap the DATE column to TIMESTAMP.

Oracle Object-Relational Data Types

This release does not support queries on objects that contain columns defined through Object-Relational data types.

This release does not support calling SQL procedures defined through Object-Relational data types for their input or return arguments.

TIMESTAMP Data Type

Oracle Application Server for DRDA represents TIMESTAMP with a fixed precision of 6 decimal places.

For compatibility reasons, extra care should be exercised when using TIMESTAMP data, and programmatic adjustments, such as type casting, may have to be made. See Oracle® Database SQL Language Reference for information about casting with the TIMESTAMP data type.

TIMESTAMP WITH TIMEZONE Data Type

Representation of TIMESTAMP WITH TIMEZONE is significantly different between Oracle Database and DB2.

Oracle Application Server for DRDA represents TIMESTAMP WITH TIMEZONE according to Oracle's presentation rules. For best compatibility between client and server, use four digit time zone suffix notation instead of written timezone description notation, such as -08:00.

XML Data Type

The DRDA XML data type (988, 989) is not supported as a program or bind variable data type in this release.

SYS.XMLType Data Type

The Oracle XML data type, SYS.XMLType, is not supported in this release.