SQL loader in SSIS fail when running via SQL Server Agent
Hi all, I use Execute Process Task to execute SQL Loader to load data from text to Oracle and it's work fine when executing SSIS package from BIDS and Integration Service in Management Studio. But when I create a SQL Server Agent job to execute the same package I found that job failed in Execute Process Task step with exit code = 4. I already set file permission in data file path and Oracle path but still cannot eliminate the error. So could you please give the suggestion, You can see job log below for more detail. Thank you in advance. =========================================== Source: EPR_TMP_SRC_POINTTRANSACTION Execute Process Task Description: In Executing "D:\oracle\product\11.2.0\client_1\BIN\sqlldr.exe" "parfile="D:\SSIS\U-Marketing\Configurations\loader.par" control="D:\SSIS\U-Marketing\Configurations\TMP_SRC_POINTTRANSACTION.ctl" LOG="D:\SSIS\U-Marketing\Logs\TMP_SRC_POINTTRANSACTION.log"" at "D:\oracle\product\11.2.0\client_1\BIN\", The process exit code was "4" while the expected was "0". End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 3:13:24 PM Finished: 3:15:32 PM Elapsed: 127.765 seconds. The package execution failed. The step failed.
July 19th, 2012 5:15am

check if the paths you are reading in the package are valid in the server, if they are existing in the server or not. Also, you should use UNC paths instead of DFC paths while putting some network folder in SSIS with proper read/write permission. regards joon
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2012 5:19am

Source file was stored in the ETL server (local server) so I cannot use UNC paths. Any idea about this issue? Please suggest.
July 19th, 2012 5:28am

we faced some thing similar, later we found that we had given permission(full control, read, write) but we had not shared the folder to the user under which the sql job(sql engine) runs in that server. It is always the access or network issue for issues regarding this. Hope you can check these things in detail. regards joon
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2012 5:32am

we faced some thing similar, later we found that we had given permission(full control, read, write) but we had not shared the folder to the user under which the sql job(sql engine) runs in that server. It is always the access or network issue for issues regarding this. Hope you can check these things in detail. regards joon
July 19th, 2012 5:34am

Thank a lot Joon84, it's working! I only give permission(full control) to network service and sql server accout the folder and it's working.
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2012 12:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics