|
|||||||||
|
|||||||||
| |||||||||
|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
Be the architects of evolution and help create the mobile internet future. It’s your move---enter to win here! |
|
#2
May 26th, 2004, 09:19 AM
|
|||
|
|||
|
creating a log file when you are loading data into a table using SQL Loader is optional, don't use log file option with your command, now take a look,
SQLLDR userid=myid/myid control=myfile.ctl log=myfile.log In above command log=myfile.log creates a log file.
|
|
#3
May 26th, 2004, 09:22 AM
|
|||
|
|||
|
In my environment, it just does it by default.
I am not passing any 'log=' arguments to the command string. It just does it by itself, that is the problem. I thought there was a way to turn it off.
|
|
#4
May 26th, 2004, 11:10 AM
|
|||
|
|||
|
Sorry, log option is used to give a user defined name to log file, oracle automatically generates these files , i don't think so you can stop it.
|
|
| Viewing: Dev Shed Forums > Databases > Oracle Development > SQL*Loader Question |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
