### WALLET_ROOT Directory Structure Example

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/WALLET_ROOT

Illustrates a typical directory layout under the WALLET_ROOT path, showing wallet files for different components and pluggable databases (PDBs) identified by GUIDs.

```Shell
wallet-root/eus/ewallet.p12
wallet-root/tde/ewallet.p12
wallet-root/tde/ewallet_2016120918333644.p12
wallet-root/tde_seps/cwallet.sso
wallet-root/tls/ewallet.p12
wallet-root/xdb_wallet/ewallet.p12
wallet-root/3FD1C95B48205D0FE053C5A0E40AEF8C/tde/ewallet.p12
wallet-root/3FD1C95B48205D0FE053C5A0E40AEF8C/tde/ewallet_2016110918331622.p12
wallet-root/3FD1C95B48205D0FE053C5A0E40AEF8C/tde/ewallet_2016110918332363.p12
wallet-root/3FD1C95B48205D0FE053C5A0E40AEF8C/tde_seps/cwallet.sso
wallet-root/3FD1C95B48205D0FE053C5A0E40AEF8C/tls/cwallet.sso
wallet-root/3FD1C95B48205D0FE053C5A0E40AEF8C/tls/ewallet.p12
```

--------------------------------

### PMEM_FILESTORE Configuration Examples

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/PMEM_FILESTORE

Examples demonstrating how to specify one or more PMEM Filestores for database instance startup. Each entry consists of a mount point and its corresponding backing file.

```config
PMEM_FILESTORE=('/var/db/db_1', '/var/db_storage/db1.f')
```

```config
PMEM_FILESTORE=('/var/db/db_1', '/var/db_storage/db1.f', '/var/db/db_2', '/var/db_storage/db2.f')
```

--------------------------------

### Example DB_FLASH_CACHE_FILE Configuration

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DB_FLASH_CACHE_FILE

An example showing how to configure the DB_FLASH_CACHE_FILE parameter with multiple raw device file names for flash memory.

```shell
db_flash_cache_file = /dev/raw/sda, /dev/raw/sdb, /dev/raw/sdc
```

--------------------------------

### Example: Forwarding Database Connections

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/FORWARD_LISTENER

Provides an example configuration to forward all database connections from an existing customer SCAN listener to an Oracle Cloud SCAN listener using the FORWARD_LISTENER, REMOTE_LISTENER, and LOCAL_LISTENER parameters.

```shell
REMOTE_LISTENER=customer-scan
FORWARD_LISTENER=oracle-cloud-scan
LOCAL_LISTENER=oracle-none-
```

--------------------------------

### WALLET_ROOT Auto-Directory Creation Example (Non-ASM)

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/WALLET_ROOT

Shows how setting WALLET_ROOT to a specific directory path enables Oracle Database to automatically create necessary subdirectories for TDE wallets, including PDB GUIDs.

```Shell
WALLET_ROOT=wallet-root-directory-path
# Example:
# /etc/ORACLE/KEYSTORES/FINANCE
```

--------------------------------

### Oracle DISPATCHERS Configuration Example

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DISPATCHERS

An example of how to configure the DISPATCHERS parameter in Oracle Database, specifying the protocol and the initial number of dispatchers.

```Oracle Configuration
DISPATCHERS = '(PROTOCOL=TCP)(DISPATCHERS=3)'
```

--------------------------------

### CREATE ROLE Authentication Examples

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DBA_ROLES

Demonstrates the SQL syntax for creating roles with different authentication types in Oracle Database.

```SQL
CREATE ROLE role1;
-- Authentication Type: NONE

CREATE ROLE role2 IDENTIFIED EXTERNALLY;
-- Authentication Type: EXTERNAL

CREATE ROLE role3 IDENTIFIED GLOBALLY;
-- Authentication Type: GLOBAL

CREATE ROLE role4 IDENTIFIED USING schema.package;
-- Authentication Type: APPLICATION

CREATE ROLE role5 IDENTIFIED BY role5;
-- Authentication Type: PASSWORD
```

--------------------------------

### Query V$QMON_TASKS

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-QMON_TASKS

Example SQL query to retrieve all information from the V$QMON_TASKS view.

```sql
SELECT *
FROM V$QMON_TASKS;
```

--------------------------------

### Query V$SERVICES View

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-SERVICES

Example SQL query to retrieve all information from the V$SERVICES dynamic performance view.

```SQL
SELECT 
    SERVICE_ID,
    NAME,
    NETWORK_NAME,
    CREATION_DATE,
    GOAL,
    DTP,
    AQ_HA_NOTIFICATION,
    CLB_GOAL,
    COMMIT_OUTCOME,
    RETENTION_TIME,
    REPLAY_INITIATION_TIMEOUT,
    SESSION_STATE_CONSISTENCY,
    "GLOBAL",
    PDB,
    SQL_TRANSLATION_PROFILE,
    MAX_LAG_TIME,
    STOP_OPTION,
    FAILOVER_RESTORE,
    DRAIN_TIMEOUT
FROM 
    V$SERVICES;
```

--------------------------------

### WALLET_ROOT Configuration Example with Environment Variable

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/WALLET_ROOT

Demonstrates setting the WALLET_ROOT parameter to use an environment variable, ensuring unique wallet directories for each database instance sharing an ORACLE_HOME.

```Shell
WALLET_ROOT=/etc/ORACLE/KEYSTORES/$ORACLE_SID
```

--------------------------------

### SHARED_SERVERS Oracle Parameter

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/basic-initialization-parameters

Specifies the number of server processes that you want to create when an instance is started. This parameter is used for shared server configurations.

```APIDOC
SHARED_SERVERS
  Description: Specifies the number of server processes to create when an instance starts.
  Purpose: Configures the number of shared server processes.
  Example Usage: ALTER SYSTEM SET SHARED_SERVERS=10 SCOPE=SPFILE;
```

