nerdexam
Oracle

1Z0-062 · Question #338

Which two statements are true about initialization parameter files? (Choose two.)

The correct answer is C. The ALTER SYSTEM command cannot be used to change the value of any parameter if a E. On startup, by default a database instance always first searches for an SPFILE, and if it does. Oracle databases use initialization parameter files (PFILEs or SPFILEs) to define instance configuration, with SPFILEs offering dynamic, persistent parameter management and a specific startup search order.

Managing the Database Instance

Question

Which two statements are true about initialization parameter files? (Choose two.)

Options

  • AA lost or damaged SPFILE can be re-created by using the parameter values listed in the alert
  • BA PFILE must exist for an SPFILE to be created.
  • CThe ALTER SYSTEM command cannot be used to change the value of any parameter if a
  • DBoth the SPFILE and PFILE must always reside on a file system accessible from the database
  • EOn startup, by default a database instance always first searches for an SPFILE, and if it does

How the community answered

(29 responses)
  • A
    3% (1)
  • B
    7% (2)
  • C
    86% (25)
  • D
    3% (1)

Why each option

Oracle databases use initialization parameter files (PFILEs or SPFILEs) to define instance configuration, with SPFILEs offering dynamic, persistent parameter management and a specific startup search order.

AA lost or damaged SPFILE can be re-created by using the parameter values listed in the alert

The alert log records parameter changes made during instance operation but does not contain a complete, formatted representation of all current parameter values suitable for directly recreating a lost or damaged SPFILE.

BA PFILE must exist for an SPFILE to be created.

An SPFILE can be created directly from the current instance's in-memory parameters using `CREATE SPFILE FROM MEMORY`, meaning a PFILE is not strictly required to exist as a prerequisite for SPFILE creation.

CThe ALTER SYSTEM command cannot be used to change the value of any parameter if aCorrect

If a database instance is started using a PFILE, the `ALTER SYSTEM` command cannot be used to make persistent parameter changes that would normally be written to an SPFILE; attempts to use `SCOPE=SPFILE` or `SCOPE=BOTH` will fail because no SPFILE exists to update.

DBoth the SPFILE and PFILE must always reside on a file system accessible from the database

While PFILEs are text files on a file system, SPFILEs can be stored either on a conventional file system or within Oracle Automatic Storage Management (ASM), making the assertion that both *must always* reside on a file system incorrect for SPFILEs.

EOn startup, by default a database instance always first searches for an SPFILE, and if it doesCorrect

By default, an Oracle database instance first searches for an SPFILE (e.g., `spfile<SID>.ora`, then `spfile.ora`) in specific locations, and only if an SPFILE is not found, it then searches for a PFILE (e.g., `init<SID>.ora`) to start the instance.

Concept tested: Oracle Initialization Parameters (PFILE vs. SPFILE)

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-initialization-parameters.html#GUID-7B03D1A3-BAF3-43D4-AE62-43224B406214

Topics

#PFILE#SPFILE#Initialization Parameters#Database Startup

Community Discussion

No community discussion yet for this question.

Full 1Z0-062 Practice