Enhancement Request- Please provide restriction capability on the new OAC feature, Shared Objects inside a subject area. This is required such that we can have control in Production to limit the over utilization of this feature.
Organizations with larger user database will face significant challenges if there’s no capability to restrict access to shared objects. Relying on users not to save the shared objects they create isn’t an effective or sustainable control. This feature needs a proper access-control mechanism, and Oracle has acknowledged this, aligning with our view. As a result, we consider this a high-priority enhancement.
The feature is available.
Subject Area > Inspect dialog will show a new Access tab that will allow you to set user/group permission as Full Control vs Write. You will see a Consume option in the UI which is bug and will be removed with September 2026 update.
We’ve identified the Consume option appears to be a defect: when we change a role’s subject area access from Write to Consume, it automatically reverts back to Write.
Our requirement is to retain full control over the “Share Objects” capability tied to subject areas in OAC solely to Admin users, particularly in Production. Given the size of our user base, we can’t allow users to freely create or modify objects based on individual needs, as this will quickly lead to an unmanageable set of artefacts.
Relying on user guidance to self-restrict object creation/editing isn’t a viable control for Production.
Only Administrators can update the Access permission on Subject Area > Inspect. Access tab will not be shown for non-admin users in the SA> Inspect dialog.
On Datasets, the dataset owner controls the Access.
OAS Classic Report Results display the first 5000 rows and the OAS user needs to click the next button for the next 5000 rows and so on. The 5000 row limit is the maximum allowed to be setup in the OAS Console. OBIEE Report Results support display of the entire report results data set. Our users would like this feature in…
Background We recently identified an issue through an inconsistency in the number of records returned in an API response. This allowed us to notice, after the fact, that a fix had been applied that changed the behavior of an existing API. Problem We understand that information about resolved bugs is eventually made…
We need a way for non-admin users to view the backend/physical SQL queries executed by reports (via Session and Query Logs) without granting them full administrator access. OAC's custom Application Role model (Console > Roles and Permissions) allows selecting fine-grained permissions instead of assigning predefined roles.…
Customer would like to request that IBM DB2 12.x be added as a supported data source for Oracle Analytics Server. They hope that it will be included as a certified and supported data source in the next(Year 2027 ) OAS release. Background: The customer is currently operating a reporting and analysis platform using Oracle…
We would like to restrict the MCP to certain OAC application roles instead of all the users. Please help us to achieve this functionality.
