PH20802: USING ANALYTICS ACCELERATOR STUDIO THE REPLICATION STATUS OF A SUBSCRIPTION SHOWS 'ERROR' WITHOUT ANY PRECEDING REPL. ISSUES

APAR status

• Closed as documentation error.

Error description

• Using the Analytics Accelerator Studio the replication status
  for a certain subscription is suddenly shown as 'ERROR' without
  any preceding replication issues. From that moment onwards, the
  replication status will remain 'ERROR'. Starting and stopping of
  the replication in Analytics Accelerator Studio or restarting of
  the Capture Agent task in zOS side will not help. 
  The error may occur if more than one pairing with 'Incremental
  Update enabled' exists on a single accelerator.
  
  The following messages may be accompanying the issue and may be
  visible in CHCPRINT: 
   CHC6448W Communications link in link slot X has terminated
  abnormally
   CHC6503E Communications link to XXX.X.X.XXX:XXXXX abnormally
  terminated by remote system (link 1, process 1) terminated
   CHC6466E Remote system on session name in session slot number
  has failed to respond ...
  
  KEYWORDS:
  IDAA REPLICATION ERROR CHC6448W CHC6503E CHC6466E JR61803
  FILE HANDLE LEAK
  .
  Additional support information: 
  
  If a deeper analysis is made by IDAA support, errors are found
  in the Replication Engine trace which suggest that too many
  files are opened by the engine. The amount of those files grows
  with the time and at some point the engine in not responsive
  anymore.
  

Local fix

• The only way to get rid of the issue (i.e. the open files) is to
  use the following procedure:
  1. Stop replication for all replication enabled parings by
  calling stored procedure ACCEL_CONTROL_ACCELERATOR using command
  '<stopReplication/>'.
  2. Use the Analytics Accelerator Console and restart the
  Incremental Update processes as described here: 
  https://www.ibm.com/support/knowledgecenter/SS4LQ8_7.5.0/com.ibm
  .datatools.aqt.doc/installmanual/task/t_idaa_inst_incr_updt_rest
  art_subscriptions.html
  3.Start replication by calling stored procedure
  ACCEL_CONTROL_ACCELERATOR using command <startReplication/>.
  
  To prevent further occurrences of the issue (until a fix will be
  available) we recommend to perform the steps described
  below regularly (e.g. once or twice a week) after business
  hours.
  

Problem summary

• The fix for CDC APAR JR61803 is part of Replication
  Engine (RE) 11.4.0.2-5537 which was included in the 7.5.0.1
  maintenance level.
  

Problem conclusion

• The affected IDAA component was fixed.
  

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