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