Shulou(Shulou.com)05/31 Report--

This article will explain in detail what to do about the excessive time difference of Oracle RAC nodes. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

Solution to excessive time difference of Oracle RAC nodes

1. Problem phenomenon

1.1. The OS time difference between the two RAC nodes is more than 5 minutes.

It is found that the time of the two nodes is indeed quite different.

[oraprod@ebsdb1 ~] $date

Wed Apr 30 11:27:20 CST 2014

[oraprod@ebsdb2 ~] $date

Wed Apr 30 11:22:24 CST 2014

1.2. Check the status of CTSS and find that it is in observation mode

[oraprod@ebsdb1 bin] $crsctl check ctss

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

[oraprod@ebsdb1 bin] $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 Observer state. Switching over to clock synchronization checks using NTP

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

NTP Configuration file check started...

NTP Configuration file check passed

Checking daemon liveness...

Liveness check failed for "ntpd"

Check failed on nodes:

Ebsdb1

PRVF-5494: The NTP Daemon or Service was not alive on all nodes

PRVF-5415: Check to see if NTP daemon or service is running failed

Clock synchronization check using Network Time Protocol (NTP) failed article copyright Jusin Hao (luckyfriends), support original, reprint please indicate.

PRVF-9652: Cluster Time Synchronization Services check failed

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

1.3. Found that the NTP configuration of the RAC node exists

Found that the NTP on RAC2 is active, and the NTP on RAC1 is listening.

[root@ebsdb2 ~] # service ntpd status

Ntpd (pid 7723) is running...

[root@ebsdb2 ~] # cd / etc/

[root@ebsdb2 etc] # ls-alt | grep ntp

-rw-r--r-- 1 root root 1833 Apr 16 2013 ntp.conf

-rw-r--r-- 1 root root 1833 Nov 17 2011 ntp.conf.original

Drwxr-xr-x 2 root root 4096 Jun 11 2011 ntp

[root@ebsdb2 ntp] # cd / var/run/

[root@ebsdb2 run] # ls-alt | grep ntp

-rw-r--r-- 1 root root 4 Apr 17 2013 ntpd.pid

[root@ebsdb1 ~] # service ntpd status

Ntpd is stopped

[root@ebsdb1 ~] # cd / etc/

[root@ebsdb1 etc] # ls-alt ntp*

-rw-r--r-- 1 root root 1833 Apr 16 2013 ntp.conf

two。 Problem solving process:

2.1. Stop application

A little.

2.2. Stop Oracle RAC and database

[oraprod@ebsdb1 bin] $. / crs_stat-t

Name Type Target State Host

Ora.CRS.dg ora....up.type ONLINE ONLINE ebsdb1

Ora.DATA.dg ora....up.type ONLINE ONLINE ebsdb1

Ora.FRA.dg ora....up.type ONLINE ONLINE ebsdb1

Ora....ER.lsnr ora....er.type ONLINE ONLINE ebsdb1

Ora....N1.lsnr ora....er.type ONLINE ONLINE ebsdb1

Ora.asm ora.asm.type ONLINE ONLINE ebsdb1

Ora.cvu ora.cvu.type ONLINE ONLINE ebsdb1

Ora....SM1.asm application ONLINE ONLINE ebsdb1

Ora....B1.lsnr application ONLINE ONLINE ebsdb1

Ora.ebsdb1.gsd application ONLINE OFFLINE

Ora.ebsdb1.ons application ONLINE ONLINE ebsdb1

Ora.ebsdb1.vip ora....t1.type ONLINE ONLINE ebsdb1

Ora....SM2.asm application ONLINE ONLINE ebsdb2

Ora....B2.lsnr application ONLINE ONLINE ebsdb2

Ora.ebsdb2.gsd application ONLINE OFFLINE

Ora.ebsdb2.ons application ONLINE ONLINE ebsdb2

Ora.ebsdb2.vip ora....t1.type ONLINE ONLINE ebsdb2

Ora.gsd ora.gsd.type ONLINE OFFLINE

Ora....network ora....rk.type ONLINE ONLINE ebsdb1

