Fails to run after database reboot

Last Updated : Mar 20, 2019 |

Avaya Co-Browsing Snap-in is in failed state after Oracle database reboot

Service install status in Avaya Breeze®
Avaya Co-Browsing snap-in is in “failed to run” state after Oracle database reboot.
Log file message text
ORA-01017: invalid username/password; logon denied
Log file
CoBrowse.log

Problem description

Avaya Co-Browsing Snap-in changes over to failed to run state if you reboot the Oracle database.

Solution

Procedure

  1. Unlock the Oracle user using oracle client or any other utility. For example, ALTER USER username ACCOUNT UNLOCK;
  2. In System Manager, retype the Oracle password under the Home  > Elements > Avaya Breeze® > Configuration > JDBC Sources.
  3. Click Commit.
  4. Reboot the Avaya Breeze® platform server instances via System Manager.