This page lists any known issues in versions of Pervasive.SQL still known to be used by Omega sites. Legacy support log IDs are included when available.
Summary: Long delays in returning lock status 84 to SQL queries (Pervasive.SQL 11.2+ only)
Details: Pervasive.SQL 11 SP2 introduced a bug whereby a relational query that triggers a lock error (status 84), instead of returning that status and cancelling the query quickly, takes 5+ minutes. Reducing the wait lock timeout setting on the database engine reduces the length of this delay but it will still take a noticeably longer time. Pervasive have assigned a tracking number of 61777 to this issue - it has been fixed in Actian PSQL 12 but unfortunately will probably not be fixed in version 11.
Summary: Relational queries cannot use indexes that are flagged as NULL_ANY or NULL_ALL.
Details: SQL/relational queries performed through ODBC/JDBC, etc. cannot use any index in Omega's database tables that have the Btrieve NULL_ flag property. Without any alternative indexes the query optimizer has to fall back on much slower full table scans. Most of the indexes in the Omega database schema use NULL_ flags and therefore cannot be used. Many of the larger tables have been modified in recent versions of Omega to iinclude new indexes that are available for optimization, and newer versions of Pervasive.SQL allow larger database caches that can help workaround the issue by keeping more tables in memory where the full table scans can be executed considerably faster.
Summary: Client/server version mismatch warnings
Details: Some versions of the Windows P.SQL client will display a dialog warning when the client and server versions do not match. This can be switched off with a registry setting.
Summary: DOS workstation performance issue connecting to Windows Server
Details: DOS workstation client performance is seriously affected connecting to Windows Server 2003 SP2 and later, with no known solution. A registry fix (IgnorePushBitOnReceives) was available to fix the problem on Windows NT, 2000 and 2003 pre-SP2, but no longer works.
Summary: Problems connecting to Omega DDFs in Pervasive Control Center (Pervasive.SQL 11.3+ only)
Details: Version 11 SP3 introduced a problem whereby you can no longer check table properties in the PCC if the associated DDFs are legacy v3 format. The PCC reports a null pointer exception. This has not been solved with Omega's DDF as of v11 SP3 Update 4, despite Pervasive listing the issue as being fixed.
Summary: Query optimizer issues
Details: Complicated SQL queries can cause the P.SQL database engine to 'lock up' for an unacceptable length of time with 100% CPU load. This appears to be due to poor query optimisation and is particularly bad in v2000. The only solution when this happens is to leave the query to complete or, if this is taking too long, stop the database services.
Summary: Cache performance issues in Windows Server operating systems not officially tested with Pervasive.SQL 2000i.
Details: Version 2000i, which is no longer supported by Pervasive, suffers various performance issues in post-Windows 2000 server installations. The maximum database cache size has been found to drop from 700MB (NT4) to 500MB (2003 R2), and cache performance with multiple clients accessing the server engine appears to be broken in 2003 SP2 and later.
Summary: Limited multi-processor core support (Pervasive.SQL 10 and earlier)
Details: Versions of Pervasive.SQL before 11 are not able to directly make use of multiple processors or processor cores. There will be some benefit in database performance due to the operating system's file I/O benefitting from extra processor cores.
Summary: Permissions issues in Windows Vista and later (Pervasive.SQL 9 and earlier)
Details: Versions before 9 SP2 have compatibility problems with Windows Vista and later due to permissions issues. There are workarounds, e.g. running the workgroup engine as a service.