Ora.oc4j ora.oc4j.type ONLINE ONLINE ebsdb1

Ora.ons ora.ons.type ONLINE ONLINE ebsdb1

Ora.prod.db ora....se.type ONLINE ONLINE ebsdb2

Ora.scan1.vip ora....ip.type ONLINE ONLINE ebsdb1

[oraprod@ebsdb1 bin] $. / crs_stop-all

Attempting to stop `ora.ons` on member `ebsdb2`

Attempting to stop `ora.LISTENER.lsnr` on member `ebsdb2`

Attempting to stop `ora.cvu` on member `ebsdb1`

Attempting to stop `ora.ons` on member `ebsdb1`

Attempting to stop `ora.LISTENER.lsnr` on member `ebsdb1`

Attempting to stop `ora.LISTENER_ SCAN1.lsnr` on member `ebsdb1`

Attempting to stop `ora.oc4j` on member `ebsdb1`

Attempting to stop `ora.CRS.dg` on member `ebsdb2`

Attempting to stop `ora.DATA.dg` on member `ebsdb2`

Attempting to stop `ora.FRA.dg` on member `ebsdb2`

Attempting to stop `ora.prod.db` on member `ebsdb2`

CRS-2789: Cannot stop resource 'ora.gsd' as it is not running on server' ebsdb2'

Attempting to stop `ora.CRS.dg` on member `ebsdb1`

Attempting to stop `ora.DATA.dg` on member `ebsdb1`

Attempting to stop `ora.FRA.dg` on member `ebsdb1`

Attempting to stop `ora.prod.db` on member `ebsdb1`

CRS-2789: Cannot stop resource 'ora.gsd' as it is not running on server' ebsdb1'

Stop of `ora.cvu` on member `ebsdb1` succeeded.

Stop of `ora.LISTENER.lsnr` on member `ebsdb1` succeeded.

Attempting to stop `ora.ebsdb1.vip` on member `ebsdb1`

CRS-2789: Cannot stop resource 'ora.LISTENER.lsnr' as it is not running on server' ebsdb1'

Stop of `ora.LISTENER_ SCAN1.lsnr` on member `ebsdb1` succeeded.

Attempting to stop `ora.scan1.vip` on member `ebsdb1`

Stop of `ora.ons` on member `ebsdb1` succeeded.

CRS-2789: Cannot stop resource 'ora.ons' as it is not running on server' ebsdb1'

Stop of `ora.LISTENER.lsnr` on member `ebsdb2` succeeded.

Attempting to stop `ora.ebsdb2.vip` on member `ebsdb2`

CRS-2789: Cannot stop resource 'ora.LISTENER.lsnr' as it is not running on server' ebsdb2'

Stop of `ora.ons` on member `ebsdb2` succeeded.

CRS-2789: Cannot stop resource 'ora.ons' as it is not running on server' ebsdb2'

Stop of `ora.scan1.vip` on member `ebsdb1` succeeded.

Stop of `ora.ebsdb1.vip` on member `ebsdb1` succeeded.

Attempting to stop `ora.net1.network` on member `ebsdb1`

Stop of `ora.net1.network` on member `ebsdb1` succeeded.

Stop of `ora.ebsdb2.vip` on member `ebsdb2` succeeded.

Attempting to stop `ora.net1.network` on member `ebsdb2`

Stop of `ora.net1.network` on member `ebsdb2` succeeded.

Stop of `ora.FRA.dg` on member `ebsdb2` succeeded.

Stop of `ora.FRA.dg` on member `ebsdb1` succeeded.

Stop of `ora.oc4j` on member `ebsdb1` succeeded.

Stop of `ora.DATA.dg` on member `ebsdb1` succeeded.

Stop of `ora.DATA.dg` on member `ebsdb2` succeeded.

Stop of `ora.prod.db` on member `ebsdb2` succeeded.

Stop of `ora.CRS.dg` on member `ebsdb1` succeeded.

Stop of `ora.CRS.dg` on member `ebsdb2` succeeded.

