|
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‘ ******* |
| 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配置可以基于如上公式计算。 公式说明： where n is the number of RDBMS instance (ASM clients) connecting to ASM The source of concurrent file creations can be any of the following: Several concurrent CREATE TABLESPACEcommands Creation of a partitioned table with several tablespace creations RMAN backup channels Concurrent archive log file creations max number of concurrent database file creations：
可以是create tablespace并发数，创建分区表涉及的表空间数，rman备份分配的通道数，并发创建归档数
|
| SHARED_POOL_SIZE: 128MB LARGE_POOL: 12MB DB_CACHE_SIZE: 64MB |
ORACLE AUTOMATIC STORAGE MANAGEMENT翻译-第二章（1）,布布扣,bubuko.com
ORACLE AUTOMATIC STORAGE MANAGEMENT翻译-第二章（1）
原文：http://blog.csdn.net/card_2005/article/details/26580347