Posts Tagged ‘RUP6’


Experiences with 12.0.6 Release Update Pack (RUP6)

February 5th, 2009 by Anonymous • 4 Comments »

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.

Tags: · · · ·

4 Comments »

 

Applying RUP6 for Release 12.0.6

December 1st, 2008 by Robert McMillen • No Comments »

I recently applied the latest RUP for Release 12 at a client that is in the midst of a new R12 installation.  I thought I’d recap my experience.

The 12.0.6 patch was released on Friday, November 7th.  We were alerted to it because we ran a fresh version of patchsets.sh during the week and it indicated that everything we had installed was superseded by an unreleased patch.  That got our curiosity going and we checked around Metalink finding that RUP6 was imminent.

The environment was using RedHat Linux 64 bit.  We had recently upgraded the Oracle database from 10.2.0.3 to 10.2.0.4.  They were already on RUP5 and we had recently applied the October CPU and the October Critical Patch Collection patches.  Bottom-line, we were very up-to-date.

Our environment consisted of two Application Servers and a single DB Server.  We were using ASM (10.2.0.4) but not using RAC.  We also had a shared APPL_TOP using OCFS2 for the two Application Servers.

You must start by applying the pre-requisite adpatch, R12 AD.A Delta 6 (Patch 7305520, Doc 736655.1).  It’s about 1.4Mb in size.  After downloading it there was a script to run for adgrants listed in the Patch 7305520 README.  We ran it, the adgrants.sql script, (as sysdba) to grant privileges to selected SYS objects and create PL/SQL profiler objects. We then applied patch 7305520 with adpatch.

Next we downloaded the RUP6 (Patch 6728000, Doc 743368.1).  It’s a big one at 2Gb in size.  It is multi-language but since we had an English-only installation we just downloaded the Linux86 version from Metalink.  It comes packaged in four files:

p6728000_R12_LINUX_1of4.zip  498Mb

p6728000_R12_LINUX_2of4.zip 546Mb

p6728000_R12_LINUX_4of4.zip 503Mb

p6728000_R12_LINUX_4of4.zip 429Mb

Looking at the README, it’s a straight-forward install with adpatch.  However if you have HR implemented there are some post-install steps which I didn’t have to do.  More information about that is in Document 145837.1 on Metalink.

The next step was to install the RUP6 Help Files (Patch 7109200, Doc 743368.1).  This is another multi-language patch where we only had to install the Generic version.  This is a simple adpatch install with no pre/post requirements.

In summary, it was a fairly simple patch exercise for our environment.  Hope yours is the same!

Tags: · · · · ·

No Comments »

 

Release 12 Tidbits

September 21st, 2008 by Robert McMillen • No Comments »

This morning’s session with the OAUG Upgrade SIG was accented by the attendance of Stephen Chan, who many of you probably recognize from his well-known blog.

During the session there was a discussion on the future of R12 updates and he noted that there are plans to to release one more Financials Family Pack for Release 12 of the E-Business Suite before Release 12.1 appears.  Currently the base release is 12.0.4 with a RUP 5 that included Family Packs for Financials and Payables.  So plan for another release from 12.0.5 to 12.0.6.

Also discussed was that all reports should be migrated from Oracle Reports formats to XML Publisher format by the time R12.1 appears.  Release 12 included a mixture of reports in both formats, but Oracle continues to migrate the application reports to the XML Publisher format.

One of the panelists works in Oracle support and noted that about half of the support requests are now generated by R12 clients.  John Stouffer noted that could be because 11i is so stable and R12 is still showing growing plans.  Probably true since there have been lots of patches to the new release.

I discussed support issues with him afterward.  He noted that many clients underestimate the need for R12 User Training because they mistakenly assume the the user experience with R12 is very similar to 11i.  “Everyone thinks it’s like upgrading within 11i, and that’s just not the case.” was his best comment.

He noted that he has actually had a customer calling for production support because they couldn’t figure out how to print out Payable’s checks!  He mentioned that changes to the setups in Payables and Receivables have been challenging for users.

Bottom-line, he highly recommends that companies considering an upgrade make time in the schedule to allow the key users plenty of time to get used to the new screens and features before going live.

Tags: · · · ·

No Comments »