Pervasive.SQL 9 Service Pack 1 (9.1) - README - General Release

This release delivers a number of new features and functionality to Pervasive.SQL as described in New Features and Enhancements.

Note: The Installation Notes section contains important information to help you install successfully. Please read this section before attempting to install Pervasive.SQL 9 SP1 (9.1) or alter your existing configuration in any way.

Installation Notes

This release has been tested in a variety of configurations. After reading these notes, see Getting Started with Pervasive.SQL 9 SP1 (9.1) for installation steps.

Compatibility with Other Releases

This section contains important information about Pervasive.SQL 9 SP1 (9.1) and support of other Pervasive products.

This release supports Pervasive AuditMaster v6.3, DataExchange v2.8, and Backup Agent v1.1. This release does not support Pervasive AuditMaster v6.2, DataExchange v2.7, or Backup Agent v1.0.

If you are using AuditMaster v6.2, DataExchange v2.7, or Backup Agent v1.0 with Pervasive.SQL V8.6, following these steps to upgrade Pervasive.SQL V8.6 to Pervasive 9 SP1 (9.1):


Step	Action
1.	Modify the Registry and add a key that will allow the upgrade. For AuditMaster, add this key: [HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\AuditMaster Server\v9_upgrade] For DataExchange, add this key: [HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Pervasive.SQL Replication\v9_upgrade] For Backup Agent, add this key: [HKEY_LOCAL_MACHINE\SOFTWARE\Pervasive Software\Products\Backup Agent\v9_upgrade] Note: Each product requires its own key. For example, if you are using all three products, add all three keys. If you prefer not to edit the Registry manually, contact Pervasive Support and request a Registry update file (.reg file). The Support representative will advise you on using the file. See http://www.pervasive.com/company/contact/index.asp for contact information.
2.	Upgrade Pervasive.SQL V8.6 to Pervasive.SQL 9 SP1 (9.1). See Getting Started with Pervasive.SQL 9 SP1 (9.1) (Server Edition).
3.	Upgrade AuditMaster v6.2 to Pervasive AuditMaster v6.3 Upgrade DataExchange v2.7 to DataExchange v2.8 Upgrade Backup Agent v1.0 to Backup Agent v1.1

Existing OLE DB Provider On Clients

Version 8.6 OLE DB clients (supplied with Pervasive.SQL V8 SP2 (8.60)) are compatible with the Pervasive.SQL 9 database engine. You do not need to update the clients if this provider is the only client component used.

Version 8 OLE DB clients (supplied with Pervasive.SQL V8 or V8 SP1) may be used with the Pervasive.SQL 9 database engine provided that you register CNSTING.DLL on the server (regsvr32 cnsting.dll). Once this DLL is registered, you do not need to update the clients if this provider is the only client component used.

Existing OLE DB Provider On Server

If you use the OLE DB provider on the database engine Server or Workgroup, an update to the provider is required. This version is an updated 8.6 provider. Visit http://www.pervasive.com/developerzone/access_methods/oledbado.asp for status on an updated provider that supports Pervasive.SQL 9.

Running Pervasive.SQL 9 Client Install On A Client

The OLE DB provider is no longer provided within the client install. If you need the provider on the client, you may download the version 8.6 of the OLE DB client provider from http://www.pervasive.com/developerzone/access_methods/oledbado.asp.

Server and Client Installs in Windows

The Pervasive.SQL Server and Client installations are separate in Pervasive.SQL 9 SP1 (9.1). You can no longer install clients from a server installation unless you add the client install manually to your installed Pervasive.SQL 9 SP1 (9.1) server installation.

Instead, use the separate Client installation program provided on the download Web page or use the following procedure to recreate the configuration of Pervasive.SQL v8.5.

To add the client install image to a server install

Windows

You must have Administrator rights to install this product.

Windows 95 is not supported. You must have at least Windows 98 to install Pervasive.SQL 9 SP1 (9.1).

If you are installing a downloaded version of Pervasive.SQL, do not place the setup files in a location that is listed in the PATH environment variables, as this can cause issues with file copying during install. Place the setup files in a location such as the Windows TEMP directory.

You cannot install Pervasive.SQL from a terminal server session. You must be on the console of the server to install.

You need Internet Explorer 4.01 SP2 or later in order to install the product due to a requirement from Windows Installer. You also need Internet Explorer to view the online documentation in CHM format, and use the Network troubleshooting features of PSA. To determine if your Internet Explorer version is adequate, select Help | About Internet Explorer from a browser window and ensure that the version displayed is 4.72.3612.1713 or higher.

