Hello Sandris,
Thursday, March 2, 2017, 5:24:03 AM, you wrote:
> Hello!
> Error occurs if i am trying to register database events using 3.0.2.
> fbclient.dll to firebird 3.0.2. on linux.
> "Failed to establish a secondary connection for event processing."
> No error if server is on
FireBirdCS-2.5.5.26952
Intel® Core™ i7-2600 Quad-Core inkl. - 4 ядра, 32 GB DDR3 RAM, 2 x 3 TB 6 Gb/s
HDD SATA3
Debian 6 Squeeze 64 bit
Work the database is on a separate 250 GB 6 Gb/s SSD
At last week in log this messages:
servTue Feb
Hello!
Error occurs if i am trying to register database events using 3.0.2.
fbclient.dll to firebird 3.0.2. on linux.
"Failed to establish a secondary connection for event processing."
No error if server is on windows or server is on linux and using 2.5 client.
Ann,
thank you very much for your answer.
Aldo
El 01/03/17 a las 11:44, Ann Harrison aharri...@ibphoenix.com
[firebird-support] escribió:
On Mar 1, 2017, at 9:53 AM, Aldo Caruso wrote:
Ann,
Thanks for your detailed answer.
But this leads me to the following question: If
> On Mar 1, 2017, at 9:53 AM, Aldo Caruso wrote:
>
>
>
> Ann,
>
> Thanks for your detailed answer.
>
> But this leads me to the following question: If snapshot transactions
> have their own copy of the Transaction Inventory Pages ( TIP ), taken when
> the transaction started,
Ann,
Thanks for your detailed answer.
I agree with you: the only isolation level which each transaction
takes care of is its own isolation level. So this behavior happens
because A isolation level is snapshot ( regardless of the isolation
level of B or C ).
Also I suspected your
Hi Andreas,
I think the main thing is
* blockdev -setfra 32768 - this has nothing to do with
firebird but speeds up reads in the RAID array quite a bit. Thanks
to wltjr on IRC.
and, probably, backup/restore.
In 2.5 the bad effect of autosweep is almost eliminated on the systems
> On Feb 28, 2017, at 3:07 PM, Aldo Caruso wrote:
>
> I'm trying to understand interactions between transactions with
> different isolation levels.
The problem is not mixed isolation levels. You would get the same behavior if
all transactions were Snapshot
The scenario (described below in
On 2017-03-01 09:59, Dmitry Yemanov dim...@users.sourceforge.net
[firebird-support] wrote:
> 01.03.2017 11:58, jonatan.laurit...@yahoo.dk wrote:
>
>> OK, I have working Firebird 3.0.1 installation and I have copied
>> security3.fdb from the broken Firebird installation and now I am also
>>
On 2017-03-01 11:41, jonatan.laurit...@yahoo.dk [firebird-support]
wrote:
> Solution found - I had to use the "create user" command with the
> "using" clause:
> SQL> create user SYSDBA password 'masterkey' using plugin Srp;
>
> My firebird.cong indicated that Legacy_Auth is the first (default)
>
On 2017-03-01 09:34, jonatan.laurit...@yahoo.dk [firebird-support]
wrote:
> Hi!
>
> Our client has Firebird 3.0 super server installation which has the
> following behaviour:
> - Client software (e.g. Flamerobin) can establish connection using
> Firebird 2.x fbclient.dll
> - When client software
Solution found - I had to use the "create user" command with the "using" clause:
SQL> create user SYSDBA password 'masterkey' using plugin Srp;
My firebird.cong indicated that Legacy_Auth is the first (default) user manager
and it was necessary for isql to know that Srp manager had to be used:
isql allowed to change the password of the SYSDBA account but that did not
removed original error message about "installation incomplete"...
OK - I am starting to understand. Apparently client had Firebird default
instance Windows registry entry from the Firebird installations of the previous
versions. That is why Firebird 3.0 installation wizard did not displayed
extended configuration form with the possibility to initialize
01.03.2017 11:37, jonatan.laurit...@yahoo.dk wrote:
> Actually, I don't understand this thing about old and new authorization
> system. Does it mean that there are two SYSDBA and other user accounts -
> one for old and other for new authorization system and does it mean that
> there are two sets
01.03.2017 11:58, jonatan.laurit...@yahoo.dk wrote:
> OK, I have working Firebird 3.0.1 installation and I have copied
> security3.fdb from the broken Firebird installation and now I am also
> receiving the error message. So - security3.fdb is somehow broken,
> problem is in security3.fdb
It's
OK, I have working Firebird 3.0.1 installation and I have copied security3.fdb
from the broken Firebird installation and now I am also receiving the error
message. So - security3.fdb is somehow broken, problem is in security3.fdb
Actually, I don't understand this thing about old and new authorization system.
Does it mean that there are two SYSDBA and other user accounts - one for old
and other for new authorization system and does it mean that there are two sets
of passwords?
Is it safe to check 'Enable authorization
Hi!
Our client has Firebird 3.0 super server installation which has the following
behaviour:
- Client software (e.g. Flamerobin) can establish connection using Firebird 2.x
fbclient.dll
- When client software (e.g. Flamerobin) tries to connect using Firebird 3.x
fbclient.dll then the error
19 matches
Mail list logo
