My Oracle Support Banner

After Reconfiguring an MMX Path, a Config Reload (SIGHUP) Fails with: "ERROR: Configuration error: Plugin 'Z' detected schema inconsistency: Schema specified closure of non-extant path! PathID: 'X' (Doc ID 1275032.1)

Last updated on AUGUST 09, 2018

Applies to:

Oracle Communications Network Charging and Control - Version: 4.1.0 and later   [Release: 4.1 and later ]
Information in this document applies to any platform.

Symptoms

When changing the parameters of any Internet Protocol (IP) based path in Messaging Manager (MMX) through the screens:


The changes are able to be correctly saved, but when triggering xmsTrigger with a SIGHUP signal to reload the configuration, the following is logged in the xmsTrigger log (/IN/service_packages/XMS/tmp/xmsTrigger.log):

Dec 25 01:50:00.504897 xmsTrigger(10669) ERROR: Configuration error: Plugin 'SMPP1' detected schema inconsistency: Schema specified closure of non-extant path! PathID: '2759'

This results in the new configuration not being correctly loaded by xmsTrigger until the entire Service Logic Execution Environment (SLEE) is restarted.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
  Symptoms
  Cause
  Solution
  References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.