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 Future consideration
Workspace Informix
Components Informix Server
Created by Guest
Created on Oct 6, 2020

Show mapped paths in ontape restore

Customer has two instances in same server one "real" for production and one for development. Development instance data is synchronized from real data by restoring production instance ontape Level 0. As both are in the same server, a chunk mapping feature is used to restore from "production" chunks to "development" chunk names.

If the mapping is not well done, we can overwrite production chunks trying to restore development instance and this can be a critical issue.

Having feedback in ontape restore process of mapped chunk names is critical before starting restore to ensure all chunks are mapped and every think will work as expected.

Needed by Date Mar 31, 2021
  • Guest
    Jun 28, 2021

    This is very useful to prevent mistakes when restoring an instance from other instance backup using mapping file.

    All chunks are in the same physical server, so a mistake in mapping file can produce an overwriting of chunks pertaining to another instance server.


    This is the mapping file:

    $cat ontape_chunks.txt

    /INFORMIXDEV/pdbreal/rootdbs        0   /INFORMIXDEV/pdbdesa/rootdbs       0
    /INFORMIXDEV/pdbreal/l_phys 0 /INFORMIXDEV/pdbdesa/l_phys 0
    /INFORMIXDEV/pdbreal/l_log1 0 /INFORMIXDEV/pdbdesa/l_log1 0

    Restore command executed in the new/copy instance:

    ontape -r -rename -f ontape_chunks.txt -t /data/BACKUP_P1/pdbreal_0_20190703_030002_L0

    Current output from ontape restore:

    Archive CheckPoint Time 06/28/2021 03:00:01
    number flags fchunk nchunks flags owner name
    1 1 1 1 N A informix rootdbs 2 1000001 2 1 N P A informix l_phys 3 1 3 1 N A informix l_log1
    chk/dbs offset size free bpages flags pathname
    1 1 0 4000000 3901872 PO--- /INFORMIXDEV/pdbreal/rootdbs
    2 2 0 11392341 5 PO--E /INFORMIXDEV/pdbreal/l_phys
    3 3 0 7000000 548973 PO--E /INFORMIXDEV/pdbreal/l_log1
    Continue restore? (y/n)

    What we want ontape restore to show:

    chk/dbs offset size free bpages flags pathname
    1 1 0 4000000 3901872 PO--- /INFORMIXDEV/pdbdesa/rootdbs
    2 2 0 11392341 5 PO--E /INFORMIXDEV/pdbdesa/l_phys
    3 3 0 7000000 548973 PO--E /INFORMIXDEV/pdbdesa/l_log1
    Continue restore? (y/n)

    It seams easy to implement and this allow us to know the mapping is done properly and prevents to restore data over existing chunks used by other instances.