AIX

I am new to AIX, but not new to the UNIX world. Recently I got a request to come with some kind of report to do the following: report if user query is using > 70% CPU (within DB2) > 5 minutes. I am by no means a DB2 guru so I do not know how to get that from within it, so I was wondering if there is another way to do it. Any help is appreciated.

I remember one of the DB/2 admins i worked with had a "Query Analyzer" he used to assess the workload a specific query causes - for the database. As far as i have understood it, it is an add-on tool not normally delivered with DB/2 but available on request. How much it tells you in OS terms (like CPU utilization) i don't know, but to the DB guys it was very helpful in optimizing their queries.

Alas, i doubt that it is possible to tie a specific CPU utiilization pattern to a certain query. DB/2 is a "shared-nothing" architecture and even the processes on the same system communicate over RPC-calls. Typically an opened but otherwise idle DB instance has about 1500 ("ps" becomes really really useful when you have a system with several instances, *cough*) processes and i have no idea what these are doing - probably that is confidential information anyways. To identify the one running your query is nigh impossible, i'd suppose.

I hope this helps.

bakunin

/PS: found it: "Visual Explain", accessible from the "Command Center"

Thanks bakunin. I checked for the Command Center on the server and it doesn't appear to be installed and I cannot install anything as my team doesn't have root privileges, although, we do have a back door if needed; which is OK'ed by the business. I also tried the ps approach, but unfortunately, it doesn't yield the necessary information I am looking for.

I wouldn't rely on such tactics, if i were you. If it isn't you at least someone has to have root-privileges and this one can be made responsible to install the software you need - or pass over root privileges to you. If this takes some time, then so be it - if the organization structure is designed in a way that nothing can get done in time than this organization structure has to be changed instead of trying to work around the problem. If the company decides to not pay for the electricity necessary to operate the server you wouldn't bring a battery to work, but make clear that work is impossible. The same principle is applying here: don't rely on backdoors but make sure things are changed in a way that work is possible - officially.

Just my two cents.

bakunin

Thanks for the info bakunin. I am working with the DBAs to determine how this can be done.