--------------------------------

### List Database Features and Descriptions

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DBA_FEATURE_USAGE_STATISTICS

An example SQL query to retrieve the names and descriptions of database features, ordered alphabetically by feature name.

```SQL
SELECT name, description FROM dba_feature_usage_statistics
ORDER BY name;
```

--------------------------------

### SQL CREATE VIEW Example with JSON Function

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_JSON_COLUMNS

Demonstrates creating a table and a view where a column is defined using a SQL function that returns JSON data, making it visible in ALL_JSON_COLUMNS.

```SQL
CREATE TABLE t1 (text varchar2(100));
CREATE VIEW v1 AS SELECT JSON_OBJECT(text) AS mycol FROM t1;
```

--------------------------------

### Display All Oracle Parameters

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/changing-parameter-values-in-a-parameter-file

Shows all current initialization parameters and their values in alphabetical order. This command is useful for getting an overview of the database configuration.

```SQL
SQL> SHOW PARAMETERS
```

--------------------------------

### recovery active instance mapping setup Wait Event

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/descriptions-of-wait-events

Tracks the time taken (in centiseconds) to set up recovery context on remote instances.

```APIDOC
recovery active instance mapping setup:
  Description: This event is used to track the time taken (in centiseconds) to set up recovery context on remote instances.
```

--------------------------------

### Sample Initialization Parameter File Entries

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/parameter-files

Provides sample entries for an Oracle Initialization Parameter File, which is a text file containing initialization parameters and their values. These parameters are read by client-side tools like SQL*Plus during database instance startup.

```text
PROCESSES = 100
OPEN_LINKS = 12
GLOBAL_NAMES = true

```

--------------------------------

### Example Diagnostic Operations

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DIAGNOSTICS_CONTROL

Examples of SQL statements that perform potentially unsafe diagnostic operations, such as setting trace events.

```SQL
ALTER SESSION SET EVENTS '1357 trace name context forever, level 2';
ALTER SYSTEM SET EVENTS 'trace[vos]';
```

--------------------------------

### Set NLS_NUMERIC_CHARACTERS Example

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/NLS_NUMERIC_CHARACTERS

An example demonstrating how to set the NLS_NUMERIC_CHARACTERS parameter to use a comma as the decimal character and a space as the group separator.

```sql
NLS_NUMERIC_CHARACTERS = ", "

```

--------------------------------

### V$SYSTEM_PARAMETER View Reference

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-PARAMETER

Provides details on Oracle's V$SYSTEM_PARAMETER view, which lists current instance initialization parameters and how new sessions inherit them.

```APIDOC
V$SYSTEM_PARAMETER:
  Description: Displays information about the initialization parameters that are currently in effect for the instance. A new session inherits parameter values from the instance-wide values.
  Usage: SELECT * FROM V$SYSTEM_PARAMETER;
```

--------------------------------

### Oracle LOG_ARCHIVE_DEST_n NULL Value Example

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/LOG_ARCHIVE_DEST_n

Example of setting the LOG_ARCHIVE_DEST_n parameter to a null string to disable archiving for a specific destination.

```SQL
LOG_ARCHIVE_DEST_n=' ';
```

--------------------------------

### ALL_SYNC_CAPTURE_PREPARED_TABS View Documentation

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_SYNC_CAPTURE_PREPARED_TABS

Documentation for the ALL_SYNC_CAPTURE_PREPARED_TABS view, detailing columns, datatypes, and descriptions for tables prepared for synchronous capture instantiation.

```APIDOC
ALL_SYNC_CAPTURE_PREPARED_TABS:
  Description: Displays information about the tables accessible to the current user that are prepared for synchronous capture instantiation.
  Related View: DBA_SYNC_CAPTURE_PREPARED_TABS
  Columns:
    TABLE_OWNER:
      Datatype: VARCHAR2(128)
      Nullable: NO
      Description: Owner of the table prepared for synchronous capture instantiation
    TABLE_NAME:
      Datatype: VARCHAR2(128)
      Nullable: NO
      Description: Name of the table prepared for synchronous capture instantiation
    SCN:
      Datatype: NUMBER
      Nullable: NO
      Description: SCN from which changes can be captured
    TIMESTAMP:
      Datatype: DATE
      Nullable: YES
      Description: Time at which the table was ready to be instantiated
```

--------------------------------

### Database Creation and Startup Commands

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DB_NAME

Illustrates SQL commands related to database creation and mounting, where DB_NAME is a critical parameter.

```SQL
CREATE DATABASE ...;

STARTUP;

ALTER DATABASE ... MOUNT;
```

--------------------------------

### SQL IS JSON Constraint Examples

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_JSON_COLUMNS

Illustrates SQL syntax for check constraints that ensure columns contain valid JSON data. These examples show conditions that cause a column to be included in the ALL_JSON_COLUMNS view.

```SQL
mycol IS JSON
mycol IS JSON AND LENGTH(mycol) > 100
```

```SQL
-- This constraint will NOT cause mycol to appear in ALL_JSON_COLUMNS:
-- mycol IS JSON OR LENGTH(mycol) > 100
```

--------------------------------

### Create Sample Tables and Users (utlsampl.sql)

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/creating-additional-data-dictionary-structures

The utlsampl.sql script is used to create sample tables, such as EMP and DEPT, and sample users, like SCOTT. This script is commonly used for demonstration and testing purposes.

```SQL
-- utlsampl.sql
-- Description: Creates sample tables (e.g., EMP, DEPT) and users (e.g., SCOTT).
-- Usage: Execute as SYS or any user with DBA role.
-- Provides a basic dataset for learning and testing SQL queries.
```

--------------------------------

### Install Java Packages with catjava.sql

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/java-scripts

The `catjava.sql` script installs various Java-related packages and classes into the Oracle Database. This script is crucial for enabling advanced Java features and ensuring proper functionality of Java components.

