Pervasive PSQL v9.6 - README
General Release - April 2007

Contents


This document contains the following topics:

General Information

Welcome to the General Release of Pervasive PSQL v9.6.

This release delivers new features and functionality to Pervasive PSQL as described in New Features and Enhancements.

Note  The Installation Notes section contains important information to help you install successfully. Please read this section before attempting to install Pervasive PSQL v9.6 or alter your existing configuration.

Installation Notes

After reading these notes, see the portable document format (PDF) book Getting Started with Pervasive PSQL for installation steps.

Compatibility with Other Releases

This release supports the use of older clients from the previous releases Pervasive PSQL v9, and Pervasive PSQL v9 SP1, and Pervasive PSQL v9 Service Pack 2 with the Pervasive PSQL v9.6 Server.

Pervasive recommends that you use client requesters that are the same version as the database engine. If you choose, you may use a client requester that is an older version than the database engine with which it interacts. In some situations, depending on the type of SDK access method used by your application, an older version requester will not work with the database engine. Your application will be unable to communicate with the database engine. For those situations, you must use client requesters that are the same version as the database engine.

Client requesters that are a newer version than the database engine may or may not function correctly. Pervasive does not guarantee that newer versions of client requesters will function correctly with older versions of the engine. Therefore, Pervasive recommends that you avoid the use of newer version client requesters with an older engine.

Using Other Data Management Products

This release supports Pervasive AuditMaster v6.3, DataExchange v2.8, and Backup Agent v1.1.

Pervasive PSQL v9.6 will not install in an environment where AuditMaster v6.2, DataExchange v2.7, or Backup Agent v1.0 are installed. The steps below explain how to upgrade Pervasive.SQL V8.x to Pervasive PSQL v9.6 in an environment with prior versions of other Pervasive data management products.

Before upgrading, ensure that no user or application is using the database engine. Any changes to your data files are not captured, audited, or put into continuous operations during the upgrade process. For DataExchange, disable any replication schedules and ensure that no replication sessions are running during the upgrade.

Step
Action
1.
Modify the Registry and add a key that will allow the upgrade.
  • For AuditMaster, add this key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\AuditMaster Server\v9_upgrade]
  • For DataExchange, add this key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Pervasive.SQL Replication\v9_upgrade]
  • For Backup Agent, add this key:
[HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Backup Agent\v9_upgrade]
Note: Each product requires its own key. For example, if you are using all three products, add all three keys.
If you prefer not to edit the Registry manually, contact Pervasive Support and request a Registry update file (.reg file). The Support representative will advise you on using the file. See www.pervasive.com/company/contact/index.asp for contact information.
2.
Upgrade Pervasive.SQL V8.x to Pervasive PSQL v9.6. See Getting Started with Pervasive PSQL (Server Edition).
3.
Update AuditMaster v6.2 to Pervasive AuditMaster v6.3
Update DataExchange v2.7 to DataExchange v2.8
Update Backup Agent v1.0 to Backup Agent v1.1
These updates are available for download from the Pervasive web site at http://www.pervasive.com/support/updates/

Server and Client Installs

The Pervasive PSQL Server and Client installations are separate in Pervasive PSQL v9.6. You can no longer install clients from a server installation unless you add the client install manually to your installed Pervasive PSQL v9.6 server installation.

Instead, use the separate Client installation program provided on the installation media or on the download Web page.

To add the client install image to a server install

  1. Install the Pervasive PSQL v9.6 Server.
  2. Make a directory named CLIENTS in the folder to which you installed Pervasive PSQL v9.6. For example, if you installed to the default location, this would be C:\PVSW\CLIENTS.
  3. Copy the contents of the client install folder to the location specified in step 2.
  4. Grant share access to the C:\PVSW\CLIENTS directory so that users can access the setup.exe program located there.

Note the following when installing:

Windows Vista

Windows Vista checks all installation executables to verify the authenticity of the executable. The Pervasive PSQL installation program is now digitally signed. As a result, when you install Pervasive PSQL the Vista execution authentication shows that the executable is from Pervasive Software.

Types of Users

Windows Vista uses two main types of user accounts: standard users and administrators. The permissions differ for these two types of users.

If a standard user needs to perform a task that requires additional privileges, Vista prompts (run as administrator) for an administrator password. Vista includes a built-in administrator, admin, whose account is disabled by default.

The following behavioral differences with Pervasive PSQL occur if you are logged on as a standard user instead of an administrator:

Communications Protocols

Pervasive PSQL supports Internet Protocol (IP) v4, not IP v6.

Security and File Permissions

Dbnames.cfg and pvsw.log can be written to by all users; neither file is virtualized on Vista. Pervasive PSQL databases are accessible to all user regardless of who creates the database. Vista still allows you to create system DSNs and user DSNs. User DSNs are not accessible by all users.

The database engine files w3dbsmgr and ntdbsmgr are added to the firewall access list. The installation of Windows Vista enables the firewall by default. With the firewall enabled, users cannot access the database engine unless certain engine files are added to the firewall access list.

