Why elapsed time is high in Partitioned table ?

Question

HI All,
I executed two cases, where I update a col of partition and non partitioned table, but the complete elapsed time is quite high in partition table. I am going to paste my findings on the board.
update test_partcodes set codetype = 'A'
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          5          0           0
Execute      1     36.65      82.90      16982        367    3554469     3476353
Fetch        0      0.00       0.00          0          0          0           0
total        2     36.65      82.91      16982        372    3554469     3476353
Elapsed times include waiting on following events:
  Event waited on                             Times   Max. Wait  Total Waited
  ----------------------------------------   Waited  ----------  ------------
  PX Deq: Join ACK                                4        0.00          0.00
  PX Deq: Parse Reply                             4        0.09          0.16
  PX Deq: Execute Reply                          61        0.07          0.18
  db file sequential read                     16982        0.57         41.57
  log file switch completion                     27        0.57          1.76
  PX Deq: Signal ACK                              5        0.10          0.10
  enqueue                                         2        0.00          0.00
  SQL*Net message to client                       2        0.00          0.00
  SQL*Net message from client                     2        8.12          8.13
  SQL*Net break/reset to client                   2        0.00          0.00
update test_partcode_partition set codetype = 'A'
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1    105.34     182.91      13334    2637470    8409866     2899525
Fetch        0      0.00       0.00          0          0          0           0
total        2    105.34     182.91      13334    2637470    8409866     2899525
Elapsed times include waiting on following events:
  Event waited on                             Times   Max. Wait  Total Waited
  ----------------------------------------   Waited  ----------  ------------
  rdbms ipc reply                                 2        0.00          0.00
  enqueue                                         2        1.28          1.28
  PX Deq: Join ACK                                5        0.00          0.00
  PX Deq: Parse Reply                             4        0.26          0.31
  PX Deq: Execute Reply                        2464        0.17          1.50
  log buffer space                              163        0.28          2.27
  log file switch completion                     75        0.41          3.04
  db file sequential read                     13333        0.67         59.54
  PX Deq: Signal ACK                              8        0.10          0.32
  SQL*Net message to client                       1        0.00          0.00
  SQL*Net message from client                     1        0.00          0.00
Also, you can check explain plan
test_staging@CHRYSLER> explain plan for update test_partcodes set codetype = 'A' ;
Explained.
test_staging@CHRYSLER> @plan
PLAN_TABLE_OUTPUT
| Id  | Operation            |  Name           | Rows  | Bytes | Cost  |  TQ    |IN-OUT| PQ Distrib |
|   0 | UPDATE STATEMENT     |                 |  3476K|  6789K|   410 |        |      |            |
|   1 |  UPDATE              | TEST_PARTCODES  |       |       |       |        |      |            |
|   2 |   TABLE ACCESS FULL  | TEST_PARTCODES  |  3476K|  6789K|   410 | 37,00  | P->S | QC (RAND)  |
test_staging@CHRYSLER> explain plan for update test_partcode_partition set codetype = 'A' ;
Explained.
test_staging@CHRYSLER> @plan
PLAN_TABLE_OUTPUT
| Id  | Operation            |  Name                    | Rows  | Bytes | Cost  | Pstart| Pstop |  TQ    |IN-OUT| PQ Distrib |
|   0 | UPDATE STATEMENT     |                          |  1159K|  3397K|   342 |       |       |     | |            |
|   1 |  UPDATE              | TEST_PARTCODE_PARTITION  |       |       |       |       |       |     | |            |
|   2 |   PARTITION RANGE ALL|                          |       |       |       |     1 |    12 | 38,00  | PCWP |            |
|   3 |    TABLE ACCESS FULL | TEST_PARTCODE_PARTITION  |  1159K|  3397K|   342 |     1 |    12 | 38,00  | P->S | QC (RAND)  |
Note: cpu costing is offhare krishna
Alok

Answer 1

Sorry for incomplete info, Now I am pasting the DDL, which I used to create a Partition Table.
create table test_partcode_partition
Partition by range (codetype)
( PARTITION part_2 VALUES LESS THAN ('C'),
PARTITION part_3 VALUES LESS THAN ('E'),
PARTITION part_4 VALUES LESS THAN ('F'),
PARTITION part_5 VALUES LESS THAN ('L'),
PARTITION part_6 VALUES LESS THAN ('M'),
PARTITION part_7 VALUES LESS THAN ('O'),
PARTITION part_8 VALUES LESS THAN ('R'),
PARTITION part_9 VALUES LESS THAN ('T'),
PARTITION part_10 VALUES LESS THAN ('X'),
PARTITION part_11 VALUES LESS THAN ('Y'),
PARTITION part_12 VALUES LESS THAN ('Z'),
PARTITION PM VALUES LESS THAN (MAXVALUE))
nologging parallel
as
select * from mxm_partcodes ;
DB VERSION - 9.2.0.5.0
OS - WIn 2003 Server.
hare krishna
Alok