JR32525: IN ORAWRITE OPERATOR, CONSTRAINT VIOLATION GENERATES "FATAL" LOGS BUT THIS DOES NOT ABORT THE JOB.

APAR status

• Closed as program error.

Error description

• When loading violating a constraint, the orawrite operator
  correctly reports error messages as the rebuild of the index(es)
  fails, but the job does not abort. The job should always abort
  if environment variable APT_ORA_FAIL_ON_INDEX_FAILURE is
  declared.
  

Local fix

• Use message handler to abort the job.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Oracle Enterprise stage. Configured for bulk load.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Job does not abort after fatal errors.
  ****************************************************************
  RECOMMENDATION:
  Apply this patch to resolve the issue.
  This change is included in 8.1 Fix Pack 1.
  ****************************************************************
  

Problem conclusion

• Job now aborts after errors are reported if
  APT_ORA_FAIL_ON_INDEX_FAILURE is specified.
  

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

• R751 PSN

     UP