Prev
Next
Forums Lawson S3 Supply Chain

copy/move MSCM

Sort:
You are not authorized to post a reply.
Author
Messages
Duane
Basic Member
Posts: 17
Basic Member
4/28/2010 7:29 PM
    We are getting ready to upgrade MSCM in place (9.0.0.12 to 9.0.1.1) but want to move to new server first. We are toying with a few scenarios? Anyone done this? Is it enough to install new WAS and MSCM of the same version and patch level, then make sure copy in-synch Lawson prodline data and MSCM database and point MSCM there? Thanks in advance for your responses.
    Saurabh
    Veteran Member
    Posts: 94
    Veteran Member
    6/9/2010 6:41 PM
      During our previous migration when we moved to a new lawson Apps and DB server we had not been able to just backup and restore the MSCM database at the same time as the actual PRODLINE database.

      Instead once the PRODLINE db had been copied we had to run scripts to resynch the MSCM database with the production database. These scripts then seem to register the MSCM database correctly (otherwise we kept getting Database is currently not availaible error)

      The downside of this was that
      (a) we had to recreate all the MSCM users (and we had around 80 of them)
      (b) we had to ensure that all par counts had bee transferred acrossed as any transactional information in
      the MSCM db will be lost
      Look at Article ID: 5160648 (its for step to do when refreshing your db)
      You are not authorized to post a reply.