Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Could not open local database, it is inconsistent.

674 views
Skip to first unread message

Anders Gustafsson

unread,
Mar 5, 2009, 8:59:44 AM3/5/09
to
Ahleia,
> The Tree has multiple Netware servers , all of our servers are Netware
> 6.5 SP7. When I run the "Unattended Full Repair" in DSREPAIR on the
> server ,it shows "Automated Repair Mode cannot continue since the local
> database is not open"
>
> Would appreciate detailed steps to resolve the above issues.

Restart the server with SERVER -ndb, then try rerunning dsrepair

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

David Gersic

unread,
Mar 5, 2009, 11:15:06 AM3/5/09
to
On Thu, 05 Mar 2009 13:36:01 +0000, ahleia wrote:

> We are getting the following error on a Novell 6.5 sp7 Server.
> Directory Services: Could not open local database, it is inconsistent.

Which error number are you getting along with this message?


> The Tree has multiple Netware servers , all of our servers are Netware
> 6.5 SP7. When I run the "Unattended Full Repair" in DSREPAIR

Do not run "unattended full". That won't help you anyway.

If the error number is a -618, I have yet to successfully recover from
that with DSRepair, so you should probably start recovering from a failed
database. If you have not done this before, and haven't planned for it,
start with this article:

http://www.novell.com/coolsolutions/feature/15748.html

which will work you through the process.

If the error is something other than a -618, DSRepair might help you.
Start the server with "server -ndb" and try "dsrepair -a", then advanced
options, repair local database.


--
---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Novell Support Forums Volunteer SysOp http://forums.novell.com

Please post questions in the newsgroups. No support provided via email.

Edward van der Maas

unread,
Mar 8, 2009, 1:43:41 AM3/8/09
to
ahleia wrote:

>
> Hi,
>
> We have restarted the server with SERVER –ndb. When we run the
> "Unattended Full Repair" in DSREPAIR on the server, it shows the
> following error message.
> “Error: Insufficient disk space or missing files, Error: -618
> Notice: Unable to update repair status, Error: -663
> Repair process aborted
> Automated repair mode can’t continue since the local database is not
> open.”


>
> Would appreciate detailed steps to resolve the above issues.

Run a local database repair with the default options while the server
is started with the -ndb option.

--
Cheers,
Edward

Edward van der Maas

unread,
Mar 8, 2009, 5:44:13 AM3/8/09
to
ahleia wrote:

>
> We have Five Novell 6.5 SP7 servers on a Single TREE.
>
> The following are Replica information of Netware servers.
>
> UNIT4_NW1....READ/WRITE REPLICA
> UNIT4_NW2....READ/WRITE REPLICA
> ASC_NW3.......MASTER REPLICA (NDS Error -663)
> ASC_NW4.......READWRITE REPLICA
> ASC_NW5.......SUBORDINATE REFERENCE REPLICA
>
> If we run local database repair on Server (ASC_NW3 with master
> replica) with the default options while the server is started with
> the -ndb option will it cause any problems on existing TREE?

If the replica on ASC_NW3 dies you can always promote a replica on
Unit4_NW1, UNIT4_NW2 or ASC_NW4 to master replica.

Just before you run it make sure that at least timesync etc is happy in
your tree.

--
Cheers,
Edward

Massimo Rosen

unread,
Mar 11, 2009, 8:24:47 AM3/11/09
to
Hi,

ahleia wrote:
>
> We have restarted the server (Novell 6.5 sp7 with master replica) with
> the –ndb option. When we press the F10 key with default options, local
> database repair was not prompting anything.
>
> Please advise us.

You already got the proper advise from David. Your error is a -618, and
as David said, it is *extremely* unlikely (if not impossible, as him
I've never seen nor heard of a succesful recovery from that error) to be
repairable. Consider DS on that server lost, and follow Davids link on
how to recover from that. Dsrepair will *not* help you here.

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

Massimo Rosen

unread,
Apr 19, 2009, 6:57:12 AM4/19/09
to
Hi,

ahleia wrote:
>
> As per the technical support we have removed the crashed server (Novell
> 6.5 sp7) from the NDS TREE. Crashed Server was installed under
> Organizational Unit ‘SERVERS’. When we try to reinstall the server into
> the TREE using Load NWCONFIG |Directory Options | Install Directory
> Services onto this server, wrong Organizational Unit (Accounts) in
> Level 1 field is selected by default. When we specify the correct
> Organizational Unit name (SERVERS) in Level1 field, OU ‘Extend’ in Level
> 2 field is selected by itself.

That doesn't matter. Just delete the second level entry from the
dialogue.

> Please find attached Screenshot of NDS
> Structure. Please explain us how we can install the server under OU
> “SERVERS”.

Is that a current screenshot? If yes, you must first delete the old
server object from NDS (via ConsoleOne), before you can reinstall eDir
on the server.

Massimo Rosen

unread,
Apr 19, 2009, 8:12:33 AM4/19/09
to
Hi,

ahleia wrote:
>
> This is not current screen shoot. We have already deleted crashed server
> objects from NDS Tree. How we can delete the second level entry from
> the
> dialogue? there is no option to delete.

You move the cursor to that field and hit the delete key until no more
characters are shown in that field. ;-)

Anders Gustafsson

unread,
Apr 19, 2009, 12:16:14 PM4/19/09
to
Ahleia,
> ERROR: Purging the invalid Trustees from the volume
>
That simply means that it removed invalid trustees from that volume.

Edward van der Maas

unread,
Apr 20, 2009, 7:14:36 PM4/20/09
to
ahleia wrote:


> How we can add R/W replica on ASC_NW3?

Use consoleone (partition and replica view) or via iManager.

--
Cheers,
Edward

0 new messages