Before You Install Pervasive PSQL for Linux

Before You Install Pervasive PSQL for Linux

Before installing or upgrading Pervasive PSQL Server or Client, review the following information:

•

System requirements listed on the Pervasive Software Web site for Pervasive PSQL v11 SP3.

•

Chapter 2, Preparing to Install Pervasive PSQL– This chapter provides important information including platform specific notes.

•

Release Notes – The release notes are located in readme_psql.htm on the distribution media and contain late-breaking news that may not be included in the user documentation.

You must be logged in as root to install any of the products. If you are installing from the CD, you must be at the CD root directory.

If you have any trouble with an installation, see Troubleshooting After Installation.

If you are planning to access the Pervasive PSQL transactional interface across a network from a Windows-based client using drive mappings, we recommend that the Samba package be installed on the server. Please refer to the Samba Web site, http://www.samba.org, for installation and configuration instructions.

After installing Pervasive PSQL Server, review Supported Path Formats for Samba for information regarding Samba’s path configuration.

The Linux client can be installed on a Linux machine with no Pervasive PSQL products currently installed, or on a Linux machine with a Pervasive PSQL v11 SP3 Server engine installed.

If your database server engine does not match certain installation requirements, your applications may receive the following status code: “status 3031: Linux requester cannot connect to this server.” This status code indicates client/server incompatibility. In some cases, you may receive a permissions error status instead: “94: The application encountered a permission error.”

The installation scripts perform the following tasks:

•

Verify necessary permissions to complete install

•

Create user psql and group pvsw (if they do no exist)

•

Sets user:group ownership to psql:pvsw for the installed files (if not already set)

Full Installations

Pervasive PSQL offers full installations of both the RPM and TAR Linux packages. A full installation includes the necessary engine and client files, utilities, and the complete user documentation. A full installation does not include the word “full” in the package name.

The following table outlines the installation packages.

Table 9

Full and Client Linux Installations

Pervasive PSQL Product

Installation Type

Engine and client files, utilities, and documentation

Engine and client files, utilities, and documentation

Client files, utilities, and documentation

1 Because of the minimal files included in the 64-bit client, the installation package name includes the word “core.”

Notes for 64-bit Distributions

Note that, by default, certain 64-bit Linux distributions support only 64-bit components and executables. The distribution media for such distributions include the 32-bit libraries, but they are not installed by default.

Pervasive PSQL supports 64-bit editions of Linux distributions, but also requires certain 32-bit libraries. If you use a 64-bit Linux distribution, verify whether the 32-bit libraries are installed by default. If not, use the following table to determine the 32-bit libraries and other components required for Pervasive PSQL.

Pervasive PSQL Product

32-bit Components Required From Linux 64-bit Distributions

•

•

•

The Pervasive PSQL installation RPM and TAR files check for the existence of the 32-bit GLIBC and LIBSTDC++ libraries. If these libraries are not present, the Pervasive PSQL installation stops and displays a message. To install Pervasive PSQL, you must first install glibc.i686 and libstdc++.i686.

The Pervasive PSQL installation RPM and TAR files also check for the existence of 32-bit GTK. If GTK is not present, Pervasive PSQL displays a warning message. The message informs you that PCC, DDF Builder and GUI Phone Authorization utilities will not function until 32-bit GTK is installed. The Pervasive PSQL installation continues and completes after displaying the message.

To ensure that PCC, DDF Builder and GUI Phone Authorization utilities work, install the following Linux packages:

•

•

PackageKit-gtk-module.i686

•

libcanberra-gtk2.i686

•

gtk2-engines.i686.

yum install gtk2.i686 PackageKit-gtk-module.i686 libcanberra-gtk2.i686 gtk2-engines.i686

Note that, except for the three utilities just mentioned, Pervasive PSQL is functional even if the 32-bit GTK is not present. That is, the database engine is functional, all command line utilities work and the Pervasive PSQL libraries are present and accessible by your applications. Your client applications should still function as long as they do not require the 32-bit GTK.

•

•

The Pervasive PSQL installation attempts to configure Samba. However, by default on certain 64-bit Linux distributions, Samba is only partially installed and is not enabled.

You may ignore installation errors pertaining to creating the PSQLDATA Samba share (the smb.conf file exists, but nothing is there to support it). The errors are benign and Pervasive PSQL functions normally.