Pervasive logo

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:

Platform Notes for NetWare

This section contains notes that may be helpful in installing Pervasive.SQL V8 on a NetWare server.

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:

Installing Over Existing Pervasive Products

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 one Pervasive_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."

Correct Level: 

0 [Root] 
  | - Container A 
      | - Group A 
      | - Psql 
      | - Server2 
      | - Pervasive_Admin (Group) 
      | - Group B 
          | - Juaquin 
          | - Steve 
          | - Tawanda

Wrong Level: 

0 [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 each Pervasive_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.

(Note: capital letter 'I' and capital letter 'O').

  1. Ensure that there is not a second entry anywhere else that sets it to No.
  2. 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