Hi,

We are using OWB as the ETL tool for the Data load into our Warehouse. We are facing two critical issues with respect to Space consumption.

1. Number of extents for tables are growing after each load even though there was lot of free space between the extents. Oracle is not using the blocks in the free list when data is being loaded rather it is creating more number of new extent. This leads to excessive space consumption for the table and the tablespaces are getting full quickly.

2. Size of Bitmap indexes are growing abnormally. Indexes are occupying more space than it has to. Bitmap indexes which were occupying 15 MB of data dramatically increases to around 5 Gb after the load. This behavior was observed when OWB mappings fail over to row based and perform insert/updates in row based mode on indexed columns.

Looking for an advice on these issues on how to manage space.


Thanks
- Partha



Confidentiality Notice

The information contained in this electronic message and any attachments to this message are intended
for the exclusive use of the addressee(s) and may contain confidential or privileged information. If
you are not the intended recipient, please notify the sender at Wipro or [Email address protected] immediately
and destroy all copies of this message and any attachments.

Oracle LazyDBA home page