alter diskgroup data mount restricted;
select name,state from v$asm_diskgroup;
NAME STATE
---------------------- -------------------
DATA RESTRICTED
|
ARBx These are the slave processes that do the rebalance activity (where x is a number). CKPTThe CKPTprocess manages cross-instance calls (in RAC). DBWR This process manages the SGA buffer cache in the ASM instance. DBW Rwrites out dirty buffers (changed metadata buffers) from the ASM buffer cache to disk. GMON This process is responsible for managing the disk-level activities (drop/offline) and advancing diskgroup compatibility. KATE The Konductor or ASM Temporary Errands (KATE) process is used to process disks online. This process runs in the ASM instance and is started only when an offlined disk is onlined. LGWRThe LGWRprocess maintains the ASM Active Change Directory (ACD) buffers from the ASM instance and flushes ACD change records to disk. MARK The Mark Allocation Unit (AU) for Resync Koordinator (MARK) process coordinates the updates to the Staleness Registry when the disks go offline. This process runs in the RDBMS instance and is started only when disks go offline in ASM redundancy diskgroups. PINGThe PINGprocess measures network latency and has the same functionality in RDBMS instances. PMON This manages processes and process death in the ASM instance. PSP0 This process spawner process is responsible for creating and managing other Oracle processes. PZ9x These processes are parallel slave processes (where xis a number), used in fetching data on behalf of GV$queries. RBAL This opens all device files as part of discovery and coordinates the rebalance activity. SMON This process is the system monitor and also acts as a liaison to the Cluster Synchronization Services (CSS) process (in Oracle Clusterware) for node monitoring. VKTM This process is used to maintain the fast timer and has the same functionality in the RDBMS instances. |
*.instance_type=asm *.asm_diskgroups=DATA,FLASH *.processes=100 **** Note that asm_diskstring is site-specific and platform specific *.asm_diskstring='/dev/rdsk/c3t19d*s4' --注意假設手動加入asm 磁盤組別忘記更新這個參數否則從新啓動後缺乏的盤組沒法本身主動帶起來 *.remote_login_passwordfile='SHARED' ****** **For 11g use only the diagnostics directory. *.diagnostic_dest='/opt/app/admin/+ASM/diag' --11g的diagnostic_dest代替了10g的bdump,cdump,udump顯然簡單介紹多了 ******* **For 10g use the standard dump locations *.background_dump_dest='/opt/app/admin/+ASM/bdump' *.core_dump_dest='/opt/app/admin/+ASM/cdump' *.user_dump_dest='/opt/app/admin/+ASM/udump' ******* |
假設diagnostic_dest沒有配置,默認位置爲$ORACLE_BASE/diagnode
SQL> SELECT NAME, VALUE FROM V$DIAG_INFO NAME VALUE ---------- --------------- Diag Enabled TRUE ADR Base /u01/app/oracle ADR Home /u01/app/oracle /diag/asm/+asm/+ASM1 Diag Trace /u01/app/oracle/diag/asm/+asm/+ASM1/trace Diag Alert /u01/app/oracle/diag/asm/+asm/+ASM1/alert Diag Incident /u01/app/oracle /diag/asm/+asm/+ASM1/incident Diag Cdump /u01/app/oracle/diag/asm/+asm/+ASM1/cdump Health Monitor /u01/app/oracle/diag/asm/+asm/+ASM1/hm Default Trace File |
11g中ASM可以使用AMM特性在init.ora中配置MEMORY_TARGET和MEMORY_MAX_TARGET,與rdbms同樣這兩個參數可以實現內存本身主動管理。 然而,由於asm內存使用率很平穩。ORACLE最佳實踐是不設置這兩個參數,默認使用256M,這個配置符合大多數的環境。 譯者注:在生產環境中ASM使用默認參數可能會引起ASM實例級別的4031錯誤,依據MOS文檔建議內存至少分配1G,這與最佳實踐又是矛盾的, 可見ORACLE的最佳實踐不必定靠譜。但可做爲參考了。 |
DB_CACHE_SIZE This value determines the size of the buffer cache, which is used to cache ASM metadata blocks. The DB_CACHE_SIZEis based on a metadata block size of 4K. This block size is the buffer page size of the cached metadata and has no bearing or impact on the database block size. db_cache_size用於緩存metadata block,它是基於metadata block size 及4K。 不受db block size的影響。 SHARED_POOL This is used for standard memory usage (control structures and so on) to manage the instance. The value is also used to store open file extent maps. shared_pool用於存儲管理實例用的數據結構。假設控制結構等。同一時候也存儲 extent maps等。 LARGE_POOLThe LARGE_POOLvalue is used for large page allocations. PROCESSES This ASM init.ora parameter limits the number of processes that can start in ASM instance. You may need to modify this parameter from its default setting for Oracle Database 10gASM instances. The following recommendation pertains to Oracle Database 10.1.0.3 through 10.2.xand will work for RAC and non-RAC systems: Processes = 25 + (10 + [max number of concurrent database file creations, and file extend operations possible])*n PROCESSES配置可以基於如上公式計算。
max number of concurrent database file creations:
可以是create tablespace併發數。建立分區表涉及的表空間數,rman備份分配的通道數,併發建立歸檔數
|
SHARED_POOL_SIZE: 128MB LARGE_POOL: 12MB DB_CACHE_SIZE: 64MB |
假設這個文件被移除,健康緩存
QQ: 173386747
Email: hailong.sun1982@gmail.com
Blog: http://blog.csdn.net/card_2005
數據結構