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

Recovery Problem
File Discrepancies
An SPR might be missing, or an old version of the file might be in the configuration. Try
placing the correct version of the file into the configuration. File discrepancies appear in
a discrepancy report.
NSKCOM produces SRLs during a DSM/SCM Build. Therefore, they always turn up as
discrepancies. These discrepancies are not a problem, so you can accept them. SRLs appear as discrepancies
in a discrepancy report.
DSM/SCM does not replace the files: An SPR is in the configuration
that is not on the target.
1. Delete or rename the files with discrepancies from the target system (only if they are
not needed for operation).
2. From the ZPHITI, run the Verify Database and Independent Snapshot requests.
3. Receive the snapshot into the host (automatic if you specify that the host has a network
connection to the target when you run ZPHIHMI).
4. Run the discrepancy report again. Missing files show a discrepancy of Not Found,
and the versions in the new revision are sent on the next Apply.
For the Initialization Build/Apply, you used an RVU other than the RVU actually installed
on the target. The discrepancy report shows
many products not found on
Use the RVU you installed on the target when you submit an Initialization Build/Apply
request.
the system although they are
there, or the report shows
many products found on the
system although they are not
there.
Place the correct SPR into the configuration. An SPR was not included in
the configuration.
These files can be accepted as discrepancies because they were changed by normal
system operations. Discrepancies appear in
HOSTS (TCP/IP), SERVICES
(TCP/IP), or edit files that you
customize (such as SxxxTMPL
files).
Request Troubleshooting
Recovery Problem
The DSM/SCM File Manager cannot access files on virtual disks managed by the
Storage Management Foundation (SMF). You receive file-system error
5001 during a request such
Retry your request without using files stored on SMF-managed virtual disks.
as receiving software or an
Apply.
A Create Snapshot, Apply,
Backout, retrieve operator 1. Check any status messages appearing on the screen.
2. Display any EMS messages (press F4).
instructions, or Verify
3. If a message appears indicating that the request is restartable, correct the problem
and restart the request (press F3).
Database request stops before
it finishes.
Check the related EMS messages, collect as much information as possible about the
problem, then contact your HP representative. After the problem is diagnosed, cancel
the request. If the cancel also stops nonrestartable, use the ZPHITMI to delete the request. A message appeared
indicating that a request has
stopped in a nonrestartable
state.
You cannot restart it from the NonStop Software Essentials Request Status page or select
Receive Snapshot from the home page and specify the snapshot location provided in
the EMS messages from the Apply request at the target system. A snapshot request from the
target system stops in a
restartable state.
If you cannot correct an error that causes a request to stop in its final stages, you might
not be able to cancel the request even though it is restartable. For instance, an error A request that stops in a
restartable state is not
accepting cancellation.
occurs on interfacing to BACKUP when creating a snapshot package to tape, and the
Request Troubleshooting 189