JR60806: ORACLE CONNECTOR JOBS ON SERVER CANVAS ARE NOT PADDING SPACE WHEN MAPPING FROM CHAR(X) TO CHAR(Y) WHERE X < Y

IBM InfoSphere Information Server, Version 11.7.1.1 (Fix Pack 1)
IBM InfoSphere Information Server, Version 11.7.1.1 for AIX
IBM InfoSphere Information Server, Version 11.7.1.1 for Windows
IBM InfoSphere Information Server, Version 11.7.1.1 for Linux

APAR status

• Closed as program error.

Error description

• Migrated OCI stage job to Oracle Connector job.
  Oracle  connector stage in Server job showed different behavior
  from OCI stage for update operation.
  If source char(7) column is mapped to target char(8) PK column,
  and the target stage is set to update (or upsert)
  (1) "OCI --> Transformer --> OCI" job
  Target OCI stage submits space padded value to Oracle (e.g.
  source value '1234567' became '1234567 ')
  (2) OraCC --> Transforemr --> OraCC
  Target Oracle Connector submits source value as is (that is, 7
  characters) and the update fails.
  If UpSert use, insert fails due to uniqueue constraint
  violation because Oracle pads a space when inserting.
  

Local fix

• Pad space in Transformer, e.g. using Fmt(input_col, "8 L")
  function before the target Oracle Connector stage.
  

Problem summary

• Oracle connector jobs on server jobs are not padding space when
  mapping from CHAR(X) to CHAR(Y) where X < Y
  

Problem conclusion

• OCI plugin is working fine in the similar scenario. Oracle
  connector code has to be changed considering the migration path
  even though the oracle connector is working as per the design.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• RB70 PSY

     UP

• RB71 PSY

     UP