IT Process Automation

Expand all | Collapse all

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

Jump to Best Answer
  • 1.  PAM Runtime Database being moved, how this affects running processes local Datasets

    Posted 10-11-2016 02:55 AM
    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?
    Andries


  • 2.  Re: PAM Runtime Database being moved, how this affects running processes local Datasets
    Best Answer

    Posted 10-11-2016 08:28 AM

    There is no bulk suspend reset resume option.  You will either need to complete all in progress instances that reference the old database location, or manually suspend reset and resume the instances that need to read from the dataset and communicate with the new database location.

     

    Having the option to do this in bulk would make a great suggestion in the IDEA area of the community



  • 3.  Re: PAM Runtime Database being moved, how this affects running processes local Datasets

    Posted 10-12-2016 11:31 AM

    Here is a little hack you might try (assuming that you reference the database server by name and the credentials you are using are the same).

    Let's say your old database server is name MYDB08 at IP address 10.20.30.8 and your new database server is named MYDB12 at IP address 10.20.30.12.

    1. Stop the ITPAM process on the server
    2. Add an entry to the hosts file like this: 10.20.30.12 MYDB08
    3. Start the ITPAM process on the server

    Now all your old processes can finish up accessing the database server they reference as MYDB08.



  • 4.  Re: PAM Runtime Database being moved, how this affects running processes local Datasets

    Posted 10-13-2016 12:25 AM

    Thanks we had the same idea here, we are going to attempt this