When installing to Windows 98 SE, you may encounter an issue if the PATH environment variable is too long, as the Pervasive.SQL installation program may be unable to modify the PATH to add the Pervasive BIN directory. If you encounter issues after installing to Windows 98 SE even if install reports success, check your PATH statement and, if necessary, manually add <installed_drive>:\PVSW\BIN to your PATH.

A local security policy in Windows XP Professional “Sharing and security model for local accounts” can adversely affect network logins. Under the default policy, all network logins to local accounts are authenticated as Guest, no matter what credentials were supplied. This causes your authorization for databases using Mixed or Database mode not to match your OS credentials and can prevent data access you intended to authorize. To resolve this condition, ensure that your policy for “Sharing and security model for local accounts” is set to Classic, which authenticates users as themselves. Windows 2003 already has a default setting of Classic. Windows XP Professional has a default setting of Guest, and Windows 2000 and earlier releases do not have this security policy. To find this policy in Windows XP, browse to Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options.

Windows 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.SQL silently and use Pervasive Control Center or Javahelp documentation, you should first run a JRE installation before installing Pervasive.SQL.

A silent install results in the following anomalies:

The Add/Remove Programs does not show the Pervasive.SQL 9 icon

PSA does not remove the Pervasive.SQL 9 entry from Add/Remove Programs

PSA does not remove the Pervasive.SQL 9 entry from the Start --> Programs menu.

To correct these anomalies, pass the argument ALLUSERS=1 in the installation command:

setup.exe /s /v"/qn ALLUSERS=1"

To determine when a silent install has finished, you may use either of the following methods:

Check VersionLevel in the following registry key:

HKEY_LOCAL_MACHINE\Software\Pervasive Software\Products\Product name\InstallInfo\VersionLevel

VersionLevel is 9.10 if the silent install has finished.

Product name is Pervasive.SQL NT Server for the Server product, Pervasive.SQL Workgroup for the Workgroup product, and Pervasive.SQL Client for the client requester.

Create a log file during the silent install and then parse the log file. For example, the following command creates a log file named “install.log”:

setup.exe /s /v"/qn /L* \"%WINDIR%\install.log\""

The log file is in Unicode format on Windows 32-bit platforms and in ASCII format on Windows 9x and ME platforms.

Parse the log file for the string "completed successfully." If this string is found, the silent install has finished.

Using the Registration Page on Windows XP SP2

The default security settings on Windows XP SP2 can prevent Internet Explorer from running scripts within HTML. You may notice this if you attempt to use the Pervasive.SQL registration page that appears at the end of installation.

“To help protect your security, Internet Explorer has restricted this file from showing active content that could access your computer. Click here for options...”

Restoring a Previous Version of Pervasive.SQL with PSA

If you install Pervasive.SQL 9 SP1 (9.1) then decide to restore your previous version of Pervasive.SQL 8.x, complete the following steps:

Uninstall Pervasive.SQL 9 SP1 (9.1) as explained in the Getting Started guide for the product.

Manually delete the following registry key:

HKEY_LOCAL_MACHINE\Software\Pervasive Software\Products\Product name\InstallInfo

Product name is Pervasive.SQL NT Server for the Server product, Pervasive.SQL Workgroup for the Workgroup product, and Pervasive.SQL Client for the client requester.

To edit the registry, click Start then Run. Type regedit and click OK. Expand the HKEY_LOCAL_MACHINE node until you locate the key as described above. Right-click on InstallInfo then click Delete. Exit the registry.

Restore Pervasive.SQL 8.x as explained in the chapter “Pervasive System Analyzer (PSA)” in Pervasive.SQL User’s Guide.

Uninstalling

Messages about failing to unregister DLLs appear during the uninstall process. Click OK for these messages to proceed. The uninstall process does successfully unregister these DLLs from your system and delete them.

NetWare

Linux

New Features and Enhancements


