Kbase P150502: ODBC error 24000 - Invalid cursor state - during load of the data after migration is completed by pr
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/09/2009 |
|
Status: Unverified
SYMPTOM(s):
ODBC error 24000 - Invalid cursor state - during load of the data after migration is completed by protoMSS process if the unicode type is selected
24000: [MicrosoftS] [ODBC Driver] invalid cursor state
FACT(s) (Environment):
The error is apparent on the screen when manually loading the .d file using the Data Administration data load utility as well as creating records on a table after protoMSS process
If Move data is selected for the protoMSS process, ABL client may cause unexpected behavior such as no errors or nothing happens or GUI client may gpf
The gpf does not create protrace file
The trigger for the progress recid is not created during the protoMSS on the MS SQL Server database
The .sql file generated from the protoMSS process has the trigger in it for each table
With the "-Dsrv qt_debug,EXTENDED" debugging option during the protoMSS process, the following errors are displayed in the dataserv.lg file:
SQLState: 37000
Native Error Code: 102
Error Message: [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near 'NN'. (15044)
If move data is selected for protoMSS process the dataserv.lg file also show the error 24000 in it
Windows
OpenEdge 10.2A01
MS SQL DataServer
CHANGE:
Hot-fix patch OE10.2A0113 is applied for the bug OE00178470
CAUSE:
Bug# OE00188693
CAUSE:
The bug is only related to the unicode data type. The MSS DataServer adds an extra 'N' on the RAISERROR (N'PSC-init',0,1) function for the unicode data type on the progress recid trigger so it becomes RAISERROR (NN'PSC-init',0,1) during push process.
FIX:
Upgrade to OE10.2A02
Or,
If upgrade is not possible, delete the MS SQL Server database and recreate a new database with the same name on the MS SQL Server, and run the protoMSS generated .sql file on the t-sql utility against the new database to create tables and triggers. The existing Schema holder should work against the MS SQL Server database.