2004-12-19 17:16:06 +01:00
|
|
|
You can't use pre-2.0 security database in firebird 2.0 or higher directly.
|
2005-02-24 13:24:38 +01:00
|
|
|
If you try to put old security.fdb into firebird's new home directory with
|
|
|
|
new (security2.fdb) name, you will get a message - cannot attach to password
|
|
|
|
database. That's OK and is by design. In order to be able to use old database,
|
|
|
|
you must run appropriate upgrade script - security_database.sql. To do so:
|
2004-12-19 17:16:06 +01:00
|
|
|
1. Put your old security database in some known to you place (not new home
|
|
|
|
directory). Always have a copy of it!
|
2005-02-24 13:24:38 +01:00
|
|
|
2. Start firebird using it's new, native security2.fdb.
|
2006-03-06 11:53:55 +01:00
|
|
|
3. Convert your old security database to ODS11 (i.e. backup and restore it
|
|
|
|
using gbak from firebird 2.0). Without this step you will get failure running
|
|
|
|
security_database.sql!
|
|
|
|
4. Connect to restored database as SYSDBA and run the script.
|
|
|
|
5. Stop firebird.
|
|
|
|
6. Copy upgraded database to firebird's home directory (as security2.fdb).
|
2006-03-15 18:23:07 +01:00
|
|
|
7. Start firebird.
|
2004-12-19 17:16:06 +01:00
|
|
|
|
|
|
|
Now you should be able to connect to firebird 2.0 server using your old
|
2006-03-15 18:23:07 +01:00
|
|
|
logins and passwords.
|