Which parameter would be ignored while starting up the instance?

You want an ASM instance to manage the files of your database. To achieve this objective, you specify the following parameters in the parameter file of the database.
INSTANCE_TYPE = RDBMS
LARGE_POOL_SIZE = 8MB
BD_BLOCK_SIZE = 4K
LOG_ARCHIVE_DEST = +dgroupA
LOG_ARCHIVE_FORMAT = "$ORACLE_SID_%s_%t.%t"
DB_CREATE_FILE_DEST = +dgroupA
COMPATIBLE = 10.1.0.2.0
CONTROL_FILES = +dgroupA
Which parameter would be ignored while starting up the instance?

You want an ASM instance to manage the files of your database. To achieve this objective, you specify the following parameters in the parameter file of the database.
INSTANCE_TYPE = RDBMS
LARGE_POOL_SIZE = 8MB
BD_BLOCK_SIZE = 4K
LOG_ARCHIVE_DEST = +dgroupA
LOG_ARCHIVE_FORMAT = "$ORACLE_SID_%s_%t.%t"
DB_CREATE_FILE_DEST = +dgroupA
COMPATIBLE = 10.1.0.2.0
CONTROL_FILES = +dgroupA
Which parameter would be ignored while starting up the instance?

A.
DB_BLOCK_SIZE

B.
CONTROL_FILES

C.
LARGE_POOL_SIZE

D.
LOG_ARCHIVE_DEST

E.
LOG_ARCHIVE_FORMAT

F.
DB_CREATE_FILE_DEST

Explanation:
If you want ASM to be the default destination for creating database files, you must specify an incomplete ASM filename in one or more of the following initialization parameters:
– DB_CREATE_FILE_DEST
– DB_CREATE_ONLINE_LOG_DEST_n
– DB_RECOVERY_FILE_DEST
– CONTROL_FILES
– LOG_ARCHIVE_DEST_n
– LOG_ARCHIVE_DEST
– STANDBY_ARCHIVE_DEST
Some additional initialization parameter considerations:
– LOG_ARCHIVE_FORMAT is ignored if a disk group is specified for LOG_ARCHIVE_DEST (for example, LOG_ARCHIVE_DEST = +dgroup1).
– DB_BLOCK_SIZE must be one of the standard block sizes (2K, 4K, 8K, 16K or 32K bytes).
– LARGE_POOL_SIZE must be set to at least 1 MB.
REF.: Oracle(r) 10g Administrator Guide , 12-39



Leave a Reply 0

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