DBMS_CLOUD_AI_AGENT History Views

The DBMS_CLOUD_AI history views are categorized into team history view, task history view, and tool history views.

See Also:

Select AI Agent

Team History Views

These views show all agent team-runs across the system. Each row records one agent team run, including team name, job names, start or end timestamps, run state, and any errors. It serves as the top-level run log, linking to task- and tool-level history for deeper analysis.

Task History Views

These views show agent task parameters within a team. These views holds the contextual data needed to run an agent task. The task reads input parameters from it when it starts and writes results back when it finishes. It connects the scheduling system with the agent framework.

Tool History Views

These views show calls to tools across the system. Each row logs the tool name, triggering agent and task, team execution ID, step name, timestamps, and input and output data. Use it to audit tool usage, monitor integrations, and debug tool behavior.

DBA_AI_AGENT_TEAM_HISTORY View

The view displays all agent team-runs across the system.

Only the Database Administrator is privileged to access this view. They can grant access to other users. The DBA* views show objects of all Database users.

Column Datatype NULL Description
TEAM_EXEC_ID VARCHAR2(128) NOT NULL

Stores the unique identifier for the team run instance, typically a GUID.

TEAM_NAME VARCHAR2(128) NOT NULL

Specifies the name of the agent being run.

TEAM_OWNER VARCHAR2(128) NOT NULL

Specifies the owner schema of the team.

START_DATE TIMESTAMP - The timestamp the process started.
END_DATE TIMESTAMP NOT NULL

The timestamp the process ended. If the process is still running, the value is NULL.

STATE VARCHAR2(30) NOT NULL
Indicates the current run state. Possible values are:
  • RUNNING: The agent team is actively processing the request.
  • WAITING_FOR_HUMAN: The agent team paused and is waiting for user input or approval.
  • RESUMING: The agent team continues after a pause or human input.
  • SUCCEEDED: The agent team finished the run and produced a final response.
  • FAILED: The agent team stopped due to an error or unmet condition.
TEAM_INSTANCE_ID NUMBER -

Specifies the session instance ID where the agent team was run.

USER_AI_AGENT_TEAM_HISTORY View

The view displays all agent team runs for teams owned by the current user.

The current user can see the team history they own. You cannot grant access to other users. The Database Administrator can access these views but sees only the objects they own.

Column Datatype NULL Description
TEAM_EXEC_ID VARCHAR2(128) NOT NULL Stores the unique identifier for the team execution instance, typically a GUID.
TEAM_NAME VARCHAR2(128) NOT NULL Specifies the name of the agent being run.
START_DATE TIMESTAMP - The timestamp the process started.
END_DATE TIMESTAMP NOT NULL

The timestamp the process ended. If the process is still running, the value is NULL.

STATE VARCHAR2(30) NOT NULL
Indicates the current run state. Possible values are:
  • RUNNING: The agent team is actively processing the request.
  • WAITING_FOR_HUMAN: The agent team paused and is waiting for user input or approval.
  • RESUMING: The agent team continues after a pause or human input.
  • SUCCEEDED: The agent team finished the run and produced a final response.
  • FAILED: The agent team stopped due to an error or unmet condition.
TEAM_INSTANCE_ID NUMBER -

Specifies the session instance ID where the agent team was run.

DBA_AI_AGENT_TASK_HISTORY View

This view shows agent task parameters within a team.

Only the Database Administrator is privileged to access this view. They can grant access to other users. The DBA* views show objects of all Database users.

Column Datatype NULL Description
TEAM_EXEC_ID VARCHAR2(128) NOT NULL

Stores the unique identifier for the team run instance, typically a GUID.

TEAM_NAME VARCHAR2(128) NOT NULL

Specifies the name of the agent team being run.

TASK_OWNER VARCHAR2(128)  

Specifies the owner schema of the team.

AGENT_NAME VARCHAR2(128) NOT NULL

Specifies the name of the agent being run.

TASK_NAME VARCHAR2(128)  

Indicates the name of the task being run.

TASK_ORDER NUMBER  

Identifies the current task’s position in the agent team sequence. Because a task can appear multiple times, task_order distinguishes this specific occurrence.

COVERSATION_PARAM CLOB  

Provides JSON parameters for the conversation API, including: conversation_id, title, and title.

INPUT CLOB  

Specifies the input data for the task.

RESULT CLOB  

Stores the output produced by the task. (For example, text, JSON, rows, or a status message).

STATE VARCHAR2(30) NOT NULL
Indicates the current run state. Possible values are:
  • RUNNING: The agent team is actively processing the request.
  • WAITING_FOR_HUMAN: The agent team paused and is waiting for user input or approval.
  • RESUMING: The agent team continues after a pause or human input.
  • SUCCEEDED: The agent team finished the run and produced a final response.
  • FAILED: The agent team stopped due to an error or unmet condition.
