JR29247: ERROR MESSAGE WHEN USING DB2 EE STAGE (DB2UPSERT) IN DATASTAGE: `RECORD_TYPE' IS NOT AN ORCHESTRATE INSERT FIELD

APAR status

• Closed as requirement.

Error description

• Datastage - DB2 Upsert problem
  
  When DB2 EE stage and using "user defined sql", the user gets
  the following error:
  
  Table_Upsert: DB2Error: The Orchestrate update
  field
  `RECORD_TYPE' is
  not an Orchestrate insert field. ￭db2Upsert.C:903
  Customer would like for upsert (DB2EE Stage, ODBC Enterprise
  Stage and
  ODBC Connector Stage) to support the use of distinct columns in
  insert
  versus update.
  Example of Customer:s user-defined sql:
  INSERT INTO BLUMCA01.PGTEST (
  CONT_ID,
  CONT_EQUIV_ID,
  ADMIN_SYS_TP_CD,
  ADMIN_CLIENT_ID,
  DESCRIPTION,
  LAST_UPDATE_DT,
  LAST_UPDATE_USER) VALUES (ORCHESTRATE.CONT_ID,
  ORCHESTRATE.CONT_EQUIV_ID, ORCHESTRATE.ADMIN_SYS_TP_CD,
  ORCHESTRATE.ADMIN_CLIENT_ID, ORCHESTRATE.DESCRIPTION,
  ORCHESTRATE.LAST_UPDATE_DT, ORCHESTRATE.LAST_UPDATE_USER)'
  -update '
  UPDATE BLUMCA01.PGTEST SET
  CONT_EQUIV_ID = ORCHESTRATE.CONT_EQUIV_ID,
  ADMIN_SYS_TP_CD = ORCHESTRATE.ADMIN_SYS_TP_CD,
  ADMIN_CLIENT_ID = ORCHESTRATE.ADMIN_CLIENT_ID,
  DESCRIPTION = ORCHESTRATE.DESCRIPTION,
  LAST_UPDATE_DT = ORCHESTRATE.LAST_UPDATE_DT,
  LAST_UPDATE_USER = ORCHESTRATE.LAST_UPDATE_USER
  WHERE (CONT_ID = ORCHESTRATE.CONT_ID AND orchestrate.RECORD_TYPE
  =
  \'U\')'
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• this enhancement accepted as of now
  

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