This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.