Scribd
Upload
40 views3 pages

FB 5 Migrationguide

Uploaded by

Branko Petrović
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
40 views3 pages

FB 5 Migrationguide

Uploaded by

Branko Petrović
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Chapter 1. Manual installation of Firebird 5.

0 in Windows

plugins directory by default. fbclient.dll version 4.0 and higher uses


plugins/chacha.dll by default, if this plugin is present. Missing plugins are ignored.

However, there is an important feature. fbclient.dll looks for the file


firebird.conf in its directory, and if it is missing, it tries to find it in the directory
above. The directory where firebird.conf is found is the root directory - from
which all other known relative paths (plugins, intl) are counted.

This behavior can play a cruel joke on you. The thing is that the 64-bit installer
places the 32-bit library fbclient.dll in the folder $(fbroot)/WOW64. If you want to
use the library from this directory, you may get the following error message

Error loading plugin ChaCha.


Module C:\Firebird\5.0\plugins/ChaCha exists but can not be loaded.
unknown Win32 error 193.

In this case, the 32-bit fbclient.dll tried to load the 64-bit ChaCha plugin.

To fix this error, just put the file firebird.conf in the folder $(fbroot)/WOW64.

The library fbclient.dll, as well as other files of the client library, must be located either next to
the application, or in one of the directories where the search is performed, for example added to
PATH or the system directory for placing public libraries (system32 or SysWOW64).

Important
Placing the client library in PATH may interfere with other applications that require

 a client library of a different version or a different server. Therefore, if it is


assumed that the application should work independently of other applications
with a specific version of the client, then the client files should be placed in the
application folder, and not add this path to PATH.

1.4.1. Using instclient

To deploy the Firebird client library in the Windows system directory, use the command

instclient install fbclient

Important

 The instclient utility does not copy any files to the system directory except
fbclient.dll.

1.5. Installing the embedded version


Starting from version Firebird 3.0, the embedded version is not distributed separately. You can use
the same set of files as both a network server and an embedded server. But, if you need an

12
Chapter 1. Manual installation of Firebird 5.0 in Windows

embedded set of minimal size, then the structure of files and directories for Firebird 5.0 embedded
is as follows:

• intl

◦ fbintl.conf

◦ fbintl.dll

• plugins

◦ engine13.dll

• firebird.conf

• icudt63l.dat

• fbclient.dll

• ib_util.dll

• icudt63.dll

• icuin63.dll

• icuuc63.dll

• msvcp140.dll

• vcruntime140.dll

• vcruntime140_1.dll

• firebird.msg

If necessary, you can also copy the executable files of the utilities fbsvcmgr.exe, fbtracemgr.exe,
gbak.exe, gfix.exe, gstat.exe, isql.exe, nbackup.exe. If you are going to use gbak with the -zip switch,
then you will also need the library zlib1.dll.

Note
For those who are migrating from Firebird 2.5, you should consider 2 points:

• Instead of a single library fbembed.dll, several files are required, and the file
fbclient.dll cannot be renamed. Access components must use the library
 fbclient.dll as the entry point.

• In the configuration file firebird.conf, you should change the value of the
parameter ServerMode to SuperClassic or Classic so that on one computer you
can connect to the same database from different applications using embedded
(behavior of Firebird 2.5 embedded by default).

13
Chapter 2. Converting the database to the new format

Chapter 2. Converting the database to the


new format
Firebird 5.0 databases have ODS (On-Disk Structure) 13.1. To make Firebird 5.0 work with your
database, you need to bring it to the native ODS. Usually this is done using the gbak tool. However,
do not rush to make a backup of your database and restore it with the new ODS - first you need to
eliminate possible compatibility issues.

2.1. List of incompatibilities at the SQL language level


SQL language compatibility issues are possible both for the objects of the database itself (PSQL
procedures and functions), and for the DSQL queries used in your application.

To detect SQL language compatibility issues for database objects, the following method is
recommended. Extract the metadata of the database into a script on the old version of Firebird.

isql <database> -x -o create_script.sql

Uncomment the CREATE DATABASE statement inside the script, make the necessary changes, and
try to create a new database from the script in Firebird 5.0:

isql -i create_script.sql -o error.log -m

where, the -i key is the input file of the script; the -o key is the output file of messages; the -m key
makes isql output error messages to the output message file.

Next, look at the file error.log for errors, and if they are found, change the metadata in the original
database. Repeat the algorithm described above until all errors are eliminated. After that, you can
safely do backup/restore.

Next, we will list some of the most common compatibility issues at the SQL level, which you can fix
before moving to the new ODS. You can read the full list of incompatibilities in Release Notes 5.0 in
the chapter "Compatibility Issues". When migrating from 3.0, you should also familiarize yourself
with the chapter of the same name in Release Notes 4.0, and when migrating from 2.5 - Release
Notes 3.0.

2.1.1. New reserved words

Check your database for new reserved words in identifiers, columns, and variables. In the first SQL
dialect, such words cannot be used at all (you will have to rename them), in the third - they can be
used, but must be enclosed in double quotes.

You can find the list of new keywords and reserved words in the Release Notes 3.0 and 4.0 in the
chapter "Reserved Words and Changes". Keywords can be used as identifiers, although this is not
recommended.

14

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy