Oracle 10g Performance between (10.2.0.3.0 and 10.2.0.5.0): Platform solari

Question

Hello all,
We have built our new UAT (10.2.0.5.0) using disk copy from old UAT(10.2.0.3.0). Ystem stats are all up to date. But one of the query takes very long time almost 6 hours in New UAT. But old UAT it takes only 20 minutes .
Can anybody tell why or what i shoudl check for?

Answer 1

Plan@OLD UAT
===============
1 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_3 . The index was scanned in ascending order..
2 The rows from step 1 were inserted into using direct-load insert.
3 Rows were retrieved using the unique index SCHEMANMMAP.XPK_SOURCE_SYSTEM_FEED .
4 Rows from table SCHEMANMMAP.SCHEMANMF_SOURCE_SYSTEM_FEED were accessed using rowid got from an index.
5 Every row in the table SYS.SYS_TEMP_0FD9D6651_E9A50186 is read.
6 A view definition was processed, either from a stored view WEIJ. or as defined by steps 5.
7 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_4 . The index was scanned in ascending order..
8 For each row retrieved by step 6, the operation in step 7 was performed to find a matching row.
9 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
10 A view definition was processed, either from a stored view WEIJ. or as defined by steps 9.
11 Every row in the table SYS.SYS_TEMP_0FD9D6651_E9A50186 is read.
12 A view definition was processed, either from a stored view WEIJ. or as defined by steps 11.
13 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_5 . The index was scanned in ascending order..
14 For each row retrieved by step 12, the operation in step 13 was performed to find a matching row.
15 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
16 A view definition was processed, either from a stored view WEIJ. or as defined by steps 15.
17 For each row retrieved by step 10, the operation in step 16 was performed to find a matching row.
18 Every row in the table SYS.SYS_TEMP_0FD9D6651_E9A50186 is read.
19 A view definition was processed, either from a stored view WEIJ. or as defined by steps 18.
20 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_5 . The index was scanned in ascending order..
21 For each row retrieved by step 19, the operation in step 20 was performed to find a matching row.
22 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
23 A view definition was processed, either from a stored view WEIJ. or as defined by steps 22.
24 For each row retrieved by step 17, the operation in step 23 was performed to find a matching row.
25 One or more rows were retrieved using index SCHEMANMERR.XIE_BATCH_CONTROL_6 . The index was scanned in ascending order..
26 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
27 For the rows returned by step 26, filter out rows depending on filter criteria.
28 Return all rows from steps 24, 27 - including duplicate rows.
29 A view definition was processed, either from a stored view WEIJ. or as defined by steps 28.
30 For each row retrieved by step 4, the operation in step 29 was performed to find a matching row.
31 The rows were sorted to support the join at step 37.
32 Rows were retrieved from concatenated index Partitions determined by Key Values without using the leading column(s).
33 Rows from table Partitions determined by Key Values were accessed using rowid got from a local (single-partition) index.
34 PARTITION LIST SINGLE
35 PARTITION RANGE ALL
36 The rows were sorted to support the join at step 37.
37 Join the sorted results sets provided from steps 31, 36.
38 Rows were retrieved using the unique index Partitions determined by Key Values.
39 Rows from table Partitions determined by Key Values were accessed using rowid got from a local (single-partition) index.
40 PARTITION LIST SINGLE
41 A range of partitions of steps 40 were accessed..
42 For each row retrieved by step 37, the operation in step 41 was performed to find a matching row.
43 Rows were retrieved using the unique index SCHEMANMADM.XPK_INSTRUMENT .
44 Rows from table SCHEMANMADM.INSTRUMENT were accessed using rowid got from an index.
45 For each row retrieved by step 42, the operation in step 44 was performed to find a matching row.
46 One or more rows were retrieved using index Partitions determined by Key Values. The index was scanned in ascending order..
47 PARTITION LIST SINGLE
48 A range of partitions of steps 47 were accessed..
49 For each row retrieved by step 45, the operation in step 48 was performed to find a matching row.
50 Rows from table SCHEMANMADM.INSTRUMENT_BALANCE were accessed using rowid got from a local (single-partition) index.
51 Every row in the table SCHEMANMINT.SCHEMANMF_ACCOUNTING_PERIOD is read.
52 The result sets from steps 50, 51 were joined (hash).
53 Every row in the table SYS.SYS_TEMP_0FD9D6651_E9A50186 is read.
54 A view definition was processed, either from a stored view WEIJ. or as defined by steps 53.
55 For each row retrieved by step 52, the operation in step 54 was performed to find a matching row.
56 The rows from step 55 were inserted into using direct-load insert.
57 Every row in the table SYS.SYS_TEMP_0FD9D6652_E9A50186 is read.
58 A view definition was processed, either from a stored view WEIJ. or as defined by steps 57.
59 Rows were retrieved using the unique index Partitions determined by Key Values.
60 Rows from table Partitions determined by Key Values were accessed using rowid got from a local (single-partition) index.
61 PARTITION LIST SINGLE
62 A range of partitions of steps 61 were accessed..
63 For each row retrieved by step 58, the operation in step 62 was performed to find a matching row.
64 Every row in the table SYS.SYS_TEMP_0FD9D6652_E9A50186 is read.
65 A view definition was processed, either from a stored view WEIJ. or as defined by steps 64.
66 Return all rows from steps 63, 65 - including duplicate rows.
67 TEMP TABLE TRANSFORMATION
68 Rows were returned by the SELECT statement.
++++++++++++++++++++++++++++++++++
Plan@NEW UAT
===============
1 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_3 . The index was scanned in ascending order..
2 The rows from step 1 were inserted into using direct-load insert.
3 Rows were retrieved using the unique index SCHEMANMMAP.XPK_SOURCE_SYSTEM_FEED .
4 Rows from table SCHEMANMMAP.SCHEMANMF_SOURCE_SYSTEM_FEED were accessed using rowid got from an index.
5 Every row in the table Partitions determined by Key Values is read.
6 PARTITION LIST SINGLE
7 PARTITION RANGE ALL
8 For each row retrieved by step 4, the operation in step 7 was performed to find a matching row.
9 Rows were retrieved using the unique index Partitions determined by Key Values.
10 Rows from table Partitions determined by Key Values were accessed using rowid got from a local (single-partition) index.
11 PARTITION LIST SINGLE
12 A range of partitions of steps 11 were accessed..
13 For each row retrieved by step 8, the operation in step 12 was performed to find a matching row.
14 Rows were retrieved using the unique index SCHEMANMADM.XPK_INSTRUMENT .
15 Rows from table SCHEMANMADM.INSTRUMENT were accessed using rowid got from an index.
16 For each row retrieved by step 13, the operation in step 15 was performed to find a matching row.
17 One or more rows were retrieved using index Partitions determined by Key Values. The index was scanned in ascending order..
18 PARTITION LIST SINGLE
19 A range of partitions of steps 18 were accessed..
20 For each row retrieved by step 16, the operation in step 19 was performed to find a matching row.
21 Rows from table SCHEMANMADM.INSTRUMENT_BALANCE were accessed using rowid got from a local (single-partition) index.
22 Every row in the table SCHEMANMINT.SCHEMANMF_ACCOUNTING_PERIOD is read.
23 The result sets from steps 21, 22 were joined (hash).
24 Every row in the table SYS.SYS_TEMP_0FD9FC8FB_DC4EE804 is read.
25 A view definition was processed, either from a stored view WEIJ. or as defined by steps 24.
26 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_4 . The index was scanned in ascending order..
27 The result sets from steps 25, 26 were joined (hash).
28 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
29 A view definition was processed, either from a stored view WEIJ. or as defined by steps 28.
30 Every row in the table SYS.SYS_TEMP_0FD9FC8FB_DC4EE804 is read.
31 A view definition was processed, either from a stored view WEIJ. or as defined by steps 30.
32 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_5 . The index was scanned in ascending order..
33 The result sets from steps 31, 32 were joined (hash).
34 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
35 A view definition was processed, either from a stored view WEIJ. or as defined by steps 34.
36 For each row retrieved by step 29, the operation in step 35 was performed to find a matching row.
37 Every row in the table SYS.SYS_TEMP_0FD9FC8FB_DC4EE804 is read.
38 A view definition was processed, either from a stored view WEIJ. or as defined by steps 37.
39 One or more rows were retrieved using index SCHEMANMERR.XAK_BATCH_CONTROL_5 . The index was scanned in ascending order..
40 The result sets from steps 38, 39 were joined (hash).
41 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
42 A view definition was processed, either from a stored view WEIJ. or as defined by steps 41.
43 For each row retrieved by step 36, the operation in step 42 was performed to find a matching row.
44 One or more rows were retrieved using index SCHEMANMERR.XIE_BATCH_CONTROL_6 . The index was scanned in ascending order..
45 The rows were sorted to support a group operation (MAX,MIN,AVERAGE, SUM, etc).
46 For the rows returned by step 45, filter out rows depending on filter criteria.
47 Return all rows from steps 43, 46 - including duplicate rows.
48 A view definition was processed, either from a stored view WEIJ. or as defined by steps 47.
49 For each row retrieved by step 23, the operation in step 48 was performed to find a matching row.
50 Every row in the table SYS.SYS_TEMP_0FD9FC8FB_DC4EE804 is read.
51 A view definition was processed, either from a stored view WEIJ. or as defined by steps 50.
52 For each row retrieved by step 49, the operation in step 51 was performed to find a matching row.
53 The rows from step 52 were inserted into using direct-load insert.
54 Every row in the table SYS.SYS_TEMP_0FD9FC8FC_DC4EE804 is read.
55 A view definition was processed, either from a stored view WEIJ. or as defined by steps 54.
56 Rows were retrieved using the unique index Partitions determined by Key Values.
57 Rows from table Partitions determined by Key Values were accessed using rowid got from a local (single-partition) index.
58 PARTITION LIST SINGLE
59 A range of partitions of steps 58 were accessed..
60 For each row retrieved by step 55, the operation in step 59 was performed to find a matching row.
61 Every row in the table SYS.SYS_TEMP_0FD9FC8FC_DC4EE804 is read.
62 A view definition was processed, either from a stored view WEIJ. or as defined by steps 61.
63 Return all rows from steps 60, 62 - including duplicate rows.
64 TEMP TABLE TRANSFORMATION
65 Rows were returned by the SELECT statement.