Subject | Re: [firebird-support] Restore problem (internal gds software consistency check / cannot start thread / failed to create database) |
---|---|
Author | Antti Nivala |
Post date | 2007-10-28T16:15:38Z |
Vlad Khorsun wrote:
a memory issue because there was plenty of free memory and the "cannot
start thread" error message from Firebird mislead us.
Anyway, we simply exceeded the maximum virtual memory size by attempting
to restore a second instance of >1 GB database into a 32-bit server
process. The page size was 8K and page buffers about 131,000, resulting
in a memory consumption of 1 GB per database. This was intentional for
the actual database, but the second temporary instance did not need that
much memory. The issue was easy to solve by reducing the number of page
buffers for the second instance.
Thanks for your help, Vlad!
Best regards,
Antti Nivala
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/
> You have no more virtual memory available in system. Double checkIndeed, this was the problem. We just did not think of the connection to
> why memory concuming is so high.
a memory issue because there was plenty of free memory and the "cannot
start thread" error message from Firebird mislead us.
Anyway, we simply exceeded the maximum virtual memory size by attempting
to restore a second instance of >1 GB database into a 32-bit server
process. The page size was 8K and page buffers about 131,000, resulting
in a memory consumption of 1 GB per database. This was intentional for
the actual database, but the second temporary instance did not need that
much memory. The issue was easy to solve by reducing the number of page
buffers for the second instance.
Thanks for your help, Vlad!
Best regards,
Antti Nivala
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.f-secure.com/