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 Functionality already exists
Workspace Db2
Components Compression
Created by Guest
Created on Jul 18, 2021

Automatically detect and uncompress NX842 compressed files in LOGPATH, OVERFLOWLOGPATH, etc.

Sometimes when after databases using a redirected restore from an online backup or db2inidb from a flash copy we are requested to copy log files from source directly into the target LOGPATH or OVERFLOWLOGPATH so that a roll forward can successfully complete.

While this works if Archive compression for logarchmeth1 LOGARCHCOMPR1=NO (no compression) and LOGARCHCOMPR1=YES (DB2 compression) this doesn't work with LOGARCHCOMPR1=NX842 as DB2 does not automatically detect and uncompress a NX842 compressed log that is in the LOGPATH.

The NX842 compressed log is usually placed into an LOGARCHMETH1 (or similar) path so that DB2 can copy with uncompress into the LOGPATH. Unfortunately, this does not work when executing a roll forward after a database copy thus the need to copy log files directly into the LOGPATH or an OVERFLOWLOGPATH.

The NX842 logs must then be sent to IBM DB2 Support so that they can execute a utility to uncompress the needed logs.

This requested idea would be to enhance DB2 to be able to detect an NX842 compressed log file where ever stored (LOGPATH, OVERFLOWLOGPATH, etc.) and automatically uncompress them as needed in the same manner that it currently does for DB2 compressed logs.

Needed By Quarter
  • Admin
    Michael Roecken
    Jul 21, 2021

    In Db2 Version 11.5.4 and onwards this functionality exists to automatically detect and un-compress ANY compressed log file in any log path managed by Db2.