Hi,
Apologies if this has been asked before, or is a really lame question.
We currently have lots of locking problems running a web-deployed (J-initiator on
Win2k) off-the-shelf application.
The application is running from an Oracle Forms 6i patch 12 application server on
Windows 2000 sp4 and
Hi!
1) You can set idle_time profile option in server, to automatically
disconnect sessions idle for some time.
2) You can set sqlnet.expire_time to some minutes or hours, that Oracle
would probe all sessions over some interval and disconnect the ones which
don't have a corresponding client
Simon,
Look for CREATE PROFILE in the SQL Reference for setting a limit on idle times.
SF
- --- Original Message --- -
From: Simon Gregory
[EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L
[EMAIL PROTECTED]
Sent: Fri, 26 Sep 2003 03:39:41
Hi,
Apologies if this has
Simon
Just another idea for you, that may or may not be helpful. I haven't
worked with Forms, others on this list can provide some ideas. However, I
have seen some weird behavior from Micro$oft apps based on VB and ASP. If
the database connection is left with mostly defaults, the app will tend
Tanel,
What is normal overhead for option 2. and repercussion in case of Oracle
Financials implementations.
Regards
Rafiq
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Date: Fri, 26 Sep 2003 04:17:35 -0800
Hi!
1) You can set idle_time profile option
