| No particular ideas, however I should point out that there ARE ways
to delete objects from a database that won't propogate to other nodes.
For example, MBMAN DELETE DDS SUB/.../RESTRICT allows you to do this.
(typically used to remove stale copies of objects from WSnodes when
the master copy has been lost from the owning node).
You could try rebuilding the AIF file; DDS can't find an object in the
PERMDB without an attribute pointer in the AIF file (except by DDSID).
Dave
|
| Hi Dave,
They will try the rebuild if there is no other way. For now , they
have some DDSIDs of entries that are missing. You told us that if DDS
searchs by DDSids, it doesn't check the aif file so iI could make
this search and see if the entries are there. This would really show
us if the rebuild is necessary or not but I didn't find any command to
search entries by ddsid.
Is there any way to do it? They want to execute the rebuild only if
it is really necessary because their machine is on production and they
are afraid that this could impact the performance they have now.
Thanks .. Marcia
|
| Standard MBMAN doesn't support searching by DDSID. A 32 character
hexadecimal string isn't something most customers want to deal
with... However, if they are running MR V3.3A on VMS V6.1 or higher,
the MBMAN image in the XDDS (aka MAILbus Directory Migration Toolkit)
kit does support some operations (SELECT and DELETE as I recall) by
DDSID. FYI, the kit has an "MBMAN subset only" installation option.
There is also an obscure utility in the MR kit that can do it, but
it's undocumented and very tedious to use. Given that the primary RMS
key of the PERM_DB file is the DDSID, with a little time and effort
you could write yourself a little program or com file and try to
read the record by its key (but don't expect to be able to make any
sense out of the data, and DON'T do it while DDS is running).
Dave
|