Then you use that name to login into the problematic database and to DROP ROLE SYSDBA COMMIT. So you would have to look into the said table, find the row with the said role, and learn the username that has authority over that role (in the example it was LOCKSMITH).Īfter that you connect to any other database on the same server and you create the user with the name you learnt. INSERT INTO RDB$ROLES(RDB$ROLE_NAME, RDB$OWNER_NAME) The query to create the blocking role is given on the 23rd page of the presentation. You only need to find and read one specific row. And probably there are more tools featuring data extraction from corrupt databases. But I hope the tool works in IBExpert Trial. Full IBExpert is paid for non-USSR states and free IBExpert Personal probably does not have the tool. One such tool is Database Explorer in the IBExpert. You can try some tool that opens Firebird databases without using Firebird itself to learn what username can pull you out of the deadlock. Like said by Mark, it is not that the database "does not have SYSDBA user" - databases in Firebird 2.x never have users - but that old trick was used to create SYSDBA named role in order to trigger names collision on login.Īfter scanning through 2007 Security presentation I have two suggestions for you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |