Re: Application architecture & prod/pre-prod switcheroos
- From: Edgar Chupit <chupit@xxxxxxxxx>
- To: "Murching, Bob" <bob_murching@xxxxxxxxx>
- Date: Thu, 26 Jan 2006 14:09:58 +0200
Bob,
Is this application using packages? If so, than to reset package
state, immediately after getting connection from the pool, application
probably calls dbms_session.reset_package procedure, to reset values
of the package variables to initial state.
Does this application validates connection that it gets from
connection pool (because if connection is killed, connection pool
still can pass this connection to application) If so, than you can ask
developers to change validation procedure (usually they execute
something simple, as select 1 from dual), to call your procedure that
will modify session state (current_schema).
You can ask developers to include a call to some procedure in the
beginning of the session, that will not only reset state of all
packages, but also will change current_schema according to a value in
some configuration table.
I think to solve this problem more simpler (and have a better night
sleep), you should work around this with development team, because it
is much simpler to change few lines of code, than to develop bunch of
scripts that you still have to monitor.
Just my 2 cents.
On 1/25/06, Murching, Bob <bob_murching@xxxxxxxxx> wrote:
> Now *that's* ingenious... But again, there's that established connection
> pool that the J2EE app is using. The sessions are persistent, so login
> triggers wouldn't work...
--
Best regards,
Edgar Chupit
callto://edgar.chupit
--
//www.freelists.org/webpage/oracle-l
Other related posts:
