Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Meaning of "DDL or commits" and other SQL statements

Meaning of "DDL or commits" and other SQL statements


This article explains the meaning of "DDL or commits" and other SQL statements.


All versions of DPA.


DPA may show "DDL or commits" and other SQL Statements. This means that at the time DPA collected the information, the database instance did not have a SQL statement associated with the current session. The session is likely in one of the following situations:


1. The session was running a command that is not tracked by the database vendor as a traditional statement.

    Data Definition Statements (DDL) - e.g. create table statements
    Statistics maintenance


2. The session was between SQL statements. When a session is running multiple SQL statements, it may spend time between the statements cleaning up after the last statement or preparing to accept the next one.


Further Investigation
Drill into the "DDL or commits" to determine the program and waits associated with this classification. That information will often give a clue as to what is occurring.



There are two Oracle-specific bugs that cause any SQL statement executed from DBMS_JOB or DBMS_SCHEDULER to show as "DDL or commits:"

  • Bug 5928612 -  V$SESSION SQL_ADDRESS / SQL_HASH_VALUE not set for DBMS_JOBs
    • Fixed in and
  • Bug 5140631  - V$SESSION.sql_address not set by DBMS_SCHEDULER
    • Fixed in and
Last modified