Cannot open local database

Lost communication with Netware 6.0 server. The server was patched with sp3. Do not know if it is hardware or software. No changes were recently made to this box. The local database remains locked or closed. I've tried dsrepair, however it will not correct the local database inconsistancy. Server has 2GB ram, No scsi, 2.8G Processor.
I'm going to start the server in stages to check for additional messages or loading problems, If you need more specifics I'll be happy to provide them for you.
Thanks,
Tom
tiacovoneAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PsiCopCommented:
Is this server part of a larger NDS tree? Does it hold any replicas?
0
PsiCopCommented:
What is the EXACT error message when the server is starting up and can't open the NDS database?
0
PsiCopCommented:
Finally, what is the EXACT version of DS.NLM on the server?
0
Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

tiacovoneAuthor Commented:
Ok,
1. Yes, The server is one of 4 and it has a read/write replica not master.
2. Directory services: Could not open local database, it is inconsistent. Try to correct the error with dsrepair.nlm
3. DS version 10350.19

Hope this helps some?

Tom
0
PsiCopCommented:
1) That is important. NDS updates are accumulating for this server on the other servers that host replicas. With a small network, it won't get to be an issue for a long time (weeks), but its still important to know this.

2) Such error messages are usually accompanied by a number, like so --> DS-5.6.02-1234: Could not open local database
What is the EXACT, verbatim error message?

3) OK, so this is eDirectory v8.6, not NDS.
0
PsiCopCommented:
Also, HOW did this error come about. Did it happen immediately after application of SP3? Or was the box running fine and then suddenly eDirectory closed and you got this error message? Or was there a power failure and this server rebooted?
0
tiacovoneAuthor Commented:
On manual load, at loadstage 4 the error was stated exactly as I wrote plus DS-10350.19-261

sp3 has been running fine for a while, this seemed to suddenly happen. However, when this did occur I had to shutdown by using the power switch.
0
PsiCopCommented:
OK, so SP3 was applied some time ago, and this error just popped up suddenly, the server crashed hard, and on reboot DS will not open during LoadStage 4. Is that a correct summation?
0
tiacovoneAuthor Commented:
Yes
0
PsiCopCommented:
Searching Novell's extensive support database, I found TID #10058536 (http://support.novell.com/cgi-bin/search/searchtid.cgi?/10058536.htm). In particular, the 3rd solution suggested sounds like it might help. Quoting:

       Bring up the server with SERVER -NDB (for no database).  Load DSREPAIR | Advanced Options menu | Repair local DS database,
       with Check Local References and Rebuild Operational Schema set to Yes.  Save the repaired database, then Esc to unlock DS.
0
tiacovoneAuthor Commented:
It will not run dsrepair. Upon pressing F10 it just blinks back and forth to the running screen and back to the configuration screen. When I escape I get this error report.

Unable to set directory services database's state for the current operation. Try running 'Repair local DS database' as follows:
1) Perform database structure and index check? Choose NO
2) Rebuild entire database? Choose YES
You may keep all other options and their defaults.
Removing directory services from you r server should be your last resource.

Nothing to do but exit dsrepair.

0
PsiCopCommented:
So you tried bringing it up with the -NDB switch and it still won't load DSREPAIR?
0
tiacovoneAuthor Commented:
Correct.
0
tiacovoneAuthor Commented:
Dsrepair loads but will not run the process.
0
PsiCopCommented:
The SYS: Volume is mounted, right?
0
tiacovoneAuthor Commented:
I have 3 Volumes on that server, they all mount.
0
PsiCopCommented:
Honestly, I think your NDS database is majorly hosed. Its hard to say why. Perhaps Transation Tracking System (TTS) ran out of resources and shut down - that can choke the NDS database. How full is the SYS: Volume?

At this point, I'm not comfortable in giving more-detailed advice, because I can't examine the system first-hand. I think its time for you to place a call to Novell Support - you need formal support on this one. If you want to PAQ this Question and get a refund, I have no problem with that.

Anyway, that's my best advice given the information I have.
0
ShineOnCommented:
Is your tree partitioned?  Is DS healthy on the Master?
0
tiacovoneAuthor Commented:
DS appears OK on master, no partitioning with tree.
0
PsiCopCommented:
That's good. You may have to remove DS from that server and then put it back on. This is a non-trivial procedure. But since your NDS database is replicated fully, you won't lose any information. If you've never done that, I recommend you engage Novell TS to walk you thru it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ShineOnCommented:
And nothing you've tried will unlock the local database?
0
tiacovoneAuthor Commented:
just want to state that I removed the hard drive from that server and put it in another. I was able to read the volume with the data that was needed. Copied all to another volume on another server, it went ok. I then blew away the corrupted box removing all instances from my tree. Everything now seems ok. I've accepted that particular response as an acceptable answer since it seems pretty close to what I have done, plus I appreciate the time spent trying to resolve this issue.
0
ShineOnCommented:
Glad you got it taken care of.  Thanks for posting your solution.
0
tiacovoneAuthor Commented:
Sorry I took so long.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.