How to minimize down time when change passwords on replication databases?
We have databases on different time zones throughout the country. We have to implement all user passwords change every 60 days. Our databases are multi master replication databases, they are managed by different dba teams with different peak times, down times, and maintenance windows. We want to make sure these password changes are smooth, with minimum to 0 down time, no broken jobs and replications. We are trying to defer job push, change passwords, recreate all db links, schedule job push at the same time throughout our databases.
Can you advice options of ways we can implement these changes, or if there are tools that will help us to enforce the passwords changes every 60 days without breaking our replication or causing any down time?
Replication account passwords are not your "regular" users.
DO NOT change passwords every 60 days, set special profiles for these accounts.
"The person who says it cannot be done should not interrupt the person doing it." --Chinese Proverb
Thanks for your reply. That what we had been doing in the past years, but recently we are required to change passwords for all users in all our databases every 60 days. We have to implement and enforce this rule!
Click Here to Expand Forum to Full Width