JR36567: MULTIPLE ORAWRITE STAGES IN JOB CORRUPT WORK FILES AND JOB FAILS

Download Fix Pack 2 for InfoSphere Information Server Version 8.1

APAR status

• Closed as program error.

Error description

• MULTIPLE ORAWRITE STAGES IN JOB CORRUPT WORK FILES AND JOB FAILS
  

Local fix

• This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Windows
  ****************************************************************
  PROBLEM DESCRIPTION:
  MULTIPLE ORAWRITE STAGES IN JOB CORRUPT WORK FILES AND JOB FAILS
  
  ****************************************************************
  RECOMMENDATION:
  apply patched librrary.
  ****************************************************************
  

Problem conclusion

• To make work file sets unique to the operator, we are using the
  timestamp (with microsecond granularity) as a part of tile name.
   But this is failing on windows leading to collision of  work
  files.
  
  Avoid using timestamp values to make unique file sets.  Use an
  instance count instead.  We can have a static counter because
  this is all with in one process shared across a set of combined
  to serve multiple orawrite operators.
  This resolves the issue of file name collisions which is behind
  work file corruption leading to job failures.
  

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