Feedback
Did this article resolve your question/issue?

   

Article

OpenAccess service crash connecting to Memory IP

Information

 
TitleOpenAccess service crash connecting to Memory IP
URL NameOpenAccess-service-crash-connecting-to-Memory-IP
Article Number000115450
EnvironmentProduct: OpenAcess SDK server
Version: 8.1.0.0088
OS: Solaris SPARC 32-bit, 64-bit
Database: N/A
Application odbcisql, example
Question/Problem Description
OpenAccess service crash connecting to Memory IP
Steps to ReproduceSteps to reproduce issue:
1) Build the C memory sample IP and start the OpenAccess C service
2) Connect to the OpenAccess Server using the OpenAccess ODBC client using the sample example program

Observed Results:
The OpenAccess C Service crashes.

Expected Results:
No crash and connection attempt should be successful without any errors.
Clarifying Information
It is a regression introduced in the product and also specific to some Solaris platforms.
Error Message
Defect NumberDefect OASL-307
Enhancement Number
Cause
OpenAccess server crashed when registering the scalar function using dam_add_scalarEx in Solaris.
Resolution
Fixed in hot fix 8.1.0.0092.
Refer to OpenAccess SDK hot fix download and install instructions for instructions to download and install the hot fix.
Workaround
Use OpenAccess 8.1 GA.
Notes
Last Modified Date11/20/2020 7:02 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.