IT32627: LWJDBC WITH ORACLE SYS_GUID() QUERY RETURNING DIFFERENT RESULT

APAR status

• Closed as program error.

Error description

• In 5241, this would return what looks like a hex value similar
  to this:
  
  2753B605C9084EA98B4131751BB44052
  
  After they upgraded
  to 6.0.1, the same query returns the data in a different format
  (raw?) similar to this:
  
  [B@c210d010
  

Local fix

Problem summary

• Users Affected:
  
  All
  
  
  
  Problem Description:
  
  The LWJDBC query
  that uses the Oracle SYS_GUID() built-in function to select a
  unique identifier:
  
  SELECT SYS_GUID() FROM DUAL
  
  In 5241, this returns a hex value similar
  to this:
  
  2753B605C9084EA98B4131751BB44052
  
  After upgrading to 6.0.1, the same query returns the data in
  a different format similar to this:
  
  [B@c210d010
  
  
  
  
  
  
  
  Platforms Affected:
  
  All
  

Problem conclusion

• Resolution Summary:
  A code fix is provided.
  Fixed the problem by handling new meta data jdbc sql type for
  the query.
  
  
  
  Delivered in:
  
  6000005
  6000303
  6000203
  

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

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels