Search Engine: Elastic

Article ID: 132244, created on Feb 15, 2018, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 7.3


There are several possible symptoms of the issue, depending on the exact conditions.

OSS Core could fail to connect to BSS Database node with the following exception in /var/log/pa/core.log:

Caused by: org.postgresql.util.PSQLException: FATAL: password authentication failed for user "pba"
        at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(
        at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(
        at org.postgresql.core.ConnectionFactory.openConnection(
        at org.postgresql.jdbc.PgConnection.<init>(
        at org.postgresql.Driver.makeConnection(

Alternatively, CCP v2 may show errors in the screens, related to Billing functionality. GET API requests on URL end with the 500 error in browser debugger:

Sorry, but something went wrong

The error reflected in core.log:

javax.persistence.PersistenceException: org.hibernate.exception.SQLGrammarException: could not extract ResultSet
Caused by: org.postgresql.util.PSQLException: ERROR: permission denied for relation PromoTrfPeriod


For old Odin Automation installations, bm4 user could remain as the default identity to access Billing database. During the OA lifetime, the default user was changed to pba. New features imply logging in under this user.


Please use the instructions provided in KB article:

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51

Email subscription for changes to this article
Save as PDF