| Subject | Re: [firebird-support] Re: Couldn't connect to local database/datafile |
|---|---|
| Author | Helen Borrie |
| Post date | 2009-02-18T11:28:40Z |
At 10:06 PM 18/02/2009, you wrote:
If the so-called adminn user login, along with the SYSDBA role, didn't get you in then there is almost certainly another layer of processing in the application code to ensure that only users of *his* application can connect. The vendor therefore took a lot of care to protect what is his.
This is always going to be a difficult situation. Your customer owns the user data - and therefore, legally, should have access to it and be able to authorise another DBA to access it on his behalf. But the vendor of the software owns the metadata, including the database design and all the PSQL objects compiled in there. I'm sure you will find this in the vendor's EULA if you look for it.
In this forum we are all developers. It's not our business to provide ways to get past barriers implemented by other developers to protect their property, whatever we might individually feel about such practices.
About your only option would be to contact the vendor and ask if s/he would be prepared to give you the Owner name and permission to disable the SYSDBA role and retrieve your customer's data. Or perhaps it would be better if your customer made the request directly. Don't be outraged if the vendor offers to grant this access for a price.
./heLen
>> Oh - then check your system for the ISC_USER and ISC_PASSWORDWell, not really...after all, the vendor of this database did this trick to keep unauthorised DBAs out.
>environment variables and set them off. Then the root login should work.
>
>none of these variables is set in my environment adn it still doesn't
>work.
>
>Is there anything else, I could try?
If the so-called adminn user login, along with the SYSDBA role, didn't get you in then there is almost certainly another layer of processing in the application code to ensure that only users of *his* application can connect. The vendor therefore took a lot of care to protect what is his.
This is always going to be a difficult situation. Your customer owns the user data - and therefore, legally, should have access to it and be able to authorise another DBA to access it on his behalf. But the vendor of the software owns the metadata, including the database design and all the PSQL objects compiled in there. I'm sure you will find this in the vendor's EULA if you look for it.
In this forum we are all developers. It's not our business to provide ways to get past barriers implemented by other developers to protect their property, whatever we might individually feel about such practices.
About your only option would be to contact the vendor and ask if s/he would be prepared to give you the Owner name and permission to disable the SYSDBA role and retrieve your customer's data. Or perhaps it would be better if your customer made the request directly. Don't be outraged if the vendor offers to grant this access for a price.
./heLen