Feature	Description
Utilities for Linux: Pervasive.SQL Control Center (PCC) bcfg bmon	PCC is an easy-to-use, graphical tool designed to help you control your DBMS. As an integrated framework, it allows you to connect to database engines, set up and modify databases and tables, query and update data, and tune engine performance. See Chapter 3, “Using Pervasive.SQL Control Center,” in Pervasive.SQL User’s Guide. Bcfg is a command-line utility that allows you to change your configuration settings for Server or Client. See the section “Configuration Through CLI Utility” in Advanced Operations Guide. Bmon is a command-line utility that allows you to monitor database resources. See the section “Command Line Interface Monitor” in Advanced Operations Guide.
Separate installations for Server, Client, PCC, and JavaHelp on Linux	Separate RPM and TAR files allow you to install Pervasive.SQL Server, Client, PCC, or JavaHelp. Pervasive.SQL Server or Client is required to install PCC. Java Runtime Edition (Standard Edition) 5.0 or greater is required to run PCC or the JavaHelp. See Part 4, “Installing Components for Linux,” in Getting Started with Pervasive.SQL 9 SP1 (9.1) (Server Edition).
Documentation for Pervasive.SQL Software Development Kit (SDK) included in documentation set	Preliminary SDK documentation is installed as part of the standard documentation set. By default, the SDK documentation does not appear in the JavaHelp viewer. Alter a setting in preferences.ini if you wish to access the SDK documentation from the viewer. See “Customizing the Help System” in What’s New.
Enhancements to Ptksetup.ini	Ptksetup.ini is part of the SDK Installation Toolkit. See Ptksetup.ini in Documentation Notes.

Environments Supported

Server Engine

Workgroup Engine

Clients

Known Issues

This section documents the known issues for this release. These issues are priority candidates for the first service pack release of Pervasive.SQL. The issues are organized alphabetically by component area, then numerically by tracking number within the component area.


Component Area	Tracking Number	Description
Documentation	51002	Searching the JavaHelp index for status codes displays all status codes that contain that value
DTI	51709	PvCreateDictionary() API returns general error on Linux client. The API returns PCM_errFailed(1).
	51710	PvOpenDictionary() API returns general error on Linux client. API returns PCM_errFailed(1).
	51926	PvUnSecureDatabase() DTI API fails to remove security from a secured database on Linux
Installation	51204	A popup message may appear at the end of the uninstall process on Windows stating that files cannot be unregistered
	51374	Ptksetup.ini sets SplashScreen=Yes when the default should be “No”
	51880	Trial license installed if Pervasive.SQL Server installed on NetWare, uninstalled, and then re-installed, even if initial installation provides valid permanent license
	51937	Graphic images used in the installation screens may look compressed
MKDE	51029	PvCopyDatabase() can copy only the data files from the first part of multiple data paths not from the second part
	51577	Variable name cannot be used as a table name when creating the table within a stored procedure
	51809	Linux only: using URI strings to repeatedly connect to the database engine (heavy stress) can crash the engine
PCC	50672	A view cannot be created on a table if the table has columns names that contain only spaces. Workaround: Do not create column names that contain only spaces.
	51376	The “communications protocols” property should read ODBC TCP/IP port, not just TCP/IP port
	51423	When retrieving very large data sets into its grid, PCC slow down significantly or return "out of memory" errors. You must restart PCC if this problem occurs. Workarounds: If the data does not need to be edited, execute the query to the text window instead of the grid. Reduce the memory requirements by narrowing the number of fetched records using a WHERE clause in the SELECT statement or by specifying a specific few columns from a table. Increase the memory available to PCC by adding the following flags when starting PCC: -vmargs -Xms256M -Xmx256M where 256 is the amount of memory you want to specify. Example: pcc -vmargs -Xms256M -Xmx256M
	51688	Error “You are not authorized to perform this operation” occurs after creating a group and then trying to modify the group permissions for create stored procedure and create view
	51786	PCC used with Pervasive.SQL Workgroup prohibits two configuration settings from being set correctly: TCP Port Number and Limit Segment Size to 2 GB
	51942	Error message "Unexpected error occurred" occurs when trying to open a view with spaces in the view name
PSA	51893	PSA clean up no longer runs on NetWare during installation
SQL	22579	Under certain conditions using ODBC, the 9.1 client shows performance degradation. Contact Pervasive Support if you notice extreme performance degradation.
	51268	Renaming user-defined functions not working correctly
	51313	An error synchronizing metadata may occur if clients other than the database engine modify the cache of metadata used by the engine. In such cases, the engine is not aware of the modification. Applications that use the relational and DTI interfaces may experience errors if the metadata is modified by other interfaces without restarting the engine.
Utilities	50961	Misspellings in the help for the pvddl command-line utility
	51208	Cobolschemaexec returns error messages difficult to understand
	51219	Cobolschemaexec does not work correctly on Netware 5.1
	51795	DDF Builder returns “7004: General failure code” if relational and transactional services fail
	51920	PCC grid show incorrect number of rows for a Cobol table that contains OCCURS constructs
Data Exchange	51628	Unknown error results when attempting to view properties of a dynamic table Workaround: restart the database engine
Data Exchange	51653	Properties display incorrect file path when an absolute path is specified in the “include path” attribute of the XML file used for deployment

Documentation Notes

This section provides information regarding the documentation included with the Pervasive.SQL 9 SP1 (9.1) product.

