Kbase P125578: DataServer Query using ROWID returns no result after migration to 10.1B or later
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/01/2009 |
|
Status: Verified
SYMPTOM(s):
Query with ROWID returns no result since 10.1B
Same query returns results in 10.1A and earlier versions
PROGRESS_RECID is defined as INT data type in Microsoft SQL server database
PROGRESS_RECID_IDENT is defined as INT data type in Microsoft SQL server database
FACT(s) (Environment):
Database was migrated from Progress to SQL Server with a pre-10.1B release
OpenEdge 10.1B
OpenEdge 10.1C
MS SQL DataServer
CHANGE:
Upgraded the MS SQL Server DataServer from OE10.1A or earlier to OE10.1B or later
CAUSE:
Bug# OE00163021
CAUSE:
Bug# OE00167925
CAUSE:
As part of the effort to introduce 64-bit data addresses into the OpenEdge database for Release 10.1B, the default implementation of PROGRESS_RECID in the DataServers for MS SQL Server and ODBC were changed to a 64-bit value. In releases prior to 10.1B, PROGRESS_RECID was a 32-bit value. This produced some PROGRESS_RECID incompatibilities for schema holders created or maintained in OpenEdge 10.1B using the 10.1B Dictionary utilities. These incompatibilities also affect schema holders that were created and maintained prior to 10.1B but are used in a 10.1B application environment or a schema holder created or maintained by the 10.1B Dictionary that is now used in a 10.1C application environment.
FIX:
To fix the issue, two situations are available:
- maintain the 32-bit RECIDs.
The incompatibilities are fully resolved in Release 10.1C02 by simply performing a schema pull from the Dictionary utilities. Therefore, if you are using or maintaining a schema holder from the OE 10.1B Dictionary (prior to Release 10.1C02) you will need to re-pull your server definitions into that schema holder using 10.1C02 Dictionary utilities to avoid application conflicts with thePROGRESS_RECID. After re-pulling definitions into your schema holder using 10.1C02, you should encounter no further problems with PROGRESS_RECID.
- migrate to 64-bit RECIDs.
If you aim to have native 64-bit RECIDs on the MS SQL Server, perform a full new migration from the Original Progress database to the MS SQL Server, using OpenEdge 10.1B or later.