- •Firebird 2 Migration & Installation
- •Table of Contents
- •Known Compatibility Issues
- •Two Changes to Note in V.2.1
- •The FIREBIRD Variable
- •Security in Firebird 2 (All Platforms)
- •Trusted Authentication on Windows
- •SQL Migration Issues
- •Changed Ambiguity Rules in SQL
- •Multiple Hits to Same Column Now Illegal
- •Query Plans
- •PSQL
- •Configuration Parameters
- •Command-line Tools
- •Change to gbak -R Semantics
- •Performance
- •Firebird API
- •Windows-Specific Issues
- •Windows Local Connection Protocol with XNet
- •Client Impersonation No Longer Works
- •Interactive Option Added to instsvc.exe
- •INSTALLATION NOTES
- •Choosing a Server Model
- •Database Compatibility Among Models
- •Full Servers
- •Embedded
- •Windows Installs
- •Choosing an Installation Method
- •READ THIS FIRST!
- •Naming databases on Windows
- •Other Pre-installation Issues
- •Installation of Microsoft system libraries
- •Zip kit install
- •Running Firebird as a service with a special user name
- •Installing Multiple Servers
- •Installing under 64-bit versions of Windows
- •Installation of fbclient.dll
- •Registry Key
- •Supporting legacy applications and drivers
- •InstClient.exe Tool
- •Cleaning up release candidate installs
- •Using the Win32 Firebird Installer
- •Uninstallation
- •Installing Superserver from a zip kit
- •Installing Classic Server from a zip kit
- •Simplified setup
- •Uninstallation
- •Other Win32 Issues
- •Updated Notes for Windows Embedded
- •Registry
- •Database Access
- •Authentication and Security
- •Compatibility
- •Installing an Embedded Server Application
- •Installation Structure Examples
- •POSIX Platforms
- •READ THIS FIRST
- •Setting Linux to Use the Old Threading Model
- •Installing on Linux
- •RPM Installer
- •Installing the Tarball
- •Testing your Linux installation
- •Step 1 - Accessing a database
- •Step 2 - Creating a database
- •Utility Scripts
- •Linux Server Tips
- •"Embedded" or direct access to database files
- •Uninstalling on Linux
- •Uninstalling an RPM package
- •Uninstalling a tarball installation
- •Solaris
- •MacOS X
- •FreeBSD
- •Debian
INSTALLATION NOTES
READ THIS FIRST
• You will need to be root user to install Firebird.
•
Note
libstdc++.so.5
Installation on Linuxen requires a glibc package installed that is equal to or greater than glibc-2.2.5. However, to enable support for some older distros, the generic binaries are built in a compiler environment that will ensure compatibility with the v.2.2.5 kernel. For this reason, the runtime library libstdc++.so.5 must be present in your system before you attempt to install Firebird. There are various ways to achieve it, as follows:
-by installing a compat-glibc package (RedHat, CentOs, OpenSuse, Debian) or a libstdc++5 package (Mandriva)
-by using a Firebird rpm (or other, appropriate package type) provided by your distro instead of the generic one provided by the Firebird Project
-by compiling Firebird yourself, on the same system that you are going to run it on!
•Do not try to use rpm --update to bring any existing Firebird package installation up to date. The Firebird packages do not support it.
•If you are installing Superserver on a Linux that supports the “new POSIX threading library ” (NPTL) then choose the NPTL build of Firebird. Most distros with the 2.6 kernel are built with NPTL enabled; some with later 2.4 kernels also enabled it, but it may be wise to prepare to revert to the regular build and set up to export the LD_ASSUME_KERNEL=2.2.5 variable if the 2.4 implementation of the NPTL causes problems. Details for doing this follow below.
•64-bit builds are available for both Classic and Superserver. These should be installed only on a 64-bit Linux system. NPTL support is native on 64-bit Linux.
Setting Linux to Use the Old Threading Model
If the NPTL causes problems for SuperServer and locally compiled programs, including utilities such as gbak throwing a Broken Pipe error, you can try to solve the problem by forcing Linux to use the old threading model. To fix.-
1.In /etc/init.d/firebird
LD_ASSUME_KERNEL=2.2.5 export LD_ASSUME_KERNEL
That takes care of the server instance.
2.You need to have the LD_ASSUME_KERNEL environment variable set up within the local environment as well, so add the following to /etc/profile, to ensure every user picks it up for the command line utilities.
after
25