AnsweredAssumed Answered

PAM Runtime Database being moved, how this affects running processes local Datasets

Question asked by AndriesJNel on Oct 11, 2016
Latest reply on Oct 13, 2016 by AndriesJNel
We are busy migrating our database from one SQL 2008 to SQL 2012 on new servers/instances/ports.   We have successfully migrated our applications but we have a problem with running/waiting ITPAM instances which use database details to perform certain functions.   We have a global database variables for our MDB db details which most of our PAM processes use.   The problem we anticipate is that processes that start before we move the databse from 2008 to 2012 will have read the old 2008 DB details from the global dataset and saved that information into the local process datasets. Then we go and move the applications to the new 2012 sql database and we update the global dataset but the running process instances will still have the references to the old 2008 database.  is there a way we can bulk update running processes dataset information to change these details? Otherwise we need to manually go in and suspend each process, change the details, and resume each process.   The fallback is to manually suspend, edit, resume all the processes after the database move

Any thoughts on this?