Pervasive PSQL v11 Release Notes
General Release—September 2010

Contents

Welcome to the General Release of Pervasive PSQL v11.

This file contains the following topics:

Overview

The General Release includes the following:

Platforms Supported

The following operating systems in both 32-bit and 64-bit editions are supported for this General Release:

Update all operating systems to their latest service packs.

Third-Party Certification

For information related to third-party certification for Pervasive PSQL v11, refer to the Pervasive Software web site for detailed status information.

Product Authorization

Product authorization is a license validation process that verifies the copy of Pervasive PSQL v11 is legitimate, correctly licensed, and on the appropriate hardware and software platform. Product authorization is required for Pervasive PSQL v11 Server and Workgroup products.

Product Authorization on Windows

On Windows, product authorization is required for Pervasive PSQL Server or Workgroup. Product authorization can be performed during installation or using the license administrator utility after installation. To authorize Pervasive PSQL v11 during installation an Internet connection is required.

Product Authorization on Linux

On Linux, product authorization is required for Pervasive PSQL Server on Linux and must be performed using the license administrator utility after installation.

License Authorization Access Through Proxy Servers on Windows

If you are using a proxy server, Pervasive Software recommends that you configure it through Windows Internet Explorer for the best results. Pervasive PSQL v11 license authorization is designed to work seamlessly with no modifications needed when configured through Window Internet Explorer.

If you are using a proxy server that was not configured using Windows Internet Explorer, we recommend that you do so.

If using Windows Internet Explorer to configure your proxy server is not an option, you will need to follow these steps:

1. Install Pervasive PSQL v11 without performing authorization.

2. In the Windows registry, add the following to the HKEY_LOCAL_MACHINE\Software\Pervasive Software\ELS\ key:

String Value
proxy_host
DWORD Value
proxy_port
String Value
proxy_userid
String Value
proxy_passwd
Note: The proxy_host and proxy_port values are the only ones required by Pervasive PSQL v11. Depending on the configuration of your proxy server, you may also need to add proxy_userid and proxy_passwd.

Caution Editing the registry is an advanced procedure. If done improperly, the editing could cause your operating system not to boot. If necessary, obtain the services of a qualified technician to perform the editing. Pervasive Software does not accept responsibility for a damaged registry.

3. Authorize Pervasive PSQL v11 using the License Administrator utility.

License Authorization Access Through Proxy Server on Linux

If you are using a proxy server on Linux, you will need to follow these steps:

1. Install Pervasive PSQL v11 without performing authorization.

2. Manually edit the ELS.INI file to include the following:

proxy_host
proxy_port
proxy_userid
proxy_passwd
Note: The proxy_host and proxy_port values are the only ones required by Pervasive PSQL v11. Depending on the configuration of your proxy server, you may also need to add proxy_userid and proxy_passwd.

3. Authorize Pervasive PSQL v11 using the command line interface License Administrator utility.

Client Compatibility

The General Release of Pervasive PSQL v11 Server and Workgroup supports Pervasive PSQL v10 or later Clients.

New Features and Enhancements

See What’s New in Pervasive PSQL for a discussion of the new and changed features in Pervasive PSQL v11.

Installing Pervasive PSQL

This section discusses topics pertaining to the installation of the product on Windows and Linux. Before reading this section, review the content on Product Authorization in the previous section.

The installation files are available for download from the Pervasive Web site: http://www.pervasivedb.com.

Windows

If you have not installed the product and want to read about installation, see the portable document format (PDF) book Getting Started with Pervasive PSQL, available on the installation media or the Pervasive Software web site.

Installing Pervasive PSQL on Windows

Run the full (setup*.exe) Pervasive PSQL v11 installation.

The following topics apply when you install to Windows.

