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 Jan 10, 2022

Enable chunk rename during log recovery

Whenever Informix performs a backup of the rootdbs, it automatically backs up Informix critical files (oncfg, onconfig & sqlhosts). When the Informix critical files are restored via "onbar -r -cf only -t <A TIMESTAMP>", it restores the latest files, ignoring the "-t" command line argument.

To restore Informix instance with chunk rename of say two day ago the process will be:

1. restore critical files backed up during the "onbar -b -L 0"

2. Parse oncfg

3. Create renamed disk subsystem to accomodate renamed instance

4. Generate informix restore file

5. Run restore

In cases a chunk (recall that the critical files are more recent), the restore as chunk did not exist in the Level 0. A typical error message is:

Unable to write storage space restore data to the database server: The old chunk path (<CHUNK PATH>, <CHUNK OFFSET>) in the input file does not exist in the backup..

This RFE is to allow onbar to continue if the the rename file contains more chunks that are not in the level 0 and also use the rename file during the logical logs apply.

Needed By Quarter