PSQL v12 for OS X Release Notes
General Release – September 2015

Contents

Welcome to the General Release of PSQL v12 for OS X.

These release notes cover the following topics:

This document is included in your PSQL installation but may be updated after the release. Its latest version is always posted on the PSQL website.

Overview

Product Editions

This release includes the following editions:

Windows

Linux

OS X

Platforms Supported

This release has been successfully tested on the following operating systems in their 32- and 64-bit editions:

We recommend updating all operating systems to their latest service packs.

Product Authorization

PSQL v12 comes with a trial key for evaluation installations. These trial keys have limits of 20 users for Server, 5 users for Workgroup, and Medium size (20 GB) for Vx Server.

If you are installing this release of PSQL v12, you are required to authorize the product, either at the time of installation or after installation using the License Administrator utility.

Authorizing on Windows

On Windows, product authorization is required for PSQL Server, Vx Server, and Workgroup. Product authorization can be performed during installation or using the license administrator utility after installation. Authorizing PSQL v12 during installation requires an Internet connection. To authorize PSQL v12 after installation, see the alternative authorization procedures outlined in PSQL User's Guide.

Authorizing on Linux

On Linux, product authorization is required for PSQL Server and Vx Server. Product authorization must be performed after installation using the license administrator utility. Authorizing PSQL v12 requires an Internet connection. To authorize PSQL v12 after installation, see the alternative authorization procedures outlined in PSQL User's Guide.

Authorizing on OS X

On OS X, product authorization is required for PSQL Server and Vx Server. Product authorization must be performed after installation using the license administrator utility. Authorizing PSQL v12 requires an Internet connection. To authorize PSQL v12 after installation, see the alternative authorization procedures outlined in PSQL User's Guide.

License Authorization Access Through Proxy Servers on Windows

We recommend that you use Windows Internet Explorer to configure proxy servers. If your proxy server was not configured using Internet Explorer, we recommend that you use Internet Explorer to configure it again. If you are unable to use Internet Explorer, then you can use the steps given here. These steps involve editing the Windows Registry.

Caution Editing the registry is an advanced procedure. If done improperly, the editing can cause your operating system not to start. If necessary, obtain the services of a qualified technician to do the editing. Actian Corporation does not accept responsibility for a damaged registry.

In a 64-bit Windows operating system, two keys in the Registry can store proxy server settings:

Depending on the PSQL edition (Server, Client, Vx Server, or Workgroup), the ELS proxy server settings can be created in either location. Licensing manager looks for its proxy server settings first in the HKEY_LOCAL_MACHINE\Software\Wow6432Node\Pervasive Software\ELS\ key. If it cannot locate them there, it looks in the HKEY_LOCAL_MACHINE\Software\Pervasive Software\ELS\ key.

If you are editing Registry settings for proxy servers, you first need to find the correct location.

  1. Begin by looking for a Wow6432Node. If it exists, edit the proxy server Registry settings in the Pervasive Software\ELS\ key.
  2. If you find no Wow6432Node, move to the Software directory and edit the proxy server Registry settings in the Pervasive Software\ELS\ key.
  3. Modify the Windows Registry by adding the following to the Pervasive Software\ELS\ key:
    • String value proxy_host
    • DWORD (32-bit) value proxy_port
    • String value proxy_userid
    • String value proxy_passwd
    • Note  PSQL requires only the proxy_host and proxy_port values. Depending on the configuration of your proxy server, you may also need to add proxy_userid and proxy_passwd.

  4. Authorize PSQL v12 using the License Administrator utility.

License Authorization Access Through Proxy Server on Linux and OS X

On Linux and OS X systems, to configure a proxy server to allow license authorization, you must edit the els.ini file. PSQL does not support any other method of configuring proxy access on Linux or OS X.

  1. Locate els.ini. In a default installation, you can find it in /usr/local/psql/etc.
  2. Manually edit els.ini to include the following:
    • proxy_host
    • proxy_port
    • proxy_userid
    • proxy_passwd
    • Note  PSQL requires only the proxy_host and proxy_port values. Depending on the configuration of your proxy server, you may also need to add proxy_userid and proxy_passwd.

  3. Authorize Pervasive PSQL Vx Server using the License Administrator CLI utility.

