| Title: | + OpenVMS Clusters - The best clusters in the world! + |
| Notice: | This conference is COMPANY CONFIDENTIAL. See #1.3 |
| Moderator: | PROXY::MOORE |
| Created: | Fri Aug 26 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5320 |
| Total number of notes: | 23384 |
Hi all,
We have installed VAXCOMPAT_062 on a VAX 4000-106A without reboot. For
configuration information see the end of the note.
I then wanted to install VAXCLUSIO01_062 in order to get the correct
shadowing software. The installation failed with the following message:
%DCL-W-ACTIMAGE, error activating image MOUNTSHR
-CLI-E-IMGNAME, image file DSA500:[SYS4.SYSCOMMON.][SYSLIB]MOUNTSHR.EXE
-SYSTEM-F-BADVEC, invalid change mode or message vector
In fact, every attempt to use BACKUP gives the above message.
Also, an attempt to us MOUNT results in the very same message beibg displayed.
I am very reluctant to try a reboot because I suppose the system is rendered
unbootable (it will mount its system disk as a shadow set, and it will mount
more shadow sets later during bootstrap).
What's wrong with VAXCOMPAT_062 (aka 'Redhawk')?
Btw, I can't find it in TIMA any more. Is this a hidden hint not to use it?
Raymond.
PS:
The system is running OpenVMS V6.2 with the following patches applied
(in this order):
VAXSHAD05_062
VAXDRIV03_070
VAXMSCP01_070
VAXDRIV04_070
VAXMANA02_070
It is an NI-member (FDDI) of a two site VMScluster with 2Alphas (OpenVMS V6.2)
and 2VAXen (OpenVMS V6.2).
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5245.1 | INSTALL REPLACE previous version | TIMABS::FREPPEL | Mosquito ergo summm... | Fri Mar 07 1997 07:53 | 9 |
Obviously VAXCOMPAT INSTALL REPLACEs SYS$SHARE:MOUNTSHR.EXE. After
renaming MOUNTSHR.EXE;0 to .COMPAT and INSTALL REPLACing the provious
version the message mentioned in the base note did not reappear.
MOUNT and BACKUP work as expected.
But what other components may have been affected by applying VAXCOMPAT?
Is this expected behaviour?
Raymond.
| |||||
| 5245.2 | VMSSG::FRIEDRICHS | Ask me about Young Eagles | Fri Mar 07 1997 09:39 | 29 | |
I'm not quite sure I follow all of the logic in .0...
The CLUSIO kit is a superset of the COMPAT kit. It has everything
in the COMPAT kit plus additional SHADOW and MOUNT fixes.
Both kits also include lots of files. Some of them, like IO_ROUTINES,
SHDRIVER and others will not get loaded until the required system
reboot. Other images, such as SDA, SHOW and MOUNT may get invoked
before a reboot.
Until the system has been rebooted, there are no guarantees what will
and won't work correctly. You have proven that there is at least
one dependency... There are more. This is not a sign that the kit
is broken in any way. Also, be careful renaming images.. If you
reboot it with the new MOUNTSHR image renamed, but the old IO_ROUTINES,
SYSINIT and SHDRIVER still installed, then you are probably going to
be in trouble. At least you have the backup of your system disk.
I can't tell you why you can't see the kits on TIMA anymore. I will
check into that. But I can tell you that I did not put a hold on it.
Please reboot the system. Thanks!
Cheers,
Jeff Friedrichs
COMPAT/CLUSIO project leader
OpenVMS Engineering
| |||||
| 5245.3 | reboot is required ! | HAN::HALLE | Volker Halle MCS @HAO DTN 863-5216 | Sun May 18 1997 04:57 | 11 |
One of our customers has made the same experience after installing
ALPCLUSIO01_062 and then trying to install ALPDRIV08_062 without an
intermediate reboot.
A reboot after xxxCLUSIO installation solved that problem.
Volker.
re: .0 You do NOT need to install the xxxCOMPAT kit first. Just install
the xxxCLUSIO.
| |||||