What causes the instance startup to fail?

You want to implement ASM for the existing database instances and define the following parameters in the parameter file of the ASM instance.

DB_UNIQUE_NAME = +ASM
ASM_POWER_LIMIT = 1
ASM_DISKSTRING = ‘/dev/dsk/*s2′,’/dev/dsk/c1*’
ASM_DISKGROUPS = dgroupA, dgroup B
LARGE_POOL_SIZE = 8MB

While starting the ASM interface, you get the following error message:
ORA-15021: parameter “asm_diskstring” is not valid in RDBMS instance.
And the instance startup fails.

What causes the instance startup to fail?

You want to implement ASM for the existing database instances and define the following parameters in the parameter file of the ASM instance.

DB_UNIQUE_NAME = +ASM
ASM_POWER_LIMIT = 1
ASM_DISKSTRING = ‘/dev/dsk/*s2′,’/dev/dsk/c1*’
ASM_DISKGROUPS = dgroupA, dgroup B
LARGE_POOL_SIZE = 8MB

While starting the ASM interface, you get the following error message:
ORA-15021: parameter “asm_diskstring” is not valid in RDBMS instance.
And the instance startup fails.

What causes the instance startup to fail?

A.
ASM:DISKGROUPS cannot have two values.

B.
LARGE_POOL_SIZE should be set to lower value.

C.
ASM_POWER_LIMIT should be set to higher value.

D.
DB_NAME parameter should have been defined add set to ASM

E.
INSTANCE_TYPE parameter should have been defined add set to ASM

F.
AMS_DISKSTRING parameter should not contain any wildcard characters.

Explanation:
Some initialization parameters are specifically relevant to an ASM instance. Of those initialization parameters intended for a database instance, only a few are relevant to an ASM instance. You can set those parameters at database creation time using Database Configuration Assistant or later using Enterprise Manager. The INSTANCE_TYPE parameter must be set to ASM. This is the only required parameter. All other parameters
take suitable defaults for most environments.
REF.: Oracle(r) 10g Administrator Guide, 12-8



Leave a Reply 0

Your email address will not be published. Required fields are marked *