20.2.8 Memory size required for the execution of optimizing the information collection utility (pdgetcst)

The following table shows the formulas for determining the memory size required for the execution of the optimizing information collection utility (pdgetcst).

ConditionFormula for determining memory size (KB)
HiRDB/Single Server6060 + 0.1 [Figure] number of table storage RDAREAs + 0.07 [Figure] number of index storage RDAREAs + 1.0 [Figure] number of indexes + 0.04 [Figure] number of tables in schema + 1.0 [Figure] number of servers + 11 [Figure] number of columns
HiRDB/Parallel ServerBES1813 + 0.06 [Figure] number of table storage RDAREAs + 0.05 [Figure] number of index storage RDAREAs + 0.03 [Figure] number of indexes
MGR3336 + 0.1 [Figure] number of table storage RDAREAs + 0.07 [Figure] number of index storage RDAREAs + 1.0 [Figure] number of indexes + 0.04 [Figure] number of tables in schema + 1.0 [Figure] number of servers + 11 [Figure] number of columns
DS16402
Note
Other than these sizes, add the memory size used by the following SQL:

SELECT internal-information*, index-first-configuration-column-name FROM authorization-identifier, table-identifier ORDER BY primary-index-component-column-name WITHOUT LOCK NOWAIT;

SELECT FLOAT (COUNT(*)) FROM authorization-identifier.table-identifier WITHOUT LOCK NOWAIT;
SELECT FLOAT (COUNT(primary-index-component-column-name)) FROM authorization-identifier.table-identifier WITHOUT LOCK NOWAIT;
ALTER TABLE authorization-identifier.table-identifier CHANGE LOCK ROW;
* The internal information is 12 bytes. Therefore, estimate as though an SQL statement were issued to retrieve a 12-byte character column (CHAR(12)), in addition to the index first configuration column name.
For details about the size of memory required by SQL, see the following sections: