ORA-01017: invalid username/password; logon denied in oracle 12c Dataguard DG broker Suddenly

 It's been long time everything was working fine with oracle DG broker (dgmgrl> ).  Suddenly we faced this error in DG broker while trying to valid network configuration before a SWITCHOVER operation, even though no one change any credentials. 

After sometime, we realized that we were connected to DG broker as SYSDG user (normally connect with SYS). and then found that, the SYSDG user's credential are not same in both PRIMARY and STANDBY password file. that's why it is not able to connect. Here is the query to check this in both environments -   

SQL> select * from v$pwfile_users;

Then logout and connect back with SYS user, everything worked perfectly.

 dgmgrl> connect sys 

So solution is- 1) Either you need to change SYSDG user's credentials in both database same (since remote_login_passwordfile is set to EXCLUSIVE) . so it will saved and match in Password file.

2) OR login with a different super user (like SYS) who's credentials are same for both databases. 

For details you may read- ora-01017

 

 

Test Endpoint failed: Application-Status: 1020912, Application-Message: Network error has occurred” - Amazon Redshift as the target endpoint for AWS DMS

Of course this is a network issue but couldn’t figurable easily. I had to spent quite a good amount of time to find the issue while setting up the Redshift as a Target endpoint in AWS DMS.  

As per below docs, in #6 they mentioned- “6. Enter your Amazon Redshift endpoint for the Server name”  - https://aws.amazon.com/premiumsupport/knowledge-center/dms-redshift-target-endpoint/

Actually it won’t work (and you will get above error message) if you just copy and paste the whole Redshift cluster endpoint from Redshift Cluster general information page.  Normally Redshift cluster endpoint consist of cluster identifier + Region Identifier for cluster + database name + port.

So, the solution is for this error, you need to remove the database name and port number from the actual Redshift cluster endpoint and use this(rest of parts) in the “Server name:” field on AWS DMS endpoint creation page.

 

Hope this will save your valuable time and efforts!