IT41960: THE DATADIRECT ORACLE ODBC DRIVER INCORRECTLY RESOLVES TIMESTAMP(S)

APAR status

• Closed as change to accomodate OEM Vendor's code.

Error description

• When two (or more) calls are made to the oracle 'TO_TIMEZONE_TZ'
  function in a single SQL statement
  
  then the first parameter of the first call to the function is
  incorrectly described and bound.
  
  If only a single call is made to the oracle 'TO_TIMEZONE_TZ'
  function the error does not occur.
  
  For example
  INSERT INTO MY_TABLE (DATE1, DATE2) VALUES
  (TO_TIMESTAMP_TZ(?,?), TO_TIMESTAMP_TZ(?,?))
  will result an error like this when it is executed
  [IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01852:
  seconds must be between 0 and 59
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of App Connect Enterprise Version 11 or Version 12 who
  use the Oracle database TO_TIMEZONE_TZ function.
  
  
  Platforms affected:
  AIX, Linux on Power platform, Linux on x86-64 platform, Linux on
  zSeries platform, Windows on x86-64 platform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When two (or more) calls are made to the oracle 'TO_TIMEZONE_TZ'
  function in a single SQL statement the first parameter of the
  first call
  to the function is incorrectly described and bound.
  
  INSERT INTO MY_TABLE (DATE1, DATE2) VALUES
  (TO_TIMESTAMP_TZ(?,?), TO_TIMESTAMP_TZ(?,?))
  will result an error like this when it is executed
  [IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01852:
  seconds must be between 0 and 59
  

Problem conclusion

• A new DataDirect Oracle ODBC driver that fixes the error is now
  supplied with App Connect Enterprise.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels