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

Recovery Problem
This error might also indicate a SWID error such as unresolved externals.
The software revision was not based initially on an RVU. During a Build request, a
message indicates that the
Create a new revision, then do one of:
release is not supported, or that
the RVU is not supported.
• Select an RVU to copy to the configuration revision.
• Select the T6032 product for the site ID to copy. NonStop Software Essentials
shows the RVU selected above the new revision table.
The RVU of a configuration revision is needed in order to choose the correct tools
for building the configuration (the correct system generation program and correct
version of tools a system generation program runs). This release level is obtained
when an RVU is selected from the Source Software table and a Copy to a revision
is performed. This RVU is not changed if you select List Products on Software in
Archive inputs and then select products to copy to the new revision.
Not enough disk space is available on the host disk where you are creating the
activation package. When you perform a Build only,
without an Apply, including all
When creating an activation package that includes all files, use a disk with at least
1 gigabyte of space.
files and creating the activation
package on a disk on the host,
an error 43 occurs.
The default for a Build/Apply is to send only changed files. Activation packages
are usually created to tape or transferred over the network.
The Build, Apply, and Process Snapshot (auto Build/Apply) option does not have
this problem because its activation package contains only headers that describe the
changed files, not the files themselves. The actual files are retrieved over the network
from the archive as needed.
A Build-only (manual Build/Apply) activation package, created on tape or disk,
contains the files themselves because the user transports the files to the target system
manually, either by carrying the tape or by using a file transfer of the activation
package files on the disk.
The Build cannot find an archive location needed to perform the Build because the
archive is being moved while the Build is running. Do not relocate the archive during
Build or Build/Apply requests. A Build request, performed at the
same time as an archive
relocation, fails.
Cancel the failed request and then resubmit the Build request.
The Apply cannot find an archive location that the Build references because the
archive is being moved while the Build/Apply is running. Do not relocate the archive
during Build or Build/Apply requests. An Apply request fails after a
configuration was built and an
archive relocation was started.
Cancel the failed request and then resubmit the Build/Apply request.
Discrepancy Troubleshooting
Recovery Problem
TSV Discrepancies
DSM/SCM assumes that if it finds at least one file in a TSV that is also in the
configuration, that TSV is a candidate for management by DSM/SCM. However, if The first part of the
discrepancy report lists TSVs
DSM/SCM also finds the TSV on more than one volume, it cannot determine the correct
volume to use. under the heading
DUPLICATE TSV INFO.
DSM/SCM therefore lists the volumes in the snapshot it sends to the host but does not
mark any of them for management by DSM/SCM. If a TSV is listed only once, it is on
more than one volume. But in one of the volumes, no files in the TSV match any of those
in the configuration.
When you accept these duplicate TSVs, they appear in the TSV list as new TSVs flagged
by an asterisk (*). You must decide which TSV is correct. Try matching files that have
the same expected and actual fingerprints. If the fingerprints match, the discrepancy is
not a problem. However, you should decide if the target volume is correct because it
is not the one indicated in the configuration.
You need to perform a new Build/Apply to address duplicate TSVs.
188 Troubleshooting