Kbase P18591: Interrogating database with VSTs only reads first 50 tables and indexes
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/01/2008 |
|
Status: Verified
FACT(s) (Environment):
All Supported Operating Systems
SYMPTOM(s):
Using Virtual System Tables (VST): _TableStat (for table activity)
Using Virtual System Tables (VST): _IndexStat (for index activity)
Startup parameters -basetable -tablerangesize -baseindex -indexrangesize are specified on the 4GL broker
Only the first 50 tables and indexes are reported
The SQL-92 broker is the primary broker
CAUSE:
If the startup parameters that are used to define the table or index range to be traced are not specified, Progress will trace the first 50 by default.
In this case, although the startup parameters -basetable -tablerangesize -baseindex -indexrangesize are specified, they are defined on the 4GL broker which is declared as the secondary broker and therefore ignored.
FIX:
The startup parameters need to be set for tracing table and index activity:
- on the client startup command line for single-user mode
or
- on the primary database broker startup command line for multi-user mode
These startup parameters define the table or index range in scope of your investigation, they are:
-basetable n /* the first table number for the trace range*/
-tablerangesize n /* the number of tables from -basetable n that need to be traced */
-baseindex n /* the first index number for the trace range */
-indexrangesize n /* the number of indexes to be included starting from -baseindex */
Other VSTs like _usertablestat and _tablestat uses the base starting table and number of tables to restrict what it monitors. The base table can be changed at runtime but the # of tables to monitor cannot.