Changing SYS and SYSTEM
When SYS or SYSTEM passwords are changed it does not effect ongoing replication because the SYS and SYSTEM passwords are used only when the *-all.sh is run. Once this script is executed and the replication is up and running, SYS and SYSTEM users are not used by Dbvisit Replicate at all.
...
1. Stop MINE/APPLY/FETCHER process.
2. In Dbvisit Replicate command console, execute
| Panelnoformat | ||
|---|---|---|
| ||
ENGINE ENCRYPT newpasswd |
This will return an encrypted value of newpassword.
3. Edit the DDC files for MINE/APPLY/FETCHER and set the new password in line
| Panelnoformat | ||
|---|---|---|
| ||
memory_set DDC_PASSWORD xxxxxx |
34. Start the console without connecting to the database
| Panelnoformat | ||
|---|---|---|
| ||
start-console.sh --no-checkdb |
45. Set new encrypted password for MINE/APPLY/FETCHER process.
| Panelnoformat | ||
|---|---|---|
| ||
set MINE.MINE_PASSWORD xxxxxx set APPLY.APPLY_PASSWORD xxxxxx set MINE.DDC_PASSWORD xxxxxx set APPLY.DDC_PASSWORD xxxxxx |
If there are more processes, then do this for all processes.
| Note |
|---|
When dbvrep password is changed on source then set MINE.MINE_PASSWORD to encrypted password value or FETCHER.FETCHER_PASSWORD if FETCHER is used. If password of dbvrep user is changed on target database then set APPLY.APPLY_PASSWORD to encrypted password value. |
...