BLOCKS and NUM_ROWS

[cbroers]

Hi there,

we are currently using your TOracleDirectPathLoader component. We have one issue about this component. At the moment we insert only one (or a few) rows the ratio between BLOCKS and NUM_ROWS is not good. When i insert only one row, also on block is created. This seriously affects the performance of our oracle system. Do you have a work-around for this issue?

regards,

chris broers

 

[Marco Kalter]

For problems at this physical database level you will need to contact your Oracle Support representative. The TOracleDirectPathLoader component, or any other OCI-level application, does not work on this level. It merely sends data to the server.

 

[al0]

Direct path load in Oracle is intended and optimized formass load. There is no sense to use it for inserting of couple of rows. Use normal inserts instead. Check "Direct path INSERT" topic in Oracle Concept guide (part of Oracle documentation set, available from otn.oracle.com).

Originally posted by cbroers:
Hi there,

we are currently using your TOracleDirectPathLoader component. We have one issue about this component. At the moment we insert only one (or a few) rows the ratio between BLOCKS and NUM_ROWS is not good. When i insert only one row, also on block is created. This seriously affects the performance of our oracle system. Do you have a work-around for this issue?

regards,

chris broers

 

[cbroers]

The problem is, i can't be sure if there are only a few records or thousands. And what are the minimum amount of rows etc. Therefor, i can't predict whether or not it would be convenient to use Direct Loader or 'normal' inserts.