Attempting to stop `ora.asm` on member `ebsdb2`

Stop of `ora.prod.db` on member `ebsdb1` succeeded.

Attempting to stop `ora.asm` on member `ebsdb1`

Stop of `ora.asm` on member `ebsdb2` succeeded.- waits here for a long time to stop

Attempting to stop `ora.asm` on member `ebsdb2`

CRS-2500: Cannot stop resource 'ora.asm' as it is not running

Stop of `ora.asm` on member `ebsdb2` succeeded.

Stop of `ora.asm` on member `ebsdb1` succeeded.

Attempting to stop `ora.asm` on member `ebsdb1`

CRS-0184: Cannot communicate with the CRS daemon.

2.3. ASM cannot be stopped until CRS stops

Attempting to stop `ora.asm` on member `ebsdb1`

Stop of `ora.asm` on member `ebsdb2` succeeded.- waits here for a long time to stop

Attempting to stop `ora.asm` on member `ebsdb2`

[oraprod@ebsdb1 bin] $. / crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

[oraprod@ebsdb1 bin] $crsctl check ctss

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

View asm Log

[oraprod@ebsdb1 trace] $tail-f alert_+ASM1.log

SUCCESS: ALTER DISKGROUP DATA DISMOUNT / * asm agent * / / * {1asm agent 52692asm agent 21791} * /

Freeing rdom 2

Received detach msg from inst 2 for dom 2

GMON querying group 1 at 23 for pid 18, osid 8802

Sun May 11 09:26:24 2014

NOTE: Instance updated compatible.asm to 11.2.0.0.0 for grp 1

Sun May 11 09:26:24 2014

ORA-15032: not all alterations performed

ORA-15027: active use of diskgroup "CRS" precludes (obstruction, Organization) its dismount

ERROR: ALTER DISKGROUP CRS DISMOUNT / * asm agent * / / * {1asm agent 52692asm agent 21791} * /

You can see from the log that ASM cannot dismount because CRS does not stop, this is because The OCR is located on ASM and CRSD is client of

ASM thus ASM can't be shutdown (see ORA-15097 Cannot Shutdown ASM if OCR is Located in ASM [ID 984663.1])

That is, under Oracle 11gR2, in addition to data files, OCR is also placed in ASM, so that CRSD will become the client of ASM. If

When we stop ASM directly as in Oracle 10g, we will report the above error. So, under 11gR2, if you want to stop the ASM instance

It can only be stopped with CRS. Execute under the root user: crsctl stop crs.

At the same time, be careful not to kill the ASM process directly, or use shutdown abort to shut down the ASM instance. So CRS will be hung up, too.

2.4. Stop CRS

[root@ebsdb1 ~] # cd / oradb/11.2.0/grid/bin/

[root@ebsdb1 bin] #. / crsctl stop crs

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'ebsdb1'

CRS-2673: Attempting to stop 'ora.crsd' on' ebsdb1'

CRS-2790: Starting shutdown of Cluster Ready Services-managed resources on 'ebsdb1'

CRS-4549: Unexpected disconnect while executing shutdown request.

CRS-2675: Stop of 'ora.crsd' on' ebsdb1' failed

CRS-2679: Attempting to clean 'ora.crsd' on' ebsdb1'

CRS-2681: Clean of 'ora.crsd' on' ebsdb1' succeeded

CRS-2673: Attempting to stop 'ora.mdnsd' on' ebsdb1'

CRS-2673: Attempting to stop 'ora.crf' on' ebsdb1'

CRS-2673: Attempting to stop 'ora.ctssd' on' ebsdb1'

CRS-2673: Attempting to stop 'ora.evmd' on' ebsdb1'

CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on' ebsdb1'

CRS-2677: Stop of 'ora.mdnsd' on' ebsdb1' succeeded

CRS-2677: Stop of 'ora.cluster_interconnect.haip' on' ebsdb1' succeeded

CRS-2677: Stop of 'ora.crf' on' ebsdb1' succeeded

CRS-2677: Stop of 'ora.ctssd' on' ebsdb1' succeeded

