ADDM Report for Task 'TASK_1465'

--------------------------------

Analysis Period
---------------
AWR snapshot range from 1440 to 1441.
Time period starts at 01-JUN-22 02.00.26 PM
Time period ends at 01-JUN-22 03.00.46 PM

Analysis Target
---------------
Database 'TRECX' with DB ID 620931255.
Database version 19.0.0.0.0.
ADDM performed an analysis of instance trecx, numbered 1 and hosted at
orcltrecx.
ADDM detected that the database type is MULTITENANT DB.

Activity During the Analysis Period

-----------------------------------
Total database time was 10562 seconds.
The average number of active sessions was 2.92.

Summary of Findings
-------------------
Description Active Sessions Recommendation
s
Percent of Activity
---------------------------------------- ------------------- --------------
-
1 Top SQL Statements 1.8 | 61.57 8
2 Row Lock Waits .38 | 13.11 2
3 Session Connect and Disconnect .11 | 3.63 1
4 Top Segments by "User I/O" and "Cluster" .07 | 2.55 1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Findings and Recommendations

----------------------------

Finding 1: Top SQL Statements

Impact is 1.8 active sessions, 61.57% of total activity.
--------------------------------------------------------
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.

Recommendation 1: SQL Tuning

Estimated benefit is .73 active sessions, 25.15% of total activity.
-------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"2qx755n9zjfgh".
Related Object
SQL statement with SQL_ID 2qx755n9zjfgh.
select * from ( select row_.*, rownum rownum_ from ( select
wvinventor0_.id_inventory as id_inventory1_0_,
wvinventor0_.article_code as article_code2_0_, wvinventor0_.reserved
 as reserved3_0_, wvinventor0_.stock as stock4_0_,
wvinventor0_.storage_code as storage_code5_0_ from wv_inventory
wvinventor0_ order by wvinventor0_.id_inventory desc ) row_ where
rownum <= :1 ) where rownum_ > :2
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "2qx755n9zjfgh" was executed 2062 times and
had an average elapsed time of 1.2 seconds.

Recommendation 2: SQL Tuning

Estimated benefit is .45 active sessions, 15.39% of total activity.
-------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"by04m82rqn0nn".
Related Object
SQL statement with SQL_ID by04m82rqn0nn.
select * from ( select row_.*, rownum rownum_ from ( select
wv_tipdesc0_.code as code1_0_, wv_tipdesc0_.article_code as
article_code2_0_, wv_tipdesc0_.business_type_code as
business_type_code3_0_, wv_tipdesc0_.discount_group_code as
discount_group_cod4_0_, wv_tipdesc0_.value as value5_0_ from
wv_tipdesc1 wv_tipdesc0_ order by wv_tipdesc0_.code asc ) row_ where
rownum <= :1 ) where rownum_ > :2
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "by04m82rqn0nn" was executed 2995 times and
had an average elapsed time of 0.53 seconds.

Recommendation 3: SQL Tuning

