Hi Karol, here's the gstat information I got once I was able to get the
database to effectively go into a tailspin when I finished updating that table:
The database:
Database header page information:
Flags 0
Checksum 12345
Generation 67880
Page size 16384
ODS version 10.1
Oldest transaction 65630
Oldest active 67799
Oldest snapshot 67799
Next transaction 67864
Bumped transaction 1
Sequence number 0
Next attachment ID 0
Implementation ID 19
Shadow count 0
Page buffers 1024
Next header page 0
Database dialect 3
Creation date Feb 18, 2019 12:56:24
Attributes force write
Variable header data:
Sweep interval: 20000
*END*
The table in question:
CLAIM_LOAD (283)
Primary pointer page: 282, Index root page: 328
Average record length: 1272.01, total records: 990032
Average version length: 1402.69, total versions: 91345, max versions: 1
Data pages: 91470, data page slots: 92296, average fill: 94%
Fill distribution:
0 - 19% = 0
20 - 39% = 0
40 - 59% = 1
60 - 79% = 0
80 - 99% = 91469
Does this give you anything of interest that I should address?
Myles
