Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps

Friday, November 2, 2007

Identify dynamic and static init.ora parameters

To identify whether an init.ora parameter is static (changing it requires restarting database) or dynamic (can be changed without restarting database), let us take a look at the structure of the v$parameter2 view which is like v$parameter, but includes extra rows for long parameters. ORDINAL allows you to get the correct ordering of multiple VALUE columns for the same parameter.:

This view lists parameters and parameter values that are currently in effect for the session. Each list parameter value appears as a row in the view.

Presenting the list parameter values in this format enables you to quickly determine the values for a list parameter. For example, if a parameter value is "a,b" looking at V$PARAMETER does not tell you if the parameter has two values ("a" and "b") or one value ("a, b"). V$PARAMETER2 makes the distinction between the list parameter values clear.

Column Datatype Description
NUM NUMBER Parameter number
NAME VARCHAR2(80) Name of the parameter
TYPE NUMBER Parameter type:
  • 1 - Boolean

  • 2 - String

  • 3 - Integer

  • 4 - Parameter file

  • 5 - Reserved

  • 6 - Big integer

VALUE VARCHAR2(512) Parameter value for the session (if modified within the session); otherwise, the instance-wide parameter value
DISPLAY_VALUE VARCHAR2(512) Parameter value in a user-friendly format. For example, if the VALUE column shows the value 262144 for a big integer parameter, then the DISPLAY_VALUE column will show the value 256K.
ISDEFAULT VARCHAR2(6) Indicates whether the parameter is set to the default value (TRUE) or the parameter value was specified in the parameter file (FALSE)
ISSES_MODIFIABLE VARCHAR2(5) Indicates whether the parameter can be changed with ALTER SESSION (TRUE) or not (FALSE)
ISSYS_MODIFIABLE VARCHAR2(9) Indicates whether the parameter can be changed with ALTER SYSTEM and when the change takes effect:
  • IMMEDIATE - Parameter can be changed with ALTER SYSTEM regardless of the type of parameter file used to start the instance. The change takes effect immediately.

  • DEFERRED - Parameter can be changed with ALTER SYSTEM regardless of the type of parameter file used to start the instance. The change takes effect in subsequent sessions.

  • FALSE - Parameter cannot be changed with ALTER SYSTEM unless a server parameter file was used to start the instance. The change takes effect in subsequent instances.

ISINSTANCE_MODIFIABLE VARCHAR2(5) For parameters that can be changed with ALTER SYSTEM, indicates whether the value of the parameter can be different for every instance (TRUE) or whether the parameter must have the same value for all Real Application Clusters instances (FALSE). If the ISSYS_MODIFIABLE column is FALSE, then this column is always FALSE.
ISMODIFIED VARCHAR2(10) Indicates whether the parameter has been modified after instance startup:
  • MODIFIED - Parameter has been modified with ALTER SESSION

  • SYSTEM_MOD - Parameter has been modified with ALTER SYSTEM (which causes all the currently logged in sessions' values to be modified)

  • FALSE - Parameter has not been modified after instance startup

ISADJUSTED VARCHAR2(5) Indicates whether Oracle adjusted the input value to a more suitable value (for example, the parameter value should be prime, but the user input a non-prime number, so Oracle adjusted the value to the next prime number)
ISDEPRECATED VARCHAR2(5) Indicates whether the parameter has been deprecated (TRUE) or not (FALSE)
DESCRIPTION VARCHAR2(255) Description of the parameter
ORDINAL NUMBER Position (ordinal number) of the parameter value. Useful only for parameters whose values are lists of strings.
UPDATE_COMMENT VARCHAR2(255) Comments associated with the most recent update

If ISSES_MODIFIABLE parameter is true, the parameter can be changed on session level, and if issys_modifiable or isinstance_modifiable is true, the parameter can be changed on system level.

No comments: