Unable to import schema from remote tree error -634

  • 3079474
  • 26-Feb-2007
  • 26-Apr-2012

Environment

Novell eDirectory 8.7
Novell eDirectory 8.8
ndsrepair -S -Ad

Situation

  • Trying to import schema from remote tree with following command:
    • ndsrepair -S -Ad
    • Choose option 5
    • Type in tree name (not IP Address)
  • Trying to import schema from another tree with "ndsrepair -S -Ad" results in an error -634
  • Trying to import schema from another tree results in an error -626
  • Trying to import schema from another tree results in "Unable to extend schema on this server.  Error -469398712"

Resolution

  • Create a /etc/hosts.nds file - (See TID 10096901 for details on what this file is used for and proper syntax)
    • Ensure an entry is created for server hosting master of Root in other tree.
      • Example: SERVER1 192.168.1.235
    • Ensure an entry is created for the root partition of that tree
      • Example: FST-TREE. 192.168.1.235
  • If you are running eDirectory 8.8.x, copy the file to /etc/opt/novell/eDirectory/conf directory.
  • Restart ndsd.

Additional Information

Example:

sb-oeslinux:~ # ndsrepair -S -Ad
Repair utility for Novell eDirectory - 8.7.3 v10550.96
DS Version 10553.36 Tree name: SBTREE
Server name: .sb-oeslinux.linux.novell

Size of /var/nds/ndsrepair.log = 2119 bytes.

Administrator name: admin.novell
Password:
Logging In To Server
Please Wait...

GLOBAL SCHEMA OPERATIONS
1. Request schema from Master Server
2. Reset local schema
3. Post Netware 5 Schema Update
4. Optional Schema Enchancements
5. Import schema from Tree
6. Declare a new epoch


Enter 'q' to escape the operation.
Enter a schema option(1-6)?5
Request schema from Tree : FST-TREE

Preparing Log File "/var/nds/ndsrepair.log"
Please Wait...
Checking and extending schema from a remote tree

Start: Monday, October 16, 2006 03:32:38 PM Local Time

Making connection to source tree, "FST-TREE"
Unable to extend schema on this server. Error -634.
Total errors: 0
NDSRepair process completed.


Feedback service temporarily unavailable. For content questions or problems, please contact Support.