---
title: "Extracting Patches for Ongoing Changes"
slug: "how-to-extract-upload-a-patch-for-ongoing-changes-analysis"
updated: 2026-08-12T11:05:54Z
published: 2026-08-12T11:05:54Z
canonical: "success.panaya.com/how-to-extract-upload-a-patch-for-ongoing-changes-analysis"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://success.panaya.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Extracting Patches for Ongoing Changes

Panaya's Release Dynamix for Oracle EBS requires running a Java program on your Oracle Apps Server.  
This article explains how to upload new Patches for **Release Dynamix projects** for **ongoing changes**. If you are working on a standalone Patches project in Panaya, follow the instructions provided in [this article](/v1/docs/how-to-extract-upload-a-patch-for-analysis). **Important**You must have uploaded at least one [Custom Code extract](/v1/docs/how-to-extract-upload-your-custom-code-using-the-code-box) to Panaya before uploading a patch extract for analysis.Please also verify the code extraction (ETL) was uploaded in the last three months (90 days) for your system, else the Patch analysis will not succeed.Before running the Patches Extraction Process,  
please make sure that you meet the requirements

 

---

## Uploading a Patch

1. [Log in to Panaya](/v1/docs/how-to-log-in-to-panaya)
2. Click on the **Menu button ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971152249.png)** and select a **Project**  
Select a project of type **Testing** or **Ongoing Changes** or [create a new project](/v1/docs/how-to-create-a-new-project-1)  
To view the types of existing projects, use the Menu button to select **All Projects.**  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971168600.png)
3. Select the **Development tab ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971180315.png)**
4. **[Create a new Feature / Requirement](/v1/docs/how-to-add-a-new-requirement)** or **select an existing** one from the list
5. Click on the **Requirement ID** or **Name** to open up the Requirement / Feature details  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971189959.png)
6. Select the **Risk Analysis tab**  
**![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971202648.png)**
7. Select **Code Changes**  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971212484.png)
8. Select **Upload new Patches**   
**![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971224121.png)**
9. Click on Download the Oracle extraction tool to download the extraction tool.  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971233209.png)

Always download the most updated version from this dialog box. We do not recommend using older versions previously downloaded.  

---

## Extracting

1. Upload the downloaded **panaya-ptl-extractor.jar** file to your Oracle Application Server
2. Change your working directory to the location of the panaya-ptl-extractor.jar
3. Create a directory that will contain only the ZIP files of the patches that you want to analyze before they have been installed  
Do not unzip or install the files.
4. Using your Oracle Apps OS user (with access to the Oracle environments), **execute one of the following commands** -

java -jar panaya-ptl-extractor.jar <APPS password> <Patches directory>  
or  
java -jar panaya-ptl-extractor.jar [-prompt] <Patches directory>  Parameters explanationA) **<APPS password>** - Mandatory - The password of your APPS schema in the DB  
B) **<Patches directory>** - Mandatory - The location of the patches you downloaded  
C) **[-prompt]** - Optional -  this will open a dialog box for the user to enter the apps password. This will mask the password for cases where other users attempt to sign in to the system and execute the command ps -ef.  An output directory will automatically be created for you during the patches extraction process. The directory's name will be output_<date>_<time>. 

When running, the screen will look like this: ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971256407.png) At the end of the process, **one ZIP File** will be created in your output directory (e.g., PTL_20121015_1259.zip), which you'll be asked to upload to the Panaya website. If you don't have access from your Application server to the Panaya website, please copy the file from there.

If you are using a **controlled release patch**, [here](/v1/docs/how-to-upload-a-patch-extract-larger-than-2gb-controlled-release-patches) for additional instructions.Follow the instructions described [here](/v1/docs/unable-to-connect-to-db-error-message-while-running-the-custom-code-patches-extraction) if you are running the Patches extractor on the 12c database.  

1. Click browse and locate the zipped file created by the patches extraction process. You can also drop the ZIP file onto the cloud area.  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971271016.png)
2. Click Upload  
The duration of the upload depends upon the size of the file. You can view the status of your Patches upload in the Code Changes section.  
![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1638971280168.png)
3. Upon completion, you will be able to [](http://success.panaya.com/Videos/Release-Dynamix-Videos/1331309781/How-to-analyze-Impact-and-Risk.htm)[analyze Impact and Risk.](/v1/docs/how-to-analyze-impact-and-risk-for-oracle-ebs)