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 Data & AI Roadmaps (http://ibm.biz/Data-and-AI-Roadmaps) - Use this site to view roadmaps for Data & AI products.
IBM Employees should enter Ideas at https://hybridcloudunit-internal.ideas.aha.io/
Hi. Yes you can. Depends on how you have TSM setup in your environment, but you can use a combination of db2adutl options NODENAME, OWNER and/or OPTIONS. An example for QUERY is in the link I provided earlier and the same should work for VERIFY. If it still doesn't work for you please contact IBM service and they can help you out. Thanks.
Thank you very much Michael Roecken. It worked.
One last query,
During crossnode recovery, Can we verify archive logs on TSM from different host(ofcourse TSM connectivity is there) without extracting locally?
[auto1111@open-stg-storage logs]$ db2 update db cfg for R74D111A using logarchopt1 "'-fromnode=ip-10-110-200-7 -fromowner=root'"
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
[auto1111@open-stg-storage logs]$ db2 update db cfg for R74D111A using VENDOROPT "'-fromnode=ip-10-110-200-7 -fromowner=root'"
DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.VENDOROPT is the main configuration that i was missingOn open staging server --[auto1111@open-stg-storage logs]$ db2 get db cfg for R74D111A | grep LOGARCH
First log archive method (LOGARCHMETH1) = TSM
Archive compression for logarchmeth1 (LOGARCHCOMPR1) = OFF
Options for logarchmeth1 (LOGARCHOPT1) = -fromnode=ip-10-110-200-7 -fromowner=root
Second log archive method (LOGARCHMETH2) = TSM
Archive compression for logarchmeth2 (LOGARCHCOMPR2) = OFF
Options for logarchmeth2 (LOGARCHOPT2) =
[auto1111@open-stg-storage logs]$ db2 get db cfg for R74D111A | grep VENDOROPT
Vendor options (VENDOROPT) = -fromnode=ip-10-110-200-7 -fromowner=root
[auto1111@open-stg-storage logs]$
Hi. Can you please clarify this point:
> Since db2 rollforward does currently not support read of Archive logs from TSM. it takes unnecessarily long to extract the Archive logs , up to factors.
> If db2 rollforward would be able to read Db2 archive logs, roll forward time would be probably fast.
Db2 ROLLFORWARD command will retrieve log files from TSM. As long as the system the rollforward is being run from has access to the TSM server the following steps can be done to ensure permissions to the TSM objects is possible:
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.ha.doc/doc/c0011981.html
If the target database name is different from the source database we have an additional option through LOGARCHOPTx --DBNAME (see https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.ha.doc/doc/r0006082.html).
If none of this works for you I would be interested in some more details the steps that you are blocked on.
Thanks.