CRS-2677: Stop of 'ora.evmd' on' ebsdb1' succeeded

CRS-2673: Attempting to stop 'ora.cssd' on' ebsdb1'

CRS-2677: Stop of 'ora.cssd' on' ebsdb1' succeeded

CRS-2673: Attempting to stop 'ora.gipcd' on' ebsdb1'

CRS-2677: Stop of 'ora.gipcd' on' ebsdb1' succeeded

CRS-2673: Attempting to stop 'ora.gpnpd' on' ebsdb1'

CRS-2677: Stop of 'ora.gpnpd' on' ebsdb1' succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'ebsdb1' has completed

CRS-4133: Oracle High Availability Services has been stopped.

[root@ebsdb2 bin] #. / crsctl stop crs-f

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'ebsdb2'

CRS-2673: Attempting to stop 'ora.crf' on' ebsdb2'

CRS-2673: Attempting to stop 'ora.ctssd' on' ebsdb2'

CRS-2673: Attempting to stop 'ora.evmd' on' ebsdb2'

CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on' ebsdb2'

CRS-2673: Attempting to stop 'ora.mdnsd' on' ebsdb2'

CRS-2677: Stop of 'ora.crf' on' ebsdb2' succeeded

CRS-2677: Stop of 'ora.mdnsd' on' ebsdb2' succeeded

CRS-2677: Stop of 'ora.evmd' on' ebsdb2' succeeded

CRS-2677: Stop of 'ora.cluster_interconnect.haip' on' ebsdb2' succeeded

CRS-2677: Stop of 'ora.ctssd' on' ebsdb2' succeeded

CRS-2673: Attempting to stop 'ora.cssd' on' ebsdb2'

CRS-2677: Stop of 'ora.cssd' on' ebsdb2' succeeded

CRS-2673: Attempting to stop 'ora.gipcd' on' ebsdb2'

CRS-2677: Stop of 'ora.gipcd' on' ebsdb2' succeeded

CRS-2673: Attempting to stop 'ora.gpnpd' on' ebsdb2'

CRS-2677: Stop of 'ora.gpnpd' on' ebsdb2' succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'ebsdb2' has completed

[oraprod@ebsdb1 bin] $

[oraprod@ebsdb1 bin] $. / crs_stat-t

CRS-0184: Cannot communicate with the CRS daemon.

[oraprod@ebsdb1 bin] $ps-ef | grep asm

Oraprod 30959 28971 0 09:37 pts/1 00:00:00 grep asm

[oraprod@ebsdb1 bin] $ps-ef | grep d.bin

Oraprod 30971 28971 0 09:37 pts/1 00:00:00 grep d.bin

2.5. Adjust RAC server time

2.5.1. Synchronize the server's OS time with CMOS time

[root@ebsdb1 ~] # date

Sun May 11 09:41:57 CST 2014

[root@ebsdb1 ~] # hwclock-View the cmos time of rac1

Sun 11 May 2014 09:36:34 AM CST-0.670362 seconds

[root@ebsdb2 bin] # date

Sun May 11 09:35:57 CST 2014

[root@ebsdb2 bin] # hwclock-View the cmos time of rac2

Sun 11 May 2014 09:36:20 AM CST-0.662735 seconds

[root@ebsdb1] # clock-systohc-synchronize cmos time and os time

[root@ebsdb1 ~] # hwclock

DateSun 11 May 2014 09:43:17 AM CST-0.983102 seconds

[root@ebsdb1 ~] # date

Sun May 11 09:43:17 CST 2014

2.5.2. The modification time of EBSDB2 (RAC2) is the same as that of RAC1

[root@ebsdb1 run] # date

Sun May 11 09:54:06 CST 2014

[root@ebsdb1 run] # hwclock

Sun 11 May 2014 09:54:09 AM CST-0.920398 seconds

[root@ebsdb2 run] # date

Sun May 11 09:46:33 CST 2014

[root@ebsdb2 run] # date-s 09:54:09-the time to modify RAC2 is the same as that of RAC1

Sun May 11 09:54:09 CST 2014

