10gDB Performance:R12
Hi,
I found following activitoes on my ADDM report .. Plz advice
FINDING 2: 73% impact (13482 seconds)
SQL statements consuming significant database time were found.
RECOMMENDATION 1: SQL Tuning, 25% benefit (4640 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"8v8h41b8xypnr".
RELEVANT OBJECT: SQL statement with SQL_ID 8v8h41b8xypnr and
PLAN_HASH 3229043654
SELECT /*+ NOREWRITE */
DECODE(o310689.ORDER_NUMBER,2020090010,'Exclude',2020090011,'Exclude'
,2010090002,'Exclude',2020090012,'Exclude',2020090016,'Exclude',20100
90006,'Exclude',2010090007,'Exclude',2010090009,'Exclude',2020090032,
'Exclude',2010090015,'Exclude',2010090019,'Exclude',2020090037,'Exclu
de',2020090039,'Exclude',2020090040,'Exclude',2010090026,'Exclude',20
20090046,'Exclude',2010090027,'Exclude',2010090028,'Exclude',20200900
51,'Exclude',2020090052,'Exclude',2020090060,'Exclude',2020090062,'Ex
clude',2010090010,'Exclude',2020090036,'Exclude',2020090038,'Exclude'
,2020090045,'Exclude',2020090058,'Exclude',2010090033,'Exclude',946,'
Exclude',91650015,'Exclude',91800718,'Exclude',91800727,'Exclude',918
00728,'Exclude',91800729,'Exclude',91800733,'Exclude',94620320,'Exclu
de',94620380,'Exclude',94620393,'Exclude',94620394,'Exclude',94620395
,'Exclude',94620400,'Exclude',94620402,'Exclude',94620403,'Exclude',9
4801118,'Exclude',94801139,'Exclude',94801148,'Exclude',94801153,'Exc
lude',94801156,'Exclude',94801163,'Exclude',94801164,'Exclude',948011
74,'Exclude',94801175,'Exclude',94801177,'Exclude',94801178,'Exclude'
,94801184,'Exclude',94801185,'Exclude',94801192,'Exclude',94940009,'E
xclude',99300565,'Exclude',99920099,'Exclude',99920101,'Exclude',9992
0103,'Exclude',99920105,'Exclude','NULL') as
C_1,NVL(o310689.SHIPPED_QUANTITY,0)-NVL(o310689.RMA_RECEIVED_QUANTITY
,0) as C_2,o310689.ORDER_TYPE as E310693,o310689.ORDERED_DATE as
E310694,o310689.ORDER_NUMBER as E310695,o310689.ITEM_BRAND as
E310696,o310689.ITEM_CODE as E310701,o310689.ORDERED_QUANTITY as
E310702,o310689.SHIPPED_QUANTITY as E310703,o310689.RMA_QUANTITY as
E310704,o310689.RMA_RECEIVED_QUANTITY as E310705,o310689.UNIT_COST as
E310706,o310689.DEALER_NAME as E310707,o310689.AUTHORIZED_BY_EMPNO as
E310708,o310689.AUTHORIZED_BY_NAME as E310709,o310689.RETURN_DAYS as
E310710,o310689.REMARKS as E310711,o310689.SHIPPING_INSTRUCTIONS as
E310712,o310689.DELIVERY_ORG as E310715,o310689.ITEM_DESCRIPTION as
E310719,o310689.ORDER_LINE_STATUS as
E310884,o310689.SOURCE_DOCUMENT_REF as E333596
FROM ( select upper(xos1.ORDER_TYPE) ORDER_TYPE
,xos1.ORDERED_DATE
,xos1.ORDER_NUMBER
,xos1.ORDER_LINE_STATUS
,xos1.ITEM_BRAND
,xos1.ITEM_GROUP
,xos1.ITEM_SUB_GROUP
,xos1.ITEM_TYPE
,xos1.ITEM_SUB_TYPE
,xos1.ITEM_CODE
,xos1.ITEM_DESCRIPTION
,xos1.ORDERED_QUANTITY
, -1*(select sum(mmts.PRIMARY_QUANTITY) from
mtl_material_transactions mmts where
mmts.TRX_SOURCE_LINE_ID=xos1.LINE_ID and
mmts.TRANSACTION_TYPE_ID=33)SHIPPED_QUANTITY
,xos1.UNIT_COST
,xos1.HD_CUST_NAME dealer_name
,xos1.HD_CUST_ADDR authorized_by_empno
,(select full_name from per_all_people_f where
employee_number=xos1.HD_CUST_ADDR) authorized_by_name
,xos1.HD_CUST_MOBNO return_days
,xos1.HD_CUST_CONTACT remarks
,xos1.SHIPPING_INSTRUCTIONS
,xos1.ORGANIZATION_CODE delivery_org
,xos1.SOURCE_DOCUMENT_REF
,xos2.RMA_quantity
,xos2.RMA_received_quantity
from XXEROS_ONT_SALESORDER_V xos1,(select
xos3.REFERENCE_HEADER_ID,xos3.REFERENCE_LINE_ID,sum(abs(xos3.ORDERED_
QUANTITY)) RMA_quantity
,sum(abs(xos3.SHIPPED_QUANTITY)) RMA_received_quantity from
XXEROS_ONT_SALESORDER_V xos3
where abs(nvl(xos3.SHIPPED_QUANTITY,0))>0
group by xos3.REFERENCE_HEADER_ID,xos3.REFERENCE_LINE_ID) xos2
where xos1.HEADER_ID=xos2.REFERENCE_HEADER_ID (+)
and xos1.LINE_ID=xos2.REFERENCE_LINE_ID (+)
and (upper(xos1.ORDER_TYPE) like ('%ISSUE TO DEALER%')
or upper(xos1.ORDER_TYPE) like ('%ISSUE TO SERVICE CENTER%')
or upper(xos1.ORDER_TYPE) like ('%ISSUE TO SC%')
or upper(xos1.ORDER_TYPE) like ('%MATERIAL ISSUE%')
or upper(xos1.ORDER_TYPE) like ('%WAREHOUSE ISSUE%'))
) o310689
WHERE (TRUNC(o310689.ORDERED_DATE) <=
TO_DATE('20110321000000','YYYYMMDDHH24MISS'))
AND (o310689.ITEM_CODE LIKE '%%')
AND (o310689.ORDER_TYPE LIKE '%ISSUE TO DEALER%')
AND (NVL(o310689.SHIPPED_QUANTITY,0) <>
NVL(o310689.RMA_RECEIVED_QUANTITY,0))
ORDER BY o310689.ORDERED_DATE ASC , o310689.ORDER_NUMBER ASC ,
o310689.DELIVERY_ORG ASC
RECOMMENDATION 2: SQL Tuning, 17% benefit (3160 seconds)
ACTION: Tune the PL/SQL block with SQL_ID "d1swc9auhtxwd". Refer to the
"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide
and Reference"
RELEVANT OBJECT: SQL statement with SQL_ID d1swc9auhtxwd
BEGIN WF_ENGINE.BACKGROUNDCONCURRENT(:errbuf,:rc,:A0,:A1,:A2,:A3,:A4,
:A5); END;
RATIONALE: SQL statement with SQL_ID "d1swc9auhtxwd" was executed 1
times and had an average elapsed time of 3166 seconds.
RECOMMENDATION 3: SQL Tuning, 17% benefit (3101 seconds)
ACTION: Tune the PL/SQL block with SQL_ID "gksvm8wmzk8w0". Refer to the
"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide
and Reference"
RELEVANT OBJECT: SQL statement with SQL_ID gksvm8wmzk8w0
begin OE_INVOICE_WF.INVOICE_INTERFACE (:v1, :v2, :v3, :v4, :v5); end;
RATIONALE: SQL statement with SQL_ID "gksvm8wmzk8w0" was executed 461
times and had an average elapsed time of 6.7 seconds.
RECOMMENDATION 4: SQL Tuning, 15% benefit (2863 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"67uwuf6a7a657".
RELEVANT OBJECT: SQL statement with SQL_ID 67uwuf6a7a657 and
PLAN_HASH 3622377863
SELECT COUNT(1) FROM RA_CUSTOMER_TRX_LINES_ALL RCTL WHERE
RCTL.INTERFACE_LINE_CONTEXT = 'ORDER ENTRY' AND RCTL.LINE_TYPE =
'LINE' AND RCTL.INTERFACE_LINE_ATTRIBUTE6 = TO_CHAR(:B2 ) AND
RCTL.SALES_ORDER = :B1 AND RCTL.SALES_ORDER_LINE IS NOT NULL
RATIONALE: SQL statement with SQL_ID "67uwuf6a7a657" was executed 462
times and had an average elapsed time of 4.3 seconds.
RECOMMENDATION 5: SQL Tuning, 10% benefit (1867 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"9kzwsazsktuzv".
RELEVANT OBJECT: SQL statement with SQL_ID 9kzwsazsktuzv and
PLAN_HASH 3342766736
SELECT end_time, status FROM v$rman_backup_job_details WHERE end_time
= (select max(end_time) from v$rman_backup_job_details)
ACTION: Investigate the SQL statement with SQL_ID "9kzwsazsktuzv" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 9kzwsazsktuzv and
PLAN_HASH 3342766736
SELECT end_time, status FROM v$rman_backup_job_details WHERE end_time
= (select max(end_time) from v$rman_backup_job_details)
RATIONALE: SQL statement with SQL_ID "9kzwsazsktuzv" was executed 28
times and had an average elapsed time of 64 seconds.
Thanks
FINDING 3: 38% impact (7137 seconds)
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
HI,
ADDM Report-- plz advice ..
RECOMMENDATION 1: SQL Tuning, 25% benefit (4640 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"8v8h41b8xypnr".
RELEVANT OBJECT: SQL statement with SQL_ID 8v8h41b8xypnr and
PLAN_HASH 3229043654
SELECT /*+ NOREWRITE */
DECODE(o310689.ORDER_NUMBER,2020090010,'Exclude',2020090011,'Exclude'
,2010090002,'Exclude',2020090012,'Exclude',2020090016,'Exclude',20100
90006,'Exclude',2010090007,'Exclude',2010090009,'Exclude',2020090032,
'Exclude',2010090015,'Exclude',2010090019,'Exclude',2020090037,'Exclu
de',2020090039,'Exclude',2020090040,'Exclude',2010090026,'Exclude',20
20090046,'Exclude',2010090027,'Exclude',2010090028,'Exclude',20200900
51,'Exclude',2020090052,'Exclude',2020090060,'Exclude',2020090062,'Ex
clude',2010090010,'Exclude',2020090036,'Exclude',2020090038,'Exclude'
,2020090045,'Exclude',2020090058,'Exclude',2010090033,'Exclude',946,'
Exclude',91650015,'Exclude',91800718,'Exclude',91800727,'Exclude',918
00728,'Exclude',91800729,'Exclude',91800733,'Exclude',94620320,'Exclu
de',94620380,'Exclude',94620393,'Exclude',94620394,'Exclude',94620395
,'Exclude',94620400,'Exclude',94620402,'Exclude',94620403,'Exclude',9
4801118,'Exclude',94801139,'Exclude',94801148,'Exclude',94801153,'Exc
lude',94801156,'Exclude',94801163,'Exclude',94801164,'Exclude',948011
74,'Exclude',94801175,'Exclude',94801177,'Exclude',94801178,'Exclude'
,94801184,'Exclude',94801185,'Exclude',94801192,'Exclude',94940009,'E
xclude',99300565,'Exclude',99920099,'Exclude',99920101,'Exclude',9992
0103,'Exclude',99920105,'Exclude','NULL') as
C_1,NVL(o310689.SHIPPED_QUANTITY,0)-NVL(o310689.RMA_RECEIVED_QUANTITY
,0) as C_2,o310689.ORDER_TYPE as E310693,o310689.ORDERED_DATE as
E310694,o310689.ORDER_NUMBER as E310695,o310689.ITEM_BRAND as
E310696,o310689.ITEM_CODE as E310701,o310689.ORDERED_QUANTITY as
E310702,o310689.SHIPPED_QUANTITY as E310703,o310689.RMA_QUANTITY as
E310704,o310689.RMA_RECEIVED_QUANTITY as E310705,o310689.UNIT_COST as
E310706,o310689.DEALER_NAME as E310707,o310689.AUTHORIZED_BY_EMPNO as
E310708,o310689.AUTHORIZED_BY_NAME as E310709,o310689.RETURN_DAYS as
E310710,o310689.REMARKS as E310711,o310689.SHIPPING_INSTRUCTIONS as
E310712,o310689.DELIVERY_ORG as E310715,o310689.ITEM_DESCRIPTION as
E310719,o310689.ORDER_LINE_STATUS as
E310884,o310689.SOURCE_DOCUMENT_REF as E333596
FROM ( select upper(xos1.ORDER_TYPE) ORDER_TYPE
,xos1.ORDERED_DATE
,xos1.ORDER_NUMBER
,xos1.ORDER_LINE_STATUS
,xos1.ITEM_BRAND
,xos1.ITEM_GROUP
,xos1.ITEM_SUB_GROUP
,xos1.ITEM_TYPE
,xos1.ITEM_SUB_TYPE
,xos1.ITEM_CODE
,xos1.ITEM_DESCRIPTION
,xos1.ORDERED_QUANTITY
, -1*(select sum(mmts.PRIMARY_QUANTITY) from
mtl_material_transactions mmts where
mmts.TRX_SOURCE_LINE_ID=xos1.LINE_ID and
mmts.TRANSACTION_TYPE_ID=33)SHIPPED_QUANTITY
,xos1.UNIT_COST
,xos1.HD_CUST_NAME dealer_name
,xos1.HD_CUST_ADDR authorized_by_empno
,(select full_name from per_all_people_f where
employee_number=xos1.HD_CUST_ADDR) authorized_by_name
,xos1.HD_CUST_MOBNO return_days
,xos1.HD_CUST_CONTACT remarks
,xos1.SHIPPING_INSTRUCTIONS
,xos1.ORGANIZATION_CODE delivery_org
,xos1.SOURCE_DOCUMENT_REF
,xos2.RMA_quantity
,xos2.RMA_received_quantity
from XXEROS_ONT_SALESORDER_V xos1,(select
xos3.REFERENCE_HEADER_ID,xos3.REFERENCE_LINE_ID,sum(abs(xos3.ORDERED_
QUANTITY)) RMA_quantity
,sum(abs(xos3.SHIPPED_QUANTITY)) RMA_received_quantity from
XXEROS_ONT_SALESORDER_V xos3
where abs(nvl(xos3.SHIPPED_QUANTITY,0))>0
group by xos3.REFERENCE_HEADER_ID,xos3.REFERENCE_LINE_ID) xos2
where xos1.HEADER_ID=xos2.REFERENCE_HEADER_ID (+)
and xos1.LINE_ID=xos2.REFERENCE_LINE_ID (+)
and (upper(xos1.ORDER_TYPE) like ('%ISSUE TO DEALER%')
or upper(xos1.ORDER_TYPE) like ('%ISSUE TO SERVICE CENTER%')
or upper(xos1.ORDER_TYPE) like ('%ISSUE TO SC%')
or upper(xos1.ORDER_TYPE) like ('%MATERIAL ISSUE%')
or upper(xos1.ORDER_TYPE) like ('%WAREHOUSE ISSUE%'))
) o310689
WHERE (TRUNC(o310689.ORDERED_DATE) <=
TO_DATE('20110321000000','YYYYMMDDHH24MISS'))
AND (o310689.ITEM_CODE LIKE '%%')
AND (o310689.ORDER_TYPE LIKE '%ISSUE TO DEALER%')
AND (NVL(o310689.SHIPPED_QUANTITY,0) <>
NVL(o310689.RMA_RECEIVED_QUANTITY,0))
ORDER BY o310689.ORDERED_DATE ASC , o310689.ORDER_NUMBER ASC ,
o310689.DELIVERY_ORG ASC
RECOMMENDATION 2: SQL Tuning, 17% benefit (3071 seconds)
ACTION: Tune the PL/SQL block with SQL_ID "gksvm8wmzk8w0". Refer to the
"Tuning PL/SQL Applications" chapter of Oracle's "PL/SQL User's Guide
and Reference"
RELEVANT OBJECT: SQL statement with SQL_ID gksvm8wmzk8w0
begin OE_INVOICE_WF.INVOICE_INTERFACE (:v1, :v2, :v3, :v4, :v5); end;
RATIONALE: SQL statement with SQL_ID "gksvm8wmzk8w0" was executed 461
times and had an average elapsed time of 6.7 seconds.
RATIONALE: Average CPU used per execution was 6.6 seconds.
RECOMMENDATION 3: SQL Tuning, 10% benefit (1867 seconds)
ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
"9kzwsazsktuzv".
RELEVANT OBJECT: SQL statement with SQL_ID 9kzwsazsktuzv and
PLAN_HASH 3342766736
SELECT end_time, status FROM v$rman_backup_job_details WHERE end_time
= (select max(end_time) from v$rman_backup_job_details)
ACTION: Investigate the SQL statement with SQL_ID "9kzwsazsktuzv" for
possible performance improvements.
RELEVANT OBJECT: SQL statement with SQL_ID 9kzwsazsktuzv and
PLAN_HASH 3342766736
SELECT end_time, status FROM v$rman_backup_job_details WHERE end_time
= (select max(end_time) from v$rman_backup_job_details)
RATIONALE: SQL statement with SQL_ID "9kzwsazsktuzv" was executed 28
times and had an average elapsed time of 64 seconds.
RATIONALE: Average CPU used per execution was 23 seconds.
FINDING 4: 26% impact (4808 seconds)
Individual database segments responsible for significant user I/O wait were
found.
RECOMMENDATION 1: Segment Tuning, 9.6% benefit (1776 seconds)
ACTION: Investigate application logic involving I/O on TABLE
"ONT.OE_ORDER_LINES_ALL" with object id 41455.
RELEVANT OBJECT: database object with id 41455
RATIONALE: The I/O usage statistics for the object are: 2 full object
scans, 1348462 physical reads, 1574 physical writes and 0 direct
reads.
RATIONALE: The SQL statement with SQL_ID "avs0dw5k4jggq" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID avs0dw5k4jggq
select HLINE_ID from XXCOGNOS_SALES_ORDER_LIST_ALL
RATIONALE: The SQL statement with SQL_ID "cajftann925ju" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID cajftann925ju
INSERT INTO XXCUST.XXWSH_DELIVERY_NOTE ( RECORD_IDENTIFIER ,
ORDER_NUMBER , DELIVERY_ID , SHIP_TO_SITE_USE_ID , DELIVERY_NAME ,
HEADER_ID , DEL_DATE , SALES_CHANNEL_CODE , INVENTORY_ITEM_ID ,
ORDERED_ITEM , ITEM_DESCRIPTION , CUST_PO_NUMBER , SHIP_INS ,
ORDERED_DATE , PRINT_STATUS , DELIVER_NUMBER , PICKED_QUANTITY ,
BALANCE_QTY ) SELECT :b1 , OOH.ORDER_NUMBER , WDA.DELIVERY_ID ,
WDD.SHIP_TO_SITE_USE_ID , WND.NAME , WDD.SOURCE_HEADER_ID , TO_DATE
(WND.ATTRIBUTE12 ) DEL_DATE , OOH.SALES_CHANNEL_CODE ,
WDD.INVENTORY_ITEM_ID , OOL.ORDERED_ITEM , WDD.ITEM_DESCRIPTION ,
OOH.CUST_PO_NUMBER , ' ' || OOH.ATTRIBUTE1
|| '/ ' || OOH.ATTRIBUTE3 || '/ ' || OOH.ATTRIBUTE7 || '/ '
|| OOH.ATTRIBUTE6 || '/ ' || OOH.ATTRIBUTE2 || '/ ' ||
OOH.ATTRIBUTE5 || '/ ' || OOH.SHIPPING_INSTRUCTIONS SHIPINS ,
TRUNC (OOH.ORDERED_DATE ) ORDERED_DATE , WND.ATTRIBUTE14 ,
WND.ATTRIBUTE13 , SUM (WDD.PICKED_QUANTITY) PICKED_QUANTITY , SUM
(WDD.REQUESTED_QUANTITY - WDD.PICKED_QUANTITY ) BALANCE_QTY FROM
OE_ORDER_HEADERS_ALL OOH , OE_ORDER_LINES_ALL OOL ,
WSH_NEW_DELIVERIES WND , WSH_DELIVERY_ASSIGNMENTS WDA ,
WSH_DELIVERY_DETAILS WDD WHERE WND.DELIVERY_ID = WDA.DELIVERY_ID
AND WDA.DELIVERY_DETAIL_ID = WDD.DELIVERY_DETAIL_ID AND
OOH.HEADER_ID = WDD.SOURCE_HEADER_ID AND OOL.LINE_ID =
WDD.SOURCE_LINE_ID AND OOL.HEADER_ID = WDD.SOURCE_HEADER_ID AND
OOH.HEADER_ID = OOL.HEADER_ID AND OOH.ORG_ID = OOL.ORG_ID AND
WDD.SOURCE_CODE = 'OE' AND RELEASED_STATUS IN ( 'C' , 'I' , 'Y' )
AND NVL(OOH.SALES_CHANNEL_CODE , 'DLY_NOTE' ) = 'DLY_NOTE' AND
OOL.SHIP_FROM_ORG_ID = :b2 AND OOH.ORDER_NUMBER BETWEEN NVL(:b3 ,
OOH.ORDER_NUMBER ) AND NVL(:b4 , OOH.ORDER_NUMBER ) AND
WND.DELIVERY_ID IN (SELECT DELIVERY_ID FROM WSH_TRIP_STOPS STP ,
WSH_DELIVERY_LEGS LEG , WSH_TRIPS WT WHERE LEG.PICK_UP_STOP_ID =
STP.STOP_ID AND STP.TRIP_ID = WT.TRIP_ID AND WT.TRIP_ID = NVL(:b5
, WT.TRIP_ID ) ) AND WND.ATTRIBUTE14 IS NULL GROUP BY
OOH.ORDER_NUMBER , WDA.DELIVERY_ID , WDD.SHIP_TO_SITE_USE_ID ,
WND.NAME , WDD.SOURCE_HEADER_ID , WND.ATTRIBUTE12 ,
OOH.SALES_CHANNEL_CODE , WDD.INVENTORY_ITEM_ID , OOL.ORDERED_ITEM ,
WDD.ITEM_DESCRIPTION , OOH.CUST_PO_NUMBER , '
' || OOH.ATTRIBUTE1 || '/ ' || OOH.ATTRIBUTE3 || '/ ' ||
OOH.ATTRIBUTE7 || '/ ' || OOH.ATTRIBUTE6 || '/ ' ||
OOH.ATTRIBUTE2 || '/ ' || OOH.ATTRIBUTE5 || '/ ' ||
OOH.SHIPPING_INSTRUCTIONS , TRUNC (OOH.ORDERED_DATE ) ,
WND.ATTRIBUTE14 , WND.ATTRIBUTE13
RATIONALE: The SQL statement with SQL_ID "4m39p9a78z133" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 4m39p9a78z133
SELECT OOD.OPERATING_UNIT ORG_ID, TRUNC (OOLV.CREATION_DATE)
CREATED_DT, TRUNC (OOLV.LAST_UPDATE_DATE) UPDATED_DT, ABS
(MMT.PRIMARY_QUANTITY) QTY, MMT.CREATED_BY CREATED_BY,
MMT.LAST_UPDATED_BY UPDATED_BY, MMT.INVENTORY_ITEM_ID ITEM_NAME,
MMT.TRANSACTION_UOM UOM, MMT.ACTUAL_COST COST1, 6717 DR_ACCOUNT_ID,
MPS.MATERIAL_ACCOUNT CR_ACCOUNT_ID , TRUNC (MMT.TRANSACTION_DATE)
TXN_DATE, MMT.SOURCE_LINE_ID LINE_ID, OOHA.ATTRIBUTE1 PRJ_NO, 'COST'
TASK1, DECODE (OOHA.ORDER_TYPE_ID, 1042, 'Equipment', 1201,
'Material', NULL ) EXP_TYPE, MMT.SOURCE_LINE_ID ORIG_TRANS_REF,
OOLV.LINE_NUMBER REQUEST_NUMBER, NULL UNMATCHED_NEGATIVE_TXN_FLAG,
MMT.DISTRIBUTION_ACCOUNT_ID, MMT.TRANSACTION_ID FROM
OE_ORDER_LINES_ALL OOLV, OE_ORDER_HEADERS_ALL OOHA,
MTL_MATERIAL_TRANSACTIONS MMT, MTL_TRANSACTION_TYPES MTT,
ORG_ORGANIZATION_DEFINITIONS OOD, MTL_PARAMETERS MPS WHERE
OOLV.LINE_ID = MMT.TRX_SOURCE_LINE_ID AND OOLV.HEADER_ID =
OOHA.HEADER_ID AND MMT.TRANSACTION_TYPE_ID = MTT.TRANSACTION_TYPE_ID
AND OOHA.CONTEXT = 'Project Transfer' AND OOHA.ATTRIBUTE1 IS NOT NULL
AND NVL (MMT.ATTRIBUTE15, 'X') <> 'TRANSFERRED_TO_PROJECT' AND
MTT.TRANSACTION_TYPE_ID = 33 AND OOD.ORGANIZATION_ID =
MPS.ORGANIZATION_ID AND MMT.ORGANIZATION_ID = OOD.ORGANIZATION_ID AND
OOHA.ORDER_TYPE_ID IN (1042, 1201) AND MMT.COSTED_FLAG IS NULL UNION
ALL SELECT OOD.OPERATING_UNIT ORG_ID, TRUNC (OOLV.CREATION_DATE)
CREATED_DT, TRUNC (OOLV.LAST_UPDATE_DATE) UPDATED_DT,
(MMT.TRANSACTION_QUANTITY * -1 ) QTY, MMT.CREATED_BY CREATED_BY,
MMT.LAST_UPDATED_BY UPDATED_BY, MMT.INVENTORY_ITEM_ID ITEM_NAME,
MMT.TRANSACTION_UOM UOM, MMT.ACTUAL_COST COST1, MPS.MATERIAL_ACCOUNT
DR_ACCOUNT_ID, 6717 CR_ACCOUNT_ID , TRUNC (MMT.TRANSACTION_DATE)
TXN_DATE, MMT.SOURCE_LINE_ID LINE_ID, OOHA.ATTRIBUTE1 PRJ_NO, 'COST'
TASK1, DECODE (OOHA.ORDER_TYPE_ID, 1042, 'Equipment', 1201,
'Material', 1239, 'Equipment', 1240, 'Material', NULL ) EXP_TYPE,
MMT.SOURCE_LINE_ID ORIG_TRANS_REF, OOLV.LINE_NUMBER REQUEST_NUMBER,
'Y' UNMATCHED_NEGATIVE_TXN_FLAG, MMT.DISTRIBUTION_ACCOUNT_ID,
MMT.TRANSACTION_ID FROM OE_ORDER_LINES_ALL OOLV, OE_ORDER_LINES_ALL
OOLR, OE_ORDER_HEADERS_ALL OOHA, MTL_MATERIAL_TRANSACTIONS MMT,
MTL_TRANSACTION_TYPES MTT, ORG_ORGANIZATION_DEFINITIONS OOD,
MTL_PARAMETERS MPS WHERE MMT.TRX_SOURCE_LINE_ID = OOLV.LINE_ID AND
OOLV.HEADER_ID = OOHA.HEADER_ID AND MMT.TRANSACTION_TYPE_ID =
MTT.TRANSACTION_TYPE_ID AND OOHA.CONTEXT = 'Project Transfer' AND
OOHA.ATTRIBUTE1 IS NOT NULL AND NVL (MMT.ATTRIBUTE15, 'X') <>
'TRANSFERRED_TO_PROJECT' AND MTT.TRANSACTION_TYPE_ID = 15 AND
OOD.ORGANIZATION_ID = MPS.ORGANIZATION_ID AND MMT.ORGANIZATION_ID =
OOD.ORGANIZATION_ID AND OOLV.REFERENCE_HEADER_ID = OOLR.HEADER_ID AND
OOLV.REFERENCE_LINE_ID = OOLR.LINE_ID AND OOHA.ORDER_TYPE_ID IN
(1239, 1240) AND MMT.COSTED_FLAG IS NULL
RATIONALE: The SQL statement with SQL_ID "8ms1bza9t8vww" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 8ms1bza9t8vww
select TRX_LINE from XXCOGNOS_SO_INV_NEW_V
RECOMMENDATION 2: Segment Tuning, 4.9% benefit (903 seconds)
ACTION: Run "Segment Advisor" on TABLE "AR.RA_CUSTOMER_TRX_LINES_ALL"
with object id 29149.
RELEVANT OBJECT: database object with id 29149
ACTION: Investigate application logic involving I/O on TABLE
"AR.RA_CUSTOMER_TRX_LINES_ALL" with object id 29149.
RELEVANT OBJECT: database object with id 29149
RATIONALE: The I/O usage statistics for the object are: 486 full object
scans, 64008942 physical reads, 63 physical writes and 0 direct
reads.
RATIONALE: The SQL statement with SQL_ID "gksvm8wmzk8w0" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID gksvm8wmzk8w0
begin OE_INVOICE_WF.INVOICE_INTERFACE (:v1, :v2, :v3, :v4, :v5); end;
RECOMMENDATION 3: Segment Tuning, 4.5% benefit (831 seconds)
ACTION: Investigate application logic involving I/O on TABLE
"INV.MTL_MATERIAL_TRANSACTIONS" with object id 38612.
RELEVANT OBJECT: database object with id 38612
RATIONALE: The I/O usage statistics for the object are: 0 full object
scans, 71252528 physical reads, 117 physical writes and 0 direct
reads.
RATIONALE: The SQL statement with SQL_ID "8v8h41b8xypnr" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 8v8h41b8xypnr
SELECT /*+ NOREWRITE */
DECODE(o310689.ORDER_NUMBER,2020090010,'Exclude',2020090011,'Exclude'
,2010090002,'Exclude',2020090012,'Exclude',2020090016,'Exclude',20100
90006,'Exclude',2010090007,'Exclude',2010090009,'Exclude',2020090032,
'Exclude',2010090015,'Exclude',2010090019,'Exclude',2020090037,'Exclu
de',2020090039,'Exclude',2020090040,'Exclude',2010090026,'Exclude',20
20090046,'Exclude',2010090027,'Exclude',2010090028,'Exclude',20200900
51,'Exclude',2020090052,'Exclude',2020090060,'Exclude',2020090062,'Ex
clude',2010090010,'Exclude',2020090036,'Exclude',2020090038,'Exclude'
,2020090045,'Exclude',2020090058,'Exclude',2010090033,'Exclude',946,'
Exclude',91650015,'Exclude',91800718,'Exclude',91800727,'Exclude',918
00728,'Exclude',91800729,'Exclude',91800733,'Exclude',94620320,'Exclu
de',94620380,'Exclude',94620393,'Exclude',94620394,'Exclude',94620395
,'Exclude',94620400,'Exclude',94620402,'Exclude',94620403,'Exclude',9
4801118,'Exclude',94801139,'Exclude',94801148,'Exclude',94801153,'Exc
lude',94801156,'Exclude',94801163,'Exclude',94801164,'Exclude',948011
74,'Exclude',94801175,'Exclude',94801177,'Exclude',94801178,'Exclude'
,94801184,'Exclude',94801185,'Exclude',94801192,'Exclude',94940009,'E
xclude',99300565,'Exclude',99920099,'Exclude',99920101,'Exclude',9992
0103,'Exclude',99920105,'Exclude','NULL') as
C_1,NVL(o310689.SHIPPED_QUANTITY,0)-NVL(o310689.RMA_RECEIVED_QUANTITY
,0) as C_2,o310689.ORDER_TYPE as E310693,o310689.ORDERED_DATE as
E310694,o310689.ORDER_NUMBER as E310695,o310689.ITEM_BRAND as
E310696,o310689.ITEM_CODE as E310701,o310689.ORDERED_QUANTITY as
E310702,o310689.SHIPPED_QUANTITY as E310703,o310689.RMA_QUANTITY as
E310704,o310689.RMA_RECEIVED_QUANTITY as E310705,o310689.UNIT_COST as
E310706,o310689.DEALER_NAME as E310707,o310689.AUTHORIZED_BY_EMPNO as
E310708,o310689.AUTHORIZED_BY_NAME as E310709,o310689.RETURN_DAYS as
E310710,o310689.REMARKS as E310711,o310689.SHIPPING_INSTRUCTIONS as
E310712,o310689.DELIVERY_ORG as E310715,o310689.ITEM_DESCRIPTION as
E310719,o310689.ORDER_LINE_STATUS as
E310884,o310689.SOURCE_DOCUMENT_REF as E333596
FROM ( select upper(xos1.ORDER_TYPE) ORDER_TYPE
,xos1.ORDERED_DATE
,xos1.ORDER_NUMBER
,xos1.ORDER_LINE_STATUS
,xos1.ITEM_BRAND
,xos1.ITEM_GROUP
,xos1.ITEM_SUB_GROUP
,xos1.ITEM_TYPE
,xos1.ITEM_SUB_TYPE
,xos1.ITEM_CODE
,xos1.ITEM_DESCRIPTION
,xos1.ORDERED_QUANTITY
, -1*(select sum(mmts.PRIMARY_QUANTITY) from
mtl_material_transactions mmts where
mmts.TRX_SOURCE_LINE_ID=xos1.LINE_ID and
mmts.TRANSACTION_TYPE_ID=33)SHIPPED_QUANTITY
,xos1.UNIT_COST
,xos1.HD_CUST_NAME dealer_name
,xos1.HD_CUST_ADDR authorized_by_empno
,(select full_name from per_all_people_f where
employee_number=xos1.HD_CUST_ADDR) authorized_by_name
,xos1.HD_CUST_MOBNO return_days
,xos1.HD_CUST_CONTACT remarks
,xos1.SHIPPING_INSTRUCTIONS
,xos1.ORGANIZATION_CODE delivery_org
,xos1.SOURCE_DOCUMENT_REF
,xos2.RMA_quantity
,xos2.RMA_received_quantity
from XXEROS_ONT_SALESORDER_V xos1,(select
xos3.REFERENCE_HEADER_ID,xos3.REFERENCE_LINE_ID,sum(abs(xos3.ORDERED_
QUANTITY)) RMA_quantity
,sum(abs(xos3.SHIPPED_QUANTITY)) RMA_received_quantity from
XXEROS_ONT_SALESORDER_V xos3
where abs(nvl(xos3.SHIPPED_QUANTITY,0))>0
group by xos3.REFERENCE_HEADER_ID,xos3.REFERENCE_LINE_ID) xos2
where xos1.HEADER_ID=xos2.REFERENCE_HEADER_ID (+)
and xos1.LINE_ID=xos2.REFERENCE_LINE_ID (+)
and (upper(xos1.ORDER_TYPE) like ('%ISSUE TO DEALER%')
or upper(xos1.ORDER_TYPE) like ('%ISSUE TO SERVICE CENTER%')
or upper(xos1.ORDER_TYPE) like ('%ISSUE TO SC%')
or upper(xos1.ORDER_TYPE) like ('%MATERIAL ISSUE%')
or upper(xos1.ORDER_TYPE) like ('%WAREHOUSE ISSUE%'))
) o310689
WHERE (TRUNC(o310689.ORDERED_DATE) <=
TO_DATE('20110321000000','YYYYMMDDHH24MISS'))
AND (o310689.ITEM_CODE LIKE '%%')
AND (o310689.ORDER_TYPE LIKE '%ISSUE TO DEALER%')
AND (NVL(o310689.SHIPPED_QUANTITY,0) <>
NVL(o310689.RMA_RECEIVED_QUANTITY,0))
ORDER BY o310689.ORDERED_DATE ASC , o310689.ORDER_NUMBER ASC ,
o310689.DELIVERY_ORG ASC
RECOMMENDATION 4: Segment Tuning, 4.1% benefit (768 seconds)
ACTION: Run "Segment Advisor" on TABLE "AR.RA_INTERFACE_LINES_ALL" with
object id 28266.
RELEVANT OBJECT: database object with id 28266
ACTION: Investigate application logic involving I/O on TABLE
"AR.RA_INTERFACE_LINES_ALL" with object id 28266.
RELEVANT OBJECT: database object with id 28266
RATIONALE: The I/O usage statistics for the object are: 49184 full
object scans, 78734476 physical reads, 610 physical writes and
36573343 direct reads.
RATIONALE: The SQL statement with SQL_ID "gksvm8wmzk8w0" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID gksvm8wmzk8w0
begin OE_INVOICE_WF.INVOICE_INTERFACE (:v1, :v2, :v3, :v4, :v5); end;
RECOMMENDATION 5: Segment Tuning, 2.9% benefit (530 seconds)
ACTION: Investigate application logic involving I/O on TABLE
"INV.MTL_SYSTEM_ITEMS_B" with object id 38489.
RELEVANT OBJECT: database object with id 38489
RATIONALE: The I/O usage statistics for the object are: 4 full object
scans, 1288002 physical reads, 451 physical writes and 0 direct
reads.
RATIONALE: The SQL statement with SQL_ID "abwz9n6zhfau7" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID abwz9n6zhfau7
SELECT DISTINCT /*+ NOREWRITE */
NVL(o253810.ATR,0)-NVL(o253810.UNRES_QTY,0) as C_1,o253810.WAREHOUSE
as E253811,o253810.BRAND as E253812,o253810.GROUPCODE as
E253813,o253810.SUBGROUP as E253814,o253810.TYPE as
E253815,o253810.SUBTYPE as E253816,o253810.ITEM_CODE as
E253817,o253810.ITEM_NAME as E253818,o253810.UNRES_QTY as
E253819,o253810.STOCK as E253820,o253810.ATR as
E253821,o253810.RESERVED as E253822,o253810.TOTAL as E253823
FROM APPS.XX_STOCK_V o253810
WHERE (o253810.ITEM_CODE LIKE '%%')
ORDER BY o253810.ITEM_CODE ASC
RATIONALE: The SQL statement with SQL_ID "5yvpw0g5cusff" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 5yvpw0g5cusff
SELECT DISTINCT /*+ NOREWRITE */
NVL(o253810.ATR,0)-NVL(o253810.UNRES_QTY,0) as C_1,o253810.WAREHOUSE
as E253811,o253810.BRAND as E253812,o253810.GROUPCODE as
E253813,o253810.SUBGROUP as E253814,o253810.ITEM_CODE as
E253817,o253810.ITEM_NAME as E253818,o253810.UNRES_QTY as
E253819,o253810.STOCK as E253820,o253810.ATR as
E253821,o253810.RESERVED as E253822,o253810.TOTAL as
E253823,o255805.PRICE as E255816
FROM APPS.XX_STOCK_V o253810,
( SELECT CUSTOMER_ITEM_ID,product_attr_val_disp
ITEM_CODE,PRODUCT_UOM_CODE,PRIMARY_UOM_FLAG,BREAK_UOM_CODE,BREAK_UOM_
CONTEXT,OPERAND PRICE,START_DATE_ACTIVE,
END_DATE_ACTIVE,MODIFIER_LEVEL_CODE,PRODUCT_PRECEDENCE,COMMENTS,REVIS
ION,REVISION_DATE,REVISION_REASON_CODE,ROW_ID,PRODUCT_ATTRIBUTE_CONTE
XT,
PRODUCT_ATTRIBUTE,BREAK_UOM_ATTRIBUTE,PRODUCT_ATTR_VALUE,INCOMPATIBIL
ITY_GRP_CODE,LIST_LINE_NO,PRICING_GROUP_SEQUENCE,ACCRUAL_FLAG,PRICING
PHASEID,
AUTOMATIC_FLAG,PRICE_BY_FORMULA_ID,INVENTORY_ITEM_ID,ORGANIZATION_ID,
RELATED_ITEM_ID,RELATIONSHIP_TYPE_ID,SUBSTITUTION_CONTEXT,SUBSTITUTIO
N_ATTRIBUTE,
SUBSTITUTION_VALUE,CREATION_DATE,CREATED_BY,LAST_UPDATE_DATE,LAST_UPD
ATED_BY,LAST_UPDATE_LOGIN,PROGRAM_APPLICATION_ID,PROGRAM_ID,PROGRAM_U
PDATE_DATE,
REQUEST_ID,LIST_HEADER_ID,LIST_LINE_ID,PRICE_BREAK_TYPE_CODE,NUMBER_E
FFECTIVE_PERIODS,EFFECTIVE_PERIOD_UOM,OVERRIDE_FLAG,PRINT_ON_INVOICE_
FLAG,
REBATE_TRANSACTION_TYPE_CODE,BASE_QTY,BASE_UOM_CODE,ACCRUAL_QTY,ACCRU
AL_UOM_CODE,ESTIM_ACCRUAL_RATE,GENERATE_USING_FORMULA_ID,REPRICE_FLAG
,CONTEXT,
ATTRIBUTE1,ATTRIBUTE2,ATTRIBUTE3,ATTRIBUTE4,ATTRIBUTE5,ATTRIBUTE6,ATT
RIBUTE7,ATTRIBUTE8,ATTRIBUTE9,ATTRIBUTE10,ATTRIBUTE11,ATTRIBUTE12,ATT
RIBUTE13,
ATTRIBUTE14,ATTRIBUTE15,PRICING_ATTRIBUTE_ID,PRICING_ATTRIBUTE_CONTEX
T,PRICING_ATTRIBUTE,PRICING_ATTR_VALUE_FROM,PRICING_ATTR_VALUE_TO,PRO
DUCT_ID,
LIST_PRICE,PERCENT_PRICE,ARITHMETIC_OPERATOR,LIST_LINE_TYPE_CODE,prod
uct_attribute_datatype,pricing_attribute_datatype,comparison_operator
_code,
ATTR_CONTEXT,ATTR_ATTRIBUTE1,ATTR_ATTRIBUTE2,ATTR_ATTRIBUTE3,ATTR_ATT
RIBUTE4,ATTR_ATTRIBUTE5,ATTR_ATTRIBUTE6,ATTR_ATTRIBUTE7,ATTR_ATTRIBUT
E8,
ATTR_ATTRIBUTE9,ATTR_ATTRIBUTE10,ATTR_ATTRIBUTE11,ATTR_ATTRIBUTE12,AT
TR_ATTRIBUTE13,ATTR_ATTRIBUTE14,ATTR_ATTRIBUTE15,ATTR_CREATION_DATE,
ATTR_CREATED_BY,ATTR_LAST_UPDATE_DATE,ATTR_LAST_UPDATED_BY,ATTR_LAST_
UPDATE_LOGIN,ATTR_PROGRAM_APPLICATION_ID,ATTR_PROGRAM_ID,ATTR_PROGRAM
UPDATEDATE,
ATTR_REQUEST_ID,PA_LIST_HEADER_ID,CONTINUOUS_PRICE_BREAK_FLAG FROM
qp_list_lines_v WHERE PRODUCT_ATTRIBUTE_CONTEXT = 'ITEM'
AND EXISTS (SELECT '1' FROM MTL_SYSTEM_ITEMS mtl WHERE
product_attr_value = mtl.inventory_item_id AND mtl.organization_id =
(SELECT qp_util.get_item_validation_org FROM Dual)
AND product_attribute= 'PRICING_ATTRIBUTE1' UNION SELECT '1' FROM
dual WHERE product_attribute != 'PRICING_ATTRIBUTE1')
and (LIST_HEADER_ID=6016) and (PA_LIST_HEADER_ID='6016')
) o255805
WHERE ( (o255805.ITEM_CODE = o253810.ITEM_CODE))
AND (o253810.ITEM_CODE LIKE '%%')
AND (o255805.END_DATE_ACTIVE IS NULL )
ORDER BY o253810.ITEM_CODE ASC
RATIONALE: The SQL statement with SQL_ID "8ms1bza9t8vww" spent
significant time waiting for User I/O on the hot object.
RELEVANT OBJECT: SQL statement with SQL_ID 8ms1bza9t8vww
select TRX_LINE from XXCOGNOS_SO_INV_NEW_V
SYMPTOMS THAT LED TO THE FINDING:
SYMPTOM: Wait class "User I/O" was consuming significant database time.
(43% impact [7964 seconds])
Similar Messages
-
Hello,
Dear all i have to ask two question.
1) How can i check if Login page of EBS suite is running fine and opmn,apache status through sql command.
2) System is Slow when all users are connected with R12? How to resolve issue?
Regards,
MerriHi Merri;
1) How can i check if Login page of EBS suite is running fine and opmn,apache status through sql command.You can check by using script $ADMIN_SCRIPTS_HOME, by the way I am sure you will know very shortly If ppl cant logins sytem ;)
2) System is Slow when all users are connected with R12? How to resolve issue?This topic mention here many times here. Basicly you need to define which tier slow db or apps than you can start tuning on hardware or EBS site.
https://forums.oracle.com/forums/search.jspa?threadID=&q=r12+and+performance&objID=c3&dateRange=all&userID=&numResults=30
Regard
Helios -
Hardware Requirements for R12 upgrade
Hi
We are planning to perform R12 upgrade(11.5.10.2 to R12) on our dual node Test servers.
Following is the H/W configurations
Node 1:DB + CCM + Admin
=>Database size is approx.38-40GB,2 CPU's & 2GB RAM
Node 2:Form + Web server
=>2 CPU's & 2GB RAM
Is this a sufficient configuration for R12 upgrade.
Thanks
ShekharIn general, you need to make the best of what you have on hand. If it were me, I would double or triple your RAM especially on your admin/DB tier, unless you only have 2-5 users.
Fast storage will make a huge impact on runtime of the upgrade driver. -
Perform custom validation on invoices created via iSupplier portal in R12
Hello,
It seems that since R12, invoices created on iSupplier portal are no longer loaded via Payables open interface tables (while ASBN's still are). It is nice that they are loaded immediately but now we do not have any way to perform custom validation that we normally do via AP_INTERFACE_WORKFLOW_PKG.do_custom_validation procedure.
Is there any way to modify how iSupplier portal inserts Invoice data into AP tables? In particular we would like to choose specific document category for certain suppliers.
Many thanks in advance,
KamilHi Friends,
Apologies to have put this in SCM-Costing Category. I just posted the same thing in Financials Category.
Please ignore this, if found irrelevant under this category.
Thanks,
AAR -
Oracle EBS R12 performance is very slow...
Our EBS R12 instance performance has become very slow.Users frequently complain of oracle forms taking a long time to open,concurrent taking more than normal time to complete etc.All standard requests like Gather Schema Statistics, Purge Concurrent/Manager Data etc are properly scheduled and complete successfully.Any pointers on how to resolve/diagnose/troubleshoot the slow performance of EBS is urgently needed and will be of much required help.
We have also observed that while starting the EBS database, using addbctl.sh script, the db gets mounted instantly but takes around 3-4 mins to open.We reviewed the alert log file, there are no reported errors as such.
Server Specifications:
Processor:3.0 GHz (Single Processor)
Memory: 16 GB
OS:RHEL 5.2(x86)
Regards,Hi,
Can you find any errors at the OS level? Any space issue or core dump files generated?
What changes have been done recently?
You should find some guidelines about troubleshooting performance in these threads, please refer to the referenced documents.
EBS, performence issue
Re: EBS, performence issue
Oracle Apps Tuning
Re: Oracle Apps Tuning
Regards,
Hussein -
Oracle E-Business Suite R12 ( Performance Monitor )
Dears,
We are having Oracle E-Business Suite R12 Multi-node on HP-UX. And we would like start monitor our ERP system performance, so I would like to hear your suggestions on this matter.Hi,
If I consider implementing OEM in our environment what is except cost from implementing this solution. since we have this version.
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
CORE 11.2.0.2.0 Production
TNS for HPUX: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production -
Gather Schema Statistics improve the performance of the R12 application?
Hi All,
If we run “Gather Schema Statistics” program, it will improve the performance of the R12 application?
Platform Linux and DB version 10.2.0.4.
Thanks & Regards,
TharunHi Tharun,
If we ruer n “Gather Schema Statistics” program, it will improve the performance of the R12 application?
Yes, it will speed up as it ensures to have an up to date statistics.
Please refer notes:
Concurrent Processing - How To Gather Statistics On Oracle Applications Release 11i and/or Release 12 - Concurrent Process,Temp Tables, Manually [ID 419728.1]
How Often Should Gather Schema Statistics Program be Run? [ID 168136.1]
Why Stats Gather?
Stats gathering must be set as a routine job and is recommended to be scheduled. Even though this program is available from the fronted in the form of submitting a concurrent program basically it performs a DB level enhancement and ensures that you have an up to date optimizer statistics.Because the objects in a database can be constantly changing, statistics must be regularly updated so that they accurately describe these database objects.
For indepth understand as to why it should be run, please refer doc:
Managing Optimizer Statistics
Thanks &
Best Regards, -
Known performance issue bugs and patches for R12.1.3
Hi Team,
We have upgraded oracle application from 12.1.1 to 12.1.3.
I wanted to apply the known performance issue bugs and patches for R12.1.3.
Please let me know for any details.
Thanks,Are u currently facing any performance issues on 1213?
Tuning All Layers Of E-Business Suite – Performance Topics
http://www.oracle.com/technetwork/apps-tech/collab2011-tuning-ebusiness-421966.pdf
• Start with Best Practices : (note: 1121043.1)
• SQL Tuning
– Trace files
– SQLT output (note: 215187.1)
– Trace Analyzer (note: 224270.1)
– AWR Report (note: 748642.1)
– AWR SQL Report (awrsqrpt.sql)
– 11g SQL Monitoring
– SQL Tuning Advisor
• PL/SQL Tuning
– Product logs
– PL/SQL Profiler (note: 808005.1)
• Reports Tracing
– note: 111311.1
• Database Tuning
– AWR Report (note: 748642.1)
– ADDM report (note: 250655.1)
– Automated Session History (ASH) Report
– LTOM output (note: 352363.1)
• Forms Tuning
• Forms Tracing (note: 373548.1)
• FRD Log (note: 445166.1)
– Generic note: 438652.1
• Middletier Tuning
– JVM Logs
– JVM Sizing (note: 362851.1)
– JDBC Tuning (note: 278868.1)
• OS
– OSWatcher (note: 301137.1) -
R12 Performance Tuning...
Are there any docs or notes that one can to follow for EBS R12 performance tuning ?
Regards,
RupdiptHi,
Please refer to the following links:
Performance Tuning the Apps Database Layer
http://blogs.oracle.com/schan/newsItems/departments/release12/2007/05/17#a1562
Understanding JDBC Connections From the eBusiness Middle Tier
http://blogs.oracle.com/schan/newsItems/departments/release12/2007/09/20#a2051
Performance Tuning for the E-Business Suite
http://blogs.oracle.com/schan/newsItems/departments/release12/2007/12/11#a2297
The following notes/links provide guidelines for setting up JVMs (Jserv groups/OC4J instances) for online applications in Apps 11i and R12:
Note: 362851.1 - Guidelines to setup the JVM in Apps Ebusiness Suite 11i and R12
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=362851.1
Note: :462550.1 - Generate JVM heap dump in E-Business suite 11i and R12
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=462550.1
Latest JVM Tuning Recommendations for Apps 11i
http://blogs.oracle.com/schan/2007/03/01
Tuning JVMs with Apps 11i
http://blogs.oracle.com/schan/2007/02/16#a1230
Configuring Middle-Tier JVMs for Applications 11i
http://blogs.oracle.com/schan/2006/08/01#a494
For tuning other application components (i.e. CM, initialization parameters, top SQL statements, application tier, ..etc), the following note should be helpful:
Note: 169935.1 - Troubleshooting Oracle Applications Performance Issues
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=169935.1
Note: 244040.1 - Oracle E-Business Suite Recommended Performance Patches
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=244040.1
Note: 744143.1 - Tuning performance on eBusiness suite
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=744143.1
Regards,
Hussein -
Performance Issue with PAY_BALANCE_VALUES_V View in Oracle R12
Dear all ,
We have recently upgraded from 11i(11.5.10.2) to R12(12.1.3). We are facing one Issue with slow performance of the queries where PAY_BALANCE_VALUES_V is used. We have so many reports & logic in Payroll which uses this View.
In 11i this works fine, however in R12 it takes very long time. There are no configuration changes we have done from 11i to R12.
Is there any way to optimize the performance or alternate way to retrieve the Balances Data in Payroll ?
Any heads up would be highly Appreciated.
Thanks,
RaziHi Razi,
The balance related performance issue is written in the following note.
Note:1494344.1 UK Payslip Generation - Self Service Program Takes Much Time To Complete (Performance Issue)
This issue was fixed in HR_PF.B RUP6 or patch:14376786. Did you apply this patch? If not, I suggest you apply it.
Also, HR_PF.B RUP6 has some balance related performance issues.
If you already have applied HR_PF.B RUP6, I suggest you log a SR with SQL trace.
Thanks,
Hideki -
R12 application performance tuning.
Hi,
I have the r12 apps instance which is running in oracle linux 4 update 5 32 bit.
DB-11.1.0.7
Apps-12.1.3
Normally in os level its showing load 20 to 30, so I can't access the application.
Because of this issue the instance is very slow.
Please help me to sove this issue.
--KumarI have the r12 apps instance which is running in oracle linux 4 update 5 32 bit.
R12 requires at least 4 GB of RAM and with 32-bit OS you can't take advantage of utilizing more memory. If you consider migrating to 64-bit OS, then I believe you would notice improvement in performance.
Frequently Asked Questions: Oracle E-Business Suite Support on x86-64 (Doc ID 343917.1) -- 4. What are the benefits of running Oracle E-Business Suite on x86-64?
If this is for personal use, you may try mdtaylor suggestions in this thread -- https://forums.oracle.com/thread/493428
Thanks,
Hussein -
Query Performance AP_INVOICES_ALL vs AP_INVOICES in R12
Hi,
I came across a strange (for me so far) that the query based on the synonym AP_INVOICES is faster than AP_INVOICES_ALL in R12. Please read through.
-- First view
create or replace view XX_AP_TEMP_V4
as
select
AI.INVOICE_AMOUNT INVOICE_AMOUNT,
AI.INVOICE_CURRENCY_CODE INVOICE_CURRENCY_CODE,
AI.INVOICE_DATE INVOICE_DATE,
AI.INVOICE_ID INVOICE_ID,
AI.INVOICE_NUM INVOICE_NUM,
AI.org_id,
AP_INVOICES_PKG.GET_APPROVAL_STATUS (AI.INVOICE_ID,
AI.INVOICE_AMOUNT,
AI.PAYMENT_STATUS_FLAG,
AI.INVOICE_TYPE_LOOKUP_CODE) approval_status
from ap_invoices_all ai
, apps.mo_glob_org_access_tmp mg
where
ai.org_id = mg.organization_id
-- Second view
create or replace view XX_AP_TEMP_V5
as
select
AI.INVOICE_AMOUNT INVOICE_AMOUNT,
AI.INVOICE_CURRENCY_CODE INVOICE_CURRENCY_CODE,
AI.INVOICE_DATE INVOICE_DATE,
AI.INVOICE_ID INVOICE_ID,
AI.INVOICE_NUM INVOICE_NUM,
AI.org_id,
AP_INVOICES_PKG.GET_APPROVAL_STATUS (AI.INVOICE_ID,
AI.INVOICE_AMOUNT,
AI.PAYMENT_STATUS_FLAG,
AI.INVOICE_TYPE_LOOKUP_CODE) approval_status
from ap_invoices ai
, apps.mo_glob_org_access_tmp mg
where
ai.org_id = mg.organization_id
select * from XX_AP_TEMP_V4 where approval_status like '%APPROVE%'; -- takes about 6mins to give first 50 rows
select * from XX_AP_TEMP_V5 where approval_status like '%APPROVE%' -- takes about 10sec to give first 50 rows
Why there is such a difference when we can't create any indexes on Synonym or View??
Thanks,
Pavan.I've read the docs thanks they are very good at helping me understand MOAC but they do not really answer the question.
I am thinking that now that a responsibility can access more than one org that org it is very likely to be a parameter on the report to give users the choice of what org data to report on. If there is a parameter is there a point of using the secure views? Because the report can look at the all table and then be restricted by org_id = &org_id. If this holds then it would be best to report from the all tables rather than the secure views.
So if I was asked to develop a report to show self billing invoices for example - what should I use ap_invoices_all with org_id as a parameter or ap_invoices without the parameter?
Thanks for the help in advance - I'm new in r12 and think this is a bit of fundamental point and it appears to me that both ways can be used but there is probably reasons to adopt one approach over another. -
I use the BI Publisher to generate AP checks. In r12 the entire functionality moved to IBY module (xml change). After modifying the 11i existing template to fit new r12 structure all works fine until I process a check with 600 invoices associated with it. It takes aver 2 hours to get it formatted by the XDO engine. Does anyone experience similar problem?
Jeremy;
No I didn't follow dan step.
- Ask functional team member to create open invoice
- Ask them to run a "quick check"
then using SQLDeveloper or TOAD to get data from
IBY_TRXN_DOCUMENTS table to get the XML file
Make sure u pick max TRXMNID and see some data.
If there is no records in your table then check with functional team again which they have lost the setting.
Another trick if not comfortable using the table is to change Java concurrent program from PDF to XML which you should be able to see the XML file.
HTH
Shaun S.
(Sorry for late response) -
R12 : Perform Product-specific Steps
I have complete R12.1 installation and then upgradation to 12.1.3.
Pls. suggest how can I check whether I have to apply the patches mention in step 4 or not. I am little confused here.
Doc 1080973.1, Step 4Pls. suggest how can I check whether I have to apply the patches mention in step 4 or not. I am little confused here.
Doc 1080973.1, Step 4
Oracle Applications Current Patchset Comparison Utility - patchsets.sh [ID 139684.1]
How to check if certain Oracle Applications product/module is implemented? [ID 443699.1]
Thanks,
Hussein -
Performance issue with XLA tables and GL tables R12
Hi all,
I have one SQL that joins all the XLA tables with GL tables to get invoice related encumbrance data.
My problem is for some reason the SQL is going to GL_LE_LINES first (from explain plane). As
a result my SQL is taking some 25 min to finish.
I am pretty sure if I can manage to force the SQL to use XLA table 1st the SQL will finish in couple of
minutes. I even tried LEADING hint. But, it didn't work.
Can someone help me?
SELECT poh.segment1,
tmp.closed_code,
gcc.segment1,
gcc.segment2,
gcc.segment3,
gcc.segment4,
gcc.segment5,
gcc.segment6,
gcc.segment7,
SUM (NVL (gjl.entered_dr, 0) - NVL (gjl.entered_cr, 0))
FROM apps.up_po_encumb_relief_tmp_nb TMP,
apps.po_headers_all POH,
apps.po_distributions_all pod,
apps.ap_invoice_distributions_all APID,
xla.xla_transaction_entities XTE,
xla_events XE,
apps.xla_ae_headers XAH,
apps.xla_ae_lines XAL,
apps.gl_import_references GIR, -- DOUBLE CHECK JOIN CONDITIONS ON THIS TO INCLUDE OTHER COLS
apps.gl_je_lines GJL,
apps.gl_je_headers GJH,
apps.gl_code_combinations GCC
WHERE POH.segment1 = TMP.PO_NUMBER
AND POH.PO_HEADER_ID = POD.PO_HEADER_ID
AND POD.Po_distribution_id = APID.po_distribution_id
AND XTE.APPLICATION_ID = 200 -- Payables
AND XTE.SOURCE_ID_INT_1 = APID.INVOICE_ID --POH.po_header_id
AND XTE.ENTITY_ID = XE.ENTITY_ID
AND XTE.APPLICATION_ID = XE.APPLICATION_ID
AND XAH.ENTITY_ID = XE.ENTity_ID
AND XAH.EVENT_ID = XE.EVENT_ID
AND XAH.APPLICATION_ID = XE.APPLICATION_ID
AND XAL.AE_HEADER_ID = XAH.AE_HEADER_ID
AND XAL.APPLICATION_ID = XAH.APPLICATION_ID
AND GIR.gl_sl_link_table = XAL.gl_sl_link_table
AND GIR.gl_sl_link_id = XAL.gl_sl_link_id
AND GJL.je_header_id = GIR.je_header_id
AND GJL.je_line_num = GIR.je_line_num
AND GJH.je_header_id = GJL.je_header_id
AND GJH.status = 'P'
AND POD.code_combination_id = GJL.code_combination_id
AND GJL.code_combination_id = GCC.code_combination_id
AND GCC.enabled_flag = 'Y'
AND GJH.je_source = 'Payables'
AND GJH.je_category = 'Purchase Invoices'
AND GJH.encumbrance_type_id IN (1001, 1002)
AND GJH.actual_flag = 'E'
AND GJH.status = 'P'
AND (NVL (GJL.entered_dr, 0) != 0 OR NVL (GJL.entered_cr, 0) != 0)
GROUP BY poh.segment1,
tmp.closed_code,
gcc.segment1,
gcc.segment2,
gcc.segment3,
gcc.segment4,
gcc.segment5,
gcc.segment6,
gcc.segment7;Hi,
did you
- check table statistics (have the affected tables been analyzed recently)?
- check explain plan for full table scans? You are using NVL on gjl.entered_dr
and gjl.entered_cr which may lead to a full table scan, as far as i know, there
is no (standard) functional index on both columns.
Regards
Maybe you are looking for
-
How do i use my 3g to connect to my computer to use internet
can someone help me connecting my phone to my laptop so i can get internet access. i can connect on my phone. but my laptop cannot connect for some reason
-
Concatenate name in select query...
Hi Pals, I was wondering how to directly concetenate client name in the select query itself... Currently the code says : SELECT SINGLE NAME1 NAME2 INTO (V_NAME1,V_NAME2) FROM KNA1 WHERE KUNNR = I_PROJ-ZZCLIENT. CONCAT
-
Hi, If you have numerous methods in a class, can you just call them like so: // in the .fla file var john:Person = new Person(63,150); // creates a new person named john 63" and 150lbs. john.weight(180); // changes johns weight to 180lbs. // in the .
-
Need to call sap transaction when the work item got rejected.
Hi all, I need to call the ME22n transaction once i reject the Work item. Once i press the rejection button on the work item it should direct to the sap transaction. how can i make this functionality in the decision task. Do i need to implement an ex
-
Add an additional field to a generated rapid application
Hello, i have created an application with the rapid application process. Thereby i used an existing database table. But now i need to add two more fields to this database table...is it possible? greets KungPow