IBM Data and AI Ideas Portal for Customers
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 updates on 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
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
IBM Employees should enter Ideas at https://ideas.ibm.com
This functionality can be implemented as part of the existing "Remote Log Analysis" feature in Db2 Recovery Expert. Currently, Recovery Expert supports deployment and execution with a remote Db2 instance that configures a TCPIP alias to the primary (production) database on another system. In this case, the Recovery Expert agent components run on the remote system and can read and process available Db2 archive logs locally without CPU and I/O impact on the primary Db2 system. Some access to the primary database catalog is needed via the alias connection, but this should be low impact. If log files exist on disk, they can be accessed directly or via a shared filesystem mount. However, in the current implementation, Recovery Expert cannot directly access or retrieve log files archived in a storage manager such as TSM (IBM Spectrum Protect) or other vendor software such as Commvault, Netbackup, Avamar, etc.
The plan is to add this support to Recovery Expert in the near future, making use of the standard Db2 vendor library interface, so that it can access backups and log files directly on the remote Db2 server, rather than on the primary system where the production database exists. Files will be retrieved and processed on local disk filesystems as configured for the Recovery Expert working data, which should limit the impact on the production system. Some local configuration will be needed so that Recovery Expert can access the database files that were archived to the storage manager by Db2, in a similar way that access is configured when Recovery Expert is used on a primary system. This requires standard techniques for setting the VENDOROPT, LOGARCHMETH1/LOGARCHMETH2 and LOGARCHOPT1/LOGARCHOPT2 database parameters to the appropriate values for the customer environment. This should allow supporting any vendor storage manager. including Commvault. The exact configuration details will vary depending on which storage manager is used.
With the Remote Log Analysis feature, the CPU and I/O processing will occur on the system where the Db2 instance and database alias are configured and the Recovery Expert agent components are deployed. This can be on the same system where the Recovery Expert server is installed, or the Db2 instance may be some other system. The user should ensure that the selected system has sufficient capacity in memory, CPU, and disk space to perform the needed processing tasks. The selected Db2 instance and operating system for the remote processing should match the production environment as close as possible, including the Db2 version and instance type.
Note that the Recovery Expert "Remote Log Analysis" feature is limited to performing SLR and Log Analysis requests, along with optional SQL generation and apply, either via the web browser application or the CLP command line utility. The object Recovery feature is not supported in this configuration due to certain limitations in Db2. If a recovery is needed, such as for a dropped table or tablespace, that action will need to be performed directly on the primary database environment. Recovery Expert can be deployed against the same database by both methods (remote and local), but currently cannot use a centralized SLR, so the SLR updates performed on the remote system will not be usable on the primary system. This capability may be added in a later update. From discussion with the customer, it is believed that the Log Analysis functionality should address the majority of their planned usage. If recovery features are needed from a remote system, the feasibility for adding certain support can be examined in the future.
Release timing for the requested feature has been discussed with the requesting customer and it should be available for all users in an upcoming fix release.
Db2 Recovery Expert for LUW Development Team