Oracle, Strange results with Oracle 8.1.7 and statistic gathering dbms_stats vs dbms

Strange results with Oracle 8.1.7 and statistic gathering dbms_stats vs dbms_utility

Author	Message
mart #1 / 3	Strange results with Oracle 8.1.7 and statistic gathering dbms_stats vs dbms_utility We have a customer with a large app using WebSphere and Oracle 8.1.7. They run: exec dbms_utility.analyze_schema('SAP', 'COMPUTE'); weekly. We recently ran: dbms_stats.gather_schema_stats(ownname=>'SAP';) on our test system and saw HUGE improvements in speed. Why is this? What is the difference between the two. Please help and advise. Martin Folb WGCUSA
Mon, 21 Mar 2005 04:38:02 GMT

Daniel Morga #2 / 3	Strange results with Oracle 8.1.7 and statistic gathering dbms_stats vs dbms_utility Quote: > We have a customer with a large app using WebSphere and Oracle 8.1.7. > They run: > exec dbms_utility.analyze_schema('SAP', 'COMPUTE'); weekly. > We recently ran: > dbms_stats.gather_schema_stats(ownname=>'SAP';) > on our test system and saw HUGE improvements in speed. > Why is this? What is the difference between the two. > Please help and advise. > Martin Folb > WGCUSA Oracle only keeps the dbms_utility_analyze, and the other anlayze methods, around for purposes of backward compatibility. They are for all intents and purposes desupported and don't handle new features. But I would suggest, in the future dbms_stats.gatehr_schema_stats(ownname=>'SAP', cascade=TRUE) so that it will also analyze the indexes. Daniel Morgan
Mon, 21 Mar 2005 23:33:54 GMT

Paul Dra #3 / 3	Strange results with Oracle 8.1.7 and statistic gathering dbms_stats vs dbms_utility Quote: > > We have a customer with a large app using WebSphere and Oracle 8.1.7. > > They run: > > exec dbms_utility.analyze_schema('SAP', 'COMPUTE'); weekly. > > We recently ran: > > dbms_stats.gather_schema_stats(ownname=>'SAP';) > > on our test system and saw HUGE improvements in speed. > > Why is this? What is the difference between the two. > > Please help and advise. > > Martin Folb > > WGCUSA > Oracle only keeps the dbms_utility_analyze, and the other anlayze > methods, around for purposes of backward compatibility. They are for all > intents and purposes desupported and don't handle new features. > But I would suggest, in the future > dbms_stats.gatehr_schema_stats(ownname=>'SAP', cascade=TRUE) > so that it will also analyze the indexes. > Daniel Morgan exec dbms_stats.gatehr_schema_stats(ownname=>'SAP', cascade=>TRUE); the '>' is required there. Make sure that you don't use a mix of stats gathered by the 2 methods. also, are you certain that the parameters for 'optimizer%' are the same? Paul
Tue, 22 Mar 2005 11:12:36 GMT

Page 1 of 1

[ 3 post ]