What is the Meaning of the alarm: Insert bulk failed due to a schema change of the target table

Document ID : KB000034364
Last Modified Date : 14/02/2018
Show Technical Document Details

Question: 

What is the Meaning of the alarm:  Insert bulk failed due to a schema change of the target table

 

Answer: 

The data_engine may generate an alarm that says "Insert bulk failed due to a schema change of the target table." This is most likely to happen during the housekeeping procedures which, among other things, are reindexing the tables at the same time the data_engine is bulk-inserting new records into the tables.

For example, the bulk insert contains a row for a insert on a locked object (being reindexed). The data_engine detects this, and saves all of the existing bulk insert packages. It then reinitializes the connection to the database (to make sure there isn't a problem), then inserts the saved bulk packages, and continues processing the data. So no data are being lost in this process.

This is behavior by design, and has been implemented to catch the several hundred error conditions which can be generated from the ADO layer, if something goes wrong

By default, these alarms are issued with severity = critical. There is an option to set the alarm_severity flag in the raw-configure module of the data_engine to raise these alarms with a different alarm level if that's desirable. But the drawback is of course that you might get into a situation where the ADO layer generates a generic error message which you might want to give attention. Unfortunately we're unable to control the messages provided by this layer, so we just present them when they come.