| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Customer upgraded VMS from V5.5-1 to V5.5-2, after restoreing the CMA files from the savesets mcc still cannot be run. From the FCL a 'dir node4 *' returns: MCC-W-REPOSNONAME, Repository ID 43 is missing name, Attempting recovery. A stack dump follows this message with a could not initialize mir. Which mir file is it complaining about? What is Repository ID 43? Any helpful hints on recovery? Steve Woestemeyer CSC/CS - Network Support Team
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5418.1 | try this | TRKWSH::COMFORT | Here beside the rising tide | Wed Aug 04 1993 15:19 | 21 |
Hi Steve -
Ya, I've experienced this. Sorry I didn't read the note earlier. If
you do not yet have the solution, then it probably will be fixed by
restoring the following two files from before the upgrade:
MCC_INSTANCE_MIR.DAT
MCC_ATTRIBUTE_MIR.DAT
What apparently happens is that during one of the reboot phases of the
VMS upgrade the system time is set to that date when VAX time began or
whatever in the 1800's. The VMS startup does a full startup, including
all layered products, before shutting down again and during that time
the MCC software starts up and somehow corrupts those files. I believe
that if the MCC startup is commented out before such an upgrade, this
problem will not occur (though I have no hard data to back this up
yet).
Dave
| |||||