nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle AI and Analytics

Child Item

in FAW implementation videos and documentation FAW ADW Dataguard is not set up.

Robin Chatterjee

Only ADW backups are taken daily. In that case how is FAW DR implemented ? As its a SaaS service does Oracel automatically restore FAW in a secondary region ?

https://videohub.oracle.com/playlist/details/1_4mvj7205/categoryId/188027173

Find more posts tagged with

Fusion HCM Analytics

Accepted answers

Subha_Tripathy-Oracle

Hi Robin,

Please refer Note 2807432.1 on My Oracle Support on this topic.

- Subha

All comments

Subha_Tripathy-Oracle

Hi Robin,

Please refer Note 2807432.1 on My Oracle Support on this topic.

- Subha

Robin Chatterjee

These are all manual solutions which require repetition of work. Also given uses can make their own changes in FAW those changes will not be replicated to the secondary site. Ther will always be additional legacy data in custom schemas and keeping two separate feeds for that is not a workable solution in this day and age. A dataguard based solution is the minimum expectation any customer would have for any kind of warehouse solution so I am afraid that though your response answers the question it does not provide a workable DR solution.

I.e this is how FAW DR is implemented, but unfortunately it's not fit for purpose of an enterprise warehouse.

FAW_User-Oracle

Please review documentation about Disaster Recovery

https://docs.oracle.com/en/cloud/saas/analytics/23r4/fawag/disaster-recovery.html#GUID-6D894569-1A83-456A-8DD4-BD12138017B2

Robin Chatterjee

This solution is not a workable solution because when we say customizations we are actually talking about custom schemas and having to pull that data twice from the various sources is not something anyone wants to keep track of. As I said before a solution that relies on manual synchronization of primary and DR in this age of automated DR and Dataguard will not be acceptable to any client.

So basically the DR strategy of FAW is tilted towards the idea that FAW only holds data from fusion and should not be used to hold stuff like historical information imported from the old EBS on-prem that was retired in favour of fusion. though there is a preview ebs adapter available there is no means to preserve this information in a DR site.

https://community.oracle.com/products/oracleanalytics/discussion/11097/faw-ebs-adaptors

Upcoming Event

AI Data Platform - Creating High Code Agents and Using Developer Tools in AI Data Platform
Explore how to build agents using code in AI Data Platform. We'll create an agent that examines and analyzes the contents of a Github repository and reports its findings. The session demonstrates how to use different developer tools to create agents including the AIDP extension for VS Code and Codex. Using these tools we…

Top Leaders

GTA 50