Could not open local database: error -6024
Roberto Sangalli
I had three servers in my TREE and I decide to remove the old hrdw just
removing the DS from the server and then restart it and shut it down for
good.
Everything was fine, I check with ConsoleOne if there still were objects
related to that server and I find few of them. I delete all those objet
related to the server such as _ADMIN_SRV3, SYS and VOL3 objects and
NLS_LSP_SRV3,NISSRSV_SRV3 and SRV3 Backup Job Queue objects.
Few hours later I run DSREPAIR on one of the remain servers to see if
there were any inconsistency or error. And here we go I got the problem
that ds repair did not start because cannot open the local database and
give me the error -6024.
Furthermore I discover that I cannot connect to the server with Remote
Manager and iManager (not recognize the ADMIN user or password) and
in ConsoleOne the SYS and VOL2 of this server are empty.
I start to feel really bad....
I need help.......Thanks
Andrew C Taubman
server to dos and bring it up with Server -NDB . Ignore all errors and
when up load dsrepair, and run a local repair with Rebuild Op
Schema=yes. Apply the changes it suggests, unload dsrepair and reboot.
If it's still bad after the reboot the server's database is too corrupt
to repair and you need to treat it like a dead server.
BTW It's unlikely that removing the other server caused this.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)
Opinions expressed above are not
necessarily those of Novell Inc.
Roberto Sangalli
> What NW, SP and eDir versions? In general what you'd do is down the
> server to dos and bring it up with Server -NDB . Ignore all errors and
> when up load dsrepair, and run a local repair with Rebuild Op
> Schema=yes. Apply the changes it suggests, unload dsrepair and reboot.
> If it's still bad after the reboot the server's database is too corrupt
> to repair and you need to treat it like a dead server.
>
> BTW It's unlikely that removing the other server caused this.
After I remove the DSfrom the old server that was not the master in the
ring and I run the dsrepair on my other server the message that I got
was the local DS was locked and the system was locking for some RFL files.
I know that I implemented the roll-forwarding log on all of my
servers..so I guess maybe the problem is in this area
Andrew C Taubman
you mention. What it would do is stop any partition operation from
completing (eg adding a new replica).
I'm really not sure what caused this issue for you, but my previous
advice remains the same.
Roberto Sangalli
> Having no master will not cause dsrepair to lock up or any of the issues
> you mention. What it would do is stop any partition operation from
> completing (eg adding a new replica).
>
> I'm really not sure what caused this issue for you, but my previous
> advice remains the same.
do you think that bringing down the server and up again without doing
the suggested procedure will do more arm to the system or not?
The server is still running with the problem since Friday and it still
provides the iPrint service and the SLP service, so it is little less
critical situation than three days ago, but it is still a serious
problem for me because this is the server that has the CA authority in
the TREE.
Before bring it down I am thinking to move the printers to the other
server and maybe the SLP services as well.
Pleas advice....Thanks
Andrew C Taubman
> do you think that bringing down the server and up again without doing
> the suggested procedure will do more arm to the system or not?
I think it will have no effect either way.