Hello, we are running QAD 8.6e on Progress 8.3C, sitting on HP-UX. We have two databases, mfgpro85e (which is fine) and addmfgpro (which suddenly starting being slow today; was fine Fri and Sat). Users always connect to both db when entering app. Queries against the slow db are running about 10x slower than the comparable queries against the test version of the addmfgpro database (week-old copy) or the other database. Compiling and data dictionary against the slow db also seem noticeably slower. GLANCE says everything is wonderful (CPU, disk utilization, network, memory).
We've been adding lots of users over the past few months, so I suspect -B needs to be raised in the problem database (addmfgpro). What does ProgressTalk think? I don't have a lot of experience in this kind of Progress DB tuning, any help appreciated.
Some parameters below. TIA.
adddmfgpro (slow)
Shared Resources:
Busy After Image Extent: /u103/PRODATA/addmfgpro.a2
Number of database buffers (-B): 60000
Number of before image buffers (-bibufs): 150
Number of after image buffers (-aibufs): 225
Before-image file name (-g): -
Before-image truncate interval (-G): 60
No crash protection (-i): Not enabled
Maximum total of all private buffers (-I): 424
Current size of locking table (-L): 360000
Locking table entries in use: 4
Locking table high water mark: 27
Maximum number of clients per server (-Ma): 4
Delay of before-image flush (-Mf): 120
Maximum number of servers (-Mn): 42
Maximum number of users (-n): 169
Before-image file I/O (-r -R): Raw
Shared memory version number: 8303
Number of semaphores used: 215
mfgpro85e (fine)
Shared Resources:
Busy After Image Extent: /u14/PRODATA/mfgpro85e.a1
Number of database buffers (-B): 225100
Number of before image buffers (-bibufs): 350
Number of after image buffers (-aibufs): 500
Before-image file name (-g): -
Before-image truncate interval (-G): 60
No crash protection (-i): Not enabled
Maximum total of all private buffers (-I): 424
Current size of locking table (-L): 720000
Locking table entries in use: 318
Locking table high water mark: 7038
Maximum number of clients per server (-Ma): 4
Delay of before-image flush (-Mf): 30
Maximum number of servers (-Mn): 42
Maximum number of users (-n): 169
Before-image file I/O (-r -R): Raw
Shared memory version number: 8303
Number of semaphores used: 215
We've been adding lots of users over the past few months, so I suspect -B needs to be raised in the problem database (addmfgpro). What does ProgressTalk think? I don't have a lot of experience in this kind of Progress DB tuning, any help appreciated.
Some parameters below. TIA.
adddmfgpro (slow)
Shared Resources:
Busy After Image Extent: /u103/PRODATA/addmfgpro.a2
Number of database buffers (-B): 60000
Number of before image buffers (-bibufs): 150
Number of after image buffers (-aibufs): 225
Before-image file name (-g): -
Before-image truncate interval (-G): 60
No crash protection (-i): Not enabled
Maximum total of all private buffers (-I): 424
Current size of locking table (-L): 360000
Locking table entries in use: 4
Locking table high water mark: 27
Maximum number of clients per server (-Ma): 4
Delay of before-image flush (-Mf): 120
Maximum number of servers (-Mn): 42
Maximum number of users (-n): 169
Before-image file I/O (-r -R): Raw
Shared memory version number: 8303
Number of semaphores used: 215
mfgpro85e (fine)
Shared Resources:
Busy After Image Extent: /u14/PRODATA/mfgpro85e.a1
Number of database buffers (-B): 225100
Number of before image buffers (-bibufs): 350
Number of after image buffers (-aibufs): 500
Before-image file name (-g): -
Before-image truncate interval (-G): 60
No crash protection (-i): Not enabled
Maximum total of all private buffers (-I): 424
Current size of locking table (-L): 720000
Locking table entries in use: 318
Locking table high water mark: 7038
Maximum number of clients per server (-Ma): 4
Delay of before-image flush (-Mf): 30
Maximum number of servers (-Mn): 42
Maximum number of users (-n): 169
Before-image file I/O (-r -R): Raw
Shared memory version number: 8303
Number of semaphores used: 215