Re: Long Sessions

pcarr01 wrote:
On Aug 18, 5:49 pm, DA Morgan <damor...@xxxxxxxxx> wrote:
pcarr01 wrote:
Hi,
We have an issue with the amount of time that a firewall will hold a
session open.
Currently we have 72 hours, this drives the security and network
people crazy but we have a requirement for stuff like very long
database queries, launch an ssh or sqlplus session onto an oracle box
and the session expires before the query finishes and we lose the
result, very bad when you are working on a problem at 3 in the
morning
and the Damages for not getting the database back up by 5 are in 6
figures.
How does the industry in general deal with this sort of issue?
A number of thoughts.

The first parallels Sybrand's ... a 72 hour query is outrageous.
Get someone in to tune it.

The second is that this query should not be running through the
firewall and be, in any manner, dependent upon the survival of
a session.

Have the query report its output to a table and then log on later
to retrieve the resultset, then SELECT * FROM report_table, or use
a materialized view to produce the result set in the first place.
--
Daniel A. Morgan
University of Washington
damor...@xxxxxxxxxxxxxxxx (replace x with u to respond)
Puget Sound Oracle Users Groupwww.psoug.org

Appreciate the comments on performance but this isnt an oracle issue
its a network issue that affects oracle.
I was working on a problem that was exposed because Oracle 8 had known
issues with bitmapped indexes and that was what ruined the
performance, we were running queries and doing updates in a diagnostic
and recovery context that were not returning within an acceptable
timescale & if some network device had detected no activity then ..
bang .. query lost. There is no way I could have done this without
some sort of client session on the target platform be it ssh, plus80
or whatever.

I did ask the question on the firewall group.


The question is

I've no doubt you believe what you just wrote but you are incorrect.
A client connection is not required to run anything on Oracle, and
once something is started, is not required to keep it running.

I have run reporting regimens that took 60 hours to complete using a
database connection that lasted a fraction of a second.

If you are ready to put away your assumptions reconsider what I wrote.
--
Daniel A. Morgan
University of Washington
damorgan@xxxxxxxxxxxxxxxx (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
.

Relevant Pages

  • Re: kill query w/o killing session?
    ... I completed chapter 27, Using the Database Resource Manager, of the Oracle ... automatic consumer group switching resource plan directives. ... allows 0 execution time, effectively killing the query. ... allowed for a session. ...
    (comp.databases.oracle.server)
  • Re: Long Sessions
    ... We have an issue with the amount of time that a firewall will hold a ... launch an ssh or sqlplus session onto an oracle box ... a 72 hour query is outrageous. ... Puget Sound Oracle Users Groupwww.psoug.org ...
    (comp.databases.oracle.misc)
  • Re: Debug ORA-03113 on Oracle XE
    ... a laptop that runs the Oracle 10g Express ... The query returns no rows with the current data set but it's pretty ... If Oracle XE generates further info I don't know where I ... I just read Oracle had such feature and I figured out it could be handy: automagical session isolation and data removal looked cool at the time. ...
    (comp.databases.oracle.server)
  • Re: Long Sessions
    ... We have an issue with the amount of time that a firewall will hold a ... database queries, launch an ssh or sqlplus session onto an oracle box ... Puget Sound Oracle Users Groupwww.psoug.org ...
    (comp.databases.oracle.misc)
  • Re: ODBC Pass-Through Queries
    ... Doing a "select * from ThisTable" on a certain table in Oracle 10g ... query slaves available". ... This can be easily fixed in a native Oracle session by issuing the ... this session parameter to the server, but cannot run two queries ...
    (microsoft.public.access.queries)