2
Release Information

This chapter contains release information for Oracle Access Manager for AS/400. It includes:

• Product Set

• Changes and Enhancements

• Known Problems and Restrictions

Product Set

The following products and component versions are included on the product tape.  All components are at production level.

• Oracle Access Manager for AS/400: 9.2.0.1.0

• Oracle Net, TCP/IP adapter: 9.2.0

Changes and Enhancements

Release 9.2.0.1.0

LONG and LONG RAW Datatypes

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".

Encryption

Saved passwords are encrypted.

Release 9.2.0.1.0

The following bugs have been fixed for this release of the Oracle Access Manager for AS/400:

Bugs Fixed as of This Release

• 2663341

  Defaults not being used when Oracle Number has precision and scale of zero.

• 2189517

  C2M1212 error messages in JobLog.

• 1947812

  MCH3601 error in QRWSARDB (apply IBM PTF SE02609 for OS/400 V5R1).  Refer to "PTF Requirements".

• 1670446

  Internal errors reported with SQL0969 do not have SQLSTATE field (in SQLCA) correctly set.

• 1630400

  MCH3601 in AM400_RID program.

• 1340863

  Lengths of default userid and password are limited to ten chars (they have been expanded to 31 chars).

• 1325197

  Enhance CRTORAPKG to include activation group specification.

• 1318943

  MCH3601 at statement 29 in ARDBIND.

• 1282791

  ORA-3106 when attempting to connect to server with UTF8 charset.

• 1219774

  MCH3601 in AM400_RIDI program.

• 1170151

  Procedure OUT parm incorrect.

• 1168479

  TGTRLS parameter added to CRTORAPKG panel.

• 1116738

  No data returned from final block fetch if rows < blksize.

• 970972

  CEE9901 MCH3601 WHEN USING STRSQL : LANGUAGE SET TO ES.

• 916836

  ZONED DECIMALS ARE LIMITED TO 16 DIGITS -- SHOULD BE 31.

Known Problems and Restrictions

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.

Problems

STRSQL on Columns of Type NUMBER

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:

Datatype *PKDEC (packed decimal)

Precision 7

Scale 2

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.

General Limitations

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:

1. Copy the relevant DELETE, SELECT, or UPDATE statement to a host variable.

2. PREPARE a statement from that host variable.

3. For a SELECT, DECLARE a cursor from that prepared statement.  Open the cursor, and then FETCH from that cursor.

4. For an UPDATE or DELETE, EXECUTE the prepared statement.

Stored Procedure Limitations

The following limitations are known to exist with Oracle stored procedure:

• The TIMESTAMP and TIME datatypes return the date only.

• You must use the DB2/400 DECLARE PROCEDURE statement in preparation to call an Oracle stored procedure from an AS/400 program.

• The DECLARE PROCEDURE statement must have the same number of arguments as the Oracle PL/SQL procedure. The input and output modes must also be the same.

• The SIMPLE CALL WITH NULLS phrase is not supported. The SIMPLE CALL phrase is supported.

Restrictions

PREPARE with a COMMIT or ROLLBACK Command

When using two-phase commit processing, COMMIT or ROLLBACK commands PREPARED as dynamic SQL statements are rejected with this error:

SQL0969: Error occurred while passing request to application requester 
driver program.

This information is available in the job log:

ARDARPS: cannot PREPARE a COMMIT or ROLLBACK

For additional information on two-phase commit processing, refer to Chapter 8, "Using Oracle Access Manager".

RDBCNNMTH Parameter set to *DUW

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.

Non-DML SQL Statements

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:

ORA-2089 COMMIT is not allowed in a subordinate session

COMMIT HOLD

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).

LONG and LONG RAW Datatypes

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.