	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.3

Tuning of query.

Asked by vamsibat in Oracle 10.x, PL / SQL, Oracle 9.x

Earlier my cursor query is SELECT b.mbr_sid
FROM mbr_identifier a, MEMBER b
WHERE a.oprtnl_flag = 'A' AND
a.idntfr = LPAD (TO_CHAR (p_assistance_unit_id), 9, '0') AND
a.idntfr_type_cid = 64 AND
a.TO_DATE >= pk_mbr_global.g_cycle_date AND
a.mbr_sid = b.mbr_sid
FOR UPDATE OF b.mbr_sid

This query is retuning more than one mbr_Sid which is creating insiede cursor loop duplicate records.

To avoid duplicates i have chnaged cursor query to below
SELECT b.mbr_sid
FROM mbr_identifier a, MEMBER b
WHERE a.oprtnl_flag = 'A' AND
a.idntfr = LPAD (TO_CHAR (p_assistance_unit_id), 9, '0') AND
a.idntfr_type_cid = 64 AND
a.TO_DATE >= pk_mbr_global.g_cycle_date AND
a.mbr_sid = b.mbr_sid
and a.rowid = (select max(a2.rowid)
FROM mbr_identifier a2, MEMBER b2
WHERE a2.idntfr = LPAD (TO_CHAR (p_assistance_unit_id), 9, '0') AND
a2.idntfr_type_cid = 64 AND
a2.oprtnl_flag = 'A' AND
a2.TO_DATE >= g_cycle_date AND
a2.mbr_sid = b.mbr_sid)
FOR UPDATE OF b.mbr_sid.

It is not creating duplicates but peorformance wise this query is taking long time. it is not doing full tabel scan but taking long in real job which contains million recrods to be porcessed.Please let me know is there any other way to tune query so that performance will be good.

T

View the Solution FREE for 30 Days

20091021-EE-VQP-81 - Hierarchy / EE_QW_3_20080625

Hall of Fame

1. sdstuber197,647
2. mrjoltcola178,293
3. schwertner94,930
4. angelIII62,456
5. Andytw41,813
6. MikeOM_...34,372
7. markgeer33,944
8. awking0033,913
9. johnsone30,820
10. sujith8028,894
11. flow0125,070
12. nav_kum_v24,658
13. dvz23,865
14. Milleniuma...21,586
15. ravindran...21,319
16. rrjegan1721,250
17. HainKurt19,390
18. shru_0...17,540
19. it-rex17,391
20. slightwv16,868
21. Suresh_...16,325
22. Geert_Gr...15,929
23. MarkusId14,500
24. lwadwell13,100
25. FVER12,225

1. sdstuber746,958
2. angelIII368,491
3. schwertner336,042
4. sujith80217,290
5. mrjoltcola178,293
6. johnsone159,507
7. nav_kum_v159,413
8. MikeOM_...135,270
9. markgeer121,700
10. jinesh_ka...101,400
11. dvz97,388
12. slightwv85,063
13. jwahl79,295
14. awking0079,292
15. shajukg66,385
16. Milleniuma...59,183
17. YANN0S58,491
18. joebednarz52,716
19. sonicefu47,306
20. DrSQL46,091
21. Andytw41,813
22. paquicuba40,180
23. dbmullen40,074
24. LindaC34,991
25. rbrooker33,769

Tuning of query.

Asked by vamsibat in Oracle 10.x, PL / SQL, Oracle 9.x

About this solution