JR37808: ORACLE CONNECTOR BY DEFAULT DROPS UNMATCHED COLUMNS FOR AUTO-GEN ERATED SQL STATEMENTS

APAR status

• Closed as program error.

Error description

• The job is using Oracle Connector stage with auto generated SQL
  UPDATE statement trying to update columns that are present on
  the link but do not exist in target database table.
  
  Oracle connector generates informational messages in Director
  log that those columns were dropped and the job finishes
  successfully instead of aborting.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  DataStage users who are utilizing Oracle Connector stage in
  their jobs.
  ****************************************************************
  PROBLEM DESCRIPTION:
  When the connector is configured to automatically generate
  INSERT, UPDATE or DELETE statement based on the column
  definitions on the input link and the provided table name, it
  default produces the statement text that references only those
  column names on the link for which corresponding column names
  exist in the target table. For the remaining unmatched columns
  on the input link the connector logs informational messages to
  inform the user that they were dropped. This is controlled by
  the connector property "Drop umatched fields" which by default
  is set to value "Yes".
  
  The default value for the "Drop unmatched fields" property
  should be set to "No" so that by default the connector stops
  the job and reports fatal error for any unmatched columns on the
  input link when auto-generating DML statements. Then if the user
  wants the connector to ignore the unmatched columns, the user
  can set the property value to "Yes".
  
  An additional issue addressed by this patch is related to the
  writing of native Oracle (OCI) messages to the job log. In
  certain cases, such as when reporting informational messages
  provided by Oracle for issues with the fetch operations, the
  connector would only log the Oracle error code and the error
  text would be truncated at the first character.
  
  ****************************************************************
  RECOMMENDATION:
  Install patch JR37808.
  ****************************************************************
  

Problem conclusion

• The default value for "Drop unmatched fields" property is now
  set to "No". The existing jobs are not affected and will have
  their existing value for this property preserved. The fix
  affects only the design of new jobs, since now the default
  value set for this property will be "No" while before it was
  set to "Yes".
  
  The logging of OCI messages was fixed. Now the complete Oracle
  message text is written to the log in certain scenarios in which
  it was previously truncated.
  

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

• R810 PSN

     UP