This is an IBM Automation portal for Cloud Management and AIOps products. 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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on-premises, containers, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Add an option to solve from the "Stuck Online" state, when you don't WANT to STOP the resource
In a DB2 HADR cluster been managed by TSA (SAMP) policy, somehow the hadr database resource was reporting "Stuck Online" state.
Everyghing was fine from DB2 and HADR perspective, Instace was UP, HADR was running normally, both primary and Standby DB were connected and in PEER state. Applications were connected to the database and running as well. Also, running the monitor command manually, was reporting 1 (online).
So, there was no reason to STOP the resource to get rid of the "Stuck Online" been reported on lssam ouput. We just need a way to tell TSA: "Hey TSA, This resouce is FINE now, start monitoring it again"
Only way to get rid of that, on this state was to hack it. killing the IBM.GblResRMd process on the server it was reporting the "stuck online" state.
We are requesting to add an official option to kind of "reset" the rs, without stopping IT, just instruct TSA that the issue is gone, and restart monitoring it again using regular TSA commands.
Do not place IBM confidential, company confidential, or personal information into any field.