Prev | Getting Started with Pervasive.SQL (Server edition) | Next |
Before You Begin
This section contains information with which you need to be familiar to install Pervasive.SQL V8. Before installing Pervasive.SQL V8, begin by reviewing the following documents:
- Chapter 2, Preparing to Install Pervasive.SQL - This chapter provides important information, including system requirements and platform specific notes, relevant to your operation.
- "What's New in Pervasive.SQL V8" - This document is included in your product package and contains information regarding the latest features and enhancements in this release.
- README - This file is located on the distribution media and contains late-breaking product news that could not be included in the product documentation.
Platform Notes for NetWare
This section contains notes that may be helpful in installing Pervasive.SQL V8 on a NetWare server.
- Native file access protocols (NFAP) is a feature of NetWare 6.0 (and a beta product for NetWare 5.1). This feature allows workstations to access and store files on NetWare servers without requiring a Novell Client or the Microsoft Client Service for NetWare. NFAP uses the same protocol (referred to as native) as the client workstation to copy, delete, move, save, and open files. Windows workstations perform these tasks using the Common Internet File System (CIFS) protocol.
Note that Pervasive.SQL V8 supports NFAP even though the feature is new with NetWare 6.0. You do not have to change the default settings for the Pervasive.SQL engines or clients to take advantage of NFAP. However, the following items do apply to the use of NFAP:
- The MicroKernel authentication uses Pervasive.SQL runtime server support (RTSS). The MicroKernel uses the NDS password; it does not use the simple password feature of NFAP. (The default setting for RTSS is "Complete," meaning that a user must supply a valid user name. A password is optional.)
- If you customize the network environment with a CIFS.CFG file, use the -SHARE parameter to point to the root of the volume. That is, do not use the -SHARE parameter to point directly to the Pervasive.SQL data files. The MicroKernel resolves locations specified by the -SHARE parameter only if the share points to the root of the volume.
- If your Windows client is running the Advanced Power Management feature of the operating system, disable it while installing Pervasive.SQL V8. The power management can cause a Pervasive.SQL V8 installation to fail if the client that is remotely installing the NetWare server is suspended during the install.
- Because some versions of NetWare include Btrieve 6.10, Btrieve system files already exist on the server and possibly on the clients. Back up these files and then remove them. If you do not remove them, set them to read/write so that the installation can overwrite them (the installation routine also backs them up). Refer to Btrieve 6.10 documentation for a component list.
- To install Pervasive.SQL V8, you must have rights to the SYS: volume and to the System directory on the server on which the product is being installed.
- The Pervasive.SQL server component is installed in the System directory of the SYS: volume, and all other supporting files are installed, by default, to subdirectories of the PVSW directory in the root of the SYS: volume (as described in What Files Are Installed as Part of Pervasive.SQL V8? .)
- NetWare versions below NetWare 4.11 are not supported.
- NetWare 4.x only: Ensure that the CPU Hog Timeout setting is a value greater than or equal to 60 seconds or you may encounter a server abnormal ending (abend) when installing Pervasive.SQL V8. The default value is 60 seconds. In addition, Unicode must be installed on the NetWare machine.
- NetWare 5.1 only: The command file AUTOEXEC.NCF for NetWare 5.1 includes an entry that launches another command file named SQLC.NCF. The command file SQLC.NCF loads a version of ODBC.NLM that is incompatible with Pervasive.SQL. On NetWare 5.1, it is necessary to comment out the line containing SQLC.NCF in your AUTOEXEC.NCF file. Otherwise, you will encounter errors when using Pervasive.SQL Control Center or performing SQL operations. Btrieve is unaffected by this issue.
- In all versions of NetWare, before starting Pervasive.SQL V8 the NetWare Loadable Module appropriate to the communication protocol being used must be loaded before starting Pervasive.SQL V8. If the SPX communication protocol is being used, then SPXS.NLM must be loaded on the server before starting Pervasive.SQL V8. If the TCP/IP protocol (the default) is being used, then TCP/IP must be correctly configured on the server before starting Pervasive.SQL V8.
- Prior to installing Pervasive.SQL V8, any existing Pervasive.SQL applications must be stopped on the client machines.
- Running the NetWare install from a Windows 2003 machine can produce Windows security warning messages that reference files install is trying to copy. If you receive such dialogs starting with "Some files can harm your computer", click Open and Install will complete normally.
- If you have any trouble with the following installation, see Chapter 21, Troubleshooting After Installation.
Installing Over Existing Pervasive Products
- Your previous versions of Pervasive products will be archived when you install Pervasive.SQL V8 so that there are no component conflicts. You can use Pervasive System Analyzer later to restore the archived products if necessary. Your licenses from previous Pervasive products such as Btrieve 6.x, Scalable SQL 4.x, and Pervasive.SQL 2000 will not be migrated to Pervasive.SQL V8.
- If you wish to make use of all the new version features, you must rebuild your data files so they use the version 8 file format. See the Advanced Operations Guide section for detailed information on how to use the Rebuild utilities to convert your data files.
Installation Tips
When installing Pervasive.SQL V8 for the first time on a system, Setup will check if all of the needed system files meet the minimum requirements. In some cases, these files are locked by the operating system and a reboot is required before Setup can continue. The following dialog box is displayed if this is the case.
Figure 8-1 Pervasive.SQL V8 Setup Reboot Required![]()
Click Yes to reboot the system. Setup is then automatically restarted.
Note
It is strongly recommended that you reboot your system if you encounter this message. If you do not reboot your system, Setup will encounter failures during engine and utilities configuration.
If you have any trouble with the following installation, see Chapter 21, Troubleshooting After Installation.
NetWare Security and Configuration Issues
This section details security issues relating to installing Pervasive.SQL V8 on the NetWare platform.
Rights Required to Install
To install Pervasive.SQL V8 on a NetWare server you should be an administrator of the server 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, or add DSNs.
In addition to the rights required on the NetWare server, you must have administrative rights on the Windows machine from which you are installing the Pervasive.SQL V8 NetWare server.
Easiest Method to Authorize Users to Administer Databases
All other users that are administrators for the NetWare server object where Pervasive.SQL V8 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 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 V8 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. To add this group and users to it, you must have the proper Novell NetWare rights enforced to add objects into the NDS tree on NetWare 4.11 or later.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 V8 installed. If all your Pervasive.SQL V8 servers are installed at the same level in your NDS tree, then only onePervasive_Admin
group is required for all of them.Here are examples of the correct and incorrect level for Pervasive_Admin. In the examples, the database engine is running on the NetWare server named "Psql."
0 [Root] | - Container A | - Group A | - Psql | - Server2 | - Pervasive_Admin (Group) | - Group B | - Juaquin | - Steve | - Tawanda0 [Root] | - Container A | - Group A | - Psql | - Server2 | - Group B | - Juaquin | - Pervasive_Admin (Group) - Wrong level | - Steve | - Tawanda
If you have multiple Pervasive.SQL V8 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 eachPervasive_Admin
group.
Note
If the Pervasive_Admin group is created at a lower level in the NDS tree than the Novell server to which it corresponds, members of the group cannot access the database engine unless they have Novell administrator rights. The attempted login to the Pervasive.SQL server from the PCC fails with the message "You have entered an invalid password or user name."
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/updates/psqlall.asp#NetWare
TurboFat on NetWare Servers
On NetWare 4.x, 5.x, and 6.x servers, data files can become corrupt in the NetWare cache or Turbo cache. The actual data file on the disk is fine, and if you rebuild the data file you will not lose any records. If you do lose records while rebuilding, that would indicate true corruption and not the turbo cache problem.
One workaround has been to down the server to clear the cache. This can be used as a test as well by getting a status 2 on a read of a record, downing the server to clear the cache, and then reading that same record again. If you can read it successfully, it is a good indication that the problem is in the turbo cache.
This issue is not unique to Btrieve files; it can be any type of file that Novell loads into its cache.
There are 2 possible workarounds for this situation.
- Workaround #1: Disable NetWare's Turbo cache
This can be done by using TURBOD2.EXE from Novell. See Novell's document TID 2960009 "TURBODIS.NLM to prevent database corruption" for more information. Its properties say it is for troubleshooting purposes and is not officially tested or supported. Experience has shown that this does not always eliminate the problem.
- Workaround #2: Serialize all I/O on a 'per file' basis in the NetWare MicroKernel.
The avoids the problem and has had outstanding results. It serializes all I/O on a per file basis in the NetWare MicroKernel. There have been no reports of this causing any problems or performance issues, so it is recommended to everyone.
- Edit the file
SYS:SYSTEM\BTI.CFG
- In the section titled
[MicroKernel]
find theUse FileIO Mutex
setting and set it to YES as shown in this example :(Note: capital letter 'I' and capital letter 'O').
- Ensure that there is not a second entry anywhere else that sets it to No.
- Restart the server for this change to take effect.
Cache Allocation Size
Beginning with NetWare 5.1, Novell deliberately sets the default Pervasive.SQL memory cache size to 1 MB, which is far too small for most applications. After you install Pervasive.SQL, you should set the Cache Allocation Size configuration parameter to 20% of the physical memory on the NetWare server, to avoid poor database performance. To access this configuration parameter within PCC, double-click the icon representing the NetWare server, double-click the Configuration, double-click Server, then Performance Tuning. Double-click on Cache Allocation Size and set the value in bytes.
Prev Installing Pervasive.SQL on NetWare |
Contents Up Check for Revisions | Next Installing the Pervasive.SQL Server Components |