RE: Extract SQL statements from Database/File

From: Rajesh Rao <>
Date: Tue, 15 Sep 2009 10:53:36 -0400
Message-ID: <>

The objective is to generate explain plans against all of the statements in a performance environment before deployment in Production. This is, in case, the current performance test cases never execute certain SQL statements. I understand that this would not be foolproof and explain plans might still differ from actual execution plans.

The problem with PL/SQL profiler is the same as I stated in the earlier email. There would be a need to execute the packages and it is possible that the execution might not execute some SQL statements due to the conditional flows, unless the data is conditioned appropriately for each and every possible test case. This is for a critical application that is being re-architected and it's a complete rewrite. Hence the need to cover all bases.


-----Original Message-----
From: Stephane Faroult [] Sent: Tuesday, September 15, 2009 10:40 AM To: Rajesh Rao
Cc: oracle-l
Subject: Re: Extract SQL statements from Database/File

Rajesh Rao wrote:
> Hello All, any tools/scripts out there that you are aware of, to
> extract all select/insert/update/delete statements from within the
> packages for a schema? The schema in question has very large number of
> packages. Executing the packages themselves with tracing enabled was
> one way I could think of, but that might not hit all SQL's within the
> package (conditional flows, etc).
> Regards
> Raj


What's the idea behind your question? My experience with packages is that when they are poorly written, which happens more often than I'd like, the problem isn't so much with individual statements that look and are usually innocuous enough and for the most part "untunable" by themselves, but with cursor loops all over the place and a crazy logic (to my eyes, at least) directly imported from the most orthodox procedural programming applied to sequential files. Have you thought about using the PL/SQL profiler? Wonderful tool, and under-used IMHO.

Otherwise, I have once written a C program that scans the source of packages, looks for WHEN OTHERS THEN [return] NULL and other niceties, cursor loops, statements in cursor loops, it was also computing cyclomatic complexity and so on. The result was so dispiriting that I have stopped using it.

Stephane Faroult
RoughSea Ltd <>

This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to for
disclosures relating to European legal entities.
Received on Tue Sep 15 2009 - 09:53:36 CDT

Original text of this message