Conference azur::mcc

6179.0. "MIB install failure" by BRAT::BUKOWSKI () Tue Nov 22 1994 13:32

Why is this MIB install failing?  Has anybody in DEC installed the
    DECserver accounting MIB successfully??????
    
    any help appreciated,
    thanks, Mike
    
    
            <<< NOTED::DISK$NOTES6:[NOTES$LIBRARY_6OF4]MCC.NOTE;2 >>>
                        -< DECmcc - Internal Use Only >-
================================================================================
Note 6171.4               DEC_SERV MIB install problem                    4 of 4
ABACUS::BUKOWSKI                                     98 lines  21-NOV-1994 09:54
                               -< failed again. >-
--------------------------------------------------------------------------------

    
    RE:-1
    
    Well, I commented out the sysUptime, and the install proceeded much
    further, but now it only complete 40% of the 'MANAGE/TOOLKIT/DICTIONARY
    MERGE' command.   What do I do now?  Help!
    
    Mike
              .
              .
              .
              .
Sorting character cell help topics.
Sorting windows help topics.
Verifying hierarchy...
    Verifying for character cell
    Verifying for windows
Processing file(s)....
MCC help files updated.
MCC help files updated.
Cleaning up any intermediate files...
Now copying ".HLB" files to SYS$COMMON:[SYSHLP] ...
Copy completed.
HELP build completed successfully.
  18-NOV-1994 13:48:07

Phase 1 for file SYSB$:[MCC]DEC_SERV.TXT; completed.

Beginning Phase 2 for file SYSB$:[MCC]DEC_SERV.TXT;


Now checking DECmcc data dictionary for subclass dec ...
%DAP-S-USE_DICT, Using dictionary file: sysb$:[mcc]mcc_fdictionary.dat;4
Found definition.

The definition for the dec MIB
  already exists in the DECmcc data dictionary.
You have the option of REPLACING or AUGMENTING this definition.

Do you want to REPLACE the existing definition? (Y/N) [Y]: n

Do you want to AUGMENT the existing definition? (Y/N) [Y]:

  18-NOV-1994 13:49:59
Now starting to run the MSL Translator ...
This may take approximately 1-10 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/SPECIFICATION DEC_SERV.MS
DECmcc Management Specification Language Translation Tool
               Version V1.3.0

%MCCMSL-S-NORMAL, Scan of MS file has completed successfully
MSL translation completed successfully.
  18-NOV-1994 13:50:15

  18-NOV-1994 13:50:15
Now starting to update the DECmcc data dictionary ...
This may take approximately 1-15 minutes.
Issuing following command:
  $ MANAGE/TOOLKIT/DICTIONARY MERGE CLASS SNMP SUBCLASS dec FROM DEC_SERV.COM
%DAP-S-USE_DICT, Using dictionary file: sysb$:[mcc]mcc_fdictionary.dat;4
Percent of file processed =  40%
%DAP-I-LINENUMB, At or near line number 1834.
%DAP-I-CMD_LINE, Command: CREATE CLASS SNMP  SUBCLASS DEC  SUBCLASS EMA  SUBCLAS
Using parse table log file: sysb$:[mcc]mcc_fdictionary.log;21
Building containment tree file

Containment tree file built, objects=55717, size = 519936
Reading parse table file: sysb$:[mcc]mcc_fdictionary.bpt;33

Please wait while parse tables are updated
  Processing entity 18 5036
%MCCPTB-I-NOENTRY, No dictionary entries found.
   No attributes defined for entity class.
  Processing entity 18 5036 2
%MCCPTB-I-NOENTRY, No dictionary entries found.
   No attributes defined for entity class.
  Processing entity 18 5036 2 1
  Processing entity 18 5036 2 1 1
  Processing entity 18 5036 2 1 2
  Processing entity 18 5036 2 1 3
  Processing entity 18 5036 2 1 4
              .
              .
              .
              .
Writing parse table file.  Please wait...
Created parse table file: sysb$:[mcc]mcc_fdictionary.bpt;34
Parse table build complete.
%MCC-E-NOENTITY,  no corresponding entity instance exists

An error occurred while trying to update the DECmcc data dictionary.

  18-NOV-1994 16:21:44

Procedure terminated in error.
%NONAME-E-NOMSG, Message number 0326CF0A

    I've run into similar errors then the first MIB for the enterprise, in
    this case DEC, or a previous MIB load was done with the prune option =
    yes.  I think what's happening is that the accounting MIB load is
    looking for a child that doesn't exist.  What I had to do is delete the
    enterprise and begin the DEC MIB loads again.
    
    You are not getting any messages about the MIB being too deep and
    forced pruning occuring are you?  
    
    Gary