Your database instance is started with a PFILE. You want to increase the size of the buffer cache. Free memory is available to increase the size of the buffer cache. You execute the command:

SQL> ALTER SYSTEM SET DB_CACHE_SIZE=1024M; Which is the outcome?

Question

Your database instance is started with a PFILE. You want to increase the size of the buffer cache. Free memory is available to increase the size of the buffer cache. You execute the command:

SQL> ALTER SYSTEM SET DB_CACHE_SIZE=1024M; Which is the outcome?

Accepted Answer

A. Change is applied to the current instance, but does not persist after instance restart. When an Oracle database instance is started using a PFILE (parameter file), `ALTER SYSTEM SET` commands only modify the parameter value in the current running instance's memory. These changes are not written back to the PFILE, meaning they are temporary and will not persist after the database instance is restarted.

Answer

B. The value is changed only in the PFILE and takes effect at the next instance startup. The `ALTER SYSTEM SET` command does not modify the PFILE; it only changes the parameter in memory for the current instance.

Answer

C. The value is changed for the current instance and in the PFILE. While the value is changed for the current instance, it is not written to the PFILE when a PFILE is in use.

Answer

D. It fails because the SCOPE clause is missing. The command `ALTER SYSTEM SET DB_CACHE_SIZE=1024M;` is syntactically valid and will execute successfully even without an explicit `SCOPE` clause, defaulting to `SCOPE=BOTH` (which is in-memory only for PFILE) or `SCOPE=MEMORY` for some parameters.

Your database instance is started with a PFILE. You want to increase the size of the buffer cache. Free memory is available to increase the size of the buffer cache. You execute the command: SQL>…

Question

Exhibit

Options

How the community answered

Why each option

Topics

Community Discussion