[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
963.0. "DIT Corruption in V3.0 ECO3" by VMSNET::R_HARRIS () Mon Jan 27 1997 17:43
Hello,
I have had three occurrences where customers are getting corrupted DITs.
These corruptions have no particular pattern, two occurrence was
related to the upgrade to v3.0 ECO3. After the upgrade, when starting
the DSA, the Corrupt DIT event occurs. The 3rd was unrelated, I am
still not clear what events led up to the DIT corruption. However,
a slave DSA failed with a DIT corruption. The question was "What if it
was a Master DSA", how will I recover?
The documentation indicates that you should Delete the DB files and
recreate the DSA, then repopulate. This is great if you have the
populate script. You are SOL if you don't.
It appears that DIT corruption is more frequent in v3.0. Are there any
safeguards to help stop DIT corruption?
Thanks in advance for your support.
Randy
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 963.1 | | 16.11.160.113::FORTY2::PALKA | Andrew Palka Altavista Directory | Thu Jan 30 1997 12:20 | 8 |
| Usually it is possible to recover a database in the event of
typical corruption. However, this requires engineering support.
If you have a copy of the corrupt database files (everything in
/var/dxd or dxd$directory) then we can analyse it to determine the
cause of the problem.
Andrew
|