|
I agree. The documentation is not good. ASMB is definitely up when it's doing something other than cp (copying data) or when the DB instance just started (if spfile is in ASM). I checked a number of my databases that use ASM. All of them have ASM ASMB process running. You would think that ASMB in ASM exits when there's no activity it needs to be involved in ("ASMB process exiting due to lack of ASM file activity for ... seconds", as sometimes seen in the ASM instance alert.log.) There may be many kinds of work this process should do and some of the work always keeps this process up and running. If you find a case where ASM ASMB is not up, please show it. I'd love to see.
Documentation on RBAL is equally bad. On all databases I checked, ASM RBAL, as well as DB RBAL, is running.
One way to see what the processes are doing is to SQL-trace it with event 10046. Let us know if you find anything interesting.
> 只要在restrict模式下,那么 我就没有办法用 PLSQL developer来remote访问 ASM实例 这种方式了吗?
Can you test? When you test remotely connecting to ASM, make sure you add UR=A to tnsnames.ora. See
How to connect to ASM instance from a remote client (Oracle Net)(Doc ID 340277.1)
Get it to work with normal mode ASM running. Then restart ASM in restricted mode and try to connect again. |
|