Crystal Reports runs very slow on Oracle database 12.1.0.2.0

[Former Member]

In our ERP application, we are using a lots of customized Crystal Reports. The CR are running against an Oracle database release 10.2.0.4.0 and the run time is fast and acceptable. I have been given the task to upgrade the database (actually install a brand new one on a different server) to Oracle 12c release 12.1.0.2.0. I have created the new database for testing and loaded the data into it. Both the old database (Oracle10g) and new one (Oracle 12c) are accessible through our application interface. The crystal report that runs against 10g database runs fast and is printed in less that 3 seconds. The same report when run against the 12c database runs a about 2-3 minutes and during the run time the database server CPU goes up and stays on about 25 percent for the duration of report completion. I have searched the internet for answers and even contacted the SAP support who forwarded me to this community network.
I have also contacted Oracle support but they couldn't help much either. My question is if there are any known issues running Crystal reports (2008, 2011) against an Oracle 12c (12.1.0.2.0) database or is there any recommended setting from SAP to be done on the Oracle 12c database in order to fix this huge performance issues.

Thank you

[vitaly_izmaylov]

Here is what I know:

There is a known issue with Oracle 12. The Bug number is 9723065 - slow performance on all_synonyms.

According to Oracle the problem is minor as delay per single call to the dynamic view is minimal.

Crystal Reports is querying All_synonyms and 3 other dynamic system views in Oracle database for every table in the report. It adds up to a noticable delay like you described if report connected to up to 10 tables/synonyms .

Oracle set a low priority to the issue.

Crystal Reports developers did not find an acceptable workaround solution without major changes to connectivity engine.

Some Customers are using a very old workaround solution and temporary replacing the dynamic System View with Static tables for the time of report refresh and then setting it back.

It would be the way for you to test if this is exactly your case.