Read part 1 of this tip.
In the last tip we talked about what is a "fan trap" in a business intelligence application. Here we discuss the automated resolution for "fan traps" included by Oracle in its Oracle Discoverer Tool Suite.
Discoverer comes with fan trap detection capability in its client tool. Each user can choose to enable or disable this feature.
- If your query contains only aggregates on the tables you are joining, then Discoverer will handle the aggregate calculations by rewriting your query for you -- very nice!
- If, however, your query contains details from those tables you are joining, then Discoverer will prevent you from doing this.
Here are some guidelines if you are running Oracle Discoverer:
- When developing reports, leave fan trap detection enabled. This ensures that you do not create a fan trap. Of course this means that you may have to rewrite your query once you are warned by Discoverer that you have one. However, if the fan trap cannot be removed, then checking the "disable" box will permit you to continue working on the report.
- When testing check "disable fan-trap detection" and leave it checked; it does not interfere with reports that do not incorporate fan traps and permits you to run those that do.
For more
Requires Free Membership to View
When you register, you'll begin receiving targeted emails from my team of award-winning editorial writers on the latest customer relationship management (CRM)and call center technology issues today. Our goal is to keep you informed on the hottest issues facing this fast-changing industry.
Hannah Smalltree, Editorial Director
This was first published in September 2002
Join the conversationComment
Share
Comments
Results
Contribute to the conversation