Thursday 8 January 2015

CRS-4700: The Cluster Time Synchronization Service is in Observer mode.

CRS-4700: The Cluster Time Synchronization Service is in Observer mode.
or 
How to switch from NTP to CTSS?

It is recommended to use CTSS for a cluster to synchronize the time between cluster nodes instead of NTP.
We will find the CTSS status in observer mode when ntp.conf file is in /etc/.

1. Check if ctssd is active or not
cd /u01/app/11.2.0.4/grid/bin
[oracle@test_node01 ~]$ ./crsctl check ctss
CRS-4700: The Cluster Time Synchronization Service is in Observer mode.
[oracle@test_node02 ~]$ ./crsctl check ctss
CRS-4700: The Cluster Time Synchronization Service is in Observer mode.
We can see that CTSSD is in observer mode

2. Stop  NTP and CRS
now we are going to disable the ntp service and enable CTSS service

#crsctl stop crs
#/sbin/service ntpd stop
#mv /etc/ntp.conf /etc/ntp.conf.original

3. Start the cluster on all nodes
#crsctl start crs

4. Check that ctssd automatically starts in active mode as shown below

[root@test_node02 etc]# crsctl check ctss
CRS-4701: The Cluster Time Synchronization Service is in Active mode.
CRS-4702: Offset (in msec): 0
[root@test_node01 etc]# crsctl check ctss
CRS-4701: The Cluster Time Synchronization Service is in Active mode.
CRS-4702: Offset (in msec): 0

./cluvfy comp clocksync

Verifying Clock Synchronization across the cluster nodes

Checking if Clusterware is installed on all nodes...
Check of Clusterware install passed

Checking if CTSS Resource is running on all nodes...
CTSS resource check passed


Querying CTSS for time offset on all nodes...
Query of CTSS for time offset passed

Check CTSS state started...
CTSS is in Active state. Proceeding with check of clock time offsets on all nodes...
Check of clock time offsets passed


Oracle Cluster Time Synchronization Services check passed


Verification of Clock Synchronization across the cluster nodes was successful.

No comments:

ORA-600 [kwqitnmphe:ltbagi], [1], [0] reported in the alert log file.

ORA-00600 [kwqitnmphe:ltbagi] Cause: This issue arises in 12.1.0.2. The error occurs because there are still Historical Messages without...