DAS autostart glitch

[Lamimi02]

I am running DB2 V8.1 FP2 on Linux. When I turn on autostart with the dasauto
command, DAS starts automatically after first reboot but not after second
reboot. Is this a bug?

[Mark A]

"Lamimi02" <lamimi02@aol.com> wrote in message
news:20030902203355.14444.00000320@mb-m12.aol.com...

> I am running DB2 V8.1 FP2 on Linux. When I turn on autostart with the

dasauto

> command, DAS starts automatically after first reboot but not after second
> reboot. Is this a bug?

Works OK on my Linux box. Did you do this as the DAS user (probably dasusr1
if you used the default).

[Bob [IBM]]

Something to look into possibly is the Fault Monitor... ensure that the fault monitor daemon is running and set to monitor that instance... I think it is by default but strange things happen.

--

Bob
IBM Toronto Lab
IBM Software Services for Data Management
"Lamimi02" <lamimi02@aol.com> wrote in message news:20030902203355.14444.00000320@mb-m12.aol.com...
I am running DB2 V8.1 FP2 on Linux. When I turn on autostart with the dasauto
command, DAS starts automatically after first reboot but not after second
reboot. Is this a bug?

[Lamimi02]

It works on my other Linux box too. The only difference is the Linux version.
Yes, I used dasusr1 account. Actually I could start das in one of the rc
scripts, but I would rather have dasauto working.

[Lamimi02]

The Fault Monitor was started automatically every time. How do I see what it is
monitoring? Is autostart setting being stored in some config file? Thanks for
your reply.

[Bob [IBM]]

Well my "understanding" is that the fault monitor will only autostart those instances that have had the autostart set with DB2IAUTO ... having said that you can use the "db2fm" utility to check the status of the fault monitor daemon and also the fault monitors for each instance. If they are running then it "should" have started the instance if the autostart registry variable was set by using the db2iauto command. Such is my understanding anyway ...

--

Bob
IBM Toronto Lab
IBM Software Services for Data Management
"Lamimi02" <lamimi02@aol.com> wrote in message news:20030903195318.03483.00000330@mb-m11.aol.com...
The Fault Monitor was started automatically every time. How do I see what it is
monitoring? Is autostart setting being stored in some config file? Thanks for
your reply.

[Bob [IBM]]

As an addition to my previous statements - you can use the db2fm command to ensure the daemon is up, running and that the individual monitors are also up and running ... see db2fm -h for details ... I hope that helps ....

--

Bob
IBM Toronto Lab
IBM Software Services for Data Management
"Bob [IBM]" <NoSpamPlease@ibm.com> wrote in message news:bj637r$mmk$1@news.btv.ibm.com...
Well my "understanding" is that the fault monitor will only autostart those instances that have had the autostart set with DB2IAUTO ... having said that you can use the "db2fm" utility to check the status of the fault monitor daemon and also the fault monitors for each instance. If they are running then it "should" have started the instance if the autostart registry variable was set by using the db2iauto command. Such is my understanding anyway ...

--

Bob
IBM Toronto Lab
IBM Software Services for Data Management
"Lamimi02" <lamimi02@aol.com> wrote in message news:20030903195318.03483.00000330@mb-m11.aol.com...
The Fault Monitor was started automatically every time. How do I see what it is
monitoring? Is autostart setting being stored in some config file? Thanks for
your reply.

[Bob [IBM]]

As an addition to my previous statements - you can use the db2fm command to ensure the daemon is up, running and that the individual monitors are also up and running ... see db2fm -h for details ... I hope that helps ....

--

Bob
IBM Toronto Lab
IBM Software Services for Data Management
"Lamimi02" <lamimi02@aol.com> wrote in message news:20030903195318.03483.00000330@mb-m11.aol.com...
The Fault Monitor was started automatically every time. How do I see what it is
monitoring? Is autostart setting being stored in some config file? Thanks for
your reply.