PH00950: OBJECTALREADYEXISTSEXCEPTION IN LOGS AFTER UPGRADING TO RAM 7.5.2.3+

Rational Asset Manager 7.5.4.5
Rational Asset Manager 7.5.4.6
Rational Asset Manager 7.5.4.7

APAR status

• Closed as program error.

Error description

• You may observe the following error/stack trace in the RAM logs
  after upgrading from RAM version <= 7.5.2.2 to RAM 7.5.2.3 or
  greater:
  
  [06/12/18 05:43:31 PDT] CRRAM0002W 78876336 WARN ws
  com.ibm.ram.repository.web.ws.quartz.CacheManagerJob - Quartz
  failed to schedule problemNotification:
  org.quartz.ObjectAlreadyExistsException: Unable to store Job
  with name: 'Problem Notification Job' and group: 'DEFAULT',
  because one already exists with this identification.
  org.quartz.ObjectAlreadyExistsException: Unable to store Job
  with name: 'Problem Notification Job' and group: 'DEFAULT',
  because one already exists with this identification.
  at org.quartz.simpl.RAMJobStore.storeJob(RAMJobStore.java:220)
  at
  org.quartz.simpl.RAMJobStore.storeJobAndTrigger(RAMJobStore.java
  :193)
  at
  org.quartz.core.QuartzScheduler.scheduleJob(QuartzScheduler.java
  :613)
  at
  org.quartz.impl.StdScheduler.scheduleJob(StdScheduler.java:238)
  at
  com.ibm.ram.repository.web.ws.quartz.CacheManagerJob.handleProbl
  emNotification(CacheManagerJob.java:110)
  at
  com.ibm.ram.repository.web.ws.quartz.CacheManagerJob.executeJob(
  CacheManagerJob.java:58)
  at
  com.ibm.ram.repository.web.ws.quartz.jobs.AbstractRAMJob.execute
  (AbstractRAMJob.java:90)
  at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
  at
  com.ibm.ram.repository.web.ws.was.quartz.RAMThreadPool$RAMWork.r
  un(RAMThreadPool.java:166)
  at
  com.ibm.ws.asynchbeans.J2EEContext$RunProxy.run(J2EEContext.java
  :271)
  at
  java.security.AccessController.doPrivileged(AccessController.jav
  a:594)
  at com.ibm.ws.asynchbeans.J2EEContext.run(J2EEContext.java:797)
  at
  com.ibm.ws.asynchbeans.WorkWithExecutionContextImpl.go(WorkWithE
  xecutionContextImpl.java:222)
  at
  com.ibm.ws.asynchbeans.ABWorkItemImpl.run(ABWorkItemImpl.java:20
  6)
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1892)
  
  Cause:
  Upon upgrading to RAM 7.5.2.3, an issue could occur where stale
  data exists in the database related to the CQ notifications job;
  if this data is not deleted during upgrade and a new entry is
  created for the notification job in RAM, you may observe the
  "ObjectAlreadyExistsException" repeatedly thrown to the logs.
  

Local fix

• The issue can be temporarily resolved by deleting the stale data
  from the appropriate database schema table; to do this, execute
  the following SQL statement against the RAM database - NOTE: it
  is important to take a backup of the RAM database prior to
  executing any DML/DDL against it:
  
  DELETE FROM RAMSCHEMA.JOB_QUEUE WHERE JQ_CATEGORY =
  'com.ibm.ram.CQNotifier';
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users who is using CQ Notification task                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * OBJECTALREADYEXISTSEXCEPTION IN LOGS for CQ Notification     *
  * Job.                                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• logs are filling with OBJECTALREADYEXISTSEXCEPTION while
  scheduling CQ notification for  'com.ibm.ram.CQNotifier' job
  category.
  This wont impact any of the functionality. We suppressed the log
  level.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RATL ASSET MGR

• Fixed component ID

  5724R4200

Applicable component levels

• R754 PSY

     UP