Changing SYS and SYSTEM
When SYS or SYSTEM passwords are changed it does not effect ongoing replicaiton because the 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.
Note |
---|
Neither of MINE, APPLY nor FETCHER stores SYS and SYSTEM passwords therefore nothing has to be done when their passwords are changed. |
Changing Dbvisit Replicate schema password
Dbvisit Replicate communicates with the source and target database through "dbvrep" the Dbvisit Replicate user created during execution of *-all.sh script. This defualt name can be changed during the setup wizard. Execute following steps after changing dbvrep password. By default this is "dbvrep".
To change the password for the Dbvisit Replicate schema:
1. Stop MINE/APPLY/FETCHER process.
2. In Dbvisit Replicate command console, execute 'ENGINE ENCRYPT newpasswd' command. It
No Format | ||
---|---|---|
| ||
ENGINE ENCRYPT newpasswd |
This will return an encrypted value of newpassword.
3. Set this value for DDC_PASSWORD parameter in Edit the DDC files for MINE/APPLY/FETCHER ddc file. 3. Execute 'and set the new password in line
No Format | ||
---|---|---|
| ||
memory_set DDC_PASSWORD xxxxxx |
4. Start the console without connecting to the database
No Format | ||
---|---|---|
| ||
start-console.sh --no-checkdb |
...
45. Set new encrypted password for MINE/APPLY/FETCHER process.
No Format | ||
---|---|---|
| ||
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. |
...