Contents

1. General Information

2. NetWare Specific Notes

3. New Features

4. Installation Notes

5. Documentation Updates

6. Known Issues

7. Technical Support

8. Notices/Disclaimer

Overview

This document provides information for all customers who have purchased this release of Pervasive.SQL 2000.

Supported Operating Systems
Pervasive.SQL 2000 client/server and 32-bit workstation engines are available for:

•  Windows NT 4.0 (Service packs 1-5)
•  Windows 95 (Service Pack 1)
•  Windows 98 (first and second edition)
•  NetWare 3.2, 4.11 and up, and 5.0

The information contained in this section is specific to NetWare platforms only. However, you should read this entire readme document for other important Pervasive.SQL 2000 information that may pertain to you as well.

****IMPORTANT NOTE****
If you are installing on a NetWare 4.x or 5.x server with NDS you MUST have your Bindery Context correctly set to the NDS context in which your Pervasive.SQL 2000 server resides. By default, this will be set correctly when you install NetWare 4.x or 5.x, but it can be changed using the following command in either STARTUP.NCF or AUTOEXEC.NCF:

SET BINDERY CONTEXT = NDS Context containing the Pervasive.SQL 2000 server

If you set an invalid context, or if you execute it with NULLs in the value, Pervasive.SQL 2000 will not be able to authenticate you in the NDS tree for engine configuration and monitoring. If you need to set multiple bindery contexts for the NetWare server, the context containing the Pervasive.SQL 2000 server must be first in the list.

NOVELL NETWARE RIGHTS FOR PERVASIVE.SQL 2000:

• Rights required to install:

To install Pervasive.SQL 2000 on a NetWare server you should be an administrator of the server object on which you are installing the database. Just having supervisor rights is not adequate. This will allow you to configure, monitor, and set up DSNs for the server after installation. However, you can do an installation if you just have read/write rights to the root of the server, but you will NOT be allowed to configure, monitor, and add DSNs.
• Simplest method to authorize users to administer databases:

All other users that are administrators for the NetWare server object where Pervasive.SQL 2000 is installed will have rights to perform administrative functions on the database too. This means the user must have Supervisor rights to the NDS Server object itself, not just Supervisor rights to the SYS: volume. This implementation is the easiest to set up and administer and is adequate if your users can be administrators for both the NetWare server and the Pervasive.SQL 2000 database.
• Alternative and more restrictive method to authorize users to administer databases:

After installation you can optionally add a group named Pervasive_Admin and add members who have the right to administer only the database engine without giving them full administrative rights on the entire server. In order to add this group and add users to it, you must have the proper Novell NetWare rights enforced by NetWare to add objects into the NDS tree on NetWare 4.x or later or create groups on NetWare 3.2. On NetWare 4.x or later, the Pervasive_Admin group object must be set up in the same NDS container as the server (or servers) with Pervasive.SQL 2000 installed. If all your Pervasive.SQL 2000 servers are installed at the same level in your NDS tree, then only one Pervasive_Admin group is required for all of them. If you have multiple Pervasive.SQL 2000 servers at varying levels in your NDS tree, you must set up multiple Pervasive_Admin groups, one for each NDS context level running a Pervasive.SQL engine. You do not need to have the same member list for each Pervasive_Admin group. On NetWare 3.2, the group Pervasive_Admin must be set up on the same server that has Pervasive.SQL 2000 installed
• If you have additional questions on this topic or would like to review examples of NDS trees and user rights, please refer to the section "Additional Information on Pervasive_Admin and NDS" in the HTML file:

http://www.pervasive.com/support/technical/papers/psql2kftf.html

• The Netware relational engine can accept connections from remote clients using only 1 homogenous protocol at a time. Your Netware Pervasive.SQL 2000 ODBC engine is by default configured to accept TCP/IP connections only. If you do not have an entry in your client's "hosts" file, or in your DNS server's tables, for the Netware server you are connecting to, you may receive connect errors such as a status 3103.


If you want to connect using IP, you must do one of the following:

