Changing an Oracle Password in an scheduled report 1

[MAPotter]

I saw a post regarding changing an Oracle password globaly for a report(s) in InfoView. I can see (and have tested) where this would work at the object level, but am I correct in that this will not work for a scheduled report as the username and password information is hard-coded in the scheduled report? Does anyone know of a way to do this? We are using Oracle 10g on a Unix box, BOE is on Windows.

 

[Turkbear]

Hi,
As far as I can remember, you would need to schedule a new instance with the new user/password information and delete the old one.





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[hilfy]

There might be a way to write code to do this using the SDK. Also, I think the APOS Instance Manager tool will allow you do do this, but you would have to purchase it. Without either of those, however, you do have to actually schedule a new instance. Since this is just a password change, you can reschedule the current instance using the new password. Note: If you ever physically change the report template, you have to schedule from scratch to get the new version to run.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[cehowski]

Since this is just a password change, you can reschedule the current instance using the new password. "

Does the above quote suggest that I can change only the password, for a "Recurring" (daily) report, and not have to change the Format, Destination, Parameters, etc? We are still using bo10 ePortfolio, and it doesn't seem possible - but I am just a user.

If not possible for a user, can an Administrator of the Server do it? Ultimately, the settings for the Schedule are in a file or db on the Server, so you would think it could be done globally.

Thanks for any input.

John

 

[hilfy]

I'm not sure if this feature is available in 10 - it's available in the various flavors of XI.

The issue is that the recurring schedules do not look at the report template when scheduling the next instance, instead they use the template the report was scheduled with for the recurring schedule. So, recurring schedules do not "see" any changes to the report template and have to be rescheduled in order to implement the changes.

-Dell

A computer only does what you actually told it to do - not what you thought you told it to do.

 

[MAPotter]

I contacted APOS regarding their Object Manager tool. It looks like the ticket. It will change the passwords on reports and recurring schedules en masse.

Thank you so much for this tip. (Now, hopefully our CIO will purchase it!)

If using BO 10, you may want to call APOS to see if they have a version for BO 10. It would be worth it.