The Message "Unable to Create or Update Capacity Management" Is Displayed When Making an Apply Changes on PMF or IMF Just After Upgrade

Asset ID:	1-72-2222609.1
Update Date:	2018-05-01
Keywords:

Solution Type Problem Resolution Sure

Solution 2222609.1 : The Message "Unable to Create or Update Capacity Management" Is Displayed When Making an Apply Changes on PMF or IMF Just After Upgrade

Applies to:

Oracle Communications Performance Intelligence Center (PIC) Software - Version 10.2.0 and later
Information in this document applies to any platform.

Symptoms

The error message "Unable to create or update capacity management" is displayed when Apply Changes operation is done on PMF or IMF.

This does not prevent to apply the changes.

Cause

This issue was raised when "Apply Changes" was managed on IMF/PMF and the upgrade was completed on these equipment, but not on the whole system (IXP not upgraded).

When IXP and Builders are not up to date, whereas IMF and PMF are, the system tries to add elements to be managed by Capacity Management, that is not already deployed.

The log file application.log contains the following trace:

2016-12-18 03:19:19,468 - INFO - NSP-MGMT - Centralized Configuration - tekelec - BUSINESS - Activate application proadmin
2016-12-18 03:19:21,816 - INFO - NSP-MGMT - Centralized Configuration - tekelec - SYSTEM - Object query statement: SELECT OBJALIAS.SESSION_ID, d.CLASS_ID, OBJALIAS.NAME, OBJALIAS.START_DATE, OBJALIAS.END_DATE, OBJALIAS.PCFLAVOR, d.DICTIONARY_TYPE_ID, OBJALIAS.FORMAT_ID, d.PROTOCOL_ID, OBJALIAS.DICTIONARY_ID, OBJALIAS.STORAGE_ID, OBJALIAS.USER_INFORMATION, SYSTEMALIAS4.OBJECT_ID, SYSTEMALIAS4.OWNER, SYSTEMALIAS4.STATE, SYSTEMALIAS4.REPLACED_BY, SYSTEMALIAS4.CREATION_TIME, SYSTEMALIAS2.ROLE_ID, SYSTEMALIAS2.PRIVILEGE FROM CFG_XDR_SESSION OBJALIAS ,CFG_DICTIONARY d ,COR_OBJECT SYSTEMALIAS4 ,COR_OBJECT_ROLE_PRIVILEGE SYSTEMALIAS2 ,COR_USER_ROLES SYSTEMALIAS3 WHERE ( ( OBJALIAS . DICTIONARY_ID = d . DICTIONARY_ID ) ) AND ( (SYSTEMALIAS3 . USER_ID = 'tekelec') ) AND ( SYSTEMALIAS4 . OBJECT_ID = SYSTEMALIAS2 . OBJECT_ID ) AND ( SYSTEMALIAS2 . ROLE_ID = SYSTEMALIAS3 . ROLE_ID ) AND ( OBJALIAS . SESSION_ID = SYSTEMALIAS4 . OBJECT_ID ) AND ( (SYSTEMALIAS2 . PRIVILEGE LIKE '%r%') ) ORDER BY NLSSORT(OBJALIAS.NAME, 'NLS_SORT=BINARY_AI') ASC,SYSTEMALIAS4.CREATION_TIME ASC
2016-12-18 03:19:33,124 - INFO - NSP-MGMT - Centralized Configuration - tekelec - SYSTEM - Create capacity management Build DFP: B_MediationCapacityManagement
2016-12-18 03:19:33,127 - ERROR - NSP-MGMT - Centralized Configuration - tekelec - SYSTEM - Unexpected exception during capacity management mediation monitoring update - com.steleus.nsp.config.system.exception.NSPCentConfException: Enable to find xDR builder Generic FlowMonitor Stats
at com.steleus.nsp.config.system.ejb.helpers.ixp.IxpUtilities.getCapacityManagementBuildDFP(IxpUtilities.java:572)
at com.steleus.nsp.config.system.ejb.helpers.ixp.IxpUtilities.updateMediationMonitoring(IxpUtilities.java:424)
at com.steleus.nsp.config.system.ejb.helpers.ixp.IxpUtilities.updateCapacityManagementMonitoring(IxpUtilities.java:335)
at com.steleus.nsp.config.system.ejb.sync.ConfigSynchronizerBean.updateCapacityManagementConfiguration(ConfigSynchronizerBean.java:1083)
at com.steleus.nsp.config.system.ejb.sync.ConfigSynchronizer_djjcpk_EOImpl.__WL_invoke(Unknown Source)
at weblogic.ejb.container.internal.SessionRemoteMethodInvoker.invoke(SessionRemoteMethodInvoker.java:40)
at com.steleus.nsp.config.system.ejb.sync.ConfigSynchronizer_djjcpk_EOImpl.updateCapacityManagementConfiguration(Unknown Source)
at com.steleus.nsp.config.system.ejb.sync.ConfigSynchronizer_djjcpk_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:174)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:345)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
at com.steleus.nsp.config.system.ejb.sync.ConfigSynchronizer_djjcpk_EOImpl_1036_WLStub.updateCapacityManagementConfiguration(Unknown Source)
at com.tekelec.cssg.nsp.proadmin.server.model.sync.SynchronizeConfigModel.updateCapacityManagementConfiguration(SynchronizeConfigModel.java:277)
at com.tekelec.cssg.nsp.proadmin.server.servlets.ixp.SynchronizeConfigServiceImpl.updateCapacityManagementConfiguration(SynchronizeConfigServiceImpl.java:45)
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:606)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:587)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:333)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:303)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:373)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.steleus.nsp.common.gui.controller.filter.LoginFilter.doFilter(LoginFilter.java:283)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.tekelec.cssg.nsp.common.gui.controller.ContextFilter.doFilter(Unknown Source)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3730)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3696)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2273)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2179)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1490)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused by: javax.ejb.ObjectNotFoundException: Bean not found in 'findByDisplayedNameSubsystemId'.
at com.steleus.nsp.config.system.ejb.ixp.XbTypeToDisplay_sib1qe__WebLogic_CMP_RDBMS.ejbFindByDisplayedNameSubsystemId(XbTypeToDisplay_sib1qe__WebLogic_CMP_RDBMS.java:1565)
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:606)
at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.scalarFinder(RDBMSPersistenceManager.java:422)
at weblogic.ejb.container.manager.BaseEntityManager.scalarFinder(BaseEntityManager.java:2534)
at weblogic.ejb.container.manager.BaseEntityManager.localScalarFinder(BaseEntityManager.java:2479)
at weblogic.ejb.container.internal.EntityEJBLocalHome.finder(EntityEJBLocalHome.java:1114)
at com.steleus.nsp.config.system.ejb.ixp.XbTypeToDisplay_sib1qe_LocalHomeImpl.findByDisplayedNameSubsystemId(XbTypeToDisplay_sib1qe_LocalHomeImpl.java:185)
at com.steleus.nsp.config.system.ejb.helpers.ixp.IxpUtilities.getCapacityManagementBuildDFP(IxpUtilities.java:567)
... 42 more

Solution

There is nothing to do in particular.

The "error" will be fixed "automatically" after upgrade completion.

Attachments

This solution has no attachment