WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Wrongly synced to dmgr

    Posted 11/15/16 02:40 AM

    Hi All,

    There are two dmgr's running in my environment instead of syncing it to dmgr1 i have done it to dmgr2. how could i justify this issue. Please suggest.

    kalyan.



  • 2.  RE: Wrongly synced to dmgr

    Posted 11/15/16 11:23 AM

    Hi Kaylan,

      I'm not sure how do you do to sync to different DMGR.
     
      I have done the next test (WAS ND 8.5.5.7 Windows7).
     
        DMGR1 (GABICell01) with 2 nodes federated (AppSrv01 and AppSrv02)
        DMGR2 (GABICell03)
        
        From AppSrv02 I have done syncNode to DMGR2 an I'm getting the next message at syncnode.log
        


        [11/15/16 17:12:34:151 CET] 00000001 NodeSyncUtili 3   Local node belongs to cell GABICell01, the cell to sync from is GABICell03
        [11/15/16 17:12:34:151 CET] 00000001 AdminTool     E   ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU0005E: Error synchronizing repositories {0}

     So, do your DMGR1 and DMGR2 have the same CELLNAME?

    Regards


  • 3.  RE: Wrongly synced to dmgr

    Posted 11/16/16 05:22 PM

    You can only has one Dmgr in a cell, and you should have one unique <deploymgr port>. 



  • 4.  RE: Wrongly synced to dmgr

    Posted 11/28/16 04:31 AM

    Hi,

    You can try to delete the node and try to add with the new node. May be that will help

    Thanks.



  • 5.  RE: Wrongly synced to dmgr

    Posted 11/30/16 09:22 AM

    I do not think it is wise to remove a node from a cell, as this can lead to loss of configuration which cannot be recovereed. We need more details on what exactly has occured in this situation to determine the best course of action.



  • 6.  RE: Wrongly synced to dmgr

    Posted 11/30/16 09:29 AM

    Hi Kalyan,

    The sync operation will not impact the configuration data in your dmgr, so you could possibly just sync the node back to the correct dmgr and that would correct your issue.

    Otherwise, I suggest the following two solutions:

    1) If you have a backup of the node profile before the sync to the wrong dmgr, you could restore from the backup, and then sync it back to the correct dmgr.

    OR

    2) If you do not have a backup (or want an alternate solution), then you can "recover" the node using the method described here:

    http://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.nd.doc/ae/tagt_addNode_asExistingNode.html

    Regards,

    Gary Vacek