BUG 20686726
When using the Oracle Fail Safe manager to add an Oracle database to a cluster group, if the "Use operating system authentication" button is checked on the Authentication page and the Next button is clicked, Fail Safe Manager would fail and display the following stack trace:
exception message: Value does not fall within the expected range at Oracle.FailSafe.ResourceDatabase.set_UserName(String value) at Oracle.FailSafe.Manager.Wizards.DatabaseAuthenticationPageView.Validate() at Oracle.FailSafe.Manager.Wizards.WizardDialog.nextButton_Click(Object sender, RoutedEventArgs e)
Oracle Fail Safe release 4.1.1 introduced an assertion in the client API in which all database usernames must be non-empty. The Oracle Fail Safe Manager would attempt to clear the database username when operating system authentication was chosen and that would cause an exception to be raised.
This problem has been corrected. Blank usernames are accepted again. In addition, Oracle Fail Safe Manager no longer attempts to clear the username when setting the operating system authentication.
There are a few different ways to avoid this problem:
Add the Oracle Fail Safe server username to the ORA_DBA group thus enabling operating system authentication for all databases accessed by the server. In this case the Authentication page is skipped
Use password authentication. This implies that the OS Authentication button is not checked
Use the Add-OracleClusterResource PowerShell cmdlet to add the database to the group