|
Return to search the Knowledge Base
Solution Details
Solution ID: 00017745
Pervasive PSQL v9 SP2 Known Issues (Part 2 of 2)
Problem Description:
Pervasive PSQL v9 SP2 Known Issues
[Please note service packs newer than v9.5 are available]
Problem Environment:Pervasive PSQL v9 SP2
Pervasive PSQL 9.5
Pervasive PSQL v9.5
Known Issues
Cause of this problem:
Solution Notes:
Link to Part 1 of Known Issues
53861 A JOIN query may return incorrect results if an index is optimized for the JOIN but some of the none-leading segments appear in disjunctive normal form in the WHERE clause
Example: SELECT p.Ss_Alpha, p.First_Name, p.Last_Name, c.Code, c.Plan FROM pr_mast AS p INNER JOIN pr_cded AS c ON (p.Loc_No=c.Loc_No AND p.Emp_No=c.Emp_No) WHERE (c.Code = 401 or c.Code = 791 or c.Code = 900)
An index with three segments (Loc_No, Emp_No, Code ) on table pr_cded is used for join optimization but the third segment, Code, appears in a disjunctive normal form connected with OR. In this case, results only contains rows with Code = 401.
Workaround: Contact Pervasive Support for field test fix (FTF)
53862 A UNION ALL in a stored procedure returns no data
Workaround: Contact Pervasive Support for field test fix (FTF)
53884 Login authentication fails on NetWare 6.5 SP5 if user name and password are specified in a URI against a database with Classic security
Workaround: Contact Pervasive Support for field test fix (FTF)
53910 Data dictionary files (DDFs) remain locked after all connections to database engine are closed
Workaround: Stop and then restart the database engine
53911 Query timeout does not working as expected with ADO.NET application
Workaround: Contact Pervasive Support for field test fix (FTF)
53912 SQL query may return incorrect results if leading segment column is STRING data type and IN operator contains values that exceed the length for the segment column
Example: Column c1 is the leading segment column. SELECT * FROM person WHERE Perm_State IN (‘KS’, ‘AZX’)
Workaround: Contact Pervasive Support for field test fix (FTF)
53948 ADO.NET provider returns “Invalid SQL data type” exceptions for DATE, TIME, and TIMESTAMP data types
Workaround: Contact Pervasive Support for field test fix (FTF)
53977 On Windows XP, F1 from Pervasive Control Center (PCC) may fail to invoke the JavaHelp a second time after JavaHelp Viewer opened then closed
Workaround: Open the JavaHelp by executing the following batch file: \PVSW\bin\plugins\com.pervasive.help.ui_1.0.0\pvswdocs.bat
53983 Database properties in Pervasive Control Center incorrectly displays relational constraints
53990 Adding additional bytes to a table created using IN DICTIONARY can result in garbage data on SELECT query
This problem occurs when the fixed length in DDF is larger than fixed length in actual data file
Workaround: Correct the fixed length in the DDF to match the actual fixed length in the data file
54003 The utilities CheckDB and DDF Builder do not check that fixed length of data dictionary files (DDFs) match the data file fixed length
54025 Canceling the installation of Pervasive PSQL Workgroup on Windows XP fails to remove the .INI and .Log files from the installation folder
54034 In Pervasive Control Center (PCC), if a save action results in an error and the editor is closed without saving the changes, PCC appears to retain the changes
Workaround: Manually refresh the Tables by right-clicking on the Tables folder then clicking Refresh.
54048 Installation of Pervasive PSQL Workgroup product does not add a "slash" between "PVSW" and "BIN" in classpath
Workaround: After installing the Workgroup product, change the classpath from this:
C:\pvswbin\pvjdbc2x.jar;C:\pvswbin\pvjdbc2.jar;C:\pvswbin\jpscs.jar
to this:
C:\pvsw\bin\pvjdbc2x.jar;pvsw\bin\pvjdbc2.jar;C:\pvsw\bin\jpscs.jar
This assumes a default installation to drive C.
On some platforms, such as Windows 98 and ME, an additional reboot is needed to instantiate the updated classpath.
Known Issues Not Assigned a Tracking Number
On Windows platforms, the JavaHelp does not invoke if the Themes service is turned off. Turn on the Windows Themes service to ensure that the JavaHelp invokes.
Link to Part 1 of Known Issues
Did this solution document help you solve your problem?
|
Return to search the Knowledgebase
|
