Oracle database connection definitions should support a centralized tnsnames.ora file.
Great idea! The benefits of centralized TNS alias management are obvious – it significantly simplifies connection configuration to all databases across the organization. With a single shared tnsnames.ora file, it's easy to update access details for all users and applications at once, without the need for individual changes. I strongly recommend giving this idea serious consideration.
tnsnames.ora
I definitely second to that.
Highly wanted feature - to be able effectively "manage" assignment of Db instance in DV connection via reference of connect descriptor defined in tnsnames.ora (central place for managing connection in our institution) instead of having to "paste" the whole connect string into connection definition. Basically we need same option as we have now when defining Connection Pool object in RPD (where in Data Source Name we refer connect descriptor from tsnames.ora). This is valid for OAS (not sure whether OAC can benefit from this).
Right now, OAC offers pre-built pages and watchlists related to NSAW. At our University, we do not need these pages, and we want to delete them entirely. We've been told in response to our SR that all we can do is keep "Access" limited to only the default admin and sysAdmin roles. This prevents regular users from seeing…
It would be nice to have a way to right click on an object (subject Area, Column, Calculation, etc.) in the Data Panel and show where that object is referenced in a workbook = canvas, visualization, filter, calculation, data action, etc.) In Workbooks with multiple canvases and multiple subject areas, we are left to hover…
We want to automate the workbook export to .dva file and import this into another OAC instance using REST API, The goal is an OCI DevOps pipeline that can promote (a) a whole folder, (b) a single workbook, or (c) several workbooks in one run to another OAC instance, and print a status result at the end. Blocker: Export and…
When Oracle Analytics AI features find an anomaly, trend or key driver, let authors save those results as a dataset or subject area. Each run would add rows with the metric, the date found, the expected versus actual value, the severity, the main drivers and the filters applied. Authors could then build workbooks, schedule…
We use the snapshot to update AppRoles members. But we would like to disable catalog content to have smaller snapshots and create snapshots faster.