Subject
Discussion
Windows firewall and client/server applications
The Pervasive PSQL Server and Workgroup installation adds files to the firewall access list to enable client/server functionality. If the operating system security prompts you during installation of Pervasive PSQL to unblock or allow communication with a Pervasive PSQL component, select OK (yes).
If you encounter problems with your client/server applications not working correctly after installation, check the firewall access list or the ports. You may need to adjust some of the security settings to enable client/server applications. You can add files to the access list or open ports. You do not need to do both.
If you want to add Pervasive PSQL components to the firewall access list, add the following:
  • For Pervasive PSQL 32-bit Server, ntdbsmgr.exe.
  • For Pervasive PSQL Workgroup, w3dbsmgr.exe.
  • For Pervasive PSQL 64-bit Server, ntdbsmgr64.exe.
If you want to open ports, Pervasive PSQL communicates via the following ones: 3351 for the transactional interface, 1583 for the relational interface, and 139 for named pipes. Note that opening a port opens it for all access, not just for Pervasive PSQL.
Refer to the operating system documentation on security, firewall settings, and ports.
Optionally Disable Restore Points
The total installation time can usually be reduced on Windows Vista and later systems by disabling Windows System Restore. On Windows 7 and Windows Server 2008 R2 systems the installation can be made to skip the creation of a system restore point without actually disabling Windows System Restore by setting the property “MSIFASTINSTALL=1” on the command line. For example:
Setup<InstallType>_x<Platform>.exe /s /v"/qn /l*v \"%temp%\PSQLv11_InstallLogFileName.log\" MSIFASTINSTALL=1"
Characters to avoid in installation path
The pound (#) and percent (%) characters should not be used in installation paths for the Pervasive PSQL products if you intend to use Pervasive PSQL Control Center or DDF Builder. Those two utilities will not run if the installation path contains a pound character or a percent character.
Upgrading to run Workgroup Engine as a Service
If you install Workgroup Engine or Client Cache Engine as an application, then later decide you want to run it as a service, uninstall the engine, then reinstall it as a service.
Authorization and security
You must have Administrator rights to install Pervasive PSQL.
Depending on the particular account, a local security policy, “Sharing and security model for local accounts,” in Vista and Windows 2008 platforms can adversely affect network logins. Ensure that your policy for “Sharing and security model for local accounts” is set to Classic, which authenticates users as themselves.
PATH location
If you are installing a downloaded version of Pervasive PSQL, do not place the setup files in a location that is listed in the PATH environment variables. This can cause issues with file copying during install. Place the setup files in a location such as the Windows TEMP directory.
Windows Installer Version
Some versions of Windows supported with Pervasive PSQL v11 may not have the minimum required version of the Windows Installer installed. Pervasive PSQL v11 requires Windows Installer v3.1 be installed in order to run the PSQL installation. To see what version of the Windows Installer is present on your system, type MSIExec /? at a command prompt.
If your version of Windows does not have Windows Installer v3.1 installed, either upgrade your version of Windows Installer or install Pervasive PSQL v11 using the Setup executable file, which will automatically upgrade the installed version of Windows Installer to v3.1 before running the Pervasive PSQL v11 installation.
Windows 2008 Server Core installation
The optional installation features are disabled by default when installing Pervasive PSQL Server on Windows 2008 Server Core.
Installing XIO on Virtual Machines
Pervasive Software does not support running XIO on a virtual machine image.

Silent Installation

To install Pervasive PSQL v11 silently follow these steps:

1. Run the PSQL installation using the silent command line option. To authorize PSQL during the installation, update the installation configuration file ptksetup.ini to specify the authorization key (PVSW_PSQL_LICENSE_KEY=<key>). To authorize PSQL from the command line after the installation has completed, see step 2. 

Setup<InstallType>_x<Platform>.exe /s /v"/qn /l*v 
\"%temp%\PSQLv11_InstallLogFileName.log\""

This example creates an installation log file in the Windows temp directory.

2. [Optional] To authorize PSQL after the installation has completed, use the License Administrator Command Line Interface utility: 

“<PSQL_install_path>\bin\clilcadm.exe” –a <key>

Linux

Installing Pervasive PSQL on Linux

Pervasive PSQL v11 supports Linux distributions running Kernel 2.6.0 or higher. For information on installing Pervasive PSQL v11 on Linux, see Getting Started with Pervasive PSQL. If you are upgrading from a previous version of Pervasive PSQL on Linux, you must uninstall and then install Pervasive PSQL v11. For information on upgrading to Pervasive PSQL v11 on Linux, see Getting Started with Pervasive PSQL.

Note  Linux installations must be performed on a system with no prior version of Pervasive PSQL.

Linux Installation Packages

Full installation packages are available for Linux. A full installation includes the necessary engine and client files, all available utilities and the complete user documentation.

The following table outlines the installation packages available.

Pervasive PSQL Product
Installation Type
Contains
Example Name of Package1
Server 64-bit
Full
Engine and client files, utilities, and documentation
Pervasive.SQL-x.yy-zzz.zzz.x86_64.[rpm | tar]
Server 32-bit
Full
Engine and client files, utilities, and documentation
Pervasive.SQL-x.yy-zzz.zzz.i486.[rpm | tar]
Client 32-bit
Client
Client files, utilities, and documentation
Pervasive.SQL-Client-x.yy-zzz.zzz.i486.[rpm | tar]
1 x.yy-zzz.zzz represents the actual digits in the file name that indicate the release and build number of the product

Eco System Products

This section details information specific to Pervasive Software Eco System products and their compatibility with Pervasive PSQL v11.

If you have Backup Agent 1.x/2.x, DataExchange 2.x/3.x, or AuditMaster 6.4 installed and are installing Pervasive PSQL v11, they will not work after you have installed Pervasive PSQL v11. You will need to uninstall or upgrade your eco products so that they are compatible with Pervasive PSQL v11.

Backup Agent (32-bit)

If you have Backup Agent 2.x 32-bit installed, you will not be able to install Pervasive PSQL v11 until you first uninstall Backup Agent 2.x 32-bit. This is a current limitation with the Backup Agent 2.x 32-bit uninstall.

JRE Components Included in Installation

The JRE is no longer invoked as a separate installation by the Pervasive PSQL installation. The components of the JRE needed by the following features are now installed as part of Pervasive PSQL unless an appropriate version of the JRE (1.6.0_01 or higher) is already installed on the system:

On Windows 32-bit operating systems, the Pervasive PSQL installation does not install the JRE components if an appropriate version of the JRE (1.6.0_01 or higher) is already present. On Windows 64-bit operating systems and on Linux, the JRE components are always installed.

Known Issues

All known issues for Pervasive PSQL v11 are published on the Pervasive web site. See http://www.pervasivedb.com for the latest Known Issues.

Usage Notes

This section discusses situations you may encounter using the product after installation.

Windows

Subject
Discussion
Restore point errors in Pervasive PSQL install log
Failures pertaining to restore point can be ignored. Sometimes the Windows operating system fails to create a snapshot of the current disk (called a restore point) prior to allowing a new application installation. The restore point is not required. Uninstalling Pervasive PSQL completely removes the Pervasive PSQL product from the system.
Right-click shortcut for "Run As Administrator" on Windows Vista and later releases
A right-click on an application utility in the Windows Start menu does not offer a "Run As Administrator" option. This is a limitation of Windows Installer 3.1.
If, for some reason, you want to run a Pervasive PSQL utility in an elevated mode, you have several options:
  • Run the utility from an elevated command prompt
  • Create your own desktop shortcut to the utility executable
  • Navigate to the utility executable with Windows Explorer.

Linux

Subject
Discussion
Internet protocol on Linux
Pervasive PSQL does not support Internet Protocol (IP) v6 on Linux. If the operating system uses IP v6 by default, consider changing the default configuration to IP v4. Using IP v4 as the default prevents the delay caused by the database engine when it attempts to use IP v6 then must revert to IP v4. Refer to the operating system documentation for setting the IP default.
ODBC and Linux
Unix ODBC does not come installed with Red Hat Enterprise 5.4. If your ODBC application is set to use the Unix ODBC cursor library, you need to install the Unix ODBC package or change your ODBC application to use the Pervasive ODBC driver.

Technical Support

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

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 ©2010 Pervasive Software Inc. All Rights Reserved.

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

*** End of Release Notes ***