Program Temporary Fixes (PTFs) offer quick resolution to specific known problems
in a given release. Therefore, PTFs do not go through the same extensive
quality assurance and field testing as do Maintenance Releases or Major Product
Releases.
This document contains a list of known bugs present in SQLBase Version
8.5.0 and for which verified fixes have since been made in the base version.
Since PTFs are cumulative, those fixes listed in a given PTF are available only
in combination with all fixes listed for earlier PTFs.
Defect ID | Description |
65491 | Using ROWID in the WHERE clause of a view definition causes SQLBase to crash. |
78307 | Updating date/time column using bind updates with null value. |
78951 | When using NLS Comparison, a specific query returns 4 rows in Windows while it only returns 2 rows in NetWare, possibly due to the way the strings are compared in Netware. |
79600 | A statement using an EXISTS clause takes much longer in SQLBase Version 8.5 than in 7.6.1. |
79715 | When doing a straight select without ANSI99 syntax, data is returned quickly. When using an inner join sequence, the data is returned very slowly. |
79887 | @SCAN() function returns wrong results with long strings. |
79933 | No rows returned in a query when an ORDER BY clause is inserted. |
79997 | Difference in results when using ROWID in an IN clause. |
80077 | SQLBase crashes without writing either a fail.sql or process activity log entry when doing a particular UPDATE. |
80173 | UNION behaves differently from UNION ALL in some circumstances. |
80207 | Performance problem running a query that has been made a view. |
80233 | SQLBase returns rows when a LIKE clause is used on the null column. |
80268 | Wrong data in results for JOINS(combination of IJ,LOJ and ROJ) made of 4 or more tables after creation of unique index. |
80318 | SQLBase stops responding to clients after 1801 error. |
80323 | sql.ini SERVERPATH keyword has a limit of 255 characters |
80731 | When @NULLVALUE(aaa,0) is used with NOT IN, the wrong result set is returned. |
80778 | Autoconversion problem. Certain query crashes SQLBase. |
80815 | SQLBase crashes with 00732 VIO MZU. Page being modified has a zero use count. |
80817 | A select with DISTINCT and a NULL column returns all NULL Values. |
80872 | Getting an error 00504 WSP CRP - Cannot relocate pointer when trying to drop a view. |
80968 | "00702 Fatal SQLBase System Failure (VIO PNO)" occurs in a test which uses 10 or more concurrent clients. |
81189 | When database name length is 16 characters, unable to connect when sql.ini is configured for client specifying the database name. |
81557 | Performance issue in selects with the NOT IN clause. |
81670 | Conditional operators are not working with bind variables that contain negative values fetched from tables. |
81794 | Partitioned database no longer reachable after unloading old database and creating a new database. Error message appeared before losing database: "10724 - PFS MDC Incorrect extent table entries in the main database" |
82066 | SQLBase server hangs sometimes when executing a join between a table and a view containing large amount of data. |
82097 | TD 3.1.0 SQLBase API sqlfgt() version 8.5 error 1307 against older SQLBase pre-8.0 |
82136 | Apparent autoconversion problem. An unload of a 8.5 database that was autoconverted from 7.5.1 fails to load back under 8.5. |
82165 | Performance problem running a query that has been made from a view which in turn is made of tables and views. |
Defect ID | Description |
79264 | Inappropriate 849 error message with IN operator. |
79598 | A SELECT query may crash the server when using large IN clauses. |
79791 | With a particular query, if the cache is set to 57373, 2,423 rows are returned. If the cache is set to 57374, no rows are returned. |
79828 | The attached sql script crashes the SQLBase Server (no fail.sql). The error is reproducible with versions 7.6.1 and 8.5. |
79908 | With ANSI Joins,when using USING clause,if we give the column name prefixed with NON-EXISTing table name or alias name, no error thrown. |
79914 | Under similiar circumstances to defect 79961, the SQLBase server crashes without any fail.sql entry. |
79923 | With 8.5 PTF1 and PTF2 (5 Users),Backup snapshot with a database size of approximately more than 500 MB gives 3208 error. |
79961 | The SQLBase server crashes without any fail.sql entry. |
79971 | Selects with subselects on the same table return wrong values in some cases. |
80014 | Wrong result in two queries out of 6 in a particular script. |
80044 | SELECT and DELETE do not work the same way with identical WHERE conditions involving a subselect. |
80089 | A particular query with DISTINCT and IN clause hangs the Netware database engine. With Windows the same query works fine. |
80108 | Data corruption - Error 839 ROW CNL |
80123 | Performance problems with multiple UNION statements. CPU usage goes to 100%. |
80206 | HAVING clause on a column which has nulls yields wrong results. |
80216 | Data missing for RIGHT OUTER JOIN on views made of more than 4 tables with GROUP BY and HAVING clause. |
80217 | Incorrect number of rows for LOJ made of more than 4 tables with GROUP BY and HAVING clause after creation of unique index. |
80291 | After creation of unique index, incorrect count of rows are returned for queries with multiple outer joins. |
Defect ID | Description |
79264 | Inappropriate 849 error with IN operator. |
79454 | A LEFT OUTER JOIN doesn't use an index and is taking a very long time. |
79696 | Database Engine will crash when we do a SELECT after dropping all the columns in the table. |
79714 | The results of executing a SELECT using a view returns a different result set than when executing the plain SELECT. |
79731 | Executing a simple query on a view causes server crash when a SQLBase 761 database is autoconverted to SQLBase 8.5 |
79732 | Selecting from a view returns 476 rows. Selecting from the same view but ordering the data returns 4 rows. |
79779 | Creation of view with NATURAL JOIN crashes DBEngine. |
79781 | Views created with more than 2 table ANSI JOINS and GROUP BY returns 0 Records. |
79782 | Select on views created with more than 4 table ANSI RIGHT OUTER JOIN and GROUP BY crashes the DBEngine. |
79783 | DBEngine crashes for any query after a particular NATURAL JOIN query. |
79845 | When a PREPAREd query contains ORDER BYand if EXECUTE and FETCH is in loop, then in the resultsets, for any column, if we encounter a null value in fetch, then the consecutive EXECUTE and FETCH results in NULL even when column has NON-NULL value. |
79850 | After applying PTF1, starting the Netware n-user server causes error message "dbnwsrv.bin is not in the same path as dbnwsrv.nlm" |
79869 | When using INSERT INTO clause with multiple table IJ/LOJ/ROJ ANSI JOIN Selects, for some instances correct number of records are not inserted and for some instances data got inserted with values missing in some of the columns. |
Defect ID | Description |
64269 | Error messages should be given when invalid values of all Keywords, such as centuradefaultmode, character set, cmdtimeout, commit server, users, workalloc, and work limit, are entered in Server Configuration - Advanced menu.
|
69009 | Correlated update (using sub-Selects) fails when using bind variables; works fine when using literals.
|
69347 | Serious Performance problem when using complex queries with views.
|
73581 | A store of a procedure produces error 09913 PRS MLD Missing line delimiter when run as part of a load script, but works fine as a command within SQLTalk.
|
74165 | Either the server or SQLTalk comes down or incorrect results are returned when doing an aggregate select with a 'having' clause.
|
74856 | Referential Integrity: Before Update Trigger using NUMBER Null causes error 00382 EXE UFV Unmatched foreign key values on a valid update.
|
78034 | Creating a foreign key having columns that can have NULL value using ALTER TABLE command generates an error 388. The same can be created using CREATE TABLE command without any problem.
|
78129 | A particular query with an aggregate returns incorrect results.
|
78872 | Join between 2 views, which are created using either ANSI syntax or with Native syntax for a particular query are taking high CPU usage and takes high processing time compared to SQL Server and Oracle.
|
78972 | The query with @coalesce (col1, col2) = ""IS NOT NULL"" in the WHERE clause is returning incorrect records.
|
78975 | A certain query with multiple LOJ sometimes returns incorrect output for the data in the last columns.
|
79060 | SELECT with a WHERE clause from a View, which has been created using ANSI left outer joins returns incorrect number of records.
|
79085 | A particular query with views and EXISTS clause is taking high CPU usage and taking 12 hrs to return correct records.
|
79414 | Attempt to make concurrent connections with local and remote databases gives the error - error 00184(invalid server name).
|
79565 | Connectivity Administrator does not allow entry of hyphen (-) character as part of the Client name.
|