Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Thinking further, I believe your approach has a fundamental flaw. If Viktors tried the single-threaded batch-insert method and had i/o wait times, that could be caused by an inefficient insert method and over-commiting (log file sync waits). The most important step ought to be to understand the Oracle mechanisms and choose the most appropriate one first, surely?
You know that with logging disabled, a media failure between the load and the completion of the first subsequent backup will leave the entire table, or sections of it in the case of a direct path insert, unrecoverable, right?
With an append hint, all but one of those threads are going to be idle due to exclusive locking. I don't think this code is at a stage of efficiency where system-level tuning is required -- it's the methodology itself that is flawed.
