Re: [firebird-support] Accessing/repairing embedded server database file
On 2015-01-21 10:33 'Paul Beach' pabe...@waitrose.com [firebird-support] wrote: Have you got any suggestions how to try to access/fix that file? I am not a Firebird expert, so I may have missed something (but I studied a lot of docs how to try to fix my problem). Nothing simple and straightforward comes to mind. If you want to acess the database using Firebird's own tools, then you need to get rid of the SYSDBA role first... or find out what the database owner username and password really is. Thanks for your answer, Paul. I tried some tools trying to remove SYSDBA role and failed. Could you point me to the guide that describes how to remove SYSDBA role? I have also one password provided by the app developers that is used to access the app as master user, but maybe it is the same as the owner username and password. But how can I access the embedded server fbd file when providing any non-standard credentials? As I try to connect by using Maestro, it does not allow me to provide any credentials. Best, Radek
[firebird-support] Accessing/repairing embedded server database file
When I try to connect to it using Maestro, I get engine error 335544745 Your login SYSDBA is same as one of the SQL role name. Ask your database administrator to set up a valid Firebird login. I can't say whether this comes due to the file damage or this is the way how embedded server should behave. I tried to connect to this file also by setting up Firebird Server and to use gfix/gsec, but also without success. This is not due to file damage. Basically whoever created the database set up a role as SYSDBA a well known trick to stop anybody accessing the database using the default security database and default user name and password. Have you got any suggestions how to try to access/fix that file? I am not a Firebird expert, so I may have missed something (but I studied a lot of docs how to try to fix my problem). Nothing simple and straightforward comes to mind. If you want to acess the database using Firebird's own tools, then you need to get rid of the SYSDBA role first... or find out what the database owner username and password really is. Paul
Re: [firebird-support] Accessing/repairing embedded server database file
Have you got any suggestions how to try to access/fix that file? I am not a Firebird expert, so I may have missed something (but I studied a lot of docs how to try to fix my problem). Nothing simple and straightforward comes to mind. If you want to acess the database using Firebird's own tools, then you need to get rid of the SYSDBA role first... or find out what the database owner username and password really is. I tried some tools trying to remove SYSDBA role and failed. Could you point me to the guide that describes how to remove SYSDBA role? I have also one password provided by the app developers that is used to access the app as master user, but maybe it is the same as the owner username and password. But how can I access the embedded server fbd file when providing any non-standard credentials? As I try to connect by using Maestro, it does not allow me to provide any credentials. I am not aware of such a guide, but you might find something if you search the internet hard enough. I can think of a few ways that it might be possible but I would have to try them before I could confirm. Regards Paul
[firebird-support] Accessing/repairing embedded server database file
Dear All, I face the problem of accessing/repairing damaged fdb file that (probably) comes from firebird embedded server (dated abt. 2004, I don't know how to find accurate version number, Windows app). The damage comes from lack of hdd space and it seems that the file has an I/O error, unexpected end of file. This prevents to run an app that bases on it that is a Polish accounting/warehouse application (EWAN System). When I try to connect to it using Maestro, I get engine error 335544745 Your login SYSDBA is same as one of the SQL role name. Ask your database administrator to set up a valid Firebird login. I can't say whether this comes due to the file damage or this is the way how embedded server should behave. I tried to connect to this file also by setting up Firebird Server and to use gfix/gsec, but also without success. Have you got any suggestions how to try to access/fix that file? I am not a Firebird expert, so I may have missed something (but I studied a lot of docs how to try to fix my problem). Greetings Radek