When restarted, it can't load DS, giving this error, "Could not open
local database. It is inconsistent, try to correct the error with
DSRepair"
With DSRepair -a loaded, repair local database fails to start and the
log states, "Insufficient space or missing files, error -618.
Unable to update repair status error -663"
Upon exiting DSRepair, I get a big red box advising, "Unable to set DS
database state for the current operation. Try running 'Repair local
dadabase as follows:
1) Perform DB structure and index check 'NO"
2) Rebuild entire database 'YES'
Removing Directory Services from this server should be your last
resort"
Even with those options, DSRepair still won't run, giving the same
errors. I have verified there is plenty of disk space available.
I tried starting the server with server -NDB, same errors.
I tried to run DSRepair -xk2, same errors.
What are my options at this point?
You're not running out of disk space on the SYS volume are you?
--
___________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Network Consultant/NSC Sysop
InfraSystems Solutions AB
>On Mon, 15 May 2006 17:12:07 +0000, Russ Ringer wrote:
>
>You're not running out of disk space on the SYS volume are you?
Monitor reports the SYS volume is 18% full.
> One of our servers running NW 6.5 sp5, edir 8.7.3.8 inexplicably
> crashed, no abend or errors, just total lockup.
>
> When restarted, it can't load DS, giving this error, "Could not open
> local database. It is inconsistent, try to correct the error with
> DSRepair"
>
> With DSRepair -a loaded, repair local database fails to start and the
> log states, "Insufficient space or missing files, error -618.
> Unable to update repair status error -663"
663 means that your DIB is in a lock status. Check the _netware
directory on your server for some strange looking files. I'm afraid
though that you either call NTS or do a nwconfig -dsremove action and
reinsert the server.
--
Cheers,
Edward
I loaded jcmd and browsed the _netware directory and compared it to a
working server.
The bad server has NDO.RFL and NDS.RFL that a good server does not
have.
I am inclined to delete them on the bad server.
What have I got to loose by deleting them?
>
>I loaded jcmd and browsed the _netware directory and compared it to a
>working server.
>
>The bad server has NDO.RFL and NDS.RFL that a good server does not
>have.
>
>I am inclined to delete them on the bad server.
>What have I got to loose by deleting them?
nm, the good server has those *.RFL files, too
The server didn't have the CPR release for SP5 installed. Could that
have caused it to crash and lockup?
Opinions expressed above are not
necessarily those of Novell Inc.
> nm, the good server has those *.RFL files, too
Those are your roll forward files and you don't really want to mess with
them unless you have to ...
--
Peter
eDirectory Rules!
> I did a nwconfig -dsremove and removed directory services and it said
> "directory services have already been removed", cleaned up the tree,
> reinstalled DS, added a replica and now it's all working OK!
Welldone
> The server didn't have the CPR release for SP5 installed. Could that
> have caused it to crash and lockup?
Not really. I agree with Andrew, could be a hardware issue.
--
Cheers,
Edward
I wondered because this server had been up for 6 months and I just
installed NW6.5 SP5 and GW SP6. It is getting kind of old. Maybe I'll
hit up the boss for a new server ;)
>With DSRepair -a loaded, repair local database fails to start and the
>log states, "Insufficient space or missing files, error -618.
>Unable to update repair status error -663"
I've seen this here a few times now. At this point, you're dead. The only thing
you can do is -dsremove and reinstall. I've used Jim Henderson's procedure to do
that, and it works fine. If you have backups (dsrepair -rc, or embox), you can
use those to recover.
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
>Unlikely, unless you were having memory errors beforehand. Seems more
>like a hardware issue to me.
I've seen the same symptoms here a few times. I'm sure it's not hardware, at
least not in my case.
>I've seen this here a few times now. At this point, you're dead. The only thing
>you can do is -dsremove and reinstall. I've used Jim Henderson's procedure to do
>that, and it works fine. If you have backups (dsrepair -rc, or embox), you can
>use those to recover.
>
Is there a way for us mere mortals to use a dsrepair -rc backup to
restore? I thought only a Novell tech via dial-in could use it.
- Anders Gustafsson, Engineer, CNE6, ASE
NSC Volunteer Sysop
Pedago, The Aaland Islands (N60 E20)
Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement
Using VA 5.51 build 315 on Windows 2000 build 2195
OK, that's good enough.
Anyway I can see from the rest of the thread you needed
to remove DS off of this server and add it back.
Glad it's working again.
>Is there a way for us mere mortals to use a dsrepair -rc backup to
>restore?
Officially, no. Asking around in at Meet the Experts night at Brainshare, or
sufficiently crafty Google searching will turn up other answers.