```sql
catjava.sql
```

--------------------------------

### Specify Multiple Parameters on One Line

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/parameter-files

Shows how to enter several parameters on a single line in an initialization parameter file, separated by spaces.

```oracle-init-params
PROCESSES = 100 CPU_COUNT = 1 OPEN_CURSORS = 10
```

--------------------------------

### Oracle Database View: ALL_JSON_DATAGUIDE_FIELDS

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_JSON_DATAGUIDE_FIELDS

Extracts path and type information from data guides accessible to the current user. This view provides details about JSON fields within data guides managed by the ALL_JSON_DATAGUIDE view.

```APIDOC
View Name: ALL_JSON_DATAGUIDE_FIELDS

Description: Extracts the path and type information from the data guides accessible to the current user. These are the data guides returned to the user by the ALL_JSON_DATAGUIDE view.

Related Views:
- DBA_JSON_DATAGUIDE_FIELDS: Extracts information from all data guides in the database.
- USER_JSON_DATAGUIDE_FIELDS: Extracts information from data guides in the current user’s schema, excluding the OWNER column.

Columns:
- OWNER: VARCHAR2(128) - Owner of the table containing the JSON column.
- TABLE_NAME: VARCHAR2(128) - Name of the table containing the JSON column.
- COLUMN_NAME: VARCHAR2(128) - Name of the JSON column that has data guide enabled.
- PATH: VARCHAR2(4000) - Path to the JSON field in the data guide.
- TYPE: VARCHAR2(40) - Type of the JSON field in the data guide.
- LENGTH: NUMBER - Maximum length of the JSON field value, in bytes.

See Also:
- DBA_JSON_DATAGUIDE_FIELDS
- USER_JSON_DATAGUIDE_FIELDS
```

--------------------------------

### Set MFA_OMA_IAM_DOMAIN_URL

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/MFA_OMA_IAM_DOMAIN_URL

Example of how to set the MFA_OMA_IAM_DOMAIN_URL parameter using the ALTER SYSTEM command in SQL.

```SQL
ALTER SYSTEM SET MFA_OMA_IAM_DOMAIN_URL =
   "https://idcs-cbcb9aaca84945e78466ab5b2e576360.identity.oraclecloud.com";
```

--------------------------------

### Querying System Privileges

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DBA_SYS_PRIVS

Example SQL query to retrieve system privileges granted to users and roles from the DBA_SYS_PRIVs view.

```SQL
SELECT 
    GRANTEE,
    PRIVILEGE,
    ADMIN_OPTION,
    COMMON,
    INHERITED
FROM 
    DBA_SYS_PRIVs
WHERE 
    GRANTEE = 'SOME_USER_OR_ROLE';
```

--------------------------------

### Oracle V$INSTANCE View

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-INSTANCE

The V$INSTANCE view provides information about the current Oracle instance. It includes details such as instance number, name, host name, version, startup time, status, and various operational states.

```APIDOC
V$INSTANCE:
  Displays the state of the current instance.

  Columns:
  - INSTANCE_NUMBER (NUMBER): Instance number used for instance registration (corresponds to the INSTANCE_NUMBER initialization parameter).
  - INSTANCE_NAME (VARCHAR2(16)): Name of the instance.
  - HOST_NAME (VARCHAR2(64)): Name of the host machine.
  - VERSION (VARCHAR2(17)): Database version.
  - VERSION_LEGACY (VARCHAR2(17)): The legacy database version used before Oracle Database 18c. This column displays the same value as the VERSION column.
  - VERSION_FULL (VARCHAR2(17)): The version string with the new Oracle Database version scheme introduced in Oracle Database 18c.
  - STARTUP_TIME (DATE): Time when the instance was started.
  - STATUS (VARCHAR2(12)): Status of the instance: STARTED, MOUNTED, OPEN, OPEN MIGRATE.
  - PARALLEL (VARCHAR2(3)): Indicates whether the instance is mounted in cluster database mode (YES) or not (NO).
  - THREAD# (NUMBER): Redo thread opened by the instance.
  - ARCHIVER (VARCHAR2(7)): Automatic archiving status: STOPPED, STARTED, FAILED.
  - LOG_SWITCH_WAIT (VARCHAR2(15)): Event that log switching is waiting for: ARCHIVE LOG, CLEAR LOG, CHECKPOINT, NULL.
  - LOGINS (VARCHAR2(10)): Indicates whether the instance is in unrestricted mode (ALLOWED) or restricted mode (RESTRICTED).
  - SHUTDOWN_PENDING (VARCHAR2(3)): Indicates whether a shutdown is pending (YES) or not (NO).
  - DATABASE_STATUS (VARCHAR2(17)): Status of the database: ACTIVE, SUSPENDED, INSTANCE RECOVERY.
  - INSTANCE_ROLE (VARCHAR2(18)): Indicates whether the instance is a PRIMARY_INSTANCE or a SECONDARY_INSTANCE, or UNKNOWN.
  - ACTIVE_STATE (VARCHAR2(9)): Quiesce state of the instance: NORMAL, QUIESCING, QUIESCED.
  - BLOCKED (VARCHAR2(3)): Indicates whether all services are blocked (YES) or not (NO).
  - CON_ID (NUMBER): The ID of the container to which the data pertains (0 for CDB, 1 for root, n for other containers).
  - INSTANCE_MODE (VARCHAR2(11)): The instance mode of the current instance: REGULAR, READ MOSTLY, READ ONLY.
  - EDITION (VARCHAR2(7)): The edition of the database: PO, FREE, SE2, EE, HP, XP.
  - FAMILY (VARCHAR2(80)): For internal use only.
```

--------------------------------

### PARALLEL_MIN_SERVERS Parameter

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/changing-parameter-values-in-a-parameter-file

