SQL profiler equivalent in oracle

Hi,
I am currently using Oracle 10G. I need to keep track of all queries that are executed with the execution time.
Is there any profiler which can show the queries that have executed with the take taken.
Regards
Deepak

U can view the active processes from the V$PROCESS provided u have privileges on this view.

Similar Messages

Oracle 10g SQL Profiler Equivalent?

As per the subject, I can monitor sessions via the web gui, but I need to see actual SQL statements that are hitting the 10g server. Is there an Oracle 10g SQL Profiler equivalent?

XE?
You might want to hunker down with some of the docco available at http://www.oracle.com/pls/db102/portal.portal_db?selected=1
In particular, you could look at the 'Reference' manual (not SQL Reference, or any other ... Reference) and browse through the DBA_ and V$ views listed. The Concepts and Administration manuals are interesting as well.
The specific views of interest include, but are not limited to, V$SQLAREA and V$SQLTEXT

SQL XMLExplicit equivalent in oracle

Hi
Is there any equivalent in oracle for SQL XMLExplicit?
In SQL the XMLExplicit will add all the retunded nodes under the single root node like that any equivalent is available in oracle.
Thanks
Surendra

I hope you will get better answers if you post this in Sql/Plsql Forum ..
PL/SQL
This one is one of the genuine and active forums .. :)

What is Oracle Equivalent of SQL Profiler

Hi All,
Iam new to oracle world. I have a problem, I have a website which was build by someone and it uses Oracle 9i/10g as its back end and I dont have the code for that website. I have to develop an interface which simulates some of the button clicks in the web site. For achieving this i have to know what are all the tables thatare effected by the button click. If it is MS SQL world we used to put SQL Profiler and get all the SQL queries executed for that particular event. In Oracle how can we achieve this. PLease help iam in a dire necessity for this PLEASE
--Phani
Edited by: user3654627 on Apr 29, 2009 9:57 AM

I don't get it:
If someone clearly states to be a newbie, but willing and eager to learn, if you realize that this is a community, that means: we all learn when we need to be teached and teach others when others need to learn, we SHARE KNOWLEDGE:
Why do you suggest OP to change jobs, when he's only asked his second question on this forum???
This forum is not about doing your work for free, and it is not for the lazy who can't be bothered to do their own work. If you are not > up to the task, consider changing jobs.Come on...you can't be serious here, either that, or you've got some human malfunction in your brain. ( bad marriage? )
You're like:
Create table sybrand (my_answer_is_always varchar2(16) default 'READ ORACLE DOCS' NOT NULL)
So, whatever we insert, it doesn't matter, same resultset in return, regardless of who fires the query on table sybrand...fine, have it your way.
Regardless of teaching a rookie or an expert.
If you don't wanna teach/learn, and just be a repeating frame, I suggest you buzz off to the Reports Forum.

SQL Profiler's equivalent in Oracle.

Hi All,
We are using Oracle 10g as backend for our application. We would like to see which database objects (stored procedures, functions, triggers etc) are getting called at the Oracle database server when various users connect to the application and they perfrom various transactions from the UI.
There is a similar tool available in SQL server. That is SQL Profiler.
Is there any similar tool which is present for Oracle database server for tracking the database objects invoked?
Please suggest any option available in Oracle or any third party tools pluggable into Oracle database.
Thanks,

U can view the active processes from the V$PROCESS provided u have privileges on this view.

Oracle 10g RAC SQL profiles not working for both the nodes

We have identified a long running sql.
Used Advisor to tune the sql
Applied the suggested sql_profile as per the recommendation.
when we re-run the sql from application, due to RAC setup the sql hit the other node, used the sql profile as indicated by v$sql but was long running.
it generated a new sql_id due to which we think it was not working.
Could you please advice how to apply sql_profile for both nodes?

HI Arun
Would you please post that in the GRID RAC section of this forum please ?
Please consult the following documents to get support on your question:
http://download.oracle.com/docs/cd/B19306_01/rac.102/b14197/votocr.htm#sthref211
http://download.oracle.com/docs/cd/B19306_01/install.102/b14205/undrstnd.htm#RISOL2610
Thanks

HANA equivalent of oracle's sql%rowcount to get affected rows.

I want to get the number of rows affected from an insert or update statement inside a stored procedure.
Is there any equivalent to oracle's sql%rowcount that can be called after the query.
For example:
create procedure procedure_name
begin
     declare l_c integer;
     insert into table values ('somevalue');
     l_c := sql%rowcount; -- This would return 1 for the row inserted.
end;

Yes, after the INSERT statement....
SELECT ::ROWCOUNT into L_C FROM DUMMY;
Cheers,
Rich Heilman

Can sql profiles be moved from Oracle SE/SEO to XE

Hi all.
I use both: 10g XE, 11g XE as well as SE and SEO.
I'd like to know if i can export / import or move sql profiles from SE / SEO to Oracle XE.
Thanks in advance!!!

Profiles? Need a bit more info on what you're after.
For sqlplus the $ORACLE_HOME/admin/glogin.sql file gets executed every time one starts sqlplus or does a connect. Or its %ORACLE_HOME% on windows hosts.
For export and import (also see the 11gR2 Utilities doc Overview of Oracle Data Pump ) but generally the tables, the data, stored procedures, functions, etc. will be compatible, the main caveat will be source and target RDBMS versions, features added (or absent) from one or the other. The first two digits, possibly all four digits of the release version number are relevant.
And the XE space limit has to apply, as well as the absence of some features not included in the engine see the XE license page Oracle® Database Express Edition it has details on what is/is not present.

Does SQL Server has an equivalent to Oracle's OEM?

I am not sure if this is the correct area to ask my question. My manager asked me if SQL Server has an equivalent to Oracle's OEM. Does it? I mean OEM is not like Microsoft SQL Server Management Studio.
lcerni

