Which three statements regarding the server parameter file (SPFILE) are true? (Choose three.)
A.
An SPFILE is a binary file
B.
An SPFILE cannot reside on a client
C.
An SPFILE cannot contain static parameters
D.
An SPFILE can store changes persistently across instance restarts
E.
An SPFILE can be read by the database server, but it is not written to by the server
F.
An SPFILE must be created manually, before creating a database, even if you use the Database
Configuration Assistant (DBCA) to create the database
The value of this parameter is the name of the current server parameter file (SPFILE) in use. This parameter can be defined in a client side PFILE to indicate the name of the server parameter file to use.
When the default server parameter file is used by the server, the value of SPFILE is internally set by the server.
Optimizer statistics are a collection of data that describe more details about the database and the objects in the database. These statistics are used by the query optimizer to choose the best execution plan for each SQL statement.
SPFILE is a binary file that contains the same information as the old PFILE
If you do not specify spfile_name, then Oracle Database uses the platform-specific default server parameter filename. If spfile_name already exists on the server, then this statement will overwrite it. When using a default server parameter file, you start up the database without referring to the file by name.
Static are the parameters those won’t take effect immediately the value is set. Restart of system is required for them to take effect.
Dynamic are the parameters those will take effect immediately in the run time. Restart of is not required for them to take effect.
A server parameter file is initially built from a text initialization parameter file using the CREATE SPFILE statement.
The SPFILE is a server side initialization parameter file.
The instance finds the SPFILE in the location and starts up with it.
SPFILE – NO CLIENT