Oracle Procedure Issue

[MD]

I'm writing to see if anyone else has experienced this issue before or if Telerik has been contacted by any other clients with a similar problem.  We have several reports that ran just fine a number of weeks ago which now return errors from Oracle.  All of the reports that are having problems utilize stored procedures.  The reports run without issue in Studio, but when executed from a web application (both locally and test server) the following message is returned every time "An error has occurred while processing Report 'ReportName': ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'ProcedureName' ORA-06550: line 1, column 7: PL/SQL: Statement ignored".  In trying to isolate the issue I created a basic report that calls a SQL Data Source with a stored procedure which just has a select * from tablename statement and only contains a cursor parameter 'CUR_RESULT OUT SYS_REFCURSOR' it runs fine in Studio, but the same error occurs in the web application.  If I move the sql statement to the report instead of the stored procedure it runs fine in both Studio in from within the web application.  I don't know if something changed on our Oracle server or Windows Update.  I've tried with three versions of Telerik reporting including the latest.

When I use a sql monitor and run the report from Studio I can see a call to bms_utility.name_resolve with the procedure name and then the actual procedure call. 

begin dbms_utility.name_resolve('Schema.ProcedureName',1,:schema,:part1,:part2,:dblink,:part1type,:objectnum); end;
begin Schema.ProcedureName(CUR_RESULT=>:CUR_RESULT); end;

I'm unable to currently profile or monitor when running the report from in a web application on IIS to see what calls are made and results returned.

Thanks

[MD]

Forgot to mention the software versions.

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
.NET 4.0
Telerik Reporting 7.1.13.802

[Stef]

Hello,

This is a quote from the answer in your support ticket on the same question:
"Please double-check the list of expected SQL parameters by the stored procedure and and the passed values from the application. In case you are using report parameters in events, notice their running values can be obtained from the processing equivalent of the report. Also if the application uses out-proc session state configuration, take a look at the Design Considerations for Out-proc Session State help article."

Let us use just one communication channel in order to keep track of the provided details and avoid splitting information between threads.

We will be waiting for your details.

Regards,
Stef
Telerik

[Sveinung]

Did you ever get to the bottom of this? Have run into a similar problem, where I get the same error message on one client, when trying to run a report that works well on another client.

Thankful for any help

[Stef]

Hello Sveinung,

Please check the attached video illustrating how to configure a SqlDataSource component to connect to an Oracle database.

Note that the selected .NET data provider determines how SQL queries are read and interpreted on the SQL server. Thus the selected data provider and corresponding database client must be installed on the machine where reports are processed.
There are also third-party additions like Glimpse that may interfere with data provider on execution of the SQL queries - Data Source Components Problems (SqlDataSource Component).

Regards,
Stef
Telerik