After Upgrade OSM 7.2.4.2.11 to 7.2.4.3.2 in Logs Error: ORA-01502: index 'ORDERMGMT.XPKOM_JMS_EVENT' or partition of such index is in unusable state

(Doc ID 2415074.1)

Last updated on JUNE 28, 2018

Applies to:

Oracle Communications Order and Service Management - Version 7.2.4 and later
Information in this document applies to any platform.

Symptoms

After an upgrade from OSM 7.2.4.2.11 to OSM 7.2.4.3.2 the following error appeared in the managed server log.

####<Jun 13, 2018 11:07:48 AM CEST> <Error> <oms> <pool-3-thread-1> <oms-internal> <BEA1-0008DA84D15C9F993853> <0b76b153c3ee4009:-321f2f2d:163f81adbd8:-7ffd-00000000000003a4> <1528880868742> <BEA-000000> <eventengine.EventDispatcherEJB: ORA-01502: index 'ORDERMGMT.XPKOM_JMS_EVENT' or partition of such index is in unusable state
Nested Exception: ORA-01502: index 'ORDERMGMT.XPKOM_JMS_EVENT' or partition of such index is in unusable state

com.mslv.oms.dataaccesslayer.ProxyException: ORA-01502: index 'ORDERMGMT.XPKOM_JMS_EVENT' or partition of such index is in unusable state
Nested Exception: ORA-01502: index 'ORDERMGMT.XPKOM_JMS_EVENT' or partition of such index is in unusable state
Nested Exception: java.sql.SQLException: ORA-01502: index 'ORDERMGMT1.XPKOM_JMS_EVENT' or partition of such index is in unusable state



Changes

 

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