PM30808: NAMESTORE.XML IS REMOVED FROM THE NODE AFTER THE INSTALL OF FIXPACK 7.0.0.13/PM14708

7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• Client has a successful install of fixpack 7.0.0.13 and finds
  that the namestore.xml file has been deleted from the node.
  namestore.xml in the node is used to store persistent bindings.
  The nodeagents systemout.log shows the following entry -
  -
  [12/14/10 18:01:53:609 CET] 00002246 FileRepositor A ADMR0017I:
  User XXXCustomRegistry/wasys deleted document
  cells/xebk701/nodes/xdaps301_1/namestore.xml
  

Local fix

• By design, the namestore.xml doesn't get synced from dmgr to
  node
  because the master copy is kept at the node level. Therefore
  doing
  subsequent syncNode would not make a difference in this case. If
  the
  namestore.xml that is at the dmgr level contains the bindings
  they need,
  they can copy it from dmgr and use it to recover those.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All V7 WebSphere Network Deployment         *
  *                  customers who use node level persistent     *
  *                  namestore bindings or synchronization       *
  *                  service exclusions.                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: Any file that is in the node            *
  *                      synchronization exclusion list is       *
  *                      being deleted from the node repository  *
  *                      during synchronization after            *
  *                      upgrading to 7.0.0.13. This includes    *
  *                      the namestore.xml file which is         *
  *                      automatically in the exclusion list.    *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A nodeagent trace will show the file is being deleted, example
  log below:
  [1/13/11 13:04:20:445 CET] 00000020
  NodeSync < invokeGetFolderSyncUpdate
  Exit
  ...
  cells/myCell/nodes/myNode/namestore.xml
   deleted
  cells/myCell/nodes/myNode/xxxxx.xml
  deleted
  cells/myCell/nodes/myNode/plugin-cfg.xm
  l deleted
  ...
  This is only an issue if the file shown above is in the
  exclusion list.
  Example what to look for in nodeagent.xml for exclusion list
  is below:
  <fileSynchronizationService
  xmi:id="ConfigSynchronizationService_11
  62465673595" enable="true"
  synchInterval="1"
  autoSynchEnabled="true"
  synchOnServerStartup="false">
  <exclusions>cells/askbpoif01pCell01/nod
  es/askbpoif01pNode1/servers/IFsrv01/plu
  gin-cfg.xml</exclusions>
  </fileSynchronizationService>
  

Problem conclusion

• Code was updated to correct this problem.
  
  The fix for this APAR is currently targeted for inclusion in
  fixpack 7.0.0.17. Please refer to the recommended updates page
  for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  .
  *** Note: see APAR PM34232 for the V6.1 equivalent of this fix
  

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

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R700 PSY

     UP