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).
Does Oracle have any plans to introduce LLM-based AI features in a future release of Oracle Analytics Server (OAS) on-Premises? In particular, is there a roadmap for bringing capabilities such as the Oracle Analytics AI Assistant or an LLM-powered conversational chatbot, currently available in Oracle Analytics Cloud, to…
Summary of the Enhancement We request two key enhancements to the native Waterfall visualization in OAC Workbooks to support standard financial bridge reporting: Attribute-Driven Category Axis: Allow standard categorical attributes (with custom sorting) directly on the X-axis, removing the current dependency on Date/Time…
Currently in OAC, although we can create application roles in the OCI application (e.g Service Administrator), there is no way to programmatically create and configure custom application roles in OAC itself. This has to be done via the console system settings manually in OAC. We are running a large scale OAS > OAC…
Currently, in Oracle Analytics Cloud (OAC), there is a 250GB storage limit for datasets, but there are no practical management features to operate within this limit. This makes day‑to‑day operations very inconvenient.I would like to request the following enhancements for dataset storage management: Configurable storage…
I'm not very technical so if this is a non-starter or there's a solid workaround that already exists, please advise. We have users that query SQL data sources directly in other tools, but then would like to bring that query as a dataset to OAS. Ideally they could create the view in the database and reference that object…