Pervasive PSQL v10 SP3 - README
General Release - November 2009

Contents


Welcome to the General Release of Pervasive PSQL v10 SP3. This readme file contains the following topics:

New Features and Enhancements

Refer to What’s New in Pervasive PSQL for complete details about the new features and enhancements. This section provides only the highlights:

Support for Windows 7

Pervasive PSQL v10 SP3 is compatible with Windows 7. It has been tested on the following versions:

Operating System
Pervasive PSQL Products Supported
Windows 7 Ultimate (32-bit and 64-bit)
Server, Workgroup, Client
Windows 7 Enterprise (32-bit and 64-bit)
Server, Workgroup, Client
Windows 7 Professional (32-bit and 64-bit)
Server, Workgroup, Client
Windows 7 Home (32-bit)
Workgroup, Client

For a full list of supported environments, including all editions of Windows 7 supported, refer to the System Requirements page on the Pervasive Software web site.

Product Authorization

Product authorization is a license validation process that verifies the copy of Pervasive PSQL is legitimate, correctly licensed, and on the appropriate hardware and software platform. Beginning with Pervasive PSQL v10, Pervasive began using product authorization for PSQL trials and e-commerce versions obtained from the Pervasive Web site.

With Pervasive PSQL v10 SP3, product authorization is also included in Pervasive PSQL software purchased from resellers and distributors. (That is, Pervasive PSQL as a boxed product.)

Currently, product authorization is not included in Pervasive PSQL products available from original equipment manufacturers (OEMs).

Note that, with Pervasive PSQL v10 SP3, a product can be authorized within a virtual machine. The same licensing requirements apply whether using Pervasive PSQL directly on a physical machine or running it within a virtual machine. Since only one copy of the software may be associated with each license key, each virtual image (including clones and copies) requires its own key.

You can authorize the product at installation time through the interactive graphical user interface (GUI), or after installation using the licensing utilities (see Note below). The installation GUI guides you though the authorization process and is self-explanatory. If you choose to authorize Pervasive PSQL after installation, see “License Administrator” chapter in Pervasive PSQL User’s Guide.

Notes

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.

Trial License for 30 Days

The trial license key that is included with the Pervasive PSQL Server and Workgroup installations has a trial period of 30 days. You have up to 30 days to authorize the Pervasive PSQL product with a non-trial key. If not authorized within 30 days, the database engine no longer runs.

The trial license for Pervasive PSQL Server 32-bit and 64-bit on both Window and Linux provides a user count of 20. The trial license for Pervasive PSQL Workgroup provides a user count of 5.

XIO Changes

The memory requirements for the optional database accelerator Xtreme I/O (XIO) have increased to 4 GB.

In addition, XIO is now supported only on server class operating systems. The following Windows 32-bit operating systems are supported (XIO is not supported on 64-bit platforms):

Installing Pervasive PSQL

This section discusses topics pertaining to the installation of the product on Windows and Linux.

Note  Before reading this section, review the content on Product Authorization in the previous section.

Windows

Run the full (setup*.exe) Pervasive PSQL v10 SP3 installation for the following:

Upgrading from Versions Prior to Pervasive PSQL v10

Product authorization is required for Pervasive PSQL Server or Workgroup. You may install Server or Workgroup with only the trial license if you want, but product authorization is required before expiration of the trial license period.

If you have Backup Agent 1.2, DataExchange 2.9 or AuditMaster 6.4 installed, they will continue to work after you upgrade to Pervasive PSQL v10 SP3.

Silent Installation

To install Pervasive PSQL v10 SP3 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 /leom 
\%temp%\v10sp3_UpgradeLogFileName.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> 

Upgrading from Pervasive PSQL v10 or Later

The interactive installation automatically uses the permanent license from the Pervasive PSQL v10 or later release. No authorization step is required by you. The Pervasive PSQL v10 SP3 installation wizard does not display the authorization dialog.

If you have Backup Agent 1.2, DataExchange 2.9 or AuditMaster 6.4 installed, they will continue to work after you upgrade to Pervasive PSQL v10 SP3.

Silent Installation

To install Pervasive PSQL v10 SP3 silently follow these steps:

1. [Optional] If Pervasive PSQL v10 or Pervasive PSQL v10.10 is installed, download the latest available update for the installed release from the Pervasive download web page and apply the update before upgrading to Pervasive PSQL v10 SP3. Applying the update ensures that the uninstall of the previous version retains any user settings.

2. Run the PSQL installation using the silent command line option.

Setup<InstallType>_x<Platform>.exe /s /v"/qn /leom 
\%temp%\v10sp3_UpgradeLogFileName.log\""  

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

