Special thanks go to Jeff Vold, the Apps DBA at Hazelden Foundation, who wrote this article about RUP6.
Hazelden Foundation is running Release 11.5.9 in production and is in the midst of a Release 12 upgrade. We recently applied the 12.0.6 Release Update Pack (RUP6) on top of our 12.0.4 development environment, and were asked to share our experiences. Here are some quick facts on RUP 6: According to Metalink Note:743368.1, RUP 6 is cumulative and delivers error corrections and system updates included in 12.0.1, 12.0.2, 12.0.3, 12.0.5, or FIN and HRMS family RUP5 along with those in 12.0.6.
Our patching consisted of the following: 7305220 – R12.AD.A.DELTA.6, 7505241 - PRC Rollup November 2008, 6728000 – RUP6, 7109200 – Consolidated Help, and the two November CPC’s for Payables and Receivables. I applied this set of patches three separate times on top of a clean Release 12.0.4 instance to eliminate all possible adworker job failures.
Prior to starting the patching, I followed Metalink Note: 372180.1 to delete an extra record from fnd_profile_option_values where profile_option_name=’PRINTER’ so an adworker program running the script afadmprf.sh for the R12.AD.A.DELTA.6 patch didn’t fail. Next I followed Metalink Note: 744973.1 so an adworker running script zpbremcwm.sql for the RUP6 patch didn’t fail.
I also had to open a couple of SR’s for failed workers with RUP6 and this is what I found:
RUP6 adworkers failed while running b6892753.sql. This was due to the column LONG_DESCRIPTION in table MTL_SYSTEM_ITEMS_TL, which was sized at 2000 and needed to be 4000. The support rep recommended applying patch 7505241 and then applying RUP6. I started with a clean Release 12.0.4 environment and applied R12.AD.A.DELTA.6, PRC Rollup November 2008, and RUP6. Again the RUP6 adworkers failed while running b6892753.sql due to another bug 7623243. Oracle is providing patch 7691702 to resolve this issue.
RUP6 adworker failed while running script gcs_hr_re_update.sql. MetaLink Doc. ID: 601803.1 documents the error, but since we are not using the Financial Consolidated Hub, this failed adworker job was skipped using adctrl.
Once the patches were completed, I followed the post-update steps. See Oracle E-Business Suite Release Update Pack Readme, Release 12.0.6 MetaLink Doc ID: 743368.1.
After the post-update steps were completed, we ran into a few other issues that needed to be resolved. A partial list is detailed below.
When first logging into the app, I received the error “The Page Cannot be displayed”. The solution that resolved this error was setting the parameter
LONG_RUNNING_JVM=false
in $INST_TOP/ora/10.1.3/j2ee/oacore/config/oc4j.properties.
After selecting a responsibility upon login, the message “APP-FND-01540: Unsuccessful logins since your last session” appears. This occurs no matter which user logs in. Metalink note 736799.1 states this is a Release 11.5.10 issue and recommends setting the system profile “Sign-On:Notification” to “No”, but this will disable all notifications and may not be desirable for all users. We opened an SR to find a resolution.
We also ran into a MOAC bug and had to apply patch 7649893. There are two bug fixes in this patch.
I hope you’ve found this overview of our experience helpful.