Status Code 11

Your application may receive a status code 11, “The specified filename is invalid,” because of the default setting for embedded spaces. The default, new with Pervasive.SQL 9, is “on.” If your applications do not permit embedded spaces in file names, change the “embedded spaces” setting to “off.” See the chapter “Configuration Reference” in Advanced Operations Guide.

Documentation Formats

The documentation is now provided in three different formats: JavaHelp, HTMLHelp, and portable document format (PDF). On Windows platforms, the JavaHelp and HTMLHelp formats are installed by default with the product. The PDF files reside on the installation media.

JavaHelp

The Pervasive.SQL Control Center utility is now a Java application. Help requests from the new utility use JavaHelp. The first time that you invoke help from within a PCC session, you may notice a slight delay as the JavaHelp system instantiates. This delay occurs only for the initial instantiation.

You may also access the JavaHelp independently from the PCC. To do so, perform one of the following:

Windows

Execute the batch file pvswdocs.bat located in the folder pvsw\bin\plugins\com.pervasive.help.ui_1.0.0.

You can also start the JavaHelp by navigating the commands for the Pervasive program on the Start menu.

Windows 98/ME

You may notice on a Windows 98/ME platform that the DOS widow remains open after you exit JavaHelp. To ensure that the DOS window closes, set the “close on exit” property for the batch file. In Windows Explorer, right-click on pvswdocs.bat then click Properties. Click the Program tab. Click the option “Close on exit” then click OK.

Linux

The JavaHelp documentation is a separate installation for Linux. To run the Javahelp, you must have a variable set for the following:

If a JAVA_HOME environment variable is set, Pervasive.SQL JavaHelp assumes that the Java executable is at $JAVA_HOME/bin/java. JAVA_HOME is not set by the JRE install. Other vendors require a JAVA_HOME variable so it may be set on your system. If it is, then it takes precedence over any PATH statements.

Without a JAVA_HOME, Pervasive JavaHelp assumes that the PATH environment variable contains the location of your JRE’s bin directory. For example, the PATH would include something similar to the following:

Some Linux distributions include gcj, a GNU compiler for the Java programming language. If your Linux distribution includes the gcj compiler, check your PATH environment variable. Ensure that the path to the Standard Edition JRE appears before the path to the gcj or that you have a JAVA_HOME variable set to the Standard Edition.

HTML Help and Internet Explorer

This release includes support for Microsoft HTML Help (files with .CHM extension). These files support utilities that have not been converted to Java.

HTML Help uses components of the Internet Explorer (IE) engine to display help files. A defect in the early versions of IE 5 (and some 5.5 versions) causes display irregularities with modular HTML Help systems. These display conditions may be seen in PVSWDOCS.CHM, the master help file for Pervasive.SQL 9 SP1 (9.1) that dynamically loads the other help files. Since this defect affects only the file merging mechanism, you will see no display irregularities when loading individual help files. Some specific symptoms you may encounter are:

If you encounter any of these display conditions, the solution is to upgrade to IE 5.01 or higher. You may download version 5.01 or higher from Microsoft’s web site. You can determine your version by clicking Help | About Internet Explorer from the browser window.

If your Internet Explorer version is one of the following, or a later version, then your HTML Help should function correctly.

Windows XP Professional and XP Home includes IE 6.0. Windows 2000 and Windows ME shipped with IE 5.01 so you should not see the display irregularities on those platforms, nor with older IE 4 versions.

Viewing PDFs in a Browser

IE Version	Description
5.00.2919.6307	Internet Explorer 5.01
5.00.3105.0106	Internet Explorer 5.01 with Service Pack 1
6.00.2800.1106	Internet Explorer 6.00 with Service Pack 1

In some instances, the Acrobat Reader plugin for browsers does not render the PDF documentation correctly. You may notice gaps on pages or pages that appear to be missing. We recommend that you view the PDFs with Adobe Reader, not in a browser. The Reader is free and available as a download from www.adobe.com.

Ptksetup.ini

The Pervasive.SQL installation programs are designed so that you can perform a variety of basic customizations without having to recompile the programs. You can perform these customizations by editing the file ptksetup.ini.

The keys and sections in the ptksetup.ini file are commented to help you understand their purpose. Please refer to the ptksetup.ini installed with Pervasive.SQL 9 SP1 (9.1). The file is installed in your PVSW root directory. For example, if you installed to the default location of C:\PVSW, the INI file location would be C:\pvsw\ptksetup.ini

The following sections of the ptksetup.ini file are obsolete and changes to these sections are ignored.

SDK Notes

