We’ve got a new security policy in place where any connection idle longer than
15 minutes gets dropped. Needless to say, this is a little annoying if I’m
writing code or editing a data grid and get up to visit the water cooler. Come
back, have to reconnect, possible edits not committed, etc.
Does anyone have a creative solution, like a box I could click in the settings,
that would allow a TOAD window (editor, browser, etc) to somehow ping the
database from time to time, so as to appear active? Alternatively, comments like
“stop cheating, follow the rules, here’s why…” are also welcome.
DBMS_OUTPUT polling or the refresh rate in the Session Browser might help, but
now that Toad is a threaded application, often times those things happen on a
separate connection than the one the editor is tied to. You could try disabling
‘Execute Queries in Threads’ and see if that does it.
Oh, and if you get caught cheating the system, make sure that you get blamed and
not Toad
–to see the profile you just created
SELECT * from DBA_PROFILES where PROFILE=‘CH04_PROF’;
–ALTER the profile to set IDLE limit time to 300 secs (5 min)
ALTER PROFILE CH04_PROF LIMIT IDLE_TIME 300;
–create a user which will use the profile
CREATE user MATTHEW identified by *******
GRANT CONNECT to MATTHEW
GRANT CREATE SESSION to MATTHEW
GRANT RESOURCE to MATTHEW
GRANT UNLIMITED TABLESPACE to MATTHEW
ALTER USER MATTHEW PROFILE MATTHEW_PROFILE
COMMIT;
–you now have 300 sec connect time before Idle time parameter disconnects you
Martin Gainty
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n’êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l’expéditeur. N’importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l’information seulement et n’aura pas n’importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
Just a thought – if your companies auditing department has installed a
policy and the DBA is merely complying – then doing this (trying to fake
activity) could lead to grounds for dismissal (depending on how grumpy your
company is on such stuff).
But that said – 15 minutes is ridiculously short – it takes me 15
minutes just to type hello world program
I would advise seeking to get limit raised to 30 minutes and then living within
that yoke ….
While it’s fun for me to fantasize how to ‘beat the system’,
if I worked with you, I would never try this myself. Jobs are too hard to come
by these days.
I’m guessing your DBAs don’t have the same 15 minute limit. It seems
somewhat arbitrary and I’m with Bert, advocate for a higher limit.
It’s also worth nothing that some of the Sarbanes-Oxley legislation just
got struck down by the Supreme Court. I wonder how long it will take for the
pendulum to start swinging back, if ever.
One other workaround comes to mind – you could download and install Oracle
Express database to do long coding sessions – and then when you’re
close and just need to compile in dev/test – then move the code there.
It’s not a great solution – but it totally removes the timeout issue
J
And yes – the pendulum will eventually swing back – but usually not
until after we’ve lost both our hair and sanity J
15 minutes here is definitely a security audit mandate, not a DBA choice. Thanks
for your creative ideas, but aside from not wanting to get fired, any solution
that involves remembering to do something with my own brain every time I stand
up and walk away from my desk, or in advance of doing certain types of work, is
destined to fail. And I like the “execute queries in threads” option too much to
give it up.
15 minutes here is definitely a security audit mandate, not a DBA choice. Thanks
for your creative ideas, but aside from not wanting to get fired, any solution
that involves remembering to do something with my own brain every time I stand
up and walk away from my desk, or in advance of doing certain types of work, is
destined to fail. And I like the “execute queries in threads” option too much to
give it up.
