Server error thrown in localhost log during upgrade when there is a [sys_db_object] record with empty name


Description

Error "sys_db_object has nil/empty name, skipping in DBObjectManager.load" in localhost logs when there is a [sys_db_object] record with an empty name.

Steps to Reproduce

1. Create a sys_db_object record with empty name and note the new record sys_id

2. Trigger the db upgrade

3. After the upgrade is completed, check the localhost log for the multiple errors on the ew record sys_id:
"SEVERE *** ERROR *** sys_db_object has nil/empty name, skipping in DBObjectManager.load: <sys_db_object's sys_id>"

Workaround

This problem is fixed in the next upcoming release. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to.

The error can be ignored as it just get logged but does not affect processing.


Related Problem: PRB1039226