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
DB_NAME = PROD
LARGE_POOL_SIZE = 8MB
DB_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 for the database PROD?
A.
LARGE_POOL_SIZE
B.
DB_CREATE_FILE_DEST
C.
LOG_ARCHIVE_DEST
D.
CONTROL_FILES
E.
LOG_ARCHIVE_FORMAT
F.
DB_BLOCK_SIZE
Explanation:
Creating Archive Log Files in ASM
Disk groups can be specified as archive log destinations in the LOG_ARCHIVE_DEST and LOG_ARCHIVE_DEST_n initialization parameters. When destinations are specified in this manner, the archive log filename will be unique, even if archived twice. All partially created archive files, created as a result of a system error, are automatically deleted.
If LOG_ARCHIVE_DEST is set to a disk group name, LOG_ARCHIVE_FORMAT is ignored. Unique filenames for archived logs are automatically created by the Oracle database. If LOG_ARCHIVE_DEST is set to a directory in a disk group, LOG_ARCHIVE_FORMAT has its normal semantics.Ref.:
Oracle Database Administrator’s Guide 10g Release 2 (10.2). Page:12-45.