ron
Member
Linux 3.10.0-1160.2.2.el7.x86_64 x86_64
OE 11.7.4 Enterprise
Hi, We have:
-tablerangesize 350
-indexrangesize 550
... and those settings comfortably accommodate the tables and indexes in our "user" system. By default, of course, the -baseindex and -basetable are both zero.
As things are we make quite a lot of use of the table and index statistics for analysing activity in our database. But, of course, there is also quite a bit of "other" activity -- especially with respect to Auditing. I see that the table numbers for Auditing are around the -300 mark. There are also many system tables between -1 and -299 which, I presume, are Schema tables. There are also tables way up in the -16000 range which I presume are VSTs.
I wish to collect the table and index statistics for Auditing. I have never set -basetable or -baseindex to negative values before. Is there anything "special" that I need to know before I delve into this new realm?
By the way (in case you ask) -- the I/O with respect to Auditing is "considerable". I am aware of ways to address that by hiving-off the reporting part of it to a second database. That is something we will do, but we can't do it in the short term.
Ron.
OE 11.7.4 Enterprise
Hi, We have:
-tablerangesize 350
-indexrangesize 550
... and those settings comfortably accommodate the tables and indexes in our "user" system. By default, of course, the -baseindex and -basetable are both zero.
As things are we make quite a lot of use of the table and index statistics for analysing activity in our database. But, of course, there is also quite a bit of "other" activity -- especially with respect to Auditing. I see that the table numbers for Auditing are around the -300 mark. There are also many system tables between -1 and -299 which, I presume, are Schema tables. There are also tables way up in the -16000 range which I presume are VSTs.
I wish to collect the table and index statistics for Auditing. I have never set -basetable or -baseindex to negative values before. Is there anything "special" that I need to know before I delve into this new realm?
By the way (in case you ask) -- the I/O with respect to Auditing is "considerable". I am aware of ways to address that by hiving-off the reporting part of it to a second database. That is something we will do, but we can't do it in the short term.
Ron.