Panaya ETL Extraction - How to extract & upload your custom code

Download the Oracle Extraction Tool

Select the Setup tab and then Code Box.

Select the relevant System from the drop down list

Download the Oracle extraction tool (jar file)
Always download the newest extraction code from Panaya's Code Box. It is not recommended to use older versions of the extraction.

Extracting the Custom Code and Usage Statistics

1. Upload panaya-extractor.jar to your Oracle Application Server.
2. Change your working directory to the location of the panaya-extractor.jar
3. Using your Oracle Apps OS user, execute the following command:
   

For Oracle EBS target version* up to 12.1.3 (including):

java -jar panaya-extractor.jar <apps password> [<ETL type>] [-customJavaTop=<Custom Java Top>]
 

For Oracle EBS target version* above 12.2 (including):

java -jar panaya-extractor.jar <apps password> <SYSTEM password> [<ETL type>] [-customJavaTop=<Custom Java Top>] 

* The target version is the version you wish to upgrade to 

Example

java -jar panaya-extractor.jar <appspass> <systempass> F

Note
If you wish to expedite the extraction process when upgrading to Oracle EBS version 12.2 and above, click here

   

Parameters explanation
<apps password> - The password of your apps schema in the DB
<SYSTEM password> - The password of your SYSTEM schema in the DB
[<ETL type>] - What data to extract during the ETL 

F - Full ETL (Customizations & Usage data) Please use this for the first extraction
C - Customizations only
U - Usage only

If no ETL type is specified, a Full ETL will be executed

[-customJavaTop=<Custom Java Top>] - Path(s) to your framework projects other than $JAVA_TOP.
If more than one path is defined in the classpath, use ':' as a delimiter - If -customJavaTop is not specified, will use only $JAVA_TOP.



During the extraction process, an output directory will automatically will be created for you.
The name of the directory will be output_<date>_<time>.
 

At the end of the process, one ZIP File will be created in your output directory, which you will need to upload to Panaya Code Box.

If you do not have access from your Application server to the Panaya web site, please copy the file from there.

If you run the Concurrent Manager on a different server than the Oracle Application server, a separate extraction must be done from each server.

Click here for more information

If you are having two node setup with concurrent managers on different server, then you need to copy the panaya extraction tool on both the servers and execute the command same as above. After we get the output file we need to merge it using below command.

A Merge tool is available to combine the two extracts into a single file which can be uploaded to Panaya’s servers.

• Run the Panaya extractor both on the Oracle Applications server and on one of the Concurrent Manager servers, as described in the section: EXTRACTING THE CUSTOM CODE AND USAGE STATISTICS.

Using your Oracle Apps OS user, execute the following command in order to merge the two files into one:
java -cp panaya-extractor.jar MergeFiles appsETL=<oa_etl> concETL=<cm_etl> [<new_etl>]
Parameters explanation

• <oa_etl> – is the full path of the extracted filename from the Oracle Application server
• <cm_etl> – is the full path of the extracted filename from the Concurrent Manager server
• <new_etl> – is the full path of the merged extracted filename. This is an optional parameter; the default value if not specified is "ETL_MERGE_ + timestamp.zip"

The merged file will be built as follows:

• reports.zip/bin.zip/sql.zip – will be copied from the cm_etl file
• framework.zip – will be copied from the cm_etl file, unless it is found in the oa_etl.zip file
• Appl_tops.properties, etl.log – will be copied from the cm_etl and renamed to conc_appl_tops.properties, conc_etl.log
• All other files will be copied from the oa_etl file

Example

java -cp panaya-extractor.jar MergeFiles appsETL=/b01/panaya_23feb/ETL_FULL_20160223_1633.zip concETL=/b01/knapps/panaya_23feb/output_20160223_0820/ETL_FULL_20160223_0820.zip /b01/knapps/panaya_23feb/merge/ETL_24feb.zip

Upload the Extract File

1. Upload the ZIP file to Panaya Code Box
   
2. Once uploaded, you should now receive a confirmation email regarding your custom code upload.
   Other users with the Upload Code and/or Manage Users permission will also receive a confirmation email. 

 To expedite the extraction process when upgrading to Oracle EBS target version 12.2 and above?

Oracle E-Business Suite Release 12.2 introduces Online Patching (OLP), a new feature that significantly reduces the patch downtime that was needed in previous releases. Panaya can greatly assist you in identifying the numerous changes required when implementing OLP.

The Panaya extract (ETL) includes 4 Oracle supplied SQL scripts (Readiness Reports) that will gather the necessary information for you about your instance and the OLP. These scripts can be very long running.

To improve the performance of these scripts, we highly recommend you refresh the SYS and data dictionary statistics to ensure that the database will use the most efficient execution plan.

Suggested commands (to be run at the DBA’s discretion) before the ETL:

1. SQL> EXEC DBMS_STATS.GATHER_SCHEMA_STATS (‘SYS’);
2. SQL> EXEC DBMS_STATS.GATHER_DATABASE_STATS (gather_sys=>TRUE);
3. SQL> EXEC DBMS_STATS.GATHER_DICTIONARY_STATS;
4. SQL> EXEC DBMS_STATS.GATHER_FIXED_OBJECTS_STATS;