Sorry to confuse Adam. Yes, I did mean read_only database. My database was read_only initially and I had to make it writable using
      GFIX -user SYSDBA -password masterkey -mode read_write

Also, I may have forgotten mention when I stress tested the db I was only doing SELECT.

Niben

--- On Sun, 8/24/08, Adam <s3057043@...> wrote:
From: Adam <s3057043@...>
Subject: [firebird-support] Re: Internal gds software consistency check (cannot find tip page (165))
To: firebird-support@yahoogroups.com
Date: Sunday, August 24, 2008, 2:00 AM











--- In firebird-support@ yahoogroups. com, Niben M Singh <niben_s@... >

wrote:

>

> I stress tested my firebird database by running a query that

> returns about fair amount of data (like 200 rows) 20000 times in a

loop. I

> found that after running the query about half an hour the database hung

> and became inaccessible. The database would not accept any

connections. I had to restart the server in order to re-run

> my queries. I looked into the firebird.log file and saw error

message "Internal gds software consistency check (cannot find tip page

(165))".

>

> Upon googling the error message I came across this page

>           http://dn.codegear com/article/ 30208

>

> Just as stated in the page the user I was using had read-only access

to the database.



No, the article states that it is a read-only database, not a user

connected with a read only transaction, a user with no insert update

or delete privileges, or a user connected with a read-write

transaction but executing read only dml.



A read-only database is a database designed to be stored but never

edited once distributed (eg CD ROM distribution) , and this appears to

be the environment the article you found refers to.



That said, Firebird shares a history with Interbase, so it is

certainly not without possibility that the errors in IB may also be

found in Firebird.



Adam





























[Non-text portions of this message have been removed]