Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

Best practice for OBIEE Repository Metadata Location

Received Response
32
Views
3
Comments
vkm
vkm Rank 5 - Community Champion
edited Aug 13, 2024 5:50PM in Oracle Analytics Cloud and Server

Hello,

What is the best practice to house the OBIEE Repository metadata (RCU) for OBIEE implementation? Is it recommended to create this metadata on the same database as the data warehouse or is it recommended to create a separate database for this? are there any pros and cons to each approach?

Thanks,

Answers

  • Gianni Ceresa
    Gianni Ceresa Mod

    No best practice for this. It really has a very little impact ...

    RCU is mainly used to store usage tracking if you enable it and agents schedules and logs. So there is no reason to try to look for something special for it.

    Manage it using the same process you have when needing a new schema for something, follow existing rules in your company to avoid creating something special DBAs will complain about.

    It is clearly not an source of heavy load or things like that.

  • vkm
    vkm Rank 5 - Community Champion

    Thank you very much for the information!

  • John_K
    John_K Rank 5 - Community Champion

    One thing to consider is whether archive logging has been switched off on the warehouse - it sometimes is due to the large amount of redo generated, particularly during full ETL's - and the fact that in the event of a failure it would often be quicker to just run a full ETL rather than doing a recovery.