Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
11 replies Latest Post - ‏2011-06-08T14:10:56Z by DanaDuffield
dysonbags
dysonbags
24 Posts
ACCEPTED ANSWER

Pinned topic Migration problem

‏2011-05-27T14:53:55Z |
I'm trying to migrate my old 6.1 federated node to 8.0. using the Migration Management Tool for z/os v 8.0. I get to the BBOWMPOS job and there I'm consistently getting this error
MIGR0304I: The previous WebSphere environment is being merged into this profile.
MIGR0428E: Incorrect Deployment Manager connection established.
com.ibm.ws.migration.utility.UpgradeException: MIGR0428E: Incorrect Deployment Manager connection established.
at com.ibm.ws.migration.postupgrade.Federated.DMgrConnectionInfo.initializeAdminClient(DMgrConnectionInfo.java:331)
at com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederatedImpl.getCorrectRepositoryForScenario(ConfigRepositoryConnectionFederatedImpl.java:203)
at com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederatedImpl.getConfigRepository(ConfigRepositoryConnectionFederatedImpl.java:167)
at com.ibm.ws.migration.document.ConfigRepositoryDocumentCollectionFederatedHelper.instantiateRepository(ConfigRepositoryDocumentCollectionFederatedHelper.java:72)
at com.ibm.ws.migration.document.ConfigRepositoryDocumentCollectionFederatedHelper.instantiateRepositoryForced(ConfigRepositoryDocumentCollectionFederatedHelper.java:56)
at com.ibm.ws.migration.postupgrade.Restore.<init>(Restore.java:284)
at com.ibm.ws.migration.postupgrade.WASPostUpgrade.restore(WASPostUpgrade.java:269)
at com.ibm.ws.migration.postupgrade.WASPostUpgrade.main(WASPostUpgrade.java:576)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:232)
at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:94)
at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:370)
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:140)
MIGR0272E: The migration function cannot complete the command.

In the Infocenter, the explanation for the error message says that I need to start the DM for the node to be migrated. I've taken that to mean the node I'm migrating from (i.e. the v6.1 node). Is that what it actually means? I find the wording rather ambiguous.

