Schema Extension Errors
Articles and Tips: qna
01 Nov 2002
Q.
I am considering declaring a new epoch to solve some problems here. We are having -659 errors when trying to extend the schema and all indications are pointing to time stamps. Will this impact anything if I extend the schema in the middle of the day? We are running eDirectory v8.79.
Over Extended Schema in Euphrates
A.
Dear Over Extended: Yes, creating a new epoch has the potential to significantly increase Network traffic, DS traffic, and hog CPU/memory. You might be able to do it and be OK, but this really depends on your environment. However, since you are using eDirectory v8.79, beware!
I have advised some other customers to go with Support Pack 4 (SP4) and then to eDirectory v8.80 before even contemplating doing this again. This was after we tried to declare a new epoch on a NetWare v5.1 SP2a/eDirectory v8.78 server. They had to have three NTS dial-ins to fix the partition problems which were a consequence of declaring a new epoch on pre-eDirectory v8.80 servers. If you read the small print in the readme for eDirectory v8.80, you will see the following:
"Changes made in DS.NLM v8.80b:
(Supersedes 8.80a)
- Resolves problems in declaring a partition epoch"
So, be warned. You may be lucky, of course, but it took about 4 months for this other customer to get a whole facility back from the year 2010!
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.