• Add the NW server's name/address into your DNS server's tables;
• Add the NW server's name/address into your local hosts file (\winnt\system32\drivers\etc\hosts for NT, \windows\hosts for 95/98); or
• Specify the actual IP address in the client DSN's "Server Address" field.


If you want to connect using SPX, you must either:

• Use Pervasive Control Center Configuration Utility to change the SQL engine's Supported Protocols; or
• Edit the file in sys:\odbc\odbc.ini on your Netware server and set

[SQLManager]
MgrUseTransport=SPX

• NetWare 3.x only: The NetWare Loadable Module TLI.NLM must be loaded on the server before starting Pervasive.SQL 2000, in order for the products to function correctly. Later versions of NetWare should have loaded this module automatically; however, in any version of NetWare, the module must be loaded for Pervasive.SQL 2000 to function correctly.

• All versions of NetWare: Before starting Pervasive.SQL 2000, the NetWare Loadable Module appropriate to the communication protocol being used must be loaded before starting Pervasive.SQL 2000. If the SPX communication protocol is being used, then SPXS.NLM must be loaded on the server before starting Pervasive.SQL 2000. If the TCP/IP protocol (the default) is being used, then TCP/IP must be correctly configured on the server before starting Pervasive.SQL 2000.

• Prior to installing Pervasive.SQL 2000, any existing Pervasive.SQL applications must be stopped on the client machines, and the Pervasive.SQL server engine must be stopped by performing the SQLSTOP and BSTOP commands from the NetWare server console. (Note: SQLSTOP is the command entered on the NetWare server console to stop the relational engine in previous versions of Pervasive.SQL. This command has changed to MGRSTOP in Pervasive.SQL 2000.)

• Please note that the command MGRSTOP may take up to a minute to unload the SQL Connection Manager. This pause does not indicate that your system is hung, only that this module takes some time to unload.

• When creating an Engine DSN on a NetWare 4.x or 5.0 server, the 'Browse' button on the 'Create Database' dialog box may set up the Dictionary and Data File Locations incorrectly.  This may happen if you are running the ODBC Administrator utility from a Windows 95 client using the Microsoft Service for NDS.  If the locations are populated with a directory path starting '\\$NDS', you must manually overwrite them with the target server name, volume name and directory in this format:

\\SERVER\VOLUME:\PATH


For example, \\MYSERVER\SYS:\PVSW\DEMODATA
Note that the ':' after the volume name is required. This works fine if you are using the Novell client.  #18371

• The NetWare MicroKernel will now automatically unlink from BTRIEVE.NLM when you run BSTOP. It will prompt you before it does this, just to be sure you have closed all connections to the server. You must realize that doing this forced unload of the MicroKernel can cause errors to be returned to any applications using it. They may get status 3s or 20s. Because the Netware Operating System uses BTRIEVE.NLM, you will not be able to unload BTRIEVE.NLM without taking down the server. This just unloads NWMKDE.NLM. But this unload will allow new configuration settings to take effect when the MicroKernel is brought back up.

3. New Features

Tech-in-the-Box
The Pervasive.SQL 2000 Tech-in-the-Box is an interactive tour of some of the new Pervasive.SQL 2000 features.

System requirements for viewing the Tech-in-the-Box are:

• Win32 operating system (Windows 95/98/NT)
• A sound card
• 32 MB of RAM
• 256 color video display

• BEFORE INSTALLING, READ THIS SECTION AND REVIEW "KNOWN ISSUES" FOR INSTALLATION, LATER IN THIS DOCUMENT.

• Pervasive IDS Server will not work after installing onto a Pervasive.SQL 2000 server until you have made some minor modifications. If you want to run these 2 products together, search the Pervasive Knowledge base for information on how to set this up. If you need further help or information call Pervasive Technical Support.

• If you have any existing Pervasive products running on your PC, you should close them completely down before installing Pervasive.SQL 2000. The install will attempt to shut down the database services on NT, but if there are any active connections, it may fail.

• If you have Pervasive.SQL 2000 Beta or Technology Preview versions installed on your PC you *must* remove them before installing this version. The best and most thorough way to do this is by running the Cleanup program that is part of your Beta CD image. This removes all components found on the machine, including registry entries and shared dll counts.

