| Title: | X.500 Directory Services |
| Notice: | Sprt: FORTY2::X500_SUPPORT, Kits: 216.*, try dir/titl=OFFICIAL |
| Moderator: | FORTY2::PULLEN |
| Created: | Tue Jan 30 1990 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1016 |
| Total number of notes: | 4299 |
Hi X.500 V2.0 Customer reports a corrupt entry in X.500. Errors: Using dxim to look at entry, it should show Common Name but it shows Common Name with hex characters including control characters When shadowing the naming context to another DSA an event is reported: Event: Shadow update failure Reason: schema incompatible Naming context is not replicated Tried to delete the entry unsuccessfully Tried to select the tree the entry is in and delete it - all other entries went but not that one He would like to know how to delete entry i.e. force deletion He also would like to know whether, if the solution is to rebuild the database, can he rebuild it on another machine and then copy the files to the original amchine - he wants to do the rebuild without having to take his live DSA out of service. Thanks Jill
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 979.1 | a-101.tunnel.crl.dec.com::FORTY2::PALKA | Andrew Palka Altavista Directory | Thu Feb 27 1997 12:03 | 19 | |
There is no way to force the deletion of an entry. If it can't be deleted with dxim then it probably can't be deleted at all, other than by patching the database by hand. It would be best to recreate the database if possible. This can be done on another system running the same version of the dsa (same kind of operating system). You should also plan to upgrade to version 3 as soon as possible to avoid these problems in the future. Use the field test of V3.1 for VMS or Unix V4 or wait till ECO 4 is available for Unix V3. If you cant go to V3 then at least upgrade to the latest ECO kit for V2. If this kind of problem arises with X.500 version 3 then we would like to examine the database to see if we can determine what caused the corruption, but V2 is so old we probably wouldn't find a bug that hasn't been fixed in V3. Andrew | |||||