START_DATE TIMESTAMP -

The timestamp the process started.

END_DATE TIMESTAMP NOT NULL

The timestamp the process ended. If the process is still running, the value is NULL.

USER_AI_AGENT_TASK_HISTORY View

This view shows agent task parameters for the current user’s teams.

The current user can see the task history they own. You cannot grant access to other users. The Database Administrator can access these views but sees only the objects they own.

Column Datatype NULL Description
TEAM_EXEC_ID VARCHAR2(128) NOT NULL

Stores the unique identifier for the team run instance, typically a GUID.

TEAM_NAME VARCHAR2(128) NOT NULL

Specifies the name of the agent team being run.

AGENT_NAME VARCHAR2(128) NOT NULL

Specifies the name of the agent being run.

TASK_NAME VARCHAR2(128)  

Indicates the name of the task being run.

TASK_ORDER NUMBER  

Identifies the current task’s position in the agent team sequence. Because a task can appear multiple times, task_order distinguishes this specific occurrence.

COVERSATION_PARAM CLOB  

Provides JSON parameters for the conversation API, including: conversation_id, title, and title.

INPUT CLOB  

Specifies the input data for the task.

RESULT CLOB  

Stores the output produced by the task. (For example, text, JSON, rows, or a status message).

STATE VARCHAR2(30) NOT NULL
Indicates the current run state. Possible values are:
  • RUNNING: The agent team is actively processing the request.
  • WAITING_FOR_HUMAN: The agent team paused and is waiting for user input or approval.
  • RESUMING: The agent team continues after a pause or human input.
  • SUCCEEDED: The agent team finished the run and produced a final response.
  • FAILED: The agent team stopped due to an error or unmet condition.
START_DATE TIMESTAMP - The timestamp the process started.
END_DATE TIMESTAMP NOT NULL

The timestamp the process ended. If the process is still running, the value is NULL.

DBA_AI_AGENT_TOOL_HISTORY View

This view lists calls to tools across the system.

Only the Database Administrator is privileged to access this view. They can grant access to other users. The DBA* views show objects of all Database users.

Column Datatype NULL Description
invocation_id VARCHAR2(128) NOT NULL

Stores the unique identifier for the call.

TEAM_EXEC_ID VARCHAR2(128) NOT NULL

Stores the unique identifier for the team run instance, typically a GUID.

TASK_ORDER NUMBER -

Identifies the current task’s position in the agent team sequence. Because a task can appear multiple times, task_order distinguishes this specific occurrence.

TOOL_OWNER VARCHAR2(128) -

Owner schema of the tool.

TOOL_NAME VARCHAR2(128) -

Indicates the tool name that is called.

AGENT_NAME VARCHAR2(128) -

Indicates the agent name that is used for calling the tool.

TASK_NAME VARCHAR2(128) -

Name of the task that ran the tool.

START_DATE TIMESTAMP - The timestamp when the tool started running.
END_DATE TIMESTAMP NOT NULL

The timestamp the when the tool stopped. If the process is still running, the value is NULL.

INPUT CLOB -

Specifies the input data for the tool.

OUTPUT CLOB -

Stores the output produced by the tool. (For example, text, JSON, rows, or a status message).

TOOL_OUTPUT CLOB -

Diagnostic messages from the tool function, used for debugging or troubleshooting and tracing behavior.

USER_AI_AGENT_TOOL_HISTORY View

This view lists calls to tools the current user owns.

The current user can see the tool history they own. You cannot grant access to other users. The Database Administrator can access these views but sees only the objects they own.

Column Datatype NULL Description
invocation_id VARCHAR2(128) NOT NULL

Stores the unique identifier for the call.

TEAM_EXEC_ID VARCHAR2(128) NOT NULL

Stores the unique identifier for the team run instance, typically a GUID.

TASK_ORDER NUMBER -

Identifies the current task’s position in the agent team sequence. Because a task can appear multiple times, task_order distinguishes this specific occurrence.

TOOL_NAME VARCHAR2(128) -

Indicates the tool name that is called.

AGENT_NAME VARCHAR2(128) -

Indicates the agent name that is used for calling the tool.

TASK_NAME VARCHAR2(128) -

Name of the task that ran the tool.

START_DATE TIMESTAMP - The timestamp when the tool started running.
END_DATE TIMESTAMP NOT NULL

The timestamp the when the tool stopped. If the process is still running, the value is NULL.

INPUT CLOB -

Specifies the input data for the tool.

OUTPUT CLOB -

Stores the output produced by the tool. (For example, text, JSON, rows, or a status message).

TOOL_OUTPUT CLOB -

Diagnostic messages from the tool function, used for debugging or troubleshooting and tracing behavior.