• If you choose to uninstall previous versions of Pervasive.SQL prior to installing Pervasive.SQL 2000 you should first uninstall your old Pervasive.SQL DSNs. Failure to do so will result in an inability to remove those DSNs after uninstalling.

Note:  All ODBC applications and ODBC services (e.g. SNMP) should be terminated before Install is attempted. If Install indicates that you need to "free locked ODBC files", exit Install, reboot your system and attempt Install again. If Install continues to detect locked ODBC files, call Pervasive Technical support.

1. Read Chapter 2 (Installation) of the Pervasive.SQL 2000 Getting Started to make sure you have the correct hardware configuration and to familiarize yourself with the installation process.

 2. Run the setup program for the Server, Client, or Workstation components.
 

• You may encounter installation failures (insufficient disk space) if your system is low on virtual memory or if the directory specified by the %TEMP% environment variable has very limited disk space available.

Solution: Quit all programs except the installation. Make sure that the file system containing your %TEMP% folder has at least 10 MB of free disk space, and your target installation directory has at least the amount of free space shown during the installation procedure. If the failed installation created an Uninstall program item, run it before re-starting the installation.

Note: if you are using a "temporary" Windows swap file (see the Virtual Memory section of the "System" controls in the Windows Control Panel), the required free space must still be available after the swap file has consumed the maximum amount of disk space that it is allowed. A temporary swap file may be small at startup, but is allowed to grow to its maximum size setting. What appears as "free" space may actually be reserved by the temporary swap file.

This section provides corrections or additions to the documentation shipped with the product.

• You may encounter GPFs in Winhlp32.exe if you attempt to print topics of Windows help files from the Contents menu.

Workaround: None. #14056

The most noteworthy issues are listed here. An up to date list of additional issues can be found on the Pervasive web site:

http://www.pervasive.com
or
http://www.pervasive.com/support/technical/papers/psql2kftf.html

Also see READDOS.TXT installed with this product. This document will provide more information on configuring the DOS client components.

GENERAL

• Using SPX as a transport protocol to the SQL Relational Database Engine (SRDE) requires that the client workstation be attached to at least one NetWare server. This is true for both the NetWare SRDE and the Windows NT SRDE.

• If you plan to use Pervasive's Java or ActiveX interfaces with Pervasive.SQL 2000, you must upgrade these interfaces to use the latest features shipping in the Pervasive.SQL 2000 SDK, available from Pervasive Software in July 1999.  The older interfaces will not recognize new features of Pervasive.SQL 2000 like true null support and multiple variable length columns but should continue to work with old data tables that do not exercise these new options.

• If your DBNames.cfg file is read-only, you will not be able to add DSNs or update or add named databases.

Workaround: Remove the read-only flag.  #18715

• If you stop your Pervasive database engine while database utilities are running and connected to the engine on the same machine, you will not be able to restart the database until you have closed these utilities.

• If you receive errors when creating tables that are named greater than 8 characters, first make sure that both the client and server you are using can support greater than 8.3 filenames.

• If you develop an application with Pervasive Tango you must use the default setting to put double quotes around all keywords or reserved words used in a table definition statement.

• You may experience slow responses running the Pervasive.SQL 2000 NT Server on a PC or laptop that is not connected to a network.

Workaround: Bring up the Pervasive Control Center and double-click on the Configuration Utility.  Select Expand Server Settings, and then chose Communications Protocols. The second setting is for Supported Protocols. Microsoft SPXII will be in the Selected Column. Highlight it and move it to the Available side and click Apply.

• You will not be able to read online documentation on Windows 3.x until you install the 16 bit Acrobat reader.  The Pervasive.SQL 2000 install does not do this for you. The 16 bit Acrobat Reader is located at <CD-ROM>:\acroread on the NetWare and Windows NT server CDs.

• If you do not have any icons for the Pervasive.SQL 2000 utilities after installing you may need to shut down the machine and restart the OS. This is related to the version of Windows Explorer and/or Active Desktop you have on your PC.  #18306

