"No row with the given identifier exists" error in ITPAM c20.logs. Processes no longer run.
search cancel

"No row with the given identifier exists" error in ITPAM c20.logs. Processes no longer run.

book

Article ID: 21773

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Process Automation Base

Issue/Introduction

C2O.log shows:

org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.optinuity.c2o.bean.C2ORunTimeInstance#65034];

This starts to happen after the ITPAM database was moved, either to a new partition (example, from C:\ to D:\) or a new server. If the database tables and keys were not moved with the database the error displays. When this occurs CA recommends that the ITPAM repository database be rebuilt through the ITPAM installer and the processes imported back in.

 

Environment

Release: ITPAM 3.1 and Higher

Resolution

Here is the outline of the process to export existing ITPAM data, create a new ITPAM database, import the data back into ITPAM.

  1. Export your data from ITPAM. This is done by going into the ITPAM client, selecting the folder(s) that contain your data. Right click on the folder and select export. This will create XML files with each export. If you export a parent folder, all sub-folders and files will be exported into the created XML file. Please confirm the XML files are created with each export.
     
  2. You can either reinstall ITPAM and have the install create a new ITPAM database or you can run a repair with the existing database. The repair will allow you to change all your configuration values but this does not rebuild the database tables unless you choose to create a new ITPAM database. CA recommends the creation of a new ITPAM database. This will ensure all the ITPAM tables are created successfully.
     
  3. Once the ITPAM install is complete log back into the ITPAM client UI and import the XML files from step 1.

Additional Information

NOTE:  In-flight instances will need to be reran after following the steps above.