[optimal] Re: OIS capture station issues...
- From: "Stratton, Rick" <RSStratton@xxxxxxxxxxxxx>
- To: "'optimal@xxxxxxxxxxxxx'" <optimal@xxxxxxxxxxxxx>
- Date: Tue, 14 Aug 2012 13:36:28 -0400
Understood.
Setting up local DB's on your 2 working capture stations would only take a few
minutes each with the help of Merge Support.
From: optimal-bounce@xxxxxxxxxxxxx [mailto:optimal-bounce@xxxxxxxxxxxxx] On
Behalf Of sandor ferenczy
Sent: Tuesday, August 14, 2012 1:32 PM
To: optimal@xxxxxxxxxxxxx
Subject: [optimal] Re: OIS capture station issues...
Thanks for the thoughts Rick, the issue is much more immediate than that - just
trying to figure out how to get 70 more patients through the clinic today.
so far we are doing panorets on all of them. the patients arent so happy with
that :)
On Tue, Aug 14, 2012 at 1:14 PM, Stratton, Rick
<RSStratton@xxxxxxxxxxxxx<mailto:RSStratton@xxxxxxxxxxxxx>> wrote:
If Capture1 was serving as the DB host and the system is down, you have a
couple of options.
1. If the Hard Drive containing the actual DB is still in working
condition, you're in good shape. A failed power supply or motherboard should
not effect the data on the HDD. You can transfer the DB from Capture1 over to
Capture2 and designate Capture2 as the new DB host. This would require a
reconfig of Captures 2&3 both in ODBC and the INI config file. Unless you know
exactly what you're doing I would STRONGLY advise consulting MERGE/OIS support
for this.
2. If the Capture1 HDD is still good and you wish to get it repaired
instead of replaced, you can configure Capture2 and Capture3 to temporarily use
a local DB. Once Capture1 is repaired and back online you would then transfer
what your shot on 2 & 3 over to Capture1 so that those exams get merged back
into the main DB. Again, unless you've done this before it's a good idea to
consult with MERGE support for assistance.
I will tell you that this is not as intimidating as it sounds IF you're
familiar with ODBC, SQL and how Winstation works but there are quite a few
steps in the process and you can truly muck things up if you don't know what
you're doing. We had a similar scenario many years ago on a somewhat larger
scale - air conditioning in a datacenter failed in the middle of the night
causing a dramatic temperature spike in the room and emergency shutdown of all
systems. Our DB servers were spared but we were without their use for a few
days until the A/C problem was resolved. We setup a couple of Winstation
machines to function using a local DB until the main DB came back online and we
were able to import the exams back in.
From: optimal-bounce@xxxxxxxxxxxxx<mailto:optimal-bounce@xxxxxxxxxxxxx>
[mailto:optimal-bounce@xxxxxxxxxxxxx<mailto:optimal-bounce@xxxxxxxxxxxxx>] On
Behalf Of sandor ferenczy
Sent: Tuesday, August 14, 2012 12:57 PM
To: optimal@xxxxxxxxxxxxx<mailto:optimal@xxxxxxxxxxxxx>
Subject: [optimal] Re: OIS capture station issues...
thats what i have been looking for.
when someone inadvertently restarts the capture1 machine, the others can
continue to capture, so i know it *can* do it, just need to figure out how to
force the issue.
On Tue, Aug 14, 2012 at 12:47 PM, James Strong
<jamesdstrong@xxxxxxxxx<mailto:jamesdstrong@xxxxxxxxx>> wrote:
Can you open the .ini file and identify where the main DB is defined and modify
it to point to capture 2? Probably not that simple...but it doesn't hurt to
look.
After saving a copy of the original .ini, of course.
j-
On Tue, Aug 14, 2012 at 12:26 PM, sandor ferenczy
<sandorferenczy@xxxxxxxxx<mailto:sandorferenczy@xxxxxxxxx>> wrote:
So, question for the collective...
If the main OIS capture station (capture1 we'll call it) dies (CPU power supply
or motherboard) is there any way to quickly get the other capture stations
(capture2, capture3, etc) up and running?
as it sits now, capture1 is dead, and capture2 and capture3 will not start the
Winstation application, as they cannot connect to the database (which resides
on capture1)
any quick help is much appreciated!
-sandor
Other related posts:
