We're here to help!

Password Management

Follow

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  *-pre-all.sh and *-all.sh scripts are  run. Once these scripts is executed and the replication is up and running, SYS and SYSTEM users are not used by Dbvisit Replicate at all. 

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 the Dbvisit Replicate user created during execution of *-all.sh script. 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

This will return an encrypted value of newpassword.

 

3. Edit the DDC files for MINE/APPLY/FETCHER and set the new password in line

memory_set DDC_PASSWORD xxxxxx

 

4. Start the console without connecting to the database

start-console.sh --no-checkdb

 

5. Set new encrypted password for MINE/APPLY/FETCHER process.

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.


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.

 

 

 

Have more questions? Submit a request

Comments