See Situations Requiring That You Clear PCC Cache.

If you are using PSQL v12, start Monitor or Maintenance, choose Help then About from the menu, and check the Build Level.

Yes. PSQL is cluster compatible with Microsoft Failover Clustering, Microsoft Cluster Service, and Linux Heartbeat. See the chapter High Availability Support in Advanced Operations Guide.

Certain requirements must be met before you can start PCC. See Starting PCC on Linux or Starting PCC on OS X.

The settings for the PSQL services can affect whether or not you have permission to log in to the machine where the database engine is running. The settings apply whether or not you use a Pervasive_Admin group. If you change the Log on as setting for a PSQL service to This account, you must change the user rights policy Act as part of the operating system for the account. Otherwise, remote log in fails.

For example, the Monitoring utility requires that you log in to the operating system on the machine where the database engine is running. You will receive a message that log in failed if the account specified for This account cannot act as part of the operating system.

Note that even the Administrator account requires that you set the user rights policy for Act as part of the operating system.

See Services Settings and Log In Authority for a complete discussion and the steps to change the user rights policy.

Refer to the tasks discussed in the chapter License Administration.

Concurrent. Refer to Concurrent User License Model.

Capacity Usage Viewer was designed for this purpose. Because it records both peak daily session use and peak daily data usage, you can see how much of each you use over time. You can use this information to make a reasonable determination of what license capacity size you need. Refer to Capacity Usage Viewer for information about how to access and use Capacity Usage Viewer.

Start PSQL System Analyzer and click Next on the Welcome screen. On the following screen, check the box Test Network Communications and make sure all the other boxes are not checked. Click Next. In the following screen, cancel the selected protocols that you do not want to test. Click Browse to select the drive that you have mapped to the installation directory on the server. You must have a mapped drive; UNC names are not supported. Click Next to run the network tests. The results window tells you if there are any significant problems with your networking.

Start PCC (see Starting PCC on Windows in PSQL User's Guide). Right-click on Local Client then click Properties. Click Access. Ensure that the option Use Local MicroKernel Engine is not check marked and that Use Remote MicroKernel Engine is check marked.

In PCC, right-click the server name where the data files are located then click Properties. Click Compatibility and set Create File Version to the file version to which you want to convert. Click OK. Click Yes to restart the engines. These changes result in new files created to be in the version selected.

Run the Maintenance utility then click Options then File Information Editor. Click Load Information and choose the data file that you want to convert. Click Create and specify the name of the new, empty data file you want to create with the older version format. Click OK to create the file. Close the File Information Editor window, but do not exit Btrieve Maintenance Utility.

From the menu, select Data then Copy. Enter the name of the source data file and the name of the target data file (your newly created file with the older version file format). Click Execute to copy the records into the older version file. After the copying has finished, if you need the new data file to have the same name as it did previously, save your original data file with a different name, then save your new file using the original file name.

In PCC, right click on the database to which the table belongs, then click Properties. Cl ick Directories. Change the value for Dictionary Location.

It may appear that the path has not changed. To confirm the change, open the X$File system table and look at the Xf$Loc field for the given user table. If you cannot see the system tables in PCC, expand System Objects.

You can also use the ALTER TABLE USING statement in SQL to change the data file used by a particular table. Refer to SQL Engine Reference for further information.

If Btrieve files have owner names on them, you must use database security for ODBC access. Turn on database security in PCC. See To turn on security using PSQL Explorer and Owner Names and Security in Advanced Operations Guide.

When you enter the statement, substitute the actual name of your table and the appropriate owner name for that table, as indicated above. Remember that each data file corresponds to an ODBC table. If you don’t know which table corresponds to which data file, see use PCC to find out. Right-click on the table in PCC then click Properties. Click Information in the tree. The File Name field shows you the file that is referenced by that table definition.

If security is important, then you must create users and assign permissions for all users expected to access the database. You do this by using the CREATE GROUP and GRANT statements in SQL. You can also add users and groups with PCC. See Users and Groups in Advanced Operations Guide.

The procedure for this task is provided in Advanced Operations Guide.

Getting Started With PSQL contains an entire chapter that provides detailed instructions on how to upgrade.

If your application uses Scalable SQL or ODBC, then you should review the Application Migration Guide available on the web site.

See also Trace Operation in Advanced Operations Guide.

Run the PSA network connectivity tests to verify network connectivity. See Test Active Installation Tasks. Also refer to the Knowledge Base, available at the PSQL website, for information about particular issues.

Yes, space from deleted records is re-used on subsequent inserts. Space in files is never de-allocated back to disk. If index balancing is turned on, unused space in index pages is also re-used. See Rebuild Utility Concepts in Advanced Operations Guide.

You can put data files into Continuous Operations mode by using the BUTIL -STARTBU command or Maintenance utility described in Advanced Operations Guide.