By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,226 Members | 1,027 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,226 IT Pros & Developers. It's quick & easy.

8.2 Windows: Health Monitor not always work

P: n/a
I had trouble to get the hmon work in 8.x FP 8 and FP 9 .

The server runnig Windows 2003 SP1 on a member server.

The db2 services are running under an domain admin account.

Ok, no problem so far (HMON working) .

Now i had made a special local group a the member server (contains both
local and domain admin accounts and some local accounts without local
windows admin rights) and i had aaded these group to SYSADM_GROUP .
After restart, HMON does nothing.

For "get health snapshot for dbm", DB2 reports after houres of run
at the "instance highest severity alert state" "Not yet evaluated"

With diaglevel "3" DB2 reports no error. With diaglevel "4" you may
see this error:

2005-05-17-11.52.50.982000+120 I3330566H1014 LEVEL: Error
PID : 5652 TID : 2824 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ******* APPHDL
: 0-27 APPID: *LOCAL.DB2.050517095250
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : Hexdump, 136 bytes
0x08784948 : 5351 4C43 4120 2020 8800 0000 BCFB FFFF SQLCA
.........
0x08784958 : 0D00 4144 4D49 4E49 5354 5241 544F 5200
...ADMINISTRATOR.
0x08784968 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0x08784978 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0x08784988 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0x08784998 : 0000 0000 0000 0000 5351 4C45 5843 4D4E
.........SQLEXCMN
0x087849A8 : 0000 0000 0000 0000 0000 0000 0000 0000
.................
0x087849B8 : 0000 0000 4000 0000 2020 2020 2020 2020 ....@...

0x087849C8 : 2020 2020 2020 2020

2005-05-17-11.52.50.982000+120 I3331582H619 LEVEL: Severe
PID : 5788 TID : 5344 PROC : db2fmp.exe
INSTANCE: DB2 NODE : 000
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1092 sqlerrml: 13
sqlerrmc: ADMINISTRATOR
sqlerrp : SQLEXCMN
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

The workaround for me is:

"db2set DB2_GRP_LOOKUP=,TOKEN" !!!

Now it works fine. IBM should investigate in this problem. It was very
hard to troubleshoot this.

I had already opened a PMR, but it was not a great help .

-Zahni

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
za*****@gmx.de wrote:
I had trouble to get the hmon work in 8.x FP 8 and FP 9 .

The server runnig Windows 2003 SP1 on a member server.

The db2 services are running under an domain admin account.

Ok, no problem so far (HMON working) .

Now i had made a special local group a the member server (contains both
local and domain admin accounts and some local accounts without local
windows admin rights) and i had aaded these group to SYSADM_GROUP .
After restart, HMON does nothing.

For "get health snapshot for dbm", DB2 reports after houres of run
at the "instance highest severity alert state" "Not yet evaluated"

With diaglevel "3" DB2 reports no error. With diaglevel "4" you may
see this error:

2005-05-17-11.52.50.982000+120 I3330566H1014 LEVEL: Error
PID : 5652 TID : 2824 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : ******* APPHDL
: 0-27 APPID: *LOCAL.DB2.050517095250
FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
DATA #1 : Hexdump, 136 bytes
0x08784948 : 5351 4C43 4120 2020 8800 0000 BCFB FFFF SQLCA
........
0x08784958 : 0D00 4144 4D49 4E49 5354 5241 544F 5200
..ADMINISTRATOR.
0x08784968 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x08784978 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x08784988 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x08784998 : 0000 0000 0000 0000 5351 4C45 5843 4D4E
........SQLEXCMN
0x087849A8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x087849B8 : 0000 0000 4000 0000 2020 2020 2020 2020 ....@...

0x087849C8 : 2020 2020 2020 2020

2005-05-17-11.52.50.982000+120 I3331582H619 LEVEL: Severe
PID : 5788 TID : 5344 PROC : db2fmp.exe
INSTANCE: DB2 NODE : 000
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1092 sqlerrml: 13
sqlerrmc: ADMINISTRATOR
sqlerrp : SQLEXCMN
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:

The workaround for me is:

"db2set DB2_GRP_LOOKUP=,TOKEN" !!!

Now it works fine. IBM should investigate in this problem. It was very
hard to troubleshoot this.

I had already opened a PMR, but it was not a great help .

-Zahni

Had this problem too. Hope the next Fixpack will all help us.

cu,

indika
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.