Estimated benefit is .15 active sessions, 5.03% of total activity.
------------------------------------------------------------------
Action
Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"5tyumgd9jmza1".
Related Object
SQL statement with SQL_ID 5tyumgd9jmza1.
SELECT "IN_ITEM"."CL_CODIGO", "IN_ITEM"."IT_CODANT",
"IN_ITEM"."IT_NOMBRE", "IN_ITEM"."IT_CODBAR", "IN_ITEM"."IT_PRECIO",
"IN_ITEM"."IT_CODIGO", "IN_ITEM"."FB_CODIGO", "IN_ITEM"."MR_CODIGO",
"IN_ITEM"."IT_PREFAB", "IN_ITEM"."MA_CODIGO", "IN_ITEM"."IT_ORIGEN",
"IN_ITEM"."IT_TIEMSEC", "IN_ITEM"."IT_KIT", "IN_ITEM"."IT_FECHA",
"IN_ITEBOD"."IB_STOCK", "IN_ITEBOD"."IB_UBICA",
"IN_ITESUCUR"."IT_RECARGO", "IN_ITESUCUR"."IT_STKDIS",
"IN_ITESUCUR"."IT_STOCK", "IN_FABRICANTE"."FB_NOMBRE",
"IN_MARCAS"."MR_DESCRI", "IN_ITEM"."EP_CODJL",
"IN_ITESUCUR"."IT_DESC", "IN_ITEM"."IT_PREFAB" +
"IN_ITESUCUR"."IT_RECARGO" PLista, round(("IN_ITEM"."IT_PREFAB" +
"IN_ITESUCUR"."IT_RECARGO") * ((100 - "IN_TIPPRE_B"."TD_DESC1")/100)
* ((100 - "IN_TIPPRE_B"."TD_DESC3")/100)*1,2) NORMAL,
round(round(("IN_ITEM"."IT_PREFAB" + "IN_ITESUCUR"."IT_RECARGO") *
((100 - "IN_TIPPRE_B"."TD_DESC1")/100) * ((100 -
"IN_TIPPRE_B"."TD_DESC3")/100)*1,2) * ( 1 + (
"PR_IMPUESTO"."IM_VALOR" * "IN_ITEM"."IT_IVA" ) ), 2) TARJET,
round(round(("IN_ITEM"."IT_PREFAB" + "IN_ITESUCUR"."IT_RECARGO") *
((100 - "IN_TIPPRE_B"."TD_DESC1")/100) * ((100 -
DECODE("IN_ITESUCUR"."IT_DESC2",'S', 4, 0) )/100) * ((100 -
"IN_TIPPRE_B"."TD_DESC3")/100)*1,2) * ( 1 + (
"PR_IMPUESTO"."IM_VALOR" * "IN_ITEM"."IT_IVA" ) ), 2) EFEC,
round(round(("IN_ITEM"."IT_PREFAB" + "IN_ITESUCUR"."IT_RECARGO") *
((100 - "IN_TIPPRE_B"."TD_DESC1")/100) * ((100 -
"IN_ITESUCUR"."IT_DESC" ) /100) * ((100 -
"IN_TIPPRE_B"."TD_DESC3")/100)*1,2) * ( 1 + (
"PR_IMPUESTO"."IM_VALOR" * "IN_ITEM"."IT_IVA" ) ), 2) FERIAPOS,
"IN_ITEM"."IT_PREPARADO", "IN_ITEM"."IT_PAQVENT",
"IN_ITEM"."IT_STATUS",
"IN_ITEM"."IT_RENTAB",
"IN_ITEM"."IT_ACTIVO",
"IN_ITEM"."IT_IVA",
decode( greatest( "IN_ITEBOD"."IB_TRANS", 0), 0, 0,
"IN_ITEBOD"."IB_TRANS") "TRANSITO",
"PR_IMPUESTO"."IM_VALOR",
"IN_ITESUCUR"."IT_DESC2" ,
"IN_TIPPRE_B"."TD_DESC1",
nvl(( select x.ma_descri from in_marca x where x.ma_codigo
="IN_ITEM"."MA_CODIGO" ),'Por Asignar' ) ma_descri
FROM "IN_ITEM", "IN_DESCITEM" "IN_DESCITEM_B", "IN_TIPPRE"
"IN_TIPPRE_B", "IN_ITEM" "IN_ITEM_B", "IN_FABRICANTE", "IN_MARCAS",
"IN_ITESUCUR", "IN_ITEBOD",
"PR_SUCUR",
"PR_IMPUESTO" WHERE ( "IN_ITEM_B"."EM_CODIGO" = "IN_ITEM"."EM_CODIGO"
) and ( "IN_ITEM_B"."IT_CODIGO" = "IN_ITEM"."IT_CODIGO" ) and (
"IN_DESCITEM_B"."TD_CODIGO" = "IN_TIPPRE_B"."TD_CODIGO" ) and (
"IN_DESCITEM_B"."EM_CODIGO" = "IN_ITEM_B"."EM_CODIGO" ) and (
"IN_DESCITEM_B"."IT_CODIGO" = "IN_ITEM_B"."IT_CODIGO" ) and (
"IN_ITESUCUR"."EM_CODIGO" = "IN_ITEM"."EM_CODIGO" ) and (
"IN_ITESUCUR"."IT_CODIGO" = "IN_ITEM"."IT_CODIGO" ) and (
"IN_ITEBOD"."EM_CODIGO" = "IN_ITEM"."EM_CODIGO" ) and (
"IN_ITEBOD"."IT_CODIGO" = "IN_ITEM"."IT_CODIGO" ) and (
"IN_FABRICANTE"."EM_CODIGO" = "IN_ITEM"."EM_CODIGO" ) and (
"IN_FABRICANTE"."FB_CODIGO" = "IN_ITEM"."FB_CODIGO" ) and (
"IN_MARCAS"."EM_CODIGO" = "IN_ITEM"."EM_CODIGO" ) and (
"IN_MARCAS"."MR_CODIGO" = "IN_ITEM"."MR_CODIGO" ) and (
"IN_ITEBOD"."EM_CODIGO" = "IN_ITESUCUR"."EM_CODIGO" ) and (
"IN_ITEBOD"."SU_CODIGO" = "IN_ITESUCUR"."SU_CODIGO" ) and (
"IN_ITEBOD"."IT_CODIGO" = "IN_ITESUCUR"."IT_CODIGO" ) and (
"IN_ITESUCUR"."EM_CODIGO" = "PR_SUCUR"."EM_CODIGO" ) and (
"IN_ITESUCUR"."SU_CODIGO" = "PR_SUCUR"."SU_CODIGO" ) and (
"PR_SUCUR"."IM_CODIGO" = "PR_IMPUESTO"."IM_CODIGO" ) and ( (
"IN_DESCITEM_B"."ES_CODIGO" = '2' ) AND ( "IN_ITEBOD"."SU_CODIGO" =
 :sucursal ) AND ( "IN_ITEBOD"."BO_CODIGO" = :seccion ) ) AND
