JR41380: Add support for spatial datatypes like Oracle SDO_GEOMETRY

APAR status

• Closed as suggestion for future release.

Error description

• Enhancement request to add support for Spatial datatype eg,
  Oracle's SDO_GEOMETRY
  

Local fix

Problem summary

• Oracle Connector originally used a piece-wise write API for
  inserting data to LONG, LOB and XMLTYPE columns.  We use this
  mode to be able to write to LONG columns, which are deprecated
  by Oracle.  This mode has limitations when it comes to inserting
  to LOB and XMLTYPE columns.  Oracle did not keep the piece-wise
  write API up to date with these newer data types.  For LOB and
  XMLTYPE datatypes an alternate mechanism is to use Oracle OCI
  locators to push data to Oracle.
  
  At target end of job, customer is calling Oracle function
  SDO_UTIL.FROM_WKTGEOMETRY for which 1st argument can be VARCHAR2
  or CLOB type.  Customer uses LongNVarChar in DataStage for the
  SDO_GEOMETRY column.  Oracle will resolve the method based on
  the bind variable type OraCC chooses for this argument.   With
  piece-wise write API used today, Oracle will go with the
  VARCHAR2 argument and will hit the 4000 barrier.  If OraCC used
  OCI locator API, Oracle would resolve argument as CLOB and OraCC
  could push a value > 4000 characters via OCI locator.
  

Problem conclusion

• OCI LOB locator support has been added.
  

Temporary fix

Comments

• Apply patch for JR41380 and set environment variable
  CC_ORA_LOB_LOCATOR_COLUMNS to comma-delimited list of
  columns that should use OCI LOB locators (or special value
  of (all) to make use of OCI LOB locators for all LONGVARCHAR
  LONGNVARCHAR, and LONGVARBINARY columns.
  

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

  INFO SRVR PLATF

• Fixed component ID

  5724Q3612

Applicable component levels