We are going to have look on the steps which use to solve  RAC database installation INFO: PRVF-9652 : Cluster Time Synchronization Services check failed.

While installing Oracle RDBMS home on Oracle Grid, you may get an error as below.

ERROR:

Clock Synchronization – This test checks the Oracle Cluster Time Synchronization Services across the cluster nodes. Error:

PRVG-1015 : Timeserver “.GPS.” has time offsets that are not within permissible limit “1000.0” on nodes “wmcpredb2,wmcpredb1”. – Cause: Offsets on the identified nodes in the cluster were not within limits for specified Time Server. – Action: Ensure that the offsets for specified time server are within limits on each node of the cluster.

PRVF-5424 : Clock time offset check failed – Cause: Offsets on all of the nodes in the cluster were not within limits for any Time Server. – Action: Look at the individual messages displayed and fix the problems indicated.

Check Failed on Nodes: [test1,test2]
Verification result of failed node: test2 Details:

PRVF-5413 : Node “test2” has a time offset of 593111.0 that is beyond permissible limit of 1000.0 from NTP Time Server “.GPS.” – Cause: The time offset for the given node clock with the specified NTP Time Server is beyond permissible limits, possibly due to a clock drift, or due to an incorrectly functioning time server. – Action: Make sure that the Time Server is functioning properly, and if yes, adjust the system clock so that the offset is within limits.
Back to Top

To find the root cause, run clock sync command from $GRID_HOME/bin location as below

oracle@test:…app/oracle/product/grid12c/bin$ ./cluvfy comp clocksync -n all -verbose

Verifying Clock Synchronization across the cluster nodes

Checking if Clusterware is installed on all nodes…
Oracle Clusterware is installed on all nodes.

Checking if CTSS Resource is running on all nodes…
Check: CTSS Resource running on all nodes
Node Name Status
———————————— ————————
test1 passed
test2 passed
CTSS resource check passed

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

Check CTSS state started…
Check: CTSS state
Node Name State
———————————— ————————
test2 Observer
test1 Observer
CTSS is in Observer state. Switching over to clock synchronization checks using NTP

Starting Clock synchronization checks using Network Time Protocol(NTP)…

Checking existence of NTP configuration file “/etc/inet/ntp.conf” across nodes
Node Name File exists?
———————————— ————————
test2 yes
test1 yes
The NTP configuration file “/etc/inet/ntp.conf” is available on all nodes
NTP configuration file “/etc/inet/ntp.conf” existence check passed

Checking daemon liveness…

Check: Liveness for “ntpd”
Node Name Running?
———————————— ————————
test2 yes
test1 yes
Result: Liveness check passed for “ntpd”
Check for NTP daemon or service alive passed on all nodes

Checking whether NTP daemon or service is using UDP port 123 on all nodes

Check for NTP daemon or service using UDP port 123
Node Name Port Open?
———————————— ————————
test2 yes
test1 yes

NTP common Time Server Check started…
NTP Time Server “.GPS.” is common to all nodes on which the NTP daemon is running
Check of common NTP Time Server passed

Clock time offset check from NTP Time Server started…
Checking on nodes “[test2 , test1 ]”…
Check: Clock time offset from NTP Time Server

Time Server: .GPS.
Time Offset Limit: 1000.0 msecs
Node Name Time Offset Status
———— ———————— ————————
PRVF-5413 : Node “test1” has a time offset of 594055.0 that is beyond permissible limit of 1000.0 from NTP Time Server “.GPS.”
wmcpredb2 594055.0 failed
PRVF-5413 : Node “test2” has a time offset of 781640.0 that is beyond permissible limit of 1000.0 from NTP Time Server “.GPS.”
wmcpredb1 781640.0 failed
PRVF-5424 : Clock time offset check failed
Result: Clock synchronization check using Network Time Protocol(NTP) failed

PRVF-9652 : Cluster Time Synchronization Services check failed

Verification of Clock Synchronization across the cluster nodes was unsuccessful on all the specified nodes.

 

Now check the timestamp on both the nodes.

oracle@test1:…app/oracle/product/grid12c/bin$ ssh test1 date
Wednesday, December 2, 2015 12:38:51 PM AST
oracle@test1:…app/oracle/product/grid12c/bin$ ssh test2 date
Wednesday, December 2, 2015 12:42:04 PM AST

 

What we see is both the nodes are not in sync.

Solution:
Ask your OS admin to stop and start the ntpd. You can follow below steps.

[root@test1 ~]# service ntpd stop
[root@test1 ~]# ntpdate
[root@test1 ~]# service ntpd start

Now run cluvfy again.

oracle@test1:…app/oracle/product/grid12c/bin$ ./cluvfy comp clock sync -n all -verbose

Verifying Clock Synchronization across the cluster nodes

Checking if Clusterware is installed on all nodes…
Oracle Clusterware is installed on all nodes.

Checking if CTSS Resource is running on all nodes…
Check: CTSS Resource running on all nodes
Node Name Status
———————————— ————————
test1 passed
test2 passed
CTSS resource check passed

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

Check CTSS state started…
Check: CTSS state
Node Name State
———————————— ————————
test2 Observer
test1 Observer
CTSS is in Observer state. Switching over to clock synchronization checks using NTP

Starting Clock synchronization checks using Network Time Protocol(NTP)…

Checking existence of NTP configuration file “/etc/inet/ntp.conf” across nodes
Node Name File exists?
———————————— ————————
test2 yes
test1 yes
The NTP configuration file “/etc/inet/ntp.conf” is available on all nodes
NTP configuration file “/etc/inet/ntp.conf” existence check passed

Checking daemon liveness…

Check: Liveness for “ntpd”
Node Name Running?
———————————— ————————
test2 yes
test1 yes
Result: Liveness check passed for “ntpd”
Check for NTP daemon or service alive passed on all nodes

Checking whether NTP daemon or service is using UDP port 123 on all nodes

Check for NTP daemon or service using UDP port 123
Node Name Port Open?
———————————— ————————
test2 yes
test1 yes

NTP common Time Server Check started…
NTP Time Server “.GPS.” is common to all nodes on which the NTP daemon is running
Check of common NTP Time Server passed

Clock time offset check from NTP Time Server started…
Checking on nodes “[test2, test1 ]”…
Check: Clock time offset from NTP Time Server

Time Server: .GPS.
Time Offset Limit: 1000.0 msecs
Node Name Time Offset Status
———— ———————— ————————
test2 38.008 passed
test1 126.76 passed
Time Server “.GPS.” has time offsets that are within permissible limits for nodes “[test2,test1]”.
Clock time offset check passed

Result: Clock synchronization check using Network Time Protocol(NTP) passed

Oracle Cluster Time Synchronization Services check passed

Verification of Clock Synchronization across the cluster nodes was successful.

About The Author

Leave a Reply