Change Assistant – Skipping Steps

I was doing a PeopleTools upgrade using Change Assistant from 8.44 to 8.54 recently, and have found that upgrading to 8.54 can be a pinch problematic mainly because of the 32bit to 64bit change-over.  So I have found it easier to do two upgrades:  8.44 to 8.53 and then 8.53 to 8.54.

One interesting problem I ran into was I reverted a failed attempt and missed a step and I had an upgrade template thinking I was going from 8.44 to 8.53 but the environment thought my database was at 8.54, so as change assistant went through the script it started skipping steps.

I ended up having to go back to the database level and set the TOOLSREL on PSSTATUS to 8.44 and rebuild the environment in Change Assistant.  Then create a new job with the updated environment and the upgrade template, then I changed the database back to the correct level it was at and marked all the completed steps in the template complete and ran the steps that were being skipped. Change Assistant will read the Tools Release level from PTSTATUS table when the Change Assistant job builds from the template and if that level is different then when the job starts any step is not at the right level will be skipped in when Change Assistant processes through the job.

Change Assistant – Performance Issues

Just working through some PUM patching of an HCM environment and the change package that was created was a little on the large size.  In the past large change assistant templates cause extreme delays in trying to get change assistant to respond.

One thing you can do is increase the Heap Size of Change assistant.  The easiest way to do this is to create a shortcut to changeassistant.exe and append the parameter:   -Xmx1024m

In PeopleTools 8.54, I have also found that to minimize the size of the application, you can do an Initial Pass with just the source and/or target steps.  This cuts out a number of steps and makes an easier package to work with.  Also, you can disable the file deployment and do it the old fashion manual way and this too will reduce the template work load.

For example I am doing Image 9 to 12 HCM patching right now, and the file deployment is approximately 1/3rd of the entire change package XML file.

Happy Patching….