Have you ever seen CRS change your Local_listener for all instances on a node?
Hello,
We just came across an instance where the oraagent aborted doing an lsnrctl check on all our listeners.
After it decided that lsnrctl problems meant the listeners were timed out, CRS changed all of our local_listener settings in memory for every instance on the node to the "LISTENER" vip & port for the cluster.
For us, this caused a huge problem, as we do not allow the default LISTENER port through the firewall... and it took us a number of hours to figure out why only 1/2 of the people were reporting errors.
We have an SR, but I'm just wondering if anyone else has ever seen anything like this? I've never had CRS change my spfile parameters that I set explicitly.
We just came across an instance where the oraagent aborted doing an lsnrctl check on all our listeners.
After it decided that lsnrctl problems meant the listeners were timed out, CRS changed all of our local_listener settings in memory for every instance on the node to the "LISTENER" vip & port for the cluster.
For us, this caused a huge problem, as we do not allow the default LISTENER port through the firewall... and it took us a number of hours to figure out why only 1/2 of the people were reporting errors.
We have an SR, but I'm just wondering if anyone else has ever seen anything like this? I've never had CRS change my spfile parameters that I set explicitly.
0