Comments on: BAAG is born http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/ Home of the BAAG Party Fri, 21 Nov 2008 07:22:05 +0000 http://wordpress.org/?v=2.2 By: Alex Gorbachev http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-180 Alex Gorbachev Fri, 12 Oct 2007 03:49:30 +0000 http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-180 You must be right and I should have said 42 mph. :) Anyway, welcome to the club! You must be right and I should have said 42 mph. :) Anyway, welcome to the club!

]]> By: CrazyGuyOnABike http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-179 CrazyGuyOnABike Fri, 12 Oct 2007 02:13:50 +0000 http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-179 "Imagine you are riding a bike with 100 km/h and in front of you is a blind summit" Actually, a condition known as "Death wobble" can kick in at around 80 kmph. I experienced moderate wobble at 50.9 mph descending PA St Rt 31 just east of the Laurel Highlands. So I can't imagine riding at 100 kmph under any conditions on a bicycle, thanks. CrazyGuyOnABike “Imagine you are riding a bike with 100 km/h and in front of you is a blind summit”

Actually, a condition known as “Death wobble” can kick in at around 80 kmph. I experienced moderate wobble at 50.9 mph descending PA St Rt 31 just east of the Laurel Highlands. So I can’t imagine riding at 100 kmph under any conditions on a bicycle, thanks.

CrazyGuyOnABike

]]> By: Alex Gorbachev http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-4 Alex Gorbachev Sun, 24 Jun 2007 18:44:23 +0000 http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-4 Thanks for your comment Ben. In this case, there are options to investigate that. Almost certainly it would be CBO estimating cost incorrectly or Oracle performing access to a fixed table ineffectively. Different techniques can be applied here -- 10053 trace, hinting and comparing the costs, 10046 trace, etc. Searching Metalink and Google is a great idea but it might result in completely irrelevant fixes because people are looking for a ready to apply solution as if Google and Metalink can diagnose the issue instead of an analyst. Google/Metalink should rather provide more details to aid the research. Educated Guess? Often it's not easy to distinguish educated guess from gut feeling or simply wild guess. Assumption is a good term and it must be verified before relying on it. Thanks for your comment Ben.

In this case, there are options to investigate that. Almost certainly it would be CBO estimating cost incorrectly or Oracle performing access to a fixed table ineffectively. Different techniques can be applied here — 10053 trace, hinting and comparing the costs, 10046 trace, etc.

Searching Metalink and Google is a great idea but it might result in completely irrelevant fixes because people are looking for a ready to apply solution as if Google and Metalink can diagnose the issue instead of an analyst. Google/Metalink should rather provide more details to aid the research.

Educated Guess? Often it’s not easy to distinguish educated guess from gut feeling or simply wild guess. Assumption is a good term and it must be verified before relying on it.

]]> By: Ben http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-3 Ben Sun, 24 Jun 2007 17:08:34 +0000 http://www.BattleAgainstAnyGuess.com/2007/06/baag-is-born/#comment-3 Not guessing at all would imply there is always a fool-proof method to determine exactly what the problem is. But there's no such thing thing, is there? You may for example, determine that a dictionary query is slow due to a FTS instead of doing index-lookups. But you wouldn't know exactly why it's doing that until you guess at a few possible causes, and try out a few solutions. Especially if it's caused by a bug. It's no different when searching Metalink for possible solutions, and guessing what you have found (and it's recommended solution) may be the answer to your problem. Sometimes Metalink may provide a method for determining if it is the same problem, but many other times you just have to guess. I see where you are coming from, and while one should avoid wild guesses, making a educated guess is a valid method in problem solving. Not guessing at all would imply there is always a fool-proof method to determine exactly what the problem is. But there’s no such thing thing, is there? You may for example, determine that a dictionary query is slow due to a FTS instead of doing index-lookups. But you wouldn’t know exactly why it’s doing that until you guess at a few possible causes, and try out a few solutions. Especially if it’s caused by a bug. It’s no different when searching Metalink for possible solutions, and guessing what you have found (and it’s recommended solution) may be the answer to your problem. Sometimes Metalink may provide a method for determining if it is the same problem, but many other times you just have to guess. I see where you are coming from, and while one should avoid wild guesses, making a educated guess is a valid method in problem solving.

]]>