CA Service Management

 View Only
  • 1.  SDM - Migration 14.1 to 17.2 - migrate ONLY MDB

    Posted Mar 11, 2020 11:14 AM
    Hi all,
    Is it possible to have only the MDB migration steps executed for a Swingbox migration from 14.1 to 17.2?
    We only want to migrate and transport the mdb once more when the 17.2 target system goes live.
    All other preparations are then already completed in advance.

    Regards,
    Peter

    ------------------------------
    Senior Technical Consultant
    Fujitsu Services
    ------------------------------


  • 2.  RE: SDM - Migration 14.1 to 17.2 - migrate ONLY MDB
    Best Answer

    Posted Mar 12, 2020 06:17 AM
    Wouldn't that be nice! 

    By the way, after a recent swingbox migration - complicated by having to go from r12.7 to 14.1 to 17.2 - I found that some contents of the al_cdb_xxx tables were left containing the swing server name.  In particular al_cdb_configurationparameters entries for componentkey = 'itsm' and machinename = 'common' were out of alignment with the new production server.  That didn't seem to affect the new SDM instance, but the old server names showed up as installation properties in the logs when integrating the Jaspersoft CABI, and I was concerned that CABI might have ended up pointing at the wrong place, so I corrected them in the 'mdb' before completing the integration.  You might want to take a look in the database and convince yourself that these are all OK.

    Regards,
    James