Issues In Production After 7.0.1 To 7.0.3 Upgrade
(Doc ID 1506496.1)
Last updated on FEBRUARY 08, 2018
Applies to:Oracle Communications Order and Service Management - Version 7.0.3 and later
Information in this document applies to any platform.
We upgraded our production environment today from version 7.0.1 to 7.0.3 and after the upgrade we are facing some serious issue in Production.
As updated yesterday, we tried to reproduce the issue in one of our Pre-prod environments and we were able to reproduce it.
Following are the steps that we took :
1. Submit a normal order to the existing cartridge which was IN PROGRESS status in OSM as it was future dated.
2. Submit an amendment order of the order which was submitted earlier.
After doing these 2 steps we made following observations :
1. It was found that there was a specific query running in the database which was taking too much time.This was the same query which we saw in Production yesterday after 7.0.3 upgrade on receiving amendment orders.
SELECT COMPENSATED_HIST_ID FROM ( SELECT HCP.HIST_SEQ_ID COMPENSATED_HIST_ID FROM OM_HIST$COMPENSATION_PLAN HCP, OM_HIST$ORDER_HEADER OH WHERE
HCP.ORDER_TARGET_SEQ_ID= :B1 AND HCP.COMPENSATION_HIST_SEQ_ID=OH.HIST_SEQ_ID START WITH HCP.COMPENSATION_HIST_SEQ_ID = :B2 AND HCP.ORDER_TARGET_SEQ_ID=
:B1 CONNECT BY PRIOR HCP.HIST_SEQ_ID = HCP.COMPENSATION_HIST_SEQ_ID ORDER BY HCP.HIST_SEQ_ID ASC ) WHERE ROWNUM = 1
2. At the same time the OSM domain logs were continuously giving the error "Cache eviction will be retried periodically until successful".
####<Nov 7, 2012 3:32:53 PM CET> <Warning> <oms> <tsrvuosmapp14> <osm> <Timer-3> <oms-internal> <> <> <1352298773421> <BEA-000000>
<impl.OrchestrationCascadingLRUPolicy: Postponed eviction of order /1137944 from order cache as this order is currently in use within an active
transaction. Cache eviction will be retried periodically until successful.>
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!