SELECT app_short_name, MAX(patch_level)
FROM apps.ad_patch_driver_minipks
GROUP BY app_short_name ;
Typical output looks like this:
SQL> /
APP_SHORT_NAME MAX(PATCH_LEVEL)
----------------------- -----------------------
ABM 11i.ABM.F
AD 11i.AD.I.4
AHL 11i.AHL.P
AHM 11i.AHM.B
AK 11i.AK.G
.
.
.
.
Subscribe to:
Post Comments (Atom)
Posts
5 comments:
Vikram,
Thank you for the query. It was really helpful.
The Metalink Doc - 457566.1 (Oracle Applications Patching FAQ for Release 11i) says
"In addition to the patches in a maintenance pack, Oracle also packages a new Rapid Install at each maintenance pack release level. So Applications Release 11.5.10CU2 Rapid Install contains the same applications code level that a customer would get if they applied the Release 11.5.10CU1 Maintenance Pack on an earlier 11i release level. Note that the technology stack could still be different because Rapid Install includes the latest certified technology stack. The maintenance pack includes only Applications code."
So, Is there any query to find the applications code level?
Thank You.
Hi Aditya,
Of course there is. Here's the query:
SQL >select release_name from apps.fnd_product_groups;
RELEASE_NAME
-----------------------------------
11.5.10.2
- Vikram
Thank You Vikram.
I use the query that you have given to find out the Oracle Applications Version. I don't know that this is also called the Applications Code level.
Aditya.
Hi Aditya,
I would say the release version is the codelevel in 11i. The term codelevel came into Apps lexicon after R12. Metalink Note 459156.1 has the definition:
What are codelines? Codelevels?
In Release 12, Oracle Applications patches are grouped into codelines. A codeline begins with a point release that delivers a unique set of features, such as Release 12.0, and progresses to include all the patches required to maintain that point release. The initial Release 12.0 point release introduces codeline A. Any future point releases introduce new codelines, each identified by a new letter. For example, Release 12.1 would introduce codeline B and Release 12.2 would introduce codeline C.
Patches associated with codelines not only implement a set of product features for that point release, but also provide fixes to that set of features. We describe this unique set of product features for a point release as a codelevel and assign it a unique number. Codelevels also identify patches for individual products. For example, codelevel R12.AD.A.1 is the first set of fixes to codelevel R12.AD.A, R12.AD.A.2 is the second set, and so on. Codelevels are cumulative - each one contains the initial set of features plus all the fixes created to date for that product or product family.
All codelevels created after the initial point release are aggregated into cumulative release update packs (RUPs). RUP1 is equivalent to R12.0.1, RUP2 is equivalent to R12.0.2, and so on. In addition, they may also provide feature enhancements, which provide new functionality that has a limited impact on your system.
A new point release contains new features that will substantially impact your system and may change its operation. It starts a new codeline (for example, codeline B). At that point, you can choose to upgrade to the new codeline and adopt the new features, or stay on your existing codeline, where bug fixes and enhancements will continue to be provided for your existing features.
- Vikram
Vikram,
Thanks for the Metalink Notes on Codelines and Codelevels. The terminology is a bit confusing. But will go through it again for clarity.
Say, the Oracle release version is 11.5.9. If after upgrading to 11.5.10.2, Can I say the code level is 11.5.10.2. Or should I say code level is 11.5.9 only?
Regards,
Aditya.
Post a Comment