Solved

What is the Haken Factor?

Posted on 2004-08-20
3
1,313 Views
Last Modified: 2008-01-09
We've encountered a problem with corrupt bitmap indexes on partitioned tables in Oracles 8.1.7.4. With Oracle's help we're making progress towards a solution, which appears to involve something called a 'Haken Factor'.

I gather this is an attribute of a table which is involved in sizing bitmap indexes, it appears in the SPARE1 column of sys.tab$.

Does anyone know anything about the Haken Factor, Metalink has quite a few references, Google almost nothing relevant. I can see that it's important, but I'm looking for a better explanation of what it is.
0
Comment
Question by:JR2003
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 23

Accepted Solution

by:
seazodiac earned 300 total points
ID: 11852275
check this out, something I came across on the web.


Hakan factor is a number used by the
bitmap index algorithms to limit the number
of rows that Oracle assumes can be stored
in a single block.  It is (generally) dictated at
table creation time by the number and type
of non-null columns.  Check tab$.spare1
just after creating a table.


Things can go wrong with partitioned tables,
though, as the table has a Hakan factor, but
in your case you've created a table to exchange
with it that has a different Hakan factor.


The closest reference to your problem comes
from (a) minimize_records_per_block, which
can only be used in the absence of bitmap indexes
on a table and resets the Hakan factor, and (b) a
note about dropping bitmap indexes before your
first compress a data segment in a partitioned
table.
0
 
LVL 35

Assisted Solution

by:Mark Geerlings
Mark Geerlings earned 200 total points
ID: 11854204
I can't answer your question exactly, but we also had some trouble with bit-mapped indexes in Oracle8.1.7.  I don't remember if they were on partitioned tables or not.  We ended up eliminating the bit-mapped indexes, because they caused more problems than they solved in our (mainly OLTP) system.  If you have a data warehouse, or if your bit-mapped indexes are limited to reporting tables that do not get concurrent inserts by multiple users, then you may want to keep your bit-mapped indexes.  We did try adjusting the spare1 column of sys.tab$ for those tables, but if I recall correctly that did not solve all of the problems.
0
 
LVL 18

Author Comment

by:JR2003
ID: 11870099
Thanks for your comments.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Working with Network Access Control Lists in Oracle 11g (part 1) Part 2: http://www.e-e.com/A_9074.html So, you upgraded to a shiny new 11g database and all of a sudden every program that used UTL_MAIL, UTL_SMTP, UTL_TCP, UTL_HTTP or any oth…
Configuring and using Oracle Database Gateway for ODBC Introduction First, a brief summary of what a Database Gateway is.  A Gateway is a set of driver agents and configurations that allow an Oracle database to communicate with other platforms…
This video explains at a high level with the mandatory Oracle Memory processes are as well as touching on some of the more common optional ones.
This video shows how to copy a database user from one database to another user DBMS_METADATA.  It also shows how to copy a user's permissions and discusses password hash differences between Oracle 10g and 11g.

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question