( "IN_ITEM"."IT_CODIGO" like :ra_busca
OR "IN_ITEM"."IT_CODANT" like :ra_busca
OR "IN_ITEM"."IT_NOMBRE" like :ra_busca
OR "IN_ITEM"."IT_CODBAR" like :ra_busca OR "IN_ITEM"."CL_CODIGO" like
:ra_busca OR "IN_MARCAS"."MR_DESCRI" like :ra_busca ) and
( "IN_ITEM"."IT_ACTIVO" in ( :as_estitem,'A') )
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "5tyumgd9jmza1" was executed 1439 times and
had an average elapsed time of 0.28 seconds.
Rationale
At least 2 distinct execution plans were utilized for this SQL statement
during the analysis period.

Recommendation 4: SQL Tuning

Estimated benefit is .14 active sessions, 4.73% of total activity.
------------------------------------------------------------------
Action
Investigate the UPDATE statement with SQL_ID "36bat5zqah5gd" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID 36bat5zqah5gd.
update pr_param set pr_valor =pr_valor + 1 where em_codigo =:1 and
pr_nombre ='CRE_CXC'
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "36bat5zqah5gd" was executed 43 times and had
an average elapsed time of 10 seconds.
Rationale
Waiting for event "enq: TX - row lock contention" in wait class
"Application" accounted for 100% of the database time spent in
processing the SQL statement with SQL_ID "36bat5zqah5gd".

Recommendation 5: SQL Tuning

Estimated benefit is .1 active sessions, 3.52% of total activity.
-----------------------------------------------------------------
Action
Investigate the SELECT statement with SQL_ID "c5tm80x963403" for
 possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID c5tm80x963403.
select pr_valor , pr_tipo , pr_sucursal from pr_param where pr_nombre
=:1 and em_codigo =:2 for update of pr_valor
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "c5tm80x963403" was executed 36 times and had
an average elapsed time of 9.7 seconds.
Rationale
Waiting for event "enq: TX - row lock contention" in wait class
"Application" accounted for 100% of the database time spent in
processing the SQL statement with SQL_ID "c5tm80x963403".

Recommendation 6: SQL Tuning

Estimated benefit is .09 active sessions, 2.92% of total activity.
------------------------------------------------------------------
Action
Investigate the SELECT statement with SQL_ID "4ukmrjmxsg3ha" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID 4ukmrjmxsg3ha.
select pr_valor from pr_param where em_codigo =:1 and pr_nombre
='NUM_ND' for update of pr_valor
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "4ukmrjmxsg3ha" was executed 52 times and had
an average elapsed time of 5.6 seconds.
Rationale
Waiting for event "enq: TX - row lock contention" in wait class
"Application" accounted for 100% of the database time spent in
processing the SQL statement with SQL_ID "4ukmrjmxsg3ha".

Recommendation 7: SQL Tuning

Estimated benefit is .08 active sessions, 2.72% of total activity.
------------------------------------------------------------------
Action
 Run SQL Tuning Advisor on the SELECT statement with SQL_ID
