July 29, 2010 at 2:38 pm
I’m having a problem with using an Oracle stored procedure with a Dynamic Data Source. We’re using SSRS 2005 connecting to an Oracle 10g database. We’re just getting started with SSRS so nothing is in Production yet, we are running against development.
In working on this I now have 4 versions of the same report with the differences being the combination of stored procedure and dynamic data source or shared data source. 3 of the reports works and 1 does not.
1) 620_shr_nosp – shared data source and no stored procedure – works in both Visual Studio and SSRS Report Server.
2) 620_shr_sp – shared data source and stored procedure – works in both Visual Studio and SSRS Report Server.
3) 620_dds_nosp – dynamic data source and no stored procedure – can’t test in Visual Studio and works on SSRS Report Server.
4) 620_dds_sp - dynamic data source and stored procedure - can’t test in Visual Studio and does NOT work on SSRS Report Server. I get the following error message:
An error has occurred during report processing. (rsProcessingAborted). Query execution failed for data set 'get_common_info'. (rsErrorExecutingCommand). For more information about this error navigate to the report server on the local server machine, or enable remote errors
The query string for accessing the stored procedure is - TAS_SSRS_COMMON.TAS_GET_COMMON_INFO
I’m using the same Oracle userid/password in both the shared and dynamic data sources.
Anyone have any ideas on what the problem might be?
July 30, 2010 at 2:54 pm
It's working now. We were attempting to switch to using Dynamic Data Sources from Shared and one of the things I read (and verified for myself) was that you could not test the dataset once you had done that. While that is correct I was also under the impression that you could not test the entire report, and discovered that you certainly can.
So, in testing through Visual Studio I discovered that my stored procedure data set command type had been accidentally set to Text rather than Stored Procedure. Once I fixed that it worked correctly in both Visual Studio and on the Report server.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply