[an error occurred while processing this directive]

HP OpenVMS Systems

ask the wizard
Content starts here

MOUNT RMTMNTFAIL Error and File Corruption?

» close window

The Question is:

 
The Problem in Analyze/RMS/FDL:
 
    In 11/26, we do the database backup for our
application. We dismount the shadow set member
to finish the job. But when we finished the
job, and try to mount the shadow set member to
its original shadown set, system tell us the
message:
%MOUNT-I-MOUNTED, PROMSECDB2 mounted on _DSA6:
%MOUNT-I-SHDWMEMCOPY, _$6$DUA62: (HSJB08) added to the shadow set with a
copy operation
%MOUNT-I-ISAMBR, _$6$DUA61: (HSJB09) is a member of the shadow set
%MOUNT-W-RMTMNTFAIL, _DSA6: failed to mount on node VIS06
-MOUNT-F-NOTQUEUED, request not queued
 
    And then, we do the backup database in 12/3,
and try to tune the database (RMS format), but when we tried to use the
command:
$analyze/rms/fdl $6$dua62:[dbsecb]hist.ism
to analyze the hist.ism file, the result file:
HIST.FDL has such error:
ANALYSIS_OF_AREA 2
        RECLAIMED_SPACE         0
***  VBN 19267585:  Pointer size of 3 is invalid in data record.
Unrecoverable error encountered in structure of file.
 
    We could not make sure whether they has any
relationship. But we hope to know how to solve
it. Could we repair the file or other way to
let the file to normal status.
 
                           Thank you!
 
 


The Answer is :

 
  It is not clear if these two events are linked.
 
  If you wish to pursue this, please contact the Compaq Customer Support
  Center directly -- direct examination of the corrupted RMS file will
  likely be needed.  You will likely also be encouraged to install the
  ALPMOUN07_071 and ALPSHAD05_071 kits, as well as the ALPRMS04_071 and
  ALPF11X06_071 kits.
 
  The OpenVMS Wizard will assume that the MOUNT command included /CLUSTER.
  (Please remember to always include the DCL command(s) involved...)
 
  The typical (rare) cause of the apparent problem underlying the MOUNT
  error is a race condition that can arise when multiple cluster members
  are all trying to mount the particular volume at the same time.  The
  node that looses -- node VIS06, in this case -- fails to acquire a
  needed lock due to the contention, and this message is then displayed.
 
  The underlying lock contention -- if that is the actual problem causing
  this error -- is remedied in OpenVMS V7.2 and later.
 
  Please upgrade to OpenVMS Alpha V7.1-2 to get the ECO kits for V7.1, or
  (far better) to V7.2-1, or later.
 
 

answer written or last revised on ( 6-DEC-1999 )

» close window