Post Deployment On OAG The Error: "Fatal error: Metrics storing could not be initialized. Metrics will not be stored.: com.vordel.common.VordelException: Domain ID mismatch; check your database connection" Is Reported (Doc ID 2036284.1)

Last updated on AUGUST 10, 2016

Applies to:

Oracle API Gateway - Version 11.1.2 and later
Information in this document applies to any platform.

Symptoms

The following error is observed on any deployment into a new OAG domain:

####################################################################################################
# Hostname: host-1
# Management Port: 6065
####################################################################################################

FATAL 2015/06/18 12:39:33.280 Fatal error: Metrics storing could not be initialized. Metrics will not be stored.:
com.vordel.common.VordelException: Domain ID mismatch; check your database connection
  at com.vordel.reporting.metricsmanagement.MetricsManager.configure(MetricsManager.java:162)
  at com.vordel.reporting.rtm.RealtimeMonitoring.configure(RealtimeMonitoring.java:131)
  at com.vordel.precipitate.SolutionPack.loadModules(SolutionPack.java:595)
  at com.vordel.dwe.Service.refresh(Service.java:427)
  at com.vordel.api.configuration.ConfigurationService.updateConfiguration(ConfigurationService.java:85)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
  at java.lang.reflect.Method.invoke(Method.java:601)
  at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
  at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
  at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
  at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:288)

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms