Steps To Take When Database User Password Changes for Source and Target Location

Issue

It’s a security best practice to change user passwords regularly, limiting the time during which others can log in when a password got leaked and hackers were able to acquire it. Passwords are stored in the encrypted form in the HVR catalog. When the HVR user’s password changes in a database that is a source or a target location of a replication, then the same change must be applied in the HVR catalog.

Environment

HVR 5

Resolution

Database administrators often use the policy to block users after 3 unsuccessful tries 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 from being locked out.

Once the jobs are suspended and the password is 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.