Service Alert Log with Failed Messages During Startup

(Doc ID 2409658.1)

Last updated on JUNE 14, 2018

Applies to:

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

Symptoms

In the service alert log, you see the following "failed" messages (5 in the log below). Are they critical or ignorable? If critical, how could we get rid of those failed messages?

ERROR

pid = 15860006
05/22/18 19:11:24: Service::processArg, using [sa] DBService
05/22/18 19:11:24: 0x1,ctp=110074f28,"<MAIN-TASK>" Redirecting cores files to /nms/nmsadmin_tst/logs/run.service_alert
05/22/18 19:11:24: 0x607,ctp=1101a0d78,"MyCentricity::mainTask" Service::initState for (gaddr=1/102.54[0])
05/22/18 19:11:24: 0x809,ctp=110075b58,"unknown" MyCentricity::cmmsGroupChange: MyCentricity Service process group membership changed
05/22/18 19:11:24: 0x607,ctp=1101a0d78,"MyCentricity::mainTask" **INFO*** ready
05/22/18 19:11:24: 0x607,ctp=1101a0d78,"MyCentricity::mainTask" PG::lookup - failed - (0/0:0.0) mycentricity.C(692) [corbagateway/publisher] scope=2 mode=3: << no error >>
05/22/18 19:11:24: 0x607,ctp=1101a0d78,"MyCentricity::mainTask" PG::lookup - failed - (0/0:0.0) NA(0) [corbagateway/publisher] scope=2 mode=3: << no error >>
05/22/18 19:11:24: 0x607,ctp=1101a0d78,"MyCentricity::mainTask" PG::lookup - failed - (0/0:0.0) NA(0) [corbagateway/publisher] scope=2 mode=3: << no error >>
05/22/18 19:11:24: service_alert 0x607,ctp=1101a0d78,"MyCentricity::mainTask" PG::wait [corbagateway/publisher] not available
05/22/18 19:11:24: service_alert 0x90a,ctp=110075b58,"ProcessGroup::wait_for" PG::lookup - failed - (0/0:0.0) NA(0) [corbagateway/publisher] scope=2 mode=3: << no error >>
05/22/18 19:11:24: service_alert 0x90a,ctp=110075b58,"ProcessGroup::wait_for" PG::lookup - failed - (0/0:0.0) NA(0) [corbagateway/publisher] scope=2 mode=3: << no error >>
05/22/18 19:11:27: service_alert 0x809,ctp=110327d68,"MyCentricity::rankChanged" MyCentricity::rankChanged: changing rank from -1 to 0
05/22/18 19:11:28: service_alert 0x607,ctp=1101a0d78,"MyCentricity::mainTask" PG::wait [corbagateway/publisher] now available


STEPS
The issue can be reproduced at will with the following steps:
1. Start services: sms_start.ces

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