PH36776: WAITFORDATA QUERIES SEEM TO GET A TIME PENALTY WHEN INTEGRATED SYNCHRONIZATION IS USED AS REPLICATION METHOD.

APAR status

• Closed as documentation error.

Error description

• WAITFORDATA Queries seem to get a time penalty when Integrated
  Synchronization is used as replication method.
  The execution of a WAITFORDATA query using accelerator V5 may
  take 13 seconds while in V7 (with Integrated Synchronization as
  replication method) it takes 27 seconds.
  
  A fix for this issue will be delivered with accelerator
  maintenance level 7.5.6.
  
  Additional keywords:
  TS005409504 HTAP WAITFORDATA QUERY
  Github...Everest/Customer-Cases/issues/163
  

Local fix

Problem summary

• Users affected:
  Users submitting WaitforData queries while Integrated
  Synchronization is used as replication method.
  
  Problem scenario:
  WAITFORDATA Queries seem to get a time penalty when Integrated
  Synchronization is used as replication method. The execution of
  a WAITFORDATA query using accelerator V5 may take 13 seconds
  while in V7 (with Integrated Synchronization as replication
  method) it takes 27 seconds.
  
  Problem Summary:
  Some internal meta data persistency operations that go on
  concurrently interfere with WAITFORDATA queries and slow
  them down with a penalty between 20s and 30s.
  With maintenance level 7.5.6 this interference has been removed.
  

Problem conclusion

• Upgrade your accelerator maintenance level to 7.5.6 or higher.
  

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