Maribel
07 de Julio del 2003

ORA-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION



How to Monitor User Tables which have been modified?

Hi,
What is the best way (requires the least amount of resources) to monitor tables that have been updated during a particular period.

Is there a single VIEW which captures this? or
Do I have to create individual triggers per table? (ouch) or
Can I use FGAC?

I am using 9i.


Hi,

Actualmente tenemos instalada la version 8.1.7.4, despues del Upgrade
hemos comenzado a tener problemas en las cargas que son realizadas mediante
exchage partition..

alter table TABLE_FIN
exchange partition P200307_27
WITH TABLE TABLE_AUX
including indexes;

ORA-14642: Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

Los indices de ambas tablas tienen las mismas caracteristicas.
Investigando he encontrado que puede deberse al valor del parametro RECORDS_PER_BLOCK.
Efectivamente el valor en las dos tablas es diferente..
Existe la opcion de ejecutar el comando : alter table TABLE_NAME minimize records_per_block;
pero en tablas con un numero de registros mayor demora bastante..

Otra opcion es crear de nuevo la tabla, lo q implica tener un espacio suficiente para poder duplicarla..

¿alguien ha tenido este tipo de error?..

Creo q esta considerado como un Bug de Oracle. ¿se sabe alguna cosa con respecto al tema?..

Saludos


At the moment we have installed version 8.1.7.4,

We have begun to have problems in the loads
that are made by means of exchage partition..

alter table TABLE_FIN
exchange partition P200307_27
WITH TABLE TABLE_AUX
including you index;
Ora-14642: For Bitmap index mismatch tables in
ALTER TABLE EXCHANGE PARTITION The indices of both tables have the same characteristics.

Investigating I have found that it can be due to the value of parametro RECORDS_PER_BLOCK.
Indeed the value in the two tables is different.
The option exists to execute the commando:
alter table TABLE_NAME minimize records_per_block;
but in tables with I number of registries greater delay enough.
Another option is to create the table again, the q implies to have a
space sufficient to be able duplicarla..

somebody has had east type of error ?
I create considered q this like a Bug de Oracle.
some thing with respect to the subject is known?
.. Greetings

Maribel