Hey there,
I’ve got to move a BI environment on new hard ware. The BO products are installed and I’ve copied the DI repository DB from one Sequel server to the new one.
DI can execute all the jobs without any problems. But I don’t see any of these jobs in the Data Integrator Administrator. Thus, I can’t schedule them either.
Seems like it’s referring to another, empty repository…
Anyone got a clue on what I’ve done wrong and how I can fix it?
Thanks,
TC
TC__ (BOB member since 2006-07-17)
In WebAdmin, re-register the repository?
Werner Daehn 
(BOB member since 2004-12-17)
Done that, Werner.
I noticed that when I execute a job in DI (designer, not the web interface) I only get one choice for the job server - that’s the old one. Some value in some table has to be changed. You know which?
-or:
So I suppose I’ll have to drop the new old repository and create an new repository. But how can I import the objects from the old server?
Thanks,
TC
TC__ (BOB member since 2006-07-17)
We did a recent move of the repository db. My steps were:
On the old (existing) Web Admin, un-schedule all of the jobs. Disable any jobs exposed as web services.
Remove the old repo from web admin
Detach the repo from the job server via Server Admin
Back up the repo db and restore to the new location. Set the old database to “offline” or “detached” in the database tools so that you’re sure it’s not getting accessed any more.
Re-attach the repo in Server Admin
Add back the repo db in Web Admin. Re-enable any web services.
Re-enable the job schedules. Note you can’t do this in bulk via the checkboxes; DI doesn’t update the job parameters correctly to the new repo db, as we found out the hard way. 
Edit each job schedule by hand and re-enable it.
If you also had a job server move as part of this, you would do that server reinstallation after step 4, and do step 5 on the new job server.
dnewton 
(BOB member since 2004-01-30)
Ok, thank you.
But I just realized that I’m facing another problem:
I’m not quite sure why that BO guy (not Werner 
) I was talking about lic-files told me that my old licence file would do 
However, I installed DI w/o any job servers. I did not notice that the job server check box was deactivated while clicking through the setup routine.
I’m contacting BO at the moment… and get back with feedback
Thanks,
TC
TC__ (BOB member since 2006-07-17)
Werner Daehn 
(BOB member since 2004-12-17)
Oh, and another step if installing a new job server:
Re-apply any customizations to DSCONFIG to the new job server’s DSCONFIG. Don’t just copy/overwrite the file, you should compare the two and make adjustments.
dnewton (BOB member since 2004-01-30)
Seems to be some sort of issue to get a simple .lic file with expired maintenance…
“same old story that everybody knows…” (Garth Brooks - for those who want to join me singing)
TC__ (BOB member since 2006-07-17)
I moved BODI from aix to windows because we had some kind of odbc connection problem, and recreated the license file on the BODI site (I have no idea how that site was incorporated into the SAP site).
You need to provide the mac address of the machine you’re installing BODI on though.
mario daniels (BOB member since 2008-03-19)
Yeah, but to log in you need to buy maintenance - which I don’t wan’t.
When you open the *.lic file with an editor you’ll find your mac address (server ID) and a part that looks like hex code.
(I suppose the server ID and that code would have to be modified. But I don’t want to crack this software 
. I bought it… I just want to get it running on other hard ware. )
TC__ (BOB member since 2006-07-17)
Ok folks, I’ve got an update on how things are going:
BODI works but:
1)
when I open the DI Designer on the server itself I don’t see the monitor and the log tab in the left upper corner.
Though I get both opening die designer on my notebook.
-> Did I miss to install some component?
I still have no access to the jobs in DI-Administrator. For some reason this web interface does not know that I’m already running jobs. Thus I can’t schedule them either.
Btw I followed instructions of dnewton.
Anyone got a clue on what I might have done wrong?
TC__ (BOB member since 2006-07-17)
Sounds like it. Or a config problem. Have you tried reinstalling Designer on the server?
Sounds like something support would need to deal with. You can run and schedule jobs without the web interface, though, we do it all the time. Just need to build the AL_Engine call for the job manually and schedule it yourself in the OS scheduler.
eepjr24 (BOB member since 2005-09-16)
regarding to the second point - what you’re doing is create batch files and let the OS schedule them. That sounds fine to me. But to “export execution command” in DI-Admin I’d need to go further than the program lets me.
When I click on Batch jobs / my Repository / configuration all I get this rolldown window where I can pick one of my JOBs. But the picked JOB doesn’t show, nor do the others. It’s just the rolldown window on that screen :?
Or is there another way?
TC__ (BOB member since 2006-07-17)
Sure, there are other ways. Check threads like this one:
or search the forums on AL_Engine, you will get posts that detail the command line parameters for your OS and how to get them to work. The web admin is just putting together a batch file, no rocket science involved.
eepjr24 
(BOB member since 2005-09-16)
Ok, I’ll check that.
But my tasks on my old w2k server did not work very reliable. Schedules tasks just didn’t run once in a while. Too unsafe for critical data.
But first I’ m gonna edit all datasets referencing to the old sever (e.g. in A_SCHED_INFO).
I set up new hardware with a new name…
TC__ (BOB member since 2006-07-17)
nods. I am not fond of the OS scheduler myself. Which is why I rolled my own scheduler inside DI and use it to execute all my jobs. =)
eepjr24 (BOB member since 2005-09-16)
Ok guys,
right now I’m pretty close to a new DI install.
What other way is there to move all objects to the new environment besides a backup and restore the repo?
TC__ (BOB member since 2006-07-17)
Export the ATL and reimport it? Or is that what you meant? If you have the licensing, you can also check all the jobs into a central repository and then just get latest on the new repo once it is set up.
eepjr24 (BOB member since 2005-09-16)
Ok, I’ve cleaned the registry, reinstalled DI, imported the ATL files.
DI desinger works, job server works as well.
Web Admin is screwed up. I can attach the repo and connect successful.
But it doesn’t show the entries made in the AL_HISTORY. Nor can I configure the batch jobs.
I suppose it’s got something to do with the account the tasks run under or a registry entry.
Waiting for your input…
TC__ (BOB member since 2006-07-17)