In the earlier Oracle Fail Safe releases, if the Oracle Fail Safe server used operating system authentication when accessing a database, password files were not created when a database was added to a cluster group. If the operating system authentication was enabled, Oracle Fail Safe Manager could not change the password for the database SYS user account.
In this release, when a database is added to a cluster group, Oracle Fail Safe Manager accepts the password for the SYS user account even when operating system authentication is selected as the authentication method for the Oracle Fail Safe server to use when accessing the database. A password file is created on each node according to the password you provide. Oracle Fail Safe Manager allows the password for the database SYS user account to change.