Changing Data Source

[darran6]

Enterprise XI
Reports XI
JDBC connection

We have various reports scheduled in Enterprise XI. For various business reasons we are moving our analysis database to another machine with a different name.

I've tried specifying "Use customer database logon information" under Process->Database (although I wasn't sure whether to use crdb_jdbc or our JDBC driver (ca.ingres.jdbc.IngresDriver) as the custom driver.)

Reports failed with "Failed to open the connection. C:\Program Files\Business Objects\BusinessObjects Enterprise 11\Data\procSched\Tiffany.reportjobserver\~tmpb803e17a855d15e.rpt"
whether they were pre-scheduled or newly scheduled.

I've also tried opening the report in Crystal, creating the new connection, setting the datasource location and re-saving to Enterprise. In this case pre-scheduled reports fail with "Error in File C:\Program Files\Business Objects\BusinessObjects Enterprise 11\Data\procSched\Tiffany.reportjobserver\~tmpb803e17a95e6660.rpt: Unable to connect: incorrect log on parameters. Details: [Database Vendor Code: 15532300 ]". If I re-schedule the report then it works fine.

Obviously I don't want to have to go through and re-schedule all of our reports! Does anyone have any thoughts/ideas?

Many thanks,
Darran

 

[darran6]

Can anyone help on this one?

 

[TIBRon]

I have a similar issue. We must change our database password regularly. When we do, I use the Business Objects "Schedule Manager" administration tool from the Launchpad.

This utility allows you to change the datasource and/or logon information for multiple reports simultaneously. The problem is that the changes only affect newly-scheduled instances. All of my previously-scheduled instances will fail with the "incorrect log on parameters" error message.

Unfortunately, this most likely means that Enterprise stores the database and logon information with each scheduled instance. I end up having to reschedule all my reports to get everything working again.

I am experimenting with Object Packages as a workaround. You can have multiple reports in an Object Package and schedule them all at once. This would save time, however you cannot schedule an individual report within the package separately from the rest.

I know there are third-party utilities to make mass changes to reports and Enterprise instances, but they are very expensive (for us, anyway).

 

[janchan]

I am facing the same problem. we have different tetsing environments and i used the schedule manager to change the database options. all our 300 reports use schedule events. so even if i change the database logon, the report fails. i have to reschedule them one by one again. the same is the case when i do some code changes to the reports. i have to reschedule them all over again.

 

[ckiklas]

There is a tool from Apos (Object Manager) that will allow you to change the login information for multiple reports all at once.

http://www.apons.on.ca

 

[janchan]

Thanks ckiklas. I am able to change the logon info from schedule manager. the problem is with the events themselves. every time we refresh a report, the schedule has to be changed manually for each report. is there a solution for this?