Skip to Content
0
Former Member
Jan 12, 2009 at 12:03 PM

Error Calling Oracle Stored Procedure From Within Report

37 Views

Hi,

I have a report that calls an oracle stored procedure which returns a ref cursor. The report is working ok in our development environment when called from our development website through .NET.

When the report is moved and accessed from our UAT website we get the following error :-

Failed to open a rowset. Details: ADO Error Code: 0x Source: Microsoft OLE DB Provider for Oracle Description: One or more errors occurred during processing of command. Failed to open a rowset. Details: ADO Error Code: 0x Source: Microsoft OLE DB Provider for Oracle Description: ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'RHS_GET_CAND_SECTION_REFS' ORA-06550: line 1, column 7: PL/SQL: Statement ignored Native Error: Failed to open a rowset. Error in File C:\WINDOWS\TEMP\temp_d663a952-bef6-4bf7-bf1a-5e288afdb612 {9B6DFB38-A436-4940-9D80-B4C23DFFFF19}.rpt: Failed to open a rowset.

If we open the report manually we are prompted to enter database connection info. If we enter the UAT connection details the report runs ok. If we save the report and try to open it from UAT website through .NET it now opens ok.

If we then move that same report back to the development environment and open from our development website it fails with the same error above.

Both connections are using Microsoft OLE DB drivers and the Oracle databases are the same version (10.2.0.1.0).

Is the connection information being stored in actual report and somehow being used when the report is opened through .NET?

Any help appreciated

Regards

Paul