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

Recovery Problem
problem is considered restartable by DSM/SCM. To correct the situation, delete the
request using the ZPHITMI.
When you cancel a request, there is usually a point in the processing of the request
beyond which the cancel has no effect. Canceling a request sets a database flag that
you can look at later. A request was cancelled, but
the cancel seems to have no
effect.
Interface Troubleshooting
Maintenance Interface Troubleshooting
Recovery Problem
If MISERVER is not running, and if a database manager needs to be started, the logons
might seem to take a long time while the database manager process starts. The KBD ZPHIHMI or ZPHITMI logons
do not seem to be doing
anything.
LOCK indicator appears on the requestor screen while this occurs. Also, the ZPHIHMI
functions of archive and database maintenance take long periods of time during which
the requestor displays KBD LOCK.
The database relocate function might also take several minutes because the database
manager for the catalog must also be copied to the new location and SQLCOMP must
be run there. The Relocate Database
function does not seem to be
doing anything.
Because files are only put in the archive once even if they exist in multiple software
packages, deleting or backing up software in the archive must update many database The Archive Maintenance and
Delete System does not seem
to be doing anything.
entries. Files in the package being backed up or deleted remain on the system if they
are also referenced by another software package.
A TMF error or a SQL/MP error occurred during the operation. For more information
on the error, view the DBRELOUT file in the ZDSMSCM subvolume. A Database Relocate fails
with an internal error 507.
The Target maintenance>Modify... item of the Maintain menu entry was used to change
the profile values for a logical target, and a snapshot was received from the target
before another Build/Apply to that system. A profile is overwritten by a
snapshot.
A Build/Apply dialog box stated that the default volume for TSVs is invalid, and the
user changed the default in the profile after submitting that Build/Apply but before
receiving the snapshot.
Check file securities, existence, and so on in the source and destination locations. The
SCOBOL Requestors have internal error messages followed by an internal error number. Internal error messages occur
in ZPHIHMI or ZPHITMI.
However, these errors are often unexpected file-system errors, especially for operations
such as Archive Maintenance and Database Relocation, which perform extensive file
system operations.
The Pathway hometerm is not accessible. A link-denied error occurs in
ZPHIHMI or ZPHITMI.
The hometerm for Pathway specified in INITENV must remain available after the servers
are started. If the hometerm is specified on a network-connected system, make sure the
Expand connection is up.
ZPHITI Troubleshooting
Recovery Problem
If TISERVER is not running, and if a database manager needs to be started, the logon
might seem to take a long time while the database manager process starts. The KBD
LOCK indicator appears on the requestor screen while this occurs. ZPHTI logon does not seem to
be doing anything.
The Pathway hometerm is not accessible. A link-denied error occurs in
ZPHITI.
The hometerm for Pathway specified in INITENV must remain available after the servers
are started. If the hometerm is specified on a network-connected system, check that the
Expand connection is up.
190 Troubleshooting