Existing Escalation Actions doesn't work after SOI upgrade from 3.3 to 4.2

Document ID : KB000071341
Last Modified Date : 19/02/2018
Show Technical Document Details
Issue:
Existing Escalation actions are not working after SOI up-gradation from 3.3 CU2 to 4.2. SOI is working fine with newly created escalation actions but problem is with existing Escalation Actions and it may throw an exception as below...
               Ticket Action - java.lang.NullPointerException
Environment:
SOI 4.2
Windows
Cause:
The cause of this problem is that those existing escalation actions did not have the correct value for the "PropertySetID" in the "ActionPropertySets" table in SAMStore DB. The value should have been 1 but it contains 0 instead
Resolution:
1) Run SQL Query "select * from ActionPropertySets" table and check "PropertySetID" value. The value should have "1", if this has "0" value then run below steps to fix this problem.

2) Stop "CA SAM Application Server" service on SOI Manager

3) Run below SQL Update query

    update ActionPropertySets
           set PropertySetID = replace (PropertySetID, '0', '1')
           where PropertySetID = 0

SQL Update Query

4) Start "CA SAM Application Server" service