Kbase 11232: ORACLE BUGS AND RELEASE FIXED IN
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
ORACLE BUGS AND RELEASE FIXED IN
Known Oracle Gateway bugs and their status:
--------------------------------------------
BUG:
----
92-07-21-031: Oracle Gateway truncates numbers to 10 positions in a
WHERE clause.
STATUS: Fixed in 6.2N
BUG:
----
92-06-16-004: Dictionary updates of field definitions for decimals does
not work. (modify schema, choose a file, then try and
modify a field) The error the user gets is:
/usr/dlc/prodict/ora/ora_fld.p unable to find shared
buffer for dfields(566).
STATUS: This bug is fixed in 6.2L
------
BUG:
----
92-06-16-005: Using the Oracle gateway and changing field values to
unknown: if you enter a value of ? it gets displayed as
spaces in the frame following the update.
STATUS: This bug is fixed in 6.2L
------
BUG:
---
92-03-25--005: Running the following program gets Progress errors and dumps
core (s/e: 1288 19 439):
update some-var as char with frame frmx editing:
do:
create anyfile.
validate anyfile.
delete anyfile.
undo.
end.
leave.
end.
STATUS: This bug is fixed in 6.2L
------
BUG:
----
91-04-10-006: When creating an Oracle Gateway schema, ORACLE fields
of datatype 'NUMBER' are represented in an incorrect
format in the PROGRESS data dictionary.
STATUS: This bug fixed in 6.2L
------
BUG:
----
92-01-08-008: When running a program in which FIND FIRST is used in a loop,
loop an stget: out of storage error occurs.
STATUS: This bug is fixed in 6.2L
------
BUG:
----
bug number 92-03-09-006. It appears that the bug is NOT in 6.2M, but
fields are not updated correctly.
STATUS: This bug is fixed in 6.2L
------
BUG:
----
91-09-24-003: Can't add new records to an Oracle db if there is a field defined
as mandatory in the schema holder.
STATUS: This bug fixed in 6.2L
-------
BUG:
----
92-10-14-002: If you create a table in ORACLE, you cannot use the
ORACLE utilities "Update/Add ORACLE FILE definition"
remotely. If you attempt to do this remotely, the
broker disconnects without displaying any messages.
additionally, if you have remote users and try this
locally, then the user will receive an error that
ORACLE is in use by remote client, and the user must
totally exit out of remote sessions to update schema.
Possible error messages are: s/e 1894, 1451.
STATUS: As of Dec 2nd, open. scheduled to be fixed in
6.2N, 6.3B. Please verify in bug report.
Progress Software Technical Support Note # 11232