I know I have raised this in the past, but just had to import 136654 rows (of 10 simple fields) into an empty table.

Still chuntering along, now looking to be complete in over the hour.

This time with the ODBC importer, but comparable with the text inmporter.

Have you had a chance to review the processing, as this not acceptable performance, and this time SQL Developer is not an option, as on an Oracle 8 database.

Thanks


Chris

Can you check in the database if the import is still loading records? In other words: is it slow or has it stopped?

It is loading records. Initially the count goes up, and one can estimate the time remaining fairly accurately. Sometimes, but not always the count ceases to display, but the load seems to continue at the same rate.

This is not a new problem - I have reported this a number of times before

Thanks


Chris

hi, I registered just to chip in on this.

If you're importing a large number of records (>5000), use sqlldr which is the command line tool (it probably calls the same libraries) for which every Oracle consultant since the year dot carried a manual in their car.

Check it out on the web and particularly look at direct=true parameter.

136k rows would take around 30 seconds in my experience. Setup for a 10 field table (you have to map the data file so SQLLDR knows how to process it) would take a few minutes at most. Dates and non-integer numbers need a little care, varchar2 are mapped as CHAR and numbers without precision are mapped as EXTERNAL INT...and your needs to be in a csv.

SQLLDR should be in your Oracle client installation and accessible from the command line.

The reason PLSQL Dev import is slow is that it's committing each batch of data but if your data is uniform, there's no need to do this. (And also I don't think the memory management is quite right.)