The documentation for the Linux requester does not mention the load order required by the Pervasive Services components, and this may lead to a program fault when unloading the core Pervasive services library.

Symptom

As your Pervasive Linux-based application closes, the requester faults when unloading the library libpscore.so.

Resolution

The problem exists if the load order is such that the PSCL library loads before the PSCORE library.

To solve this issue, add the PSCL and PSCORE libraries to your program’s make file, which will produce the correct loading order. The following statement is an example.

Useful Links

For a comprehensive list and details of Pervasive Products, see

http://www.pervasive.com/products

Review information about application development at:

http://www.pervasive.com/developerzone

For Technical Papers, see:

http://www.pervasive.com/support/techpapers.asp

For Product Manual downloads, see:

http://www.pervasive.com/support/technical/online_manuals.asp

For viewing Product Manuals online, see:

http://www.pervasive.com/library

For information on our Support programs, see

http://www.pervasive.com/support/support_programs.asp

For information on updates and Service Packs, see:

http://www.pervasive.com/support/updates

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.  
PERVASIVE SOFTWARE INC. MAKES NO OTHER WARRANTIES 
WHATSOEVER, EITHER EXPRESS OR IMPLIED, REGARDING 
THE SOFTWARE OR THE CONTENT OF THE DOCUMENTATION; 
PERVASIVE SOFTWARE INC. HEREBY EXPRESSLY STATES AND 
YOU OR YOUR COMPANY ACKNOWLEDGES THAT PERVASIVE 
SOFTWARE INC. DOES NOT MAKE ANY WARRANTIES, 
INCLUDING, FOR EXAMPLE, WITH RESPECT TO 
MERCHANTABILITY, TITLE, OR FITNESS FOR ANY 
PARTICULAR PURPOSE OR ARISING FROM COURSE OF 
DEALING OR USAGE OF TRADE, AMONG OTHERS.  
THIS APPLICATION USES THE FREE unixODBC DRIVER 
MANAGER AS WRITTEN BY PETER HARVEY 
(pharvey@codebydesign.com), MODIFIED AND EXTENDED 
BY NICK GORHAM (nick@easysoft.com), WITH LOCAL 
MODIFICATIONS FROM PERVASIVE SOFTWARE. PERVASIVE 
SOFTWARE WILL DONATE THEIR CODE CHANGES TO THE 
CURRENT MAINTAINER OF THE unixODBC DRIVER MANAGER 
PROJECT, IN ACCORDANCE WITH THE LGPL LICENSE 
AGREEMENT OF THIS PROJECT. THE unixODBC DRIVER 
MANAGER HOME PAGE IS LOCATED AT WWW.UNIXODBC.ORG. 
FOR FURTHER INFORMATION ON THIS PROJECT, CONTACT 
ITS CURRENT MAINTAINER: Nick Gorham 
(nick@easysoft.com)." 
Copyright © 2005 Pervasive Software Inc.  
All Rights Reserved.

Pervasive.SQL 9 Service Pack 1 (9.1) - README
General Release - June 2005

Contents

General Information

Installation Notes

Compatibility with Other Releases

Server and Client Installs in Windows

To add the client install image to a server install

Windows

Windows Silent Install

Using the Registration Page on Windows XP SP2

Restoring a Previous Version of Pervasive.SQL with PSA

Uninstalling

NetWare

Linux

New Features and Enhancements

Environments Supported

Server Engine

Workgroup Engine

Clients

Known Issues

Documentation Notes

Status Code 11

Documentation Formats

JavaHelp

Windows

Windows 98/ME

Linux

HTML Help and Internet Explorer

Viewing PDFs in a Browser

Ptksetup.ini

SDK Notes

Symptom

Resolution

Useful Links

Disclaimer

Pervasive.SQL 9 Service Pack 1 (9.1) - README General Release - June 2005

Contents

General Information

Installation Notes

Compatibility with Other Releases

Server and Client Installs in Windows

To add the client install image to a server install

Windows

Windows Silent Install

Using the Registration Page on Windows XP SP2

Restoring a Previous Version of Pervasive.SQL with PSA

Uninstalling

NetWare

Linux

New Features and Enhancements

Environments Supported

Server Engine

Workgroup Engine

Clients

Known Issues

Documentation Notes

Status Code 11

Documentation Formats

JavaHelp

Windows

Windows 98/ME

Linux

HTML Help and Internet Explorer

Viewing PDFs in a Browser

Ptksetup.ini

SDK Notes

Symptom

Resolution

Useful Links

Disclaimer

Pervasive.SQL 9 Service Pack 1 (9.1) - README
General Release - June 2005