Configuration Settings

The registry configuration settings allow full access to all users. Pervasive PSQL configuration settings are persistent for all user types on Vista.

Running Workgroup Engine or Cache Engine As a Service

If a user starts the Workgroup Engine or Cache Engine in a Terminal Services environment or by switching users through fast-user switching, other users on the system cannot access that engine nor can they start their own copy of the engine.

Status code 3032 results if a second user attempts to access another user's engine through the transactional interface: "Unable to connect to local engine. Possibly an engine has been started by another user on this machine in a non-elevated mode. Other users will not be able to connect to that engine."

If it is desirable to have multiple users accessing a local engine, then start that engine as a service. Ensure that you are logged on as an administrator, then complete the following steps.

  1. Determine which engine you want to run as a service: Workgroup or Cache. You cannot run them both concurrently.
  2. Stop the current engine: right-click on the tray icon then click stop.
  3. Open a DOS prompt and change directory to c:\pvsw\bin.
  4. Perform step 5 or step 6 based on the engine you want to run as a service.
  5. Type the following command to create a service for the Workgroup Engine:
  6. psc create "psqlWGE" "Pervasive PSQL Workgroup Engine" own auto "c:\pvsw\bin\w3dbsmgr.exe service srde"

  7. Type the following command to create a service for the Cache Engine:
  8. psc create "psqlCE" "Pervasive PSQL Cache Engine" own auto "c:\pvsw\bin\w3dbsmgr.exe service btrv"

  9. Type one of the following commands to start the engine service:
  10. psc start "psqlWGE"

    or

    psc start "psqlCE”

See also “psc” in the chapter “Command Line Interface Utilities” in Pervasive PSQL User’s Guide.

Uninstalling the Product and the Service

If you run the Workgroup Engine or Cache Engine as a service but later decide to uninstall the engine, remember to delete the service after you uninstall the product.

This applies whether you use a Pervasive PSQL utility, third-party utility, or the operating system to set up the Workgroup Engine or Cache Engine as a service. Since the Pervasive PSQL installation program did not install the service, the Pervasive PSQL uninstall program is unaware of its existence.

You can delete a service through the operating system Service Manager or with a third-party utility.

New Features and Enhancements

Pervasive PSQL v9.6 includes the following new features and enhancements.

Feature
Description
Windows Vista support
The Pervasive PSQL Server, Workgroup, and Client products can be installed and used under Windows Vista.
Java Runtime Environment (JRE) 6 installed with Pervasive PSQL
The JRE 6, which is Vista compatible, is installed with the Pervasive PSQL products

Environments Supported

Server Engine

The Pervasive PSQL v9.6 Server is supported on the following.

Workgroup Engine

The Pervasive PSQL v9.6 Workgroup is supported on the following.

Clients

The Pervasive PSQL v9.6 client is supported on the following.

Known Issues

This section lists the known issues for Pervasive PSQL v9.6.

Windows Vista

Documentation Notes

The documentation is provided in three different formats: JavaHelp, HTMLHelp, and portable document format (PDF).

The PDF files reside on the installation media and are not installed. In some instances, the Acrobat Reader plugin for browsers does not render the PDF documentation correctly. You may notice gaps on pages or pages that appear to be missing. We recommend that you view the PDFs with Adobe Reader, not in a browser. The Reader is free and available as a download from www.adobe.com.

The JavaHelp and HTMLHelp (CHM) formats are installed by default with the product. The JavaHelp is installed under the Bin\Plugins directory (by default, C:\PVSW\Bin\Plugins). The HTMLHelp is installed under Program Files\Common Files\Pervasive Software Shared\Doc.

The Java Runtime Environment (JRE) is required to use the Javahelp documentation. Ensure that the system variables on your operating system are correctly set to include the location of the JRE. Certain platforms may not include the location of the JRE bin directory in the PATH variable. Verify the specific location of the JRE on your operating system before adding the location to the PATH variable.

Technical Support

You may obtain technical support from the following Web-based support options:

If you require something other than what Web-based support options provide, contact Pervasive Support by phone:

For community technical support and discussions about Pervasive products in general:

For information on updates and Service Packs:

Useful Links

Disclaimer

PERVASIVE SOFTWARE INC. LICENSES THE SOFTWARE AND 
DOCUMENTATION PRODUCT TO YOU OR YOUR COMPANY SOLELY 
ON AN "AS IS" BASIS AND SOLELY IN ACCORDANCE WITH 
THE TERMS AND CONDITIONS OF THE ACCOMPANYING 
LICENSE AGREEMENT.  
Copyright © 2007 Pervasive Software Inc.  
All Rights Reserved.  

Pervasive Software Inc.
http://www.pervasive.com
12365 Riata Trace Pkwy, Bldg B
Austin, TX 78727 USA
Voice: (512) 231-6000
Fax: (512) 231-6010
Online Pervasive Contacts

*** END OF README ***