Problem Summary: Steps to take when database user's password changes for source and Target location
It’s a security best practice to change user passwords regularly, limiting the time while others can login when the password got leaked and hackers were able to acquire it. Passwords are stored in the HVR catalog encrypted. When the HVR user’s password changes in a database which is a source or a target location of a replication then the same change must be applied in the HVR catalog.
Database administrator often use the policy to block users after 3 unsuccessful try with a wrong password so it’s recommended to suspend the related jobs in the HVR GUI before changing the password within the DBMS to prevent the user to be locked.
Once the jobs were suspended and password was changed in the database the next step is to change the password in the location configuration in the HVR GUI. Location configuration can be changed by double clicking on the name of the location in the GUI. After changing the password in the catalog, the related capture and integrate jobs must be reinitialized with the “Scripts and Jobs” option enabled on the advanced tab.
The refresh jobs (if there were any) have to be recreated as well with HVR Refresh.