Skip to Content

Access procedure inside a package

Aug 31, 2017 at 10:48 PM


avatar image
Former Member

We have recently upgraded to Oracle 12 db and are using oracle 11 client and crystal reports 13.0.5. We are not able to access procedures which are defined inside a package.

Is there any solution for this.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Ian Waterman Sep 01, 2017 at 07:58 AM

I have used Crystal with SPs in a package. You just need to name path

Execute SchemaName.PackageName.Procedure followed by parameter list.

It could be that the Crystal Reports user defined to access Oracle does not have sufficient rights to see Package or procedure.


Show 3 Share
10 |10000 characters needed characters left characters exceeded

Sorry forgot to mention this can only be done in a command. You will then need to create command parameters to replicate the Procedure Parameters. NB You can not use Report Parameters.

In command Dialog you will see in top right a create button to create parameters.


Former Member

Thanks Ian for replying back. These reports were working fine when we were using oracle 11 database. We moved to Oracle 12 g database and now we are not able to access the procedures inside the packages.

we looked into this article and created a new procedure which is calling the package and then the procedure inside it. This solution is working but we have too many of them to change.

When we try to access the reports they give database connection error when we open the reports in viwer to try to update the connection it gives "Failed to retrieve data from the database. Details: ORA-00942: table or view does not exist [Database Vendor Code:942"

Any other suggestions for this ....


Two things to try

Make sure Crystal Reports Oracle user for Logon has all the correct rights on Oracle 12


In database ->Set datasource see image

Double click Overrridden Qualified Table name and Enter name of Stored Proc so same as shown in datasource.

This will remove any legacy schema names from SQL, go to Show SQlLand make sure Query is not picking up and incorrect schemas


datasource.jpg (15.4 kB)
Don Williams
Sep 08, 2017 at 07:41 PM

CR 13.0.5 is old amnd may have problems connecting to Oracle 12c.

Upgrade to SP 21 and test again:

MUST READ the What's new to make this work now.


10 |10000 characters needed characters left characters exceeded