Hello,
You can use SQL Server Management Studio to manage SQL Server instances as you do with Oracle Enterprise Manager, and you can have a management and performance
data warehouse using SQL Server Management Data Warehouse (MDW) as explained on the following article:
http://msdn.microsoft.com/en-us/library/dd939169(v=SQL.100).aspx
MDW data collection can be customized.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Use of SQL Profiles where each schema has very different data distribution and volumes

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
PL/SQL Release 11.2.0.3.0 - Production
CORE 11.2.0.3.0 Production
TNS for Linux: Version 11.2.0.3.0 - Production
NLSRTL Version 11.2.0.3.0 - Production
Our architecture has multiple client schemas in the same database. Each schema has the same code base (tables, procedures etc) but each client's data is very different in terms of volumes and skew/distribution per table. This architecture was done based on cost - I know it's not ideal but it can't change.....
I am fairly seasoned with performance management and so know the usual tricks of when to eat up the table using parallel full table scans etc. I couldn't further optimise a given stmt for our largest table. I'll call it TSPCI and it has monthly partitions (2 years) and totals about 35Gb in the largest client schema.
Anyway, I was surprised when ADDM suggested that I could achieve 98% improvement if I were to use a given SQL Profile. Great?
So, here's my issue - I've found that the same SQL_ID is shared across all those different client schemas: I can't see how to get it to pick/use the SQL Profile in only a particular client schema - let's call it NEX - and not in another (lets call it COL).
If I generate a SQL Profile as NEX, has it analysed and built the SQL Profile based on the NEX schema and is it therefore invalid/undesirable to have that SQL Profile used in the COL schema??
I suppose that I could add a small change (say /*+ NEX */) to the SQL in the NEX schema to make the given sql unique there and then generate a SQL Profile for that..........
What am I missing here?

Well, I can confirm the behaviour: accept a SQL Profile for a given SQL in one schema and verified that it is used in another schema (where the data volume and distribution is very different).
I can also confirm the workaround - simply add a hint to the SQL to make it unique such that I could use different sql profiles for the otherwise exact same sql in different schemas.
I'm happy enough with this workaround but I'll leave this thread unanswered in case someone can suggest a better approach.

DMBS_SQL.to_refcursor equivalent in Oracle 10g

Hello,
Is there any other way to get result as a refcursor in Oracle 10g with DBMS_SQL? I have the function that function generate dynamic query and execute with DBMS_SQL. This function called by java code for viewing result as report. How can I do this, is there equivalent in Oracle 10g for DMBS_SQL.to_refcursor? Please help.
Thanks,

ilkinesrefli wrote:
Is it difficult to understand my answers?Yes, because they are not accurate. You keep saying you can't use ref cursors and must use DBMS_SQL, but you have failed to show us why that is so.
It is impossible because there is dynamic where clause in my query. Show us why it's impossible.
BluShadow     please solve this one:
p_sql := 'select empno, ename, deptno from emp where deptno=:pdeptno';
if ... then
p_sql := p_sql || ' AND empno=:pempno';
end if;
...Is it possible by your way?Yes, ref cursors can be used for dynamic queries. basic example...
SQL> ed
Wrote file afiedt.buf
1 create or replace function get_refcursor(p_sql in varchar2
2                                          ,p_whereclause in varchar2 := null
3                                          ,p_whereval in number := null) return sys_refcursor is
4    v_rc sys_refcursor;
5 begin
6    if p_whereval is not null then
7      open v_rc for p_sql||' where '||p_whereclause using p_whereval;
8    else
9      open v_rc for p_sql;
10    end if;
11    return v_rc;
12* end;
SQL> /
Function created.
SQL> var rc refcursor;
SQL> exec :rc := get_refcursor('select empno, ename, deptno from emp');
PL/SQL procedure successfully completed.
SQL> print rc;
     EMPNO ENAME          DEPTNO
      7369 SMITH              20
      7499 ALLEN              30
      7521 WARD               30
      7566 JONES              20
      7654 MARTIN             30
      7698 BLAKE              30
      7782 CLARK              10
      7788 SCOTT              20
      7839 KING               10
      7844 TURNER             30
      7876 ADAMS              20
      7900 JAMES              30
      7902 FORD               20
      7934 MILLER             10
14 rows selected.
SQL> exec :rc := get_refcursor('select empno, ename, deptno from emp', 'deptno = :1', 20);
PL/SQL procedure successfully completed.
SQL> print rc;
     EMPNO ENAME          DEPTNO
      7369 SMITH              20
      7566 JONES              20
      7788 SCOTT              20
      7876 ADAMS              20
      7902 FORD               20
SQL>So, please explain to us again why ref cursors are impossible to use and you have to use DBMS_SQL?

Sql profiles in 11.1.0.7

We just upgraded from 10.1.0.3 to 11.1.0.7 and some very complex queries are running slower. When I check the plans in a non-production 11g database, the join orders are slightly different. I also have traces from my 10g production database and that I loaded into a sql tuning set in production. I am running the sql tuning advisor. When I get a recommendation to use the old plan, I implement it in the 10.2.0.5 Oracle Enterprise manager grid control.
How do I tell the sql_id of the sql profile? Is it part of the name? So if I look in dba_sql_profiles and see
SYS_SQLPROF_012a8f339c4b0001
Is the last part the sql_id? When I search on that value, I do not see it in v$sql. It does not appear that my queries are using the sql profile. So there might a slight difference from these queries (space maybe) than the ones I have. How do I confirm that my queries are using a sql profile as well?

Dear user11990507,
I do think that the value "012a8f339c4b0001" is nothing to do with the SQL_ID in the v$sql fixed view. It can be generated based on an algorithm like generating SQL_IDs. That is an internal information and i really don't know much about it.
You can also accept, alter or drop an SQL profile with the below commands;
DECLARE my_sqlprofile_name VARCHAR2(30);
BEGIN my_sqlprofile_name := DBMS_SQLTUNE.ACCEPT_SQL_PROFILE (task_name => 'my_sql_tuning_task', name => 'my_sql_profile', force_match => TRUE);
END;
BEGIN
DBMS_SQLTUNE.ALTER_SQL_PROFILE(name => 'my_sql_profile', attribute_name => 'STATUS', value => 'DISABLED');
END;
BEGIN
DBMS_SQLTUNE.DROP_SQL_PROFILE(name => 'my_sql_profile');
END;
DBA_SQL_PROFILES;
http://download.oracle.com/docs/cd/B28359_01/server.111/b28320/statviews_4256.htm#REFRN23477
Check the SQL_TEXT column for you particular SQLs.
Hope That Helps.
Ogan

