Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Delivered
Workspace Informix
Components Informix Server
Created by Guest
Created on Oct 2, 2015

SQL interface to obtain the temporary space usage (tables, hash, sorts...)

A DBA and possibly a programmer needs an easy way to monitor who is responsible for the temporary space usage.
Currently it's possible a user may be consuming a lot of temporary space and impacting other sessions, without the DBA being able to quick and easily identify the session responsible.

Other reports (from IIUG mailing list) and another RFE (36245) mentions the need for programmers to be able to find out the current session's temp tables (onstat -g ses shows this).

The definitive solution for this should be an SQL interface showing:
- session ID
- object name
- object type (explicit temp table, implicit temp table, hash join, sort ...?)
- used space
- chunk/dbspace being used
- owner nam
- ??? (PID and others, but probably thos can be gathered with joins)

This should supersede RFE ID 36245 and this includes the request for that RFE and more.
  • Guest
    Oct 16, 2019

    This was already implemented. There's a "sid" field in sysmaster:sysptnhdr which contains the session ID which created the object if it's a temporary object.
    For previous versions that don't support this (before 12.10.FC8) you can try this script:


    P.S.: An RFE system where a request that is already implemented stays open for nearly 1 year is not credible...

  • Guest
    Aug 6, 2019

    There are times when Temp space fills up.
    And there is no way to find out which session is holding all the space.

    I usually look at the onstat -u output, 
    looking for the most read-write counts
    for a session that looks like a reporting session
    And try killing it.

    But it would be really good to actually know which session is responsible.