Installing Pervasive PSQL for the First Time

Product authorization is required for Pervasive PSQL Server or Workgroup on systems with no previous version of Pervasive PSQL installed. You may install Server or Workgroup with only the trial license if you want, but product authorization is required before expiration of the trial license period.

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.

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, ntdbsmgr.exe and 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.
Default location of installed components
The default location of installed components places files into different root locations depending on product and platform. See “Default Location of Installed Components” in What’s New in Pervasive PSQL for details.
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.
FireFox browser
Note that the Registration page invoked at the end of a Pervasive PSQL installation, register.htm, does not display in the FireFox browser.
The Workaround solution is to open the registration page manually in FireFox. The file is located in installation_location\Pervasive Software\PSQL\Docs.
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. Any previous Beta versions of Pervasive PSQL v10 must be uninstalled prior to installing this General version.
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 v10 SP3 may not have the minimum required version of the Windows Installer installed. Pervasive PSQL v10 SP3 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 v10 SP3 using the Setup executable file, which will automatically upgrade the installed version of Windows Installer to v3.1 before running the Pervasive PSQL v10 SP3 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 v10 SP3 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 /leom 
\%temp%\v10sp3_UpgradeLogFileName.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

Linux installations are one of the following types:

Upgrading from Prior Versions of Pervasive PSQL

If you are upgrading from a previous version of Pervasive PSQL on Linux, you must uninstall and then install Pervasive PSQL v10 SP3. For information on upgrading to Pervasive PSQL v10 SP3 on Linux, see “Upgrade Installation” in Getting Started with Pervasive PSQL.

Product Authorization

If you upgrade from a version prior to Pervasive PSQL v10, Pervasive PSQL Server must be authorized after you upgrade. A Pervasive PSQL v10 key is required. You perform product authorization after installation by using a licensing utility. See “License Administrator” chapter in Pervasive PSQL User’s Guide.

If you upgrade from Pervasive PSQL v10 or later, the key provided with your original product is still valid. After installation, use a licensing utility to authorize the product with your original key. See “License Administrator” chapter in Pervasive PSQL User’s Guide.

Installing Pervasive PSQL for the First Time

Pervasive PSQL v10 SP3 supports Linux distributions running Kernel 2.6.0 or higher. For information on installing Pervasive PSQL v10 SP3 on Linux, see “Installing Pervasive PSQL for Linux” in Getting Started with Pervasive PSQL.

Product authorization is required for Pervasive PSQL Server on systems with no previous version of Pervasive PSQL installed. By default, the product is installed with the trial license. Product authorization is required before expiration of the trial license period. You perform product authorization after installation by using a licensing utility. See “License Administrator” chapter in Pervasive PSQL User’s Guide.

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

Known Issues

This section lists the known issues for Pervasive PSQL v10 SP3.

Client Requesters

Tracking Number
Description
57018
PCC says incorrectly "Windows 32-bit only" for Embedded spaces setting
57586
When a communication session between client and server is no longer valid status 170 is returned

Data Archival

Tracking Number
Description
55919
Archival logging does not work when a client machine has "use cache engine" turned on and Workgroup Engine or Cache Engine configured to run as a service.
Workaround: Configure the Workgroup or Cache Engine service to run under a username/password that has the necessary rights to access objects on the remote server machine.

Documentation

Tracking Number
Description
58262
Explanation of how to add ActiveX controls to a Visual Basic project is out of date

Eco-system Products

Tracking Number
Description
58520
On Windows 7, navigational icons do display on DataExchange Wizard screen

I18N

Tracking Number
Description
57338
Fails to bind database with lowercase non-Ascii characters using DTI PvModifyDatabase() function

Installation

Tracking Number
Description
55591
After installation, the Add/Remove Programs “Modify” option displays features that were disabled during install
55835
Installation time on Windows Vista is twice or more slower than non-Vista operating systems on equivalent hardware. Microsoft has confirmed that this is expected behavior because of the increased number of filter drivers such as UAC Virtualization and Vista Search Indexing.
56018
Install not prompting user to uninstall PDAC SDK
56075
Engines not added to firewall when performing minimum installation.
56240
Pervasive PSQL v10 upgrade install does not disable DX 2.8 services
56300
bdu command line utility is installed by a V10 client32 utility
56496
Environment variables for v9 are not cleared on upgrading from v9 to v10
57224
v10.10 install cannot handle long Java path
57447
At the end of a Workgroup installation on Vista SP1 and Win 2008, the engine may not be started properly.
Workaround: Manually start the Workgroup engine or reboot the machine to restart the engine.
57947
Install may fail if 'MyPictures' folder is not available
58040
Install fails if BtrevDos.cab is not present
58042
Command line repair fails if EclipRCP.cab is not present
58045
PSQL uninstall does not check for pending reboots on the system
58295
10.20 Install miscalculates disc space requirements
58316
Workgroup Engine returns message engine already loaded as install runs
Workaround: Click OK on the message dialog and the patch install continues and successfully installs.
58355
Patch install on top of 10.10 is slow on Vista 64 bit
58420
Install cancellation rollback result different than reported when invoked after the service is started
58553
PSQL Install: Show disabled checkbox option to 'view registration page' on install finish dialog.