MS SQL Server/VB6 to Oracle 8i using OBDC

OMW,
I presently connect to MS SQL in Visual Basic 6.0 using ODBC. I
would like to connect to Oracle in the same manner. Does the OMW
do this, and if so are there any things I should know before
attempting to use it in this application? I have purchased and
installed a trial version of Oracle 8i, but I am experiencing
some slight difficulties in the way Oracle handles Resultsets
(RDO Components) compared to MS SQL.
thanks
g
null

Gary,
There is some information in the faq (reproduced below), showing
how the application may not need to be changed.
Some of the functionality provided by the intersolve driver is
now available in the oracle 8.1.5.3 odbc driver.
Turloch
Oracle Migration Workbench team
from the faq (shipped with the workbench):
How are result sets/dynasets returned to the calling program?
The Oracle Migration Workbench parser adds an extra argument
of type REF CURSOR for result sets/dynasets. This type is
understood and can be
manipulated by both PL/SQL and Oracle JDBC. Oracle8 release
8.0.5 ODBC drivers support REF CURSORs which means that the
additional argument must
be explicitly handled by the application, and the client
application code must be changed. However, some third-party
vendors such as Intersolv supply ODBC
drivers for Oracle that support REF CURSORs and can, in
addition, implicitly make use of REF CURSORs for using result
sets/dynasets. Therefore, no
change is required in the client application code. This is
illustrated in the following examples of an MS SQL Server stored
procedure and its equivalent Oracle
package and stored procedure as generated by the Oracle
Migration Workbench parser.
MS SQL Server Stored Procedure
CREATE PROCEDURE byroyalty
AS
select au_id from titleauthor
GO
Oracle8i Package and Stored Procedure
PACKAGE BYROYALTYPkg AS
TYPE RT1 IS RECORD (
au_id titleauthor.au_id%TYPE
TYPE RCT1 IS REF CURSOR RETURN RT1;
END;
PROCEDURE byroyalty(
RC1 IN OUT byroyaltyPkg.RCT1)
AS
StoO_selcnt INTEGER;
StoO_error INTEGER;
StoO_rowcnt INTEGER;
StoO_errmsg VARCHAR2(255);
StoO_sqlstatus INTEGER;
BEGIN
OPEN RC1 FOR
SELECT au_id FROM titleauthor;
END byroyalty;
The following example illustrates the typical ODBC code used
by Intersolv to call the above MS SQL Server stored procedure.
This code also works for the
above Oracle8i package and stored procedure. Note that error
handling must be added in a real application:
SQLPrepare(...,'{call byroyalty()}',...)
SQLExecute()
SQLBindCol()
SQLFetch()
Comments:
SQLPrepare(...,'{call byroyalty()}',...) is the ODBC SQL
syntax used to execute stored procedures.
SQLExecute()executes the stored procedure.
SQLBindCol()assigns storage for result column 1 in the
result set (au_id).
SQLFetch() fetches the first record from the result set
generated by the stored procedure.
The following examples illustrate how to call the above MS
SQL Server stored procedure with result sets/dynasets in Visual
Basic using DAO and RDO on
top of ODBC. This code works for Oracle8i packages and
stored procedures if you use an Intersolv ODBC driver to
understand Oracle REF CURSORs.
DAO
Private Sub Command2_Click()
Dim sSql As String
sSql = "{call byroyalty()}"
'In Oracle ODBC driver use refcusor argument to get
result set
Set rCustomers = dbsServer.OpenRecordset(sSql,
dbOpenDynamic)
Text4 = rCustomers.Fields(0)
theend:
End Sub
Please note, this example assumes that a DAO connection has
been set up already.
RDO
Private Sub Command1_Click()
StrSql = "{call byroyalty}"
'in oracle odbc driver uses refcusor argument to get
result set
Set Ps = connx1.CreatePreparedStatement("PsTest",
StrSql)
Set Rs = Ps.OpenResultSet(rdOpenStatic
Text3 = Rs!au_id
Rs.Close
End Sub
Please note, this example assumes that an RDO connection has
been set up already.
Gary (guest) wrote:
: OMW,
: I presently connect to MS SQL in Visual Basic 6.0 using ODBC. I
: would like to connect to Oracle in the same manner. Does the
OMW
: do this, and if so are there any things I should know before
: attempting to use it in this application? I have purchased and
: installed a trial version of Oracle 8i, but I am experiencing
: some slight difficulties in the way Oracle handles Resultsets
: (RDO Components) compared to MS SQL.
: thanks
: g
Oracle Technology Network
http://technet.oracle.com
null

SQL PROFILE USED/NOT USED

Hi All,
We have slow runnig query problem with below queries:
QUERY 1
=======
SELECT "PC0".pxObjClass AS "pxObjClass", "PC0".PXINSNAME AS "pxInsName"
, "PC0".WORKTYPENAME AS "WorkTypeName" , "PC0".PYSTATUSWORK AS
"pyStatusWork" , "PC0".PXCREATEDATETIME AS "pxCreateDateTime",
"PC0".LINKEDREFTO as "pxInsHandle" FROM V_FORM_RELATIONSHIPS_R_1_0
"PC0" WHERE ( "PC0".LINKEDREFFROM = :1 ) AND ( "PC0".pxObjClass = :2
   ) ORDER BY "PC0".PXINSNAME DESC , "PC0".PXCREATEDATETIME
QUERY 2
=======
SELECT PYID AS "pyID" , PXOBJCLASS AS "pxObjClass" , PZINSKEY AS
"pzInsKey", PZINSKEY as "pxInsHandle" FROM V_WORK_R_1_0   WHERE (
PYID = :1 ) AND ( pxObjClass = :2   )
V_WORK_R_1_0 is a view which union all of two table without any where clause
V_FORM_RELATIONSHIPS_R_1_0 is another view that is made up of V_WORK_R_1_0 view and one more table.
Production DBA accepted both the SQL PROFILE created for these two queries.
FROM DBA_HIST_SQLSTATS it looks like sometime the profile getting used and sometime old plan is being used.How to ensure that correct SQLPROFILE once accepted is used?
This is 4 node RAC oracle 11.2.0.2.0 on Linux
For first query below are sql stats
col BEGIN_INTERVAL_TIME for a26
col end_INTERVAL_TIME for a26
col ROWS_PROCESSED_TOTAL for 99999
col ROWS_PROCESSED_delta for 99999
select s.begin_interval_time, s.end_interval_time , q.snap_id, q.dbid, q.sql_id, q.plan_hash_value, q.optimizer_cost, q.optimizer_mode
--,ROWS_PROCESSED_TOTAL,ROWS_PROCESSED_delta--,CPU_TIME_TOTAL,CPU_TIME_DELTA,ELAPSED_TIME_TOTAL,ELAPSED_TIME_DELTA
from dba_hist_sqlstat q, dba_hist_snapshot s
where q.dbid = 4026476544 and q.sql_id = '1um96ykvtwrh4'
and q.snap_id = s.snap_id
and s.begin_interval_time between sysdate-2 and sysdate
order by 1,s.snap_id desc;
BEGIN_INTERVAL_TIME        END_INTERVAL_TIME             SNAP_ID       DBID SQL_ID        PLAN_HASH_VALUE OPTIMIZER_COST OPTIMIZER_
03-JUL-13 06.00.33.805 AM 03-JUL-13 07.00.21.439 AM       17316 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 06.00.33.843 AM 03-JUL-13 07.00.21.475 AM       17316 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 06.00.33.843 AM 03-JUL-13 07.00.21.475 AM       17316 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 06.00.33.843 AM 03-JUL-13 07.00.21.474 AM       17316 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 07.00.21.475 AM 03-JUL-13 08.00.06.051 AM       17317 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 08.00.06.023 AM 03-JUL-13 09.00.11.626 AM       17318 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 08.00.06.023 AM 03-JUL-13 09.00.11.626 AM       17318 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 08.00.06.051 AM 03-JUL-13 09.00.11.596 AM       17318 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 08.00.06.051 AM 03-JUL-13 09.00.11.623 AM       17318 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 08.00.06.051 AM 03-JUL-13 09.00.11.596 AM       17318 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 11.00.10.502 AM 03-JUL-13 12.00.16.034 PM       17321 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 11.00.10.502 AM 03-JUL-13 12.00.16.033 PM       17321 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 11.00.10.503 AM 03-JUL-13 12.00.16.034 PM       17321 4026476544 1um96ykvtwrh4       377865450             20 ALL_ROWS
03-JUL-13 12.00.16.034 PM 03-JUL-13 01.00.42.715 PM       17322 4026476544 1um96ykvtwrh4       377865450                ALL_ROWS
03-JUL-13 01.00.42.685 PM 03-JUL-13 02.00.10.200 PM       17323 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 01.00.42.714 PM 03-JUL-13 02.00.10.200 PM       17323 4026476544 1um96ykvtwrh4      1122713586         179350 ALL_ROWS
03-JUL-13 03.00.15.887 PM 03-JUL-13 04.00.05.570 PM       17325 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 03.00.15.887 PM 03-JUL-13 04.00.05.570 PM       17325 4026476544 1um96ykvtwrh4       377865450          30585 ALL_ROWS
03-JUL-13 03.00.15.914 PM 03-JUL-13 04.00.05.541 PM       17325 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 03.00.15.915 PM 03-JUL-13 04.00.05.570 PM       17325 4026476544 1um96ykvtwrh4       377865450          30585 ALL_ROWS
03-JUL-13 04.00.05.541 PM 03-JUL-13 05.00.09.865 PM       17326 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 05.00.09.866 PM 03-JUL-13 06.00.26.710 PM       17327 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 08.00.12.716 PM 03-JUL-13 09.00.00.960 PM       17330 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
03-JUL-13 08.00.12.716 PM 03-JUL-13 09.00.00.989 PM       17330 4026476544 1um96ykvtwrh4      1122713586         179347 ALL_ROWS
377865450 is the sql_hash of explain plan given by SQL_PROFILE
select
    2 extractvalue(value(d), '/hint') as outline_hints
    3 from
    4 xmltable('/*/outline_data/hint'
    5 passing (
    6 select
    7 xmltype(other_xml) as xmlval
    8 from
    9 dba_hist_sql_plan
   10 where
   11 sql_id = '&sql_id'
   12 and plan_hash_value = &plan_hash_value
   13 and other_xml is not null
   14   15 ) d;
Enter value for sql_id: 1um96ykvtwrh4
old 11: sql_id = '&sql_id'
new 11: sql_id = '1um96ykvtwrh4'
Enter value for plan_hash_value: 377865450
old 12: and plan_hash_value = &plan_hash_value
new 12: and plan_hash_value = 377865450
OUTLINE_HINTS
IGNORE_OPTIM_EMBEDDED_HINTS
OPTIMIZER_FEATURES_ENABLE('11.2.0.2')
DB_VERSION('11.2.0.2')
ALL_ROWS
OUTLINE_LEAF(@"SEL$B01C6807")
OUTLINE_LEAF(@"SEL$8E13D68A")
OUTLINE_LEAF(@"SET$5715CE2E")
PUSH_PRED(@"SEL$F5BB74E1" "VW"@"SEL$2" 3)
OUTLINE_LEAF(@"SEL$F5BB74E1")
MERGE(@"SEL$2")
OUTLINE(@"SEL$3")
OUTLINE_HINTS
OUTLINE(@"SEL$4")
OUTLINE(@"SET$1")
OUTLINE(@"SEL$F5BB74E1")
MERGE(@"SEL$2")
OUTLINE(@"SEL$1")
OUTLINE(@"SEL$2")
INDEX_RS_ASC(@"SEL$F5BB74E1" "LR"@"SEL$2" ("LINK_RELATIONSHIP"."PXLINKEDREFFROM"
NO_ACCESS(@"SEL$F5BB74E1" "VW"@"SEL$2")
LEADING(@"SEL$F5BB74E1" "LR"@"SEL$2" "VW"@"SEL$2")
OUTLINE_HINTS
USE_NL(@"SEL$F5BB74E1" "VW"@"SEL$2")
INDEX_RS_ASC(@"SEL$8E13D68A" "W"@"SEL$4" ("WORK_COMMON"."PZINSKEY"))
INDEX_RS_ASC(@"SEL$B01C6807" "WORK_BATCH"@"SEL$3" ("WORK_BATCH"."PZINSKEY"))
select id, operation, options, object_name, cost
from dba_hist_sql_plan
where dbid = 4026476544 and sql_id = '1um96ykvtwrh4'
and plan_hash_value = 377865450 2    3    4
    5 ;
    ID OPERATION                      OPTIONS                        OBJECT_NAME                     COST
     0 SELECT STATEMENT                                                                                20
     1 SORT                           ORDER BY                                                         20
     2 FILTER
     3 NESTED LOOPS                                                                                    19
     4 TABLE ACCESS                   BY INDEX ROWID                 LINK_RELATIONSHIP                  5
     5 INDEX                          RANGE SCAN                     RELATIONSHIP_REFFROM               3
     6 VIEW                                                          V_WORK_R_1_0                       7
     7 UNION ALL PUSHED PREDICATE
     8 TABLE ACCESS                   BY INDEX ROWID                 WORK_BATCH                         4
     9 INDEX                          UNIQUE SCAN                    WORK_BATCH_PK                      3
    10 TABLE ACCESS                   BY INDEX ROWID                 WORK_COMMON                        3
    11 INDEX                          UNIQUE SCAN                    WORK_COMMON_PK                     2
EXPLAIN PLAN OF SQL_PROFILE PROVIDED
select * from table(dbms_xplan.display_awr('1um96ykvtwrh4',377865450,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 1um96ykvtwrh4
SELECT "PC0".pxObjClass AS "pxObjClass", "PC0".PXINSNAME AS "pxInsName"
, "PC0".WORKTYPENAME AS "WorkTypeName" , "PC0".PYSTATUSWORK AS
"pyStatusWork" , "PC0".PXCREATEDATETIME AS "pxCreateDateTime",
"PC0".LINKEDREFTO as "pxInsHandle" FROM V_FORM_RELATIONSHIPS_R_1_0
"PC0" WHERE ( "PC0".LINKEDREFFROM = :1 ) AND ( "PC0".pxObjClass = :2
    ) ORDER BY "PC0".PXINSNAME DESC , "PC0".PXCREATEDATETIME
Plan hash value: 377865450
| Id | Operation                        | Name                 | E-Rows |E-Bytes| Cost (%CPU)| E-Time   |
|   0 | SELECT STATEMENT                 |                      |        |       |    20 (100)|          |
|   1 | SORT ORDER BY                   |                      |      2 | 1362 |    20   (5)| 00:00:01 |
|   2 |   FILTER                         |                      |        |       |            |          |
|   3 |    NESTED LOOPS                  |                      |      2 | 1362 |    19   (0)| 00:00:01 |
|   4 |     TABLE ACCESS BY INDEX ROWID | LINK_RELATIONSHIP    |      2 |   204 |     5   (0)| 00:00:01 |
|   5 |      INDEX RANGE SCAN            | RELATIONSHIP_REFFROM |      2 |       |     3   (0)| 00:00:01 |
|   6 |     VIEW                         | V_WORK_R_1_0         |      1 |   579 |     7   (0)| 00:00:01 |
|   7 |      UNION ALL PUSHED PREDICATE |                      |        |       |            |          |
|   8 |       TABLE ACCESS BY INDEX ROWID| WORK_BATCH           |      1 |    89 |     4   (0)| 00:00:01 |
|   9 |        INDEX UNIQUE SCAN         | WORK_BATCH_PK        |      1 |       |     3   (0)| 00:00:01 |
| 10 |       TABLE ACCESS BY INDEX ROWID| WORK_COMMON          |      1 |   109 |     3   (0)| 00:00:01 |
| 11 |        INDEX UNIQUE SCAN         | WORK_COMMON_PK       |      1 |       |     2   (0)| 00:00:01 |
Query Block Name / Object Alias (identified by operation id):
     1 - SEL$F5BB74E1
     4 - SEL$F5BB74E1 / LR@SEL$2
     5 - SEL$F5BB74E1 / LR@SEL$2
     6 - SET$5715CE2E / VW@SEL$2
     7 - SET$5715CE2E
     8 - SEL$B01C6807 / WORK_BATCH@SEL$3
     9 - SEL$B01C6807 / WORK_BATCH@SEL$3
    10 - SEL$8E13D68A / W@SEL$4
    11 - SEL$8E13D68A / W@SEL$4
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'xxxx-xxx-SERVICEREQUEST-WORK-ACCTMAINT AM-13640'
Note
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
OLD EXPLAIN PLAN IS
select * from table(dbms_xplan.display_awr('1um96ykvtwrh4',1122713586,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 1um96ykvtwrh4
SELECT "PC0".pxObjClass AS "pxObjClass", "PC0".PXINSNAME AS "pxInsName"
, "PC0".WORKTYPENAME AS "WorkTypeName" , "PC0".PYSTATUSWORK AS
"pyStatusWork" , "PC0".PXCREATEDATETIME AS "pxCreateDateTime",
"PC0".LINKEDREFTO as "pxInsHandle" FROM V_FORM_RELATIONSHIPS_R_1_0
"PC0" WHERE ( "PC0".LINKEDREFFROM = :1 ) AND ( "PC0".pxObjClass = :2
    ) ORDER BY "PC0".PXINSNAME DESC , "PC0".PXCREATEDATETIME
Plan hash value: 1122713586
| Id | Operation                 | Name                  | E-Rows |E-Bytes|E-Temp | Cost (%CPU)| E-Time   |
|   0 | SELECT STATEMENT          |                       |        |       |       |   171K(100)|          |
|   1 | SORT ORDER BY            |                       | 32220 |    20M|    22M|   171K (1)| 00:34:18 |
|   2 |   FILTER                  |                       |        |       |       |            |          |
|   3 |    HASH JOIN              |                       | 32220 |    20M| 3560K|   166K (1)| 00:33:22 |
|   4 |     VIEW                  | index$_join$_002      | 31931 | 3180K|       | 1648   (1)| 00:00:20 |
|   5 |      HASH JOIN            |                       |        |       |       |            |          |
|   6 |       INDEX RANGE SCAN    | RELATIONSHIP_REFFROM | 31931 | 3180K|       |   430   (1)| 00:00:06 |
|   7 |       INDEX FAST FULL SCAN| AK1_LINK_RELATIONSHIP | 31931 | 3180K|       | 1096   (1)| 00:00:14 |
|   8 |     VIEW                  | V_WORK_R_1_0          |   3946K| 2178M|       | 54733   (1)| 00:10:57 |
|   9 |      UNION-ALL            |                       |        |       |       |            |          |
| 10 |       TABLE ACCESS FULL   | WORK_BATCH            |   3910K|   331M|       | 53959   (1)| 00:10:48 |
| 11 |       TABLE ACCESS FULL   | WORK_COMMON           | 35334 | 3761K|       |   774   (1)| 00:00:10 |
Query Block Name / Object Alias (identified by operation id):
     1 - SEL$F5BB74E1
     4 - SEL$838CAA44 / LR@SEL$2
     5 - SEL$838CAA44
     6 - SEL$838CAA44 / indexjoin$_alias$_001@SEL$838CAA44
     7 - SEL$838CAA44 / indexjoin$_alias$_002@SEL$838CAA44
     8 - SET$1        / VW@SEL$2
     9 - SET$1
    10 - SEL$3        / WORK_BATCH@SEL$3
    11 - SEL$4        / W@SEL$4
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'xxxxxx-xxx-SERVICEREQUEST-WORK-BD-DOCUMENTREQUEST ACE_BD_DR-166646'
Note
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
52 rows selected.
Select sql_id,plan_hash_value,old_hash_value,child_number,OUTLINE_CATEGORY,CPU_TIME,ELAPSED_TIME,SQL_PROFILE from gv$sql where sql_id='1um96ykvtwrh4';
SQL_ID        PLAN_HASH_VALUE OLD_HASH_VALUE CHILD_NUMBER OUTLINE_CA   CPU_TIME ELAPSED_TIME SQL_PROFILE
1um96ykvtwrh4       377865450     3763442152            2                 81989       198629 SYS_SQLPROF_013fa7a18f7c0001
1um96ykvtwrh4      1122713586     3763442152            0              44147289    172322738
1um96ykvtwrh4      1122713586     3763442152            1            1905933242   6101663681
1um96ykvtwrh4       377865450     3763442152            3                 55988       108690 SYS_SQLPROF_013fa7a18f7c0001
FOR QUERY 2
col BEGIN_INTERVAL_TIME for a26
col end_INTERVAL_TIME for a26
select s.begin_interval_time, s.end_interval_time , q.snap_id, q.dbid, q.sql_id,q.VERSION_COUNT, q.plan_hash_value, q.optimizer_cost, q.optimizer_mode
from dba_hist_sqlstat q, dba_hist_snapshot s
where q.dbid = 4026476544 and q.sql_id = '4prk4w6sdtxa5'
and q.snap_id = s.snap_id
and s.begin_interval_time between sysdate-2 and sysdate
order by 1,s.snap_id desc;
BEGIN_INTERVAL_TIME        END_INTERVAL_TIME             SNAP_ID       DBID SQL_ID        PLAN_HASH_VALUE OPTIMIZER_COST OPTIMIZER_
04-JUL-13 12.00.01.427 PM 04-JUL-13 01.00.02.453 PM       17346 4026476544 4prk4w6sdtxa5      3168544609          56710 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5       455675889            985 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5      3168544609          56710 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5       455675889            985 ALL_ROWS
04-JUL-13 12.00.01.430 PM 04-JUL-13 01.00.02.413 PM       17346 4026476544 4prk4w6sdtxa5      3168544609          56710 ALL_ROWS
OLD EXPLAIN PAL
select * from table(dbms_xplan.display_awr('4prk4w6sdtxa5',3168544609,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 4prk4w6sdtxa5
SELECT PYID AS "pyID" , PXOBJCLASS AS "pxObjClass" , PZINSKEY AS
"pzInsKey", PZINSKEY as "pxInsHandle" FROM V_WORK_R_1_0   WHERE (
PYID = :1 ) AND ( pxObjClass = :2   )
Plan hash value: 3168544609
| Id | Operation                      | Name            | E-Rows |E-Bytes| Cost (%CPU)| E-Time   |
|   0 | SELECT STATEMENT               |                 |        |       | 53846 (100)|          |
|   1 | VIEW                          | V_WORK_R_1_0    |      2 | 1238 | 53846   (1)| 00:10:47 |
|   2 |   UNION-ALL                    |                 |        |       |            |          |
|   3 |    FILTER                      |                 |        |       |            |          |
|   4 |     TABLE ACCESS FULL          | WORK_BATCH      |      1 |    67 | 53844   (1)| 00:10:47 |
|   5 |    FILTER                      |                 |        |       |            |          |
|   6 |     TABLE ACCESS BY INDEX ROWID| WORK_COMMON     |      1 |   578 |     2   (0)| 00:00:01 |
|   7 |      INDEX RANGE SCAN          | AK1_WORK_COMMON |      1 |       |     1   (0)| 00:00:01 |
Query Block Name / Object Alias (identified by operation id):
     1 - SET$1 / V_WORK_R_1_0@SEL$1
     2 - SET$1
     3 - SEL$2
     4 - SEL$2 / WORK_BATCH@SEL$2
     5 - SEL$3
     6 - SEL$3 / W@SEL$3
     7 - SEL$3 / W@SEL$3
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'CM-22180'
Note
     - dynamic sampling used for this statement (level=2)
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
NEW EXPLAIN PLAN IS
select * from table(dbms_xplan.display_awr('4prk4w6sdtxa5',455675889,4026476544, 'ALL +peeked_binds +ALLSTATS LAST'));
PLAN_TABLE_OUTPUT
SQL_ID 4prk4w6sdtxa5
SELECT PYID AS "pyID" , PXOBJCLASS AS "pxObjClass" , PZINSKEY AS
"pzInsKey", PZINSKEY as "pxInsHandle" FROM V_WORK_R_1_0   WHERE (
PYID = :1 ) AND ( pxObjClass = :2   )
Plan hash value: 455675889
| Id | Operation                            | Name            | E-Rows |E-Bytes| Cost (%CPU)| E-Time   |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT                     |                 |        |       |   985 (100)|          |        |      |            |
|   1 | PX COORDINATOR                      |                 |        |       |            |          |        |      |            |
|   2 |   PX SEND QC (RANDOM)                | :TQ10001        |      2 | 1238 |   985   (1)| 00:00:12 | Q1,01 | P->S | QC (RAND) |
|   3 |    BUFFER SORT                       |                 |      2 | 1238 |            |          | Q1,01 | PCWP |            |
|   4 |     VIEW                             | V_WORK_R_1_0    |      2 | 1238 |   985   (1)| 00:00:12 | Q1,01 | PCWP |            |
|   5 |      UNION-ALL                       |                 |        |       |            |          | Q1,01 | PCWP |            |
|   6 |       FILTER                         |                 |        |       |            |          | Q1,01 | PCWC |            |
|   7 |        PX BLOCK ITERATOR             |                 |      1 |    67 |   983   (1)| 00:00:12 | Q1,01 | PCWC |            |
|   8 |         TABLE ACCESS FULL            | WORK_BATCH      |      1 |    67 |   983   (1)| 00:00:12 | Q1,01 | PCWP |            |
|   9 |       BUFFER SORT                    |                 |        |       |            |          | Q1,01 | PCWC |            |
| 10 |        PX RECEIVE                    |                 |      1 |    59 |     2   (0)| 00:00:01 | Q1,01 | PCWP |            |
| 11 |         PX SEND ROUND-ROBIN          | :TQ10000        |      1 |    59 |     2   (0)| 00:00:01 |        | S->P | RND-ROBIN |
| 12 |          FILTER                      |                 |        |       |            |          |        |      |            |
| 13 |           TABLE ACCESS BY INDEX ROWID| WORK_COMMON     |      1 |    59 |     2   (0)| 00:00:01 |        |      |            |
| 14 |            INDEX RANGE SCAN          | AK1_WORK_COMMON |      1 |       |     1   (0)| 00:00:01 |        |      |            |
Query Block Name / Object Alias (identified by operation id):
     1 - SEL$1
     4 - SET$1 / V_WORK_R_1_0@SEL$1
     5 - SET$1
     6 - SEL$2
     8 - SEL$2 / WORK_BATCH@SEL$2
    12 - SEL$3
    13 - SEL$3 / W@SEL$3
    14 - SEL$3 / W@SEL$3
Peeked Binds (identified by position):
     1 - :1 (VARCHAR2(30), CSID=873): 'AM-15042'
Note
     - automatic DOP: Computed Degree of Parallelism is 64
     - SQL profile "SYS_SQLPROF_013fa79ff2ee0000" used for this statement
     - Warning: basic plan statistics not available. These are only collected when:
      * hint 'gather_plan_statistics' is used for the statement or
      * parameter 'statistics_level' is set to 'ALL', at session or system level
53 rows selected.
HINT USED IN EXPLAIN PLAN GIVEN BY SQL_PROFILE
select
   extractvalue(value(d), '/hint') as outline_hints
   from
   xmltable('/*/outline_data/hint'
   passing (
   select
   xmltype(other_xml) as xmlval
   from
   dba_hist_sql_plan
   where
   sql_id = '&sql_id'
   and plan_hash_value = &plan_hash_value
   and other_xml is not null
)) d;
   OUTLINE_HINTS
IGNORE_OPTIM_EMBEDDED_HINTS
OPTIMIZER_FEATURES_ENABLE('11.2.0.2')
DB_VERSION('11.2.0.2')
OPT_PARAM('optimizer_dynamic_sampling' 5)
ALL_ROWS
SHARED(64)
OUTLINE_LEAF(@"SEL$2")
OUTLINE_LEAF(@"SEL$3")
OUTLINE_LEAF(@"SET$1")
OUTLINE_LEAF(@"SEL$1")
NO_ACCESS(@"SEL$1" "V_WORK_R_1_0"@"SEL$1")
INDEX_RS_ASC(@"SEL$3" "W"@"SEL$3" ("WORK_COMMON"."PYID"))
FULL(@"SEL$2" "WORK_BATCH"@"SEL$2")
col OUTLINE_CATEGORY for a10
col SQL_PROFILE for a30
select sql_id,plan_hash_value,old_hash_value,child_number,OUTLINE_CATEGORY,CPU_TIME,ELAPSED_TIME,SQL_PROFILE from gv$sql where sql_id='4prk4w6sdtxa5';
SQL_ID        PLAN_HASH_VALUE OLD_HASH_VALUE CHILD_NUMBER OUTLINE_CA   CPU_TIME ELAPSED_TIME SQL_PROFILE
4prk4w6sdtxa5      3168544609      353644632            0            2633226703   4.4271E+10
4prk4w6sdtxa5       455675889      353644632            1              27225852    759830164 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632            2             119988890   9664144040 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632            3              85872011   5942746451 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5      3168544609      353644632            0             335776954    337580538
4prk4w6sdtxa5      3168544609      353644632            1             399056329    401261240
4prk4w6sdtxa5      3168544609      353644632            2             484240383    486679352
4prk4w6sdtxa5      3168544609      353644632            3             401375979    492360355
4prk4w6sdtxa5      3168544609      353644632            4             930830490   2.2156E+10
4prk4w6sdtxa5      3168544609      353644632            5             403837610    472368680
4prk4w6sdtxa5      3168544609      353644632            6            1136393235   2.5397E+10
4prk4w6sdtxa5      3168544609      353644632            7             858015552   1.6636E+10
4prk4w6sdtxa5       455675889      353644632            8              68884598   6001624174 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632            9              21730702    629077530 SYS_SQLPROF_013fa79ff2ee0000
4prk4w6sdtxa5       455675889      353644632           10              93504893   8216578447 SYS_SQLPROF_013fa79ff2ee0000
OTHER INFO
SQL> select table_name,owner,index_name,INDEX_TYPE from dba_indexes where table_name in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP');
TABLE_NAME                     OWNER                          INDEX_NAME                     INDEX_TYPE
LINK_RELATIONSHIP              ACE                            SYS_IL0000120332C00018$$       LOB
WORK_BATCH                     ACE                            SYS_IL0000120308C00085$$       LOB
WORK_COMMON                    ACE                            SYS_IL0000243612C00085$$       LOB
LINK_RELATIONSHIP              ACE                            LINK_RELATIONSHIP_PK           NORMAL
LINK_RELATIONSHIP              ACE                            AK1_LINK_RELATIONSHIP          NORMAL
LINK_RELATIONSHIP              ACE                            RELATIONSHIP_REFFROM           NORMAL
WORK_BATCH                     ACE                            WORK_BATCH_PK                  NORMAL
WORK_BATCH                     ACE                            IDX1_WORK_BATCH                NORMAL
WORK_COMMON                    ACE                            AK2_WORK_COMMON                NORMAL
WORK_COMMON                    ACE                            AK1_WORK_COMMON                NORMAL
WORK_COMMON                    ACE                            WORK_COMMON_PK                 NORMAL
col object_name for a25
select created,object_name,object_type,owner,LAST_DDL_TIME from dba_objects where object_name in ('WORK_BATCH','WORK_COMMON','WORK_BATCH_PK','WORK_COMMON_PK','AK1_LINK_RELATIONSHIP','RELATIONSHIP_REFFROM')
    2
CREATED     OBJECT_NAME               OBJECT_TYPE         OWNER                          LAST_DDL_TI
28-JUN-2012 WORK_BATCH                TABLE               ACE                            15-JUN-2013
28-JUN-2012 WORK_BATCH_PK             INDEX               ACE                            29-MAY-2013
30-NOV-2012 RELATIONSHIP_REFFROM      INDEX               ACE                            03-JUL-2013
23-FEB-2013 AK1_LINK_RELATIONSHIP     INDEX               ACE                            23-FEB-2013
15-JUN-2013 WORK_COMMON               TABLE               ACE                            15-JUN-2013
15-JUN-2013 WORK_COMMON_PK            INDEX               ACE                            15-JUN-2013
09-MAR-2013 WORK_BATCH                SYNONYM             ACE_USER                       09-MAR-2013
col COLUMN_NAME for a20
Select INDEX_NAME,TABLE_NAME,COLUMN_NAME,COLUMN_POSITION from dba_ind_columns where table_name in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP');
INDEX_NAME                     TABLE_NAME                     COLUMN_NAME          COLUMN_POSITION
RELATIONSHIP_REFFROM           LINK_RELATIONSHIP              PXLINKEDREFFROM                    1
AK1_LINK_RELATIONSHIP          LINK_RELATIONSHIP              PXLINKEDREFTO                      1
LINK_RELATIONSHIP_PK           LINK_RELATIONSHIP              PZINSKEY                           1
IDX1_WORK_BATCH                WORK_BATCH                     CAPTUREUNIQUEID                    1
WORK_BATCH_PK                  WORK_BATCH                     PZINSKEY                           1
WORK_COMMON_PK                 WORK_COMMON                    PZINSKEY                           1
AK1_WORK_COMMON                WORK_COMMON                    PYID                               1
AK2_WORK_COMMON                WORK_COMMON                    PXOBJCLASS                         1
SQL> select distinct tablespace_name from dba_tablespaces where tablespace_name like '%INDEX%';
TABLESPACE_NAME
ACE_INDEXES_M
RBS_INDEXES_S
SPS_INDEXES_S
ACE_INDEXES_S
ACE_INDEXES_L
FI_INDEXES_S
FI_INDEXES_M
RBS_INDEXES_M
8 rows selected.
   col SEARCH_CONDITION for a25
   col OWNER for a10
   select OWNER,CONSTRAINT_NAME,CONSTRAINT_TYPE,TABLE_NAME,SEARCH_CONDITION,INDEX_NAME from dba_constraints where TABLE_NAME in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP')
   OWNER      CONSTRAINT_NAME                C TABLE_NAME                     SEARCH_CONDITION          INDEX_NAME
ACE        SYS_C00150550                  C WORK_COMMON                    "PZINSKEY" IS NOT NULL
ACE        WORK_BATCH_PK                  P WORK_BATCH                                               WORK_BATCH_PK
ACE        LINK_RELATIONSHIP_PK           P LINK_RELATIONSHIP                                        LINK_RELATIONSHIP_PK
ACE        WORK_COMMON_PK                 P WORK_COMMON                                              WORK_COMMON_PK
select attr_val hint
from dba_sql_profiles p, sqlprof$attr h
where p.signature = h.signature
and name like ('SYS_SQLPROF_013fa7a18f7c0001')
order by attr#
   select LAST_ANALYZED,SAMPLE_SIZE,num_rows from dba_tables where table_name in ('WORK_BATCH','WORK_COMMON','LINK_RELATIONSHIP');
LAST_ANALYZ SAMPLE_SIZE   NUM_ROWS
02-JUL-2013     4122880    4122880
02-JUL-2013       81108      81108
03-JUL-2013       40802      40802
SQL> select count(pzinskey) from ace.WORK_BATCH;
COUNT(PZINSKEY)
    4138044
SQL> select count(pzinskey) from ace.WORK_COMMON;
COUNT(PZINSKEY)
      40805

Hi,
i think you should give a try on baseline.
Profiles are more subject to stats ad dynamic sampling.
You can find this useful:
Kerry Osborne SQL Profiles Disable Automatic Dynamic Sampling
This doesn't match your case but can give some advices.
Regs,
Drew

Explain plan and SQL profile.

Hi ,
I got a sql tuning result for one query , and i need to understand the below fileds in the explain plan
operation lineid object object_type order rows bytes cost time cpucost iocost
any document to understand will be appreciated
and in recomendation i got Consider accepting the recommended SQL profile. suppose if it was not feasible after accepting the SQL profile can i revert back.
Thanks

user12266475 wrote:
Hi ,
I got a sql tuning result for one query , and i need to understand the below fileds in the explain plan
operation lineid object object_type order rows bytes cost time cpucost iocost
any document to understand will be appreciated
and in recomendation i got Consider accepting the recommended SQL profile. suppose if it was not feasible after accepting the SQL profile can i revert back.
Thankshttp://docs.oracle.com/cd/E11882_01/server.112/e16638/toc.htm
Thread: HOW TO: Post a SQL statement tuning request - template posting
HOW TO: Post a SQL statement tuning request - template posting

SQL profiler equivalent in oracle

Similar Messages

Maybe you are looking for