JR31964: TERADATA CONNECTOR BULK LOAD CAN INTERMITTENTLY FAIL WITH [IIS-CONN-TERA-005027] UNABLE TO ISSUE A CHECKPOINT AT 50 ROWS

APAR status

• Closed as program error.

Error description

• The problem is that a Teradata Connector bulk load can
  intermittently fail with the following error when run in
  parallel:
  
   [IIS-CONN-TERA-005027] Unable to issue a checkpoint at 50 rows
  because the master instance encountered an error
  (CC_TeraAdapter::doCheckpoint, file CC_TeraAdapter.cpp, line
  5,856) [pxbridge.C:2885]
  
  
  This problem involves a race condition in the Teradata
  Connector's checkpoint synchronization code, and it can happen
  if the player 0 process happens to be running a little faster
  than the other player processes.  One work around is to run the
  stage sequentially so that there is no synchronization required.
  In cases where you cannot run the stage sequentially without
  affecting performance, you can try changing the connector's Sync
  poll property.  The default of 0 means the connector will wait 1
  second between synchronization phases.  You can try setting that
  property to 2 or 3 or maybe 4 seconds.  That could slow down the
  player 0 process enough to avoid the race condition.  I wouldn't
  normally recommend changing that property, since it does slow
  down the starting and ending of the job, but you can try it for
  the jobs that are seeing this race condition.
  

Local fix

• Run sequentiall
  
  This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users using TDCC in "bulk" mode.
  ****************************************************************
  PROBLEM DESCRIPTION:
  TDCC "bulk" load jobs fail intermittantly.
  ****************************************************************
  RECOMMENDATION:
  This fix is included in Information Server 81 Fix Pack 1.
  Install the TDCC patch (or FP1) & also the patch for TPT
  library: "plod.08.02.00.03" or above.
  ****************************************************************
  

Problem conclusion

• Due to a bug in TDCC & also in the third package Teradata PT
  library.
  

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