Oracle Exalytics Aggregates Script Intermittently Not Deleting Existing Aggregate Tables
(Doc ID 1529598.1)
Last updated on FEBRUARY 21, 2019
Applies to:Business Intelligence Suite Enterprise Edition - Version 184.108.40.206.0 to 220.127.116.11.140415 [Release 11g]
Oracle Exalytics Software - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 1.0]
Information in this document applies to any platform.
An Oracle Exalytics summary advisor script includes a "delete aggregates" statement which is intended to delete any existing aggregates with the same name. For example, an aggregates script may start out with commands as shown:
When running the script, it sometimes fails while trying to delete any existing aggregates with the same name. In these cases, any subsequent runs of the create aggregates script will result in an error similar to that shown below:
[nQSError: 84007] [Aggregate Persistence] Metadata delete failed.
[2013-01-25T14:00:04.000-05:00] [OracleBIServerComponent] [ERROR:1]  
[ecid: 004p268xGLD2FSUCi7IbKo00046h0000C1] [tid: 45993940] 
[Aggregate Persistence] Physical table
"TT_AGGR_STORE1".."EXALYTICS"."SA_Year0000A683" already exists in the RPD.
Please use DELETE AGGREGATES or manually remove the table from your RPD and your database.
This occurs intermittently and does not happen while running every aggregation script.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document