NonStop dba/m Database Manager for NonStop SQL/MP Installation and Operations Guide (dba/m 6.0+)

5-2
Licensing dba/m Database Manager to Manually Update
Statistics
If you must update table statistics manually to simulate production statistics in
development nodes, you must license the GDBASQL process.
You can FUP-license and FUP revoke the process using the following commands:
FUP LICENSE GENPROG.GDBASQL
FUP REVOKE GENPROG.GABASQL
You must log onto the Himalaya System as SUPER.SUPER in order to license and
revoke the process.
Updating dba/m Database Manager Table Statistics
HP Computer recommends that you periodically run an update statistics operation on all
dba/m Database Manager tables. Table 5-1 in the next section provides the names of the
dba/m Database Manager tables.
Managing dba/m Database Manager Subvolumes and Files
dba/m Database Manager uses the following subvolumes in the installation volume and
GENUS subvolumes in $SYSTEM:
$SYSTEM.GENUS. Contains dba/m Database Manager configuration information
shown in one file named CONFIG.
GENBAT. Contains the edit files for every batch. The edit files contain the
SQLCI/IN <SQLEDT file> or SQLCOMP/IN commands generated by the GSQLBAT
process, depending on the type of batch. The edit-file name is the same as the batch
number assigned on the client when the batch is created.
GENCOLL. Contains edit-type files, which have the output from SQLCI or
SQLCOMP, depending on the type of batch. The contents of the files are displayed
on the Results screen. The edit-file name is the same as the batch number.
GENCAT. Contains the SQL catalog tables for the GENCAT catalog.
GENDB. Contains the files listed in Table 5-1.