Zfs destroy command takes more time than usual

Hi,
When I run the destroy command it takes more than usual.
I have exported the lun form this zfs volume ealier.
Later I have removed the lun view and deleted the lun.After that when I run the below command it takes more time (more than 5mins and still running)
#zfs destroy storage/lu

Is there a way to quickly destroy the filesystem.
It looks it removing the allocated files.
              capacity     operations    bandwidth
pool        alloc   free   read  write   read  write
storage0     107G   116T  3.32K  2.52K  3.48M  37.7M
storage0     107G   116T    840    551  1.80M  6.01M
storage0     106G   116T    273      0   586K      0
storage0     106G   116T  1.19K      0  2.61M      0
storage0     106G   116T  1.47K      0  3.20M  

Similar Messages

  • Count (*)  for select stmt take more time than  execute a that sql stmt

    HI
    count (*) for select stmt take more time than execute a that sql stmt
    executing particular select stmt take 2.47 mins but select stmt is using the /*+parallel*/ (sql optimer) in that sql  command for faster execute .
    but if i tried to find out total number of rows in that query it takes more time ..
    almost 2.30 hrs still running to find count(col)
    please help me to get count of row faster.
    thanks in advance...

    797525 wrote:
    HI
    count (*) for select stmt take more time than execute a that sql stmt
    executing particular select stmt take 2.47 mins but select stmt is using the /*+parallel*/ (sql optimer) in that sql  command for faster execute .
    but if i tried to find out total number of rows in that query it takes more time ..
    almost 2.30 hrs still running to find count(col)
    please help me to get count of row faster.
    thanks in advance...That may be because your client is displaying only the first few records when you are running the "SELECT *". But when you run "COUNT(*)", the whole records has to be counted.
    As already mentined please read teh FAQ to post tuning questions.

  • Delete DML statment takes more time than Update or Insert.

    i want to know whether a delete statement takes more time than an update or insert DML command. Please help in solving the doubt.
    Regards.

    i do not get good answers sometimes, so, i ask again.I think Alex answer to your post was quite complete. If you missed some information, continue the same post, instead of opening a new thread with the same subject and content.
    You should be satistied with the answers you get, I also answered your question about global indexes, and I do think my answer was very complete. You may ask more if you want, but stop multiposting please. It is quite annoying.
    Ok, have a nice day

  • Why import of change request in production takes more time than quality?

    Hello All,
                 why import of change request in production takes more time than import into quality?

    Hi jahangeer,
    I believe it takes same time to import a request in both quality and production as they will be in sync.
    Even then if it takes more time in production that may depend on the change request.
    Thanks
    Pavan

  • When i put my Mac for sleep it takes more time than normal ( 20 secs). Sometimes, coming back from sleep the system is not responding (freeze).

    When i put my Mac for sleep it takes more time than normal (>20 secs). Sometimes, coming back from sleep the system is not responding (freeze).

    Perform SMC and NVRAM resets:
    http://support.apple.com/en-us/HT201295
    http://support.apple.com/en-us/HT204063
    The try a safe boot:
    http://support.apple.com/en-us/HT201262
    Any change?
    Ciao.

  • Calc takes more time than previous

    Hi All,
    I have a problem with the calc as this calc take more time to execute please help!!!
    I have included calc cache high in the .cfg file.
    FIX (&As, &Af, &C,&RM, @RELATIVE("Pr",0), @RELATIVE("MS",0), @RELATIVE("Pt",0), @RELATIVE("Rn",0),@RELATIVE("Ll",0))
    CLEARDATA "RI";
    /* 22 Comment */
    FIX("100")
    "RI" = @ROUND ((("RDL")/("SBE"->"RDL"->"TMS"->"TP"->"TR"->"AF"->"Boom")),8);
    ENDFIX
    FIX("200")
    "RI" = @ROUND ((("RDL")/("ODE"->"RDL"->"TMS"->"T_P"->"TR"->"AF"->"Boom")),8);
    ENDFIX
    Appriciate your help.
    Regards,
    Mink.

    Mink,
    If the calculation script ,which you are using is the same which performed better before and data being processes is same ( i mean data might not have exceptionally grown more).Then, there must be other reasons like server side OS , processor or memory issues.Consult sys admin .Atleast you ll be sure that there is nothing wrong with systems.
    To fine tune the calc , i think , you can minimise fix statements . But,thats not the current issue though
    Sandeep Reddy Enti
    HCC
    http://analytiks.blogspot.com

  • Suddenly ODI scheduled executions taking more time than usual.

    Hi,
    I have set ODI packages scheduled for execution.
    From some days those are taking more time to execute themselves.
    Before they used to take 1 hr 30 mins approx.
    Now they are taking 3 - 3 hr 15 mins approx.
    And there no any major change in data in terms of Quantity.
    My ODI version s
    Standalone Edition Version 11.1.1
    Build ODI_11.1.1.3.0_GENERIC_100623.1635
    ODI packages are mainly using Oracle as SOURCE and TARGET DB.
    What things should i check to get to know reasons of sudden increase in time of execution.
    Any pointers regarding this would be appreciated.
    Thanks,
    Mahesh

    Mahesh,
    Use some repository queries to retrieve the session task timings and compare your slow execution to a previous acceptable execution, then look for the biggest changes - this will highlight where you are slowing down, then its off to tune the item accordingly.
    See here for some example reports , you might need to tweak for your current repos version but I dont think the table structures have changed that much :
    http://rnm1978.wordpress.com/2010/11/03/analysing-odi-batch-performance/

  • RMAN cold backup taking more time than usual

    Hi everybody.. please help me resolving below issue..
    I have configured the RMAN in one of the production database with separate catalogue database six months earlier. I have sceduled weekly cold backup through RMAN on sunday 6pm. Normally it used to take one hour to complete the cold backup and database goes down soon as the job starts.
    But since from then every week the time taken to just initiate the database shutdown continuosly increasing and recently when i checked it is taking 1 hour to initiate the database shutdown. Once the initiation starts it hardly take 1 to 3 min to shutdown.
    Database is up and running during that one Hour. I was in the assumption that RMAN takes some time to execute its internal packages.
    Please help
    Regards,
    Arun Kumar

    Hi John and Tychos,
    Thank you very much for your valuable inputs.
    Yesterday there was cold backup and i have monitored the CPU usage. But there was no load on the CPU at that time and CPU usage was 0%
    I have tried connecting to RMAN manually and it connects within a second. And also noticed in prstat -a that rman connects as soon as the job starts.
    So i think that its taking time at the deleting obsolete backups.
    But I have observerd following observation.
    Before executing the delete obsolete command as mentioned before
    RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Backup Set 83409 25-JUL-09
    Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
    Backup Set 83410 25-JUL-09
    Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
    Backup Set 83411 25-JUL-09
    Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
    After executing the delete obsolete command
    RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
    Report of obsolete backups and copies
    Type Key Completion Time Filename/Handle
    Backup Set 83409 25-JUL-09
    Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
    Backup Set 83410 25-JUL-09
    Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
    Backup Set 83411 25-JUL-09
    Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
    Please advice me on the following.
    1. Why its not deleting the obsolete BACKUP SETS?
    2. Is it normal that RMAN takes this much deleting obsolete backup sets? How can i minimize the time taking for deleting obsolete files.
    Thanks and Regards,
    Arun Kumar

  • RMAN backup taking more time than usual suddenly

    Hi All,
    We are using 11.1.0.7 database, We regularly takes the full level 0 incremental backup which generally tooks 4:30 hours to complete but from last 2-3 days it is taking 6 hours /or more to complete. We did not made any parameter changes or script change in the database.
    Below are the details of rman :
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name OLAP are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'f:\backup
    CONFIGURE DEVICE TYPE DISK PARALLELISM 6 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE DISK MAXOPENFILES 2;
    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
    CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
    CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
    CONFIGURE CHANNEL 4 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
    CONFIGURE CHANNEL 5 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
    CONFIGURE CHANNEL 6 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
    CONFIGURE CHANNEL 7 DEVICE TYPE DISK FORMAT 'e:\backup\OLAP\OLAP_full_%u
    CONFIGURE CHANNEL 8 DEVICE TYPE DISK FORMAT 'f:\backup\OLAP\OLAP_full_%u
    CONFIGURE MAXSETSIZE TO UNLIMITED;
    CONFIGURE ENCRYPTION FOR DATABASE OFF;
    CONFIGURE ENCRYPTION ALGORITHM 'AES128';
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2';
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'f:\backup\OLAP\SNCFOLAP.ORA';
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'F:\BACKUP\OLAP\SNCFOLAP.ORA';
    =====================================================
    Please help me, as this more time make my schedule task to extend.
    Thanks
    Sam

    sam wrote:
    Hi All,
    We are using 11.1.0.7 database, We regularly takes the full level 0 incremental backup which generally tooks 4:30 hours to complete but from last 2-3 days it is taking 6 hours /or more to complete. We did not made any parameter changes or script change in the database.could be due to change in server load,
    please compare server load(cpu/memory) on above two period.

  • Cube content deletion is taking more time than usual.

    Hi Experts,
    We have a Process chain which ideally should run in every two hours. This chain has a delete data cube content step before the new data is loaded in the cube. This chain is running fine for one instance & the other instance is taking more time so it is quite intermittent.
    In the process chain we are also deleting contents from the Dimension tables (in the delete content step). Need your inputs to improve the performance of this step.
    Thanks & Regards
    Mayank Tyagi.

    Hi Mayank ,
    You can delete the indexes of the cube before deleting the contents of the cube . The concept is same as of data loading that data loads happens faster when indexes are deleted .
    If you are having aggregates over this cube , then that aggregate will be also adjusted .
    Kind Regards,
    Ashutosh Singh

  • Why HTML report takes more time than the PDF one?

    Hi,
    I have created report in Reports 6i. When I run the report on the web with FORMAT = PDF it runs very fast and shows all the pages in 2 minutes. But when I run with
    FORMAT = HTML it shows the first page in 2 minutes, after that it takes lot of time to show the remaining pages. If the total pages are more than 40, the browser just freezes
    Can somebody give me the reason?
    Is there any way to rectify this?
    Thanks alot.
    Ram.

    Hi Senthil,
    Iam running with the below parameters.
    Format : HTML
    Destination : Screen.
    My default browser is IE. When I try to run using Netscape it showed only 1 page out of 34 pages.
    When I run Format as PDF it is faster but font size is small when it opens up. Offcourse user can zoom it.
    If I increase the report width from 11 to 14 the font size becomes very small when it open up in browser.
    Is there any way that I can set up zoom when I run as PDF?
    Thanks for your help.
    Ram.

  • SYS_REFCURSOR takes more time than direct query execution

    I have a stored proc which has 4 inputs and 10 output and all outputs are sys_refcursor type.
    Among 10 ouputs, 1 cursor returns 4k+ records and all other cursors has 3 or 4 records and average 5 columns in each cursors. For this, it takes 8 sec to complete the execution. If we directly query, it gives output in .025 sec.
    I verified code located the issue with cursor which returns 4k+ only.
    The cursor opening from a temporary table (which has 4k+ records ) without any filter. The query which inserted into temporary is direct inserts only and i found nothing to modify there.
    Can anyone suggest, how we can bring the results in less than 3 sec? This is really a challenge since the code needs to go live next week.
    Any help appreciated.
    Thanks
    Renjish

    I've just repeated the test in SQL*Plus on my test database.
    Both the ref cursor and direct SQL took 4.75 seconds.
    However, that time is not the time to execute the SQL statement, but the time it took SQL*Plus in my command window to print out the 3999 rows of results.
    SQL> create or replace PROCEDURE TEST_PROC (O_OUTPUT OUT SYS_REFCURSOR) is
      2  BEGIN
      3    OPEN  O_OUTPUT FOR
      4      select 11 plan_num, 22  loc_num, 'aaa' loc_nm from dual connect by level < 4000;
      5  end;
      6  /
    Procedure created.
    SQL> set timing on
    SQL> set linesize 1000
    SQL> set serverout on
    SQL> var o_output refcursor;
    SQL> exec test_proc(:o_output);
    PL/SQL procedure successfully completed.
    Elapsed: 00:00:00.04
    SQL> print o_output;
      PLAN_NUM    LOC_NUM LOC
            11         22 aaa
            11         22 aaa
            11         22 aaa
            11         22 aaa
            11         22 aaa
    3999 rows selected.
    Elapsed: 00:00:04.75
    SQL> select 11 plan_num, 22  loc_num, 'aaa' loc_nm from dual connect by level < 4000;
      PLAN_NUM    LOC_NUM LOC
            11         22 aaa
            11         22 aaa
            11         22 aaa
            11         22 aaa
            11         22 aaa
            11         22 aaa
    3999 rows selected.
    Elapsed: 00:00:04.75
    That's the result I expect to see, both taking the same amount of time to do the same thing.
    Please demonstrate how you are running it and getting different results.

  • Threaded program takes more time than running serially!

    Hello All
    Ive converted my program into a threaded application so as to improve speed. However i found that after converting the execution time is more than it was when the program was non threaded. Im not having any synchronised methods. Any idea what could be the reason ?
    Thanx in advance.

    First, if you are doing I/O, then maybe that's what's taking the time and not the threads. One question that hasn't been asked about your problem:
    How much is the time difference? If it takes like 10 seconds to run the one and 10 minutes to run the threaded version, then that's a big difference. But if it is like 10 seconds vs 11 seconds, I think you should reconsider if it matters so much.
    One analogy that comes to mind about multiple threads vs. sequential code is this:
    With sequentially run code, all the code segments are lined up in order and they all go thru the door one after the other. As one goes thru they all move up closer, thus they know who's going first.
    With multi-threaded code, all the code segments sorta pile up around the door in a big crowd. Some push go thru one at a time while others let them (priority), while other times 2 go for the door at the same time and there might be a few moments of "oh, after you", "no, after you", "oh no, I insist, after you" before one goes thru. So that could introduce some delay.

  • 11g takes more time than 9i to execute

    Hi
    We are trying to move 9.1.0.7 to 11.1.0.6 on Solaris 5.10. When we are trying to compare the performance on both database using the same SQL, it is noticed that 11g is taking about 10minutes more than 9i. The schema, objects, data, ... everything is similar. Can anyone please give an idea on why this difference?
    SQL is:
    --sql_id='bt04cp43n28m3'
    --hash_value=2461919517
    INSERT /*+APPEND */INTO act_com
    (act_id, rep, ytd_fee, ytd_commission, mtd_fee, mtd_commission,
    monthly_avg_fee, monthly_avg_comm, ttm_fee, ttm_commission,
    curr_dec_fee, curr_dec_comm, curr_nov_fee, curr_nov_comm,
    curr_oct_fee, curr_oct_comm, curr_sep_fee, curr_sep_comm,
    curr_aug_fee, curr_aug_comm, curr_jul_fee, curr_jul_comm,
    curr_jun_fee, curr_jun_comm, curr_may_fee, curr_may_comm,
    curr_apr_fee, curr_apr_comm, curr_mar_fee, curr_mar_comm,
    curr_feb_fee, curr_feb_comm, curr_jan_fee, curr_jan_comm,
    yr1_dec_fee, yr1_dec_comm, yr1_nov_fee, yr1_nov_comm,
    yr1_oct_fee, yr1_oct_comm, yr1_sep_fee, yr1_sep_comm,
    yr1_aug_fee, yr1_aug_comm, yr1_jul_fee, yr1_jul_comm,
    yr1_jun_fee, yr1_jun_comm, yr1_may_fee, yr1_may_comm,
    yr1_apr_fee, yr1_apr_comm, yr1_mar_fee, yr1_mar_comm,
    yr1_feb_fee, yr1_feb_comm, yr1_jan_fee, yr1_jan_comm,
    yr2_dec_fee, yr2_dec_comm, yr2_nov_fee, yr2_nov_comm,
    yr2_oct_fee, yr2_oct_comm, yr2_sep_fee, yr2_sep_comm,
    yr2_aug_fee, yr2_aug_comm, yr2_jul_fee, yr2_jul_comm,
    yr2_jun_fee, yr2_jun_comm, yr2_may_fee, yr2_may_comm,
    yr2_apr_fee, yr2_apr_comm, yr2_mar_fee, yr2_mar_comm,
    yr2_feb_fee, yr2_feb_comm, yr2_jan_fee, yr2_jan_comm,
    tot_fee_prev_day, tot_comm_prev_day)
    SELECT act.acct_no, x.rep,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr)
    THEN x.dollar_amt
    ELSE 0
    END
    ) ytd_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr)
    THEN x.dollar_amt
    ELSE 0
    END
    ) ytd_commission,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND curr_mm = mm)
    THEN x.dollar_amt
    ELSE 0
    END
    ) mtd_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND curr_mm = mm)
    THEN x.dollar_amt
    ELSE 0
    END
    ) mtd_comm,
    SUM (CASE
    WHEN ( x.cf_ind = 'F'
    AND ( (yr = curr_yr - 1 AND mm >= curr_mm)
    OR (yr = curr_yr AND mm < curr_mm)
    THEN x.dollar_amt
    ELSE 0
    END
    / 12 monthly_avg_fee,
    SUM (CASE
    WHEN ( x.cf_ind = 'C'
    AND ( (yr = curr_yr - 1 AND mm >= curr_mm)
    OR (yr = curr_yr AND mm < curr_mm)
    THEN x.dollar_amt
    ELSE 0
    END
    / 12 monthly_avg_comm,
    SUM (CASE
    WHEN ( x.cf_ind = 'F'
    AND ( (yr = curr_yr - 1 AND mm > curr_mm)
    OR (yr = curr_yr AND mm <= curr_mm)
    THEN x.dollar_amt
    ELSE 0
    END
    ) ttm_fee,
    SUM (CASE
    WHEN ( x.cf_ind = 'C'
    AND ( (yr = curr_yr - 1 AND mm > curr_mm)
    OR (yr = curr_yr AND mm <= curr_mm)
    THEN x.dollar_amt
    ELSE 0
    END
    ) ttm_commission,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 12)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_dec_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 12)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_dec_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 11)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_nov_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 11)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_nov_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 10)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_oct_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 10)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_oct_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 9)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_sep_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 9)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_sep_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 8)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_aug_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 8)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_aug_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 7)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_jul_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 7)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_jul_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 6)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_jun_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 6)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_jun_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 5)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_may_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 5)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_may_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 4)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_apr_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 4)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_apr_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 3)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_mar_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 3)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_mar_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 2)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_feb_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 2)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_feb_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr AND mm = 1)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_jan_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr AND mm = 1)
    THEN x.dollar_amt
    ELSE 0
    END
    ) curr_jan_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 12)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_dec_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 12)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_dec_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 11)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_nov_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 11)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_nov_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 10)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_oct_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 10)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_oct_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 9)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_sep_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 9)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_sep_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 8)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_aug_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 8)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_aug_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 7)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_jul_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 7)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_jul_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 6)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_jun_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 6)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_jun_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 5)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_may_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 5)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_may_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 4)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_apr_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 4)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_apr_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 3)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_mar_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 3)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_mar_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 2)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_feb_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 2)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_feb_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 1 AND mm = 1)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_jan_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 1 AND mm = 1)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr1_jan_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 12)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_dec_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 12)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_dec_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 11)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_nov_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 11)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_nov_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 10)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_oct_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 10)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_oct_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 9)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_sep_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 9)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_sep_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 8)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_aug_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 8)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_aug_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 7)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_jul_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 7)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_jul_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 6)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_jun_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 6)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_jun_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 5)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_may_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 5)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_may_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 4)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_apr_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 4)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_apr_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 3)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_mar_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 3)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_mar_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 2)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_feb_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 2)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_feb_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND yr = curr_yr - 2 AND mm = 1)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_jan_fee,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND yr = curr_yr - 2 AND mm = 1)
    THEN x.dollar_amt
    ELSE 0
    END
    ) yr2_jan_comm,
    SUM (CASE
    WHEN (x.cf_ind = 'F' AND asof_cymd = bus_day)
    THEN x.dollar_amt
    ELSE 0
    END
    ) tot_fee_prev_day,
    SUM (CASE
    WHEN (x.cf_ind = 'C' AND asof_cymd = bus_day)
    THEN x.dollar_amt
    ELSE 0
    END
    ) tot_comm_prev_day
    FROM (SELECT acct_no, status
    FROM action_tab
    UNION
    SELECT '0' acct_no, 'AC' status
    FROM DUAL) act,
    (SELECT TO_NUMBER (TO_CHAR (TO_DATE (NVL (asof_cymd, trade_cymd),
    'YYYY-MM-DD'
    'YYYY'
    ) yr,
    TO_NUMBER (TO_CHAR (TO_DATE (NVL (asof_cymd, trade_cymd),
    'YYYY-MM-DD'
    'MM'
    ) mm,
    TO_NUMBER (TO_CHAR (h_inner.bus_day, 'yyyy')) curr_yr,
    TO_NUMBER (TO_CHAR (h_inner.bus_day, 'mm')) curr_mm,
    rep_commission,
    TO_DATE (NVL (asof_cymd, trade_cymd),
    'YYYY-MM-DD'
    ) asof_cymd,
    c.acct_no, rep_full rep, f.acct_no fba_acct,
    CASE
    WHEN ( TO_DATE (f.close_cymd, 'YYYY-MM-DD') <=
    SYSDATE
    OR f.acct_no IS NULL
    THEN 'C'
    ELSE 'F'
    END cf_ind,
    CASE
    WHEN (adj_commission != 0
    AND adj_commission IS NOT NULL
    THEN adj_commission
    ELSE NVL (commission, 0) + NVL (mark_up_down, 0)
    END dollar_amt
    FROM coding_tab c, fbaact_tab f, hist_dt_ctrl_tab h_inner
    WHERE c.acct_no = f.acct_no(+)) x,
    hist_dt_ctrl_tab
    WHERE act.acct_no = x.acct_no
    AND x.rep IS NOT NULL
    --AND act.rep = x.rep
    AND act.status IN ('AC', 'IN')
    GROUP BY act.acct_no, x.rep
    Thanks in advance.

    Hi
    The details given below.
    Execution Plan on 9i
    1.00     2,412.00     SELECT STATEMENT      93,164.00     260,496.00          93,164.00     CHOOSE
    2.00     2,412.00     -SORT GROUP BY      93,164.00     260,496.00          93,164.00     
    3.00     8,684,104.00     --NESTED LOOPS OUTER      17,410.00     937,883,232.00          17,410.00     
    4.00     8,684,104.00     ---HASH JOIN      17,410.00     772,885,256.00          17,410.00     
    5.00     538,055.00     ----MERGE JOIN CARTESIAN      5,632.00     28,516,915.00          5,632.00     
    6.00     1.00     -----MERGE JOIN CARTESIAN      6.00     14.00          6.00     
    7.00     1.00     ------TABLE ACCESS FULL HIST_DT_CTRL     3.00     7.00          3.00     ANALYZED
    7.00     1.00     ------BUFFER SORT      3.00     7.00          3.00     
    8.00     1.00     -------TABLE ACCESS FULL HIST_DT_CTRL     3.00     7.00          3.00     ANALYZED
    6.00     538,055.00     -----BUFFER SORT      5,629.00     20,984,145.00          5,629.00     
    7.00     538,055.00     ------VIEW      5,626.00     20,984,145.00               
    8.00     538,055.00     -------SORT UNIQUE      5,626.00     5,298,870.00          5,599.00     
    9.00          --------UNION-ALL                          
    10.00     529,887.00     ---------TABLE ACCESS FULL ACTION_TAB     4,164.00     5,298,870.00          4,164.00     ANALYZED
    10.00     8,168.00     ---------TABLE ACCESS FULL DUAL     11.00               11.00     
    5.00     3,518,688.00     ----TABLE ACCESS FULL CODING_TAB     3,978.00     126,672,768.00          3,978.00     ANALYZED
    4.00     1.00     ---TABLE ACCESS BY INDEX ROWID FBAACT_TAB          19.00               ANALYZED
    5.00     1.00     ----INDEX UNIQUE SCAN FBA_ACT_PK_ACCT_NO                         ANALYZED
    Execution Plan on 11g
    1.00     2,399.00     SELECT STATEMENT      37,681.00     271,087.00     17,370,453,529.00     35,293.00     ALL_ROWS
    2.00     2,399.00     -HASH GROUP BY      37,681.00     271,087.00     17,370,453,529.00     35,293.00     
    3.00     10,291,120.00     --HASH JOIN RIGHT OUTER      36,195.00     1,162,896,560.00     6,562,221,120.00     35,293.00     
    4.00     1.00     ---TABLE ACCESS FULL FBAACT_TAB     2.00     19.00     7,121.00     2.00     ANALYZED
    4.00     10,291,120.00     ---HASH JOIN      36,051.00     967,365,280.00     5,529,464,283.00     35,291.00     
    5.00     660,746.00     ----MERGE JOIN CARTESIAN      14,778.00     38,323,268.00     2,126,486,738.00     14,486.00     
    6.00     1.00     -----MERGE JOIN CARTESIAN      10.00     16.00     185,497.00     10.00     
    7.00     1.00     ------TABLE ACCESS FULL HISTDT_CTRL     5.00     8.00     92,749.00     5.00     ANALYZED
    7.00     1.00     ------BUFFER SORT      5.00     8.00     92,749.00     5.00     
    8.00     1.00     -------TABLE ACCESS FULL HISTDT_CTRL     5.00     8.00     92,749.00     5.00     ANALYZED
    6.00     660,746.00     -----BUFFER SORT      14,773.00     27,751,332.00     2,126,393,989.00     14,481.00     
    7.00     660,746.00     ------VIEW      14,768.00     27,751,332.00     2,126,301,241.00     14,476.00     
    8.00     660,746.00     -------SORT UNIQUE      14,768.00     6,607,450.00     2,119,018,839.00     14,474.00     
    9.00          --------UNION-ALL                          
    10.00     660,745.00     ---------TABLE ACCESS FULL ACTION_TAB     12,058.00     6,607,450.00     1,494,346,997.00     11,853.00     ANALYZED
    10.00     1.00     ---------FAST DUAL      2.00          7,271.00     2.00     
    5.00     3,418,417.00     ----TABLE ACCESS FULL CODING_TAB     11,116.00     123,063,012.00     1,823,935,730.00     10,865.00     ANALYZED
    The differences in INIT Parameters
    9i 11g
    multi_block_read_count 16 128
    optimizer_mode choose all_rows
    other h/w and load related
    CPUs 8@900MHZ 8@1200MHZ
    load used by many QA users just testing to make sure
    all our cronjobs are running
    fine or not
    the above mentioned SQL is part of one of the processes, takes about 41 min on 9i and the same taking about 52-56 minutes on 11g.
    Also, I took out every in-line SELECT statement and ran in both envs. looks 11g is executing them fast. But as a whole it takes about 10-12 mins more on 11g. So
    I suspect that its problem with INSERT statement. So I just wrote a simple PL/SQL block to insert 1m records and tested on both.
    INSERTION OF 1M records 1:46 min 2:06 min
    count(*) 0:0.35 sec 0:0.17 sec
    delete 0:28.9 sec 0:36.72 sec
    rollback 0:32.19 sec 0:41.36 sec

  • Threaded program takes more time than executing serially!

    Hello All
    Ive converted my program into a threaded application so as to improve speed. However i found that after converting the execution time is more than it was when the program was non threaded. Im not having any synchronised methods. Any idea what could be the reason ?
    Thanx in advance.

    Putting aside fstreams amusing comment, I suspect your
    theads are never yielding (they are sitting in a tight
    loop, thus taking all available procesor power). Try
    adding Thread.sleep(0) at som point in the loop.No. If you just want to encourage one thread to give another thread a turn, use yield, not sleep.
    Note, though, that this may not help your situation. As was pointed out, on a single CPU machine, the only way a multithreaded program will run faster (by which I mean total wall-clock time start to finish) than its single-threaded equivalent is if the 1-thread version spends a lot of time waiting for IO when it could be doing something else. (If it's waiting for IO, but that IO is needed for the big number crunching, then putting the crunching in another thread won't make things any faster.)
    On the other hand, if by "faster" you're referring to a more responsive GUI, then, yes, in general you might expect better GUI response be putting non-GUI stuff in a different thread, but there's no guarantee. Depending on what the other thread does, how much work your GUI has to do, how your VM's scheduler works, how you've split up the work, etc., it may not be any better.
    I know that's not very specific, but neither was your question.

Maybe you are looking for