Discussion5Replies1681Views×Close popoverArundhati Das (ARUNDHATI) Capgemini Capgemini IN View ProfileSend Message ARUNDHATI Member since 2014 5 posts Capgemini Posted: October 30, 2015Last activity: October 4, 2018Posted: 30 Oct 2015 0:47 EDTLast activity: 4 Oct 2018 11:08 EDT Closed Unable to save operator id after upgradeHi,We have upgraded from 6.2 to 7.1.8. After upgrade we are unable to save Operator ID as its giving below error. Please help.Save failed: Unable to open an instance using the given inputs: pxObjClass = "Data-Preference-Operator", pyUserIdentifier = "zkycyv7"**Moderation Team has archived post**This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post. System Administration Upgrades ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion. Posted: 5 years agoPosted: 30 Oct 2015 2:07 EDT×Close popoverChetan Shrivastava (__ChetanS7293) Pegasystems Inc. Principal Software Engineer - Customer Success Pegasystems Inc. IN View ProfileSend Message__ChetanS7293 Pegasystems Inc. replied to ARUNDHATIFrom Pega 7.1.8 onwards , there is a new table introduced for operator preference PR_Oprator_Pref, can you see if you have this table in your setup, I doubt if the upgrade was successful. Posted: 5 years agoPosted: 30 Oct 2015 2:20 EDT×Close popoverArundhati Das (ARUNDHATI) Capgemini Capgemini IN View ProfileSend MessageARUNDHATI Capgemini replied to ARUNDHATII found the table PR_Operator_Prefs in database but that is empty. What should be done now? Posted: 5 years agoPosted: 12 Jan 2016 4:38 EST×Close popoverBhushan Patil (BHUSHANPATIL) Cognizant Technology Solutions Bhushan Patil Cognizant Technology Solutions US View ProfileSend MessageBHUSHANPATIL Cognizant Technology Solutions replied to ARUNDHATIwhat was solution for this? Posted: 5 years agoPosted: 22 Jan 2016 20:15 EST×Close popoverArundhati Das (ArundhatiD) Infosys Infosys US View ProfileSend MessageArundhatiD Infosys replied to BHUSHANPATILchanged data source from XA to non XA, it resolved the issue Posted: 3 years agoPosted: 20 Oct 2017 14:38 EDT×Close popoverNagoor Khasim Shaik (NagoorShaik) Scotiabank Consultant Scotiabank CA View ProfileSend MessageNagoorShaik Scotiabank replied to ARUNDHATIHi, We are also facing the same issue. Do we need to re run the upgrade scripts after changing the data source from XA to Non-XA? Please confirm. Thanks, Nagoor.