Feedback
Did this article resolve your question/issue?

   

Article

Failed to execute stored procedure using InitialiationString

Information

 
TitleFailed to execute stored procedure using InitialiationString
URL Namefailed-to-execute-stored-procedure-using-initialiationstring
Article Number000134477
EnvironmentProduct: Connect for ODBC Oracle Wire Protocol driver
Version: 8.0
OS: Linux
Database: Oracle
Application: All supported applications
Question/Problem Description
Calling a stored procedure using IntializationString connection option results in below error
Steps to Reproduce
Clarifying Information
Steps to reproduce :

1. CREATE TABLE TEST("NAME" VARCHAR2(200))
2. create or replace PROCEDURE insert_name (pname VARCHAR2) IS 
BEGIN 
INSERT INTO TEST(name) 
VALUES (pname); 
END insert_name;
3. Set InitializationString= begin insert_name('abc');end; 
in the Datasource
4. Try to establish a connection to the database








 
Error Message[DataDirect][ODBC Oracle Wire Protocol driver][Oracle] ORA-00600: internal error code; arguments: 12259
Defect NumberDefect XDBC-1672
Enhancement Number
Cause
Resolution
Fixed in hotfix 08.02.2114 (B0330, U0219). 
Refer to Connect and Connect64 for ODBC hot fix download and install instructions for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date11/20/2020 7:08 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.