Feedback
Did this article resolve your question/issue?

   

Article

OpenAccess server crashes calling rtrim scalar function

Information

 
TitleOpenAccess server crashes calling rtrim scalar function
URL NameOpenAccess-server-crashes-calling-rtrim-scalar-function
Article Number000132217
EnvironmentProduct: OpenAccess SDK Server
Version: 8.1.0.0063
OS: Windows 64-bit
Database: N/A
Application: odbcisql
Question/Problem Description
OpenAccess server crashes calling rtrim on column which contains many blank/empty values multiple times
Steps to ReproduceRepeatedly execute query with rtrim on column which contains many blank/empty values

Observed results:
Executing the same SQL containing rtrim over and over eventually crashes the C service.

Expected Results:
No crash.
Clarifying Information
Error MessageCrash
Defect NumberDefect 82969
Enhancement Number
Cause
Resolution
Fixed in hot fix 8.1.0.0066.
Refer to "OpenAccess SDK hot fix download and install instructions" for instructions to download and install the hot fix.
 
Workaround
Do not use rtrim function in the query.
Notes
Last Modified Date11/20/2020 7:12 AM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.