Omega - Support Information

Page Updated: 4-5-17

Pervasive.SQL - Q&A

This page consolidates the FAQs and knowledge database articles from the previous site.

FAQs

What versions of Pervasive.SQL and Btrieve work with Omega, WIPC, etc.?
Omega for Windows, Print Server, Datalink and Archiver should work with any version of Pervasive.SQL 7-12.
Omega for DOS and WIPC should work with Pervasive.SQL 7-12 and Btrieve v6.15. They work with 10.x and later provided they are run as DOS sessions under Windows via DOSBox support (version 10 no longer supports 16-bit clients - Omega for DOS and WIPC will therefore definately not work when run on pure-DOS machines or under 32-bit Windows via the DOS requesters).
The version 2000i, 8.x, 9.0, 9.5, 10.1, 10.2, 10.3, 11.2, 11.3 and 12 workgroup engines and 2000i Windows server engines have all been tested in-house; the 2000i, 9.x workgroup engine and 2000i, 8.x, 9.x, 10.1 and 11.2 server engines (Windows) have been tested/installed successfully at customer sites.
Actian PSQL 12 was released in December 2014 and has been tested without issues with Omega, but not WIPC (the test platform was 64-bit, which does not support DOS applications).

What Windows OS/platform does Pervasive.SQL 12 support?
The workgroup engine works on Windows Vista, 7, 8.x and 10.
The client requester works on Windows Vista, 7, 8.x and 10.
The server engine works on Windows 2008 and 2012.
Both 32-bit and 64-bit versions of the server and client components are available.
 
What Windows OS/platform does Pervasive.SQL 11.x support?
The workgroup engine works on Windows XP (SP3 recommended), Vista, 7 and 8.x.
The client requester works on Windows XP, Vista, 7 and 8.x.
The server engine works on Windows 2003 Server SP2, 2008 and 2012.
Both 32-bit and 64-bit versions of the server and client components are available.
 
What Windows OS/platform does Pervasive.SQL 2000i/8.x support?
The workgroup and workstation engine work on Windows 95, 98, ME, NT 4 (service pack 3+), 2000 and XP.
The client requester works on DOS 5.0+, Windows 3.11, 95, 98, ME, NT 4 (service pack 3+), 2000 and XP.
The server engine works on Windows NT 4 (service pack 3+) Server, 2000 Server and 2003 Server; NetWare 3.2+.
 
What Windows OS/platform does Pervasive.SQL 7 support?
The workgroup and workstation engine work on Windows 95, 98 and NT (service pack 3+).
The client requester works on DOS 5.0+, Windows 3.1+, 95, 98 and NT (service pack 3+).
The server engine works on NT (service pack 3+); NetWare 3.12+.

What other operating systems does Pervasive.SQL/Actian PSQL run on?
The server engine and client can also be run on Linux and, since version 12, Mac OSX. Omega has not been tested with the Linux/OSX server engine.
 
When trying to run Omega or WIP Control a "Btrieve Status 20" error appears. What does this mean and how do I overcome the problem?
A "Btrieve Status 20" error means that Pervasive.SQL or Btrieve is not running on that workstation or on the file server.
When running a single user Omega system on a workstation, depending on the database version you are using, check that a Pervasive.SQL workstation/workgroup has been installed (Windows) or the BTRIEVE.EXE executable (DOS) is present in the Omega directory.
When running a multi-user Omega system on either a Netware or NT Server, you should check that Pervasive.SQL or Btrieve is running on the server, then check that the workstation has the Windows client installed (Windows) or access to the BREQUEST.EXE/BREQNT.EXE/BREQTCP.EXE requesters and any necessary supporting components(DOS).
Windows clients trying to use the DOS requester without having deactivated the built-in DOS-box support will also produce a status 20 error.
 
I have upgraded my Btrieve version on the Netware file server to 6.15.525 and now the Omega Print Engine does not work.
If you are using Windows 95 or NT workstations you will need to set an additional configuration option to allow access to the Btrieve engine. Edit the "BSTART.NCF" file on the "\SYSTEM" directory by adding "-r1500" to the LOAD BSPXCOM line.
You should then run "BSTOP" and "BSTART" at the file server console prompt and the problem should be corrected.
 
Are there any known problems with the Pervasive.SQL 7/2000/8.x/9.x database engines?
Known issues with the latest versions (10+) can be found on the Pervasive website. Unfortunately Pervasive has removed known issues documentation for older versions of its database engine.
 
What does “Btrieve Status n” mean?
The most commonly reported Pervasive.SQL/Btrieve errors are listed below. For more status code descriptions see here.
2 - input/output or file corruption
4 - key value not found
5 - duplicate key
11 - directory error
12 - file not found
20 - database engine not found
22 - data buffer too small
46 - access to the requested file is denied
84 - record or page is locked
85 - file is locked
95 - session is longer valid
 
Opening certain files keeps producing status 2 errors.
A status 2 Pervasive.SQL or Btrieve error usually corresponds to a serious input/output or file corruption problem which will require the file in question to be rebuilt or restored from backup. However inversions 7 and 2000, it also occurs as a ‘phantom’ status 2 and does not indicate a serious problem. In this case the database engine needs to be restarted, or sometimes the computer on which the engine runs rebooted.

With Netware server engines you must also ensure that the TurboFAT issue has also been resolved. Unfortunately this is not an issue that I am familiar with.
 
I have also seen this happen when a delta file (during continuous mode) has been locked by the backup software, when it should have been excluded from backup.
 

Knowledge database

No articles

 

This site is copyright 2003-2017 Neil Hughes. All rights reserved.
Company and product names on this site may be trademarks or registered trademarks and are hereby acknowledged.

Contact (Support)
Email: support@support4omega.co.uk
Skype: support4omega

Contact (Website/other)
Email: admin@support4omega.co.uk