Change Assistant Pre-requisites Issues

I was putting a Campus Solutions Bundle on a system for a client and as per usual PeopleSoft delivered an emergency ISIR patch to follow up.  However, this time when I went to apply the ISIR patch after the fact Change Assistant was complaining that the pre-requisite bundle was not applied yet.  Now I know my memory is bad, but it was just the other day, I know I put the patch on this environment.

First, I thought cache, so I stopped all the agents and all the environments cleared the cache and reset the PSEM Agents & Hub.  Fired it back up and still the same error.  I even reset the GUID on PSOPTIONS.

I checked the PS_MAINTENANCE_LOG and clearly the update I put on is there, however, it looks a little different on one of the fields for other bundles.  The FIXOPRID for the bundle was PS and not PPLSOFT like the other bundles.  Sure enough I did a


Re-ran the check and sure enough all is right in the world again.  All pre-requisites need to have the FIXOPRID be PPLSOFT otherwise things don’t go as planned.

Error: Change Package was not created, see invalid File References

During the last upgrade pass I was attempting to apply patches to the upgraded environment and ran into an unusual error when trying to build the change package within Change Assistant.

As it turns out when we build the image, we did not force it to always use the same IP address.  So every time it starts the IP address has a tendency to change.  As it turns out this can cause some problems with the configuration that was done before on previous passes.  Depending on your setup you may find that the Oracle Database Listening will not work, which in turn makes it unavailable for the application server and process scheduler and the database is not listening to requests.  So you will need to change the listening and tnsnames files, as well as the tnsnames file on the server where change assistant is running.

However, the error with building the change packages was caused because the mapped drive for the “pi_home” on the virtual image was mapped as a network drive using the IP address.  Once the mapping was changed and the pi_home was available the change package error was eliminated.