| 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 |
*********************
*** URGENT PLEASE ***
*********************
Vaxstation 4000.90 SPXg
VAX/VMS V5.5-2
DECMCC BMS 1.3 + elm AM+FM 1.3
image name: "MCC_MAIN"
image file identification: "DECMCC V1.3-0"
link date/time: 9-FEB-1993 14:17:25.53
When trying to start a Historian session with Bridge partition, i got
an error with ENQLM quota exceeded. After ENQLM quota modification (50->600)
i'm not able to access DECMCC environment with iconic and FCL anymore.
Can someone explain what is going wrong ? and what to do to recover my
environment without installing, registering a lot of entities, compiling new
MIBs and so on ...
Regards,
Guy.
follow somme command examples: same behaviour with other entity classes ...
------------------------
$mana/enter dir domain *
DECmcc (V1.3.0)
%MCC-W-REPOSNONAME, repository ID 49 is missing name, attempting recovery
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
000E4FA0 000E4FA0
0007452A 0007452A
00085791 00085791
000EAADB 000EAADB
000E3B80 000E3B80
001172E7 001172E7
0007452A 0007452A
00085791 00085791
000EAADB 000EAADB
001177EB 001177EB
001069BA 001069BA
00555341 00555341
000B1F71 000B1F71
0007A8AB 0007A8AB
0007506C 0007506C
000857B1 000857B1
000B2079 000B2079
001008A7 001008A7
000BF85F 000BF85F
000BF567 000BF567
000BF4E9 000BF4E9
000BEF29 000BEF29
000BEA10 000BEA10
000BE82F 000BE82F
001E82E0 001E82E0
001E901E 001E901E
001E7AE5 001E7AE5
001EAD71 001EAD71
001EA147 001EA147
001E5A52 001E5A52
001E5769 001E5769
000D6362 000D6362
MCC_MAIN main 7756 00000208 000020B4
0000596F 0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE 163 00000027 000059A3
0000594A 0000594A
%MCC-E-REPOSNORECOV, could not recover from repository errors
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
000E5101 000E5101
0007452A 0007452A
00085791 00085791
000EAADB 000EAADB
000E3B80 000E3B80
001172E7 001172E7
0007452A 0007452A
00085791 00085791
000EAADB 000EAADB
001177EB 001177EB
001069BA 001069BA
00555341 00555341
000B1F71 000B1F71
0007A8AB 0007A8AB
0007506C 0007506C
000857B1 000857B1
000B2079 000B2079
001008A7 001008A7
000BF85F 000BF85F
000BF567 000BF567
000BF4E9 000BF4E9
000BEF29 000BEF29
000BEA10 000BEA10
000BE82F 000BE82F
001E82E0 001E82E0
001E901E 001E901E
001E7AE5 001E7AE5
001EAD71 001EAD71
001EA147 001EA147
001E5A52 001E5A52
001E5769 001E5769
000D6362 000D6362
MCC_MAIN main 7756 00000208 000020B4
0000596F 0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE 163 00000027 000059A3
0000594A 0000594A
----------------------------
$ mana/enter show domain *
AT 10-JUN-1993 16:36:14
The requested operation cannot be completed
MCC Routine Error = %MCC-F-MIR_INIT_FAIL, the MIR could
not be initialized
------------------------------
$ mana/enter test mcc 0 notif
DECmcc (V1.3.0)
%MCC-W-REPOSNONAME, repository ID 49 is missing name, attempting recovery
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
000E4FA0 000E4FA0
0007452A 0007452A
00085791 00085791
000EAADB 000EAADB
000E3B80 000E3B80
0055E69F 0055E69F
0054FDC8 0054FDC8
000CDDC2 000CDDC2
001007B3 001007B3
000BF85F 000BF85F
000BF567 000BF567
000BF4E9 000BF4E9
000BEF29 000BEF29
000BEA10 000BEA10
000BE82F 000BE82F
001E82E0 001E82E0
001E901E 001E901E
001E7AE5 001E7AE5
001EAD71 001EAD71
001EA147 001EA147
001E5A52 001E5A52
001E5769 001E5769
000D6362 000D6362
MCC_MAIN main 7756 00000208 000020B4
0000596F 0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE 163 00000027 000059A3
0000594A 0000594A
%MCC-E-REPOSNORECOV, could not recover from repository errors
%TRACE-E-TRACEBACK, symbolic stack dump follows
module name routine name line rel PC abs PC
000E5101 000E5101
0007452A 0007452A
00085791 00085791
000EAADB 000EAADB
000E3B80 000E3B80
0055E69F 0055E69F
0054FDC8 0054FDC8
000CDDC2 000CDDC2
001007B3 001007B3
000BF85F 000BF85F
000BF567 000BF567
000BF4E9 000BF4E9
000BEF29 000BEF29
000BEA10 000BEA10
000BE82F 000BE82F
001E82E0 001E82E0
001E901E 001E901E
001E7AE5 001E7AE5
001EAD71 001EAD71
001EA147 001EA147
001E5A52 001E5A52
001E5769 001E5769
000D6362 000D6362
MCC_MAIN main 7756 00000208 000020B4
0000596F 0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE 163 00000027 000059A3
0000594A 0000594A
%MCC-E-DSPMMLOCFILERR, dispatch local management module file access error during
probe
%MCC-E-DSPMMLOCFILERR, dispatch local management module file access error during
probe
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5179.1 | TOOK::GUERTIN | MCC: Legend or Nightmare? | Tue Jul 06 1993 16:20 | 10 | |
When the MIR subsystem of MCC starts up on VMS, it does a first pass
verification of the MIR Master Repository (MCC_MIR_INSTANCE.DAT and
MCC_MIR_ATTRIBUTE.DAT). If it finds any corruptions it attempts to
recover by deleting the partial records. In your case it tried to
delete the partial records, but failed. Usually, it fails because
the user does not have write access to these "master" repository files.
The solution is generally to run MCC from an account which has
read/write access to these files.
-Matt.
| |||||