Database Architecture   «Prev  Next»

Oracle Initialization File - Exercise

Inspect Initialization Parameters

Objective: Identify the initialization parameter source for an Oracle instance and explain three parameter settings.

Exercise Scoring

This exercise is worth 5 points:

  • Identify the parameter source and explain your findings: 2 points.
  • Record and explain three initialization parameters: 1 point each.

Compare your response with the sample solution after submitting. The website does not connect to your database or automatically verify your findings.

Instructions

An Oracle instance can start using a binary server parameter file (SPFILE) or a text initialization parameter file (PFILE). Do not open an SPFILE in a text editor to modify it.

  1. In an authorized lab environment, connect through SQL*Plus using an account permitted to inspect initialization parameters. For this instance-level exercise, use the CDB root (CDB$ROOT).

    Check your current container and the SPFILE setting:

    SHOW CON_NAME
    SHOW PARAMETER spfile

    If the SPFILE value contains a path, record that path. It may identify a filesystem file or an Oracle ASM file. If the value is blank, the instance is not currently using an SPFILE. Ask the DBA or inspect the startup configuration to identify the PFILE used; this command does not report its path.

  2. Inspect the following parameter values:

    SHOW PARAMETER db_name
    SHOW PARAMETER db_block_size
    SHOW PARAMETER processes
    SHOW PARAMETER open_cursors
    SHOW PARAMETER diagnostic_dest

    Choose three parameters. Record their displayed values and explain what each controls.

  3. If an authorized text PFILE is available, inspect it in a text editor. If the instance uses an SPFILE, an authorized DBA can create a text copy for inspection with:

    CREATE PFILE = '/approved/path/init_review.ora'
    FROM SPFILE;

    Replace the example path with a new filename in an existing, approved directory on the database server. The Oracle database process must be able to write there. This operation requires an appropriate administrative privilege.

    The export contains stored SPFILE settings, which may differ from current in-memory values. Creating the export does not change the active configuration. Do not replace startup files, change parameters, or restart the instance for this exercise.

What to Submit

  • Your current container and the SPFILE path, or an explanation that the SPFILE value was blank.
  • Whether you inspected a text PFILE, and its location if known.
  • Three parameter names, their values, and their purposes.

If you do not have access to an Oracle lab, submit a walkthrough using these illustrative values:

db_name=LABCDB
db_block_size=8192
processes=300
open_cursors=300
diagnostic_dest='/u01/app/oracle'

Explain the difference between an SPFILE and a PFILE and describe three of these parameters. State that you used the illustrative example. These values are not a complete startup configuration or sizing recommendation.