Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Databases not visible in EDBManager after restart of EDB Server.
Wed, Oct 5 2011 2:23 AMPermanent Link

TonyWood

Hi All

Using EDB 2.05 b11, occasionally (well maybe a couple of times a day) I have to reboot my PC to workaround a stubborn table lock issue. On restarting , i manually restart edbsrvr.exe and edbmgr.exe. I have a 'remote' edb server running at 127.0.0.1.

The problem is this : the databases which were present before the reboot aren't visible in the EDB manager's left hand column. I can see the previous sessions (Default, 127.0.0.1 and local, but drilling down fails to reveal the databases. However, if i run DDL 'CREATE DATABASE' commands to re-create the missing table(s), they now appear in the expandable click tree in the left hand pane (as you would expect), but the constituent tables are also present and populated with their data from before the reboot (which i didn't expect).

Any thoughts on this one ?
Thanks in advance
Tony Wood
Wed, Oct 5 2011 11:19 PMPermanent Link

TonyWood

Well I just went through this again, but, to make a liar of myself, the populated DBs did re-appear as soon as i restarted edbsrvr.

not sure what's going on - must be my aura
Thu, Oct 6 2011 3:11 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

TonyWood


I'd be more inclined to suspect the ini file than your aura Smiley

The ini file is what's used to set up the sessions in EDBManager and its the sessions that link to the configuration file which tells ElevateDB where the catalog files are which hold the information about the table.

Roy Lambert [Team Elevate]
Tue, Oct 11 2011 3:00 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Tony,

<< Using EDB 2.05 b11, occasionally (well maybe a couple of times a day) I
have to reboot my PC to workaround a stubborn table lock issue. On
restarting , i manually restart edbsrvr.exe and edbmgr.exe. I have a
'remote' edb server running at 127.0.0.1. >>

Is this the same table lock issue that you were having with the ODBC Driver
?  If so, then you should check the server sessions when this happens to see
if there are any "dead sessions" hanging around.  Dead sessions are sessions
that are present, but not connected to a client.  Therefore, they can be
holding locks and other resources that other sessions need to acquire.

--
Tim Young
Elevate Software
www.elevatesoft.com
Image