Skip to main content

How to use Patch wizard in Oracle EBS Environment for Analysing the Patch Impact

How to use Patch wizard in Oracle EBS Environment for Analysing the Patch Impact

I am using R12.1.3 environment for demonstration.

When we have to run Patch Wizard first time in EBS, we have followed the below steps to run Patch Wizard without an internet connection to generate the latest EBS Patch Recommendation Analysis or to analyze any EBS patch(es) against your current EBS Application.

If you want to get the latest Oracle E-Business Suite patch recommendations:
Download the Patch Information Bundle (InfoBundle) on to a system that has Internet access.

The InfoBundle can be downloaded from the following locations:

or

From Patch Wizard > Preferences, set up a staging directory if not already done so.



Make sure the Patch Wizard can read from and write to the staging directory. The InfoBundle Zip file must be copied to a system that can access the Patch Wizard staging directory. If the staging directory is on a local disk, it must be copied to the system where you run Patch Wizard. If the staging directory is on a shared (network) disk, it can be copied to any system with access to the shared disk.

For example Patch Wizard runs in the concurrent tier and is usually owned by SYSADMIN, so ensure SYSADMIN can access the staging directory from the concurrent tier
 
Copy the InfoBundle Zip file to the staging directory(/tmp in my case).

Go to Patch Wizard > Recommend/Analyze Patches.

Select Create Recommendation, choose any Patch Filters, and click OK.

NOTE: if you are using a version of Patch Wizard later than Release 12.0.4, Patch Wizard will use the latest InfoBundle that exists in the staging directory, so make sure to update this InfoBundle file regularly.




NOTE: if you are using a version of Patch Wizard earlier than Release 12.0.2, like 11.5.10.2 then you must also check Upload patch information bundle before analyzing patches, to include the current InfoBundle file found in the staging directory.





NOTE: if you are using a version of Patch Wizard earlier than Release 12.0.2, like 11.5.10.2 you can optionally upload the latest InfoBundle file to Patch Wizard by clicking the Upload patch information bundle (no analysis) button, and clicking OK.




The patch info upload will take time to complete the job for the first time.

Once the Patch info is uploaded then we can run the patch wizard to analyze the patches.

1) Create a staging directory where the patches will be kept.
I am using /tmp location.

[applmgr@ebs122 sf_Downloads 03:26 PM]$cd /tmp
[applmgr@ebs122 tmp 03:38 PM]$mkdir nonad ad




Make sure the Patch Wizard can read from and write to the staging directory. The patch Zip files must be copied to a system that can access the Patch Wizard staging directory. If the staging directory is on a local disk, it must be copied to the system where you run Patch Wizard. If the staging directory is on a shared (network) disk, it can be copied to any system with access to the shared disk.


2) Copy the downloaded patch Zip file(s) to the Patch Wizard staging directory.

In Oracle E-Business Suite 12.1.2 Release Update Pack (RUP2) and higher, all the AD product patches must be placed in the <staging  directory>/ad directory, and all the non-AD patches must be placed in the <staging directory>/nonad directory.

3) Go to Patch Wizard > Recommend/Analyze Patches.

Select Analyze Specific Patches.



4) When the patch analysis is complete, the analysis report appears on the Patch Wizard page. Click the Details icon to view the detailed report.


Reference:
741129.1


If you like please follow and comment
Labels:

Comments

Post a Comment

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...
Post a Comment
Read more

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...
Post a Comment
Read more

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...
Post a Comment
Read more