[root@ebsdb2 run] # date

Sun May 11 09:54:14 CST 2014

[root@ebsdb2 run] # hwclock-r

Sun May 11 09:48:15 2014-0.045481 seconds

[root@ebsdb2 run] # clock-w-writes time to CMOS

[root@ebsdb2 run] # hwclock

Sun May 11 09:55:48 2014-0.686071 seconds

[root@ebsdb2 run] # hwclock-r

Sun May 11 09:55:53 2014-1.014941 seconds

[root@ebsdb2 run] # date

Sun May 11 09:55:55 CST 2014

2.6. Stop NTPD for OS and disable

2.6.1. Stop the NTPD service

[root@ebsdb1 ~] # service ntpd status

Ntpd is stopped

[root@ebsdb2 bin] # service ntpd status

Ntpd is stopped

[root@ebsdb2 bin] # ps-ef | grep ntpd

Root 21397 20896 0 09:40 pts/2 00:00:00 grep ntpd

2.6.2. Disable NTPD automatic start

[root@ebsdb1 ~] # chkconfig ntpd off

[root@ebsdb2 ~] # chkconfig ntpd off

2.6.3. Rename ntpd.conf

[root@ebsdb1 etc] # ls-alt | grep ntp

-rw-r--r-- 1 root root 1833 Apr 16 2013 ntp.conf

-rw-r--r-- 1 root root 1833 Nov 17 2011 ntp.conf.original

Drwxr-xr-x 2 root root 4096 Jun 11 2011 ntp

[root@ebsdb1 etc] # mv / etc/ntp.conf / etc/ntp.conf.20140511

[root@ebsdb1 etc] # ls-alt | grep ntp

-rw-r--r-- 1 root root 1833 Apr 16 2013 ntp.conf.20140511

-rw-r--r-- 1 root root 1833 Nov 17 2011 ntp.conf.original

Drwxr-xr-x 2 root root 4096 Jun 11 2011 ntp

[root@ebsdb2 etc] # ls-alt | grep ntp

-rw-r--r-- 1 root root 1833 Apr 16 2013 ntp.conf

-rw-r--r-- 1 root root 1833 Nov 17 2011 ntp.conf.original

Drwxr-xr-x 2 root root 4096 Jun 11 2011 ntp

[root@ebsdb2 etc] # mv ntp.conf ntp.conf.20140511

[root@ebsdb2 etc] # ls-alt | grep ntp

-rw-r--r-- 1 root root 1833 Apr 16 2013 ntp.conf.20140511

-rw-r--r-- 1 root root 1833 Nov 17 2011 ntp.conf.original

Drwxr-xr-x 2 root root 4096 Jun 11 2011 ntp

2.6.4. Delete PID Fil

[root@ebsdb1 etc] # cd / var/run

[root@ebsdb1 run] # ls-alt | grep ntp

[root@ebsdb2 etc] # cd / var/run

[root@ebsdb2 run] # ls-alt | grep ntp

2.7. Start Oracle RAC

[root@ebsdb1 run] # ps-ef | grep d.bin

Root 32003 29334 0 09:58 pts/2 00:00:00 grep d.bin

[root@ebsdb2 run] # ps-ef | grep d.bin

Root 21985 20896 0 09:58 pts/2 00:00:00 grep d.bin

2.7.1. Start crs for RAC1

[root@ebsdb1 bin] #. / crsctl start crs

CRS-4123: Oracle High Availability Services has been started.

[root@ebsdb1 bin] #. / crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4535: Cannot communicate with Cluster Ready Services

CRS-4530: Communications failure contacting Cluster Synchronization Services daemon

CRS-4534: Cannot communicate with Event Manager

[root@ebsdb1 bin] # ps-ef | grep d.bin

Oraprod 354 1 4 10:00? 00:00:00 / oradb/11.2.0/grid/bin/oraagent.bin

Oraprod 357 11 10:00? 00:00:00 / oradb/11.2.0/grid/bin/scriptagent.bin

