PH35160: REPLICATION USING INTEGRATED SYNCHRONIZATION MAY FAIL WITH SQLCODE=-20570, SQLSTATE=22551

APAR status

• Closed as documentation error.

Error description

• When replication using Integrated Synchronization processes a
  table containing a column of type
  TIMESTAMP WITH TIME ZONE NOT NULL
  the replication may be suspended, the table state will be set to
  'ERROR'.
  The issue happens when more than 20.000 rows are inserted or
  deleted.
  The additional Db2 SQL Diagnostics show:
  "SQLCODE=-20570, SQLSTATE=22551,
  SQLERRMC=3188.0x0000000035280DCC18990002-0x0D2D0319-D.fifo.00063
  453.0036095.log
  The statement failed because the number of rejected rows exceeds
  the limit set in the MaxErrors option value. Log file name:
  log-file-name."
  The issue is accompanied by the following messages appearing in
  DB2MSTR:
  DSNX881I  ... 20 E 5109 ... Message: Error during write
  PipeWriterCallable
  DSNI090I  ...  DSNILGRT -STARTING ASYNCHRONOUS LOG READER TASK
  FOR SESSION ID  ...
  DSNI092I  ...  DSNILGRT -TIMEOUT CAUSED TERMINATION OF
  ASYNCHRONOUS LOG READER TASK FOR  SESSION ID ...
  A fix for this issue will be provided with maintenance level
  7.5.5.
  Additional keywords:
  TS004851335 InSync SQL20570N TIMESTAMP NOT NULL
  Github...Everest/customer-cases/issues/139
  

Local fix

• As a workaround we suggest to
  - limit the insert and deletes to a batch size of 20000 rows and
  updates to 10000 rows
  or
  - change the column definition: remove the 'NOT NULL' clause for
  the timestamp with timezone column
  

Problem summary

• Problem Summary:
  A table having got a column of type TIMESTAMP WITH TIMEZONE may
  be suspended from replication using Integrated Synchronization.
  
  Users Affected:
  Users of of replication based on Integrated Synchronization with
  an accelerator server maintenance level lower than 7.5.5.
  
  Problem Scenario:
  When a table having got a column of type TIMESTAMP WITH TIMEZONE
  with the specification NOT NULL is replicated the table may be
  suspended from replication. This happens when more than 20000
  inserts/deletes or 10000 updates are performed in one
  transaction.
  
  Problem Symptoms:
  The subject table is suspended from replication.
  

Problem conclusion

• This issue has been fixed with accelerator maintenance level
  7.5.5.
  Upgrade your maintenance level accordingly.
  

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

Applicable component levels