Client Compatibility

For Windows and Linux, PSQL v12 Server and Workgroup support PSQL v11 Client or later.

For OS X server, clients must be 12.00 or later.

New Features and Enhancements

See What’s New in PSQL for coverage of new and changed features in PSQL v12. This document is included with the installed documentation and at the PSQL website on the download page and in the online help.

Actian Analytics Platform (AAP) for PSQL

Customers who purchase PSQL v12 Server or Vx Server 12 for use in Windows environments will also receive a license for Actian Analytics Platform (AAP) for PSQL. AAP offers PSQL users major performance increases and access to new technologies. AAP for PSQL includes everything you need for high performance reporting and split-second query responses. It also provides tools for data integration and analytics. For more information, see the link above.

Updates Since the OS X Beta Release

This release provides an update based on work done after the beta release in July. The file name for the beta version was PSQL-12.01-037.000.x86_64. The general availability (GA) release file name is PSQL-macosx-12.01-zzz.000.x86_64, where zzz.000 is a build number.

To upgrade from the beta to the GA release, you must first remove the beta installation. When you install the upgrade, settings and data used in the beta version are preserved.

Upgrade Changes and Fixes

We recommend that you upgrade your beta installation to the new version. The following table summarizes updates that may be important to beta users.

Issue in Beta
Resolution in GA
Beta supports only TAR installation. A standard DMG installer is required.
Added.
OS X and Linux need different TAR file names.
Done.
Pluggable authentication module (PAM) security on OS X is not supported.
Added.
An open client connection prevents server engine shutdown (PSQL-3027).
Fixed.
Native OS X SMB is not supported (PSQL-2935).
Fixed.
Phone authorization is not supported (PSQL-2895).
Fixed.

Installing PSQL

This topic discusses installation of the product. Before reading further, be familiar with Product Authorization.

Installation files are available for download from the PSQL website.

You must uninstall any previously installed prerelease version, such as a beta or release candidate from any edition, before installing the final General Availability (GA) release of PSQL v12.

If you have not installed the product before or are upgrading for the first time and want to read about installation in detail, see Getting Started with PSQL, available on the installation media or the PSQL website.

Installation comes in three types:

Installing PSQL on Windows

To start the installation, run the installer application (Install_*.exe) for the PSQL engine or client type that you want to install and follow the instructions displayed by the installer.

The PSQL v12 installer automatically detects the bit architecture of the operating system and installs the right components. You do not have to choose the 32- or 64-bit installer application.

The following table describes PSQL v12 installers on Windows operating systems.

PSQL v12 Installation Package (.exe)
Description
Install_PSQL_Server_Engine
Installs 32-bit engine on 32-bit operating system.
Installs 64-bit engine on 64-bit operating system.
Installs all client components.
Install_PSQL_Vx_Server
Installs 32-bit engine on 32-bit operating system.
Installs 64-bit engine on 64-bit operating system.
Installs all client components.
Install_PSQL_Workgroup_Engine
Installs 32-bit engine on both 32- and 64-bit operating systems. Installs all client components.
Install_PSQL_Client
Installs 32-bit components on 32-bit operating system.
Installs both 32- and 64-bit components on 64-bit system.

Important Notes about Installing on Windows

The following information applies when you install PSQL on Windows systems.

