Question 2 Replies 13 Views × Close popover Hareesh Paruchuri (Hareesh_Incessant) Incessant Technologies Technical Lead Incessant Technologies US View Profile Send Message Hareesh_Incessant Member since 2013 4 posts Incessant Technologies Posted: March 22, 2018 Last activity: April 6, 2018 Posted: 22 Mar 2018 8:49 EDT Last activity: 6 Apr 2018 19:26 EDT Closed few rules are not imported and it is causing an exception and build is failed Hi, We are tryinng to upgrade from Pega 6.2 to Pega 7.3.1. As we are on the process, migarte is fine. But, when we tried to run upgrade script, we are seeing below error com.pega.pegarules.pub.PRException: There were 18 instances that were not imported. and the build is failed. Attached is the log file. Can somebody help? System Administration Upgrades × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Moderation Team has archived post, learn more × Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years ago Posted: 22 Mar 2018 10:03 EDT × Close popover Penchalanarasimhulu Vendipalli (Narasimha522) PEGA Senior Technical Solutions Engineer Pegasystems Inc. IN View Profile Send Message Narasimha522 PEGA replied to Hareesh_Incessant Can you look into the below PDN link which might help https://pdn.pega.com/community/pega-7-upgrade-center/question/pega-61-sp2-pega-722-rules-upgrade-place-db-upgrade-resume Posted: 3 years ago Posted: 23 Mar 2018 3:36 EDT × Close popover Hareesh Paruchuri (Hareesh_Incessant) Incessant Technologies Technical Lead Incessant Technologies US View Profile Send Message Hareesh_Incessant Incessant Technologies replied to Narasimha522 Thanks Narasmiha. It says, we need to go for index of pzinskey in .PR_INDEX_REFERENCE table to make it faster. But, do not have answer for the asked one. Any other suggestions are welcome..!!