HP Integrity NonStop H-Series - Manual (Page 233)

Troubleshooting
DSM/SCM User’s Guide — 529846-014
13 - 8
Database Management Troubleshooting
Database Management Troubleshooting
Problem Recovery
Performance slows
during actions that
reference the database. On certain backward migrations, the Database Managers need
SQLCOMP run to be compatible with the SQL PVU. If
performance slows, the SQL statistics might be out of date for the
tables. In either case, run SQLCOMP for the Database Manager.
Enter:
> VOLUME $volume.ZDSMSCM

> RUN UPDATES
UPDATES is installed only on the host system. To run UPDATES
on a target system, copy UPDATES from the host system to
$volume
.ZDSMSCM on the target system. Then run it as
described here.
UPDATES takes from five to twenty minutes to run, depending on
the system on which you are running it.
After you back out a
revision, the Database
Managers are not
compatible with the SQL
PVU. If SQLCOMP is performed on the database manager or
managers on a newer RVU (by INITENV on that RVU, or
manually), and you fall back to an earlier RVU, you might need to
perform SQLCOMP for the database managers on the earlier
RVU.
If you fall back to an earlier SQL/MP PVU, you might also need
to downgrade the SQL catalog for DSM/SCM (for example, falling
back to D20 from D30):
1. Change the volume to XPHIHDB (host database catalog) or
Xtarget-system-name (target database catalog).
2. SQLCI DOWNGRADE CATALOG TO n (where n is the
SQL/MP PVU; for example, 2 for SQL Release 2 [D20]).
An OM Database
Constraint Error from
the Planner Interface, or
an Internal Error 279
from ZPHIHMI, occurs
while you are logging
on. This might indicate an SQL error with PHIHDBMG. The OM DB
Constraint Error is misleading. The error could be any of several
SQL errors encountered by the host database manager. Check
for TMF and SQL errors, such as a database volume not being
audited or TMF at the MAXFILES limit.
Otherwise, the error condition might be recoverable by running
SQLCOMP on PHIHDBMG:
1. Enter:
> VOLUME $volume.ZDSMSCM

> OBEY ADDHDEFS

> SQLCOMP /IN PHIHDBMG, OUT ZPHICOMP/

CATALOG $vol.XPHIHDB
2. Check ZPHICOMP for successful SQLCOMP.
These SQL restrictions might be relaxed in certain PVUs. Other
SQL restrictions most likely exist as well.