Oracle Analytics Analyses Fail Intermittently With [nQSError: 46006] Operation cancelled

Dhamu

My Dashboard has an analysis which is resulting in below error intermittently when it is run for more periods (say more than 6) or when it has been running for more than 10 mins. Please suggest if any workarounds or solution to mitigate this.

Error Code:

[nQSError: 46066] Operation cancelled. (HY000)

GayathriAnand-Oracle

There is a limit to the number of concurrent queries that will be allowed to run beyond 10 mins in OAC. So you should either simplify the report to reduce the volume of data retrieved (rows and size) and look at optimizations to the design of the report to optimize the queries generated or you should reduce the concurrent executions of such complex reports. As Gianni mentioned there is no one formula fits all, it all depends on your usage, shape of our oac instance, design, etc. Please review the performance best practice series blog by ceal team:

https://blogs.oracle.com/analytics/post/oracle-analytics-best-practices-series-optimal-performance-and-usage

Gianni Ceresa

What product name and version are you using?

Have you seen this? Oracle Analytics Analyses Fail Intermittently With [nQSError: 46006] Operation cancelled (Doc ID 2962591.1)

Joel

For an analysis to run for 10 minutes would suggest that there is a large volume of data being processed. Reducing the data volumes being processed can help improve performance and potentially clear these types of issues. Do you actually need to return all that data or is there a chance that a redesign can reduce the data volume? These large volumes of data tend to indicate that the analytics system is being used to extract a data dump which is pumped into some other system for further analysis.

Dhamu

Hi @Gianni Ceresa - yes checked(Doc ID 2962591.1), but my RPD has already maximum number of connections (as 110) and using OAC September 2024.

Dhamu

Hi @Joel yes, my analysis has complex calculations and approx 2-3L of records for 9 months data. It is intended for daily data exports from users.

Gianni Ceresa

The issue is that errors in Oracle Analytics are fairly generic: a given error can have many possible causes.

Having a maximum connections of 110 could still be too small, it all depends on how your environment is used.

The idea behind that error, and what the MOS document doesn't say but hint to, is that you should analyze the usage of your environment: check the number of active users, check the queries the run, check if there are bottlenecks somewhere with a setting queueing request too much making them being cancelled etc.

Ideally you should go through all your logs to find out what is going on, but you are in OAC, it's a bit more challenging than that (there are ways to collect logs in OAC).