Troubleshooting Errors and Warnings in the ITSM Installer Log

Problem

When you upgrade BMC Remedy ITSM on the Primary Server from version 8.1.02 to 9.1.04, the following warning is displayed in the installation logs.

WARNING,com.bmc.install.product.rik.statement.
 RIKLoadApplicationStatement,
  LOG EVENT {Description=[Execution of statement 
 delegate returned a warning
  return code 1025],Detail=[RIK load application 
 command file C:\Program Files
 \BMC Software\BMCRemedyITSMSuite\Workflow\post_install
 \upgrade_from_9.1.01_to_9.1.02\
 systems\fnd\workflow\en\adf_fnd.xml returnCode= 1025]}

Solution

If the Filter Max Limit value for the MSM migration task is greater than the value in Server Information, reset the Maximum Stack of Filter value to the maximum.

To calculate the Maximum Stack of Filter value

1. Log in the BMC Remedy Developer Studio.

2. Run FND_CORRECT_PEOPLE_PERMISSION_ASSGINEEGRP

To find the Filter Max Limit

1. Identify number of records in the ‘CTM:People Permission Groups’ by using the following SQL query.
   select COUNT(*) from CTM_People_Permission_Groups WHERE Assignee_Groups = ';'+Last_Modified_By+';'
2. Multiply the count returned in the above step by 7 to get the Filter Max Limit for the MSM migration task.

Problem

When you upgrade BMC Remedy ITSM from earlier versions  to 9.1.04, the upgrade completes with the following errors in BMCRemedyKnowledgeManagement_error.log.

ERROR RIKMain  - Data import for /opt/bmc/BMCRemedyITSMSuite
 /Workflow/post_install/
 9.1.04_fresh_install/systems
 /rkm/workflow/en/rkm_MSM_MigrationTasks_cfg.arx 
 is returned with code 1025

Error importing record 3: ERROR (298): 
 Too many filters processed during this 
 operation; max total is 500000

Solution

If the Filter Max Limit value for the MSM migration task is greater than the value in Server Information, reset the Maximum Stack of Filter value to the maximum, else no action is required.

The rkm_MSM_MigrationTasks_cfg.arx file has 3 entries with below tags. Calculate the Filter Max Limit for each of those using the steps below.

Update_KAM_WIPArticles   

To find the Filter Max limit

1. Identify the number of records in ‘RKM:KnowledgeArticleManager’ using the following SQL query.
   select COUNT(*) from RKM_KnowledgeArticleManager where (ArticleStatusEnglish = 'Work In Progress') AND(StatusStringForSearch = 'Not Searchable')
2. Multiply the count returned in the above step by 10 to get the Filter Max Limit for the MSM migration task.

DW_RKM_RAS_7604_UPGRADE

To find the Filter Max limit

1. Identify the number of records in ‘RKM:Associations’ by using the following SQL query.
   select COUNT(*) from RKM_Associations where (KAMDocID IS NOT NULL) AND(KAMInstanceId IS NULL)
2. Multiply the count returned in the above step by 7 to get the Filter Max Limit for the MSM migration task.

DW_RKM_VG_7604_UPGRADE

To find the Filter Max limit

1. Identify the number of records in ‘RKM:KnowledgeArticleManager’ using the following SQL query.
   select COUNT(*) from "RKM_KnowledgeArticleManager" where ("Visibility_Assignee_Groups" IS NULL) AND (("VGs" IS NULL) OR ("VGs" LIKE 'NONE'));
2. Calculate first part of the Filter Max Limit as A = Count of records returned above multiplied by 10.
3. Find the exact view name of RKM:VisibilityGroupAndCompany_Article by using the following SQL query
   select viewName from arschema where name = 'RKM:VisibilityGroupAndCompany_Article';
4. Assuming view name returned by the database is RKM_VisibilityGroupAndComp2811, use the following nested query to find relevant common records from RKM:KnowledgeArticleManager  and RKM:VisibilityGroupAndCompany_Article.
   select COUNT(*) from "RKM_VisibilityGroupAndComp2811" where "KAMInstanceID" in (select "InstanceId" from "RKM_KnowledgeArticleManager" where ("Visibility_Assignee_Groups" IS NULL) AND (("VGs" IS NULL) OR ("VGs" LIKE 'NONE')))
5. Calculate the second part of Filter Max Limit as B = Count of records returned above multiplied by 4.
6. Calculate the Filter Max Limit for the MSM migration as C = A+B.