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

1. [grid@RAC01] $crsctl stop database-d RACwh

After the database shuts down the ok, we should shut down the crs service. Do not shut down the ASM instance directly. The information of the ocr service in 11.2.0.2 in 11g is stored on the asm disk and depends on asm, so close the crs instead of shutting down the asm instance directly. If you forcibly close the asm instance here, it is likely that the asm disk will be damaged or lost, resulting in a complete crash of the entire cluster. When I was testing RAC, after dismount a disk group, I shut down the database first, then shut down the asm instance directly, and everything was fine when I closed it. No error was reported, but when starting, it was found that asm could not start crs prompt CRS-0184: Cannot communicate with the CRS daemon. In any case, it is impossible to start CRS. Realize that there may be a problem with the voting disk or OCR, and then check the asm disk: oracleasm listdisks, there is no disk information, and oracleasm scandisks is the same situation. This is probably troublesome. After logging in to another node, the same command looks at the asm disk and finds that the disk is fine. So at this time, I also shut down the database and asm instance of the node, and then restarted the server, and then a tragic scene happened, and neither node could scan the asm disk information. The whole cluster was completely destroyed and data was lost. It may be my personal reason for this abnormal data loss, but I personally recommend shutting down startup RAC in the usual order.

2. [root@RAC01 bin] #. / crsctl stop crs

If you are careful enough, you can see the order in which RAC's CRS shuts down and which services will shut down at the same time when crs is turned off. In addition, you may also find that our command is executed on the RAC01 node, so the RAC02 node should work properly at this time. It is strongly recommended that you study the following log.

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

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

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

CRS-2673: Attempting to stop 'ora.LISTENER_SCAN3.lsnr' on' rac01'

CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on' rac01'

CRS-2673: Attempting to stop 'ora.FLASH.dg' on' rac01'

CRS-2673: Attempting to stop 'ora.OCRVD.dg' on' rac01'

CRS-2673: Attempting to stop 'ora.registry.acfs' on' rac01'

CRS-2673: Attempting to stop 'ora.DATA.dg' on' rac01'

CRS-2673: Attempting to stop 'ora.oc4j' on' rac01'

CRS-2673: Attempting to stop 'ora.LISTENER_SCAN2.lsnr' on' rac01'

CRS-2673: Attempting to stop 'ora.LISTENER_SCAN1.lsnr' on' rac01'

CRS-2677: Stop of 'ora.LISTENER_SCAN3.lsnr' on' rac01' succeeded

CRS-2673: Attempting to stop 'ora.scan3.vip' on' rac01'

CRS-2677: Stop of 'ora.scan3.vip' on' rac01' succeeded

CRS-2672: Attempting to start 'ora.scan3.vip' on' rac02'

CRS-2677: Stop of 'ora.LISTENER_SCAN2.lsnr' on' rac01' succeeded

CRS-2673: Attempting to stop 'ora.scan2.vip' on' rac01'

CRS-2677: Stop of 'ora.scan2.vip' on' rac01' succeeded

CRS-2672: Attempting to start 'ora.scan2.vip' on' rac02'

CRS-2677: Stop of 'ora.LISTENER.lsnr' on' rac01' succeeded

CRS-2673: Attempting to stop 'ora.rac01.vip' on' rac01'

CRS-2677: Stop of 'ora.LISTENER_SCAN1.lsnr' on' rac01' succeeded

CRS-2673: Attempting to stop 'ora.scan1.vip' on' rac01'

CRS-2677: Stop of 'ora.rac01.vip' on' rac01' succeeded

CRS-2672: Attempting to start 'ora.rac01.vip' on' rac02'

CRS-2677: Stop of 'ora.scan1.vip' on' rac01' succeeded

CRS-2672: Attempting to start 'ora.scan1.vip' on' rac02'

CRS-2677: Stop of 'ora.registry.acfs' on' rac01' succeeded

CRS-2677: Stop of 'ora.FLASH.dg' on' rac01' succeeded

CRS-2676: Start of 'ora.scan3.vip' on' rac02' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN3.lsnr' on' rac02'

CRS-2676: Start of 'ora.scan2.vip' on' rac02' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN2.lsnr' on' rac02'

CRS-2676: Start of 'ora.rac01.vip' on' rac02' succeeded

CRS-2676: Start of 'ora.scan1.vip' on' rac02' succeeded

