[533] in Tooltime
Re: locked logs
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Mon Nov 17 13:42:58 1997
In-Reply-To: <v03110700b0961a8787aa@[18.162.2.67]>
Date: Mon, 17 Nov 1997 13:47:21 -0500
To: Peter Ragone <pragone@MIT.EDU>
From: Steven Wade Neiterman <wade@MIT.EDU>
Cc: tooltime@MIT.EDU
Peter,
Regarding your senario (Morning arrives - which I happen to believe is
always a good sign):
My guess is that the Scopus GUI will give an Oracle error message before
the user can update any records. Remember, the database is taken down each
night for backup. Thus any connections are lost, which would result in an
error.
Your welcome to try this if you would like.
..Steve
At 11:09 AM -0500 11/17/97, Peter Ragone wrote:
>>lock on the record. Each locked record needs to be cleared one at a time.
>>
>>Here is what I propose. Let's run a SQL statement once each night to
>>unlock all currently locked records.
>>
>
>Okay. I understand how to unlock the records. Before we write a SQL
>statement to unlock logs, I think we should investigate what happens in the
>following common scenario:
>
>- Student leaves Scopus client running after he leaves his shift (they know
>they shouldn't).
>- Evening arrives and the client is still running, showing a log which
>means that it's locked and for a valid reason.
>- The SQL statement to unlock all records runs.
>- Morning arrives.
>
>Now this might happen:
>- Someone might exit from Scopus, which would do what to the state of the
>log which is now unlocked but Scopus is trying to release its lock before
>exiting?
>- Someone might try to alter that log before exiting Scopus. What would
>this do?
>
>Hmmmm.. Food for thought.
>
>By the way, Scopus things seem to be going okay. We'll try to figure out
>what's causing the the records to be locked by Richard Luong right now.
