Pervasive PSQL Vx Server 11 Release Notes
Release Candidate—November 2011

Contents

Welcome to the Release Candidate of Pervasive PSQL Vx Server 11.

This file contains the following topics:

Overview

The Release Candidate of Pervasive PSQL Vx Server 11 includes the following:

Platforms Supported

Operating Systems

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

Update all operating systems to their latest service packs.

Virtualization Platforms

See the Pervasive Web site (http://www.pervasivedb.com) for the most up-to-date list of virtualization platforms supported for the Release Candidate. At the time of these release notes, Pervasive PSQL Vx Server 11 supported the following:

Product Authorization

The machine, physical or virtual, on which you install Pervasive PSQL Vx Server must have Internet connectivity. This is required for product authorization at installation time. Internet connectivity is also required for periodic product validation after installation.

If you download a trial version of Pervasive PSQL Vx Server 11 from the Pervasive Web site, you are provided with a trial key. The trail key lets you authorize the product for a short period so that you can use the database engine on a trail basis.

For long-term use of Pervasive PSQL Vx Server, you must apply a permanent key, which is provided by Pervasive Software or your application vendor.

You may install Pervasive PSQL Vx Server 11 without providing a trail key or a permanent key. However, the database engine is functional only until midnight on the date of installation.

Therefore, if you have a trial key or a permanent key, apply it during installation. That way, product authorization is completed as part of the installation process. Otherwise—as a separate activity that must occur after installation—you must use License Administrator to authorize the product.

Note that you cannot authorize Pervasive PSQL Vx Server with a key for Pervasive PSQL Server or Pervasive PSQL Workgroup.

Client Compatibility

Because of the licensing differences with Pervasive PSQL Vx Server, Pervasive Software recommends that you use the Client that comes with Pervasive PSQL Vx Server. This helps ensure that your applications correctly count licenses and allows you to monitor license compliance from the Client.

Pervasive PSQL Vx Server can be used with Pervasive PSQL v10 Clients and Pervasive PSQL v11 Clients (see the following Note for Pervasive PSQL v11 Clients). However, the API’s available with such Clients may consume more sessions (over count). You may need to increase the number of licenses required for the same application usage. Also, the License Administrator with those Clients does not correctly display all of the attributes of Vx Server licenses. License compliance can be accurately monitored only with the License Administrator installed with Pervasive PSQL Vx Server.

Note  An update is available for Pervasive PSQL v11 Clients. If you apply the latest update, your applications correctly count licenses and you can correctly monitor license compliance from a Pervasive PSQL v11 Client. The update is available only for Pervasive PSQL v11, not products prior to Pervasive PSQL v11.

Features

See Pervasive PSQL Vx Server Product Guide for a discussion of the features in Pervasive PSQL Vx Server 11.

Installing Pervasive PSQL Vx Server 11

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.

Note that you need to uninstall the Beta Release of Pervasive PSQL Vx Server 11 prior to installing the Release Candidate.

Note  You cannot install Pervasive PSQL Vx Server on the same machine, physical or virtual, with Pervasive PSQL Server or Pervasive PSQL Workgroup. You must uninstall the other Pervasive PSQL database engine product. The machine, physical or virtual, on which you install Pervasive PSQL Vx Server must have Internet connectivity to validate the key.

Windows

For complete installation details, see the book Pervasive PSQL Vx Server Product Guide, available on the Pervasive Software Web site (http://www.pervasivedb.com).

Installing Pervasive PSQL Vx Server 11 on Windows

Run the full (setup*.exe) Pervasive PSQL Vx Server 11 installation.

The following topics apply when you install to Windows.

Subject
Discussion
Windows firewall and client/server applications
The Pervasive PSQL Vx Server 11 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 Vx Server 11 to unblock or allow communication with a Pervasive PSQL Vx Server 11 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 Vx Server 11 components to the firewall access list, add the following:
  • For Pervasive PSQL Vx Server 11 32-bit, ntdbsmgr.exe.
  • For Pervasive PSQL Vx Server 11 64-bit, ntdbsmgr64.exe.
If you want to open ports, Pervasive PSQL Vx Server 11 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 Vx Server 11.
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" /l*v \"%temp%\PSQLVx11_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 Vx Server 11 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.
Authorization and security
You must have Administrator rights to install Pervasive PSQL Vx Server 11.
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 Vx Server 11, 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 Vx Server 11 may not have the minimum required version of the Windows Installer installed. Pervasive PSQL Vx Server 11 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 Vx Server 11 using the Setup executable file, which will automatically upgrade the installed version of Windows Installer to v3.1 before running the Pervasive PSQL Vx Server 11 installation.
Windows Server 2008 Core installation
The optional installation features are disabled by default when installing Pervasive PSQL Vx Server 11 on Windows Server 2008 Core.

Silent Installation

To install Pervasive PSQL Vx Server 11 silently, use the following command line option: 

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

To authorize Pervasive PSQL Vx Server during the installation, update the installation configuration file ptksetup.ini to specify the authorization key (PVSW_PSQL_LICENSE_KEY=<key>).

To authorize Pervasive PSQL Vx Server from the command line after the installation has completed, use the License Administrator command line interface (CLI) utility: 

<PSQL_install_path>\bin\clilcadm.exe -a <key>

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

Linux

Installing Pervasive PSQL on Linux

Pervasive PSQL Vx Server 11 supports Linux distributions running Kernel 2.6.0 or higher. For information on installing Pervasive PSQL Vx Server 11 on Linux, see Pervasive PSQL Vx Server Product Guide. Upgrading from a previous version of Pervasive PSQL on Linux is not permitted. You must uninstall the previous version and then install Pervasive PSQL Vx Server 11.

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

JRE Components Included in Installation

The JRE is not invoked as a separate installation by the Pervasive PSQL Vx Server 11 installation. The components of the JRE needed by the following features are installed as part of Pervasive PSQL Vx Server 11 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 Vx Server 11 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

The known issues for the Release Candidate for Pervasive PSQL Vx Server 11 are published on the download page. See http://www.pervasivedb.com.

Usage Notes

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

Windows

Subject
Discussion
Restore point errors in Pervasive PSQL Vx Server 11 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 Vx Server 11 completely removes the Pervasive PSQL Vx Server 11 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 Vx Server 11 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 Vx Server 11 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
unixODBC does not come installed with Red Hat Enterprise 5.4 or later. If your ODBC application is set to use the unixODBC cursor library, you need to install the unixODBC package or change your ODBC application to use the Pervasive PSQL ODBC driver.
If your application explicitly requests the unixODBC cursor library instead of the one provided by Pervasive PSQL, Pervasive PSQL attempts to link the application to the libodbccr.so.1 library from the unixODBC installation. The linking fails for Red Hat 5.4 and later because the libodbccr.so.1 library has been renamed to libodbccr.so.2.
Possible Workarounds
  • Install a version of unixODBC that includes libodbccr.so.1 instead of libodbccr.so.2.
  • Create a symbolic link in /usr/local/psql/lib to point libodbccr.so.1 to libodbccr.so.2.
            ln -sf libodbccr.so.2 libodbccr.so.1
            libodbccr.so.1 -->libodbccr.so.2
       Note that this solution assumes that libodbccr.so.2 is backward compatible with libodbccr.so.1.

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 ©2011 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 ***