| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2550.1 | You Deleted the Alarms MIR !!! | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Mar 12 1992 07:50 | 16 |
| Denis,
FSCK deleted the Alarms MIR ... That is why you had no rules !!
I am not sure about the IO_ERROR you are getting ... but I suggest
that you Delete the Alarms MIR files again, and the re-enroll Alarms:
% rm /var/mcc/MCC_ALARMS_INSTANCE_MIR.pag
% manage
MCC> enroll mcc_alarms_fm
Alarms will recreate its MIR files during enrollment.
Give this a try, and let us know how it goes.
/keith
|
| 2550.2 | Vive DBM ! | TAEC::LAVILLAT | | Thu Mar 12 1992 07:57 | 35 |
| > During this FSCK , it found 2 bad files :
>
> /var/mcc/MCC_ALARMS_INSTANCE_MIR.pag
> /var/mcc/mcc_alarms_notification_log
>
I am not a DBM expert but the .pag file is working in combination with a .dir
file, so you should have removed *both* files.
> I already restored
>
>
>-rw-rw-rw- 1 root 4096 Mar 11 17:53 /var/mcc/MCC_ALARMS_INSTANCE_MIR.dir
>-rw-rw-rw- 1 root 4096 Feb 26 16:00 /var/mcc/MCC_ALARMS_INSTANCE_MIR.dir_bad
>-rw-rw-rw- 1 root 2048 Mar 11 17:53 /var/mcc/MCC_ALARMS_INSTANCE_MIR.pag
>
> but I still get the same error.
>
Yes, this is because these files are stupid files and cannot be restored (guess
it was from a backup file). This is because these file have holes in them that
are filled in when you back-up them (or something like that...)
>
> The next step , will be to deinstall/reinstall DECmcc but do you have
> any other idea to solve this problem ??
>
you should try first to remove both /var/mcc/MCC_ALARMS_INSTANCE_MIR.dir and
/var/mcc/MCC_ALARMS_INSTANCE_MIR.pag and re-enroll the ALARMS_FM.
Regards.
Pierre.
|
| 2550.3 | Check protection | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Thu Mar 12 1992 08:56 | 5 |
| Also, double check the ownership and protection of the alarms MIR files
after you re-create them.
-- Erik
|
| 2550.4 | It's working again....THANKSSSSSSSSSSSSS!!!!!! | BEAGLE::DIVINE | Denis DIVIN� @VBO (7)828-5450 (Valbonne-FRANCE) | Thu Mar 12 1992 09:22 | 30 |
|
Gentlemen,
Many thanks it's working again.
1] I removed only /var/mcc/MCC_ALARMS_INSTANCE_MIR.pag
When I enrol the ALARM_FM
>>>>>> SAME ERROR MESSAGE
2] I removed /var/mcc/MCC_ALARMS_INSTANCE_MIR.pag
&
/var/mcc/MCC_ALARMS_INSTANCE_MIR.dir
When I enrol the ALARM_FM
>>>>>> SAME ERROR MESSAGE
3] I kill DECmcc and retry my alarm definition
and NOW IT IS WORKING FINE..
Thanks again for your help , you save my life (or at least a customer demo)
Cheers,
/Denis
|
| 2550.5 | Some inaccuracies in previous note... | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Thu Mar 12 1992 09:34 | 7 |
| MIR (dbm) files *can* be backed up and restored. The problem is that
if they are very large (>5MB), the restored files may take more
physical space than the original files, but the data will be the same.
Also note that this only occurs if backup/restore is done with logical
file utilities like cp or tar. Physical copy utilities like dump(1)
will not lose space if you restore the files.
|
| 2550.6 | Sorry... | TAEC::LAVILLAT | | Thu Mar 12 1992 12:22 | 21 |
| >
> MIR (dbm) files *can* be backed up and restored. The problem is that
> if they are very large (>5MB), the restored files may take more
> physical space than the original files, but the data will be the same.
> Also note that this only occurs if backup/restore is done with logical
> file utilities like cp or tar. Physical copy utilities like dump(1)
> will not lose space if you restore the files.
>
Sorry then...
So why were we using things like mcc_dup / mcc_dlp some time ago ?
I really thougth it was not just a space/holes problem.
Anyway I still say : Vive DBM !
Regards.
Pierre.
|
| 2550.7 | More on DBM | MOLAR::BLACK | | Mon Mar 16 1992 14:17 | 33 |
| DBM files cannot be copied by normal means (cp, cat, tp, tar or ar)
without filling in the holes. Filling in the holes does not invalidate
the file; it does, however, eat disk space needlessly. The move
command, 'mv' does not fill in the holes unless, of course, if the move
results in a copy, i.e. moving from one file system to another.
Use of setld for installations forced us to depend on files being
copied by normal means as defined above. Since the dictionary was
huge, we provided mcc_dlp/mcc_dup to transport the dictionary to and
from ultrix installations and to copy the dictionary within an
installation. This greatly reduced the disk requirements for DECmcc
installations.
Beginning with baselevel x1.2.18 we will begin again using a DBM-based
dictionary. We provide a new tool, mcc_ndbm, to load and update DBM
files.
--------------------------------------------------------------------------
mcc_ndbm documentation --
mcc_ndbm is a simple utility that unloads (-u) and loads (-l) sparsely
populated databases (ndbm files). This utility is primarily for use
with the dictionary though it will work on MIR files as well.
mcc_ndbm requires three arguments:
mcc_ndbm -[u,l] <source> <destination>
mcc_ndbm -u ndbmfile outfile
mcc_ndbm -l infile ndbmfile
In and out files are variable length record files. Variable length
record files may have any extension. By default .dir/.pag are appended
to ndbm files. If a .dat extension is present on a ndbm file,
.dat/.dat.dir files are expected/created.
|