How to migrate the Batch Jobs schedules to another server

system · February 13, 2014, 7:26pm

Hi Gurus,
I have a requirement of moving all the BODS Jobs and contents from one server to another, including the Job schedules. I can use import and export for all the BODS Jobs and Projects but for the schedules what needs to be done to make sure all the schedules are present in the new environment and will start working after the migration.

Thanks,
Deepak N.

deepak_n01 (BOB member since 2008-07-22)

system · February 14, 2014, 3:46am

You could try copying the export execution command files. This would ONLY work if you did a global search/replace on the server/database specific information within the files. It may not work if the GUID is used in the file and if the GUID of the job changes when it is exported/imported.

To be on the safe side I would manually export all the export execution commands on the new server.

eganjp (BOB member since 2007-09-12)

system · February 15, 2014, 10:45pm

Thanks for your response Jim! Appreciate it!

deepak_n01 (BOB member since 2008-07-22)

system · February 16, 2014, 9:08pm

Hi Jim,
Another question. What should we do to retain the CUID of the Jobs? We have some jobs in the BODS which kicks off other Jobs using exec cmd line command and their bat file. If we export the jobs into the other repository, wont the CUID changes? and these jobs wont kick off? What should we do to handle this situation?

Thanks,
Deepak N.

deepak_n01 (BOB member since 2008-07-22)

system · February 17, 2014, 2:58am

The GUID may change. I don’t know for sure if it will. When you import a job into a repository where the job already exists (like from development to production) the GUID doesn’t change. But I don’t know how that works when migrating into an empty repository. I suspect that it will retain the GUID from the import file, but you need to verify that.

eganjp (BOB member since 2007-09-12)

system · February 17, 2014, 6:22am

Verification is always good! But…

I am pretty sure that it will not change. It has given problems in the past where the GUIDS stayed the same and the job server got confused which guid belonged to which repository…

Johannes Vink (BOB member since 2012-03-20)

system · February 17, 2014, 1:51pm

You can try to reference the job by name using a -s switch.
(I remember running into a problem using it though)

jlynn73 (BOB member since 2009-10-27)

system · February 18, 2014, 10:52pm

Thanks for your ideas! Appreciate it! But the thing is there are a lot of Jobs which calls other Jobs using the generated bat file and without retaining the GUID, it will be hard to manually update and setup all the schedules again. So, there is no other option to retain the GUID? I know you can retain the ID in business objects, why not in DS?

Thanks,
Deepak N.

deepak_n01 (BOB member since 2008-07-22)

system · February 18, 2014, 10:53pm

If you are using the generated file name to call a job then there shouldn’t be a problem. The file name won’t change or you can simply export the job again and use the same file name.

eganjp (BOB member since 2007-09-12)

system · February 18, 2014, 11:07pm

Hi Jim,
The issue is, I have migrated these Jobs to a different server, where when I try to create the bat file once again, it has a different name because the GUID is changed for this Job.

Thanks,
Deepak N.

deepak_n01 (BOB member since 2008-07-22)

system · February 18, 2014, 11:10pm

Are you creating these as scheduled jobs? If you create them as Export Execution Command files then you can create them with whatever file name you choose.

eganjp (BOB member since 2007-09-12)

system · February 18, 2014, 11:31pm

Yes, these are created as scheduled Jobs, not using Export Execution command. So we don’t have a control in changing the file names.

Thanks,
Deepak N.

deepak_n01 (BOB member since 2008-07-22)

system · February 18, 2014, 11:44pm

I can come up with a number of crazy ways to make this work. None of them are ones that a reasonable ETL Developer would want to use.

Leading the list of crazy: Update AL_LANG and set the GUID back to the original value in the old repository.

eganjp (BOB member since 2007-09-12)

system · February 18, 2014, 11:50pm

well, I guess we gotta do what we gotta do! Thanks for your inputs Jim…It just sucks that I have to do this for multiple jobs. wish there was an easier way.

Thanks,
Deepak N.

deepak_n01 (BOB member since 2008-07-22)

system · February 18, 2014, 11:57pm

Unfortunately, updating the GUID IS the easy way. It’s just not a solution that anybody would want to use because it would never be supported by SAP.

eganjp (BOB member since 2007-09-12)

system · February 19, 2014, 12:04am

Agreed!

Thanks,
Deepak N.

deepak_n01 (BOB member since 2008-07-22)

system · May 7, 2018, 4:48pm

Can someone explain elaborate more on how to migrate Schedules onto new server?
I appreciate your help.

s_iska (BOB member since 2009-08-21)

system · May 7, 2018, 4:53pm

The simple answer is that you can’t, or at the very least you shouldn’t. There is server-specific information embedded in the generated schedule file.

Read through the entire thread and post back if you have specific questions.

eganjp (BOB member since 2007-09-12)

system · May 8, 2018, 1:08pm

My suggestion is to migrate to an enterprise job scheduler.

I’ve got 14,059 jobs in my scheduler database and migrating to and from is easy.

jlynn73 (BOB member since 2009-10-27)

system · May 8, 2018, 1:50pm

Every client I go to I try to get them to do just that. The small ones can’t justify the cost or the time needed to come up to speed on it. it’s hard to get across to them that they’ll have to spend the time one way or another. Sure I can write a “scheduler” in Data Services. But it won’t be anywhere as robust as an enterprise scheduler.

eganjp (BOB member since 2007-09-12)