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
IIDR version 11.4 should to support Oracle RAC flexibility allowing database instances up/down on any nodes for undefined lon
IIDR version 11.4 should to support Oracle RAC flexibility allowing database instances up/down on any nodes for undefined long period time within the cluster. For Oracle RAC databases, as long as one instance is up and running, the database is available. In our environment, not all Oracle RAC instances for a given database are up and running on all Oracle RAC nodes. we have defined cluster service that has the AVAILABLE and PREFERED nodes defined, the web/app server connects to a database instance using the cluster service for example, in a 4 node RAC, database A will be created with 4 instances(4 redo threads) but only 2 database instance of A will be up and functional. rest of the two database instances will be shut down and will only be started and used in the event of any of the failure of the 2 nodes where the database was up.
we also use Oracle RAC to protect IBM CDC as cluster resource, so it can fail over with Application- VIP (CDC-VIP) to an available Cluster nodes.
we expected CDC agent can come up clean and able to restart replication without any human intervention like reset bookmark or change datastore parameters.
The problem we had experienced was on a two node RAC. Instance one was down on node1, CDC on node2 can read instance 1 archive logs from the shared archive logs directory and subscription can restart replication from the fail point.
Few days later, some event caused the subscription to go down again. This time subscription cannot be restarted because it was looking for the long gone archive logs for instance 1. but if we restart instance 1 on node1, the problem went away.
we request that without having to restart the database instance on the node that was down, we should be able to re-start the subscription and continue mirroring/replication.
Do not place IBM confidential, company confidential, or personal information into any field.