Migrating Parameter Definitions from Oracle Reports

Yes, the ‘Concurrent Program’ import option is designed specifically for this task . This feature allows you to import the parameter definitions, associated Lists of Values (LOVs), and Request Group assignments from any standard Oracle concurrent program . This significantly simplifies the migration process, especially for technologies like Oracle Reports (.rdf files) where the actual report SQL usually cannot be imported automatically .

There is a helpful workaround . If you run the target concurrent program (e.g., the Oracle standard report) immediately before executing the Blitz Report import option, the Blitz Report code attempts to retrieve the program’s largest SQL statement directly from the database memory (SGA) . While this is not 100% reliable, it can capture the extraction query, which you can then copy and refine for your Blitz Report definition .

If the SGA retrieval is unreliable, you can use the seeded Blitz Report called ‘DBA SGA SQL Performance Summary’ . You would run this report, restricting it by the module type ‘Concurrent Request’ and the module name of the specific concurrent program you are interested in, to identify the SQL statements executed by that program . This provides the query text necessary for manual import.

Yes, if you only want to export the SQL text, you would use the `XXEN_API.EXPORT_FILE_DATA` function and set the `p_type` parameter to ‘SQLs’ . Alternatively, if you want the history of old SQL texts, you would use ‘SQL Versions’ , optionally filtered by `p_creation_date` .