My Oracle Support Banner

Long Running Query Against SIEBEL.S_AUDIT_ITEM (Doc ID 781941.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Tools - Version 7.8.2.9 SIA [19238] to 7.8.2.16 SIA [19255] [Release V7]
Information in this document applies to any platform.
Checked for Relevance on 08-Jul-2014
””Checked for Relevance on 21-DEC-2015””

Symptoms

A long-running query occurs when Audit Trail Engine is enabled and these steps are performed:

This results in the following long running query:

SELECT
T2.CONFLICT_ID,
T2.LAST_UPD,
T2.CREATED,
T2.LAST_UPD_BY,
T2.CREATED_BY,
T2.MODIFICATION_NUM,
T2.ROW_ID,
T2.USER_ID,
T1.LOGIN
FROM
SIEBEL.S_USER T1,
SIEBEL.S_AUDIT_ITEM T2
WHERE
T2.USER_ID = T1.PAR_ROW_ID (+)
ORDER BY
T2.OPERATION_DT DESC

Note that there is no search specification in the WHERE clause, only a join. This causes the query to take a long time to execute, especially when the tables are large.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.