extend the timeout for the SQLPLUS
happy
Mladen Gogala
> How can I extend the timeout for the SQLPLUS sql commands entry ?
You can create profile with the limit on CONNECT_TIME, something like this
SQL> create profile myprof limit connect_time 30;
Profile created.
Elapsed: 00:00:00.38
SQL>
That will drop the connection after 30 minutes, along with any query that
might be executing at that time. You can also limit CPU_PER_CALL which is
not the exact time limit but will usually kill all the queries that take
longer than 5*CPU limit. It does take a little experimenting, though.
Mark D Powell
> How can I extend the timeout for the SQLPLUS sql commands entry ?
happy, by default SQLPlus itself does not have a timeout. If your
sessions are being timed out then there are several ways it can be
done. mgogala identified database user profiles as one method. The
Oracle database resouce manager can also be used to time out sessions
and kill queries that exceed resource limits.
Many DBA set up dead/idle connection detection scripts that identify
and kill sessions that have not done any work in X time.
Also many Firewalls will close connections throught he firewall that
have not been active for X time.
If mgogala's solution does not appear to fit whatever unposted actual
message you are getting then maybe one of these other items fit.
HTH -- Mark D Powell --