existing security database on the Firebird 2.0 server, you should create a gbak backup of your old security.fdb (from v.1.5) or isc4.gdb (from v.1.0) using the old server's version of gbak and then restore least 4 Kb. The new security2.fdb will not work with a smaller page size. Warning A simple 'cp security.fdb security2.fdb' will make it impossible to attach to the firebird server ! Known Compatibility earlier than version 2.0 you should use gbak to back up your old security database. It is named security.fdb for Firebird 1.5 or isc4.gdb for a Firebird 1.0 installation. You can restore it later as security2

a single security database. This is located on the server in a normal Firebird database named security.fdb for Firebird 1.5 or security2.fdb for Firebird 2.0 onwards. The default locations for this file The solution is to use TCP local loopback. • Put an alias in aliases.conf for the path to your security.fdb, e.g. sec = C:\Program Files\Firebird\Firebird_1_5\security.fdb. • Call gsec using gsec -database

-user sysdba -password masterkey -database "localhost:C:\Program Files\Firebird \Firebird_1_5\security.fdb" (при необходимости измените путь) Firebird 1.5 Quick Start 14 Замечание • В Linux, лучше

Die Sicherheitsdatenbank wird auch mit dem neuen Kennwort aktualisiert. (/opt/firebird/security.fdb oder /opt/firebird/security2.fdb)  Das Skript muss als Root-Benutzer ausgeführt werden. Wenn

located in your Firebird installation directory. • Maybe your security database is a renamed security.fdb from Firebird 1.5. Of course this can't be the case immediately after installation. Someone (you

Firebird Installationsverzeichnis. • Womöglich ist Ihre Sicherheitsdatenbank eine umbenannte security.fdb von Firebird 1.5. Dies kann natürlich nicht der Fall unmittelbar nach der Installation sein. Irgendjemand