Oracle Fusion Data Intelligence

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Fusion Data Intelligence› Oracle Fusion Data Intelligence

Categories

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

Extend Semantic model sandbox framework-Moving to Prod and semantic model refers to dev schema

Received Response
37
Views
4
Comments
VeenaP
VeenaP Rank 2 - Community Beginner
in Oracle Fusion Data Intelligence

Hi, We are facing an issue in PROD after importing and deploying semantic model bundle from Non Prod to prod.

Steps followed so far-

  1. Create custom schema in Prod ADW.
  2. Create Custom table, synonym in custom schema. Grant select access to OAX$OAC and OAX_USER.
  3. Generate and export bundle for the semantic model in Non Prod
  4. Import and deploy Semantic Model bundle in PROD
  5. There were no errors in PROD after we validated Semantic model
  6. We can see the Subject area updated with the fact and Degen Dimension but when we add it to the workbook ,it throws an error that table does not exist.
  7. Based on the execution logs , the query is checking for DEV_ADW.CUSTOM_ACT.  Hence, it is erroring in PROD as DEV_ADW is not valid schema in PROD. We created custom schema PROD_ADW in Prod

When we create logical star, are we supposed to use custom schema and custom table as we did, or should we be using the seeded schema OAX_USER only?

Could anyone please advise?

Thanks

Veena

Answers

  • JohnW-Oracle
    JohnW-Oracle Rank 7 - Analytics & AI Coach

    Hello @VeenaP,

    It seems like you found your own solution with the schema name.

    To clarify your earlier asks, if you have used data augmentation, FDI creates synonyms for each table in the OAX_USER schema. Did you use these synonyms in OAX_USER for semantic model extensions?

    Have you migrated your data augmentations?

    Regards,

    John

  • RVohra
    RVohra Rank 7 - Analytics & AI Coach

    Is it possible to check connection pool and make sure it points to your PROD PROD_ADW and not DEV_ADW?

  • VeenaP
    VeenaP Rank 2 - Community Beginner

    Thanks for your responses. I was able to resolve the issue by creating a synonym in OAX_USER for the custom schema.customtable and then use the OAX_USER synonym in the semantic model extensions.

    We have a requirement to load external source data each month in to FDI so taking this approach.

    Thanks,

    Veena

  • RVohra
    RVohra Rank 7 - Analytics & AI Coach

    Appreciate you sharing the solution here. It will definitely help someone.