• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 933
  • Last Modified:

NDS object move

I have moved a client from one container to another and realized it is the wrong container. Now that I try and move him to the correct container I get an error.  “Error-637 After an object has been moved from one context in the tree to another, the Directory database will not allow that object to be moved again until all replicas of that object have been updated.” I understand the error but it’s been a little over a week and I still can’t move it. How do I check on replica status or object transfer status?  We are using Netware 6.5, Support Pack 07, eDirectory Version 8.7.3.9 SMP and NDS version 10553.73
0
Ryan Sanchez
Asked:
Ryan Sanchez
  • 5
  • 4
2 Solutions
 
deroodeCommented:
Normally any changes in eDirectory are replicated to all replica's in your tree. You can check with Dsrepair if synchronisation is working properly. (Report Synchronisation status)

If synchronisation isn't working properly check to see if all servers can be contacted and all replica's are up. You can try to force replication through Advanced options - Replica and partition operations - Select the replica you want to sync - Synchronize the replica.

If that doesn't work the problem you are facing is called "stuck obituaries". This problem is extensively documented here:

http://support.novell.com/docs/Tids/Solutions/10062149.html
0
 
Ryan SanchezSystem SpecialistAuthor Commented:
I have done a few Time Synchronization and all servers that have replicas on them report back without any issues. The only severs that report errors are servers that do not have any replicas and that are turned off. These are off because they no longer full fill a need and I need to save power consumption and A/C work load. I will try your suggestion.

Thanks for your time,
  Ryan Sanchez
0
 
ZENandEmailguyCommented:
Ryan,
In your followup to deroode you mentioned "servers that do not have any replicas and that are turned off"...

Have they been removed from the eDirectory tree?  If not, eventhough they don't have replicas, they are likely halting some sort of sync process needed behind the scenes and in the background to get synchronization going.

I've spent a lot of years troubleshooting eDirectory problems and used to teach the Novell courses on eDirectory troubleshooting where we learned to fix problems like you are reporting.  I think deroode is right on with his point on inhibit_move obituaries.

To see if you have any, do the following:
1) load dsrepair -a
2) choose Advanced Options
3) Check External References
4) wait for the report to finish and look for external references that might show "inhibit_move".  If you have those let us know.

Scott
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
Ryan SanchezSystem SpecialistAuthor Commented:
Okay guys thanks a lot. I have a lot to go over. I am new to Netware, a year now, and We are now going to Linux so I have a lot of catching up to do. Now with that being said, I have a question, Do I run DSREPAIR on the master server only or on all servers that are in the replica ring? I've researched and read articles but non that I can see states to run on master or all servers.

Thanks,
 Ryan Sanchez
0
 
Ryan SanchezSystem SpecialistAuthor Commented:
Okay I ran the dsrepair -a command and checked for external references. There are quite a number of "inhibit_move" errors.
  @Scott I have not removed those servers from the tree. I thought as long as we removed what ever replicas they had on them and if they weren't doing a major function such as e-mail it would be okay to turn them off. Should i turn them back on and see if the replica will complete?

Thanks,
 Ryan Sanchez
0
 
ZENandEmailguyCommented:
Ryan,
You'll run the dsrepair first on the Master replica server and then on the other servers in the ring.

As you move to OES2-Linux the commands take on a new look but get you to the same result.  Instead of choosing menu commands you'll feed switches to the ndsrepair command.

Scott
0
 
Ryan SanchezSystem SpecialistAuthor Commented:
I have another question on this topic:
  Before preforming the "Processing stuck obituaries in All DS versions" do i need to remove all servers that are not "full filling" a job? If i do have to remove all the servers first do i turn then all on and remove one by one or can i just turn one on and then remove it?
0
 
ZENandEmailguyCommented:
No, you won't need to remove any servers.  Look at the dsrepair | advanced options | replica and partition operations | view replica ring and choose the partition where the moved object came from or is going to (may be one and the same).  Press enter on that partition and choose View replica ring to show all of the servers with real and subordinate reference replicas for that partition.

You'll see the Master and some Read Write and possible some SubRefs.

I assume that all servers listed in the replica ring are up and running correct?  If not they all must be turned on and accessible by DS in order to clear anything.

Scott
0
 
ZENandEmailguyCommented:
Ryan,

Were you able to fix the "inhibit_move" obituaries that you saw?

Scott
0
 
Ryan SanchezSystem SpecialistAuthor Commented:
I am sorry, Yes we were! I was able to remove unneeded servers from our tree and once we did that replication completed. I had to power on servers and remove them from out Tree using TID 10019060. It was a big sigh of relief once I was able to move Elem students to Middle school and a Teacher from one school to another.

Thank you all very much for all your responses!!!

Ryan
0

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now