db2diag tool doesn't use attached instance db2diag.log

meehange · #1 (**permalink**) 09-06-11, 00:48

8.2/9.1 on Windows

It's been a while since I've worked on a Windows environment and this one has several instances defined on the same box. I would have assumed that when I run db2diag that it picks up the db2diag.log of the instance I am currently attached to, but it's not doing this. I can specifiy the path to the diag.log in the db2diag command and this works fine.... but if I don't specify a path to the file it looks like it defaults to the db2diag.log of the first created instance.

Can't find any doco on this.... Normal behavior or a poorly configured install?

przytula_guy · #2 (**permalink**) 09-06-11, 02:10

have you tried : set db2instance=xxx to work with that instance instead of attach
execute db2diag..

n_i · #3 (**permalink**) 09-06-11, 07:55

Quote:

Originally Posted by meehange

I would have assumed that when I run db2diag that it picks up the db2diag.log of the instance I am currently attached to

Why would you? db2diag is an application that runs in its own process space, and as such it has no way of knowing what db2bp (another application) is attached to.

meehange · #4 (**permalink**) 09-06-11, 20:14

Quote:

Originally Posted by n_i

Why would you? db2diag is an application that runs in its own process space, and as such it has no way of knowing what db2bp (another application) is attached to.

I dunno, I would have though the utility a little more useful/user friendly if it were context sensitive. After all I'm obviously more likely to want to perform diagnostics on the instance/DB that I'm currently connected to, right?

przytula_guy - that worked a treat, thanks

Internet Services

Web Development

Digital Marketing

Consumer Tech