6.10 Database Shutdown By Batch

In PET how soon are you looking at the DB status? I have seen, from time to time, a delay of up to 5 minutes in this correctly showing the DB as started. Maybe give it some time and refresh rather than trying to start it. I have also seen it take awhile after the admin service starts for it to even let me manually start the DB so I think all this might be related to things in the service startup.

Cool idea though for the batch routines.

-Todd C.


-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]On Behalf Of Richard Bailey
Sent: Thursday, September 28, 2006 10:54 AM
To: UserGroup
Subject: [Vantage] 6.10 Database Shutdown By Batch



Our mains power is being disconnected on Saturday a.m and I can't be there
to bring the databases and servers down gracefully also I'm unsure (a) how
long our UPS will keep us up and (b) How long the outtage will last.

Therefore I've written a simple batch file to force an emergency shutdown of
the database which seems to work OK (basically "proshut mfgsys -by -F").
I'll schedule this to run before the outtage will happen.

Then I thought, why not schedule a batch start for later on Saturday after
power is restored (assume that I've turned off the auto start option on the
database because power will be off & on sporadically), so again I wrote a
simple batch file (basically "proserve mfgsys -S 6100 -H name -N TCP"). This
seems to start the database OK and I can log in to Vantage successfully
HOWEVER in Progress Explorer Tool the database still shows as 'stopped' and
gives an error if you try and start it (not unreasonably).

Any ideas re what I'm missing or +/- of adopting such an approach.
Thanks in advance

Regards,
Richard

Richard Bailey
Dudley Industries
Mailto: rbailey@dudleyindus <mailto:rbailey%40dudleyindustries.co.uk> tries.co.uk
Tel: +44(0)1253 738311
Mob: +44(0)7836 550360
Fax: +44(0)870 7628173







[Non-text portions of this message have been removed]
Our mains power is being disconnected on Saturday a.m and I can't be there
to bring the databases and servers down gracefully also I'm unsure (a) how
long our UPS will keep us up and (b) How long the outtage will last.

Therefore I've written a simple batch file to force an emergency shutdown of
the database which seems to work OK (basically "proshut mfgsys -by -F").
I'll schedule this to run before the outtage will happen.

Then I thought, why not schedule a batch start for later on Saturday after
power is restored (assume that I've turned off the auto start option on the
database because power will be off & on sporadically), so again I wrote a
simple batch file (basically "proserve mfgsys -S 6100 -H name -N TCP"). This
seems to start the database OK and I can log in to Vantage successfully
HOWEVER in Progress Explorer Tool the database still shows as 'stopped' and
gives an error if you try and start it (not unreasonably).

Any ideas re what I'm missing or +/- of adopting such an approach.
Thanks in advance

Regards,
Richard

Richard Bailey
Dudley Industries
Mailto: rbailey@...
Tel: +44(0)1253 738311
Mob: +44(0)7836 550360
Fax: +44(0)870 7628173