Qurey running for last 18 Hours plz help in this regard

Question

my server has 4 Gb Ram plz tell me something. what action should i take. This Query is running 18 hours plz by seeing this ADDM plz sugest what to do i'm highly thanksful to yoy
ADDM Report for Task 'ADDM:1196827189_1_679'
Analysis Period
AWR snapshot range from 678 to 679.
Time period starts at 25-NOV-08 09.01.03 AM
Time period ends at 25-NOV-08 09.53.05 AM
Analysis Target
Database 'ORCL' with DB ID 1196827189.
Database version 11.1.0.6.0.
ADDM performed an analysis of instance orcl, numbered 1 and hosted at SRV01.
Activity During the Analysis Period
Total database time was 7940 seconds.
The average number of active sessions was 2.54.
Summary of Findings
Description Active Sessions Recommendations
Percent of Activity
1 Virtual Memory Paging 2.54 | 100 1
2 Top SQL by DB Time 2.47 | 97.18 1
3 CPU Usage 2.47 | 97.09 1
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Findings and Recommendations
Finding 1: Virtual Memory Paging
Impact is 2.54 active sessions, 100% of total activity.
Significant virtual memory paging was detected on the host operating system.
Recommendation 1: Host Configuration
Estimated benefit is 2.54 active sessions, 100% of total activity.
Action
Host operating system was experiencing significant paging but no
particular root cause could be detected. Investigate processes that do
not belong to this instance running on the host that are consuming
significant amount of virtual memory. Also consider adding more physical
memory to the host.
Finding 2: Top SQL by DB Time
Impact is 2.47 active sessions, 97.18% of total activity.
SQL statements consuming significant database time were found.
Recommendation 1: SQL Tuning
Estimated benefit is 2.54 active sessions, 100% of total activity.
Action
Run SQL Tuning Advisor on the SQL statement with SQL_ID "9d65avvugb899".
Related Object
SQL statement with SQL_ID 9d65avvugb899 and PLAN_HASH 1187702671.
UPDATE GN_FLAT_IN_TABLE SET DG0_ID=(SELECT JAG_N24_DG0.DG0_ID FROM
JAG_N24_DG0 WHERE NVL ( JAG_N24_DG0.ITEM_DISC_AMT , -1033 ) = NVL (
GN_FLAT_IN_TABLE.ITEM_DISC_AMT , -1033 ) AND NVL (
JAG_N24_DG0.LINE_AMT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_AMT ,
-1033 ) AND NVL ( JAG_N24_DG0.LINE_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_CODE , -1033 ) AND NVL ( JAG_N24_DG0.LINE_NAME
, -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.LINE_INTERNAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_INTERNAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_REC_SEQ , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_REC_SEQ , -1033 ) AND NVL (
JAG_N24_DG0.PRIMARY_CARD , -1033 ) = NVL (
GN_FLAT_IN_TABLE.PRIMARY_CARD , -1033 ) AND NVL (
JAG_N24_DG0.TXN_CAT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_CAT ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DATE , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_DATE , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_TIME , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_TIME , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_ID , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_ID ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DURATION , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TXN_DURATION , -1033 ) AND NVL (
JAG_N24_DG0.TILL_LOCAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TILL_LOCAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.STORE_CODE , -1033 ) = NVL ( GN_FLAT_IN_TABLE.STORE_CODE
, -1033 ) AND NVL ( JAG_N24_DG0.STORE_NAME , -1033 ) = NVL (
GN_FLAT_IN_TABLE.STORE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.OPERATOR_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.OPERATOR_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_QTY , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_QTY ,
-1033 ) AND NVL ( JAG_N24_DG0.CUSTOMER_STAFF_REF , -1033 ) = NVL (
GN_FLAT_IN_TABLE.CUSTOMER_STAFF_REF , -1033 ) AND
NVL(GN_FLAT_IN_TABLE.OPERATIONAL_DATE, '14-AUG-1947'
)=NVL(JAG_N24_DG0.OPERATIONAL_DATE, '14-AUG-1947' ))
Action
Investigate the SQL statement with SQL_ID "9d65avvugb899" for possible
performance improvements.
Related Object
SQL statement with SQL_ID 9d65avvugb899 and PLAN_HASH 1187702671.
UPDATE GN_FLAT_IN_TABLE SET DG0_ID=(SELECT JAG_N24_DG0.DG0_ID FROM
JAG_N24_DG0 WHERE NVL ( JAG_N24_DG0.ITEM_DISC_AMT , -1033 ) = NVL (
GN_FLAT_IN_TABLE.ITEM_DISC_AMT , -1033 ) AND NVL (
JAG_N24_DG0.LINE_AMT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_AMT ,
-1033 ) AND NVL ( JAG_N24_DG0.LINE_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_CODE , -1033 ) AND NVL ( JAG_N24_DG0.LINE_NAME
, -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.LINE_INTERNAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_INTERNAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_REC_SEQ , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_REC_SEQ , -1033 ) AND NVL (
JAG_N24_DG0.PRIMARY_CARD , -1033 ) = NVL (
GN_FLAT_IN_TABLE.PRIMARY_CARD , -1033 ) AND NVL (
JAG_N24_DG0.TXN_CAT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_CAT ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DATE , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_DATE , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_TIME , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_TIME , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_ID , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_ID ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DURATION , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TXN_DURATION , -1033 ) AND NVL (
JAG_N24_DG0.TILL_LOCAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TILL_LOCAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.STORE_CODE , -1033 ) = NVL ( GN_FLAT_IN_TABLE.STORE_CODE
, -1033 ) AND NVL ( JAG_N24_DG0.STORE_NAME , -1033 ) = NVL (
GN_FLAT_IN_TABLE.STORE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.OPERATOR_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.OPERATOR_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_QTY , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_QTY ,
-1033 ) AND NVL ( JAG_N24_DG0.CUSTOMER_STAFF_REF , -1033 ) = NVL (
GN_FLAT_IN_TABLE.CUSTOMER_STAFF_REF , -1033 ) AND
NVL(GN_FLAT_IN_TABLE.OPERATIONAL_DATE, '14-AUG-1947'
)=NVL(JAG_N24_DG0.OPERATIONAL_DATE, '14-AUG-1947' ))
Finding 3: CPU Usage
Impact is 2.47 active sessions, 97.09% of total activity.
Time spent on the CPU by the instance was responsible for a substantial part
of database time.
Recommendation 1: SQL Tuning
Estimated benefit is 2.54 active sessions, 100% of total activity.
Action
Run SQL Tuning Advisor on the SQL statement with SQL_ID "9d65avvugb899".
Related Object
SQL statement with SQL_ID 9d65avvugb899 and PLAN_HASH 1187702671.
UPDATE GN_FLAT_IN_TABLE SET DG0_ID=(SELECT JAG_N24_DG0.DG0_ID FROM
JAG_N24_DG0 WHERE NVL ( JAG_N24_DG0.ITEM_DISC_AMT , -1033 ) = NVL (
GN_FLAT_IN_TABLE.ITEM_DISC_AMT , -1033 ) AND NVL (
JAG_N24_DG0.LINE_AMT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_AMT ,
-1033 ) AND NVL ( JAG_N24_DG0.LINE_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_CODE , -1033 ) AND NVL ( JAG_N24_DG0.LINE_NAME
, -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.LINE_INTERNAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_INTERNAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_REC_SEQ , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_REC_SEQ , -1033 ) AND NVL (
JAG_N24_DG0.PRIMARY_CARD , -1033 ) = NVL (
GN_FLAT_IN_TABLE.PRIMARY_CARD , -1033 ) AND NVL (
JAG_N24_DG0.TXN_CAT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_CAT ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DATE , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_DATE , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_TIME , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_TIME , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_ID , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_ID ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DURATION , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TXN_DURATION , -1033 ) AND NVL (
JAG_N24_DG0.TILL_LOCAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TILL_LOCAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.STORE_CODE , -1033 ) = NVL ( GN_FLAT_IN_TABLE.STORE_CODE
, -1033 ) AND NVL ( JAG_N24_DG0.STORE_NAME , -1033 ) = NVL (
GN_FLAT_IN_TABLE.STORE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.OPERATOR_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.OPERATOR_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_QTY , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_QTY ,
-1033 ) AND NVL ( JAG_N24_DG0.CUSTOMER_STAFF_REF , -1033 ) = NVL (
GN_FLAT_IN_TABLE.CUSTOMER_STAFF_REF , -1033 ) AND
NVL(GN_FLAT_IN_TABLE.OPERATIONAL_DATE, '14-AUG-1947'
)=NVL(JAG_N24_DG0.OPERATIONAL_DATE, '14-AUG-1947' ))
Action
Investigate the SQL statement with SQL_ID "9d65avvugb899" for possible
performance improvements.
Related Object
SQL statement with SQL_ID 9d65avvugb899 and PLAN_HASH 1187702671.
UPDATE GN_FLAT_IN_TABLE SET DG0_ID=(SELECT JAG_N24_DG0.DG0_ID FROM
JAG_N24_DG0 WHERE NVL ( JAG_N24_DG0.ITEM_DISC_AMT , -1033 ) = NVL (
GN_FLAT_IN_TABLE.ITEM_DISC_AMT , -1033 ) AND NVL (
JAG_N24_DG0.LINE_AMT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_AMT ,
-1033 ) AND NVL ( JAG_N24_DG0.LINE_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_CODE , -1033 ) AND NVL ( JAG_N24_DG0.LINE_NAME
, -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.LINE_INTERNAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_INTERNAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_REC_SEQ , -1033 ) = NVL (
GN_FLAT_IN_TABLE.LINE_REC_SEQ , -1033 ) AND NVL (
JAG_N24_DG0.PRIMARY_CARD , -1033 ) = NVL (
GN_FLAT_IN_TABLE.PRIMARY_CARD , -1033 ) AND NVL (
JAG_N24_DG0.TXN_CAT , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_CAT ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DATE , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_DATE , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_TIME , ' 14-AUG-1947' ) = NVL (
GN_FLAT_IN_TABLE.TXN_TIME , ' 14-AUG-1947' ) AND NVL (
JAG_N24_DG0.TXN_ID , -1033 ) = NVL ( GN_FLAT_IN_TABLE.TXN_ID ,
-1033 ) AND NVL ( JAG_N24_DG0.TXN_DURATION , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TXN_DURATION , -1033 ) AND NVL (
JAG_N24_DG0.TILL_LOCAL_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.TILL_LOCAL_CODE , -1033 ) AND NVL (
JAG_N24_DG0.STORE_CODE , -1033 ) = NVL ( GN_FLAT_IN_TABLE.STORE_CODE
, -1033 ) AND NVL ( JAG_N24_DG0.STORE_NAME , -1033 ) = NVL (
GN_FLAT_IN_TABLE.STORE_NAME , -1033 ) AND NVL (
JAG_N24_DG0.OPERATOR_CODE , -1033 ) = NVL (
GN_FLAT_IN_TABLE.OPERATOR_CODE , -1033 ) AND NVL (
JAG_N24_DG0.LINE_QTY , -1033 ) = NVL ( GN_FLAT_IN_TABLE.LINE_QTY ,
-1033 ) AND NVL ( JAG_N24_DG0.CUSTOMER_STAFF_REF , -1033 ) = NVL (
GN_FLAT_IN_TABLE.CUSTOMER_STAFF_REF , -1033 ) AND
NVL(GN_FLAT_IN_TABLE.OPERATIONAL_DATE, '14-AUG-1947'
)=NVL(JAG_N24_DG0.OPERATIONAL_DATE, '14-AUG-1947' ))
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Additional Information
Miscellaneous Information
Wait class "Application" was not consuming significant database time.
Wait class "Commit" was not consuming significant database time.
Wait class "Concurrency" was not consuming significant database time.
Wait class "Configuration" was not consuming significant database time.
Wait class "Network" was not consuming significant database time.
Wait class "User I/O" was not consuming significant database time.
Session connect and disconnect calls were not consuming significant database
time.
Hard parsing of SQL statements was not consuming significant database time.