The number of parallel execution processes Oracle creates when the instance is started.

```APIDOC
PARALLEL_MIN_SERVERS:
  Description: The number of parallel execution processes Oracle creates when the instance is started.
  Type: Integer
  Usage: SET PARAMETER PARALLEL_MIN_SERVERS = <minimum_servers>;
```

--------------------------------

### AWR_SNAPSHOT_TIME_OFFSET

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/changing-parameter-values-in-a-parameter-file

Specifies an offset for the Automatic Workload Repository (AWR) snapshot start time.

```APIDOC
AWR_SNAPSHOT_TIME_OFFSET
  Description: Specifies an offset for the Automatic Workload Repository (AWR) snapshot start time.
  Parameters:
    (No specific parameters detailed in source text)
  Returns:
    (No return value detailed in source text)
  Usage:
    (No usage example detailed in source text)
```

--------------------------------

### ASM_IO_PROCESSES

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/changing-parameter-values-in-a-parameter-file

Specifies the number of I/O worker processes to be started in an Oracle IOServer instance.

```APIDOC
ASM_IO_PROCESSES
  Description: Specifies the number of I/O worker processes to be started in an Oracle IOServer instance.
  Parameters:
    (No specific parameters detailed in source text)
  Returns:
    (No return value detailed in source text)
  Usage:
    (No usage example detailed in source text)
```

--------------------------------

### Oracle Initialization Parameters and Views

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/background-processes

Details on specific Oracle initialization parameters and data dictionary views mentioned in the context of background processes.

```APIDOC
Initialization Parameters:

JOB_QUEUE_PROCESSES:
  - Description: Specifies the maximum number of processes that can be created for the execution of jobs.
  - Usage: Controls the concurrency of scheduled jobs within the database.

PGA_AGGREGATE_LIMIT:
  - Description: Specifies a limit on the aggregate Program Global Area (PGA) memory consumed by the instance.
  - Usage: Helps manage memory usage by limiting the total PGA allocated. The CKPT process checks this limit.

Views:

V$XSTREAM_CAPTURE:
  - Description: Provides information about the Replication Capture Process (CPnn).
  - Usage: Query this view to monitor the status and details of XStream capture processes.

V$GOLDENGATE_CAPTURE:
  - Description: Provides information about Oracle GoldenGate capture processes, which are related to replication capture.
  - Usage: Query this view for details on GoldenGate capture activities.
```

--------------------------------

### V$PARAMETER View Schema and Columns

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-PARAMETER

Details the columns available in the V$PARAMETER view, which provides information about Oracle initialization parameters. Includes column names, data types, and descriptions of their meaning and possible values.

```APIDOC
V$PARAMETER:
  Description: Displays information about the initialization parameters that are currently in effect for the session.
  Columns:
    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(4000)): Parameter value for the session (if modified within the session); otherwise, the instance-wide parameter value.
    DISPLAY_VALUE (VARCHAR2(4000)): Parameter value in a user-friendly format (e.g., '256K').
    DEFAULT_VALUE (VARCHAR2(255)): The default value for this parameter.
    ISDEFAULT (VARCHAR2(9)): Indicates whether the parameter is set to the default value ('TRUE') or specified in the parameter file ('FALSE').
    ISSES_MODIFIABLE (VARCHAR2(5)): Indicates whether the parameter can be changed with ALTER SESSION ('TRUE' or 'FALSE').
    ISSYS_MODIFIABLE (VARCHAR2(9)): Indicates how the parameter can be changed with ALTER SYSTEM. 'IMMEDIATE' (takes effect immediately), 'DEFERRED' (takes effect in subsequent sessions), 'FALSE' (cannot be changed with ALTER SYSTEM unless SPFILE was used, takes effect in subsequent instances).
    ISPDB_MODIFIABLE (VARCHAR2(5)): Indicates whether the parameter can be modified inside a PDB ('TRUE' or 'FALSE').
    ISINSTANCE_MODIFIABLE (VARCHAR2(5)): For parameters changeable with ALTER SYSTEM, indicates if the value can differ per instance ('TRUE') or must be the same for all RAC instances ('FALSE'). Always 'FALSE' if ISSYS_MODIFIABLE is 'FALSE'.
    ISMODIFIED (VARCHAR2(10)): Indicates if the parameter has been modified after instance startup. 'MODIFIED' (ALTER SESSION), 'SYSTEM_MOD' (ALTER SYSTEM), 'FALSE' (not modified).
    ISADJUSTED (VARCHAR2(5)): Indicates whether Oracle adjusted the input value to a more suitable value ('TRUE' or 'FALSE').
    ISDEPRECATED (VARCHAR2(5)): Indicates whether the parameter has been deprecated ('TRUE' or 'FALSE').
    ISBASIC (VARCHAR2(5)): Indicates whether the parameter is a basic parameter ('TRUE' or 'FALSE').
    DESCRIPTION (VARCHAR2(255)): Description of the parameter.
    UPDATE_COMMENT (VARCHAR2(255)): Comments associated with the most recent update.
    HASH (NUMBER): Hash value for the parameter name.
    CON_ID (NUMBER): The ID of the container to which the data pertains. 0 for CDB, 1 for root, n for applicable container.
```

--------------------------------

### ALL_SOURCE Database View Documentation

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_SOURCE

Documentation for the ALL_SOURCE database view, detailing its columns, datatypes, nullability, and descriptions. It also references related views like DBA_SOURCE and USER_SOURCE.

