We are experiencing an issue with a specific repository where saved sets disappear from the UI a few minutes after creation. Although the record for the saved set remains in the B_SAVED_SET table, it is deleted from the B_SAVED_SET_REPO table. This problem is isolated to this particular repository, as saved sets in other repositories function correctly.
When attempting to re-add the saved set to the UI, it indicates that the saved set still exists because it remains in the B_SAVED_SET table. To address this, we delete the remnants of the saved set using the following SQL commands and then recreate it in the UI. We create the saved set again in the UI. However, the issue reoccurs after a few minutes:
DELETE FROM B_SAVED_SET_ITEM WHERE SAVED_SET_ID = 113305;
DELETE FROM B_SAVED_SET_REPO WHERE SAVED_SET_ID = 113305;
DELETE FROM B_SAVED_SET WHERE SAVED_SET_ID = 113305;
We have tried changing the name of the saved set and adjusting the shared setting. Additionally, I manually set the Temporary_IND column in B_SAVED_SET to ensure it was not marked as a temporary saved set. Despite these efforts, the saved set continues to be deleted.
I have also searched the WebMaster, EPX, and Worker logs for any log messages related to the saved set name and ID but found none.
Are there any configurations or settings that could prevent the creation of permanent saved sets in a repository? If not, what other methods can we use to diagnose this issue?
------------------------------
Joseph McHugh
MDM Solution Engineer
Volvo IT North America
NC
------------------------------