Shulou(Shulou.com)06/01 Report--

Last week, we encountered a small problem with commands that need to be mastered, that is, we need to restart database monitoring. Some students even use oracle users to restart monitoring, and the principle is wrong. The following operations need to be done under the grid user.

1. Check the monitoring status

$srvctl status listenerListener LISTENER is enabledListener LISTENER is running on node (s): roidb1,roidb2 $srvctl status scan_listenerSCAN Listener LISTENER_SCAN1 is enabledSCAN listener LISTENER_SCAN1 is running on node roidb2 $

2. Turn off monitoring

$srvctl stop listener-n roidb1 $srvctl status listener-n roidb1Listener LISTENER is enabled on node (s): roidb1Listener LISTENER is not running on node (s): roidb1 $$srvctl stop scan_listener$srvctl status scan_listenerSCAN Listener LISTENER_SCAN1 is enabledSCAN listener LISTENER_SCAN1 is not running$

3. Start monitoring

$srvctl status listenerListener LISTENER is enabledListener LISTENER is running on node (s): roidb1,roidb2 $srvctl status scan_listenerSCAN Listener LISTENER_SCAN1 is enabledSCAN listener LISTENER_SCAN1 is running on node roidb2 $

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.