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 Not under consideration
Workspace Db2
Created by Guest
Created on Feb 11, 2015

DB2 should check if there are any errors in the history file for(RIMS)

Headline cont... the relevant backup before the restore operation is started Description: Customer canceled/aborted a backup (kill against the vendor process) of his database after some hours (the reason is not relevant for this problem). The incomplete backup image was stored in netbackup and they forgot to delete it. The next day he restored this backup image by mistake (from netbackup). The strange thing was that the restore process didn�t checked that the image was incomplete. Instead of it started until the customer found out the mistake by himself (which was after some hours). list history snippet -> ********************* --------------------------------------------------Comment: DB2 BACKUP P91 ONLINE Start Time: 20140210020046 End Time: 20140210171002 EID: 174996 Location: /usr/openv/netbackup/bin/nbdb2.sl64 SQLCA Information sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1224 sqlerrml: 0 sqlerrmc: sqlerrp : sqlubPol sqlerrd : (1) 0 (2) 0 (3) 0 (4) 0 (5) 0 (6) 0 sqlwarn : (1) (2) (3) (4) (5) (6) (7) (8) (9) (10) (11) sqlstate: Now customer had two questions:1) Doesn�t DB2 check the backup image for his integrity at the beginning of a restore process? 2) Why DB2 does not make a 'quick' check in the history file if there are any kind of errors for the relevant backup file and if YES directly abort the restore operation? In customer�s situation there was a sqlcode: -1224 message for the relevant backup.ACTION_TAKEN:************* Regarding question 1)Received feedback from the development that we don�t check the backup at the beginning of a restore operation. To validate first, you would need to download the entire image for every sequence which you might not even have enough disk space to do and would be a huge performance hitCustomer is OK with this, so this question is answered. Regarding question 2)L2 confirmed that DB2 does NOT check the recover history file BEFORE that restore is started. So the main request is: DB2 should check if there are any errors in the history file for the relevant backup (as it was in customer�s situation) before the restore operation is started.