2.412 THREADED_EXECUTION

THREADED_EXECUTION specifies whether to enable the multithreaded Oracle Database model.

Property Description

Parameter type

Boolean

Default value

On UNIX and Linux: false

On Windows: true

Modifiable

No

Modifiable in a PDB

No

Range of values

true | false

Basic

No

Oracle RAC

If specified, all instances must use the same value

THREADED_EXECUTION on UNIX and Linux

Oracle Database 12c introduced the THREADED_EXECUTION initialization parameter for RDBMS instances running on UNIX and Linux systems. On such instances, the default value for THREADED_EXECUTION is false. Setting this parameter to true enables the multithreaded Oracle Database model, which allows Oracle processes on UNIX and Linux to run as operating system threads in separate address spaces.

By default, some background processes on UNIX and Linux always use threaded execution; the remaining Oracle processes run as operating system processes. Thus, an "Oracle process" is not always equivalent to an "operating system process."

Note:

When THREADED_EXECUTION = true on an RDBMS instance running on a UNIX or Linux system, operating system authentication is not supported. In this case, if a client process attempts to connect to the RDBMS instance using operating system authentication (for example, CONNECT / AS SYSDBA or CONNECT / ), the following error will occur: ORA-01017: invalid credential or not authorized; logon denied. Instead, client processes can use local database password authentication or an external authentication method, such as TCPS, to connect to the RDBMS instance.

If you are using traditional auditing, operating system authentication is possible using the IPC key info recorded in audit files. This applies only to bequeath (local) connections; clients on remote hosts cannot use operating system authentication.

Also, when THREADED_EXECUTION = true on an RDBMS instance running on a UNIX or Linux system, the DEDICATED_THROUGH_BROKER_listener-name=ON parameter should be added to the listener.ora file, where listener-name is the name of the Oracle Net listener and the LOCAL_LISTENER initialization parameter should be set to a TNS name entry corresponding to your instance service. This enables the server to spawn threads when connections to the instance are requested through the listener.

THREADED_EXECUTION on Windows

Starting with Oracle Database 21c, the THREADED_EXECUTION initialization parameter is supported for RDBMS instances running on Microsoft Windows. On such instances, this parameter must remain set to its default value of true; setting this parameter to false on RDBMS instances running on Windows is not supported. The introduction of this parameter does not change the threading model for Oracle Database on Windows. As in previous releases, an RDBMS instance on Windows is a service with a single multi-threaded operating system process. However, starting with Oracle Database 21c, you will observe changes to the V$PROCESS view, the dedicated connection broker, and the naming of trace files. For details about these changes, refer to Oracle AI Database Administrator’s Reference for Microsoft Windows.

Note:

Unlike on UNIX and Linux systems, when THREADED_EXECUTION = true on Windows, operating system authentication is supported.

See Also: