Hi, assuming your DR does not want to include the data warehouse layer then this is no different to standard OBIEE => https://docs.oracle.com/cd/E25178_01/bi.1111/e10541/backup.htm

One more thought, is your hierarchy skip level or ragged hierarchy?

Hi, have you checked this with a new analysis, to rule out corruption with a particular analysis / existence of other drill functionality overlayed above and beyond the business model drill behaviour? have you also double checked the keys down your hierarchy are exactly what you think they are - looking into the physical…

Was exactly going to be my next advice, if multi-table source then join your tables as they are defined to join by the physical joins and check that the key is always populated / is always at the most granular level for the level of detail in question... +1 to Joel

Sorry - too many hierarchies in one day!!

Hi, if your time dimension is based on a detail level folder then you have bigger issues, the time hierarchy is central to so many queries and making it summarise a detail table everytime any analysis (who queries without dates!) runs will be a big impact on performance. You don't need to check your fact folder, only that…

Hi, I would run a select against the underlying physical table, select distinct year, quarter from your_table and select distinct year, quarter, quarter_key from your_table Substitute your field and table names, if the first result gives the same number of rows as the second then all is okay, if not then your key is out of…

Hi, I have seen this also. The fix is to make sure you explicitly convert it (cast to...) and never rely on implicit conversion at any point. I am not sure why this works initially, and then fails, but that is the fix.

Also, if this is an intermittent issue; - can you recreate when you bypass cache? have you checked the physical data in the table is correct for the key at that level?

Have you double checked that all of the keys are correct in the hierarchy and ensure uniqueness and correct level of granularity?

See this as a useful reference; - https://gerardnico.com/dat/obiee/obis/time_dimension

Hi, you should see 4 quarters in every year, the key at that level needs to be unique for the combination of year and quarter. Where you would need to look would be in the dimension hierarchy associated with your time dimension in the business model layer. The structure should be along the lines of; - total ¬ year ¬…

On your first comment what I was suggesting was using formula to create; - 1. a positive / negative text value to act as a group for the logic of whether it is positive or negative graphs 2. an absolute value for your values Using the combination of the two 100% will be 100%, just 100% of positive and 100% of negative, as…

Never reached 32 but once created one with 20 on 11g, so my suspicion is yes it can, and I have not seen any documented limits on number of unions.

I would double check your syntax too, there have been recent posts in a similar it errored, then on refresh it didn't and typically there was an underlying syntax issue, strip the syntax back to basics and reapply piece by piece and see what causes the error to manifest.

Okay, when you said - "When I will get back to prompt screen and press Apply once again, second opening is without problems." is this with all things the same, does just clicking apply again with no other action clear the error?

Hi, your error won't persist once the cache is cleared, this is just to get over the short term issue.

That sounds like cache, I would clear your cache, and in development in the advanced tab selection the option to bypass generally, it saves a lot of pain - in development...

You might want to add a piece of logic into your analysis for Positive / Negative and change your numbers to absolute (strip the minus from the negatives). Then have two pie charts, both of which will come to 100%, one for positive numbers, one for negative. i.e. A = 25, B=25, C=-75, D = -25, E = 50 Graph 1 Positives: A,…

Either; - "CC - Business Unit"."Business Unit - OpCo" IN case when @{PV_SELECTEDOPCO} is null then "CC - Business Unit"."Business Unit - OpCo" when @{PV_SELECTEDOPCO} = 'WhateverTheCombinationIsForAllValues' then "CC - Business Unit"."Business Unit - OpCo" else @{PV_SELECTEDOPCO}['@']{A} end Or "CC - Business…