I have an ESE instance and Express-C instance. both with TCPIP communication manager enabled.
I am able to start stop db2 in Express-C [regular instance] even if network is off or down.
I am not able to start stop db2 in ESE [ESE instance with db2nodes.cfg] even if network is off or down
so if for some reason the network is down, some physical error with cables, then how do you start stop db2 if needed. I do not want to wait till the network problem is getting fixed right?
As per this file, if network is down, then it should still resolve machine/host name from /etc/hosts file.
so that should not prevent the db2 instance stop or start.
I do not what I am missing?
Harishkumar .Pathangay[Organization Members] @ Dec 17, 2017 - 10:56 PM (Asia/Calcutta)