There's a big clue in the Oracle Documentation for SQL*Loader that states :
"A key point when using multiple INTO TABLE statements is that field scanning continues from where it left off when a new INTO TABLE statement is processed."
That is, the second INTO TABLE will NOT start...
This can be a frustrating issue, but here's some info that might help.<br><br>Every time a user locks a table for DML ( insert, update, delete ) an entry will appear in v$lock. This view contains a column called id1, which is the object id of that table. As soon as the user...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.