novell errors found running dsrepair

[scloan]

I have been receiving error messages for the last 3 days when running DSREPAIR. The errors seem to pertain to every user logged on to the network. The error message states: "Value is more than 60 days old, being deleted". Then it lists the object, context, and user id logged on. The Dsrepair fixes the error, but it reappears the next day. Does anyone have any clue as to what this error message really means? Thanks for any help you can give.

 

[6pack]

What version of ds.nlm are you running on the system. And what version of the OS (4.10, 4.11, 5.0). Let's get the latest service pack installed first and then see what happens?? Be aware that a service pack can mess up your backup (just more good news).

 

[Warcorp]

Ok, Aside from not knowing what version of DS you are running, here is a brief note reagrding this "error". Netware stores all it's user information in NDS including temporary values, such as a users logged in network address. Over time, DS needs to clean those out since those particular values may not be updating for a particular user. As an example, the user is still in NDS but the user has not logged in within 60 days. This note is telling you that the particular value it's removing, is first, temporary, second, unneccessary and removes it to keep NDS tidy.<br>
<br>
Now for the reason why it's trying to delete the same value each day...good question. 6pack is right, seeing what version of NDS is important at this point.

 

[scloan]

Thanks for your responses. The NDS version is 6.00(DS.NLM) and the<br>
DSREPAIR version is 4.59. This morning I ran dsrepair after getting<br>
a tip from another novell administrator who discussed my problem<br>
with the people at Brainshare. They had me run "Load Dsrepair -n5".<br>
But this didn't seem to make a difference. Any other suggestions?<br>
Thanks.

 

[Warcorp]

Hmmm, Are you running DSRepair at the master replica? and is NDS Partitioned between servers? What is the synchronization status? Do a:<br>
dstrace=on<br>
dstrace=*h<br>
<br>
and switch over to the dstrace screen and look to see if it is replcating any errors.

 

[Warcorp]

thats set dstrace=on<br>
and<br>
set dstrace=*h

 

[scloan]

I ran the dstrace and there were no replicating errors. I have only <br>
one server so we don't have to have the NDS partitioned between any other server. I still am getting the errors every day. I am<br>
running out of ideas. If you have any other suggestions I sure<br>
would appreciate it. Thanks

 

[6pack]

I'm out of ideas. Novell has a bunch of "secret" switches that goes with dsrepair. I hadn't heard of -n5. I assume that things are running well as far as your users are concerned and they don't see these problems? You only see them because you are trying to keep a healthy NDS? You're doing your job - that's good. Looks like it is time for a call to Novell. If you do and get it fixed, let us know.

 

[glenna]

Did you try the Novell Knowledge base at support.novell.com ?

 

[scloan]

I did try the Novell Knowledgebase at novell but<br>
couldn't find any solutions there either. We even<br>
had the problem discussed at BrainShare in Utah<br>
and still nothing. It isn't looking like good. <br>
Thanks for the suggestion though. Chuck W