MicroKernel Engine

Tracking Number
Description
56363
Accessing a file using two different symlinks on Windows Vista or Windows 2008 results in status 85 (file locked).
If two applications access a file using two different symlinks, the second open results in status 85 (file locked). For example, if one application opens C:\ProgramData\Pervasive Software\PSQL\Demodata\Class.mkd and another application opens C:\Users\All Users\Pervasive Software\PSQL\Demodata\Class.mkd, the database engine returns status 85.
Workaround: Use the same path for each open to access the file.
58003
A B_GET_EQUAL operation on the system key (index 125) copies 244 bytes of the input key buffer even only 8 bytes were passed in. That does not happen on any other index but 125 (system key).
58427
Custom installation using a128 byte destination path crashes the MicroKernel on Windows 7

Services

Tracking Number
Description
55946
Set data path to ~150 chars and Pervasive PSQL services will not start

Software Development Kit (SDK)

Tracking Number
Description
55423
PvCopyDatabase() does not work for database with referential integrity (RI), regardless of RI level. PvCopyDatabase API cannot properly copy tables with RI constraints. The copied tables with RI constraints return status 73 on open attempts.
55994
Pervasive OLEDB Provider does not work with a database under "mixed" mode security.
Workaround: Use MSDASQL Provider instead.
56481
After completion of the ADO.NET design time installation, ADO.NET 3.0 provider does not appear in the Add Reference list.
56968
DTO won't set a DBCodePage other than UTF8
58146
Memory leak running .net application using Pervasive OLEDB.
58153
Enumerated Types in DTO & DTI do not include Numeric even digit flag
58323
JCL SDK Package is missing PVIDEODB's dbbackup folder and contents
58484
ADO.NET provider fails to display in Visual Studio column names that contain a hyphen

SQL

