This content has been marked as final. Show 7 replies
Sorry, but this is not a duplicate post.
In the post you referred to I was trying to understand the Maint Wizard steps and MOS note 954704.1 (recommended R12 patches). I finally realized that only a "section" of that note was involved.
The MW then moves on to the upgrade steps which I have outlined in this thread (Financials Pre-Upgrade Patches).
This post has to do specifically with the MW since the steps are vague and overlap and it seems to me the the MW folks are interested in finding these types of issues so that they can be corrected and/or improved.
Please have someone answer my question since the answer will probably indicate that at least one of the MW steps will need to be modified.
We have setup the Maintenance Wizard tasks and steps to be as exact as possible and I would agree that this TASK is the most difficult to follow as the directions in each patch vary. What we have laid out is the following:
Task: Apply Preinstall Patches
1-Check for critical pre-upgrade patches for Financials (Required)
Apply these patches first in preinstall mode so that they get staged in the $APPL_TOP/admin/$TWO_TASK/preinstall directory. Most likely this directory will not exist and you will need to create it. If it already exists it should be empty at this point in the upgrade process.
Do not apply patch 7303029 until the step occurs in the maintenance wizard even though referenced in the financials note. The first part of the step for 7303029 downloads the patch 7303029 and verifies that the u67780700.drv driver is in the correct location and ready to be merged. The execute part is a manual step the merges all the 25 financials pre-upgrade patches with 7303029 and the u67780700.drv driver to create a new merged driver with all the fixes.
So the order is -
- 25 financials pre-upgrade patches from MOS 1127593
- AD patches 9179588:R12.AD.B, 9477107:R12.AD.B, 7461070:R12.AD.B.1 0
This does not effect the pre-install patches from the 25 financials nor the next step for 7303029. We put the step where we did to call out the note so it did not get overlooked or confused with the upgrade task outlined in the upgrade document.
- patch 7303029
Basically - follow the maintenance wizard steps as they are laid out in the exact order of execution based on our upgrade documentation.
I will log an enhancement request to change the text in the Check for critical pre-upgrade patches for Financials step to be more specific on what part of the document to follow.
Thanks for your feedback and keep it coming please !!!
Thanks for the clarification. This is really helpful.
Regarding the 25 pre-upgrade patches.
1) Can I merge them in the normal fashion, "admrgpch -s SRC -d DEST -merge_name PRE_UPG_MERGE"
2) Then apply the merge patch using "adpatch -preinstall" using the "u_PRE_UPG_MERGE.drv" file?
Yes absolutely - I would recommend that you do.
After applying the merged AD patches (9179588:R12.AD.B, 9477107:R12.AD.B, 7461070:R12.AD.B.1) I had these invalid objects (and errors):
186 PL/SQL: ORA-02289: sequence does not exist
149 PL/SQL: SQL Statement ignored
674 PLS-00302: component 'SET_AGGREGATE_LIST' must be declared
674 PL/SQL: Statement ignored
Here's the file header info:
/* $Header: adpaipb.pls 120.2 2006/03/27 08:07:14 msailoz noship $ */
/* $Header: adpasrb.pls 120.3 2006/09/08 16:14:20 ababkuma noship $ */
I found no hits anywhere on either of these. Do I need to open an SR?
These are for patchwizard and should not interfere with your upgrade - after the upgrade this should be valid based on the post install patchwizard patches