ASM instance can have many background processes. All the required database's background processes are existed in the ASM instance like ARC, CKPT, LGWR, PMON, SMON, DBWn, etc.. Additionally, below are the list of ASM primary processes
ps -ef |egrep "rbal|mark|gmon|arb|onnn|pz|vdbg|vbg|vmb"
oracle 21913 1 0 15:16 ? 00:00:00 asm_rbal_+ASM1
oracle 21915 1 0 15:16 ? 00:00:00 asm_gmon_+ASM1
oracle 22439 1 0 15:17 ? 00:00:00 ora_rbal_OLTP1
oracle 22451 1 0 15:17 ? 00:00:00 ora_mark_OLTP1
oracle 22511 1 0 15:17 ? 00:00:00 ora_rbal_BRIO1
oracle 22525 1 0 15:17 ? 00:00:00 ora_mark_BRIO1
oracle 22729 1 0 15:17 ? 00:00:00 ora_pz99_OLTP1
oracle 22755 1 0 15:17 ? 00:00:00 asm_vbg0_+ASM1
oracle 22783 1 0 15:17 ? 00:00:00 asm_vdbg_+ASM1
oracle 22785 1 0 15:17 ? 00:00:00 asm_vmb0_+ASM1
oracle 22841 1 0 15:17 ? 00:00:00 ora_pz99_BRIO1
oracle 22977 1 0 15:18 ? 00:00:00 asm_vbg1_+ASM1
oracle 22979 1 0 15:18 ? 00:00:00 asm_vbg2_+ASM1
rbal: rebalance activities
arbn: Slave - rebalance activity
gmon: Manage disk-level activities
mark: Marks ASM aollocation units as stale when needed
pz: Parallel Slave
asm_vdbg_+ASM1: Volume driver background. It's a fatal background process that can bring down ASM instance. It forwards ASM requests to lock or unlock an extent for volume operations to the dynamic volume manager.
asm_vbg1_+ASM1: Volume background process waits for requests from the dynamic volume manager.
asm_vmb0_+ASM1: Volume membership cordinates cluster member with ASM instance
No comments:
Post a Comment