We have recently been asked to move from non-expiring database logon passwords to ones which expire, for security reasons.
We are looking for a way to do this most efficiently, even if it involves doing a little coding, we would consider all options.
We are running on windows, boxi r2 sp2, oracle db.
The schedule manager that comes with boe works with the following exceptions: it only searches for reports by original database name, rather than looking at custom info so all our reports which point to 1 production database are scattered under several development instance names.
The second problem is users who have created scheduled instances - we can see no way of editing these.
We have looked at a product from APOS, but it was very expensive considering we'd only use it to change passwords.
any ideas would be appreciated.
We are looking for a way to do this most efficiently, even if it involves doing a little coding, we would consider all options.
We are running on windows, boxi r2 sp2, oracle db.
The schedule manager that comes with boe works with the following exceptions: it only searches for reports by original database name, rather than looking at custom info so all our reports which point to 1 production database are scattered under several development instance names.
The second problem is users who have created scheduled instances - we can see no way of editing these.
We have looked at a product from APOS, but it was very expensive considering we'd only use it to change passwords.
any ideas would be appreciated.