Hi !
Em 16/1/2014 04:13, brucedickin...@wp.pl escreveu:
Hi guys.
Yesterday I was trying to figure out what is the cause of my problem.
And I've noticed that two months ago my colleague added one trigger on
this table. The trigger is:
SET TERM ^ ;
ALTER TRIGGER CLIENT_LM INACTIVE
AFTER
Looking at my production system I see that I have an FDB file and an
FDB.delta. The date of the FDB is May 2nd, 2013. The date of the
delta is today.
These are just 2 separate databases. Firebird does not require a
special extension, .fdb ist just the usual extension to use.
From the names I
Whoa, this is interesting...
My first attempt to move the DB was to simply copy over the FDB. That didn't
work, so that's when I went down the nbackup rabbit hole. As it turns out,
nbackup is the problem, not the solution...
When I tried to re-attach the FDB file on the new server I got a file
Hello Maury,
When I tried to re-attach the FDB file on the new server I got a file not
found error. But looking in some of the logging files I found...
Reason: I/O error for file CreateFile (open)
D:\FISHBOWL\DATABASE\DATA\ASSOLAR.FDB.delta
Error while trying to open file
null
A.
On 2014-01-16, at 10:11 AM, Paul Vinkenoog wrote:
What exactly are you missing in the documentation? Notice that delta
files are normally very short-lived.
That's the issue right there. As it is clearly possible that these are not
*always* short lived, this should be mentioned along with
On Wed, Jan 15, 2014 at 4:42 PM, rmcgi...@oceris.com wrote:
Ok, running the gfix -sweep with everyone logged out did work and only
took about 5 minutes. I believe the issue came from me only trying to run
the sweep one time and a transaction being stuck. I never tried to run
sweep AFTER
You should check wich application holds the oldest transaction open, and fix
it.
Thank you, is it possible that this transaction is just hanging and an
application which started it,has been already terminated? If I am not mistaken,
I can somehow check out some system table for active
Do you know if or when the trigger was ACTIVATED? It's very hard to see how
deactivating a hungry trigger like that one could *degrade* performance.
I am sorry Helen for confusing you. I've posted DDL for already deactivated
trigger which I've deactivated yesterday.
The trigger was
I notice that it is now possible to connect to a database via the embedded
server and simultaneously connect via other embedded processes to the same
database file. This was not possible in previous version - the second
process would be locked out.
Can someone lead me to an explanation of how
Hi Alan,
I notice that it is now possible to connect to a database via the embedded
server and simultaneously connect via other embedded processes to the same
database file. This was not possible in previous version - the second
process would be locked out.
Can someone lead me to an
Hello, Paul, Alan!
PV Windows Embedded now contains a SuperClassic instead of a SuperServer
engine.
PV File locks are shared, so a database can be accessed by one or more
Embedded
PV servers and a regular Classic or SuperClassic server at the same time.
PV Consult the Firebird 2.5 Release
Hi Alan,
I notice that it is now possible to connect to a database via the
embedded server and simultaneously connect via other embedded
processes to the same database file. This was not possible in previous
version - the second process would be locked out.
Can someone lead me to an
Hello, Paul, Alan!
PV Windows Embedded now contains a SuperClassic instead of a
SuperServer engine.
PV File locks are shared, so a database can be accessed by one or more
PV Embedded servers and a regular Classic or SuperClassic server at the
same time.
PV Consult the Firebird 2.5
On 16/01/2014 6:07 PM, Helen Borrie wrote:
At 06:28 p.m. 16/01/2014, Cam wrote:
Hi
Using Firebird 2.5.2 32 bit SuperServer.
Happens on Win XP, WIN7 64 BIT oS'S
Occasionally on some sites I am getting a dialog Box with
ISCErrorCode 335544648
Unknown ISC Error 0
According to the error
Alan McDonald wrote:
Windows Embedded now contains a SuperClassic instead of a SuperServer
engine.
File locks are shared, so a database can be accessed by one or more
Embedded servers and a regular Classic or SuperClassic server at the same
time.
Consult the Firebird 2.5 Release
Maury Markowitz wrote:
What exactly are you missing in the documentation? Notice that delta
files are normally very short-lived.
That's the issue right there. As it is clearly possible that these are not
*always* short lived, this should be mentioned along with suggestions on what
to
16 matches
Mail list logo
