Как установить firebird на windows 10

Installation drives

Note

You can mount a read-only database on a CD-ROM drive but you cannot run Firebird
server from one.

Installation script or program

Installing on Windows

The Firebird Guardian is a utility that monitors the server process and tries to
restart it if it terminates abnormally. The Guardian does not work with Firebird Classic
Server on Windows if run as an application. This is due to a known bug, which may be fixed
later. Currently the Firebird 2.5 installer doesn’t give you the option to include the
Guardian at all with a Classic Server, even if you install it as a
service.

The Guardian works correctly with Superserver, whether run as an application or as a
service.

If you run Firebird as a service on Windows 2000 or newer, the
Guardian is a convenience rather than a necessity, since these operating systems have the
facility to watch and restart services. It is recommended that you keep the Guardian
option on (if possible) in all other situations.

Installing on Linux and other Unix-like platforms

• If you have installed a Classic/SuperClassic Server on Linux/Unix or any Firebird
  server on Windows, it is possible to connect directly to the local server, without using
  a network layer. If you intend to use Firebird for this type of connection only, you can skip the “Pinging the server” section
  below.

• For information about using the NetBEUI protocol in an all-Windows environment,
  refer to the Network Configuration chapter in the
  Using Firebird manual sold by IBPhoenix, or consult the InterBase
  6 Operations Guide (http://www.ibphoenix.com/files/60OpGuide.zip).

• Firebird does not support IPX/SPX networks.

Pinging the server

ping localhost –or– ping 127.0.0.1

Checking that the Firebird server is running

On Linux or other Unix-like systems:

As a service.

On Windows server systems (NT, 2000/3/8, XP, Vista, 7):

As a service or as an application. Service is default and highly
recommended.

On Windows non-server systems (95, 98, ME):

As an application.

Use the top command in a command shell to inspect the
running processes interactively. If a Firebird Superserver is running, you should see a
process named fbguard. This is the Guardian
process. Further, there will be one main and zero or more child processes named
fbserver.

The following screen shows the output of top, restricted
by grep to show only lines containing the characters
fb:

frodo:/inkomend/firebird # top -b -n1 | grep fb
 2587 firebird  24   0  1232 1232 1028 S  0.0  0.3   0:00.00 fbguard
 2588 firebird  15   0  4124 4120 2092 S  0.0  0.9   0:00.04 fbserver
 2589 firebird  15   0  4124 4120 2092 S  0.0  0.9   0:00.00 fbserver
 2604 firebird  15   0  4124 4120 2092 S  0.0  0.9   0:00.00 fbserver
 2605 firebird  15   0  4124 4120 2092 S  0.0  0.9   0:00.02 fbserver
 2606 firebird  15   0  4124 4120 2092 S  0.0  0.9   0:00.00 fbserver
 2607 firebird  15   0  4124 4120 2092 S  0.0  0.9   0:00.00 fbserver

As an alternative to top, you can use ps
-ax or ps -aux and pipe the output to
grep.

For Classic Server, the process name is fb_inet_server. There will be one instance of this process
running for each network connection. Note that if there are no active connections, or if
there are only direct local connections, you won’t find fb_inet_server in the process list. fb_lock_mgr should be present though as soon as any kind of
Classic connection has been established.

For SuperClassic, the process name is fb_smp_server and it will visible as soon as the service is
started. SuperClassic, just like Superserver, does its own port-listening, so it will be
running even if there are no connections.

Other ways to test a Firebird server immediately after installation include
connecting to a database, creating a database, and launching the
gsec utility. All these operations are described later on in
this guide.

Open Control Panel -> Services (NT) or Control Panel -> Administrative Tools
-> Services (2000/3/8, XP, Vista, 7).

This illustration shows the Services applet display on Windows 2000. The
appearance may vary from one Windows server edition to another. Also, service names may
vary with the Firebird version.

You should at least find the Firebird server in the services listing. The Guardian
may or may not be running, depending on the choices you made during installation.

If Firebird is up and running as an application, it is represented by an icon in the
system tray:

A flashing icon indicates that the server is in the process of starting up (or at
least trying to do so). A red icon, or an icon with an overlying red stop sign, indicates
that startup has failed.

One way to make 100% sure if the server is running or not is to press Ctrl-Alt-Del
and look for the fbserver or fb_inet_server process (and possibly fbguard) in the task list.

On some occasions, you may need to start the Guardian or server once explicitly via
the Start menu even if you opted for “Start Firebird now” at the end of the
installation process. Sometimes a reboot is necessary.

If you’re desperately trying to start Firebird and nothing seems to work, ask
yourself if you’ve installed Firebird 2.5 (Super)Classic server with the Guardian option
enabled (the installation program doesn’t offer this possibility anymore, but there are
other ways). As said before, the combination (Super)Classic + Guardian currently doesn’t
work if Firebird runs as an application. Uninstall Firebird if necessary and reinstall
(Super)Classic without Guardian, or Superserver with or without
Guardian.

You can shut the server down via the menu that appears if you right-click on the
tray icon. Notice that this also makes the icon disappear; you can restart Firebird via
the Start menu.

In the case of Superserver you can also use a Control Panel applet to check and
alter the Firebird server status. Some available applets will be presented a little later
in this guide.

Windows

Linux and some other Posix clients

1. Look for libfbclient.so.2.5.n
   (n being the patch version number) in /opt/firebird/lib on the machine where the Firebird server
   is installed. Copy it to /usr/lib on the client
   (or /usr/lib64 if both server and client are
   64-bits).

2. Create chained symlinks using the following commands:

   ln -s /usr/lib/libfbclient.so.2.5.n
   /usr/lib/libfbclient.so.2

   ln -s /usr/lib/libfbclient.so.2
   /usr/lib/libfbclient.so

   …replacing 2.5.n with your version
   number, e.g. 2.5.0 or 2.5.3

   If you’re running applications that expect the legacy libraries to be present,
   also create the following symlinks:

   ln -s /usr/lib/libfbclient.so /usr/lib/libgds.so.0

   ln -s /usr/lib/libfbclient.so /usr/lib/libgds.so

3. Copy firebird.msg to the client machine, preferably into the
   /opt/firebird directory. If you place it
   somewhere else, create a system-wide permanent FIREBIRD environment
   variable pointing to the right directory, so that the API routines can locate the
   messages.

4. Optionally copy some of the Firebird command-line tools – e.g.
   isql – to the client machine. Note:
   always copy the tools from a Superserver kit, regardless of the architecture of the
   server(s) you’re planning to connect to. Tools from Classic distributions terminate
   immediately if they can’t find the libfbembed
   library (which is useless for network connections) upon program start.