At Process level, we user the Super Classic, and the Process is loaded, but has NO activity, and no errors, it takes the initial memory load but after the first minute or 2 after the restart there is no CPU activity... even when trying to access the DB... I will be restarting the server around 7 or 8pm today South African Time... as soon as I’ve run the Gstat I will post...
Thank you for the assistance so far, so hoping we find the issue, something I also noticed while poking around is that this DB’s Buffer is much lower than any of my other DB’s, this could also cause an issue? Other DB buffer Pages : 4096 Size : 16384 This DB buffer Pages : 75 Size : 300 Both DB’s are roughly the same size From: [email protected] [mailto:[email protected]] On Behalf Of Ann Harrison Sent: 19 December 2013 00:01 To: [email protected] Subject: Re: [firebird-support] Database Inaccessability On 12/18/2013 7:48 AM, [email protected] wrote: I have a Firebird SQL database running on a HP ML350 Server, 16GB Ram and Dual Processors.. The Problem I have is when we restart this server, the Database is completely inaccessible for a minimum of 2 - 3 hours, can't even open Using a SQL Manager... any Ideas on what to look at?? after the 2-3Hours the db is accessible and works perfectly, it only happens when the server is restarted... What is happening on the machine at the process level? If you're running a shared server - SuperServer or Super Classic - has that process started? If so, what's it doing - I/O? CPU load? Page faulting? Idle? If you're running classic, has the connection process started? Same questions about what's happening. After your database has been running for a while, check the header statistics, looking for a long-running process. Good luck, Ann __________ Information from ESET Smart Security, version of virus signature database 9190 (20131218) __________ The message was checked by ESET Smart Security. http://www.eset.com __________ Information from ESET Smart Security, version of virus signature database 9190 (20131218) __________ The message was checked by ESET Smart Security. http://www.eset.com
