Aout plan stabilty matching.

This is a multi-part message in MIME format.

------=_NextPartTM-000-3310e2c4-b897-4066-ac6e-0db4483ef567
Content-Type: text/plain;

        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi, All,
 From Oracle Doc: "if the SQL text of the incoming statement exactly = matches the SQL text in an outline in that category, then Oracle = considers both texts identical, and Oracle uses the outline. Oracle = considers any differences a mismatch."=20

How could I ensure the incoming SQL text exactly match the SQL text in = an outline?
If I fish out an offensive SQL from library cache by some scripts in = SQL*Plus, is this offensive SQL text identical to the incoming SQL text? = Supposed this SQL text is extracted from stored procedure.=20

Appreciated your experience.

Chuan

------=_NextPartTM-000-3310e2c4-b897-4066-ac6e-0db4483ef567
Content-Type: text/plain;

        name="InterScan_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;

        filename="InterScan_Disclaimer.txt"

Unless otherwise stated, this e-mail does not represent the views of TransACT Communications Pty Limited. This text and any attachments of this e-mail are confidential and may be legally privileged. This email is for the use of the intended recipient only. If you are not the intended recipient do not take any action in relation to this email, other than to notify TransACT Communications by replying to this e-mail and destroying the original communication. Except as required by law, TransACT Communications does not represent that this transmission is free of errors, viruses or interference.

------=_NextPartTM-000-3310e2c4-b897-4066-ac6e-0db4483ef567--
Received on Tue Sep 10 2002 - 00:50:54 CDT