Subject | Re: [ib-support] Re: Closing the gap between OAT and Next transaction |
---|---|
Author | Luciano Sparacino |
Post date | 2002-01-22T16:08:01Z |
I'm getting a similar error with IB6 and FB RC1 but i always get the server to slow down performance at a specified time everyday (always close to noon). Once the server is restarted, the application starts working ok again.
Our application also uses IBO and TIBOTable and TIBOQuery components to access the database and most of them uses autocommit. We are actually changing the code to manage explicit transactions (with TIB_TransactionSinlge) for the main operations and we started to get better results (at least the server recovers after a user finishes to ask for a heavy query). I don't know how IBO manages Autocommit, but it's not a subject to be discused in this group.
When we examine the IB log we find the message " gds__free: attempt to release bad block " like 10 times per second before it gets slow and needs to be restarted.
[Non-text portions of this message have been removed]
Our application also uses IBO and TIBOTable and TIBOQuery components to access the database and most of them uses autocommit. We are actually changing the code to manage explicit transactions (with TIB_TransactionSinlge) for the main operations and we started to get better results (at least the server recovers after a user finishes to ask for a heavy query). I don't know how IBO manages Autocommit, but it's not a subject to be discused in this group.
When we examine the IB log we find the message " gds__free: attempt to release bad block " like 10 times per second before it gets slow and needs to be restarted.
[Non-text portions of this message have been removed]