Even if this list is empty at instance startup, any existing disk
group can be manually mounted.
LARGE_POOL_SIZE The LARGE_POOL_SIZE parameter is useful for both regular and ASM
instances; however, this pool is used differently for an ASM instance. All internal ASM packages
are executed from this pool, so this parameter should be set to at least 12MB for a single instance
and 16MB for a RAC instance.
ASM_PREFERRED_READ_FAILURE_GROUPS The ASM_PREFERRED_READ_FAILURE_GROUPS
parameter, new to Oracle Database 11g, contains a list of the preferred failure groups for a given
database instance when using clustered ASM instances. This parameter is instance specific: each
instance can specify a failure group that is closest to the instance??™s node (for example, a failure
group on the server??™s local disk) to improve performance.
ASM Instance Startup and Shutdown
An ASM instance is started much like a database instance, except that the startup command
defaults to startup mount. Because there is no control file, database, or data dictionary to mount,
the ASM disk groups are mounted instead of a database. The command startup nomount starts
up the instance but does not mount any ASM disks. In addition, you can specify startup restrict to
temporarily prevent database instances from connecting to the ASM instance to mount disk groups.
Performing a shutdown command on an ASM instance performs the same shutdown command
on any database instances using the ASM instance; before the ASM instance finishes a shutdown,
it waits for all dependent databases to shut down.
Pages:
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203