OSM 724 COM Deployment Not Getting Reflected Into the Database
(Doc ID 2173099.1)
Last updated on APRIL 03, 2023
Applies to:
Oracle Communications Order and Service Management - Version 7.2.4 and laterInformation in this document applies to any platform.
Symptoms
Deployment of COM cartridge on the servers is failing. the cartridges are not getting reflected in the database even though the log is showing deployment as completed.
this is preventing us from Deploying COM code on the environment .
OSM Version and Patch Level
7.2.4.1.10.705
<[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <T
he model deployment for cartridge[OSM_COM_NewCo_Solution/15.3.0.0.0] with sessionId[1001] is rolling back.>
0.0.0] with sessionId[1001] is rolling back.>
<[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <D
eployment for cartridge[OSM_COM_NewCo_Solution/15.3.0.0.0] with sessionId[1001] is cancelled.>
h sessionId[1001] is cancelled.>
- OSM to rollback what imported so far hence the deployment (of the rollback) successful
<[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <S
tarting JMS Servers - Deployed cartridge>
<[ACTIVE] ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'> <D
eploy request for cartridge[OSM_COM_NewCo_Solution/15.3.0.0.0] with sessionId[1001] is complete successfully.>
with sessionId[1001] is complete successfully.>
What was discovered is that the following job ORDERMGMT.om_job_pkg.invoke_notif_engine is having too many orders to be processed hence it is creating a lot of messages inside the oms_events table.
Is there a way to get rid of these orders?
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |