[firebird-support] Start service of Firebird 2.5 in Centos 7

2016-04-13 Thread Carlos Mazariegos carlos.mazarie...@umg.edu.gt [firebird-support] 
Hello:


I can not start the service Firebird 2.5 on Centos 7. Please if someone
can tell me how.


thank you
--


Carlos Mazariegos
/Dirección de Desarrollo/


Universidad Mariano Gálvez
3a. Av. 9-00 Zona 2 · Int. Finca El Zapote
Tel: *24111800 Ext. 1166 y 1290* · Fax: *Ext. 1166*

carlos.mazarie...@umg.edu.gt  · 

www.umg.edu.gt

Re: [firebird-support] FB on LAN

2016-04-13 Thread Hugo Eyng hugoe...@msn.com [firebird-support] 

Hello Mark.

I changed the firebird.conf by another one and restarted the server.

Now my string connection 192.168.0.158:C:\DIR1\BASEDIR\MYDATABASE.FDB is 
working.


I compared both firebird.conf and found two differences:

1) In the line near

# Remove protection against opening databases on NFS mounted volumes on
# Linux/Unix and SMB/CIFS volumes on Windows.

that appears in original

# ***WARNING*** ***WARNING*** ***WARNING*** ***WARNING***

in my firebird.conf the line was brioked, like

# ***WARNING*** ***WARNING**
* ***WARNING*** ***WARNING***

2)  There was difference in this line too, but the lines are commented.

#CpuAffinityMask = 1

#CpuAffinityMask = 192

I am sure this could not cause problems, but the item 1 could? I think 
it is not pr
Em 08/04/2016 04:12, Mark Rotteveel m...@lawinegevaar.nl 
[firebird-support] escreveu:


On 7-4-2016 20:54, Hugo Eyng hugoe...@msn.com [firebird-support] wrote:
> Hello Mark.
>
> I was like you showed 192.168.0.158:C:\DIR1\BASEDIR\MYDATABASE.FDB
>
> Than I changed from FB 32 to FB 64 and it stopped working. After that,
> after that even turnning to FB 32 it doesn´t work using this structure.
> I only works
> using \\192.168.0.158\C:\DIR1\BASEDIR\MYDATABASE.FDB or
> C:\DIR1\BASEDIR\MYDATABASE.FDB

In your first question your connection string was:

192.168.0.158:\DIR1\BASEDIR\MYDATABASE.FDB

Note the absence of _C:_ This means you are connecting with a relative
path. And the root of this path depends on the configuration (and maybe
on the user running Firebird).

> I open the 3050 port in FW. But it keep not connecting.

I just realised that you never specified the exact error you received.
Can't you connect to Firebird at all? What error do you get?

In that case it might be that it is 1) configured to use a different
port (setting RemoteServicePort), 2) is blocked by the (Windows)
firewall (make sure there is an exclusion for the process), 3) another
process is running on port 3050, or 4) the firebird process is only
listening on 127.0.0.1 (setting RemoteBindAddress).

Mark
--
Mark Rotteveel




--


Atenciosamente,

Hugo Eyng

Re: [firebird-support] FB on LAN

2016-04-13 Thread Hugo Eyng hugoe...@msn.com [firebird-support] 

Hello Mark.

I changed the firebird.conf by another one and restarted the server.

Now my string connection 192.168.0.158:C:\DIR1\BASEDIR\MYDATABASE.FDB is 
working.


I compared both firebird.conf and found two differences:

1) In the line near

# Remove protection against opening databases on NFS mounted volumes on
# Linux/Unix and SMB/CIFS volumes on Windows.

that appears in original

# ***WARNING*** ***WARNING*** ***WARNING*** ***WARNING***

in my firebird.conf the line was wraped, like

# ***WARNING*** ***WARNING**
* ***WARNING*** ***WARNING***


Em 08/04/2016 04:12, Mark Rotteveel m...@lawinegevaar.nl 
[firebird-support] escreveu:


On 7-4-2016 20:54, Hugo Eyng hugoe...@msn.com [firebird-support] wrote:
> Hello Mark.
>
> I was like you showed 192.168.0.158:C:\DIR1\BASEDIR\MYDATABASE.FDB
>
> Than I changed from FB 32 to FB 64 and it stopped working. After that,
> after that even turnning to FB 32 it doesn´t work using this structure.
> I only works
> using \\192.168.0.158\C:\DIR1\BASEDIR\MYDATABASE.FDB or
> C:\DIR1\BASEDIR\MYDATABASE.FDB

In your first question your connection string was:

192.168.0.158:\DIR1\BASEDIR\MYDATABASE.FDB

Note the absence of _C:_ This means you are connecting with a relative
path. And the root of this path depends on the configuration (and maybe
on the user running Firebird).

> I open the 3050 port in FW. But it keep not connecting.

I just realised that you never specified the exact error you received.
Can't you connect to Firebird at all? What error do you get?

In that case it might be that it is 1) configured to use a different
port (setting RemoteServicePort), 2) is blocked by the (Windows)
firewall (make sure there is an exclusion for the process), 3) another
process is running on port 3050, or 4) the firebird process is only
listening on 127.0.0.1 (setting RemoteBindAddress).

Mark
--
Mark Rotteveel




--


Atenciosamente,

Hugo Eyng

Re: [firebird-support] [FB 2.1] Firebird engine seems to slowdown on high load without utilizing hardware

2016-04-13 Thread liviusliv...@poczta.onet.pl [firebird-support] 
Hi,
i have few questions releated to your problem
1. What is your sweep settings?
2. When you run backup and do you use gbak or nbackup?
3. what is your transactions settings? Do you use readonly readcommited or 
prefered shapshot?
regards,
Karol Bieniaszewski

Re: Re: [firebird-support] [FB 2.1] Firebird engine seems to slow down on high load without utilizing hardware

2016-04-13 Thread liviuslivius liviusliv...@poczta.onet.pl [firebird-support] 
>>Hey,
>>not sure how you can survive with superserver :)
>>I can't see that working with our kind of load (realtime-data-processing, 
>>reports, mostly write IOPS)
>>It's a long time ago (Fb 1.5) since we used superserver but we didn't have 
>>the best time with it back then.
 
I do not know what is your database for
but we have monitoring database where we move all older than 3 day data to 
monthly archive databases.
Then any raports created are fast on working database and slow down in archive.
Archive databases are on different server. Then we never do large raport on big 
data on production server.
>>But currently this is not about switching the server-version. More about 
>>undestanding why the server is not using the provided hardware :)
>>Also it reads kinda strange if you talk about high load, but always have low 
>>cpu usage :)
 
i have high load with low cpu.
When i mean load i think about IO.
I have many record modifications/insert but cpu near to never increase above 
50% of core.
Maybe you have much more load i have 17 000 000 new records stored into 
database and one new record cause 1 to many updates to existing records.
if we calc than we have 196 record per second (if i cal this correctly) - i do 
not know what is your load to compare.
 
All work fast - and only system slow down, when backup start.
But backup is fast because we do backup to RAM disk and then automatically we 
move this backup to another server where automatically db is restored to check 
if db is healthy
 
regards,
Karol Bieniaszewski

Re: [firebird-support] monitoring Table

2016-04-13 Thread 'Thomas Steinmaurer' t...@iblogmanager.com [firebird-support] 
Hello Olaf,

'Checkmail' check_m...@satron.de [firebird-support] schrieb am 13.04.2016 14:38:

> Hello,
> 
> 
> 
> I've a problem with our database, firebird 3.0 RC2, some Clients (C++,
> Microsoft Access over Firebird ODBC). There are 7 open transactions. But
> in the monitoring Table, I cannot see the one who is the oldest was shown.
> Why?

How/where do you identify the oldest transaction?


--
With regards,
Thomas Steinmaurer
http://www.upscene.com

Professional Tools and Services for Firebird
FB TraceManager, IB LogManager, Database Health Check, Tuning etc.



> 
> 
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2834893, 85000, 1, '2016-04-13 14:34:31',
> 2834893, 2774214, 2771000, 2, 0, 0, 0, 1, 201);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2208191, 68114, 0, '2016-04-07 05:03:44',
> 2208191, 2768721, 2771000, 2, -1, 1, 0, 1, 319);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2833276, 83617, 1, '2016-04-13 07:00:29',
> 2771000, 2768721, 2769594, 2, -1, 0, 0, 1, 1267);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2834878, 84239, 1, '2016-04-13 10:38:25',
> 2792941, 2768721, 2771000, 2, -1, 0, 0, 1, 1677);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2834800, 84681, 1, '2016-04-13 14:21:39',
> 2832348, 2768721, 2771000, 2, -1, 0, 0, 1, 1933);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2833230, 84857, 1, '2016-04-13 14:25:23',
> 2833010, 2768721, 2771000, 2, -1, 0, 0, 1, 2196);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2829258, 84866, 1, '2016-04-13 14:06:50',
> 2829258, 2768721, 2771000, 2, -1, 0, 0, 1, 2293);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2834822, 84891, 1, '2016-04-13 14:13:14',
> 2829911, 2768721, 2771000, 2, -1, 0, 0, 1, 2358);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2833355, 84977, 1, '2016-04-13 14:27:03',
> 2833355, 2768721, 2771000, 2, -1, 0, 0, 1, 2450);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2833491, 84980, 1, '2016-04-13 14:28:18',
> 2833491, 2768721, 2771000, 2, -1, 0, 0, 1, 2527);
> 
> INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
> MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
> MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
> MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)
> 
>  VALUES (2834880, 85006, 1, '2016-04-13 14:34:02',
> 2834880, 2774214, 2771000, 2, -1, 0, 0, 1, 2664);
> 
> 
> 
> COMMIT WORK;
> 
> 
> 
> Thank you
> 
> 
> 
> Best re

[firebird-support] monitoring Table

2016-04-13 Thread 'Checkmail' check_m...@satron.de [firebird-support] 
Hello,

 

I've a problem with our database, firebird 3.0 RC2, some Clients (C++,
Microsoft Access over Firebird ODBC). There are 7 open transactions. But
in the monitoring Table, I cannot see the one who is the oldest was shown.
Why?

 

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2834893, 85000, 1, '2016-04-13 14:34:31',
2834893, 2774214, 2771000, 2, 0, 0, 0, 1, 201);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2208191, 68114, 0, '2016-04-07 05:03:44',
2208191, 2768721, 2771000, 2, -1, 1, 0, 1, 319);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2833276, 83617, 1, '2016-04-13 07:00:29',
2771000, 2768721, 2769594, 2, -1, 0, 0, 1, 1267);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2834878, 84239, 1, '2016-04-13 10:38:25',
2792941, 2768721, 2771000, 2, -1, 0, 0, 1, 1677);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2834800, 84681, 1, '2016-04-13 14:21:39',
2832348, 2768721, 2771000, 2, -1, 0, 0, 1, 1933);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2833230, 84857, 1, '2016-04-13 14:25:23',
2833010, 2768721, 2771000, 2, -1, 0, 0, 1, 2196);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2829258, 84866, 1, '2016-04-13 14:06:50',
2829258, 2768721, 2771000, 2, -1, 0, 0, 1, 2293);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2834822, 84891, 1, '2016-04-13 14:13:14',
2829911, 2768721, 2771000, 2, -1, 0, 0, 1, 2358);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2833355, 84977, 1, '2016-04-13 14:27:03',
2833355, 2768721, 2771000, 2, -1, 0, 0, 1, 2450);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2833491, 84980, 1, '2016-04-13 14:28:18',
2833491, 2768721, 2771000, 2, -1, 0, 0, 1, 2527);

INSERT INTO MON$TRANSACTIONS (MON$TRANSACTION_ID, MON$ATTACHMENT_ID,
MON$STATE, MON$TIMESTAMP, MON$TOP_TRANSACTION, MON$OLDEST_TRANSACTION,
MON$OLDEST_ACTIVE, MON$ISOLATION_MODE, MON$LOCK_TIMEOUT, MON$READ_ONLY,
MON$AUTO_COMMIT, MON$AUTO_UNDO, MON$STAT_ID)

  VALUES (2834880, 85006, 1, '2016-04-13 14:34:02',
2834880, 2774214, 2771000, 2, -1, 0, 0, 1, 2664);

 

COMMIT WORK;

 

Thank you

 

Best regards

 

Olaf