crystal report problem with Oracle Stored Procedure

Which 3rd party tools ? Did you check with the technical support of the vendors ?

To be clear, do the stored procedure reports work in Crystal Reports by themselves and just not in the third-party viewers or do they not work at all?

In general, reporting from Oracle stored procedures has additional requirements that aren't necessary with other databases. Here's a link to documentation:

http://scn.sap.com/docs/DOC-21842

The 3rd party tools are Jeffnet and rePortal.
The vendors said their reports should be able to run with Oracle Stored Procedures.

The stored procedure reports are able to run in crystal report design while
developing and testing.  Then we are trying to have a 3rd party tool for the users to schedule and view the reports.

I have seen the sap documentation and did not find any useful information.

If the reports work in Crystal Reports Designer then you don't really have a Crystal Reports problem.  You have a a problem with third-party products and should really contact them for support.

That being said, if either of those products are server-based, have you configured the server to use the exact same drivers and TNSnames.ora files as the development machine(s)?  When you tested the reports, did you test them on the development machine(s) or in a copy of Crystal Reports on the same server running Jeffnet and rePortal?

Unfortunately, this is a risk you take when using third-party products as opposed to compatible products from the same vendor (SAP Crystal Server, for example).

Are you hitting the same database?

What connection method for the stored procedures?

If these are server apps running the reports does the system user they run under have EXECUTE  permissions on the stored procedures?

mlmcc

Assuming that the "[Database Vendor Code: 1456 ]" message is coming from the Oracle side, this is the meaning of that message.

ORA-01456: may not perform insert/delete/update operation inside a READ ONLY transaction
Cause: A non-DDL insert/delete/update or select for update operation was attempted
Action: commit (or rollback) transaction, and re-execute

Select allOpen in new window

What that tells me is that the third party tool that you are using is setting a transaction to read only.  You need to find in that tool where you can tell it to not do that.  If that is the message that is being referred to, that should solve the problem.

I guess you are using the WEB portal version of Jeffnet. rePortal is a WEB portal too.Try to install Crystal Reports on the server or the WEB portal on the development machine to make sure that Crystal Reports is able to run the report where the 3rd party tool cannot. My expectations are that the server computer is not configured in the same way as the development machine.

I found a possible solution on SAP that I will be testing.

It has to do with setting the ODBC registry key for SAP Business Objects.

For the sake of clarification, I'm assuming you created this registry key on the server running the third-party viewer(s)?  After all, you specifically stated:

The stored procedure reports are able to run in crystal report design while
developing and testing.  Then we are trying to have a 3rd party tool for the users to schedule and view the reports.

That tells me you weren't have any issues on the actual machines running Crystal Reports, just the machines running the viewers. Did you have to create this key on servers only or on actual client machines, too?

I'm glad you found a solution that worked, but I really think you need to take a step back and examine the overall situation. You chose to evaluate two relatively popular third party products and ended up having to go to the SAP knowledge base (which you have to be a paying support customer with an S-id to access) in order to find a workaround.   In other words, you paid the original vendor to find a solution to a problem with a third-party product when you could have just used an official solution to begin with.

You might want to consider whether using a third-party tool is worth it, since you obviously didn't get the support you needed.

Also, if you look at what that key is actually controlling, that is what I said needed to be done in post ID: 38889074

You needed to change the transaction state, which is what that key controls.

seting up the key value fix the problem