Oracle E-Business Suite 12.2.9 upgrade to version 12.2.10

Customer February 29, 2020 at 7:23 am

When upgrading EBS (e.g., to 12.2.10), is it feasible to combine all critical patching components—Maintenance Tool Kit (MTT), AD/TXK deltas, and the 12.2.10 RUP—into a single ADOP cycle? We are concerned that running everything together might introduce excessive complexity and make troubleshooting difficult.

Viewing 10 reply threads

Author
Replies
- Support February 29, 2020 at 11:29 am
  That is a valid concern regarding combining the MTT + AD TXK patches + RUP (like 12.2.10 patchset) in one ADOP cycle, as it can make troubleshooting complex if something goes wrong. A more conservative approach, and often recommended in Oracle Notes, is dividing the patching: running MTT + AD TXK deltas in one cycle, and then the RUP (e.g., 12.2.10 cycle) separately.
- Customer February 29, 2020 at 10:32 pm
  If we proceed with separate ADOP cycles, how can we efficiently verify the status of the AD/TXK delta patches before starting the final RUP application?
- Support March 1, 2020 at 9:48 pm
  You should use a Blitz Report that leverages the AD_PATCH.IS_PATCH_APPLIED database function. This allows you to quickly query specific patch numbers (like 28840822, 29965377, or 29781255 for critical TXK patches) to ensure they are explicitly marked as ‘APPLIED’ before moving to the next cycle.
- Customer March 3, 2020 at 9:01 pm
  If an ADOP application phase hangs or fails silently, what is the initial diagnostic focus for the DBA team?
- Support March 4, 2020 at 4:29 am
  If an ADOP phase (like `fs_clone`) is stuck , the DBA should immediately run diagnostics on the configuration of the Application Tier nodes. Specifically, query `apps.fnd_nodes` to check for correct service names, webhost, and domain configurations, as misalignments can cause silent failures.
- Customer March 5, 2020 at 2:35 am
  We need to ensure all custom reports remain fully functional after the upgrade, especially high-volume financial extracts. How can we quickly identify potential issues with data access or performance post-upgrade?
- Support March 7, 2020 at 4:31 am
  Include running your critical, saved Blitz Reports in your smoke test plan. Blitz Report provides speed and reduced processing overhead for financial reports , allowing quick validation of data integrity, especially for complex structures like GL Account Analysis and YTD calculations.
- Customer March 8, 2020 at 10:32 pm
  Our security team requires confirmation that all EBS Java Archives (Jar Files) are properly signed after the patching to maintain code integrity.
- Support March 9, 2020 at 8:21 am
  The patching process often modifies JAR files, necessitating re-signing. You can locate the list of files modified after patching within the ADOP log subdirectories. Ensure the process adheres to your policies, especially if using a Hardware Security Module (HSM) for Signing EBS Jar Files.
- Customer March 9, 2020 at 8:20 pm
  If we were migrating from 12.2.8 to 12.2.9, would similar steps apply?
- Support March 11, 2020 at 11:58 am
  Yes, major EBS version upgrades (like 12.2.7 to 12.2.8 or 12.2.8 to 12.2.9 ) follow similar technical protocols, requiring careful RUP application, AD/TXK patching, and environmental verification using tools like SQL diagnostic reports.
Author
Replies

Viewing 10 reply threads

You must be logged in to reply to this post.