SAP Data Services Job Scheduler is not working not executing

[former_member397022]

Hi All,

Have an issue with job scheduler.

I scheduled a job in Data Services Management console using Data Services Scheduler. The .bat and .txt files are created in the scheduler location, and it seems like they are executing, but nothing happens on BODS 4.1 side. I tired executing it manually and log file shows that job started but in reality nothing happens.

Also want to mention that on DEV side everything works perfect but on Production I'm having this issue.

Any help will be greatly appreciated!

Here is the log file.

AL_RWJobLauncherLog.txt

--------------------------
(14.1.1.210) 05_03_2013 23:55:00 (3448):  CRWJobLauncherApp::InitInstance called.
(14.1.1.210) 05_03_2013 23:55:02 (3448):  Launching Job (no wait, no status).  inet address <inet:PTCDSRPROD01:3500>, GUID <ad25b241_53fd_4cbd_9708_10c8353dfd68>. (BODI-1250134)
XML_REQUEST:
(14.1.1.210) 05_03_2013 23:55:02 (3448):  <?xml version="1.0" encoding="UTF-8"?>
<DSAdminServiceRequest xmlns="http://www.sap.com/DataServices/DSAdminServiceXSD">
<RunBatchJob>
<GUID>ad25b241_53fd_4cbd_9708_10c8353dfd68</GUID>
<RepoName>ds_prd_local_repo</RepoName>
<JobServer>PTCDSRPROD01:3500</JobServer>
<JobCommandLine><![CDATA[ -BOESPTCDSRPROD01 -BOEAsecEnterprise -BOEUAdministrator  -SPTCBOBDBP1 -NMicrosoft_SQL_Server -Ueim_admin_prd  -G"ad25b241_53fd_4cbd_9708_10c8353dfd68" -t5 -T14 -GV"$JobRunID=am9iX3J1bl9pZCggKQ;$G_MatchAccGrp_1_2=J1kn;$G" -GV"_MatchAccGrp_3=J1kn;$G_MatchAccGrp_4=J1kn;$G_CustomerMa" -GV"ster_Stg=J1kn;$G_MatchGlobal=J1kn;$FaildRecordPath=J0Q6" -GV"XFZhbGlkYXRpb25GYWlsZWRSZWNvcmRzJw;$G_CleansingProposal" -GV"s=J1kn;"   -CtBatch -CmPTCDSRPROD01 -CaAdministrator -CjPTCDSRPROD01 -Cp3500 ]]></JobCommandLine>
</RunBatchJob>
</DSAdminServiceRequest>

Launch response:
(14.1.1.210) 05_03_2013 23:55:02 (3448):  <?xml version="1.0" encoding="UTF-8"?><DSAdminServiceResponse xmlns="768866ds_prd_local_repoPTCDSRPROD01:35000http://www.sap.com/DataServices/DataServicesXSD"><RunBatchJ...>
(14.1.1.210) 05_03_2013 23:55:02 (3448):  Job has started.  inet address <inet:PTCDSRPROD01:3500>, GUID <ad25b241_53fd_4cbd_9708_10c8353dfd68>. (BODI-1250135)

[former_member397022 · Accepted solution]

OK here is the resolution we found, seems like a bug in 4.1.

so the text file is missing Repository name, to fix it just add the repo name at the end.

[Former Member]

Hello Vlad,

     All jobs are executing manually and also in the Development environment. This issue is happen in quality environment and the BODS version here we are using is 4.0 SP03 patch 1.

Regards,

Vipin

[former_member397022]

what i ment buy manualy, if you can execute DI__2c72ce5a_6ea9_4db3_bc2e_8f9b4c50f940_1276484870_r_0_w_n_7_57.sh file from command line and see if the job is starting.

[Former Member]

Hello Vlad,

I'm also experincing the same issue what Vipin is facing, i tried all the solutions which you provided.

I executed the job manualy by commond line (DI__2c72ce5a_6ea9_4db3_bc2e_8f9b4c50f940_1276484870_r_0_w_n_7_57.sh) and job is started, i see admin console the job is running.

My Environment is

Repository Database : Oracle

BODS Version: XI 3.2 (R 12.2.2.3)

OS : Linux

Is it require to change any parameters to trigger the jobs in Admin Console automatically.

Thanks in advance!!

Thanks,

Tirupathirao

[former_member397022]

Hi Tirupathirao,

I'm not sure how Linux scheduler works, but in windows, the issue was the that the scheduler was executing the .bat file with less parameters required to execute the job.

If you were able to execute the file manually and the job was started, look into the command like in scheduler which triggers that file. see if it points to the right file. 

[Former Member]

Same scheduler error is getting in BODS version 4.0 SP03 patch 1 and repository name is already added in the specified file.  Scheduler are working fine in Development and problem is for quality environment . Is there anything more for version 4.0 ?

DI__2c72ce5a_6ea9_4db3_bc2e_8f9b4c50f940_1276484870_r_0_w_n_7_57.sh 

  ksh /sapdata/dataservices/bin/AL_RWJobLauncher.sh
"/sapdata/dataservices/log/otdsqd01_job_server1/"
"inet:otdsqd01:3500" " -ScheduleID 1276484870_r_0_w_n_7_57
-PLocaleUTF8  -Sotbodd02 -NsecEnterprise -Q"DS4_Repository"
-UAdministrator -PTWFzdGVyMTFfIw
-G"2c72ce5a_6ea9_4db3_bc2e_8f9b4c50f940" -r1000 -T14
-ClusterLevelJOB
-GV\"\$GV_SITE=bnVsbA;\$GV_SEQ_NO=bnVsbA;\$GV_Count=TlVMTA;\$GV_\"  -GV\"File_Name=bnVsbA;\

$GV_Count_Err=bnVsbA;\$GV_Sys_Date=bnVs\"
-GV\"bA;\$GV_File_Name1=bnVsbA;\"    -CtBatch -Cmotbodd01 -CaAdministrator
-Cjotdsqd01 -Cp3500 "

[former_member397022]

Hi,

Did you try to manually execute that batch file, and see if the job is
starting? this will help you understand if the problem is with the file or
windows scheduler. i had some issues with permissions for that folder