Issue
Symptoms
The following message appeared when attempting to commit and update set:
"The table name must be non nil."
Release
Seen in Jakarta Patch 8
Cause
The error is related to a table with an empty name and label. ServiceNow Support can search the application logs to find the name of the table causing the error, and recreate it if needed.
Example:
017-06-07 19:09:08 (669) worker.5 worker.5 SEVERE *** ERROR *** sys_db_object has nil/empty name, skipping in DBObjectManager.load: 54ce2fdbdb056a0025affcb6ae961967
Resolution
Submit an incident to ServiceNow Customer Support to report the incident. The table may need to be deleted along with the supporting records and recreated.
