Rudi,
try to set BugcheckAbort = 1 at firebird.conf
Regards,
Vlad
Hello shg_siste...@yahoo.com.ar,
Friday, September 15, 2017, 2:53:19 AM, you wrote:
> I read somewhere that the "read only" transactions are absolutelly
> harmless to the GC and sweeping. Is that so?
It is true for READ ONLY transactions that are started in READ
COMMITTED isolation mode. In
>but did you checked your DB against corruption?
>gfix –validate –full
>any errors (also in firebird.log)?
The server have about 20 db’s, haven’t performed a validate full on each one of
them.
At the moment Im assuming theres no corruption because all of our clients are
fully operational
Hi,
i do not remember your previous description
but did you checked your DB against corruption?
gfix –validate –full
any errors (also in firebird.log)?
Did you performed backup/restore process.
Do you use any udf? also system udf?
Do you have enough free mem, free disk space also for temp files
Hello
It’s been a while since I gave na update on my situation here.
To recap, firebird 3 is crashing randomly on my server. It may crash once,
twice, or 10 times a day. Or not once during the day.
Server load is always minimal during the crashes, and so is the memory usage.
With the help
>>Karol,
>>I was referring to the default transaction state of snapshot (repeatable
>>read)
>>Other transaction states will have different effects. In your case
>>read commited needs only the newest record version (or record versions
>>created by
>>the transaction itself) so its not going
> I read somewhere that the "read only" transactions are absolutelly harmless
> to the GC and sweeping. Is that so?
>>Read only transactions only physically have an impact on the TIP/Header
>>page(s), however a long running read only transaction
>>will have the same effect as a long running
> I read somewhere that the "read only" transactions are absolutelly harmless
> to the GC and sweeping. Is that so?
>>Read only transactions only physically have an impact on the TIP/Header
>>page(s), however a long running read only transaction
>>will have the same effect as a long running
<>
Not really, 2 weeks or 2 months would be a huge time.
> I read somewhere that the "read only" transactions are absolutelly harmless
> to the GC and sweeping. Is that so?
Read only transactions only physically have an impact on the TIP/Header
page(s), however a long running read only
Hello Helen!!
THANKS A MILLION FOR YOUR VERY COMPLETE ANSWER
I did a simple routine to trap in a TXT log file all the active transactions.
I realized that I need to be SYSDBA in order to run a query against
MON$TRANSACTIONS. So, every time a user enters or exits from the applitaction
10 matches
Mail list logo
