On Jan 15, 2006, at 10:27 AM, Bhaskar, KS wrote:
My guess is that while database structural integrity is restored,
there
is invalid information in the database such as information about
processes that no longer exist since they died with the crashing
system.
Right. It's liker cache coherence: memory may be in a consistent
state, even if that state is "impossible" from the point of view of
an application.
There must be a procedure in VistA to clean out this type of
information.
There is (sort of). For example, if a scheduled task is marked a
RUNNING but there is no corresponding process, you may need to edit
the task before deleting. In general, you should always use the menu
option (in this case "Delete a Task") over Fileman, if at all
possible. Other problems are possible, too. The first step is
diagnosing the problem.
-- Bhaskar
===
Gregory Woodhouse
[EMAIL PROTECTED]
"You must unlearn what you have learned."
--Yoda
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