CRS-2672: Attempting to start 'ora.LISTENER_SCAN1.lsnr' on' rac02'

CRS-2676: Start of 'ora.LISTENER_SCAN3.lsnr' on' rac02' succeeded

CRS-2676: Start of 'ora.LISTENER_SCAN2.lsnr' on' rac02' succeeded

CRS-2676: Start of 'ora.LISTENER_SCAN1.lsnr' on' rac02' succeeded

CRS-2677: Stop of 'ora.OCRVD.dg' on' rac01' succeeded

CRS-2677: Stop of 'ora.DATA.dg' on' rac01' succeeded

CRS-2673: Attempting to stop 'ora.asm' on' rac01'

CRS-2677: Stop of 'ora.asm' on' rac01' succeeded

CRS-2677: Stop of 'ora.oc4j' on' rac01' succeeded

CRS-2672: Attempting to start 'ora.oc4j' on' rac02'

CRS-2676: Start of 'ora.oc4j' on' rac02' succeeded

CRS-2673: Attempting to stop 'ora.eons' on' rac01'

CRS-2673: Attempting to stop 'ora.ons' on' rac01'

CRS-2677: Stop of 'ora.ons' on' rac01' succeeded

CRS-2673: Attempting to stop 'ora.net1.network' on' rac01'

CRS-2677: Stop of 'ora.net1.network' on' rac01' succeeded

CRS-2677: Stop of 'ora.eons' on' rac01' succeeded

CRS-2792: Shutdown of Cluster Ready Services-managed resources on 'rac01' has completed

CRS-2677: Stop of 'ora.crsd' on' rac01' succeeded

CRS-2673: Attempting to stop 'ora.cssdmonitor' on' rac01'

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

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

CRS-2673: Attempting to stop 'ora.asm' on' rac01'

CRS-2673: Attempting to stop 'ora.drivers.acfs' on' rac01'

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

CRS-2677: Stop of 'ora.cssdmonitor' on' rac01' succeeded

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

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

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

CRS-2677: Stop of 'ora.drivers.acfs' on' rac01' succeeded

CRS-2677: Stop of 'ora.asm' on' rac01' succeeded

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

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

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

CRS-2673: Attempting to stop 'ora.diskmon' on' rac01'

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

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

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

CRS-2677: Stop of 'ora.diskmon' on' rac01' succeeded

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

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

[root@RAC01 bin] #

3. Verify the shutdown:

[root@RAC01 bin] #. / crs_stat-t-v

CRS-0184: Cannot communicate with the CRS daemon.

[root@RAC01 bin] #

4. Start the crs service:

[root@RAC01 bin] #. / crsctl start crs- it may take some time to wait here.

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

[root@RAC01 bin] #

5. Check the startup status:

[grid@RAC02] $crs_stat-t-v

Name Type R/RA F/FT Target State Host

Ora.DATA.dg ora....up.type 0/5 0/ ONLINE ONLINE rac02

Ora.FLASH.dg ora....up.type 0/5 0/ ONLINE ONLINE rac02

Ora....ER.lsnr ora....er.type 0/5 0/ ONLINE ONLINE rac01

Ora....N1.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE rac01

Ora....N2.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE rac02

Ora....N3.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE rac02

Ora....N4.lsnr ora....er.type 0/5 0/0 ONLINE ONLINE rac02

Ora.OCRVD.dg ora....up.type 0/5 0/ ONLINE ONLINE rac01

Ora.asm ora.asm.type 0/5 0/ ONLINE ONLINE rac01

Ora.eons ora.eons.type 0/3 0/ ONLINE ONLINE rac01

Ora.gsd ora.gsd.type 0/5 0/ OFFLINE OFFLINE

Ora....network ora....rk.type 0/5 0/ ONLINE ONLINE rac01

Ora.oc4j ora.oc4j.type 0/5 0/0 ONLINE ONLINE rac02

Ora.ons ora.ons.type 0/3 0/ ONLINE ONLINE rac01

Ora....SM1.asm application 0/5 0/0 ONLINE ONLINE rac01

Ora....01.lsnr application 0/5 0/0 ONLINE ONLINE rac01

Ora.rac01.gsd application 0/5 0/0 OFFLINE OFFLINE

Ora.rac01.ons application 0/3 0/0 ONLINE ONLINE rac01

Ora.rac01.vip ora....t1.type 0/0 0/0 ONLINE ONLINE rac01

