The server OS is Windows Server 2003. All the workstations are Windows
XP or Windows 2000.
> Utilities heap size (4KB) (UTIL_HEAP_SZ) = 88338
> Buffer pool size (pages) (BUFFPAGE) = 400000
> Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = 26646
You need to check if the sizes mentioned above are not too high. Check
the size of the available bufferpools with the command 'select char
(bpname, 30) as bpname, npages, pagesize from syscat.bufferpools'. If
NPAGES = -1 then the bufferpool uses at least 1.6 GB, depending on the
pagesize. This might be too much for your system, check if it's paging
too much.
With a bufferpool of this size it will also take some extra time for
your first connection to connect because all memory needs to be
allocated. To prevent this you can activate the db with the ACTIVATE
DATABASE command. Before creating a backup you need to use the
DEACTIVATE DATABASE command because otherwise the backup will fail.
Ray - 26 Apr 2006 21:50 GMT
When I run the SQL statement select char(bpname,30) as bpname, npages,
pagesize from syscat.bufferpools I get the following results
BPNAME NPAGES PAGESIZE
------------------------------ ----------- -----------
IBMDEFAULTBP 350000 4096
How can I tell if the system is paging to much?
Ray
tuarek - 26 Apr 2006 22:31 GMT
Gert,
I don't think this is a memory/bufferpool issue. Otherwise, Ray should
see db2 error messages in the windows server event log.
Ray:
I think you have an user authentication problem. Check how long does it
take you to connect to server with your network username & password?
Then create a local user on the server machine and then connect with
this user. If there is a big difference in between them, this can
explain your problem.
Regards,
Mehmet