```APIDOC
ALL_SOURCE Database View:
  Description: Describes the text source of stored objects accessible to the current user.
  Columns:
    OWNER:
      Datatype: VARCHAR2(128)
      NULL: NOT NULL
      Description: Owner of the object
    NAME:
      Datatype: VARCHAR2(128)
      NULL: NOT NULL
      Description: Name of the object
    TYPE:
      Datatype: VARCHAR2(12)
      NULL: 
      Description: Type of object: ASSEMBLEY, FUNCTION, LIBRARY, MLE, MODULE, PACKAGE, PACKAGE BODY, PROCEDURE, TRIGGER, TYPE, TYPE BODY
    LINE:
      Datatype: NUMBER
      NULL: NOT NULL
      Description: Line number of this line of source
    TEXT:
      Datatype: VARCHAR2(4000)
      NULL: 
      Description: Text source of the stored object
    ORIGIN_CON_ID:
      Datatype: VARCHAR2(256)
      NULL: 
      Description: The ID of the container where the data originates. Possible values include: 0 (for non-CDBs), n (for CDBs where n is the container ID).
  Related Views:
    DBA_SOURCE: Describes the text source of all stored objects in the database.
    USER_SOURCE: Describes the text source of stored objects owned by the current user.
```

--------------------------------

### Set INMEMORY_ADG_ENABLED for all RAC instances

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/INMEMORY_ADG_ENABLED

Example SQL command to set the INMEMORY_ADG_ENABLED parameter to true for all instances in an Oracle RAC environment.

```sql
SQL> alter system set inmemory_adg_enabled=true sid='*';
```

--------------------------------

### HS_ALL_INITS View - Oracle Database Initialization Parameters

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/HS_ALL_INITS

The HS_ALL_INITS view provides information about initialization parameters for non-Oracle (FDS) data stores. It details parameter names, values, types, and associated FDS class and instance names.

```APIDOC
HS_ALL_INITS:
  Description: Contains initialization parameter information about non-Oracle (FDS) data stores.
  Columns:
    INIT_VALUE_NAME (VARCHAR2(64)): Name of the initialization parameter.
    INIT_VALUE (VARCHAR2(255)): Value of the initialization parameter.
    INIT_VALUE_TYPE (VARCHAR2(1)): Environment variable indicator ('T' means this is an environment variable; 'F' means do not set as an environment variable).
    FDS_CLASS_NAME (VARCHAR2(30)): Name of the FDS Class.
    FDS_INST_NAME (VARCHAR2(30)): Name of the FDS instance.
```

--------------------------------

### Modifying DB_FILE_MULTIBLOCK_READ_COUNT

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DB_FILE_MULTIBLOCK_READ_COUNT

Examples of how to modify the DB_FILE_MULTIBLOCK_READ_COUNT parameter using SQL commands for the current session or the entire system.

```SQL
-- Modify for the current session
ALTER SESSION SET DB_FILE_MULTIBLOCK_READ_COUNT = 16;

-- Modify for the entire system (requires appropriate privileges)
ALTER SYSTEM SET DB_FILE_MULTIBLOCK_READ_COUNT = 32 SCOPE=BOTH;
```

--------------------------------

### Binary Operators for Initialization Parameter

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/parameter-files

Sets an initialization parameter using binary operators for multiplication (*), division (/), modulo (%), addition (+), and subtraction (-). Operator precedence applies (*/% before +-), and results are truncated to integers.

```APIDOC
SHARED_SERVERS = MAX_SHARED_SERVERS / 2
DATA_GUARD_MAX_LONGIO_TIME = DATA_GUARD_MAX_IO_TIME + 10 * 3
```

--------------------------------

### OS_ROLES Parameter Configuration

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/OS_ROLES

Configures the management of user roles between the operating system and Oracle Database. This parameter is not modifiable after initial setup.

```APIDOC
OS_ROLES
  Description: Determines whether Oracle or the operating system identifies and manages the roles of each username.
  Properties:
    Parameter type: Boolean
    Default value: false
    Modifiable: No
    Modifiable in a PDB: No
    Range of values: true | false
    Basic: No
  Values:
    TRUE: The operating system completely manages the role grants for all database usernames. When a user attempts to create a session, the username's security domain is initialized using the roles identified by the operating system. Revocation by Oracle of roles granted by the operating system is ignored, as are any roles previously granted by Oracle.
    FALSE: Oracle identifies and manages the roles.
```

--------------------------------

### DBA_ADVISOR_SQLW_TEMPLATES View Documentation

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DBA_ADVISOR_SQLW_TEMPLATES

Provides details on the DBA_ADVISOR_SQLW_TEMPLATES view, which aggregates SQLWkld template objects. It includes column definitions, datatypes, nullability, and descriptions, along with information on a related view.

```APIDOC
DBA_ADVISOR_SQLW_TEMPLATES

Description:
  Displays an aggregated picture of all SQLWkld template objects in the database.

Related View:
  USER_ADVISOR_SQLW_TEMPLATES: Displays an aggregated picture of the SQLWkld template objects owned by the current user. This view does not display the OWNER column.

Columns:
  OWNER:
    Datatype: VARCHAR2(128)
    NULL: Yes
    Description: Owner of the workload object
  WORKLOAD_ID:
    Datatype: NUMBER
    NULL: No
    Description: Unique identifier number of the workload object
  WORKLOAD_NAME:
    Datatype: VARCHAR2(128)
    NULL: Yes
    Description: Unique name of the workload
  DESCRIPTION:
    Datatype: VARCHAR2(256)
    NULL: Yes
    Description: User-specified description of the workload
  CREATE_DATE:
    Datatype: DATE
    NULL: No
    Description: Date on which the workload object was created
  MODIFY_DATE:
    Datatype: DATE
    NULL: No
    Description: Date of last update to the current workload
  SOURCE:
    Datatype: VARCHAR2(128)
    NULL: Yes
    Description: Optional object or template on which the object was based
  READ_ONLY:
    Datatype: VARCHAR2(5)
    NULL: Yes
    Description: Indicates whether the workload template can be modified or deleted (TRUE) or not (FALSE)

See Also:
  USER_ADVISOR_SQLW_TEMPLATES
```

