DG Standby database "Failed to connect" after SYS password change
edited Aug 5, 2022 4:19PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 8 commentsAnswered ✓
Hi and thanks in advance,
We changed the SYS password a week ago on the primary database in a Data Guard configuration managed in EM 13c. We were not aware of the implications to the standby database, but actually everything continued to run fine until now. Both primary and standby are 19c (19.14.0.0.0)
Yesterday we realized that we need to get the SYS passwords in sync, so we copied the password file from the primary to the standby. The Preferred Credentials were updated and continue to test OK against both primary and standby. Yet EM 13c shows Target Status down for the standby instance and there is an Incident with "Invalid username/password"
0