Oracle SQL*Loader

[MarkPare]

Hello, I am running Windows 2000 and when I issue a SQL*Loader using a Windows .bat file, for some reason, when the SQL*Loader process is finished, the window does not close. I tried setting the "Close on Exit" option that used to exist in prior versions of Windows but that doesn't work.

My .bat file is:

sqlldr80.exe userid=xx/yy@zz control=aa.ctl log=bb.log
exit

I am running Oracle 8.0.6.0.0

Any help would be greatly appreciated. Thanks

 

[comgrit]

this is nothing to do with Oracle SQL*Loader - it is more on how Windows manage the DOS batch file.

I don't have the Win2000 to test with. But i think it might worth to try the PIF file that point to the BAT file instead.

Good luck.

 

[MarkPare]

I tried what you said and created a PIF file and had:

sqlldr80.exe userid=xx/yy@zz control=aa.ctl log=bb.log on the Cmd line option in the Program tab. I also had Close on Exit checked and the SQL*Loader process still hangs there when it finishes the import.

Anyone with any other ideas or have I used the previous suggestion wrong?

 

[Beantree]

I have 8.17 on W2K server.

I usually run SQLLDR through sheduled tasks, which opens a command windowe, exectutes, then closes.

I just tried taking the command line from one of the scheduled tasks, and making a bat file out of it.

It behaved the same, opened, executed, and closed.

 

[MarkPare]

Beantree, thanks for your suggestion. I tried what you described and when the task was running via, c:\winnt\system32\mstask.exe, it again just stopped at the end of the SQL*Loader process without closing the window.

Could there be permission problems with my Oracle account? What about Windows account permissions? What about something in Environment variables?

Still looking...

 

[stlnetengr]

MarkPare,
I too am running 8.0.6.0 and have ran into the same problem. I have to ^C to get out of the batch job and then it prompts if I want to continue... I have more than one sqlldr80 command in the batch file.

I know it's been a while since your question was posted, but have you found a solution?

It's possible that the new version mentioned in this thread may have resolved this problem.

Any assistance would be appreciated.