Environment
Novell NetWare 6.0
Novell NetWare 5.1
Novell NetWare 5.0
Novell Directory Services
Novell NetWare 5.1
Novell NetWare 5.0
Novell Directory Services
Situation
Server abended or had to be forced down
NDS Database Locked
Database Locked
NDS will not unlock
eDirectory will not unlock
Error: "-618" - Inconsistent Database
Error: "-663"
-797 FFFFFCE3 ERR DIRECT WRITING FILE
Error: "-797"
NDS Database Locked
Database Locked
NDS will not unlock
eDirectory will not unlock
Error: "-618" - Inconsistent Database
Error: "-663"
-797 FFFFFCE3 ERR DIRECT WRITING FILE
Error: "-797"
Resolution
There are 2 resolutions to this problem. If the server can be rebuilt easily and does not have user home directories, print queues, etc- then follow option #1 and #2. If there is a current backup of the DIB, you may call Novell Technical Support (option #3)
NOTE: If the server was the Master of any Partitions, you might want to use DSREPAIR to designate a Read/Write to be the Master.
To do this: Load DSREPAIR | Advanced Options | Replica and Partition Operations | Select the desired partition (verify it holds a Read/Write and is in the ON state) | Designate this server as the new master replica.
1. First try to load the server with a -NDB or load DS.NLM -NDB and try running a local database repair to see if that unlocks the database
2. If possible, try running a DSREPAIR -XK2, which will remove all replicas off the server. Please see Tid 7001592
To do this: Load DSREPAIR | Advanced Options | Replica and Partition Operations | Select the desired partition (verify it holds a Read/Write and is in the ON state) | Designate this server as the new master replica.
3. Remove Directory Services (NWCONFIG -dsremove). NOTE: you will loose file system trustee assignments with this option, bindery print queues, etc. You also need to remove volume objects and server objects from NDS.
NOTE: If you have a recent DIB set (Created via DSREPAIR -RC ) you may call Novell Technical Support to possibly restore it. This can save trustee rights, print queues and pointers to user Home directories.
Additional Information
Corruption in the NDS/eDirectory files
If a -797 error occurs when the DS.NLM loads and it occurs prior to the -663 error, then more than likely one of the database files is corrupt as the server is not able to do an I/O Write. The -797 errors do not present themselves in all circumstances. At times you will only see -663 and/or the -618 errors.
Novell recommends that all customers upgrade to eDirectory 8.7 as it provides the functionality, to the Customer, to fully backup and restore their eDirectory database.
Formerly known as TID# 10068165
If a -797 error occurs when the DS.NLM loads and it occurs prior to the -663 error, then more than likely one of the database files is corrupt as the server is not able to do an I/O Write. The -797 errors do not present themselves in all circumstances. At times you will only see -663 and/or the -618 errors.
Novell recommends that all customers upgrade to eDirectory 8.7 as it provides the functionality, to the Customer, to fully backup and restore their eDirectory database.
Formerly known as TID# 10068165