--------------------------------

### Oracle Log Timestamp Format Example

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/UNIFORM_LOG_TIMESTAMP_FORMAT

Demonstrates the standardized timestamp format used in Oracle Database trace files when UNIFORM_LOG_TIMESTAMP_FORMAT is set to TRUE.

```text
2012-09-26 00:16:47.154
```

--------------------------------

### Setting Initialization Parameters with Expressions via SQL

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/parameter-files

Demonstrates how to set initialization parameters using expressions within SQL statements like ALTER SESSION SET and ALTER SYSTEM SET. Expressions must be enclosed in single quotation marks.

```APIDOC
ALTER SESSION SET AQ_TM_PROCESSES = 'MIN(40, PROCESSES * .1)';
ALTER SYSTEM SET JOB_QUEUE_PROCESSES = 'PROCESSES' SCOPE=BOTH;
```

--------------------------------

### ALL_JSON_DATAGUIDES View Schema

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_JSON_DATAGUIDES

Details the structure and purpose of the ALL_JSON_DATAGUIDES view, which lists JSON columns with data guides accessible to the current user. It also references related views for broader database access.

```APIDOC
ALL_JSON_DATAGUIDES:
  Description: Provides information on the JavaScript Object Notation (JSON) columns accessible to the current user that have data guide enabled.

  Related Views:
    - DBA_JSON_DATAGUIDES: Provides information on all JavaScript Object Notation (JSON) columns in the database that have data guide enabled.
    - USER_JSON_DATAGUIDES: Provides information on the JavaScript Object Notation (JSON) columns owned by the current user that have data guide enabled. This view does not display the OWNER column.

  Columns:
    OWNER:
      Datatype: VARCHAR2(128)
      NULL: NOT NULL
      Description: Owner of the table containing the JSON column
    TABLE_NAME:
      Datatype: VARCHAR2(128)
      NULL: NOT NULL
      Description: Name of the table containing the JSON column
    COLUMN_NAME:
      Datatype: VARCHAR2(128)
      NULL: NOT NULL
      Description: Name of the JSON column that has data guide enabled
    DATAGUIDE:
      Datatype: CLOB
      NULL: 
      Description: The data guide of the JSON column in flat format
```

--------------------------------

### Setting PLSQL_CCFLAGS

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/PLSQL_CCFLAGS

Examples of how to set the PLSQL_CCFLAGS parameter using SQL ALTER SESSION statements. This allows dynamic control over conditional compilation flags.

```SQL
ALTER SESSION SET PLSQL_CCFLAGS = 'DeBug:TruE';
```

```SQL
ALTER SESSION SET PLSQL_CCFLAGS = 'debug:TRUE';
```

--------------------------------

### Oracle DISPATCHERS Parameter Configuration

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DISPATCHERS

Detailed documentation for the Oracle Database DISPATCHERS initialization parameter, covering its syntax, sub-clauses, options, and behavior.

```APIDOC
DISPATCHERS
  Configures dispatcher processes in the shared server architecture.

Syntax:
  DISPATCHERS = 'dispatch_clause'

  dispatch_clause::=
    (PROTOCOL = protocol)
  | (ADDRESS = address)
  | (DESCRIPTION = description)
  [options_clause]

  options_clause::=
    (DISPATCHERS = integer) | (SESSIONS = integer) | (CONNECTIONS = integer) |
    (MULTIPLEX = {1 | ON | YES | TRUE | BOTH | IN | OUT | 0 | OFF | NO | FALSE})
    | (LISTENER = tnsname) | (SERVICE = service) | (INDEX = integer)

Parameters:
  PROTOCOL: The network protocol for which the dispatcher generates a listening endpoint.
  ADDRESS: The network protocol address of the endpoint on which the dispatchers listen.
  DESCRIPTION: The network description of the endpoint on which the dispatchers listen, including the protocol address.

Options:
  DISPATCHERS: The initial number of dispatchers to start. Default is 1.
  SESSIONS: The maximum number of network sessions to allow for each dispatcher. Default is OS-specific (often 16 KB).
  CONNECTIONS: The maximum number of network connections to allow for each dispatcher. Default is OS-specific.
  MULTIPLEX: Enables Oracle Connection Manager session multiplexing.
    - 1, ON, YES, TRUE, BOTH: Enabled for incoming and outgoing connections.
    - IN: Enabled for incoming connections.
    - OUT: Enabled for outgoing connections.
    - 0, NO, OFF, FALSE: Disabled for both incoming and outgoing connections (default).
  LISTENER: Specifies the network name of an address or address list of Oracle Net listeners with which dispatchers will register. Takes precedence over LOCAL_LISTENER and REMOTE_LISTENER.
  SERVICE: Specifies one or more names by which clients can connect to the dispatchers. Takes precedence over SRVCTL, GDSCTL, or DBMS_SERVICE settings.
  INDEX: Used in ALTER SYSTEM SET DISPATCHERS to indicate which dispatcher configuration to modify. Specifies the order of initialization (0-based).

Default Value:
  If SHARED_SERVERS > 0, defaults to '(PROTOCOL=tcp)', creating 1 TCP/IP dispatcher.

Modifiable:
  ALTER SYSTEM

Modifiable in a PDB:
  No

Notes:
  - Attributes can be specified using full names or substrings starting with the first 3 characters (e.g., SESSIONS can be SES, SESS, SESSI).
  - Specify only one of PROTOCOL, ADDRESS, or DESCRIPTION.
  - Specifying ADDRESS or DESCRIPTION allows additional network attributes for multi-homed hosts.
  - INDEX is ignored if specified in the initialization parameter file; it's for ALTER SYSTEM statements.
```

--------------------------------

### Set MFA_SMTP_PORT using ALTER SYSTEM

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/MFA_SMTP_PORT

