View the Exhibit and examine the output of the query.
What do you infer from this?
A.
The SGA_TARGET is a static parameter.
B.
The instance is started, but the database is not yet open.
C.
The server parameter file (SPFILE) was used to start the instance.
D.
The SGA_TARGET parameter does not have any effect on the database instance until the
SGA_MAX_SIZE parameter is specified.
Exhibit not showing
V$PARAMETER displays information about the initialization parameters that are currently in effect for the session. A new session inherits parameter values from the instance-wide values displayed by the V$SYSTEM_PARAMETER view.
When using pfile start, sga_target of is specified set to true, if it is false, it is started using a pfile.
You can also show parameter spfile this method, if the value has a value, then use spfile start.
If there is no value, and then pfile will start.
sys@TEST0924> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
sys@TEST0924> startup pfile=’/u01/app/oracle/product/11.2.0/dbhome_1/dbs/inittest0924.ora’;
ORACLE instance started.
sys@TEST0924> show parameter spfile
NAME TYPE VALUE
——— ———– ——-
spfile string
So we can see that the spfile started.
What is the difference between a PFILE and SPFILE:
A PFILE is a static, client-side text file that must be updated with a standard text editor like “notepad” or “vi”. This file normally reside on the server.
An SPFILE (Server Parameter File), on the other hand, is a persistent server-side binary file that can only be modified with the “ALTER SYSTEM SET” command.
How will I know if my database is using a PFILE or SPFILE:
You can use the V$SPPARAMETER view to check if you are using a PFILE or not: if the “value” column is NULL for all parameters, you are using a PFILE.
V$SPPARAMETER displays information about the contents of the server parameter file.