Kbase P177253: BUFFER-COPY or ASSIGN of the decimal records on the SQL server causes soft crash of the Procedure ed
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/12/2010 |
|
Status: Unverified
SYMPTOM(s):
BUFFER-COPY or ASSIGN of the decimal records on the SQL server causes soft crash of the Procedure editor with error 6177
SYSTEM ERROR: Assignment error. (6177)
22005[Microsoft][SQL Native Client]Invalid character value for cast specification
After the above errors the procedure editor crashes and comes back with a new one while the schema holder and foreign database connections are still intact
Even when procedure editor soft crashes, some records are being copied to the MS SQL Server to the point where the decimal data mismatch occurs
The decimal field on the OE database has up to 6 decimal value on some of the records even though the decimal is set to 2 on the data dictionary
The reason for how the 6 decimal value got in to the OE table with 2 decimal value is specified is unknown
The SQL Server has the decimal or numeric data type set to (10,2)
FACT(s) (Environment):
Windows
OpenEdge 10.1x
OpenEdge 10.2x
MS SQL DataServer
CAUSE:
The decimal data mismatch with the length caused the soft crash, but any crash is not an acceptable behavior. However, this crash is not reproducible on OE10.2B
FIX:
There are three workarounds available:
1. Upgrade to OE10.2B with latest service pack
Or,
2. Change the MS SQL Server decimal or numeric to (10,6). After the change, delete the table from the schema holder and repull it back in to the schema holder using "Update/Add Table Definitions" from the Data Administration > DataServer > MS SQL server Utilities.
Or,
3. Dump and load the data in to the progress database table so the decimal data will be fix automatically. This way next time the buffer-copy will work fine.