IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Add a new idea Subscribe
Status Under review
Workspace Data Lineage by Manta
Created by Guest
Created on Jun 5, 2026

RELATED IDEAS

Support Oracle lineage extraction in Data Guard read-only environments without requiring primary database access

DESCRIPTION

Many enterprise Oracle environments use Oracle Data Guard architectures where governance and metadata tools are allowed to access only read-only standby databases, while direct access to production primary databases is restricted.

Current Oracle lineage extraction relies on DBMS_METADATA.GET_DDL. In Data Guard read-only environments this approach may require write-capable database operations and can fail, forcing customers to use one of the following workarounds:

- Connect directly to production primary databases.
- Temporarily enable write access.
- Maintain additional writable Oracle instances.

These approaches conflict with common enterprise security and operational practices designed to isolate production systems from governance tooling.

IBM should provide an alternative Oracle metadata extraction mechanism compatible with Data Guard read-only environments, avoiding dependency on DBMS_METADATA.GET_DDL execution against write-capable primary databases.

A possible implementation could follow an approach similar to script-based metadata extraction methods already available for other database technologies.

This enhancement would improve adoption of Oracle lineage capabilities in large enterprise and public sector environments where Data Guard architectures are standard.

Why is it useful?

Many customers intentionally restrict metadata tools from accessing production primary Oracle databases.

Without an alternative extraction mechanism, customers must introduce architectural exceptions, operational workarounds or additional infrastructure simply to enable lineage extraction.

Supporting Data Guard read-only environments would allow lineage adoption while preserving existing governance, security and operational standards.

Who benefits?

Customers operating Oracle Data Guard environments, particularly large enterprises and public sector organizations with strict production isolation requirements.

IBM also benefits by reducing deployment friction, improving lineage adoption rates and removing a recurring objection during Oracle lineage projects.

How should it work?

Oracle lineage extraction should support a mode that does not require DBMS_METADATA.GET_DDL execution against a write-capable database.

The extraction process should be able to obtain the required metadata from Oracle Data Guard read-only environments through an alternative extraction mechanism, avoiding direct dependency on production primary databases and avoiding write operations during metadata collection.

Needed By Yesterday (Let's go already!)
  • Admin
    Yurii Plakhtii
    Jun 11, 2026

    Thank you very much for submitting this idea. We fully understand the importance of being able to obtain metadata from Oracle environments that use Oracle Data Guard architectures.

    The main challenge with metadata extraction from Oracle is that, the only possible way to retrieve the metadata is through the DBMS_METADATA.GET_DDL package. This is a long-standing limitation on the Oracle side, and unfortunately it is not something we can work around from within our product.

    That said, on our mid-term roadmap we are considering an approach that would allow lineage generation for Oracle without a direct connection to the database instance and without automatic metadata extraction, provided that the necessary metadata is supplied through an attached file. At this stage, however, this approach is still under evaluation and needs to be validated for technical and functional viability.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.