BODS Scheduled Jobs Don't Execute After Moving Databases

[tammy_datri]

I am fairly new to Data Services and I having issues scheduling jobs in the Data Services Management Console.

I recently moved my CMC and Repository databases to a different SQL Server.  I am able to connect to the new repository database within Data Services Designer and run my jobs interactively.  When I try to schedule a job in DS Management Studio, the job never executes.

I submitted a ticket to SAP support but was told that they no longer support this version of Data Services.  They suggested I do the following:

• Log on to the DS Managment Console
• Expand the list of repositories under Batch
• Click on my repository
• Click on Batch Job Configuration
• Click on "Export Execution Conmmand"
• Open Windows Explorer
• Navigate to ..\BusinessObjects Data Services\log
• Edit the .txt file for my scheduled job to show the new server name insead of the old one
• Execute the .bat file
• The job works fine when I execute the .bat file manually
• The job does not work if I try to schedule it in DS Management Studio

Does anyone have any suggestions on what I may have missed when I moved my databases that would cause the scheduler to still look for the old database server?  I don't want to have to do these steps every time I want to schedule a job.  Not to mention, the jobs scheduled through DS Management Console don't run anyway.  What am I missing?

I was told that support ended for this version in March 2013 and they recommended that I upgrade to the latest version of DS.  I am a BusinessObjects only customer running BOE EDGE 3.1 SP4.  I believe that I will need an additional license to run DS 4.x.  I don't plan to upgrade my BOE till 4.1 is out and stable.

I am hoping someone out there can tell me what I am missing and hoping it is a simple updated to the job server or database to point the schduler to the new SQL Server. 

I am on Data Services 12.2.2.3

SQL Server 2005

Tammy Datri

Applications Manager

Grane Healthcare

[Former Member]

Hi Tammy,

Are you using any password files for the schedules ,if yes is that updated to point new server?

Also please check in the log folder of the JobServer for any errors.

Thanks

[tammy_datri]

No, I am not using a password file.  That option is unchecked.  Where would I update that if I was using them?

I don't see any errors in the AL_RWJobLauncerLog.txt file as noted above. 

I don't see any errors in the Tracelog.txt file

The Errorlog.txt file has not been updated since 5/11/2013

Is there somewhere else I should be looking?

[Former Member]

Hi Tammy,

As you specified in post,did you resync the Jobserver to new db?(Using Server manager).

If yes,can you please verify if you are pointing to the correct job server in the schedule?

Thanks

[tammy_datri]

I'm not really sure if I hit the resync or not.  I moved these databases several months ago when our DBA was pushing to get everyone off the old SQL Server.  I know that I looked at that last week as it seemed to be something I should do but I was afraid to do it since I wasn't sure what it really did.

I realized yesterday that when I was looking at the database tables, I was looking at the central repository database.  Late yesterday, I looked at the AL_Machine_Info table in my local repository database and found the entry for the old database server.  I updated the table with the new server name and my job ran overnight.   Does the resync have updated the tables in the local repository databases?  Maybe that is a clue that I missed it and should do it now.

I also noticed that when I manually edited the.txt file in the ..\log folder, it did not include those edits in the .txt files in the ..\log\job_server_1\ that get created when you setup a schedule.  Once I updated that field in my local repository, the .txt files were correct at both levels.

All of that said, I am fairly new to DS.  I took a training bootcamp 1.5 years ago.  I wrote 2 small jobs last year that didn't need scheduled.  I just wrote a job that I need to run nightly and am about to create several new ones that will be much bigger.  I'm looking to find some best practices. 

Maybe you could give me a clue on is ... should I be pushing my jobs from my local repository to the central repository and scheduling them there?  I know we talked about check in/out in our class but have not been able to find it again to see what I should be doing to take a job to production.  It seems wrong to leave it in a local repository.  Then again, should I push to central and run on job server local repository instead?  What happens when someone leaves and you don't know the password to their local repository?

[vnovozhilov]

Hi Tammy,

Could you give more information on "I recently moved my CMC and Repository databases to a different SQL Server"? What has been done precisely?

Did you catch any information in %LINK_DIR%/log/ALRW_JobLauncher.txt log?

Thank you,

Viacheslav.

[tammy_datri]

When I installed DS originally, the databases were on SQL1 which was a SQL Server 2005 machine.  My DBA descomissioned that box and I had to move my databases to SQL2 which is a SQL Sever 2008 machine.

It has been several months since I moved the databases so I'm not sure of all the steps/places I changed things.  At the time, I tested the jobs interactively and never gave a thought to testing the scheduling.  My DBA moved them so I'm not sure what his method of moving them was (backup/restore or something else).

Here's what I see in JobLauncher.txt. 

7_22_2013 14:15:02 CRWJobLauncherApp::InitInstance called.

07_22_2013 14:15:02 Launching Job (no wait, no status).  INET ADDR <inet:BUSOBJ-SERVER:3500> GUID <d29f5b5e_18dd_4de9_b829_7a30aa9ec929>. (BODI-1250134)

07_22_2013 14:15:02 Job has started.  INET ADDR <inet:BUSOBJ-SERVER:3500>, GUID <d29f5b5e_18dd_4de9_b829_7a30aa9ec929>. (BODI-1250135)

If I got to the %LINK_DIR%/log/Job_Name.txt file, I see the old SQL1 being referenced.  If I edit the .txt file and change it to SQL2 instead, I can kick off the %LINK_DIR%/log/Job_Name.bat file manually and the job will run successfully.  If I try to schedule it in DS Management Console, it doesn't run.  It's almost as if the job server is still pointing back to the old database some how.

I'm fairly new to DS and my training was 1.5 years ago so I'm a bit weak and rusty on this stuff. 

I was wondering if I need to "Resync" the job server or something like that.  I don't see anywhere in a configuration screen that I missed changing the DB location.  It only seems to be a problem right now when I try to schedule a job.  I can run them interactively in the Designer fine.  I have created a few jobs in the past but none of them are on a schedule.  I update them when the users tell me they have made changes to the database and the job needs to run.

Any help you can give would be greatly appreciated.  I can probably schedule the .bat to run via windows scheduler but I was hoping to get the DS scheduling working properly.

Tammy

[vnovozhilov]

Please review KBA 1481432 - How to migrate a local repository to another database - Data Services / Data Integrato...

Thank you,

Viacheslav.

[tammy_datri]

This would have been very helpful back when Imoved the databases!  I don't see any reference to moving the Central Repository.  Do you have any links to something that might help me with that?

I submitted a ticket to support after the move because I was getting te error "Cannont find Profiler Repository".  These are my notes from the ticket

Talked with Tammy. We fixed the AL_MACHINE_INFO table in profiler
repository to point to the correct SQL DB ( the reserved2 filed was
pointing to old SQL server). After that ti started wotjing fine.

Sending the ticket back for closing.

The value in "Reserved2" right now is "CENTRAL REPOSITORY"

Your thoughts on changing the "CENTRAL REPOSITORY" to the actual database name for my central repository?