• IMPORTANT NOTE: It is highly recommended that you backup all your files before you perform functions through SQL Data Manager such as alter and create table, null conversion, or import of an external file. This powerful tool is designed to give you the ability to modify your database schema and data. If you inadvertently set the options incorrectly or enter incorrect data you could change your files in an irreversible manner. Full recovery will be possible if you have performed a backup.

• SQL Data Manager Utility will not be able to connect locally to a Pervasive.SQL 2000 NT server if no user count licenses are available.  #18208

• The default statement separator in SQL Data Manger is the "#" character. This can be changed to the ";" by selecting Tools -> Properties.  #17574

• Some of the shortcut keys designed specially for SQL Data Manager do not work.  This includes the Ctrl-F to bring up the FIND window; Ctrl-A to run all statements; Activate Database, table, column, or template; and Activate SQL Text or Results windows.

• Some integer data fields will accept values outside of the range for that data type in the display grid.  These data types are : utinyint, uinteger, ubigint, and integer.  Inserting a number too large or too small will result in the binary value being pruned internally to fit the column size.  You must be careful when entering values in these fields to not exceed the acceptable range.  Entering a SQL query that does this will fail with an appropriate error message. #18620

• The Table Statistics tool allows a user to manipulate the definitions of an existing data table in one of two modes 'Linked' and 'Unlinked'.  Linked mode will cause any changes in the database table definitions to replicate the changes in the actual data file.  Unlinked mode allows the user to change the database definitions to fit a table data file without altering the contents of the file.  'Unlinked' mode is the default.  Table modification modes are for experienced developers and tech support.

• Before you can view your local user DSNs through Pervasive Control Center's namespace you must add at least one System DSN on your local machine. Also, the default setting in PCC is to not display Client Engine DSNs used for Client/Server connections. If you want your local client DSNs listed in your namespace you must change the setting for this under View -> Options.  #18173

• If one of the servers in your namespace is down or unresponsive, several utilities that check for the existence of available database DSNs will respond very slowly.  To improve response time, simply right click on the problem system in the namespace and select disconnect until the network availability improves.

• User count licenses in use in the Monitor utility for an NT server tracks only applications accessing the Pervasive.SQL 2000 NT engines through the transactional interface. It does not show the relational interface users. They are being tracked internally by the database. So, if you get an error that you are out of licenses, you cannot rely on the number in Monitor if you have ODBC applications accessing the database. This is not the case when monitoring a Netware server engine. Both relational and transactional are monitored in the total licenses in use. #18658

• If you try to connect with the Monitor utility to a server that is running the transactional service but not the relational service, it will take a long time to connect.  This is because it is waiting for a time-out period to elapse for the relational service to respond.  #18256

• When using the Workgroup Engine to process remote databases, applications may experience delays on the initial database connection as the client requester attempts to connect on all supported protocols to a server engine before starting a workgroup engine. Performance may be improved by configuring the client requester to use a single supported protocol appropriate to your network.

• If you are using NetBIOS to access the workgroup engine running on a Windows NT 4 workstation or server, you must have Windows NT 4 Service Pack 4 or later installed. NetBIOS on earlier versions of Windows NT 4 may result in dropped connections to the workgroup engine. If you are running NetBIOS on Windows 95 you must have Service Pack 1 and Winsock II.  The most recent version can be downloaded from the Microsoft web site at:

http://www.microsoft.com/windows95/downloads/contents/wuadmintools/s_wunetworkingtools/w95sockets2/default.asp

• The ODBC interface relies on the ODBC cursor library to provide support for SQLExtendedFetch and Rowset Scrolling when connecting via a front-end application such as Microsoft Visual Basic. The connect string property should be set to "Use ODBC" or "UseIfNeeded". See the Microsoft documentation for more information.

• Schema changes are not allowed from within a stored procedure. A "syntax unsupported" error is returned rather than a "driver not capable" error.

• Limited error detection/checking is performed when Stored Procedures and Triggers are created.  Therefore, it is possible to create a Stored Procedure or Trigger that will not execute properly.  Full SQL level checking and validation is performed when they are executed.  In some cases the SP or Trigger will return only error "S1000" rather than a more detailed error to be used in debugging.

