5.2.23.8 pn32fIncorrectDbConf

Table 5-114 pn32fIncorrectDbConf

Field Details
Trigger Condition This alert will be raised when incorrect database configuration provided for pn32f service and resulting in connection failure with database.
Severity Major
Alert Details Provided

Summary:

Due to incorrect database configuration, connection failed with database.

Expression:

(up{app="pn32f-svc",namespace="sepp-namespace"} unless on (namespace) absent(hikaricp_connections{app="pn32f-svc",namespace="sepp-namespace"})) == 0
OID 1.3.6.1.4.1.323.5.3.46.1.2.4064
Metric Name NA
Resolution Possible resolutions:
  1. Verify the ocsepp_custom_values_<version>.yaml file to ensure that the correct namespace where cnDBTier is installed is specified, and the database names are also correct.

    Example: 
    
seppDbName: &dbNameRef "seppdb_user1_sepp"
seppBackupDbName: &backupDbNameRef "seppbackupdb_user1_sepp"
mysql:
  primary:
    host: &mySqlHostRef "mysql-connectivity-service.cndb-sepp"  # Ensure the namespace is correct in which cndb should get installed.
  2. For more details, refer 'Multiple SEPP instances on Shared cnDBTier Cluster' section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.