Tuesday, May 22, 2012

The Page Stuck in Processing

We applied Tuxedo patch level 089 (from 069) over the weekend, and it didn't help with the issue users have with getting stuck in processing.  It happens most often when a user clicks the magnifying glass to look up a value.  The processing pinwheel starts spinning, and it doesn't ever come back.  It's the same issue I listed here.

I just got an update from Oracle that this issue is fixed in PeopleTools 8.51.17.  It is "Report ID: 13865710       The Page Struck[sic] in Processing".  We are in the middle of upgrading from HCM 8.9 to 9.1 and a PeopleTools patch does not fit in our upgrade timeline.  I've asked to get an individual fix pulled out from the patch.  Responses to requests like this are hit or miss.  I'll let you know if we get lucky.

Update: See Stuck-in-Processing Solved

Tuesday, May 8, 2012

Best Practices for Upgrading PeopleSoft Enterprise

I came across this Oracle White Paper recently titled, Best Practices for Upgrading PeopleSoft Enterprise.  It's a useful reference document for what Oracle considers "best practices".

From pages 12 & 13:

Tip #3—Use Change Management Appropriate for an Upgrade

During an upgrade, it is imperative to freeze metadata and system data in your production environment. With respect to the new release, ensure all relevant patches available are applied appropriately. There are two types of new release patches to manage throughout the upgrade project: "required for upgrade" patches and "regular product" patches. For each upgrade pass, required for upgrade patches only are applied to your upgrade environment. For each user acceptance test rollout or environment, apply regular product patches to the test environment only and never to the upgrade environment. Failure to appropriately manage these different
change management requirements can result in upgrade step failures and unexpected user acceptance test results.