We had a problem 2 times now that when our Unix machine is bounced, it "looses" it's setting for DB2COMM. All the other settings seem to be okay. My understanding is that you only need to set this once, and it should remember it through reboots. Am I correct? Do I need to put it in the .profile or something?
No idea. My settings on the DB2 (on a Solaris box) are retained even after reboot. Did you check the diaglog.log file?
See if the setting was retained if you did a db2stop and db2start (ie DBM retstart)
I checked the db2diag.log. The only messages I have are as follows:
2004-11-04-188.8.131.523109 Instance:db2inst1 Node:000
common_communication sqlcctcpconnr Probe:110
DIA3202C The TCP/IP call "connect" returned an errno="22".
These started last night around 23:20. Our sysadmin noticed the application wasn't working around 3:00 am (don't ask why he was on the system then! ) He then rebooted the whole machine. When I got in, I found out about the problem.
And, like I said, the DB2COMM was set for the other 2 instances just fine. It's just one of them I have problems with. I'm baffled.
Under db2 home directory under sqllib there is a file profile.env.
It contains the db2 profile registry like DB2COMM . check that
it contains the that registry parameter, using the command
This is the file that instance read for finding the registry parameters.
Check file permissions. I think this should be a problem,