From EDB Manager, when i try to

DROP DATABASE "<DB_Name>"

(or otherwise access that database)

I get the error :

"ElevateDB Error #400 The table  already exists in the schema Default"

It looks like the offending table has the name of the empty string

I'm guessing this weird behaviour is to do with a system crash which just occurred while running an SQL script into EDB.

Do i need to re-install Elevate ?

Thanks in advance
Tony Wood

Tony


Without being able to play with your PC myself I'd suggest the following:


1. Try creating a new database and see if that works OK. If so you don't need to reinstall ElevateDB
2. If that doesn't work try deleting the ini file that controls EDBManager - mine's in C:\Documents and Settings\Roy Lambert\AppData\Local\Elevate Software\ElevateDB Manager\ - Try creating a new database and see if that works OK
3. If that doesn't work uninstall EDBManager and reinstall (its a separate stand alone app so no need to uninstall ElevateDB generally), removing the ini file and its directory, reinstall EDBManager - Try creating a new database and see if that works OK

The system crash may have corrupted the config file or the catalog file. If its the config file then deleting and recreating will fix things, if its the catalog then the database is probably gone for good. Its worth saving a copy in case Tim wants it for forensics or can recover things for you.

Assuming its the config file that's gone then once you can create a new database, if you didn't need to delete the ini file go and edit it and remove the session information for that configuration, delete the config file and use EDBManager to create a new session pointing at the database.


Roy Lambert [Team Elevate]

Hi Roy, thanks for your thoughtful and considered reply.

With no config changes, I can create a new database, and also drop other databases which were present before the crash, but not the one which was being loaded during the crash.

I've tried disconnecting the session (to 'remote' server at 127.0.0.1), still same deal

I tried deleting and re-creating the session, same deal.

As per your advice, I then found the EDB server ini file and deleted it (actually being paranoid I renamed it). After restarting the server, the zombie database had disappeared. All now looks OK again

thanks again for your help
Tony Wood

Tony,

<< I'm guessing this weird behaviour is to do with a system crash which just
occurred while running an SQL script into EDB. >>

If you were modifying the database catalog for that database at the time of
the crash, then you need to make sure to restore the edbdatabase.edbcat.old
from within the database directory, along with any .old versions of the
table files that were also being modified at the time.  If you do a
directory listing of the database directory by modification date/time,  you
should see the latest modified files along with their .old versions, which
are the backup copies of the files made before they were modified.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tony,

BTW, when I say "restore", I mean copy the .old file over the original,
non-.old extension version of the same root file name.

--
Tim Young
Elevate Software
www.elevatesoft.com