Reporting and Analytics for Sales

Get Involved. Join the Conversation.

Topic

    Ling Xiang
    R13.19A OTBI Direct Database Query Privilege Change
    Topic posted February 6, 2019 by Ling XiangGold Trophy: 10,000+ Points, last edited February 19, 2019, tagged BI Publisher, Shared Reports 
    618 Views, 8 Comments
    Title:
    R13.19A OTBI Direct Database Query Privilege Change
    Summary:
    In R13.19A OTBI direct database query has been disabled by default. To prevent reports generating system errors, BI Administrator can modify BI privileges to revert this change.
    Content:

    What is the Change?

    Prior to R13.19A, BI Administrator has the privilege to create and run Direct Database Query in BI Answers.  In R13.19A, this feature has been disabled by default.  Specifically, two privileges that control direct database query access, namely ‘Edit Direct Database Analysis’ and ‘Execute Direct Database Analysis’,  have been denied for authenticated users. 

    Reports created with ‘Direct Database Query’ option prior to R13.19A will receive a system error when executed in R13.19A.  To prevent the system error, customers can revert the R13.19A privilege changes by granting BI Administrator privilege to both ‘Edit Direct Database Analysis and ‘Execute Direct Database Analysis’.  

    Please note: This change does not affect BI Publisher SQL reports created with BI Publisher Data Model or BI Answers reports created with Logical SQL.

    How to revert the change?

    BI Administrator can modify direct database analysis privileges in BI Administration -> Manage Privileges page.  To grant BI Administrator access to direct database query, customers can remove ‘Authenticated User’ that has ‘Denied’ permission from the seeded privileges and add a new role of ‘BI Administrator Role’ with ‘Granted’ permission. 

    Repeat the same step to grant ‘BI Administrator Role’ to ‘Execute Direct Database Analysis’ privilege.  

    Future Product Direction

    Direct database query is not a supported OTBI feature for building reports.  Customers are encouraged to use BI Answers to create interactive analyses, use BI Publisher for fixed-format reports and use BI Cloud Connector (BICC) for data extraction.  If customers have created OTBI reports with Direct Database Query option, Oracle development strongly recommends migrating those reports to use OTBI subject areas as Direct Database Query will be deprecated in OTBI in 12 months. 

    Please refer to attached document for more detailed information.  If you have further questions, please contact Oracle Support.

    Comment

     

    • Reghu

      Thanks Ling for sharing this. 

       

      Say if I have a Data model based report generating forms (RTF), will that also be deprecatetd?

      • Ling Xiang

        This doesn't affect BI Publisher SQL reports.  If you have created reports using New -> Create Direct Database Query option in BI Answers, this applies.

        Ling

    • Reghu

      Thanks a lot for clarifying this.  I was panicked.

    • Rajagopalan Srinivasan

      We have added both the above privileges but still we are getting 'You do not have the necessary privileges to create or edit Direct Database Analysis.' error.

      Application version is 19D.

      • Priscila Terazawa

        Hi Rajagopalan,

        There was another communication about this feature.

        In Fusion Applications Update 19D, Oracle will discontinue the Direct Database Query option for writing reports using BI Answers.  As a result, you will not be able to create or modify new reports, but you will be able to run your existing (saved) reports through the end of Update 19D.

        In Update 20A, the Direct Database Query option will be permanently disabled, meaning you will no longer be able to create, modify or run these types of reports.

        Thanks,

        Priscila

    • Becki Willard

      Is there anyone that can open a .catalog file to get the sql out of it to create a data model from it? We are on 19D.

      • Priscila Terazawa

        Becki,

        As a workaround, what you can do is to run the report, then go to Administration > Manage Session and find the nqquery log generated by that report.
        You can get the SQL details from there.

        Regards,
        Priscila