This guide is designed to help you learn the ins and outs of processing stuck obituaries on OES2 Linux and SLES. It provides all of the required commands to help you stop guessing and panicking in times when you really need it. It also provides some guidelines for learning about the obituary process first so that you don't do something you should not be doing. In the end, it makes obituary processing easy and straightforward on Linux...
To proactively keep your eDirectory tree healthy, run automated, scheduled reports using iMonitor on a regular basis, and check the results regularly.
Check time synchronization, replica synchronization status and external references for stuck obituaries on a regular basis. Check to make sure all servers are up and running. Follow Novell TID NDS / eDirectory Health Check Procedures - Cross Platform TID (10060600)
If you run into stuck obituaries that will not clear themselves, the following are some tips that can help to clear them.
Be sure to check the health of eDirectory to make sure time is in sync and synchronization of all replicas on servers are processing without errors. Check to make sure all servers are up and running.
- Check eDirectory time synchronization: ndsrepair -T
- Check Replica Synchronization Status: ndsrepair -E
- Check external references for stuck obituaries: ndsrepair -C -Ad -A
Follow Novell TIDs such as How to progress stuck obituaries TID (7002659) for additional details on the obituary process so that you understand the ins and outs of obituary processing.
Go through TID Processing stuck obituaries in All DS versions (7001603) for some of the dsrepair and ndstrace commands on Linux. More useful commands are below.
By going through the above documents first, you will gain a better understanding of how to proactively keep your eDirectory tree healthy and free of stuck obituaries, you will gain a better understanding of the obituary process and the commands involved to better prepare yourself to clean them up completely should you run into stuck obituaries.
After going through the above information, use the following tips to make sure you are not wasting time and effort, and not creating more problems by running processes you should not be running in certain cases.
Always remember to get a backup copy of your dibset before going forward with any operations that could negatively affect eDirectory. With Linux or Unix, one alternative for getting a backup is ndsrc.pl script - http://www.novell.com/communities/node/1129/ndsrc . Another alternative is to setup dsbk to automate your backups, or to get a backup when you need to using the following documentation. http://www.novell.com/documentation/edir88/edir88/?page=/documentation/edir88/edir88/data/bsl7jmp.html
Only timestamp an obituary if other new obituaries in the same partition are processing fine but obituaries with older dates and times are still unprocessed. You will notice that the timestamps on these obituaries are older so they are not being seen by the purger (behind the purge vector) ndsrepair -R -Ad -A -OT
This will timestamp all the obits.
Then run: ndstrace
At the ndstrace prompt type: set ndstrace = *j
Then type: set ndstrace = *f
Keep in mind that this can take a long time on a large DIB and would probably be better if done on single objects or partitions unless there are too many stuck obituaries throughout the tree.
Repair obits that are showing insync with some kind of error EX: -699 or -618. You can use a single object repair with ndsrepair -Ad -J (You will need to provide the Entry ID (in hexadecimal format) of the object you want to repair). Alternatively this can be done using iMonitor to simplify the process.
XK3 and then re-backlink servers that show in the backlink list (from the external reference report) with flags of 0000 and don't hold replicas of the partition.
ndsrepair -R -Ad -Xk3
set ndstrace = +BLNK
Check to make sure any server with flags 0000 is up and communicating. You will see these flags in the External Reference report generated..
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.