Could someone explain why when I execure the following command in my
VB code I get no log file whereas when I call it within a bin file I
get a log file.

sControlFolder = ""C:\TEMP\"

SQLLDR EQRISK/eq control=" & sControlFolder &
"InstrumentComposition.ctl

(in the bin file I have)

sqlldr userid=eqrisk/eq control=instrument.ctl

colmkav wrote:
> Could someone explain why when I execure the following command in my
> VB code I get no log file whereas when I call it within a bin file I
> get a log file.
>
> sControlFolder = ""C:\TEMP\"
>
> SQLLDR EQRISK/eq control=" & sControlFolder &
> "InstrumentComposition.ctl
>
> (in the bin file I have)
>
> sqlldr userid=eqrisk/eq control=instrument.ctl
>

You have two different control file specified here. Are the contents
identical? How do they differ with respect to logging?

Cheers,
Brian

--
================================================== =================

Brian Peasland
dba@nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown

--
Posted via a free Usenet account from http://www.teranews.com

Sorry it should read the same file. I know that I can specify the log
file by saying log=filename.

However, it seems strange that the logfile is not created by default
like it is when running from a bat file.

Perhaps it is being created in some other folder but all the likely
default folders I look in I dont see it.


On 21 Jun, 20:02, Brian Peasland <d...@nospam.peasland.net> wrote:
> colmkav wrote:
> > Could someone explain why when I execure the following command in my
> > VB code I get no log file whereas when I call it within a bin file I
> > get a log file.
>
> > sControlFolder = ""C:\TEMP\"
>
> > SQLLDR EQRISK/eq control=" & sControlFolder &
> > "InstrumentComposition.ctl
>
> > (in the bin file I have)
>
> > sqlldr userid=eqrisk/eq control=instrument.ctl
>
> You have two different control file specified here. Are the contents
> identical? How do they differ with respect to logging?
>
> Cheers,
> Brian
>
> --
> ================================================== =================
>
> Brian Peasland
> d...@nospam.peasland.nethttp://www.peasland.net
>
> Remove the "nospam." from the email address to email me.
>
> "I can give it to you cheap, quick, and good.
> Now pick two out of the three" - Unknown
>
> --
> Posted via a free Usenet account fromhttp://www.teranews.com

On Thu, 21 Jun 2007 23:56:02 -0700, colmkav <colmjkav@yahoo.co.uk>
wrote:

>Sorry it should read the same file. I know that I can specify the log
>file by saying log=filename.
>
>However, it seems strange that the logfile is not created by default
>like it is when running from a bat file.
>
>Perhaps it is being created in some other folder but all the likely
>default folders I look in I dont see it.

Either your VB code is incorrect, or it is a VB problem.
Sqlldr doesn't run 'by default' from VB but from a DOS box.
And in a DOS box sqlldr *does* generate a log file!
Apart from that, you failed to specify both database version and O/S
version, so who can tell what is going on? Maybe it is a known
problem, but as your post is incomplete and inaccurate (you are
missing out a closing " in your VB command) you won't get any
responses.

--
Sybrand Bakker
Senior Oracle DBA

colmkav (colmjkav@yahoo.co.uk) wrote:
: Could someone explain why when I execure the following command in my
: VB code I get no log file whereas when I call it within a bin file I
: get a log file.

: sControlFolder = ""C:\TEMP\"

: SQLLDR EQRISK/eq control=" & sControlFolder &
: "InstrumentComposition.ctl

: (in the bin file I have)

: sqlldr userid=eqrisk/eq control=instrument.ctl

Perhaps you need to escape the back slashes, or perhaps you can use
forward slashes (often works even in dos from within applications).

change C:\TEMP\ to C:\\TEMP\\ or C:/TEMP/

$0.10