JR32828: ORACLE CONVENTIONAL LOAD SHOULD ALLOW TRIGGER TO RESOLVE NOT NUL

APAR status

• Closed as program error.

Error description

• Customer want to use oracle trigger to fill in not null column,
  which means DataStage does not need to provide any value.
  Current software functionality checks that all not null columns
  exist and this is not desirable.  Customer is using conventional
  path load which fires trigger.  Could use upsert or ODBC but
  those do not allow open/close commands.
  

Local fix

• use upsert to insert data or ODBC stage.
  
  This fix is included in 8.0.1 fix pack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  none. minor enhancement.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Customer want to use oracle trigger to fill in not null column,
  which means DataStage does not need to provide any value.
  Current software functionality checks that all not null columns
  exist and this is not desirable.  Customer is using
  conventionalpath load which fires trigger. Could use upsert or
  ODBC but     those do not allow open/close commands.
  ****************************************************************
  RECOMMENDATION:
  apply patch provided.
  This change is included in 8.1 Fix Pack 1.
  ****************************************************************
  

Problem conclusion

• Enhanced load method. Now it does not warn or error if a column
  with NOT NULL column is not loaded values from DS. Loader
  sessions fail unless the column has a default value or is
  handled specially by an before-insert trigger. Load will be in
  conventional  path facilitate user in these cases.
  

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

• R801 PSN

     UP