Tracking Number
Description
54781
Executing a stored procedure that contains a print statement inside the PCC or any other GUI tool (such as ODBCTest) may cause the tool to hang.
Workaround: Modify the PSQL Relational Engine service property to "allow service to interact with desktop." This option is configurable with the "Log On" pane under the service's "Properties" screen.
55807
DROP DATABASE disables user session. Any attempt to switch to another database fails.
56108
On Linux, creating a user with a password of length 129 or greater is crashing the engine.
56863
Attempting to create a client DSN from 10.10 client to v9.50 server fails
57076
Data pulled from cross databases of different encodings is corrupted
57216
Database Code Page setting change doesn't take effect until all connections are closed
57274
Stored procedure out parameters crash server
57330
Set owner to a value longer than 24 characters returns an erroneous message.
57345
SQL Engine not matching index definition to existing Btrieve key
57362
When doing ODBC translation for UTF8 database, space padding is not adjusted
57372
Relational engine converts I18N Characters to upper case.
57385
SQLForeignKeys() incorrectly returns HY000 instead of HY009 with invalid use of NULL pointer
58404
Create database fails if database deleted then re-created and DDFs exist from previous creation
58630
“Record Too Large” error from MS Access 2007 (escalation #183524)

System Driver

Tracking Number
Description
56575
XIO is not supported in the Microsoft cluster environment

Utilities

Tracking Number
Description
54446
DDF Builder does not support creating a table definition for a file that uses ISR (International Sort Rules). DDF Builder does not currently provide a warning.
How to determine if a data file uses ISR:
When a key has one of the ACS flags set, look at the 265 bytes for that ACS.
If the signature byte is 0xAC, then it's a User-defined ACS.
If the signature byte is 0xAD, then it's a locale-specific ACS.
If the signature byte is 0xAE, then it's an ISR.
54785
BDU utility fails when the secured database password is longer than 111 characters.
54990
Some configuration settings in PCC are missing from a virtual network computing (VNC) session.
Workaround: To configure the database engine, use PCC directly on that engine's console or use a remote desktop tool other than VNC.
55321
PCC grid cannot display tables with numerous fields.
Workaround: Use views or SELECT statements to limit the number of fields displayed in the grid.
55396
The PSA functionality “View loaded Pervasive modules” does not list 64-bit Pervasive PSQL components.
55960
DDF Builder encounters error when operating on files that are held open exclusively by another process.
Workaround: Ensure that the files are not held open exclusively by another process.
56633
DDF Builder should not allow saving a file with more than 119 indexes
56634
DDF Builder creates an invalid definition for an overlapping segment file
56681
Invoking DDF Builder plug-in details on 64-bit Linux results in internal error
56779
PCC crashes in FedoraCore8 on Linux when adding a new table.
This is caused by a known bug in Sun's JRE.
Workaround: turn off some features using the following command:
sed -i 's/XINERAMA/FAKEEXTN/g' $JAVA_HOME/lib/i386/xawt/libmawt.so
56842
CNVDDF.exe returns status 357 and will not convert dictionary
56855
'Master' login name does not show in PCC on Linux as it does on Windows
56857
One-column select in PCC on Linux results in grid taking the entire space instead of the width of the column data
56878
COLLATE once specified in PCC is not removed on deletion
57056
Create Btrieve File\Key Specification Page isn't scrolling.
57070
When using DDF Builder in a virtual enviroment the SQL Index pane is very small or can barely be seen
57077
DDF Builder does not show preview values for GUID
57088
DDF Builder does not complain when you try to create a definition on a file with 1 multisegmented key
57093
Help link for Table Definition Editor throws an error dialog
57111
DDF Builder will not import btrieve schema remotely against demodata
57210
PCC F10 hot key to Execute All SQL Statements does not work on Linux
57217
butil crashes on Linux when incorrect -endbu parameter is used
57230
Can't execute a view right after you create it in PCC
57255
Window DDF Builder does not recognize 5x files on remote Linux servers.
57257
Progress dialog displayed when loading data in the grid has unusable cancel button
57265
Remote Window DDF Builder cannot see large file with extension going against linux server
57271
Cannot export Btrieve Schema from a remote machine using DDF Builder
57310
On SuSE 10.1 PCC may abort with message "line4: 5502 Aborted". This is a known system issue with SuSE 10.1 GTK controls.
57334
butil @commandfile does not utilize quoted paths correctly
57335
DDF Builder prompts multiple times for owner name on tables with owner names during database check even if you cancel the operation
57343
Problem importing Btrieve schema remotely using DDF Builder
57345
Error refreshing grid after adding a row in PCC
57414
PCC displays a “20: Session Security Error” when showing properties of a table in a secure database
58150
PCC GUI allows entering scale higher than precision for numeric data types
58170
Minimum State Delay units would be better as seconds as in the manual
58171
Range description in bcfg for Minimal State Delay is incorrect
58173
Preview of DateTime doesn't show Milliseconds values
58230
Repeated offline authorization request for an auth.pky file fails with rc7267
58237
Call from clilcadm.exe should start the engine like it did pre latest els changes
58259
One part of PSA's log file has English dates
58268
CLI license administrator can connect to another server without username and password but the GUI cannot
58276
PCC throws errors when launched as user psql on Suse11. The GCC libraries installed with Pervasive PSQL are a different version from those provided with the Linux distribution.
Workaround: Move the version of the libraries installed with Pervasive PSQL so the database engine will use the libraries provided with the Linux distribution.
On a 32-bit installation run:
cd /usr/local/psql/lib
mkdir away
mv libstdc++.so.6 away/
mv libgcc_s.so.1 away/
On a 64-bit installation run:
cd /usr/local/psql/lib64
mkdir away
mv libstdc++.so.6 away/
mv libgcc_s.so.1 away/
58287
DDFBuilder log file cannot be displayed on SUSE 11
58303
w64clilcadm displays a different message to clilcadm when no local engine is present (when client64 is installed).
58341
PCC does not stop infinite loop resulting from stored procedure execution
58379
File types incorrect in PCC Open File dialog
58493
Signing information details about DDF Builder plugin display is in English on a Japanese system
58524
DDF Builder does not create a new database with default options or with recommended options when directory is not present
58543
Setting an encoding crashes PCC
58545
XIOStats “Open CSV File” returns English errors on a Japanese system
58602
CLI license administrator gives erroneous 7317 error when attempting to deauthorize a product key
58611
DDF Builer CheckTable sees LONGVARCHAR columns as a warning

Usage Notes

This section discusses situations you may encounter using the product after installation. See also Known Issues.

Windows

Subject
Discussion
Authorization of Workgroup Key on Vista and Windows 7
You can encounter difficulty authorizing a permanent key for Pervasive PSQL Workgroup on Windows Vista or Windows 7 if the following conditions are all true:
  • Pervasive PSQL Workgroup was installed as an application.
  • The Workgroup database engine is running without administrative privileges. Note that, by default, applications run with privileges of a standard user unless the privileges are elevated. That is, even if you are a member of the administrator’s group and you start the Workgroup database engine without using Run as Administrator to elevate privileges, the engine runs with privileges of a standard user.
  • A permanent key for Pervasive PSQL Workgroup was not supplied during the installation process. That is, you chose to authorize the permanent key after installation by using a licensing utility.
Complete the following steps to ensure a permanent key is correctly authorized:
1. If the Pervasive PSQL Workgroup application is running, close the application (stop the database engine by right-clicking on the engine tray icon then clicking stop).
2. From File Explorer, locate the file w3dbsmgr.exe. Look for the file under <install_drive>\Program Files\Pervasive Software\PSQL\bin.
3. Right-click w3dbsmgr.exe then click Run as Administrator. You must have administrative rights or know the password and name of a user with administrative rights. You need to elevate the privileges of the database engine before authorizing a key with a licensing utility.
4. From File Explorer, locate the file guilcadm.exe. Look for the file under <install_drive>\Program Files\Pervasive Software\PSQL\bin. (Alternatively, you could use the command line interface licensing utility, clicladm.exe, if you prefer.)
5. Right-click guilcadm.exe then click Run as Administrator. You must have administrative rights or know the password and name of a user with administrative rights. You need to elevate the privileges of the utility before authorizing a key with it.
6. Type, or paste, the permanent key for Pervasive PSQL Workgroup in the Key field, then click the button to initiate the authorization of the key.
7. Optionally, stop the database engine and re-start it without elevated privileges.
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 because the Pervasive PSQL uninstall completely removes the Pervasive PSQL product, rendering the same result as if you had used the Windows restore capability.
System DSN creation on Windows 2008 Server and Windows Vista
You can create system data source names (DSNs) only if logged on as an elevated administrator. A standard user cannot create system DSNs. This is a restriction placed by Windows, not Pervasive PSQL.
When you create a new database with PCC, a corresponding system DSN is created by default. (You can override the default if you choose.)
If you are logged on as a standard user or a non-elevated administrator and attempt to create a system DSN from PCC, status code 7011 results.
As a standard user, you have two choices to create the system DSN for the database. You can use PCC or the Pervasive Distributed Tuning Interface PvCreateDSN() call. You must run the Workgroup Engine in an elevated mode with administrative privilege, or as a service with LocalSystem or administrative privilege.
If you are logged on as a non-elevated administrator, you can also use the ODBC Administrator to create a system DSN locally once you elevate to full administrator.
Once the system DSN is created successfully, any user may start the Workgroup Engine and use the DSN.
Refer to the Windows documentation for security and types of users.
Internet protocol on Windows 2008 Server and Windows Vista
Pervasive PSQL supports Internet Protocol (IP) v4, not IP v6. Consider changing the operating system default configuration from IP v6 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.
Right-click shortcut for "Run As Administrator" on Windows 2008 Server and Windows Vista
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.
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 elevate command prompt
  • Create your own desktop shortcut to the utility executable
  • Navigate to the utility executable with Windows Explorer.

Linux

Subject
Discussion
ODBC and Linux
Unix ODBC does not come installed with Red Hat Enterprise 5. 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:

Windows 2008 Server Certification

Pervasive PSQL is Certified for Windows 2008 Server (64-bit editions). As part of the certification requirements, the following topics are included in this readme file.

Files Not Digitally Signed

The following two tables list files installed with the Pervasive PSQL v10 SP3 products on Windows platforms that are not digitally signed.

File
Vendor
Product
Description
keyhh.exe
KeyWorks Software (www.keyworks.net)
KeyHH
KeyHH augments HTMLHelp, a help development environment from Microsoft that produces .chm files from HTML-based source. KeyHH can be used in addition to, or as a complete replacement for, HH.EXE, which is provided by Microsoft. KeyHH provides all of the functionality of HH.EXE, offers solutions for some known bugs in HTMLHelp, and provides additional functionality.
mfc80.dll
MFC80ENU.dll
MFC80JPN.dll
mfc80u.dll
mfcm80.dll
mfcm80u.dll
msvcm80.dll
msvcp80.dll
msvcr80.dll
Microsoft (www.microsoft.com)
Visual C++ 2005 SP1 Libraries
Installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ SP1 on a computer that does not have Visual C++ 2005 SP1 installed.
localfile_1_0_0.dll in org.eclipse.core.filesystem.
win32.x86_1.1.0.v20070510.jar
swt-awt-win32-3347.dll in org.eclipse.swt.win32
.win32.x86_3.3.2.v3347a.jar
swt-gdip-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-wgl-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-xpcominit-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
swt-xulrunner-win32-3347.dll in org.eclipse.swt.win32.win32
.x86_3.3.2.v3347a.jar
update.dll in org.eclipse.update.core.win32
_3.2.110.v20070615.jar
win32refresh.dll in org.eclipse.core.resources.win32
_3.3.0.v20070226.jar
Eclipse Foundation (www.eclipse.org)
Eclipse Platform Software Development Kit (SDK)
Eclipse Platform SDK's Windows native libraries

The following Java Runtime Environment (JRE) files from Sun Microsystems (www.sun.com) are installed as required (see JRE Components Included in Installation). The JRE is a set of computer software programs and data structures that use a virtual machine model for the execution of other computer programs and scripts.

File
Abidjan, Accra, Adak, Addis_Ababa, Adelaide, Aden, Algiers, Almaty, Amman, Amsterdam, Anadyr, Anchorage, Andorra, Anguilla, Antananarivo, Antigua, Apia, Aqtau, Aqtobe, Araguaina, Argentina, Aruba, Ashgabat, Asmara, AST4, AST4ADT, Asuncion, Athens, Atikokan, Auckland, awt.dll, axbridge.dll, Azores
Baghdad, Bahia, Bahrain, Baku, Bamako, Bangkok, Bangui, Banjul, Barbados, Beirut, Belem, Belgrade, Belize, Berlin, Bermuda, Bishkek, Bissau, blacklist, Blanc-Sablon, Blantyre, Boa_Vista, Bogota, Boise, Brazzaville, Brisbane, Broken_Hill, Brunei, Brussels, Bucharest, Budapest, Buenos_Aires, Bujumbura
cacerts, Cairo, calendars.properties, Cambridge_Bay, Campo_Grande, Canary, Cancun, Cape_Verde, Caracas, Casablanca, Casey, Catamarca, Cayenne, Cayman, Center, CET, Ceuta, Chagos, charsets.pack, Chatham, Chicago, Chihuahua, Chisinau, Choibalsan, Chongqing, Christmas, chrome, chrome.manifest, CIEXYZ.pf, classlist, client, cmm.dll, Cocos, Colombo, Comoro, Conakry, content, content-types.properties, Copenhagen, COPYRIGHT, Cordoba, Costa_Rica, CST6, CST6CDT, Cuiaba, Curacao, Currie, cursors.properties
Dakar, Damascus, Danmarkshavn, Dar_es_Salaam, Darwin, Davis, Dawson, Dawson_Creek, dcpr.dll, Denver, deploy.dll, deploy.pack, deploytk.dll, Detroit, Dhaka, Dili, Djibouti, dnsns.jar, Dominica, Douala, dt_shmem.dll, dt_socket.dll, Dubai, Dublin, DumontDUrville, Dushanbe
Easter, Edmonton, EET, Efate, Eirunepe, El_Aaiun, El_Salvador, Enderbury, EST, EST5, EST5EDT, Eucla, eula.dll
Fakaofo, Faroe, ffjcext.zip, Fiji, flavormap.properties, fontconfig.98.bfc, fontconfig.98.properties.src, fontconfig.bfc, fontconfig.properties.src, fontmanager.dll, Fortaleza, Freetown, Funafuti
Gaborone, Galapagos, Gambier, Gaza, Gibraltar, Glace_Bay, GMT, GMT+1, GMT+10, GMT+11, GMT+12, GMT+2, GMT+3, GMT+4, GMT+5, GMT+6, GMT+7, GMT+8, GMT+9, GMT-1, GMT-10, GMT-11, GMT-12, GMT-13, GMT-14, GMT-2, GMT-3, GMT-4, GMT-5, GMT-6, GMT-7, GMT-8, GMT-9, Godthab, Goose_Bay, Grand_Turk, GRAY.pf, Grenada, Guadalcanal, Guadeloupe, Guam, Guatemala, Guayaquil, Guyana
Halifax, Harare, Harbin, Havana, Helsinki, Hermosillo, Ho_Chi_Minh, Hobart, Hong_Kong, Honolulu, Hovd, hpi.dll, hprof.dll, HST, HST10
Indiana, Indianapolis, indicim.jar, install.rdf, instrument.dll, Inuvik, invalid32x32.gif, ioser12.dll, Iqaluit, Irkutsk, Istanbul
j2pcsc.dll, j2pkcs11.dll, jaas_nt.dll, Jakarta, Jamaica, java-rmi.exe, java.dll, java.exe, java.policy, java.security, java_crw_demo.dll, javacpl.cpl, javacpl.exe, javaw.exe, javaws.exe, javaws.pack, javaws.policy, jawt.dll, Jayapura, jbroker.exe, jce.jar, JdbcOdbc.dll, jdk_header.png, jdwp.dll, Jerusalem, jkernel.dll, jli.dll, jmxremote.access, jmxremote.password.template, Johannesburg, Johnston, jp2iexp.dll, jp2launcher.exe, jp2native.dll, jp2ssv.dll, jpeg.dll, jpicom.dll, jpiexp.dll, jpinscp.dll, jpioji.dll, jpishare.dll, jqs.conf, jqs.exe, jqs_plugin.dll, jqsmessages.properties, jqsnotify.exe, jsound.dll, jsoundds.dll, jsse.jar, jsse.pack, jucheck.exe, Jujuy, Juneau, jureg.exe, jusched.exe, jvm.cfg, jvm.dll, jvm.hprof.txt
Kabul, Kaliningrad, Kamchatka, Kampala, Karachi, Kashgar, Kathmandu, Kentucky, Kerguelen, keytool.exe, Khartoum, Kiev, Kigali, kinit.exe, Kinshasa, Kiritimati, klist.exe, Knox, Kolkata, Kosrae, Krasnoyarsk, ktab.exe, Kuala_Lumpur, Kuching, Kuwait, Kwajalein, La_Paz, La_Rioja, Lagos, Libreville
LICENSE, LICENSE.rtf, LICENSE_de.rtf, LICENSE_es.rtf, LICENSE_fr.rtf, LICENSE_it.rtf, LICENSE_ja.rtf, LICENSE_ko.rtf, LICENSE_sv.rtf, LICENSE_zh_CN.rtf, LICENSE_zh_TW.rtf, Lima, Lindeman, LINEAR_RGB.pf, Lisbon, local_policy.jar, localedata.pack, logging.properties, Lome, London, Lord_Howe, Los_Angeles, Louisville, Luanda, Lubumbashi, LucidaBrightDemiBold.ttf, LucidaBrightDemiItalic.ttf, LucidaBrightItalic.ttf, LucidaBrightRegular.ttf, LucidaSansDemiBold.ttf, LucidaSansRegular.ttf, LucidaTypewriterBold.ttf, LucidaTypewriterRegular.ttf, Lusaka, Luxembourg, lzma.dll
Macau, Maceio, Madeira, Madrid, Magadan, Mahe, Majuro, Makassar, Malabo, Maldives, Malta, management-agent.jar, management.dll, management.properties, Managua, Manaus, Manila, Maputo, Marengo, Marquesas, Martinique, Maseru, Mauritius, Mawson, Mayotte, Mazatlan, Mbabane, McMurdo, Melbourne, Mendoza, Menominee, Merida, messages.properties, messages_de.properties, messages_es.properties, messages_fr.properties, messages_it.properties, messages_ja.properties, messages_ko.properties, messages_sv.properties, messages_zh_CN.properties, messages_zh_HK.properties, messages_zh_TW.properties, MET, meta-index, Mexico_City, Midway, Minsk, Miquelon, mlib_image.dll, Mogadishu, Monaco, Moncton, Monrovia, Monterrey, Montevideo, Monticello, Montreal, Montserrat, Moscow, MST, MST7, MST7MDT, msvcr71.dll, msvcrt.dll, Muscat
Nairobi, Nassau, Nauru, Ndjamena, net.dll, net.properties, new_plugin, New_Salem, New_York, Niamey, Nicosia, nio.dll, Nipigon, Niue, Nome, Norfolk, Noronha, North_Dakota, Nouakchott, Noumea, Novosibirsk, npdeploytk.dll, npjp2.dll, npjpi160_16.dll, npoji610.dll, npt.dll
Omsk, Oral, orbd.exe, Oslo, Ouagadougou, overlay.js, overlay.xul, pack200.exe
Pago_Pago, Palau, Palmer, Panama, Pangnirtung, Paramaribo, Paris, Perth, Petersburg, Phnom_Penh, Phoenix, Pitcairn, plugin.pack, policytool.exe, Ponape, Pontianak, Port-au-Prince, Port_Moresby, Port_of_Spain, Porto-Novo, Porto_Velho, Prague, psfont.properties.ja, psfontj2d.properties, PST8, PST8PDT, Puerto_Rico, PYCC.pf, Pyongyang
Qatar, Qyzylorda
Rainy_River, Rangoon, Rankin_Inlet, Rarotonga, README.txt, Recife, Regina, Resolute, resources.jar, Reunion, Reykjavik, Riga, Rio_Branco, Rio_Gallegos, Riyadh, Riyadh87, Riyadh88, Riyadh89, rmi.dll, rmid.exe, rmiregistry.exe, Rome, Rothera, rt.jar
Saipan, Sakhalin, Salta, Samara, Samarkand, San_Juan, San_Luis, Santarem, Santiago, Santo_Domingo, Sao_Paulo, Sao_Tome, Scoresbysund, Seoul, servertool.exe, Shanghai, Simferopol, Singapore, snmp.acl.template, Sofia, sound.properties, soundbank.gm, South_Georgia, splash.gif, splashscreen.dll, sRGB.pf, ssv.dll, ssvagent.exe, St_Helena, St_Johns, St_Kitts, St_Lucia, St_Thomas, St_Vincent, Stanley, Stockholm, sunjce_provider.jar, sunmscapi.dll, sunmscapi.jar, sunpkcs11.jar, Swift_Current, Sydney, Syowa
Tahiti, Taipei, Tallinn, Tarawa, Tashkent, task.xml, task64.xml, Tbilisi, Tegucigalpa, Tehran, Tell_City, thaiim.jar, Thimphu, THIRDPARTYLICENSEREADME.txt, Thule, Thunder_Bay, Tijuana, Tirane, tnameserv.exe, Tokyo, Tongatapu, Toronto, Tortola, Tripoli, Truk, Tucuman, Tunis, tzmappings
UCT, Ulaanbaatar, unicows.dll, unpack.dll, unpack200.exe, Urumqi, US_export_policy.jar, Ushuaia, UTC, Uzhgorod
Vaduz, Vancouver, verify.dll, Vevay, Vienna, Vientiane, Vilnius, Vincennes, Vladivostok, Volgograd, Vostok
w2k_lsa_auth.dll, Wake, Wallis, Warsaw, Welcome.html, WET, Whitehorse, win32_CopyDrop32x32.gif, win32_CopyNoDrop32x32.gif, win32_LinkDrop32x32.gif, win32_LinkNoDrop32x32.gif, win32_MoveDrop32x32.gif, win32_MoveNoDrop32x32.gif, Winamac, Windhoek, Winnipeg, wsdetect.dll
Xusage.txt, Yakutat, Yakutsk, Yekaterinburg, Yellowknife, Yerevan, YST9, YST9YDT, Zaporozhye, zip.dll, ZoneInfoMappings, Zurich

Windows Installer Custom Actions

The technical details of each Windows Installer Custom Action executed during the Pervasive PSQL installation process are available to System Administrators. This information is listed in the document PSQL_CA_Reference.rtf, which is embedded in the Pervasive PSQL MSI installation packages.

Administrators can view and print the RTF content from the "Custom Action Reference" dialog which is only displayed during an Administrative Installation. An administrative Installation can be launched the following ways.

Using InstallShield Launcher Program (Setup*.exe)

  1. Click Start -->Run --> {path}\SetupInstallType_xPlatformType.exe /a
  2. Click Next to display the Custom Actions Reference dialog.
  3. Click Print to print the RTF document.

Using Microsoft Windows Installer (MSI) Process Only

  1. Click Start -->Run --> msiexec.exe /a {path}\PervasivePSQLv10_InstallType_xPlatformType.msi /leom {path}\LogFileName.log
  2. Click Next to display the Custom Actions Reference dialog.
  3. Click Print to print the RTF document.

Log Files Stored at Root

The Pervasive PSQL Server installation stores the following log files on the system drive in the folder C:\exts:

Files Requiring Administrator Privileges

The following files require Administrator privileges to run.

Files Not Installed To The Applications Directory

The following files do not install to the applications directory:

Files Without Valid Version Information

The following files, which are part of the Java Runtime Environment (JRE), do not contain valid file version information:

Icon Resource Files With an EXE File Extension

Microsoft Windows Installer (MSI) contains icon resource files with a file name extension of “exe.” Note that these files, despite the file name extension, are not executable files.

Such files are located in the %windir%\Installer\{install_type_product_code}\ directory.

For example, in that directory you might see files with names similar to c:\Windows\Installer\{0A3238D7-AC64-1010-B717-F3E3F18B4A8C}\ARPPRODUCTICON.exe and c:\Windows\Installer\{0A3238D7-AC64-1010-B717-F3E3F18B4A8C}\pvswDocsShortcut.A01E0590_D2E0_43CE_B351_BB16EA0FBDE0.exe.

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