The PAM processes triggered from SDM are not running after moving the PAM database and reconfigure to point to the new database server
search cancel

The PAM processes triggered from SDM are not running after moving the PAM database and reconfigure to point to the new database server

book

Article ID: 266324

calendar_today

Updated On:

Products

CA Process Automation Base CA Service Management - Service Desk Manager CA Service Desk Manager CA Service Desk Manager

Issue/Introduction

After moving the PAM database and re-configure to point to the new database server, the processes triggered from SDM are not running.


PAM UI shows the following error: An error has occurred on the server. Check the server log for details.

c2o.log shows the following:

ERROR [com.optinuity.c2o.persistence.RuntimeDBHibernateSessionHandler] [eportingManager] Failed to create Hibernate session
org.hibernate.InvalidMappingException: Could not parse mapping document from resource C2OTelemetryCustomerDetails.hbm.xml
    at org.hibernate.cfg.Configuration.addResource(Configuration.java:569)
    at com.optinuity.c2o.persistence.RuntimeDBHibernateSessionHandler.<init>(RuntimeDBHibernateSessionHandler.java:162)
    at com.optinuity.c2o.persistence.RuntimeDBHibernateSessionHandler.getInstance(RuntimeDBHibernateSessionHandler.java:221)
    at com.optinuity.c2o.reporting.ReportingManager.processQueryStoreData(ReportingManager.java:1245)
    at com.optinuity.c2o.reporting.ReportingManager.startReporterProcess(ReportingManager.java:1012)
    at com.optinuity.c2o.reporting.ReportingManager.access$500(ReportingManager.java:91)
    at com.optinuity.c2o.reporting.ReportingManager$2.run(ReportingManager.java:307)
Caused by: org.hibernate.PropertyNotFoundException: field [segmentIdentified] not found on com.optinuity.c2o.bean.telemetry.C2OTelemetryCustomerDetails
    at org.hibernate.property.DirectPropertyAccessor.getField(DirectPropertyAccessor.java:112)
    at org.hibernate.property.DirectPropertyAccessor.getField(DirectPropertyAccessor.java:104)
    at org.hibernate.property.DirectPropertyAccessor.getGetter(DirectPropertyAccessor.java:127)
    at org.hibernate.util.ReflectHelper.getter(ReflectHelper.java:83)
    at org.hibernate.util.ReflectHelper.reflectedPropertyClass(ReflectHelper.java:71)
    at org.hibernate.mapping.SimpleValue.setTypeUsingReflection(SimpleValue.java:276)
    at org.hibernate.cfg.HbmBinder.createProperty(HbmBinder.java:2164)
    at org.hibernate.cfg.HbmBinder.createClassProperties(HbmBinder.java:2141)
    at org.hibernate.cfg.HbmBinder.createClassProperties(HbmBinder.java:2031)
    at org.hibernate.cfg.HbmBinder.bindRootPersistentClassCommonValues(HbmBinder.java:359)
    at org.hibernate.cfg.HbmBinder.bindRootClass(HbmBinder.java:273)
    at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:144)
    at org.hibernate.cfg.Configuration.add(Configuration.java:669)
    at org.hibernate.cfg.Configuration.addInputStream(Configuration.java:504)
    at org.hibernate.cfg.Configuration.addResource(Configuration.java:566)
    ... 6 more

 

Environment

Release: PAM 4.3.05 CP04

Cause

The re-configure updated the environment to a previous version, not the current that is 4.3 SP5 CP04

Resolution

Re-install CP04 (which is the original version before reconfiguring using 4.3 SP5 files) after reconfiguring. See the steps and considerations to install CP04 here.