[CAUSE] The tmnxOesDbInvalid notification may be raised under the following conditions: 1) During initial installation, if the OES is not properly commissioned; 2) The serial number in the database does not match that of the OES either because the controller was replaced or the alarm card was replaced; 3) A downgrade of OES software has occurred; 4) Equipment Controller is removed/reseated during a system process, causing file corruption; 5) The database audit failed indicating some type of corruption of the database. [EFFECT] The OES is not in a normal operating mode. It does not have the correct configuration and the state of its cards is unpredictable. As a result, the OES will not boot normally and not all commands are allowed. [RECOVERY] A database corruption on the OES requires that the OES be re-commissioned. The correct database is held in the host system so it will be restored to the shelf once the existing database is cleared and the host re-establishes communication with the OES.