1Z0-062 · Question #368
Which three statements are true PFILEs, SPFILEs or both? (Choose three.)
The correct answer is B. Some SPFILE parameters can be modified successfully with the SCOPE=MEMORY clause D. A PFILE can be created by an idle instance E. All SPFILE parameters can be modified successfully with the SCOPE=BOTH clause. PFILEs are editable text files, while SPFILEs are binary files managed by the database; dynamic parameters in SPFILEs can be modified in memory, and a PFILE can be created by an idle instance.
Question
Which three statements are true PFILEs, SPFILEs or both? (Choose three.)
Options
- ASPFILEs and PFILEs may both be edited with an O/S editing utility
- BSome SPFILE parameters can be modified successfully with the SCOPE=MEMORY clause
- CA SPFILE can be created by an idle instance
- DA PFILE can be created by an idle instance
- EAll SPFILE parameters can be modified successfully with the SCOPE=BOTH clause
- FAll SPFILE parameters can be modified successfully with the SCOPE=MEMORY clause
How the community answered
(41 responses)- A2% (1)
- B90% (37)
- C2% (1)
- F5% (2)
Why each option
PFILEs are editable text files, while SPFILEs are binary files managed by the database; dynamic parameters in SPFILEs can be modified in memory, and a PFILE can be created by an idle instance.
SPFILEs are binary files and should not be edited directly with an operating system utility, as this can lead to corruption.
Many SPFILE parameters are dynamic, allowing their values to be successfully changed in the current instance's memory using ALTER SYSTEM SET parameter=value SCOPE=MEMORY; without requiring a database restart.
Creating an SPFILE (e.g., using CREATE SPFILE FROM PFILE) requires an Oracle instance to be at least in the NOMOUNT state, meaning the background processes are active, which is not considered an 'idle' instance.
A PFILE is a plain text file that can be manually created or edited using an operating system utility at any time, even when no Oracle instance is running.
The ALTER SYSTEM SET command with SCOPE=BOTH updates the parameter in the SPFILE on disk, ensuring persistence, and also attempts to modify the in-memory value for dynamic parameters; while static parameters require a database restart to take effect in memory, the command successfully records their new value in the SPFILE on disk.
Only dynamic SPFILE parameters can be modified successfully using SCOPE=MEMORY; static parameters will result in an error if this clause is used.
Concept tested: Oracle PFILE and SPFILE management, parameter scopes
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/managing-initialization-parameters.html#GUID-E3A3C8B7-992F-4318-8742-9903332D7337
Topics
Community Discussion
No community discussion yet for this question.