MBService Cores When Applying Specific Maps

(Doc ID 2312764.1)

Last updated on OCTOBER 16, 2017

Applies to:

Oracle Utilities Network Management System - Version to [Release 2.3]
Oracle Network Management for Utilities - DMS - Version to [Release 2.3]
Information in this document applies to any platform.


On : version, NMS Infrastructure

When attempting to rebuild a model, MBService would core on several maps during the apply phase of the build.

The MBService stack trace looked like this:

#0 0x00007f1523e83f96 in __strcpy_ssse3 () from /usr/lib64/libc.so.6
#1 0x00007f15267283e0 in MBEntitySet::apply(Database*) ()
from /scratch/users/toh3/nms/product/
#2 0x00007f15266f5946 in PartitionEdits::apply(int, Database*) ()
from /scratch/users/toh3/nms/product/
#3 0x00007f152675a9ff in Patch::apply(Database*) ()
from /scratch/users/toh3/nms/product/
#4 0x0000000000477a4b in MBFuncCalls::apply(Database*) ()
#5 0x0000000000452d34 in MBService::submit(int, int, oms::basic_string<char, std::char_traits, std::allocator > const&, oms::basic_string<char, std::char_traits, std::allocator > const&, oms::basic_string<char, std

This could not be reproduced on an OPAL model.


 The customer model was being migrated from to


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