| Subject | RE: [firebird-support] size specification either missing or incorrect |
|---|---|
| Author | Helen Borrie |
| Post date | 2008-01-16T22:05:46Z |
At 08:01 AM 17/01/2008, you wrote:
You *can* configure Fb 1.5 to run alongside another Firebird or Interbase server but this requires manual configuration of the service port to make Firebird use a different port; and all client calls (including service manager ones) will need the port included in the server element of the connection string; and more. You can study this in detail in Chapter 9 of the release notes, "Configuring the Port Service on Client and Server".
Your client also must use the appropriate *Firebird* client: there are several necessary things that the IB 5 client library doesn't support, or supports differently. If you need to, you can rename fbclient.dll to gds32.dll.
In case you haven't looked closely at the migration issues, you need to be aware that, while restoring an IB 5 database under Fb 1.5 will make it an ODS 10 database, it does not convert any data into the formats or types assumed for an ODS 10 database. One example is that your DATE fields are not DATE fields; another is that fixed numerics defined with precision higher than 9 will still be DOUBLE PRECISION (the ODS 9 workaround used to provide higher-precision support for DECIMAL and NUMERIC types in IB 5.x and below).
There are ways (good and bad) to migrate your data and fix your application code but, until you do, your database will be a "Dialect 1" database and all client connections will need to be set to SQLDialect=1. (Native ODS 10+ databases are Dialect 3.)
You can study the issues by reading the IB6 Beta Migration Guide (pick up a link in the Firebird documentation index, at http://firebirdsql.org?op=doc#category_9 ). The database conversion techniques described in that document are unsound so, if/when you're ready to convert, ask here and/or in firebird-tools for advice.
./heLen
>Success I think as I can now straight away see the 3 .fdb files: S6.fdb,Of course not!
>s6A.fdb and S6B.fdb !
>
>So, it looks you were right with your last suggestion, but also it looks IB
>can't be running when doing a FB restore.
You *can* configure Fb 1.5 to run alongside another Firebird or Interbase server but this requires manual configuration of the service port to make Firebird use a different port; and all client calls (including service manager ones) will need the port included in the server element of the connection string; and more. You can study this in detail in Chapter 9 of the release notes, "Configuring the Port Service on Client and Server".
Your client also must use the appropriate *Firebird* client: there are several necessary things that the IB 5 client library doesn't support, or supports differently. If you need to, you can rename fbclient.dll to gds32.dll.
In case you haven't looked closely at the migration issues, you need to be aware that, while restoring an IB 5 database under Fb 1.5 will make it an ODS 10 database, it does not convert any data into the formats or types assumed for an ODS 10 database. One example is that your DATE fields are not DATE fields; another is that fixed numerics defined with precision higher than 9 will still be DOUBLE PRECISION (the ODS 9 workaround used to provide higher-precision support for DECIMAL and NUMERIC types in IB 5.x and below).
There are ways (good and bad) to migrate your data and fix your application code but, until you do, your database will be a "Dialect 1" database and all client connections will need to be set to SQLDialect=1. (Native ODS 10+ databases are Dialect 3.)
You can study the issues by reading the IB6 Beta Migration Guide (pick up a link in the Firebird documentation index, at http://firebirdsql.org?op=doc#category_9 ). The database conversion techniques described in that document are unsound so, if/when you're ready to convert, ask here and/or in firebird-tools for advice.
./heLen