Upgrading the Pervasive.SQL Server Components

---

The Pervasive.SQL installation package is provided in the following form:

Operating System	Package Name
Linux	Pervasive.SQL-8.00-109.000.i486.rpm1

1 The Package Name listed here is only an example. Verify the actual name for the version you are installing. The Package Name is listed in the README file.

---

Note
To install this package, you must be logged in as root. If you are installing from the CD, you must be at the CD root directory.

---

Upgrade Procedure for Pervasive.SQL 2000i (SP3 or SP4)

   To upgrade Pervasive.SQL V8 on a Linux machine:

1. Log in as the root user
2. Assuming the new Pervasive.SQL V8 RPM package is in the current directory, issue the following command.

   rpm -Uvh <Pervasive.SQL-8.00-109.000.i486.rpm>  
   

---

Note
You must substitute the Package Name listed in your product's README file for the variable <Pervasive.SQL-8.00-109.000.i486.rpm> to complete the installation.

---

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

3. The package script installs the product and performs other tasks as noted in Installation Information .

---

Note
If you had any trouble with installation, see Chapter 21, Troubleshooting After Installation.

---

Upgrade Procedure for Versions Older than Pervasive.SQL 2000i (SP3)

   To upgrade Pervasive.SQL V8 on a Linux machine:

1. Log in as the root user
2. Uninstall the previous Pervasive.SQL 2000 package.

   rpm -e 'Pervasive.SQL-server' 
   

---

Note
You cannot use the rpm -Uvh command to upgrade the package because the package name has changed.

---

3. Assuming the new Pervasive.SQL V8 RPM package is in the current directory, issue the following command.

   rpm -ivh <Pervasive.SQL-8.00-109.000.i486.rpm>  
   

---

Note
You must substitute the Package Name listed in your product's README file for the variable <Pervasive.SQL-8.00-109.000.i486.rpm> to complete the installation.

---

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

4. The package script installs the product and performs other tasks as noted in Installation Information .

---

Note
If you had any trouble with installation, see Chapter 21, Troubleshooting After Installation.

---

Installation Information

For all installations, 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
• Stops Pervasive.SQL daemons if they are running
• Applies a 10 user, 30 day limited license
• Launches both Pervasive.SQL daemons - mkded and sqlmgr
• Creates a new ODBC DSN (data source name) for the DEMODATA test database
• Creates a new Samba share PSQLDATA if Samba configuration file is found
• Creates startup/shutdown scripts for Pervasive.SQL daemons

After the installation script is finished, you should verify that both engines (mkded - transactional, sqlmgr - relational) are running with the Linux ps utility:

Type the following at the command line:

ps -e | egrep 'mkded|sqlmgr' 

On Linux, you can verify that the RPM packager upgraded the Pervasive.SQL package by issuing the following at the command prompt:

rpm -q 'Pervasive.SQL' 

User Count License

It is highly recommended that you go through the README file to find out the latest information on updating your user count information.

Once you have completed installation, you may need to update your user count license by using the clilcadm utility. It can be done anytime before using Pervasive.SQL from a client. Information about how to do this can be found in Pervasive.SQL User's Guide (see License Administrator ). Detailed information about clilcadm can also be found in the man pages and in the documentation for clilcadm located in the "Linux Supplementary Documentation" section of Pervasive.SQL User's Guide.

---

Note
You must be a member of group pvsw to run the clilcadm utility. See Pervasive.SQL Account Management on Linux for more information.

---

Accessing README file information

It is highly recommended that you go through the README file to find out the latest changes and additions to Pervasive.SQL V8.