Example of setting the MFA_SMTP_PORT parameter using the ALTER SYSTEM command in Oracle Database.

```sql
ALTER SYSTEM SET MFA_SMTP_PORT = 587;
```

--------------------------------

### WALLET_ROOT Parameter Syntax

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/WALLET_ROOT

Defines the basic syntax for setting the WALLET_ROOT initialization parameter, specifying the directory path for wallet storage.

```Oracle SQL
WALLET_ROOT = wallet-root-directory-path
```

--------------------------------

### SQL Query Example: Select All Credentials

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_CREDENTIALS

A basic SQL query to retrieve all columns for all credentials visible to the current user from the ALL_CREDENTIALS view.

```SQL
SELECT 
    OWNER, 
    CREDENTIAL_NAME, 
    USERNAME, 
    WINDOWS_DOMAIN, 
    COMMENTS, 
    ENABLED
FROM 
    ALL_CREDENTIALS;
```

--------------------------------

### V$HS_PARAMETER View Description

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-HS_PARAMETER

Provides details on the columns of the V$HS_PARAMETER view, which outlines initialization parameters for the server and agent. It includes column names, data types, and descriptions, along with mapping information to related views.

```APIDOC
V$HS_PARAMETER:
  Description: Describes the initialization parameters in use by the server and agent.
  Columns:
    - HS_SESSION_ID (NUMBER): Unique HS session identifier (maps to the HS_SESSION_ID column of V$HS_SESSION)
    - PARAMETER (VARCHAR2(128)): Name of the parameter
    - VALUE (VARCHAR2(64)): Value of the parameter
    - SOURCE (VARCHAR2(1)): Indicates whether the parameter was defined in the agent (A) or server (S)
    - ENV (VARCHAR2(1)): Indicates whether the parameter was set as an environment variable in the agent (T) or elsewhere (F)
    - CON_ID (NUMBER): The ID of the container to which the data pertains. Possible values include:
      - 0: Used for rows containing data that pertain to the entire CDB or for rows in non-CDBs.
      - 1: Used for rows containing data that pertain to only the root.
      - n: Where n is the applicable container ID for the rows containing data.
```

--------------------------------

### V$SCHEDULER_IN_MEMORY_TRACE View

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-SCHEDULER_IN_MEMORY_TRACE

Displays in-memory trace and other information about all processes executing scheduler-related actions. This view is available starting with Oracle Database 23ai.

```APIDOC
V$SCHEDULER_IN_MEMORY_TRACE:
  Description: Displays in-memory trace and other information about all processes executing scheduler-related actions.
  Availability: Oracle Database 23ai and later.
  Columns:
    SID:
      Datatype: NUMBER
      Description: ID of the session generating scheduler trace
    SERIAL#:
      Datatype: NUMBER
      Description: Serial number of the session generating scheduler trace
    USER#:
      Datatype: NUMBER
      Description: Oracle identifier of the user generating scheduler trace
    USERNAME:
      Datatype: VARCHAR2(128)
      Description: Name of the user generating scheduler trace
    PROCESSNAME:
      Datatype: VARCHAR2(5)
      Description: Name of the process generating scheduler trace
    PADDR:
      Datatype: RAW(8)
      Description: Address of the process state object generating scheduler trace
    SPID:
      Datatype: VARCHAR2(24)
      Description: Operating system identifier of the process generating scheduler trace
    PID:
      Datatype: NUMBER
      Description: Oracle identifier of the process generating scheduler trace
    TRACE_ST:
      Datatype: CLOB
      Description: Scheduler trace generated by the process
    CON_ID:
      Datatype: NUMBER
      Description: The ID of the container to which the data pertains. Possible values include: 0 (entire CDB or non-CDB), 1 (root), or n (applicable container ID).
```

--------------------------------

### VInn: Volume I/O Process

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/background-processes

VInn processes route ADVM volume I/O for ASM instances on compute nodes within an Exadata environment. They handle I/Os targeted at storage not locally accessible and are used for Exadata-specific storage. These processes start only when an ASM Volume is created and configured, with one process per NUMA node on target machines. They are not started on non-Exadata hardware or Exadata hardware not utilizing ASM volumes. Up to 32 VI processes exist, named VI00 to VI31.

```APIDOC
VInn | Volume I/O
  Route ADVM volume I/O for ASM instances on compute nodes within an Exadata.
  Functionality:
    - Handle requests for I/Os targeted at storage not locally accessible.
    - Used for Exadata targeted storage.
  Activation:
    - Start only when an ASM Volume is created and set up for use.
    - One process starts for each NUMA node on target machines.
    - Not started on non-Exadata hardware or Exadata hardware not utilizing ASM volumes.
  Naming Convention:
    - Up to 32 VI processes, named sequentially from VI00 to VI31.
  Context: Oracle ASM Proxy instances
```

--------------------------------

### Oracle TDE Wallet Directory Paths

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/WALLET_ROOT

Illustrates the expected directory structures for TDE wallets when `WALLET_ROOT` is configured with Oracle ASM and Oracle Managed Files (OMF). Includes examples for single-instance databases and isolated PDBs.

```Oracle Configuration
WALLET_ROOT=+DATA/FINRAC

+DATA/FINRAC/tde

+DATA/FINRAC/3FD1C95B48205D0FE053C5A0E40AEF8C/tde
```

--------------------------------

### SQL JSON Function Examples

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/ALL_JSON_COLUMNS

Lists SQL functions that return JSON data, which can cause their output columns in views to be recognized as JSON columns.

```SQL
TREAT( expr AS JSON )
JSON_ARRAY(...)
JSON_ARRAYAGG(...)
JSON_MERGEPATCH(...)
JSON_OBJECT(...)
JSON_OBJECTAGG(...)
JSON_QUERY(...)
JSON_SERIALIZE(...)
JSON_TRANSFORM(...)
```

--------------------------------

