Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

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

Meaning of "DDL or commits" and other SQL statements

Overview

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

Environment

All versions of DPA.

Details

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.

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

 

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.

 

Oracle SQL run from DBMS_JOB or DBMS_SCHEDULER

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 10.2.0.4 and 11.1.0.7
  • Bug 5140631  - V$SESSION.sql_address not set by DBMS_SCHEDULER
    • Fixed in 10.2.0.4 and 11.1.0.6
Last modified
14:21, 9 Dec 2015

Tags

Classifications

Public