0% found this document useful (0 votes)
9 views3 pages

AWR Analysis

The document provides SQL performance statistics, detailing elapsed time, CPU time, and buffer gets for various SQL statements executed in a database. It highlights the resource usage of PL/SQL code and includes a breakdown of SQL statements ordered by elapsed time, CPU time, and buffer gets. Additionally, it poses questions regarding the feasibility of performing certain SQL activities during non-business hours.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
9 views3 pages

AWR Analysis

The document provides SQL performance statistics, detailing elapsed time, CPU time, and buffer gets for various SQL statements executed in a database. It highlights the resource usage of PL/SQL code and includes a breakdown of SQL statements ordered by elapsed time, CPU time, and buffer gets. Additionally, it poses questions regarding the feasibility of performing certain SQL activities during non-business hours.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

SQL ordered by Elapsed Time

 Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.
 % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100

Elapsed CPU Elap per % Total SQL


Executions SQL Id SQL Text
Time (s) Time (s) Exec (s) DB Time Module
2,555 2 1,063 2.40 55.45 8b4uwcnk933xp JDBC Thin begin tpp_user_login ( :1 , ...
Client
2,348 0 1,063 2.21 50.96 5vr7g31knk62a JDBC Thin UPDATE TPT_PERSON_LOG
Client SET BAD_...
1,264 1,205 1 1263.73 27.43 8vab19advdxbs SQL*Plus BEGIN
pkg_mig_ext_organization...
998 990 2,041 0.49 21.65 8btdqg396y5qp SQL*Plus SELECT COUNT(*) FROM
TPT_ACCOU...
374 360 1 373.61 8.11 fpdx65rx03g5h SQL*Plus BEGIN
pkg_mig_internal_person....
205 0 949 0.22 4.45 516hbks3jztzu JDBC Thin UPDATE TPT_PERSON_LOG
Client SET LOGG...
162 160 11,075 0.01 3.52 438pfygvt7sj1 SQL*Plus SELECT ID, CREATED_BY,
CREAT...
111 111 282 0.39 2.41 167bsrc46y3bb JDBC Thin select username from cmt_perso...
Client
61 61 11,076 0.01 1.33 g4kudqkgm2vju SQL*Plus SELECT COUNT(* ) FROM
CMT_PERS...
20 20 50 0.40 0.44 3qrphtjfspy9w JDBC Thin select /* 70771:300 */ 'basi...
Client

Back to SQL Statistics


Back to Top

SQL ordered by CPU Time


 Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.
 % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100

CPU Elapsed CPU per % Total SQL


Executions SQL Id SQL Text
Time (s) Time (s) Exec (s) DB Time Module
1,205 1,264 1 1205.45 27.43 8vab19advdxbs SQL*Plus BEGIN
pkg_mig_ext_organization...
990 998 2,041 0.49 21.65 8btdqg396y5qp SQL*Plus SELECT COUNT(*) FROM
TPT_ACCOU...
360 374 1 359.74 8.11 fpdx65rx03g5h SQL*Plus BEGIN pkg_mig_internal_person....
160 162 11,075 0.01 3.52 438pfygvt7sj1 SQL*Plus SELECT ID, CREATED_BY,
CREAT...
111 111 282 0.39 2.41 167bsrc46y3bb JDBC Thin select username from cmt_perso...
Client
61 61 11,076 0.01 1.33 g4kudqkgm2vju SQL*Plus SELECT COUNT(* ) FROM
CMT_PERS...
20 20 50 0.40 0.44 3qrphtjfspy9w JDBC Thin select /* 70771:300 */ 'basi...
Client
15 15 232 0.06 0.33 9z8tm5h0q6r7m JDBC Thin select c.id, c.name2 cname, ...
Client
9 17 35,358 0.00 0.37 f699zfyrxnf5t SQL*Plus UPDATE CMT_EXT_SOURCE
SET SOUR...
8 9 1 8.17 0.20 4xn6yvufrqt1y SQL*Plus BEGIN
pkg_mig_job_type.scp_mig...
2 2,555 1,063 0.00 55.45 8b4uwcnk933xp JDBC Thin begin tpp_user_login ( :1 , ...
Client
0 2,348 1,063 0.00 50.96 5vr7g31knk62a JDBC Thin UPDATE TPT_PERSON_LOG
Client SET BAD_...
0 205 949 0.00 4.45 516hbks3jztzu JDBC Thin UPDATE TPT_PERSON_LOG
Client SET LOGG...

What activities we were doing from sqlplus in Business Hours time? Can this be done in non-business
hrs. Can we do DB_imports in non-business hrs.

1,264 1,205 1 1263.73 27.43 8vab19advdxbs SQL*Plus BEGIN pkg_mig_ext_organization...


360 374 1 359.74 8.11 fpdx65rx03g5h SQL*Plus BEGIN pkg_mig_internal_person....
8 9 1 8.17 0.20 4xn6yvufrqt1y SQL*Plus BEGIN pkg_mig_job_type.scp_mig...

SQL ordered by CPU Time


 Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.
 % Total DB Time is the Elapsed Time of the SQL statement divided into the Total Database Time multiplied by 100

CPU Elapsed CPU per % Total SQL


Executions SQL Id SQL Text
Time (s) Time (s) Exec (s) DB Time Module
1,205 1,264 1 1205.45 27.43 8vab19advdxbs SQL*Plus BEGIN
pkg_mig_ext_organization...
990 998 2,041 0.49 21.65 8btdqg396y5qp SQL*Plus SELECT COUNT(*) FROM
TPT_ACCOU...
360 374 1 359.74 8.11 fpdx65rx03g5h SQL*Plus BEGIN
pkg_mig_internal_person....
160 162 11,075 0.01 3.52 438pfygvt7sj1 SQL*Plus SELECT ID, CREATED_BY,
CREAT...

SQL ordered by Gets


 Resources reported for PL/SQL code includes the resources used by all SQL statements called by the code.
 Total Buffer Gets: 90,018,778
 Captured SQL account for 72.4% of Total

CPU
Buffer Gets per Elapsed SQL
Executions %Total Time SQL Id SQL Text
Gets Exec Time (s) Module
(s)
48,747,929 1 48,747,929.00 54.15 1205.45 1263.73 8vab19advdxbs SQL*Plus BEGIN
pkg_mig_ext_organization...
34,223,343 2,041 16,767.93 38.02 990.15 997.53 8btdqg396y5qp SQL*Plus SELECT COUNT(*) FROM
TPT_ACCOU...
19,441,512 1 19,441,512.00 21.60 359.74 373.61 fpdx65rx03g5h SQL*Plus BEGIN
pkg_mig_internal_person....
11,174,675 11,075 1,009.00 12.41 159.81 161.98 438pfygvt7sj1 SQL*Plus SELECT ID, CREATED_BY,
CREAT...
SELECT object_id, file_name, unprocessed, success, failure, total, created_on
FROM (Select CREATED_ON, TENANT_ID, OBJECT_ID, FILE_NAME, UNPROCESSED,
SUCCESS, FAILURE, TOTAL from(
SELECT cd.created_on created_on, cd.tenant_id tenant_id, cd.object_id
object_id, cd.file_name file_name, cd.unprocessed unprocessed, cd.success
success, cd.failure failure, cd.total total FROM (
SELECT min(created_on) created_on, object_id object_id, file_name
file_name, sum(decode(lower(status), 'unprocessed', 1, 0)) unprocessed,
sum(decode(lower(status), 'success', 1, 0)) success, sum(decode(lower(status),
'failure', 1 , 0)) failure, sum(decode(status, null, 0 , 1)) total, tenant_id
FROM tp2.tpt_conn_data GROUP by object_id, file_name , tenant_id )
cd
GROUP by cd.created_on, cd.object_id, cd.file_name, cd.unprocessed,
cd.success, cd.failure, cd.total, cd.tenant_id))
order by created_on desc

You might also like