Richard Sims [SMTP:rbs AT BU DOT EDU] wrote:
[various answers]

Hi Richard, thanks for taking the time to answer, and thanks for the sample
shutdown script, I'm sure I can do something similar for my server.

It's a pity the startup/shutdown processes are so lacking in the product
itself, hopefully Tivoli are working to improve on this.

> The best cause of db mangling is in your computer, opsys, or TSM suddenly
> going away, without graceful shutdown, with just a single image of your
> db.
> Use TSM db mirroring, with MIRRORWrite Sequential to stay out of trouble.
>
Thanks for the hint, I see the defaults are sequential for the DB and
parallel for the log.
Would you recommend changing the log to sequential as well, or leave it as
is?  Normally I'm inclined to trust defaults unless I know better, but
certain... experiences... have make me wary.

> Server programming errors also result in "interesting" situations,
>
Hopefully this won't occur, as we have a policy of testing all changes in
the lab before applying them to production.