"4qsxsp8b52y0z".
Related Object
SQL statement with SQL_ID 4qsxsp8b52y0z.
SELECT "IN_ITEBOD"."IB_STKINI", "IN_ITEBOD"."IB_STOCK",
"IN_MOVIM"."TM_CODIGO", "IN_MOVIM"."TM_IOE", "IN_MOVIM"."IT_CODIGO",
"IN_MOVIM"."EM_CODIGO", "IN_MOVIM"."SU_CODIGO",
"IN_MOVIM"."BO_CODIGO", "IN_MOVIM"."MV_NUMERO",
"IN_MOVIM"."MV_CANTID", "IN_MOVIM"."MV_FECHA",
"IN_MOVIM"."MV_OBSERV", "IN_MOVIM"."VE_NUMERO",
"IN_ITEM"."IT_CODANT", "IN_ITEM"."IT_NOMBRE", "IN_ITEM"."IT_COSTO",
"IN_ITEM"."IT_PREFAB", "IN_ITEM"."CL_CODIGO", "IN_ITEM"."FB_CODIGO",
"IN_ITEM"."IT_KIT", "IN_ITEM"."IT_VALSTK",
"IN_ITEM"."IT_CONSIGNA", "IN_MOVIM"."ES_CODIGO",
"IN_MOVIM"."GV_CODIGO", "IN_ITEBOD"."IB_RESERVA"
FROM "IN_MOVIM", "IN_ITEM", "IN_ITEBOD" WHERE (
"IN_MOVIM"."IT_CODIGO" = "IN_ITEM"."IT_CODIGO" ) and (
"IN_MOVIM"."EM_CODIGO" = "IN_ITEM"."EM_CODIGO" ) and (
"IN_ITEBOD"."IT_CODIGO" = "IN_ITEM"."IT_CODIGO" ) and (
"IN_ITEBOD"."EM_CODIGO" = "IN_ITEM"."EM_CODIGO" ) and (
"IN_ITEBOD"."EM_CODIGO" = "IN_MOVIM"."EM_CODIGO" ) and (
"IN_ITEBOD"."SU_CODIGO" = "IN_MOVIM"."SU_CODIGO" ) and (
"IN_ITEBOD"."BO_CODIGO" = "IN_MOVIM"."BO_CODIGO" ) and ( (
"IN_MOVIM"."IT_CODIGO" = :codigo ) AND ( "IN_MOVIM"."EM_CODIGO" = '1'
) AND ( "IN_MOVIM"."SU_CODIGO" = :sucursal ) AND (
"IN_MOVIM"."BO_CODIGO" = :seccion ) ) AND ( "IN_MOVIM"."MV_FECHA" <
:ad_fcorte + 1 )
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
This part of database time may be improved by the SQL Tuning Advisor.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "4qsxsp8b52y0z" was executed 35 times and had
an average elapsed time of 8.1 seconds.
Rationale
At least 3 distinct execution plans were utilized for this SQL statement
during the analysis period.
Rationale
I/O and Cluster wait for TABLE "DINAMIC.IN_MOVIM" with object ID 23689
consumed 100% of the database time spent on this SQL statement.

Recommendation 8: SQL Tuning

Estimated benefit is .06 active sessions, 2.11% of total activity.
------------------------------------------------------------------
Action
Investigate the SELECT statement with SQL_ID "4hxnactkaf564" for
possible performance improvements. You can supplement the information
given here with an ASH report for this SQL_ID.
Related Object
SQL statement with SQL_ID 4hxnactkaf564.
select ps_valor from pr_numsuc where em_codigo =:1 and su_codigo =:2
and pr_nombre =:3 for update of ps_valor
Rationale
 The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL spent only 0% of its database time on CPU, I/O and Cluster
waits. Therefore, the SQL Tuning Advisor is not applicable in this case.
Look at performance data for the SQL to find potential improvements.
Rationale
Database time for this SQL was divided as follows: 100% for SQL
execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
execution.
Rationale
SQL statement with SQL_ID "4hxnactkaf564" was executed 1994 times and
had an average elapsed time of 0.1 seconds.
Rationale
Waiting for event "enq: TX - row lock contention" in wait class
"Application" accounted for 100% of the database time spent in
processing the SQL statement with SQL_ID "4hxnactkaf564".

Finding 2: Row Lock Waits

Impact is .38 active sessions, 13.11% of total activity.
--------------------------------------------------------
SQL statements were found waiting for row lock waits.