Root 361 1 2 10:00? 00:00:00 / oradb/11.2.0/grid/bin/orarootagent.bin

Root 610 29334 0 10:01 pts/2 00:00:00 grep d.bin

Root 32057 1 2 09:59? 00:00:02 / oradb/11.2.0/grid/bin/ohasd.bin reboot

Oraprod 32173 1 0 09:59? 00:00:00 / oradb/11.2.0/grid/bin/oraagent.bin

Oraprod 32185 1 0 09:59? 00:00:00 / oradb/11.2.0/grid/bin/mdnsd.bin

Oraprod 32195 1 0 09:59? 00:00:00 / oradb/11.2.0/grid/bin/gpnpd.bin

Root 32206 11 09:59? 00:00:00 / oradb/11.2.0/grid/bin/orarootagent.bin

Oraprod 32208 11 09:59? 00:00:00 / oradb/11.2.0/grid/bin/gipcd.bin

Root 32223 1 8 09:59? 00:00:05 / oradb/11.2.0/grid/bin/osysmond.bin

Root 32234 1 0 09:59? 00:00:00 / oradb/11.2.0/grid/bin/cssdmonitor

Root 32252 1 0 09:59? 00:00:00 / oradb/11.2.0/grid/bin/cssdagent

Oraprod 32264 1 2 09:59? 00:00:01 / oradb/11.2.0/grid/bin/ocssd.bin

Root 32295 11 10:00? 00:00:00 / oradb/11.2.0/grid/bin/ologgerd-M-d

/ oradb/11.2.0/grid/crf/db/ebsdb1

Root 32341 10 10:00? 00:00:00 / oradb/11.2.0/grid/bin/octssd.bin reboot

Oraprod 32363 10 10:00? 00:00:00 / oradb/11.2.0/grid/bin/evmd.bin

Root 32661 1 11 10:00? 00:00:01 / oradb/11.2.0/grid/bin/crsd.bin reboot

Oraprod 32731 32363 0 10:00? 00:00:00 / oradb/11.2.0/grid/bin/evmlogger.bin-o

/ oradb/11.2.0/grid/evm/log/evmlogger.info-l / oradb/11.2.0/grid/evm/log/evmlogger.log

2.7.2. Start crs for RAC2

[root@ebsdb2 bin] #. / crsctl check crs

CRS-4639: Could not contact Oracle High Availability Services

[root@ebsdb2 bin] #. / crsctl start crs

CRS-4123: Oracle High Availability Services has been started.

[root@ebsdb2 bin] #. / crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4535: Cannot communicate with Cluster Ready Services

CRS-4530: Communications failure contacting Cluster Synchronization Services daemon

CRS-4534: Cannot communicate with Event Manager

[root@ebsdb2 bin] # ps-ef | grep d.bin

Root 22148 14 10:00? 00:00:02 / oradb/11.2.0/grid/bin/ohasd.bin reboot

Oraprod 22265 10 10:00? 00:00:00 / oradb/11.2.0/grid/bin/oraagent.bin

Oraprod 22277 10 10:00? 00:00:00 / oradb/11.2.0/grid/bin/mdnsd.bin

Oraprod 22287 11 10:00? 00:00:00 / oradb/11.2.0/grid/bin/gpnpd.bin

Root 22299 11 10:00? 00:00:00 / oradb/11.2.0/grid/bin/orarootagent.bin

Oraprod 22300 1 3 10:00? 00:00:00 / oradb/11.2.0/grid/bin/gipcd.bin

Root 22315 1 6 10:00? 00:00:01 / oradb/11.2.0/grid/bin/osysmond.bin

Root 22326 10 10:00? 00:00:00 / oradb/11.2.0/grid/bin/cssdmonitor

Root 22343 10 10:00? 00:00:00 / oradb/11.2.0/grid/bin/cssdagent

Oraprod 22355 1 3 10:00? 00:00:00 / oradb/11.2.0/grid/bin/ocssd.bin

Root 22386 1 3 10:01? 00:00:00 / oradb/11.2.0/grid/bin/ologgerd-m ebsdb1-r-d

