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 Future consideration
Workspace Data Lineage by Manta
Created by Guest
Created on Apr 21, 2026

RELATED IDEAS

Support for Oracle SQL Loader Lineage in Manta

Background
In our current data pipelines, Oracle SQL Loader plays a critical role in loading data from flat files into Oracle tables. These loads are orchestrated through shell scripts and control files (.ctl), which define the mapping between input files and target database tables. This step represents a key transformation point between upstream systems (e.g., COBOL/mainframe-generated files) and downstream Oracle environments.

Current Gap
At present, Manta does not support integration with SQL Loader processes. As a result, lineage between source files and Oracle tables is not captured, creating a visibility gap between upstream technologies (such as COBOL/VSAM) and downstream database objects.

Requested Enhancement
We are requesting support for Oracle SQL Loader, including:

  • Parsing of .ctl (control) files to identify:
    • Input file sources (e.g., .dat files)
    • Target Oracle tables
    • Column-level mappings (where defined)
  • Recognition of SQL Loader executions within shell scripts
  • Integration of SQL Loader steps into end-to-end lineage, enabling visibility from upstream file-based systems into Oracle

Business Value
Supporting SQL Loader would:

  • Enable end-to-end lineage across heterogeneous systems (e.g., COBOL → file → Oracle)
  • Improve data traceability and governance for file-based ingestion patterns
  • Reduce the need for custom lineage stitching or manual mapping
  • Provide more accurate impact analysis and transparency for critical data flows
Needed By Not sure -- Just thought it was cool
  • Guest
    May 14, 2026

    Thank you for the update to this idea.

    This limitation follows the same pattern as how Manta ingests COBOL files and custom SQL scripts such as BTEQ which does not reside on the same Teradata host as the targeted databases.

    Could the potential SQL Loader scanner implement an RSYNC command? We would then specify in the scanner:

    • Server Name (server which hosts the .ctl files)
    • Directory (dir where .ctl files are stored)
    • Username and Password (user who has access to read the .ctl files).

    Thanks,

    Patrick

    Reply
  • Admin
    Yurii Plakhtii
    Apr 24, 2026

    Data lineage for Oracle SQL Loader would primarily rely on parsing control files (.ctl). A notable limitation is that these .ctl files typically reside in the filesystem, so we won't extract them automatically. As a result, they need to be manually attached to the scan or ingested through Git. Taking this feature request for the long term considerations.

    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.