Kbase P109480: Oracle DataServer bug fixes in 10.0B03
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
GOAL:
Oracle DataServer bug fixes in 10.0B03
FIX:
Below is a list of Oracle DataServer issues fixed within 10.0B03.
The READMSP file does not list the bug which were already fixed within 10.0B02 .
20040702-028 GPF on GET NEXT with Oracle Dataserver
20040623-022 Error -1410, ROWID invalid, when running query containing the ROWID function
20040709-037 Performance degradation using Reposition with Oracle DataServer.
20050120-008 Client crashes when loading a schema cache file which contains a Dataserver schema.
20050105-020 Oracle error 933 when querying multiple tables with nested query.
20041117-002 Oracle error -911 when the Where clause contains a logical array.
20041116-021 Webspeed agents crashes when using Oracle Dataserver and ROWID function.
20041028-009 Oracle DataServer does not generate the correct index hint with DESCENDING indexes in ORDER BY DESC query.
20050816-023 Erroneous double upper function is being defined by Oracle Dataserver when doing a REPOSITION
20050725-003 When using "begins """ clause in 4GL, the DataServer translates it into where "1=1" causing Oracle to do a full table scan.
20050714-006 When writing a FOR EACH that causes a join in Oracle and character fields participate in the WHERE clause, the Oracle DataServer is generating SQL which contains a double UPPER clause. An example would be UPPER(UPPER(field)). This is causing Oracle to perform a full table scan instead of using an index even if a query-tuning index hint is supplied.
20050712-043 A query containing the ROWID function in a where clause returns incorrect records using Oracle Dataserver
20050317-025 The Oracle Bulk Load utility does not load records and gives an error implying that the data is too large even though the data had been dumped from the same table.
20050118-002 Oracle DataServer returns incorrect result when using PRESELECT.
20050214-017 he General Delta SQL utility for Oracle is not correctly naming the fields created in an array in oracle. All the extents have ##1 in the name instead of the proper extent number.
20050311-015 When using the Oracle Generate SQL Utility, a new array field will not generate the proper SQL to create the field. The first element of the array does not have the "ADD" keyword in the SQL file so when it is loaded into Oracle it is rejected. 20050311-014 When using the Oracle Delta SQL, if a new index name is 30 characters long and matches an existing index name, the utility appends a number at the end of the index name to make it unique without verifying that the name is not longer than 30 characters