HansF wrote:
> I can think of no reason for two hits on one policy, unless you are
> performing two separate actions and have asked for the policy to be
> invoked for each action. For example - are you updating and then
> querying the table? Or is something invoking the table through a trigger?
>
> Try adding a trigger to the table to insert into a [different] log for
> each action. See if you can match the insert from the policy with the
> trigger log.
>
> Try restricting your policy to one operation only (SELECT, UPDATE, etc.)
> and see if that narrows the hit.
>
> BTW - your policy should *normally* not have an insert or an update to a
> log table. I assume you are doing that for testing only. The purpose of
> the policy is to provide a rewrite predicate, not to do an audit (use
> auditing for that!). As it is, you have the potential for dramatically
> slowing the policy driven table.
>
The only reason I have the INSERT is for debugging purposes. I don't
suppose Oracle has a console or log file I can use instead?
Received on Sat Jun 04 2005 - 06:21:00 CDT