Recommendation 1: Application Analysis

Estimated benefit is .32 active sessions, 11.13% of total activity.
-------------------------------------------------------------------
Action
Significant row contention was detected in the TABLE "DINAMIC.PR_PARAM"
with object ID 23646. Trace the cause of row contention in the
application logic using the given blocked SQL.
Related Object
Database object with ID 23646.
Rationale
The database segment belongs to container PINTULAC with database ID
2802383285.
Rationale
The SQL statement with SQL_ID "36bat5zqah5gd" was blocked on row locks.
Related Object
SQL statement with SQL_ID 36bat5zqah5gd.
update pr_param set pr_valor =pr_valor + 1 where em_codigo =:1 and
pr_nombre ='CRE_CXC'
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL statement with SQL_ID "c5tm80x963403" was blocked on row locks.
Related Object
SQL statement with SQL_ID c5tm80x963403.
select pr_valor , pr_tipo , pr_sucursal from pr_param where pr_nombre
=:1 and em_codigo =:2 for update of pr_valor
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The SQL statement with SQL_ID "4ukmrjmxsg3ha" was blocked on row locks.
Related Object
SQL statement with SQL_ID 4ukmrjmxsg3ha.
select pr_valor from pr_param where em_codigo =:1 and pr_nombre
 ='NUM_ND' for update of pr_valor
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.
Rationale
The session with ID 664 and serial number 64490 in instance number 1 was
the blocking session responsible for 61% of this recommendation's
benefit.
Rationale
The session was active in container PINTULAC with database ID
2802383285.
Rationale
The session with ID 652 and serial number 4822 in instance number 1 was
the blocking session responsible for 23% of this recommendation's
benefit.
Rationale
The session was active in container PINTULAC with database ID
2802383285.

Recommendation 2: Application Analysis

Estimated benefit is .06 active sessions, 1.98% of total activity.
------------------------------------------------------------------
Action
Significant row contention was detected in the TABLE "DINAMIC.PR_NUMSUC"
with object ID 23649. Trace the cause of row contention in the
application logic using the given blocked SQL.
Related Object
Database object with ID 23649.
Rationale
The database segment belongs to container PINTULAC with database ID
2802383285.
Rationale
The SQL statement with SQL_ID "4hxnactkaf564" was blocked on row locks.
Related Object
SQL statement with SQL_ID 4hxnactkaf564.
select ps_valor from pr_numsuc where em_codigo =:1 and su_codigo =:2
and pr_nombre =:3 for update of ps_valor
Rationale
The SQL statement executed in container PINTULAC with database ID
2802383285.

Symptoms That Led to the Finding:

---------------------------------
Wait class "Application" was consuming significant database time.
Impact is .39 active sessions, 13.36% of total activity.

Finding 3: Session Connect and Disconnect

Impact is .11 active sessions, 3.63% of total activity.
-------------------------------------------------------
Session connect and disconnect calls were consuming significant database time.

Recommendation 1: Application Analysis

Estimated benefit is .11 active sessions, 3.63% of total activity.
------------------------------------------------------------------
Action
Investigate application logic for possible reduction of connect and
disconnect calls. For example, you might use a connection pool scheme in
the middle tier.
Finding 4: Top Segments by "User I/O" and "Cluster"
Impact is .07 active sessions, 2.55% of total activity.
-------------------------------------------------------
Individual database segments responsible for significant "User I/O" and
"Cluster" waits were found.

Recommendation 1: Segment Tuning

Estimated benefit is .07 active sessions, 2.55% of total activity.
------------------------------------------------------------------
Action
Investigate application logic involving I/O on TABLE "DINAMIC.IN_MOVIM"
with object ID 23689.
Related Object
Database object with ID 23689.
Action
Look at the "Top SQL Statements" finding for SQL statements consuming
significant I/O on this segment. For example, the SELECT statement with
SQL_ID "4qsxsp8b52y0z" is responsible for 100% of "User I/O" and
"Cluster" waits for this segment.
Rationale
The database segment belongs to container PINTULAC with database ID
2802383285.
Rationale
The I/O usage statistics for the object are: 0 full object scans, 614449
physical reads, 171 physical writes and 0 direct reads.

Symptoms That Led to the Finding:

---------------------------------
Wait class "User I/O" was consuming significant database time.
Impact is .11 active sessions, 3.77% of total activity.