Scott,
Do a list applications and see if the logger and kernel threads are
conencted to the control database. If not then put your userid and password
into the db2cli.ini file and restart logger and kernel etc.
See if they start now, This may not be your problem and may not ecen be the
solution but worth a go.
I have been through a similar exercise and found the above happening (on
AIX). I have reported this to IBM as a problem but did find that updating
the db2cli.ini helped (although may be a temp fix).
Richard
"ScottH" <fa*********@newsgroupsonly.com> wrote in message
news:6v********************@giganews.com...
Well, I spoke too soon. I thought all was well due to seeing the
processes started automatically. When I try to start the DWC I get
An unexpected communication error has occurred.
Connection refused: no further information.
RC=6200 RC2=0
<sigh>
It may have something to do with the security tag in the registry. This
may be different on different machines and is a way of detecting a tampered
install.
Scott
"ScottH" <fa*********@newsgroupsonly.com> wrote in message
news:Rp********************@giganews.com... I am running DB2 7.2 FP8e with the Data Warehouse Center (using Tivoli
Data Warehouse). Everything was humming along fine. I defragged all my
drives without bringing DB2 down (should have known better). When I rebooted,
the vwkernel and vwlogger services were gone. Not listed at all, not in the
registry. I could open a command prompt, go to SQLLIB\BIN and run them
manually, so I knew it wasn't hopeless. I got a registry export (for
just those two services) from someone else running the same env, imported,
rebooted and all is well again.
Does this sound possible, that a defrag could wipe out a service ? The
databases don't seem any worse for the wear.
Thanks,
Scott