### Configure OKV Keystore for Mounted PDB

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/TDE_CONFIGURATION

Configures the Oracle Database system to use OKV as the keystore for a PDB in MOUNTED state. This setting is applied to the server's parameter file.

```sql
ALTER SYSTEM SET TDE_CONFIGURATION="KEYSTORE_CONFIGURATION=OKV" SCOPE=SPFILE SID='*';
```

--------------------------------

### SHARED_SERVERS

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/changing-parameter-values-in-a-parameter-file

Specifies the number of server processes that you want to create when an instance is started. This parameter configures the number of dedicated server processes.

```APIDOC
SHARED_SERVERS
  SHARED_SERVERS specifies the number of server processes that you want to create when an instance is started.
```

--------------------------------

### Oracle Data Guard Broker Configuration View (V$DG_BROKER_CONFIG)

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-DG_BROKER_CONFIG

Provides a summary of an Oracle Data Guard broker configuration, similar to the DGMGRL CLI's SHOW CONFIGURATION command. It offers a view of the entire Data Guard broker configuration from any database within the setup.

```APIDOC
V$DG_BROKER_CONFIG:
  Description: Provides a summary of an Oracle Data Guard broker configuration.
  Purpose: Offers a view of the entire Oracle Data Guard broker configuration from any database in the configuration, analogous to the DGMGRL CLI's SHOW CONFIGURATION command.
  Columns:
    DATABASE: VARCHAR2(30) - Database unique name.
    CONNECT_IDENTIFIER: VARCHAR2(512) - Net connect identifier used to reach the database.
    DATAGUARD_ROLE: VARCHAR2(20) - Oracle Data Guard role of the database (e.g., PRIMARY, PHYSICAL STANDBY, FAR SYNC, LOGICAL STANDBY, SNAPSHOT STANDBY, etc.).
    REDO_SOURCE: VARCHAR(30) - The database unique name of the redo source.
    ENABLED: VARCHAR2(5) - Indicates whether the database is managed by Oracle Data Guard broker ('TRUE') or not ('FALSE').
    STATUS: NUMBER - An Oracle error number denoting the database's current status.
    SEVERITY: VARCHAR2(30) - Severity of the Oracle error. Possible values include: FAILURE, SUCCESS, WARNING.
    STATUS_MESSAGE: VARCHAR2(256) - Error message associated with the Oracle error number in the STATUS column.
    VERSION: VARCHAR2(30) - Version of the broker configuration.
    TRANSPORT_MODE: VARCHAR2(30) - Transport mode of the standby databases. Available starting with Oracle Database 23ai.
    CON_ID: NUMBER - The ID of the container to which the data pertains. 0 for CDB root/non-CDB, 1 for CDB root, n for applicable container ID.
```

--------------------------------

### UNDO_TABLESPACE Oracle Parameter

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/basic-initialization-parameters

Specifies the undo tablespace to be used when an instance starts. This parameter defines the default tablespace for undo data.

```APIDOC
UNDO_TABLESPACE
  Description: Specifies the undo tablespace to be used when an instance starts.
  Purpose: Defines the default tablespace for undo data.
  Example Usage: ALTER SYSTEM SET UNDO_TABLESPACE=UNDOTBS1 SCOPE=SPFILE;
```

--------------------------------

### Oracle TDE Keystore Creation Command

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/WALLET_ROOT

Documents the `ADMINISTER KEY MANAGEMENT CREATE KEYSTORE` command, which is used to create TDE wallets. The command automatically creates necessary directories based on the `WALLET_ROOT` setting, ensuring proper separation of wallets for different databases or PDBs.

```APIDOC
ADMINISTER KEY MANAGEMENT CREATE KEYSTORE
  -- Creates a TDE keystore.
  -- When WALLET_ROOT is configured with ASM/OMF, this command automatically creates the necessary directory structure.
  -- Example:
  -- For WALLET_ROOT=+DATA/FINRAC, running this command creates +DATA/FINRAC/tde.
  -- For isolated PDBs, the PDB GUID is included in the path.
  -- Related Parameters:
  --   WALLET_ROOT: Specifies the root directory for TDE wallets.
  --   DB_UNIQUE_NAME: Used in conjunction with WALLET_ROOT for directory naming.
  --   See Also: TDE_CONFIGURATION
```

--------------------------------

### Query Default Value for ALLOW_GLOBAL_DBLINKS

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/V-PARAMETER

Example SQL query to retrieve the default value of the ALLOW_GLOBAL_DBLINKS initialization parameter from the V$PARAMETER view.

```SQL
SELECT name, default_value FROM v$parameter
WHERE name = 'allow_global_dblinks';
```

--------------------------------

### DBA_CAPTURE_PREPARED_TABLES: Oracle Database View

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/DBA_CAPTURE_PREPARED_TABLES

This entry describes the DBA_CAPTURE_PREPARED_TABLES data dictionary view. It provides details on tables prepared for instantiation within the Oracle database. The view's structure and content are identical to the ALL_CAPTURE_PREPARED_TABLES view.

```APIDOC
DBA_CAPTURE_PREPARED_TABLES:
  Description: Displays information about all tables prepared for instantiation at the local database.
  Columns: Identical to ALL_CAPTURE_PREPARED_TABLES.
  Related Views:
    - ALL_CAPTURE_PREPARED_TABLES: Provides the same information for tables accessible to the current user.
```

--------------------------------

### Set AUDIT_TRAIL to db (SQL)

Source: https://docs.oracle.com/en/database/oracle/oracle-database/23/refrn/AUDIT_TRAIL

Example SQL statement to set the `AUDIT_TRAIL` parameter to `db` using `ALTER SYSTEM`. The new value takes effect after the database is restarted.

```SQL
SQL> alter system set AUDIT_TRAIL=db scope=spfile;

System altered.

SQL>
```