Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps products. 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 (

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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Feb 25, 2021

In the Netcool JDBC Probe it should be possible to configure a limit for the select statement

The Netcool Omnibus JDBC Probe uses a select statement to read event data from a table. The select returns everything that falls under the "where" condition - and all that data is ingested into the memory of the Probe for processing. When the number of records retrieved gets extremely high, the probe will fail with an OutOfMemory exception. Upon restart (by PA), it will either fail again, and/or, when the bkg-file already has been updated, it will loose events.
This can easily be avoided by limiting the number of records returned by the select statement. For MSSQL, this can easily be achieved by using a "select top 1000 x,y,z from a.b...". For DB2, Oracle, MySql/MariaDB and others, the limit must be post-fixed to the SQL statement (DB2: select x,y,z from a.b where condition FETCH FIRST 1000 ROWS ONLY).
Such a construct is currently impossible because the probe adds the condition for the MarkerColumn after the SQL-Statement resulting in a syntax error.
What I suggest is to add an "sql postfix" property which is pasted behind the final SQL statement by the probe. For above example, this would be "FETCH FIRST 1000 ROWS ONLY".
Apart form that, I'd also love to see a hint in the docs and the Support Guide on the fact that the probe reads everything from the select statement into memory.

Idea priority Medium
RFE ID 148869
RFE Product Tivoli Netcool/OMNIbus Probes
  • Guest
    Feb 28, 2021

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Cloud
    Product family - Operations Management
    Product - Tivoli Netcool/OMNIbus Probes
    Component - Product functionality
    Source - Other

    For recording keeping, the previous attributes were:
    Brand - Cloud
    Product family - Operations Management
    Product - Tivoli Netcool/OMNIbus
    Component - Common Integration
    Source -