Error: "-699" when Importing Remote Schema to NetWare 6
(Last modified: 11Sep2003)
This document (10066345) is provided subject to the disclaimer at the end of this document.
fact
Novell eDirectory 8.6 for NetWare 6
Novell NetWare 6
symptom
Error: "-699" when Importing Remote Schema to NetWare 6
Photo and Pager schema SYNTAX are different in current production tree and the NetWare 6 tree.
rbsPageMembership schema SYNTAX is different in current production tree and the NetWare 6 tree.
Import remote schema from the production tree into the NW6 test tree, the customer received a Error: -699 An unrecoverable error has occurred and the operation cannot be completed
Error: -699 An unrecoverable error has occurred and the operation cannot be completed.
change
In preparation for a NetWare 6 Server to be introduced into in an existing network with NetWare 5.0/5.1 and/or NetWare 4.11/4.2 the NetWare 6 server was created in a temp tree so that the schema could be imported into the production environment
cause
The problem is caused by a difference in the schema SYNTAX between the current production tree and the NetWare 6 tree. It may fail on a schema attribute called "photo", "pager", and "rbsPageMembership" although other attributes may be affected as well.
Although the production tree had NetWare 6 servers in the tree, the syntax on the Photo attribute definition set was set to syn_stream, which is the old syntax.
note
To determine if there will be a difference in schema SYNTAX before installing the NetWare 6 server into a TEMPTREE, follow the steps below for the following attributes in your Production tree.
"Possible Existing SYNTAX"
photo = Stream
pager = Case Ignore String
rbsPageMembership = Case Ignore String
"NetWare 6 Shipping SYNTAX"
photo = Octet String
pager = Telephone Number
rbsPageMembership = Case Exact String
Steps for DSBROWSE:
LOAD DSBROWSE | Choose Schema Browse | [Schema Root] | [Attribute Definitions] | and search for the attributes above. Press enter on the attribute | View Attributes | Press enter on [ID Schema Value] | View Value Details | Look for Attribute Syntax:
Steps for DSVIEW:
LOAD DSVIEW | Choose 4. <Attribute Definitions> | Then use 1. <Next> to search for the attributes above. (You must go through all attributes one by one.) Once each is found, Look for Syntax: If your production tree schema SYNTAX matches the "Existing SYNTAX" above, continue with the following steps.
Steps for iMonitor:
To display the schema entry of a specific attribute, add the following after attribute?: attr=schema attribute
Sample URL:
https: //192.168.86.250:8009/nds/schema/attribute?attr=photo
fix
There are number of ways to deal with the schema SYNTAX differences.
1. Leave the SYNTAX as it is and don't import the schema. The NetWare 6 install is smart enough to see the schema SYNTAX difference and to continue on with the Existing SYNTAX.
2. If it is necessary to import schema from a NetWare 6 temp tree to your production tree, prior to installing NetWare 6 into your environment then do the following:
NOTE: If you continue with these options and there is data poplulated on objects that use these attributes, you will lose that data in the attributes.
For Example: If you are needing to change the syntax for the Photo attribute and you have data poplutated in the photo attribute - the following steps will purge photo attributes from all objects in eDirectory/NDS
If you are unsure or confused, please call Novell Techical Support to discuss your options.
NOTE: To verify NDS/eDirectory has been backed up on all servers prior to beginning the process below by loading DSREPAIR -RC on all servers in the tree.
NOTE: Use DSBROWSE/iMonitor to verify the case of the attribute. In some cases Photo attribute had a Capital "P" instead of lowercase. The below DSREPAIR switches are case sensitive. Copy the case found in DSBROWSE/iMonitor.
To resolve photo syntax use the following switch:
DSREPAIR -sm "photo" -ac9 -rd
To resolve pager syntax use the following switch:
DSREPAIR -sm "pager" -ac10 -rd
To resolve rbsPageMembership use the following switch:
DSREPAIR -sm "rbsPageMembership" -ac2 -rd
Case 1
If all servers are NDS 8.xx (or greater) which includes eDirectory 8.5 (85.xx) eDirectory 8.6 (103XX.XX) and eDirectory 8.7 (104XX.XX) then:
LOAD DSREPAIR using the syntax shown above on EVERY server in the tree
NOTE: This MUST be run on every server in the tree that are NDS 8.xx (or greater) - No Exceptions
Case 2
If there is a mixture of NDS7.xx, NDS6.xx, and NDS8.xx (or greater)
Move all Replicas to NDS8.xx (or greater) servers and remove all replicas off of the NDS7.xx and NDS 6.xx servers then:
LOAD DSREPAIR using the syntax shown above on EVERY server in the tree
Once the above DSREPAIRs have been run - replicas may be added back to the NDS7.xx and NDS6.xx servers.
Case 3
There are no NDS 8 (or greater) servers in the tree and the schema must be imported before the introduction of NetWare 6 (Only NDS 7.xx or 6.xx)
Please call Novell Technical Support.
Case 4
There are no NDS 8 (or greater) servers in the tree and it is possible to install a NetWare 6 server into the tree. (Only NDS 7.xx or 6.xx)
Once NetWare 6 has been introduced, follow Case 2 above.
For additional information on eDirectory 8.6, please see the following solution. TID #10066455 - eDirectory 8.6 Readme Addendum
document
| Document Title: | Error: "-699" when Importing Remote Schema to NetWare 6 |
| Document ID: | 10066345 |
| Solution ID: | NOVL64596 |
| Creation Date: | 26Nov2001 |
| Modified Date: | 11Sep2003 |
| Novell Product Class: | NetWare Novell eDirectory |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.