OracleSqlDataBaseTablesTruncate

Truncates the configured Oracle tables in the order they are listed.

What It Does

Truncates the configured Oracle tables in the order they are listed.

It serves the same purpose as the other SQL truncate probes, but uses the Oracle provider and connection details.

YAML Example

Sessions:
  - Name: ProbeSession
    Probes:
      - Name: OracleSqlDataBaseTablesTruncateProbe
        Probe: OracleSqlDataBaseTablesTruncate
        ProbeConfiguration:
          UseGlobalDict: true
          ConnectionString: User Id=qaas;Password=qaas-password;Data Source=oracle.local:1521/XEPDB1;
          CommandTimeoutSeconds: 30
          TableNames:
            - QAAS_OUTBOX
            - QAAS_ORDERS

What This Configuration Does

This configuration connects to Oracle and truncates QAAS_OUTBOX followed by QAAS_ORDERS.

It is a database reset step that clears the table contents while keeping the table definitions in place.

Global Dictionary Behavior

With UseGlobalDict: true, missing ConnectionString and other shared SQL settings can be resolved from the session-scoped Sql/Defaults alias when those keys do not appear in the local probe configuration. The probe still binds and validates after the merge, and any key that is present locally keeps priority over the shared default.

That makes the probe useful when Oracle cleanup probes should reuse the same SQL connection definition while each probe keeps its own table list.

No recovery alias is written for SQL truncation in this first pass.

When UseGlobalDict is false, the probe behaves exactly as before and uses only local YAML or code configuration.