nerdexam
Oracle

1Z0-062 · Question #375

A PFILE exists for your database. You want to increase the value of the PROCESSES parameter from 300 to 400 and make it persistent for your database instance. You plan to use the ALTER SYSTEM…

The correct answer is C. Create an SPFILE, start the database instance by using the SPFILE, and then execute the ALTER F. Use the PFILE to STARTUP MOUNT the database instance, and then execute the ALTER SYSTEM. To persistently increase the static PROCESSES parameter using ALTER SYSTEM when a PFILE exists, you must ensure an SPFILE is active, then use ALTER SYSTEM SET with SCOPE=SPFILE, and finally restart the database.

Managing the Database Instance

Question

A PFILE exists for your database. You want to increase the value of the PROCESSES parameter from 300 to 400 and make it persistent for your database instance. You plan to use the ALTER SYSTEM command. Which two methods can be used? (Choose two.)

Options

  • AEdit PFILE manually, re-create the SPFILE from the edited PFILE, and restart the database
  • BCreate an SPFILE, start the database instance by using the SPFILE, and then execute the ALTER
  • CCreate an SPFILE, start the database instance by using the SPFILE, and then execute the ALTER
  • DCreate an SPFILE, STARTUP MOUNT the database instance by using the SPFILE, and then
  • EStart the database instance by using the PFILE, and then execute the ALTER SYSTEM SET
  • FUse the PFILE to STARTUP MOUNT the database instance, and then execute the ALTER SYSTEM

How the community answered

(52 responses)
  • A
    6% (3)
  • B
    12% (6)
  • C
    79% (41)
  • D
    2% (1)
  • E
    2% (1)

Why each option

To persistently increase the static `PROCESSES` parameter using `ALTER SYSTEM` when a PFILE exists, you must ensure an SPFILE is active, then use `ALTER SYSTEM SET` with `SCOPE=SPFILE`, and finally restart the database.

AEdit PFILE manually, re-create the SPFILE from the edited PFILE, and restart the database

This method does not use the `ALTER SYSTEM` command to set the parameter persistently, which is explicitly requested by the question.

BCreate an SPFILE, start the database instance by using the SPFILE, and then execute the ALTER

The `ALTER SYSTEM` command provided in this choice is incomplete, making it an invalid method.

CCreate an SPFILE, start the database instance by using the SPFILE, and then execute the ALTERCorrect

This method explicitly involves creating an SPFILE, starting the database instance with it, and then using `ALTER SYSTEM SET PROCESSES=400 SCOPE=SPFILE;` to persistently update the static parameter in the SPFILE before a final restart applies the change.

DCreate an SPFILE, STARTUP MOUNT the database instance by using the SPFILE, and then

The `ALTER SYSTEM` command provided in this choice is incomplete, making it an invalid method.

EStart the database instance by using the PFILE, and then execute the ALTER SYSTEM SET

The `ALTER SYSTEM` command provided in this choice is incomplete, making it an invalid method.

FUse the PFILE to STARTUP MOUNT the database instance, and then execute the ALTER SYSTEMCorrect

Although initially using a PFILE for `STARTUP MOUNT`, this method implies that an SPFILE is subsequently made active (e.g., by creating one and restarting with it), allowing `ALTER SYSTEM SET PROCESSES=400 SCOPE=SPFILE;` to successfully update the persistent configuration, which then requires another restart to take effect.

Concept tested: Oracle Parameter Management (PFILE, SPFILE, ALTER SYSTEM)

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/sqlrf/ALTER-SYSTEM.html#GUID-2BC3E9E2-4112-4217-AF21-BE01041112D9

Topics

#PFILE#SPFILE#ALTER SYSTEM#parameter persistence

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 1Z0-062 Practice