Processing Stuck Obituaries
Novell Cool Solutions: Feature
Digg This -
Posted: 4 Jun 2002
Here's some great info from the tech support team that will help you process stuck obituaries in NetWare 5.x, NetWare 6, eDirectory 7.x and eDirectory 8.7x.
For updates and the full details, see TID-10062149.
The first question that needs to be addressed when attempting to process stuck obituaries is: "what is the version of DS and DSREPAIR?" If the NLM modules on the server are older than November 2001, then chances are that NDS/eDirectory should be updated as part of the process.
Another key factor in getting obituaries to process is communication. Obituaries cannot process when a server is down or not in sync. For NetWare 5.x servers and above, the wsock4f needs to be in place and SLP needs to be set up and running correctly.
If the above items are in place and the obituaries are still not making progress, then unload the DS.NLM and reload it. *Note, bouncing the server is not necessary and will not have the same effect as simply unloading the DS.NLM module and then re-loading it. A repair with the -OT switch after re-loading the DS.NML should time stamp the obituaries and get things moving. A typical set of trace commands (such as the ones listed below) can then be issued and verification of the sync process will be displayed on the trace screen.
Run this process on the master server to begin with. (The master of the partition that is having obituary problems.) If this process works to clear the obituaries for the master server and not the others, a Read/Write or Read-Only can be designated as the master and then the same process can be run on it.
- LOAD DSREPAIR -RC (a dump file will be created).
**** CAUTION ****
It is recommended that when running repairs, that caution be used in selecting REBUILD OPERATIONAL SCHEMA. If auxiliary classes have been added or if the on a NDS/eDirectory version is greater than 85.xx, avoid using this option as part of the standard repair process. It is the customer's responsibility to ensure an understanding of the ramifications of using the options that are in Repair. For any questions or concerns, please call Novell Technical Support for additional clarification.
- LOAD DSREPAIR -XK3, go to advanced options, then to repair local DS database. Say YES to rebuild operational schema (after reading the above CAUTION) and YES to check local references. The rest of the options can be set to NO. After the repair is done, select YES to save the repaired local database and run the same options multiple times to lower the number of errors. Save and exit out of DSREPAIR.
- At the console:
Toggle over to the Directory Services Screen and wait for it to say "Finished Checking Backlinks Succeeded."
- Then go back to the console and:
Toggle to the Directory Services Screen and wait for about five minutes.
- LOAD DSREPAIR -A and go to ADVANCED OPTIONS | CHECK EXTERNAL REFERENCES and see if the obituaries have cleared or have started clearing (Flags are advancing from 0000 to 0001 to 0002, etc.). If they have cleared, go to a Read/Write, designate it to be a master and then do the above again. If they have started clearing then give it some time. If they seem to be the same, use the DSREPAIR VERSION 5.27 or later. Version 5.29 is available in patch DS758.EXE, available for download from http://support.novell.com. IF you are running DS 8.x extract DSREPAIR 85.14 from DS patch DS880b.EXE or higher. Any future releases of DSREPAIR will have this functionality built in as well.
- LOAD DSREPAIR -OT (that is the letter O and NOT the number 0). This should be done on the master of the partition containing the obituaries. Load DSREPAIR | Advanced Options | Repair local database and select YES to check local references. After the repair is done, select YES to save the repaired local database and run the same options multiple times to lower the number of errors. Save and exit out of DSREPAIR.
- SET DSTRACE=*. (bounces DS.) This will not effect users connected to the server.
- Run the following again:
Toggle over to the Directory Services Screen and wait for about five minutes.
- LOAD DSREPAIR -A and go to ADVANCED OPTIONS | CHECK EXTERNAL REFERENCES and see if the obituaries have cleared or have started clearing. If they have not cleared, go to a Read/Write, designate it to be a master and then do the above again. If they have started clearing then give it some time to work. NOTE: This should also help process the TYPE C obituaries that seems to take an additional amount of time to process.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com