Well, if it is possible (that is : if you are the creator of the text file), I would put :
Insert into x values( 1, TO_DATE('01-FEB-2005', 'DD-MON-YYYY'), 7 , ....);
Remember explicit convertions are ALWAYS MUCH BETTER than implicit ones. One day you'll forget to alter your session and insert incorrect data .
Furthermore, I agree with WilliamR : it is a good habit always to precise the columns in an insert statement (though it was not your primary point, WilliamR, was it ? ). Therefore you won't have to recode your statements if you add a column to the table (unless it is a NOT NULL column of course), and you won't have problems if you ever change the order of columns in your table.
Concerning CURSOR_SHARING, FORCE may help you in such a case (many insert statements with different values) because it will avoid flooding the shared pool with many insert statements that won't ever be reused and potentially kick out of the shared pool other statements that would need to stay in there since they are reused frequently. It will also help a little performance-wise, as WilliamR said, because it will reuse the same context for all these insert statements, doing "soft parses" instead of "hard parses".
HTH & Regards,
Last edited by RBARAER; 12-12-05 at 06:44.
Reason: Agree with WilliamR
ORA-000TK : No bind variable detected... Shared Pool Alert code 5 - Nuclear query ready .