Pervasive PSQL v10 - README
General Release - September 2007

Contents

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

Installation Notes

This section discusses situations you may encounter installing the product.

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 that is provided on the product installation media.

Note the following when installing to Windows:

Subject
Discussion
Hardware and software requirements
The software and hardware requirements for Pervasive PSQL v10 are listed on the Pervasive Software web site.
See http://www.pervasive.com/psqlv10/v10systemrequirements.asp
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 differs in Pervasive PSQL v10 from previous releases. This change allows the Pervasive PSQL products to adhere to installation guidelines provided by the operating system vendor.
Installation now 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.
Upgrading
Any previous Beta versions of Pervasive PSQL v10 must be uninstalled prior to installing this General version.
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.
Complimentary data management products
Pervasive Backup Agent 1.2 and Pervasive AuditMaster 6.4 are compatible with Pervasive PSQL v10. Refer to the readme file for each product for further information.
Service names
The display names of the Pervasive PSQL transactional and relational services have changed. The display name is what you see in Pervasive PSQL Control Center and in Windows Services, for example. The service names—the name that identifies the service to the operating system—remain the same.
Note that, because the service names remain the same, any scripts or applications that start or stop the Pervasive PSQL services should work as before. The service names for the transactional and relational interfaces are still Pervasive.SQL (transactional) and Pervasive.SQL (relational), respectively.
See “Service Names” in What’s New in Pervasive PSQL for details.
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 certain Windows 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 2000 Service Pack
The Microsoft Windows Installer requires version 3.1, which means that Windows 2000 must have at least service pack 3. The Pervasive PSQL installation, however, requires that Windows 2000 has service pack 4. If your Windows 2000 is below service pack 3, upgrade it to service pack 4.
Silent install
The installation for the Java Runtime Environment (JRE) Standard Edition does not run in silent install mode. If you want to install Pervasive PSQL silently and use Pervasive Control Center or Javahelp documentation, you should first run a JRE installation before installing Pervasive PSQL.
To determine when a silent install has finished, you may use either of the following methods:
1. Modify the command passed to the Windows Installer Process (msiexec.exe) to have the Pervasive PSQL install run with one of the standard UI options such as /qb, /qb!, /qb+, /qb-, /qb, and so forth. More specific information on MSI UI levels is available on the Microsoft Developer Network (MSDN) Library on the Web.
Note that everything after the setup.exe command line option /v is passed to msiexec.exe. See also the Macrovision Helpnet Web site for additional information on how to pass msiexec.exe command line options via the InstallShield launcher (setup.exe).
2. Create a log file during the silent install and then parse the log file. For example, the command line below will create a log file named "PSQL_v10_Install.log" in the TEMP directory.
setup.exe /s /v"/qn /L*v \"%TEMP%\PSQL_v10_Install.log\""
Parse the log file for the string "completed successfully." If this string is found, the silent install has finished.

Usage Notes

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

See also Known Issues.

Subject
Discussion
DDF Builder
Use DDF Builder only with a local database engine. Using the utility with a remote connection to the engine is not recommended.
Pervasive System Analyzer (PSA)
With Pervasive PSQL v10, PSA does not provide the functionality to archive, restore, or delete archives or components. The Pervasive PSQL uninstall program now handles all deletion requirements.
The PSA functionality “View loaded Pervasive modules” does not list 64-bit Pervasive PSQL components.
ODBC Administrator on 64-bit Platforms
Windows 64-bit operating systems contain two different executable files for ODBC Administrator, a 64-bit version and a 32-bit version. The Windows Control Panel uses the 64-bit ODBC Administrator. (The Pervasive PSQL drivers are not listed in the 64-bit ODBC Administrator.)
Because Pervasive PSQL provides only 32-bit ODBC support, you need to use the 32-bit ODBC Administrator to add a system data source name (DSN) for a Pervasive Engine or Client driver.
You can start the 32-bit ODBC Administrator from the Pervasive PSQL Control Center, or run the executable directly. The executable is located in windows_directory\sysWOW64\odbcad32.exe.
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 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 Vista, 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 Vista documentation for security and types of users.
Internet protocol on 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.
Patches for Windows Vista
The Pervasive PSQL XIO driver experiences incompatibility with the Windows Vista patches that were provided in April, 2007. If you last patched Windows Vista with the April patches, please update Vista with the most current patches. No incompatibility with XIO exists with the most current Vista patches.
File operations on Windows Vista
With the Windows Vista patches that were provided in April, 2007, you may notice lengthy delays for file operations such a deleting, moving, or copying, and refresh rates may be very slow for certain activities such as product uninstalls. If you last patched Windows Vista with the April patches, please update Vista with the most current patches.
Right-click shortcut for "Run As Administrator" on 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 Vista.
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.

New Features and Enhancements

Refer to What’s New in Pervasive PSQL for a discussion of the new features and enhancements included with this release.

Known Issues

This section lists the known issues for Pervasive PSQL v10.

Component Area
Tracking Number
Description
Installation
54957
DDF Builder can be installed as part of a client install but is supported only on a local system and cannot access data paths of databases on remote server.
Work-around: Install DDF Builder on a local machine where the database engine is installed and the data files reside.
55169
Very long paths for installation destination results in error 1320.
Work-around: Use a path less than 121 characters.
55194
In certain custom installation situations, the product install does not properly detect the exact amount of disk space required. As a result, install may run out of disk space during installation.
Work-around: Ensure that the target disk has at least 200 MB of free space prior to installation.
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.
56004
PCC and DDF Builder are not functional when added with install "Modify" operation.
Work-around: Uninstall and reinstall all of PSQL.
56091
A silent install reboots after installation if the target machine meets the requirements for XIO and is running the Windows 2000 operating system.
Work-around: Use the following command line for the silent installation to prevent the reboot:
server32>SetupServer_x86.exe /s /v"/qn REBOOT=ReallySuppress /l*v c:\install.log"
Utilities
54785
BDU utility fails when the secured database password is longer than 111 characters.
54937
Deleted key not refreshed on the Create New Btrieve File grid in Function Executor utility.
55396
The PSA functionality “View loaded Pervasive modules” does not list 64-bit Pervasive PSQL components.
55901
Incomplete path displayed while loading, copying, or saving data in Btrieve Maintenance utility.
55969
XIO requires a minimum of 2GB of RAM for installation. If a machine was installed without XIO due to insufficient memory, but subsequently more memory was added to that machine, the install "Repair" option will not add the XIO component even though the machine now meets the 2GB minimum memory requirement.
Work-around: Uninstall and reinstall the product.
Utilities (DDF Builder)
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.
55960
DDF Builder encounters error when operating on files that are held open exclusively by another process.
Work-around: Ensure that the files are not held open exclusively by another process.
Utilities (PCC)
53977
F1 in PCC fails to load the Help page if called the second time on XP only.
Workaround: Close the help window, click the Pervasive PSQL Explorer window, then press F1. Once help invokes the second time, subsequent invocation is fine.
54786
Index dropped using butil utility results in an error in PCC while editing the table.
54990
Some configuration settings in PCC are missing from a virtual network computing (VNC) session.
Work-around: 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.
Work-around: Use views or SELECT statements to limit the number of fields displayed in the grid.
55576
PCC returns "Failed to execute runnable (java.lang.OutOfMemoryError: Java heap space)" error for some large data sets.
Work-around: Increase the amount of memory available to PCC during start up. The amount of memory you can specify is limited by the physical memory installed on your machine. You can specify a minimum and a maximum amount of memory. For example, to specify a minimum and maximum of 256 megabytes, start PCC with the following command:
pcc.exe -vmargs -Xms256M -Xmx256M
The parameter -vmargs is required if you specify the other parameters.
The parameter -Xms specifies the minimum amount of memory to allocate to PCC. The parameter -Xmx specifies the maximum amount of memory to allocate to PCC. If you specify the -Xms parameter, you must also specify the -Xmx parameter.
SQL
55759 (and 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.
Work-around: 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.
55955
Psp_columns returns (null) for data type, type name, length, and so forth on columns created with data type UNIQUEIDENTIFIER.
Software Development Kit (SDK)
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.
Work-around: Use MSDASQL Provider instead.
Data Archival
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.
Work-around: 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.
JavaHelp
55246
The JavaHelp search feature does not correctly highlight the search term. This is a known defect in the JavaHelp viewer and is not caused by the Pervasive PSQL documentation.

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

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

*** END OF README ***