IT05536: UPDATABLE RSS SERVER LEFT IN UPDATES BLOCKED STATE AFTER SMX DISCONNECT/RECONNECT

APAR status

• Closed as program error.

Error description

• It appears possible that after the smx connection is lost
  between the RSS and it's primary, when the RSS goes to
  reconnect, it can successfully reconnect at the smx level, but
  still leave the server in it's update blocked state.  In the
  MSGPATH file the following messages would be seen.
  
  First to show the disconnect you'd see the following:
  
  08:31:53  The SMX connection between high availability servers
  was closed because the
   peer server was unresponsive for the timeout period (60 seconds
  times the
   number of retries).
  08:31:53  The SMX connection between high availability servers
  was closed because the
   peer server was unresponsive for the timeout period (60 seconds
  times the
   number of retries).
  08:32:00  The SMX connection between high availability servers
  was closed because the
   peer server was unresponsive for the timeout period (60 seconds
  times the
   number of retries).
  08:32:01  RSS: Lost connection to pri
  08:32:01  Updates from secondary currently not allowed
  08:32:01  Updates from secondary currently not allowed
  08:32:01  Updates from secondary currently not allowed
  08:32:01  Updates from secondary currently not allowed
  
  The above shows the smx connection dropping, then the RSS
  reports the connection lost and then the updates blocked
  messages.
  
  Now if the updates get left in the blocked state, when the RSS
  connects you would only see something like this for the
  reconnect:
  
  08:32:12  RSS: Reconnected to pri
  
  However, if the updates were correctly unblocked you should also
  see messages like the following as well:
  
  08:29:28  Updates from secondary allowed
  08:29:28  Updates from secondary allowed
  08:29:28  Updates from secondary allowed
  08:29:28  Updates from secondary allowed
  
  Also, in the case where updates are blocked, in onstat -g ath
  there will be an absence of proxySync threads.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of updatable MACH11 Cluster.                           *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Update to IDS-12.10.xC5                                      *
  ****************************************************************
  

Problem conclusion

• Problem Fixed In IDS-12.10.xC5
  

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

  INFORMIX SERVER

• Fixed component ID

  5725A3900

Applicable component levels

• RC10 PSY

     UP