At 09:46 AM 10/03/2008, Fidel Viegas wrote:

>In my case, I did not have to restart the server. All I did was
>restart isql, and it was able to connect to the database without any
>problems. After reading the article about IB6, I thought that my
>database would end up being corrupted, but it didn't.
>
>Your explanation was clearer, and now I have an idea of what may cause
>this to happen.
>
>I really don't want to be wasting people's time,

The comments about wasting people's time were directed at the OP of this thread, not at you or your case.

>so I was wondering if
>there is any troubleshooter's guide that explains the most common
>issues we may find, and what the causes are.

For Bugcheck errors: no. They are not meant to happen so there is no way to predict how or when they might occur. The best one can say is that, if you're using a new release, or field-testing an alpha or beta, under conditions that are physically safe and adequate, then the more detail you can provide about reproducing the fault, the sooner a genuine bug can be identified and fixed.

It is a waste of bandwidth and effort when people report a bugcheck condition without any information. Note that the OP has now posted a second message that clearly shows the database is corrupt. That doesn't happen under safe conditions, either, so no matter how much he yells at the list, he's not going to get much relief if he continues to withhold the essential information.

>I am sorry if I have given the wrong suggestion to Ahmad. It was never
>my intention to waste anyone's time.

That wasn't implied. I hope it's a message that will get through to Ahmad and anyone else who posts a problem with no information. If you're using a released version, post the problem HERE first, with every piece of information that might be useful.

If a problem needs to be escalated to firebird-devel and/or Tracker as a possible bug, the OP will be *invited* to do so.

./heLen