High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

sys password change in data guard broker environment

Team, As per best practices in "Data Guard Physical Standby Changing the SYS password when a broker configuration exists(1199943.1)", we should be disabling the redo transport before sys password should be changed and password file should be copied from primary to standby.

I wanted to understand why we need to disable the redo transport services. As per my tests, I can see that shipping continues even the sys password got changed on primary. This is for obvious reason as existing sys connection to standby remains valid. We require new password file only when standby goes down and so redo transport services require to have fresh sys connections to standby.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center