在11.2后的版本中crs被称为gi，通过crsctl stop cluster来关闭整个实例的资源非常方便，，但是对于数据库实例需要单独关闭,stop cluster对于实例直接以非正常的方式结束，环境是基于12c的。
正确的顺序:
先关闭数据库
[oracle@rac1 ~]$ srvctl stop database -db tt
alert.log显示是通过immediate方式关闭.
sat apr 19 05:12:19 2014
shutting down instance (immediate)
stopping background process smco
shutting down instance: further logons disabled
stopping background process cjq0
sat apr 19 05:12:28 2014
killed process oracle@rac1 (qm05) with pid is 58, os pid 26310
stopping background process mmnl
stopping background process mmon
license high water mark = 8
all dispatchers and shared servers shutdown
alter database close normal /* db agent *//* {1:28512:1593} */
sat apr 19 05:12:33 2014
smon: disabling tx recovery
sat apr 19 05:12:33 2014
确认一下配置oracle实例是不是immediate方式来关闭的。
[oracle@rac1 ~]$ srvctl config database -db tt
database unique name: tt
database name: tt
oracle home: /u01/app/oracle/product/12.1.0.0/db_1
oracle user: oracle
spfile: +data/tt/spfilett.ora
password file: +data/tt/orapwtt
domain:
start options: open
stop options: immediate
database role: primary
management policy: automatic
server pools: tt
database instances: tt1,tt2
disk groups: data
mount point paths:
services:
type: rac
start concurrency:
stop concurrency:
database is administrator managed
[oracle@rac1 ~]$
错误的方法:
为图省事,直接关闭整个cluster
[root@rac1 ~]# crsctl stop cluster -all
crs-2673: attempting to stop 'ora.crsd' on 'rac1'
crs-2790: starting shutdown of cluster ready services-managed resources on 'rac1'
crs-2673: attempting to stop 'ora.listener.lsnr' on 'rac1'
crs-2673: attempting to stop 'ora.ocr1.dg' on 'rac1'
crs-2673: attempting to stop 'ora.tt.db' on 'rac1'
crs-2673: attempting to stop 'ora.listener_scan1.lsnr' on 'rac1'
crs-2673: attempting to stop 'ora.cvu' on 'rac1'
crs-2677: stop of 'ora.listener.lsnr' on 'rac1' succeeded
crs-2673: attempting to stop 'ora.rac1.vip' on 'rac1'
crs-2677: stop of 'ora.listener_scan1.lsnr' on 'rac1' succeeded
crs-2673: attempting to stop 'ora.scan1.vip' on 'rac1'
crs-2677: stop of 'ora.cvu' on 'rac1' succeeded
crs-2677: stop of 'ora.tt.db' on 'rac1' succeeded
crs-2673: attempting to stop 'ora.data.dg' on 'rac1'
crs-2677: stop of 'ora.rac1.vip' on 'rac1' succeeded
crs-2677: stop of 'ora.scan1.vip' on 'rac1' succeeded
crs-2673: attempting to stop 'ora.crsd' on 'rac2'
crs-2790: starting shutdown of cluster ready services-managed resources on 'rac2'
crs-2673: attempting to stop 'ora.tt.db' on 'rac2'
crs-2673: attempting to stop 'ora.ocr1.dg' on 'rac2'
crs-2673: attempting to stop 'ora.listener.lsnr' on 'rac2'
crs-2677: stop of 'ora.listener.lsnr' on 'rac2' succeeded
crs-2673: attempting to stop 'ora.rac2.vip' on 'rac2'
crs-2677: stop of 'ora.rac2.vip' on 'rac2' succeeded
crs-2677: stop of 'ora.data.dg' on 'rac1' succeeded
crs-2677: stop of 'ora.tt.db' on 'rac2' succeeded
crs-2673: attempting to stop 'ora.data.dg' on 'rac2'
crs-2677: stop of 'ora.data.dg' on 'rac2' succeeded
..............................
alert.log显示实例是非常结束
license high water mark = 6
sat apr 19 05:15:14 2014
user (ospid: 5792): terminating the instance
sat apr 19 05:15:14 2014
opiodr aborting process unknown ospid (3667) as a result of ora-1092
sat apr 19 05:15:15 2014
instance terminated by user, pid = 5792
由此可以看出通过stop cluster来关闭实例会非常危险，直接是以非正常的方式来关闭实例的.
重启实例可以看到恢复操作
sat apr 19 05:31:20 2014
beginning crash recovery of 1 threads
parallel recovery started with 2 processes
sat apr 19 05:31:21 2014
started redo scan
sat apr 19 05:31:21 2014
completed redo scan
read 255 kb redo, 69 data blocks need recovery
sat apr 19 05:31:21 2014
started redo application at
thread 2: logseq 2, block 3004
sat apr 19 05:31:22 2014
recovery of online redo log: thread 2 group 4 seq 2 reading mem 0
mem# 0: +data/tt/redo04.log
sat apr 19 05:31:22 2014
completed redo application of 0.14mb
sat apr 19 05:31:22 2014
completed crash recovery at
thread 2: logseq 2, block 3514, scn 1969283
69 data blocks read, 69 data blocks written, 255 redo k-bytes read
推荐阅读：
centos 6.3(x32)下安装oracle 10g r2
linux-6-64下安装oracle 12c笔记
本文永久更新链接地址：