Kbase P172225: Simple SQL query on primary indexed Integer field with no where clause fails with dsmCursorFind from
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/5/2011 |
|
Status: Verified
SYMPTOM(s):
Simple SQL query on primary indexed Integer field with no where clause fails with dsmCursorFind from tpl_scan_fetch on PUB.<table name> for PUB._Userid
[DataDirect][OpenEdge JDBC Driver][OpenEdge] Internal error -1 (see dsmret.h) in SQL from subsystem DSM SERVICES function dsmCursorFind called from tpl_scan_fetch on PUB.test for PUB._Userid. Save log for Progress technical support.
[DataDirect][ODBC Progress OpenEdge Wire Protocol driver][OPENEDGE]Internal error -1 (see dsmret.h) in SQL from subsystem DSM SERVICE function dsmCursorFind from tpl_scan_fetch on PUB.test on PUB test for PUB._Userid. Save log for Progress technical support.
DataDirect][ODBC Progress OpenEdge Wire Protocol driver] Error in row
[DataDirect][OpenEdge JDBC Driver][OpenEdge] Encountered internal error in SQL ENGINE at 3968 in /vobs_sql/sql/src/progstub/pro_cache.cxx. Contact Progress Technical Support
FACT(s) (Environment):
Connecting to database with user ID SYSPROGRESS
IBM AIX 5.3
OpenEdge 10.2x
CAUSE:
Bug# OE00199909
CAUSE:
Database schema damaged. The problem appears when the database schema of an OpenEdge 10.2A database is modified with the data dictionary of OpenEdge 10.1A . When modifying the OpenEdge 10.2A database schema with the data dictionary of OpenEdge 10.1A, the SQL query will crash with the above error. Modifying the OpenEdge 10.2A database schema with the data dictionary of OpenEdge 10.2A does not damage the schema.
FIX:
None at this time. To avoid this problem, make sure a newer OpenEdge database schema is not modified with an older version of OpenEdge.