Step-by-Step Process to Apply a Patch in Oracle Apps EBS R12.1

Applying an application patch in Oracle E-Business Suite R12.1 is a systematic process that involves several steps to ensure minimal disruption to the system and data. Please note this process involves application downtime.

Also make sure to have application and database backup before starting patching.

Steps

1. Download the Patch from My Oracle Support (MOS)

Log in to My Oracle Support at https://support.oracle.com.
Search for the patch you need by its patch number.
Download the patch to your local machine.

2. Transfer the Patch to the EBS Application Node

Once downloaded, transfer the patch file (usually a .zip file) to the application node of your Oracle E-Business Suite.
Use an SCP tool or another secure file transfer method.

3. Unzip the Patch File

SSH into the application node as the applmgr user.
Navigate to the patch directory (or create a new directory to store the patch).

Example:

cd /u01/oracle/patches/

Unzip the patch file:


unzip <patch_number>.zip

This will extract the patch contents into a directory with the patch number as the name.

4. Check Pre-requisites and Patch ReadMe

Navigate into the unzipped patch directory:


cd /u01/oracle/patches/<patch_number>

Read the patch-specific README file, which contains the prerequisites, instructions, and any special considerations for your environment. For example:


cat README.txt

Ensure you have completed any pre-requisites mentioned, such as applying database patches or downloading driver files.

5. Put the Application in Maintenance Mode

Switching to Maintenance Mode ensures that the system is in a stable state and restricts user access to avoid conflicts during the patching process.


adadmin

Select Enable Maintenance Mode.

6. Stop Application Services

Ensure that all application services are stopped before applying the patch to avoid inconsistencies. If its multi node environment then stop application services on all nodes.


cd $ADMIN_SCRIPTS_HOME
./adstpall.sh apps/apps_password

7. Apply the Patch Using ADPATCH

Now, apply the patch using the ADPATCH utility.

Change directory to the patch location where the driver file resides:
```
cd /u01/oracle/patches/<patch_number>
```
Run ADPATCH:
```
adpatch
```

You will be prompted for the following inputs:
- APPL_TOP: Default will be displayed.
- Apps username: Enter apps.
- Apps password: Provide the password for the apps user.
- System password: Provide the password for the system user.
- Path of application location: Path were application patch is kept.(/u01/oracle/patches/<patch_number>)
- Driver file: Enter the patch driver file name (usually uNNNNNN.drv, where NNNNNN is the patch number).

Example:


Please enter the name of your AutoPatch driver file: u123456.drv

ADPATCH will then begin applying the patch. This process may take some time, depending on the size and complexity of the patch.

8. Monitor the Patch Application

Monitor the progress of the patch application in the terminal.
Additionally, you can tail the ADPATCH log file to track progress in real-time:


tail -f $APPL_TOP/admin/<SID>/log/adpatch.log

Resolve any errors encountered during the patch application by referring to the logs and the Oracle Support documentation.

9. Run Post-Patch Steps (If Required)

After the patch is applied, check the README file for any post-patch steps. These may include running SQL scripts, executing data migrations, or recompiling forms and reports.

10. Disable Maintenance Mode

Once the patch is successfully applied, disable Maintenance Mode:

Use the adadmin utility to disable it:


adadmin

Choose the option to Disable Maintenance Mode.

11. Start Application Services

Start the application services again on all nodes:


cd $ADMIN_SCRIPTS_HOME
./adstrtal.sh apps/apps_password

12. Verify the Patch Application

Verify the patch was applied successfully by running the following query in the database:


SELECT bug_number,creation_date
FROM ad_bugs
WHERE bug_number = '<patch_number>';

If the patch was applied successfully, this query will return a row.

You can also check the patch logs for any errors or warnings.

13. Perform Testing

Test the functionality of the patched components.
Ensure that all essential processes are running as expected after the patch is applied.

Please do like and subscribe to my youtube channel: https://www.youtube.com/@foalabs If you like this post please follow,share and comment

Step-by-Step Process to Apply a Patch in Oracle Apps EBS R12.1