Monday, September 28, 2015

Scan listener down even if it is up

Some times oem shows scan listener status down even if it is up.

Problem is with configuration.

While creating a listener_scan target in oem it stores internally on which host the listener is active.

When a scan listener is failed over to another node and still up on oem it shows down as in oem config it is checking on a different node.

If that is the case

do the following

In my case listener_scan3 is showing down

bash-3.2$ ./srvctl status scan_listener
SCAN Listener LISTENER_SCAN1 is enabled
SCAN listener LISTENER_SCAN1 is running on node hmaistmsdb2
SCAN Listener LISTENER_SCAN2 is enabled
SCAN listener LISTENER_SCAN2 is running on node hmaistmsdb1
SCAN Listener LISTENER_SCAN3 is enabled
SCAN listener LISTENER_SCAN3 is running on node hmaistmsdb1

scan3 is running on node1 but in oem its pointing towards node  2

So we need to relocate the scan listener to node 2.

bash-3.2$ ./srvctl relocate scan_listener -i 3 -n hmaistmsdb2

3 refers to listener_scan3 in above

No comments:

Post a Comment

Featured Post

Apply Patch 22191577 latest GI PSU to RAC and DB homes using Opatch auto or manual steps

Patch 22191577: GRID INFRASTRUCTURE PATCH SET UPDATE 11.2.0.4.160119 (JAN2016) Unzip the patch 22191577 Unzip latest Opatch Version in or...