|Oracle Access Manager Installation and User's Guide
Release 184.108.40.206.0 for IBM AS/400
Part Number A97616-01
This chapter contains release information for Oracle Access Manager for AS/400. It includes:
The following products and component versions are included on the product tape. All components are at production level.
Oracle LONG and LONG RAW columns can now be retrieved, subject to the IBM VARCHAR length limit (32,740 characters). Refer to "LONG and LONG RAW Datatypes".
Saved passwords are encrypted.
The following bugs have been fixed for this release of the Oracle Access Manager for AS/400:
Defaults not being used when Oracle Number has precision and scale of zero.
C2M1212 error messages in JobLog.
MCH3601 error in QRWSARDB (apply IBM PTF SE02609 for OS/400 V5R1). Refer to "PTF Requirements".
Internal errors reported with SQL0969 do not have SQLSTATE field (in SQLCA) correctly set.
MCH3601 in AM400_RID program.
Lengths of default userid and password are limited to ten chars (they have been expanded to 31 chars).
Enhance CRTORAPKG to include activation group specification.
MCH3601 at statement 29 in ARDBIND.
ORA-3106 when attempting to connect to server with UTF8 charset.
MCH3601 in AM400_RIDI program.
Procedure OUT parm incorrect.
TGTRLS parameter added to CRTORAPKG panel.
No data returned from final block fetch if rows < blksize.
CEE9901 MCH3601 WHEN USING STRSQL : LANGUAGE SET TO ES.
ZONED DECIMALS ARE LIMITED TO 16 DIGITS -- SHOULD BE 31.
The following problems and restrictions are known to exist in the Oracle Access Manager for AS/400 products on the product CD. The description of problems includes suggestions for dealing with them, when possible.
A current list of problems is available online. Contact your local Oracle Corporation office for information about gaining access to this list.
When using STRSQL, an ORA-1457 might occur on columns of type NUMBER where no precision or scale is specified. Oracle Access Manager supplies default datatypes precision and scale, for these situations. Even the use of these datatypes, however, may not be sufficient, and you could still receive the ORA-1457 error. To check the default datatype, precision and scale values use the Oracle Access Manager for AS/400 CHKSQLDFLT command.
The AS/400 is shipped with the following default settings:
For example, when using STRSQL, a column of type NUMBER with a value of 123456 results in an ORA-1457 error. To avoid this error, you can change the default datatype to *FLOAT or keep the datatype as *PKDEC and change the precision to 8 while keeping the default scale of 2.
Oracle hints cannot be specified in a SQL statement that is explicitly part of any EXEC SQL statement. The IBM preprocessor strips out the Oracle hints, as if they are comments.
If you want Oracle hints in a DELETE, SELECT, or UPDATE statement, you must:
The following limitations are known to exist with Oracle stored procedure:
When using two-phase commit processing, COMMIT or ROLLBACK commands PREPARED as dynamic SQL statements are rejected with this error:
This information is available in the job log:
For additional information on two-phase commit processing, refer to Chapter 8, "Using Oracle Access Manager".
Oracle Access Manager requires that the RDBCNNMTH parameter be set to *DUW for any SQL package that is preprocessed with any of the CRTSQLxxx commands.
When using two-phase commit processing, CONNECT is the only non-Data Manipulation Language (DML) SQL statement supported by Oracle Access Manager. Use of such non-DML statements results in this error:
The HOLD parameter on an EXEC SQL COMMIT HOLD command is not honored. All cursors are closed at each logical unit of work boundary (COMMIT and ROLLBACK).
Only the first 32,740 bytes in a LONG or LONG RAW column can be retrieved. This is because of the DB2/400 length limit on a LONG VARCHAR column. Also note that the total data length on a SELECTed row is 32,760 bytes. The maximum length for a LONG or LONG RAW column will be further diminished by the amount of data in the OTHER columns retrieved.