ASM和数据库实例，启动和关闭

ASM启动顺序

从gpnp profile中读取ASM的初始化参数文件，获得启动实例所必须的参数
根据参数文件的设置分配SGA并启动后台进程
根据初始化参数asm_diskstring指定位置检索磁盘，挂载ASM磁盘


可以通过ASM alter.log来看一下具体ASM启动过程

SQL> show parameter dump; --查看ASM日志所在位置



NAME TYPE VALUE

------------------------------------ ----------- ------------------------------

background_core_dump string partial

background_dump_dest string /u01/app/grid/diag/asm/+asm/+A

SM1/trace

[grid@rac1 trace]$ tail -f alert_+ASM1.log



ASM实例被启动，根据gpnp profile中的信息找到了集群的网络信息（主要是集群的私网）

Starting ORACLE instance (normal)

LICENSE_MAX_SESSION = 0

LICENSE_SESSIONS_WARNING = 0

Initial number of CPU is 1

Private Interface 'eth1' configured from GPnP for use as a private interconnect.

[name='eth1', type=1, ip=10.10.10.1, mac=00-0c-29-30-bb-a6, net=10.10.10.0/24, mask=255.255.255.0, use=cluster_interconnect/6]

Public Interface 'eth0' configured from GPnP for use as a public interface.

[name='eth0', type=1, ip=192.168.11.100, mac=00-0c-29-30-bb-9c, net=192.168.11.0/24, mask=255.255.255.0, use=public/1]





可以看到ASM参数文件被发现了

Starting up:

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

With the Real Application Clusters and Automatic Storage Management options.

ORACLE_HOME = /u01/app/11.2.0/grid

System name: Linux

Node name: rac1

Release: 2.6.32-358.el6.x86_64

Version: #1 SMP Tue Jan 29 11:47:41 EST 2013

Machine: x86_64

VM name: VMWare Version: 6

Using parameter settings in server-side spfile +FRA/rac-cluster/ASMPARAMETERFILE/REGISTRY.253.1034189293







可以看到ASM实例的参数被读取，使用HAIP和集群中其他的ASM实例进行通讯

System parameters with non-default values:

large_pool_size = 12M

instance_type = "asm"

remote_login_passwordfile= "EXCLUSIVE"

asm_diskstring = "/dev/raw/raw*"

asm_diskgroups = "DATA"

asm_diskgroups = "FRA"

asm_power_limit = 1

diagnostic_dest = "/u01/app/grid"

Cluster communication is configured to use the following interface(s) for this instance

10.10.10.1

cluster interconnect IPC version:Oracle UDP/IP (generic)







ASM实例后台进程被启动

IPC Vendor 1 proto 2

Thu Mar 05 22:53:40 2020

PMON started with pid=2, OS id=6565

Thu Mar 05 22:53:40 2020

PSP0 started with pid=3, OS id=6567

Thu Mar 05 22:53:42 2020

VKTM started with pid=4, OS id=6574 at elevated priority

VKTM running at (1)millisec precision with DBRM quantum (100)ms

Thu Mar 05 22:53:42 2020

GEN0 started with pid=5, OS id=6578





实例级别Reconfiguration结束

List of instances:

1 (myinst: 1)

Global Resource Directory frozen

* allocate domain 0, invalid = TRUE

Communication channels reestablished

Master broadcasted resource hash value bitmaps

Non-local Process blocks cleaned out

LMS 0: 0 GCS shadows cancelled, 0 closed, 0 Xw survived

Set master node info

Submitted all remote-enqueue requests

Dwn-cvts replayed, VALBLKs dubious

All grantable enqueues granted

Post SMON to start 1st pass IR

Submitted all GCS remote-cache requests

Post SMON to start 1st pass IR

Fix write in gcs resources

Reconfiguration complete





ASM实例启动之后开始挂载所发现的所有磁盘组

Thu Mar 05 22:53:46 2020

SQL> ALTER DISKGROUP ALL MOUNT

NOTE: Diskgroups listed in ASM_DISKGROUPS are

DATA

FRA

NOTE: Diskgroup used for Voting files is:

DATA

Diskgroup with spfile:FRA

Diskgroup used for OCR is:ARCHIVE





磁盘组挂载成功

NOTE: cache registered group ARCHIVE number=1 incarn=0xcaca6a74

NOTE: cache began mount (first) of group ARCHIVE number=1 incarn=0xcaca6a74

NOTE: cache registered group DATA number=2 incarn=0xcaca6a75

NOTE: cache began mount (first) of group DATA number=2 incarn=0xcaca6a75

NOTE: cache registered group FRA number=3 incarn=0xcaea6a76

NOTE: cache began mount (first) of group FRA numbe
————————————————
版权声明：本文为CSDN博主「富士康质检员张全蛋」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。
原文链接：https://blog.csdn.net/qq_34556414/article/details/85274938