This tool accepts any clean Oracle SQL dump that contains PACKAGE, PACKAGE BODY, PROCEDURE, or FUNCTION code. There is no strict format — if the dump contains real Oracle PL/SQL code line by line, the analyser will process it correctly.
Uploaded .zip files are processed entirely in RAM and
are never written to disk.
They are automatically deleted immediately after the report is generated.
Run the following SQL query to retrieve all PL/SQL objects:
SELECT
(CASE WHEN line = 1 THEN 'CREATE OR REPLACE ' || text ELSE text END) AS code_line
FROM all_source
WHERE owner = 'your_schema_owner'
AND type IN ('PROCEDURE', 'FUNCTION', 'PACKAGE', 'PACKAGE BODY','TRIGGER')
ORDER BY name, type, line;
This ensures each object begins with CREATE OR REPLACE, matching PostgreSQL and migration tool expectations.
Your goal is to produce a clean SQL text file — no INSERTs, no CSV headers.
CODE_LINE.CODE_LINE column.dump.sql (UTF-8).CODE_LINE column.dump.sql (UTF-8).-- Make output "flat" (no headers, no paging)
SET HEADING OFF
SET FEEDBACK OFF
SET PAGESIZE 0
SET VERIFY OFF
SET ECHO OFF
SET TRIMSPOOL ON
SET LINESIZE 32767
SET LONG 1000000
SET LONGCHUNKSIZE 32767
SPOOL C:\temp\dump.sql
SELECT
(CASE WHEN line = 1 THEN 'CREATE OR REPLACE ' || text ELSE text END) AS code_line
FROM all_source
WHERE owner = 'YOUR_SCHEMA_OWNER'
AND type IN ('PROCEDURE', 'FUNCTION', 'PACKAGE', 'PACKAGE BODY')
ORDER BY name, type, line;
SPOOL OFF
After spooling, zip dump.sql and upload the .zip file.
Compress the SQL file into a .zip archive and upload it under
“1. Upload ZIP” on the main page.