• Repeated relational queries from a Delphi application may exhaust MicroKernel resources, resulting in Btrieve error 87.

Workaround: Recycle the relational and transactional services. #15709

• Timestamp with decimal is documented, but NOT supported in this release.  #18496

• GRANT ALL on <Tablename> to User does not give that user CREATE TABLE rights. It is necessary to specifically do a GRANT CREATETAB to User as well as a GRANT ALL before they can create tables.  Even though GRANT ALL gives Reference Rights they cannot be utilized without CREATE TABLE rights.  This is expected behavior.  Also, only the "Master" can grant rights to users.  The user that created the table does not have grant rights.

It is necessary to specifically do a GRANT CREATETAB to User as well as a GRANT ALL before they can create tables.  Even though GRANT ALL gives Reference Rights they cannot be utilized without CREATE TABLE rights.  This is expected behavior.  Also, only the "Master" can grant rights to users.  The user that created the table does not have grant rights.

• Subtraction on timestamp data types does not work correctly.

Example:
create table time1 (c1 timestamp, c2 timestamp)
insert into time1 values('1999-09-26 00:00:00', '1999-09-25 00:00:01')
select c1-c2 from time1

Result
1
Expected
Incremental Values
#17495

• While huge chunks of data (on the order of MBs) can be inserted into longvarchar or longvarbinary columns, it is *recommended* that you insert data in chunks of <=65500.  This will reduce the risk of running out of memory and increase performance.  For retrieving such data it is *required* to retrieve it in chunks of <=65500. #18558

• If your network's DNS configuration is incorrect, you could receive an ODBC connection error with the string "The ODBC Client Interface cannot communicate with SQL Connection Manager due to a network error (RPC = 65, Error = 121)" or "Server name not found by Pervasive Network Services Layer". You may see this error message while using InstallScout to test Relational Interface or by using the "Test" button in the Pervasive ODBC Client Interface Setup to test connectivity. You will receive this error because the DNS lookup failed between your client and your server. To correct this error, add the name of your server to your "hosts" file.  #18758

• Using a default clause to insert data into a BINARY column will not work correctly.  Do not use this clause to set values. Example:
create table bintest (col1 integer, col2 binary(20) default '23')
insert into bintest (col1) values (1)
insert into bintest values (2, '23')
select * from bintest
returns -- 1 0x3233202020202020202020202020202020202020
               2 0x2300000000000000000000000000000000000000
#18681

• If you are running the Pervasive.SQL 2000 Netware Server engine and are using an Alternate Collating Sequence on a relational table, your DDF files and the ACS file must reside in the same directory and must reside in a location that does not have any directories or filenames over 8 characters. You will receive the error "szErrorMsg="[Pervasive][ODBC Engine Interface]Invalid Collate Sequence Identifier." This will occur either when the setting the collation for a column in a table or when using the collate clause in an order by. Examples that will fail:
create table t1 (c1 char (10) collate 'xyz', c2 char(10))#
select * from t1 order by c2 collate 'abc'#
You must physically change the location of the DDF files and the ACS file on the Netware drive to a location that does not have any directories or filenames over 8 characters, and you must change the dictionary location for the associated Named Database through the Configuration Utility/Settings/Maintain named databases.
 
• Though the maximum amount of data that can be inserted into a longvarchar/longvarbinary column is 2GB, if a literal is used in the insert statement, one can only insert up to 997 characters. To insert more data than this, parameterized insert should be used.

Please see "Getting Started" Chapter 7 for information about how to contact Pervasive Software and/or get more information about Pervasive.SQL 2000.

This application uses the free iODBC Driver Manager as written by Ke Jin <kejin@inprise.com>, enhanced with local modifications from Pervasive for the NetWare platform. Pervasive will donate their code changes to the current maintainer of the iODBC Driver Manager project, in accordance with the LGPL license agreement of this project.

The iODBC Driver Manager home page is located at:

      http://www.openlinksw.com/iodbc/

For further information on this project, contact it's current maintainer: Patrick van Kleef <iodbc@openlinksw.com>.

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.

(C) Copyright 1999 Pervasive Software Inc.
All Rights Reserved.

**End of README.HTML**