Answer 1

JACK DBA wrote:
my server has 4 Gb Ram plz tell me something. what action should i take. This Query is running 18 hours plz by seeing this ADDM plz sugest what to do i'm highly thanksful to yoy As already mentioned here in the thread you need to check the execution plan of the UPDATE statement. If you're unlucky then the scalar subquery querying JAG_N24_DG0 is potentially executed for each row of GN_FLAT_IN_TABLE. Depending on the execution plan of the subquery this approach might be quite inefficient.
Generic instructions how to generate a meaningful plan output and how to use the {noformat}{{noformat}code{noformat}}{noformat} tag to get it formatted in mono-space font here follow below:
Could you please post an properly formatted explain plan output using DBMS_XPLAN.DISPLAY including the "Predicate Information" section below the plan to provide more details regarding your statement. Please use the {noformat}[{noformat}code{noformat}]{noformat} tag before and {noformat}[{noformat}/code{noformat}]{noformat} tag after or the {noformat}{{noformat}code{noformat}}{noformat} tag before and after to enhance readability of the output provided:
In SQL*Plus:
SET LINESIZE 130
EXPLAIN PLAN FOR <your statement>;
SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);Note that the package DBMS_XPLAN.DISPLAY is only available from 9i on.
In 9i and above, if the "Predicate Information" section is missing from the DBMS_XPLAN.DISPLAY output but you get instead the message "Plan table is old version" then you need to re-create your plan table using the server side script "$ORACLE_HOME/rdbms/admin/utlxplan.sql".
In previous versions you could run the following in SQL*Plus (on the server) instead:
@?/rdbms/admin/utlxplsA different approach in SQL*Plus:
SET AUTOTRACE ON EXPLAIN
<run your statement>;will also show the execution plan.
In order to get a better understanding where your statement spends the time you might want to turn on SQL trace as described here:
When your query takes too long ...
and post the "tkprof" output here, too.
Regards,
Randolf
Oracle related stuff blog:
http://oracle-randolf.blogspot.com/
SQLTools++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676/
http://sourceforge.net/projects/sqlt-pp/