/ oradb/11.2.0/grid/crf/db/ebsdb2

Root 22432 1 2 10:01? 00:00:00 / oradb/11.2.0/grid/bin/octssd.bin reboot

Root 22449 20896 0 10:01 pts/2 00:00:00 grep d.bin

2.7.3. Check the CTSS status has been in and out of Active mode

[root@ebsdb2 bin] #. / crsctl check ctss

CRS-4701: The Cluster Time Synchronization Service is in Active mode.

CRS-4702: Offset (in msec): 0

[root@ebsdb2 bin] #

[root@ebsdb1 bin] #. / crsctl check ctss

CRS-4701: The Cluster Time Synchronization Service is in Active mode.

CRS-4702: Offset (in msec): 0

[root@ebsdb1 bin] #

[root@ebsdb1 bin] #. / crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

[root@ebsdb2 bin] #. / crsctl check crs

CRS-4638: Oracle High Availability Services is online

CRS-4537: Cluster Ready Services is online

CRS-4529: Cluster Synchronization Services is online

CRS-4533: Event Manager is online

[root@ebsdb2 bin] #. / crsctl stat resource-t-init

NAME TARGET STATE SERVER STATE_DETAILS

Cluster Resources

Ora.asm

1 ONLINE ONLINE ebsdb2 Started

Ora.cluster_interconnect.haip

1 ONLINE ONLINE ebsdb2

Ora.crf

1 ONLINE ONLINE ebsdb2

Ora.crsd

1 ONLINE ONLINE ebsdb2

Ora.cssd

1 ONLINE ONLINE ebsdb2

Ora.cssdmonitor

1 ONLINE ONLINE ebsdb2

Ora.ctssd

1 ONLINE ONLINE ebsdb2 ACTIVE:0

Ora.diskmon

1 OFFLINE OFFLINE

Ora.evmd

1 ONLINE ONLINE ebsdb2

Ora.gipcd

1 ONLINE ONLINE ebsdb2

Ora.gpnpd

1 ONLINE ONLINE ebsdb2

Ora.mdnsd

1 ONLINE ONLINE ebsdb2

2.7.4. View cluster status

[root@ebsdb1 bin] #. / crs_stat-t

Name Type Target State Host

Ora.CRS.dg ora....up.type ONLINE ONLINE ebsdb1

Ora.DATA.dg ora....up.type ONLINE ONLINE ebsdb1

Ora.FRA.dg ora....up.type ONLINE ONLINE ebsdb1

Ora....ER.lsnr ora....er.type OFFLINE OFFLINE

Ora....N1.lsnr ora....er.type OFFLINE OFFLINE

Ora.asm ora.asm.type ONLINE ONLINE ebsdb1

Ora.cvu ora.cvu.type OFFLINE OFFLINE

Ora....SM1.asm application ONLINE ONLINE ebsdb1

Ora....B1.lsnr application OFFLINE OFFLINE

Ora.ebsdb1.gsd application ONLINE OFFLINE

Ora.ebsdb1.ons application ONLINE ONLINE ebsdb1

Ora.ebsdb1.vip ora....t1.type OFFLINE OFFLINE

Ora....SM2.asm application ONLINE ONLINE ebsdb2

Ora....B2.lsnr application OFFLINE OFFLINE

Ora.ebsdb2.gsd application ONLINE OFFLINE

Ora.ebsdb2.ons application ONLINE ONLINE ebsdb2

Ora.ebsdb2.vip ora....t1.type OFFLINE OFFLINE

Ora.gsd ora.gsd.type ONLINE OFFLINE

Ora....network ora....rk.type ONLINE ONLINE ebsdb1

Ora.oc4j ora.oc4j.type OFFLINE OFFLINE

Ora.ons ora.ons.type ONLINE ONLINE ebsdb1

Ora.prod.db ora....se.type OFFLINE OFFLINE

Ora.scan1.vip ora....ip.type OFFLINE OFFLINE

This is the end of the article on "what to do if the time difference between Oracle RAC nodes is too large". I hope the above content can be helpful to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.

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.