On the Administer tab of the portal, in the Database section, the system administrator can choose Modify/View a Database Schema. When this function is chosen, and the database is selected, after the Administrator clicks Next , the Select a Table form appears:
If the Administrator clicks on the Resave Table button, messages similar to the following may occur:
Resaving instances of AtPega-Task (Class: 1 of 9) Saved 0 instances of AtPega-Task Resaved 0 instances for AtPega-Task (0 of 0)
Resaving instances of AtPega-Task-Support (Class: 2 of 9) Saved 0 instances of AtPega-Task-Support Resaved 0 instances for AtPega-Task-Support (0 of 0) Resaving instances of AtPega-Task-Support-Request (Class: 3 of 9)
Error: Failed to resave page: Database-LockFailure-LockLost ATPEGA-TASK null (Key: Resave) Error: Failed to resave page: Database-LockFailure-LockLost ATPEGA-TASK SR-1 null (Key: Resave)
Error: Failed to resave page: Database-LockFailure-LockLost ATPEGA-TASK SR-10 null (Key: Resave)
Error: Failed to resave page: Database-LockFailure-LockLost ATPEGA-TASK SR-100 null (Key: Resave)
The Resave Table function opens all instances of the specified class and resaves them. This process does not involve locking any of the instances - just an open and resave.
However, due to improvements in security in Version 4.2 SmartBuild Release (SP2), all classes that have Locking functionality enabled must have a lock taken out in order to save them, so errors occur.
ForV4.2 SP2, SP3, SP4, and SP5:
Do not use the Resave Table button.
Identify the classes in the system which are saved to the table (by checking the Data-Admin-DB-Table class) and resave these classes using the Resaver Servlet.
Note: In V4.2SP6+ the Resave Table button is no longer present on this form