Installing Pervasive PSQL Vx Server Using RPM

In all cases, the yy.yy designates a release number and zzz.zzz designates a build number. Refer to the distribution media for the actual name of the package.

Installation is categorized as either first time, in which no previous version exists, or upgrade, in which a previous version exists.

•

First Time Installation

•

Upgrade Installation

First Time Installation

The package manager copies all necessary files onto disk (default location is /usr/local/psql) and runs a post-installation script which performs the following tasks:

•

Creates user psql and group pvsw

•

Sets user:group ownership to psql:pvsw for the installed files

•

Applies a trial license

•

Creates a new ODBC DSN (data source name) for the DEMODATA test database

•

If Samba configuration file is found

•

Creates a new Samba share PSQLDATA

•

Creates a new Samba share PVPIPE$

•

Creates startup/shutdown scripts for Pervasive PSQL Vx Server daemons

•

Launches the Pervasive PSQL Vx Server daemon (mkded)

►

To install Pervasive PSQL Vx Server using RPM

Note: If you have a previous version of Pervasive PSQL Vx Server on your Linux machine, see Upgrade Installation.

Assuming the RPM package is in the current directory, enter the following command:

rpm -ivh <Vx_Server_Package_Name>

Note: Refer to Vx Server Package Names - RPM for the package name to use. You must include the appropriate release and build number information to perform the installation. Verify the complete package name from the distribution media.

If the RPM package is in another directory, preface the package name with a path.

Upgrade Installation

If you have a previous version of Pervasive PSQL Vx Server already installed, you must uninstall that product and then install the Pervasive PSQL Vx Server product.

See Uninstalling Pervasive PSQL Vx Server for Linux for information on uninstalling Pervasive PSQL Vx Server.

Installing Pervasive PSQL Client for Linux - RPM

The name of the Pervasive PSQL Client installation package conforms to the following conventions:

Table 20

Client Package Names - RPM

Installation Type

Package Name

Client 64-bit

Pervasive.SQL-Client-Core-yy.yy-zzz.zzz.x86_64.rpm

Client 32-bit

Pervasive.SQL-Client-yy.yy-zzz.zzz.i486.rpm

In all cases, the yy.yy designates a release number and zzz.zzz designates a build number. Refer to the distribution media for the actual name of the package.

Installation is categorized as either first time, in which no previous version of the product exists, or upgrade, in which a previous version of the product exists.

•

First Time Installation

•

Upgrade Installation

Note: The Client 64-bit installation does not include certain utilities, documentation, or SDK components. To install them, you need to install both the Client 64-bit and Client 32-bit products. Because this is the same as for the Pervasive PSQL Client for Windows, see Installing the Pervasive PSQL Client for Windows for details.

First Time Installation

►

To install Pervasive PSQL Client Using RPM

Assuming the RPM package is in the current directory, execute the following command.

rpm -ivh <Client_Package_Name>

Note: Refer to Client Package Names - RPM for the package name to use. You must include the appropriate release and build number information to perform the installation. Verify the complete package name from the distribution media.

If the RPM package is in another directory, preface the package name with a path.

Upgrade Installation

If you have a previous version of Pervasive PSQL Client already installed, you must uninstall it and then install the Client.

See Uninstalling Pervasive PSQL Vx Server for Linux for information on uninstalling Pervasive PSQL.

Installing Pervasive Backup Agent for Linux - RPM

Pervasive Backup Agent is an optional installation. The utility provides an alternative method for implementing Continuous Operations. See Pervasive Backup Agent Guide for details.

The name of the Pervasive Backup Agent installation package conforms to the following conventions:

Table 21

Package Names for Pervasive Backup Agent - RPM

Installation Type

Package Name

64-bit

Pervasive-Backup-Agent-yy.yy-zzz.zzz.x86_64.rpm

32-bit

Pervasive-Backup-Agent-yy.yy-zzz.zzz.i486.rpm

In all cases, the yy.yy designates a release number and zzz.zzz designates a build number. Refer to the distribution media for the actual name of the package.

Caution: Installation of Backup Agent stops and then restarts Pervasive PSQL services, so your database is briefly shut down.

If you have a previous version of Pervasive Backup Agent already installed, you must uninstall it before installing it again.

►

To install Backup Agent using RPM

Change directories to the location of the RPM package

Issue the following command, replacing the package name used here with the correct name:

rpm -ivh <Backup_Agent_Package_Name>

Note: If you are installing to a non-RPM based Linux installation such as Slackware, you need to add the --nodeps option so that the package manager does not check for RPM dependencies, which your system does not have. For example, rpm -ivh --nodeps <package>.

The package scripts install the product and perform other tasks required for installation. If successful, the prompt displays the following message:

Install has successfully completed.

After installation, you can verify that the databse engine is running by using the Linux ps utility at the command prompt:

ps -e | egrep mkded

To use Pervasive Backup Agent on Linux, see the topic “Using Backup Agent on Linux” in Pervasive Backup Agent Guide.

Verifying RPM Installation

You can verify that RPM installed the Backup Agent package by issuing the following case-sensitive command at a prompt:

rpm -q ‘Pervasive-Backup-Agent’

When successful, a specific version should be returned. For example:

Pervasive-Backup-Agent-yy.yy-zzz.zzz

The yy.yy designates a release number and zzz.zzz designates a build number. Refer to the distribution media for the actual name of the package.