Anyone got any ideas?
Updated on 2011-06-08T14:10:56Z at 2011-06-08T14:10:56Z by DanaDuffield
  • SystemAdmin
    SystemAdmin
    462 Posts
    ACCEPTED ANSWER

    Re: Migration problem

    ‏2011-05-27T15:15:05Z  in response to dysonbags
    Hi,

    Sorry for the confusion, you need to have the v8.0 DMgr started, not the v6.1 DMgr

    DanaDuffield
    • dysonbags
      dysonbags
      24 Posts
      ACCEPTED ANSWER

      Re: Migration problem

      ‏2011-05-27T15:22:45Z  in response to SystemAdmin
      Just beginning to come to that conclusion. Will try it.

      Perhaps the documentation could be clearer?

      Cheers
      Graham
    • dysonbags
      dysonbags
      24 Posts
      ACCEPTED ANSWER

      Re: Migration problem

      ‏2011-05-27T15:33:06Z  in response to SystemAdmin
      No, that doesn't work either. It's trying to connect to port 13510 which is the SOAP port of the 6.1 DMGR, and as that is down, it can't connect. Should both DMGRs be up?

      Cheers
    • dysonbags
      dysonbags
      24 Posts
      ACCEPTED ANSWER

      Re: Migration problem

      ‏2011-05-27T15:33:50Z  in response to SystemAdmin
      MIGR0304I: The previous WebSphere environment is being merged into this profile.
      MIGR0380E: The JMX connection is not established with the deployment manager node mvs4.gb.tntpost.com, using connector type of SOAP on port 13510. The WASPostMigration program is now closing. No changes are made to the local Application Server environment.
      com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host mvs4.gb.tntpost.com at port 13510.
      MIGR0272E: The migration function cannot complete the command.
      ==============================================================================================================
      SUMMARY OF WASPostUpgrade
      ==============================================================================================================

      MIGR0304I: The previous WebSphere environment is being merged into this profile.
      MIGR0428E: Incorrect Deployment Manager connection established.
      com.ibm.ws.migration.utility.UpgradeException: MIGR0428E: Incorrect Deployment Manager connection established.
      at com.ibm.ws.migration.postupgrade.Federated.DMgrConnectionInfo.initializeAdminClient(DMgrConnectionInfo.java:331)
      at com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederatedImpl.getCorrectRepositoryForScenario(ConfigRepositoryConnectionFederatedImpl.java:203)
      at com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederatedImpl.getConfigRepository(ConfigRepositoryConnectionFederatedImpl.java:167)
      at com.ibm.ws.migration.document.ConfigRepositoryDocumentCollectionFederatedHelper.instantiateRepository(ConfigRepositoryDocumentCollectionFederatedHelper.java:72)
      at com.ibm.ws.migration.document.ConfigRepositoryDocumentCollectionFederatedHelper.instantiateRepositoryForced(ConfigRepositoryDocumentCollectionFederatedHelper.java:56)
      at com.ibm.ws.migration.postupgrade.Restore.<init>(Restore.java:284)
      at com.ibm.ws.migration.postupgrade.WASPostUpgrade.restore(WASPostUpgrade.java:269)
      at com.ibm.ws.migration.postupgrade.WASPostUpgrade.main(WASPostUpgrade.java:576)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:232)
      at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:94)
      at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:75)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
      at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
      at org.eclipse.core.launcher.Main.run(Main.java:977)
      at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:370)
      at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:140)
      MIGR0272E: The migration function cannot complete the command.
      MIGR0304I: The previous WebSphere environment is being merged into this profile.
      MIGR0380E: The JMX connection is not established with the deployment manager node mvs4.gb.tntpost.com, using connector type of SOAP on port 13510. The WASPostMigration program is now closing. No changes are made to the local Application Server environment.
      com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host mvs4.gb.tntpost.com at port 13510.
      com.ibm.ws.migration.utility.UpgradeException: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host mvs4.gb.tntpost.com at port 13510.
      at com.ibm.ws.migration.postupgrade.Federated.DMgrConnectionInfo.initializeAdminClient(DMgrConnectionInfo.java:342)
      at com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederatedImpl.getCorrectRepositoryForScenario(ConfigRepositoryConnectionFederatedImpl.java:203)
      at com.ibm.ws.migration.utility.ConfigRepositoryConnectionFederatedImpl.getConfigRepository(ConfigRepositoryConnectionFederatedImpl.java:167)
      at com.ibm.ws.migration.document.ConfigRepositoryDocumentCollectionFederatedHelper.instantiateRepository(ConfigRepositoryDocumentCollectionFederatedHelper.java:72)
      at com.ibm.ws.migration.document.ConfigRepositoryDocumentCollectionFederatedHelper.instantiateRepositoryForced(ConfigRepositoryDocumentCollectionFederatedHelper.java:56)
      at com.ibm.ws.migration.postupgrade.Restore.<init>(Restore.java:284)
      at com.ibm.ws.migration.postupgrade.WASPostUpgrade.restore(WASPostUpgrade.java:269)
      at com.ibm.ws.migration.postupgrade.WASPostUpgrade.main(WASPostUpgrade.java:576)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at com.ibm.wsspi.bootstrap.WSLauncher.launchMain(WSLauncher.java:232)
      at com.ibm.wsspi.bootstrap.WSLauncher.main(WSLauncher.java:94)
      at com.ibm.wsspi.bootstrap.WSLauncher.run(WSLauncher.java:75)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
      at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
      at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
      at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
      at java.lang.reflect.Method.invoke(Method.java:611)
      at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
      at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
      at org.eclipse.core.launcher.Main.run(Main.java:977)
      at com.ibm.wsspi.bootstrap.WSPreLauncher.launchEclipse(WSPreLauncher.java:370)
      at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:140)
      Caused by: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: The system cannot create a SOAP connector to connect to host mvs4.gb.tntpost.com at port 13510.
      at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:628)
      at com.ibm.websphere.management.AdminClientFactory.access$000(AdminClientFactory.java:122)
      at com.ibm.websphere.management.AdminClientFactory$1.run(AdminClientFactory.java:203)
      at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:63)
      at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:199)
      at com.ibm.ws.migration.postupgrade.Federated.DMgrConnectionInfo.initializeAdminClient(DMgrConnectionInfo.java:309)
      ... 33 more
      Caused by: java.lang.reflect.InvocationTargetException
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:56)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:39)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:527)
      at com.ibm.websphere.management.AdminClientFactory.createAdminClientPrivileged(AdminClientFactory.java:451)
      ... 38 more
      Caused by: com.ibm.websphere.management.exception.ConnectorNotAvailableException: SOAPException: faultCode=SOAP-ENV:Protocol; msg=; targetException=java.net.MalformedURLException
      at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:422)
      at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:222)
      ... 43 more
      Caused by: SOAPException: faultCode=SOAP-ENV:Protocol; msg=; targetException=java.net.MalformedURLException
      at org.apache.soap.rpc.Call.WASinvoke(Call.java:516)
      at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(SOAPConnectorClient.java:380)
      at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118)
      at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:365)
      ... 44 more
      MIGR0272E: The migration function cannot complete the command.

      End of WASPostUpgrade Summary Log

      ==============================================================================================================
      ==============================================================================================================

      WASPostUpgrade Failed
    • dysonbags
      dysonbags
      24 Posts
      ACCEPTED ANSWER

      Re: Migration problem

      ‏2011-05-27T15:46:03Z  in response to SystemAdmin
      Hmm.. just found all the ports defined in DATA(BBOWMMRF). Will edit them and see what happens.
      • dysonbags
        dysonbags
        24 Posts
        ACCEPTED ANSWER

        Re: Migration problem

        ‏2011-05-27T15:47:56Z  in response to dysonbags
        Nope that didn't work either.

        On holiday next week. Will pick this up when I get back.
  • SystemAdmin
    SystemAdmin
    462 Posts
    ACCEPTED ANSWER

    Re: Migration problem

    ‏2011-05-27T16:14:33Z  in response to dysonbags
    Hi,

    It's only the v8DMgr that has to be running. During DMgr migration the same port values must be mapped over from the v6.1 DMgr to the v8.0 DMgr, including the SOAP connector. This is the default behavior. This implies that if both v6.1 an v8.0 DMgr are on the same machine that both cannot be running at the same time because there would be a port confict. When you migrated the v6.1 DMgr to v8.0 did you use the default parameters or did you use dfferent port values between the two? If you used the command line WASPostUpgrade this would be the -replacePorts parameter

    Thanks

    Dana Duffield
    • dysonbags
      dysonbags
      24 Posts
      ACCEPTED ANSWER

      Re: Migration problem

      ‏2011-06-07T13:47:13Z  in response to SystemAdmin
      Hi Dana,

      I think you might have found the problem there. The v8 environment has different ports to the V6.1 so that we can run them both at the same time. Does this mean that I won't be able to do a direct migration? We're going to want to run in parallel when we go through test and development too.

      Also it appears that the V8 environment uses rather more ports than the V6.1. Can you therefore do a straight conversion without the possibility of port conflicts?

      Cheers
      Graham
  • DanaDuffield
    DanaDuffield
    3 Posts
    ACCEPTED ANSWER

    Re: Migration problem

    ‏2011-06-07T14:29:43Z  in response to dysonbags
    Hi Graham,

    The default scenario is to keep the ports the same on the DMgr in order for the new DMgr to be able to manage the old nodes whilst migrating the environment. There are a couple of ways to setup parallel environments.
    1) Create a new environment from scratch (this has plusses and minuses)
    2) Migrate the environment without disabling the old DMgr and then change the ports in the new environment to non-conflicting values. This is outlined in a redpiece http://www.redbooks.ibm.com/redpieces/abstracts/redp4635.html?Open

    As far as port conflictions go we're pretty go here, I have seen some cases in the past where we've had issues but I believe those have been fixed.

    Thanks

    Dana Duffiel
    • dysonbags
      dysonbags
      24 Posts
      ACCEPTED ANSWER

      Re: Migration problem

      ‏2011-06-08T10:14:27Z  in response to DanaDuffield
      Thanks for the link to the Redpaper. Looks useful, but I notice it's for V7. Is it all relevant to V8?

      Cheers
      Graham
  • DanaDuffield
    DanaDuffield
    3 Posts
    ACCEPTED ANSWER

    Re: Migration problem

    ‏2011-06-08T14:10:56Z  in response to dysonbags
    Hi Graham,

    Yes, the same procedures work for v8 as well as v7.

    Dana Duffield