Subject
Discussion
Windows firewall and client/server applications
PSQL installations add files to the firewall access list to enable client-server functionality. If the operating system security prompts you during installation of PSQL to unblock or allow communication with a PSQL component, select OK (yes).
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 or later and Windows Server 2008 R2 or later 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:
Install_PSQL_<InstallType>.exe /s /v" /l*v \"%temp%\PSQLv12_InstallLogFileName.log\" MSIFASTINSTALL=1"
Characters to avoid in installation path
Do not use the characters for pound (#), percent (%), or double backslash (\\, used to specify a UNC path) in installation paths for PSQL products if you plan to use PSQL Control Center or DDF Builder. These two utilities cannot run if the installation path contains these characters.
Modifying to run Workgroup Engine as an Application
If you install Workgroup Engine as service, then later decide you want to run it as an application, uninstall the engine, then reinstall it as an application.
Upgrading to run Client Cache Engine as a Service
If you install Client Cache Engine as an application, then later decide you want to run it as a service, uninstall the client, then reinstall it as a service.
Authorization and security
You must have Administrator rights to install PSQL.
Depending on the particular account, a local security policy called “Sharing and security model for local accounts” in Vista and Windows Server 2008 can adversely affect network logins. Be sure that this policy is set to Classic, which authenticates users as themselves.
PATH location
If you are installing a downloaded version of 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 installation. Place the setup files in a location such as the Windows TEMP directory.
Windows Server 2008 Core installation
The optional installation features are disabled by default when installing Pervasive PSQL Server on any version of Windows Server Core.

Installing Silently on Windows

To install PSQL v12 silently, run the PSQL installation using the quiet command line option /qn, as shown in this example:

Install_PSQL<InstallType>.exe /s /v"/qn /l*v \"%temp%\PSQLv12_InstallLogFileName.log\""

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

Optionally, to authorize PSQL after the installation has completed, use the License Administrator command line tool clilcadm.exe:

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

Installing PSQL on Linux

PSQL v12 has been tested on Red Hat Enterprise Linux 7. For information about installing or upgrading to PSQL v12 on Linux, see Getting Started with PSQL.

Installation Packages

PSQL offers full and client installations of both RPM and TAR Linux packages. A full installation includes the necessary engine and client files, utilities, and the complete user documentation. A client installation provides only files needed to support a client, including utilities and documentation. The following table lists the installation packages.

PSQL Package           
Contains
Package Names1                                                          
Server 64-bit
Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.
PSQL-linux-yy.yy-zzz.zzz.x86_64.rpm
PSQL-linux-yy.yy-zzz.zzz.x86_64.tar.gz
Vx Server 64-bit
Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.
PSQL-Vx-linux-yy.yy-zzz.zzz.x86_64.rpm
PSQL-Vx-linux-yy.yy-zzz.zzz.x86_64.tar.gz
Client 64-bit
64-bit client files, 64-bit utilities, documentation.
PSQL-Client-linux-yy.yy-zzz.zzz.x86_64.rpm
PSQL-Client-linux-yy.yy-zzz.zzz.x86_64.tar.gz
Client Access 32-bit
32-bit client files for compatibility with 32-bit applications on 64-bit Linux. Installed after one of the other three packages.
Note: Glibc and stdc++ packages are prerequisites for the Client Access installation. Before installing Client Access, you can add these packages from the repository of your Linux distribution using a yum command:
yum install glibc.i686 libstdc++.i686
In LD_LIBRARY_PATH, add the /lib directory of the Client Access installation location so that your 32-bit application can find it. For example, /usr/local/psql/lib64:/usr/local/psql/lib.
PSQL-Client-Access-linux-yy.yy-zzz.zzz.x86_64.rpm
PSQL-Client-Access-linux-yy.yy-zzz.zzz.x86_64.tar.gz
1 yy.yy-zzz.zzz represents the digits in the file name for the release and build numbers of the product.

Note  To upgrade to PSQL v12 from a previous PSQL version on Linux, you must first uninstall the current version.

Installing PSQL on OS X

PSQL v12 has been tested on OS X 10.8, 10.9, and 10.10. For information about installing or upgrading to PSQL v12 on OS X, see Getting Started with PSQL.

Installation Packages

PSQL offers full and client installations of both TAR and DMG packages on OS X. A full installation includes the necessary engine and client files, utilities, and the complete user documentation. A client installation provides only files needed to support a client, including utilities and documentation. The following table lists the installation packages.

PSQL Package           
Contains
Package Names1                                                    
Server 64-bit
Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.
PSQL-macosx-yy.yy-zzz.zzz.x86_64.tar.gz
PSQL-macosx-yy.yy-zzz.zzz.x86_64.dmg
Vx Server 64-bit
Full installation of 64-bit engine, 64-bit client files, 64-bit utilities, documentation.
PSQL-Vx-macosx-yy.yy-zzz.zzz.x86_64.tar.gz
PSQL-Vx-macosx-yy.yy-zzz.zzz.x86_64.dmg
Client 64-bit
64-bit client files, 64-bit utilities, documentation.
PSQL-Client-macosx-yy.yy-zzz.zzz.x86_64.tar.gz
PSQL-Client-macosx-yy.yy-zzz.zzz.x86_64.dmg
1 yy.yy-zzz.zzz represents the digits in the file name for the release and build numbers of the product.

Note  To upgrade to PSQL v12 from a previous PSQL version on OS X, you must first uninstall the current version.

Important Notes about Installing on OS X

The following information applies when you install PSQL on OS X systems. These notes all relate to access and authentication using the Samba implementation of the SMB/CIFS networking protocol. The instructions for configuring Samba on Linux also apply to OS X, but with the exceptions shown here.

Subject
Discussion
Samba version
Samba (SMB) file sharing is required for remote Btrieve-level file access. Set OS X native file sharing under System Preferences > Sharing or use an OS X-compatible Samba 3 package, such as SMBUp.
Authentication level
All three levels of authentication are supported on OS X. However, authentication through PVPIPE$ is not supported on that operating system.
Samba configuration file location
If your Samba package installs the Samba configuration file in a location other than one in the following list, you must enter that path name in the Properties > Access settings for your server.
  • /etc/samba/smb.conf
  • /etc/smb.conf
  • /usr/local/samba/lib/smb.conf
  • /usr/local/lib/smb.conf
  • /lib/smb.conf
  • /etc/samba.d/smb.conf
  • /opt/samba/lib/smb.conf
  • /usr/share/samba/smb.conf
  • /usr/local/share/samba/smb.conf
  • /home/samba/lib/smb.conf
  • /opt/local/etc/samba3/smb.conf (default location for Samba 3)
If you use OS X native file sharing, PSQL retrieves drive-sharing settings directly from the system. No smb.conf file is required. For more information, see the topic on native SMB file sharing on OS X in Getting Started with PSQL.
For more information, see Server Configuration Parameters in Advanced Operations Guide.
PVPIPE$
PVPIPE$ applies only to Linux. PSQL currently does not use this FIFO on OS X.

Source Code for PSQL unixODBC

In accordance with GNU General Public Licensing (GPL), on Linux and OS X systems the source code for PSQL unixODBC functionality is redistributed in the /etc directory of the installation as psql-unixODBC-2.2.11.tar.gz.

JRE Components Included in Installation

On Windows 32-bit operating systems, the PSQL installation does not install the JRE components if an appropriate version of the JRE (1.7 or later) is already present for all users. On Windows 64-bit operating systems and on Linux and OS X, the JRE components are always installed.

Installing Backup Agent

You can use Backup Agent v12 to upgrade from all previous versions of Backup Agent.

Windows

On Windows platforms, PSQL v12 provides two upgrade paths from older versions of Backup Agent. The following table compares the two upgrades.

Backup Agent
Upgrade Method
3.x
The PSQL v12 installer warns that it is not compatible with Backup Agent 3.x, but it allows you to complete the PSQL v12 installation.
After installing PSQL v12, you can upgrade to Backup Agent v12. Running the Backup Agent v12 installer automatically uninstalls Backup Agent 3.x and replaces it.
2.x
1.x
The PSQL v12 installer informs you that the PSQL installation cannot run until you uninstall Backup Agent.
Exit from the PSQL v12 installer, uninstall Backup Agent, and then restart the PSQL v12 installer.
After PSQL v12 installation is finished, you can install Backup Agent v12.

Linux

On Linux, after installing PSQL v12 you must manually uninstall your existing version of Backup Agent and then manually install Backup Agent v12.

OS X

In this beta release, Backup Agent v12 is not currently supported.

Fixed Issues and Known Issues

The online download page for PSQL v12 provides a history log that lists issues fixed and enhancements added since PSQL v11.30. You can also download a file of known issues for PSQL v12.

Usage Notes

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

For Windows

Subject
Discussion
Restore point errors in 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) before allowing a new application installation. The restore point is not required. Uninstalling PSQL completely removes the PSQL product from the system.
No right-click option to run as administrator on Windows Vista and later releases
Right-clicking 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 you want to run a 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.

Technical Support

You can obtain technical support from several online options at the PSQL website:

Disclaimer

ACTIAN CORPORATION 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 © 2015 Actian Corporation. All Rights Reserved.


Actian Corporation

*** End of Release Notes ***