It may happen that a configuration file (ex: ConfigValues_OMS.xml) gets deleted inadvertently from the configuration directory of a given microservice (ex: $OM_HOME/roles/omsServer/standalone/config). Hence, the microservice fails to start.
Issue/Introduction
This KB explains how to recover from the database a FOM/OMLR configuration file of microservice.
Environment
ALL
Resolution
Please follow the steps below to solve the issue: 1/ Set configurator.db.enabled=true in configDBrepo.properties of the microservice. 2/ Delete "revision.properties" file from "config" directory of the microservice (ex: $OM_HOME/roles/omsServer/standalone/config). 3/ Start the microservice. Like this, all configuration files will be downloaded again from the database, hence the missing file will be recovered.