JR61803: IIDR GENERATES A FILE DESCRIPTOR LEAK ONLY WHEN MULTIPLE INSTANCES ARE RUNNING FROM SAME INSTALLATION.

APAR status

• Closed as program error.

Error description

• InfoSphere Data Replication instances may produce a File handle
  leak  when multiple IIDR instances are running from the same
  product installation.
  
  Problem Identificaiton:
  IIDR instances may fail with an exception:
  processUnhandledException()   An uncaught exception has
  occurred: <86>java.lang.AssertionError
  java.lang.RuntimeException: The alias "{0}" was not found.|  at
  com.datamirror.ts.metadata.MetadataManager.getCustomerDatabasePa
  rams(MetadataManager.java:3778)| ...
  
  With the following Cause lower in the stack trace :
  Caused by: java.io.FileNotFoundException
  /opt/ibm/dwa/ext/iu/ReplicationEngineforIBMDB2/keystore/secrets.
  b64 (Too many open files)|...
  
  
  This behavior may also be identified prior to failure by
  examining OS level open file handles  on the   secrets.b64
  file.     lsof -p <PID> | grep secrets     may be one way to
  help check if the # of file descriptors is increasing or very
  high.
  

Local fix

• Work Around:
  If monitoring the file handle usage can be done proactively,
  stopping and restarting could be done.
  Stop all subscriptions and restart the IIDR Instance affected.
  Then restart Instance and subscriptions to resume mirroring
  
  Otherwise  the failure will cause the subscriptions and instance
  to possibly end on error and require a restart.
  
  IIDR will be able to operate for some time until the file handle
  limit is reached again.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * This issue affects clients using CDC replication engines     *
  * 11.4.0.1-5101 through IDR 11.4.0.2-5521.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Processing TLS encryption profiles caused a file descriptor  *
  * leak.                                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to IDR LUW 11.4.0.2-5522 or newer.                   *
  ****************************************************************
  

Problem conclusion

• Upgrading to IDR LUW 11.4.0.2-5522 or newer resolves the issue.
  

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

  IS DATA REPLICA

• Fixed component ID

  5725E3000

Applicable component levels

• RB40 PSY

     UP