Ora....SM2.asm application 0/5 0/0 ONLINE ONLINE rac02

Ora....02.lsnr application 0/5 0/0 ONLINE ONLINE rac02

Ora.rac02.gsd application 0/5 0/0 OFFLINE OFFLINE

Ora.rac02.ons application 0/3 0/0 ONLINE ONLINE rac02

Ora.rac02.vip ora....t1.type 0/0 0/0 ONLINE ONLINE rac02

Ora.racwh.db ora....se.type 0/2 0/1 OFFLINE OFFLINE

Ora....f01.svc ora....ce.type 0 OFFLINE OFFLINE- 0 OFFLINE OFFLINE- the STAF service that I personally added.

Ora....f02.svc ora....ce.type 0 OFFLINE OFFLINE- 0 OFFLINE OFFLINE- the STAF service that I personally added.

Ora....ry.acfs ora....fs.type 0/5 0/ ONLINE ONLINE rac01

Ora.scan1.vip ora....ip.type 0/0 1/0 ONLINE ONLINE rac01

Ora.scan2.vip ora....ip.type 0/0 1/0 ONLINE ONLINE rac02

Ora.scan3.vip ora....ip.type 0/0 0/0 ONLINE ONLINE rac02

Ora.scan4.vip ora....ip.type 0/0 0/0 ONLINE ONLINE rac02

[grid@RAC02 ~] $

6. Start the database:

[grid@RAC02] $srvctl start database-d RACwh

PRCR-1079: Failed to start resource ora.racwh.db

ORA-16038: log 3 sequence# 41 cannot be archived

ORA-19504: failed to create file ""

ORA-00312: online log 3 thread 2:'+ DATA/racwh/redo03.log'

CRS-2674: Start of 'ora.racwh.db' on' rac01' failed

CRS-2632: There are no more servers to try to place resource 'ora.racwh.db' on that would satisfy its placement policy

[grid@RAC02 ~] $

In view of the above error, it is found that the original asm where the archive log is located is caused by the failure of mount. Execute the mount of the disk and then restart the database boot.

In addition, I would like to recommend a few daily startup and shutdown commands:

Other management and maintenance guidelines

one。 Managed through srvctl

1. Turn off the RAC database service order

[oracle@dbp] $srvctl stop database-d RACwh

[oracle@dbp] $srvctl stop asm-n RAC01

[oracle@dbp] $srvctl stop asm-n RAC02

[oracle@dbp] $srvctl stop nodeapps-n RAC01

[oracle@dbp] $srvctl stop nodeapps-n RAC02

two。 Start RAC database service order

[oracle@RAC01] $srvctl start nodeapps-n RAC01

[oracle@RAC01] $srvctl start nodeapps-n RAC02

[oracle@RAC01] $srvctl start asm-n RAC01

[oracle@RAC01] $srvctl start asm-n RAC02

[oracle@RAC01] $srvctl start database-d RACwh

3. Other commands

Case management

[oracle@RAC01] $srvctl status instance-d RACwh-I RACwh2

[oracle@RAC01] $srvctl stop instance-d RACwh-I RACwh2

[oracle@RAC01] $srvctl start instance-d RACwh-I RACwh2

Monitoring management

[oracle@RAC01] $srvctl status listener-n RAC01

[oracle@RAC01] $srvctl stop listener-n RAC01

[oracle@RAC01] $srvctl start listener-n RAC01

two。 Managed by crsctl tool

[oracle@RAC01] $crs_stat-t

[oracle@RAC01 ~] $crs_stat

[oracle@RAC01 ~] $crs_start-all

[oracle@RAC01 ~] $crs_stop-all

[oracle@RAC01 ~] $crs_stop "ora. RACwh.db"

The Crs_stat command tends to become obsolete after oracle11g, as shown below:

[grid@RAC02] $crs_stat-h

This command is deprecated and has been replaced by 'crsctl status resource'

This command remains for backward compatibility only

Usage: crs_stat [resource_name [...]] [- v] [- l] [- Q] [- c cluster_member]

Crs_stat [resource_name [...]]-t [- v] [- Q] [- c cluster_member]

Crs_stat-p [resource_name [...]] [- Q]

Crs_stat [- a] application-g

Crs_stat [- a] application-r [- c cluster_member]

Crs_stat-f [resource_name [...]] [- Q] [- c cluster_member]

Crs_stat-ls [resource_name [...]] [- Q]

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.