Firebird Documentation IndexFirebird 3.0.2 Release NotesCompatibility Issues → Upgrading a v.2.x Security Database
Firebird Home Firebird Home Prev: Legacy AuthenticationFirebird Documentation IndexUp: Compatibility IssuesNext: Local Connections to Superserver on Windows

Upgrading a v.2.x Security Database

Steps

Because of the new authentication model in Firebird 3, upgrading a v.2.5 security database (security2.fdb) directly for use under Firebird 3 is not possible. However, an upgrade procedure is in place to enable retention of the user account data—user name, first name, etc., but not passwords— from the security2.fdb database that was used under v.2.x. servers.

The SYSDBA user is not touched: after the upgrade procedure, it will remain as it was before.

Steps

Note

  • In the commands below, replace masterkey with the actual SYSDBA password for the server version, as appropriate.
  • The procedure requires running the script security_database.sql that is located in the misc/upgrade directory of your Firebird 3 installation. These instructions assume you have a temporary copy of this script in the same directory as the isql executable.
  1. Under the Firebird 2.5 server, back up the security database. Here, use the SYSDBA password for the v.2.5 installation:
      gbak -user sysdba -pas masterkey -b {host/path}security2.fdb security2.fbk
                
  2. Under the Firebird 3 server, restore a copy of v.2.5 backup. Here, use the SYSDBA password for the v.3 installation:
      gbak -user sysdba -pas masterkey -c security2.fbk {host/path}security2db.fdb
                
  3. Under the Firebird 3 server, go to the directory where the isql utility is located and run the upgrade script:
      isql -user sysdba -pas masterkey -i security_database.sql {host/path}security2db.fdb
                
    "security2db.fdb" is just a sample name for the database: it can be any preferred name.
  4. The procedure will generate new, random passwords and will output them to screen afterwards. Capture the output and notify users of their new passwords.
  5. When you are ready, shut down Firebird. Rename security3.fdb or move it another location; then rename the upgraded database to security3.fdb.
Prev: Legacy AuthenticationFirebird Documentation IndexUp: Compatibility IssuesNext: Local Connections to Superserver on Windows
Firebird Documentation IndexFirebird 3.0.2 Release NotesCompatibility Issues → Upgrading a v.2.x Security Database