identifying packages with persistent state
From: Greg Norris <spikey.mcmarbles_at_gmail.com>
Date: Wed, 6 Aug 2008 14:18:03 -0500
Message-ID: <d4beff360808061218m64d8aaf6s7597bef7af3e0b7b@mail.gmail.com>
end invocations;
Date: Wed, 6 Aug 2008 14:18:03 -0500
Message-ID: <d4beff360808061218m64d8aaf6s7597bef7af3e0b7b@mail.gmail.com>
We're experimenting with select-level TAF under Oracle 10.2.0.3 for some of
our reporting applications, most of which aren't RAC/failover-aware. It's
working fairly well so far, but I can foresee some possible issues triggered
by packages which have a persistent state. An admittedly contrived example:
create or replace package test_pkg as
function invocations return number;
end test_pkg;
/
create or replace package body test_pkg as
cnt number(38) := 0;
function invocations return number is begin
cnt := cnt + 1; return cnt;
end invocations;
end test_pkg;
/
Is there a good and/or easy way to query for these beasties? I'd like to identify the potential candidates up-front if possible.
Thanx!
-- "I'm too sexy for my code." - Awk Sed Fred. -- http://www.freelists.org/webpage/oracle-lReceived on Wed Aug 06 2008 - 14:18:03 CDT