Knowledge Base
Showing results for 
Search instead for 
Did you mean: 

Can not add additional histories to an existing Niagara G3 SQL database. The error messages "javax.baja.sys.BajaRuntimeException" and "Caused by: java.sql.Batch...


The following error messages are displayed in the Application Director output windows when attempting to add additional histories to a existing SQL database.

at javax.baja.rdb.history.BRdbmsHistoryExport.insertMetaRecord(
at javax.baja.rdb.history.BRdbmsHistoryExport.exportRecords(
at javax.baja.rdb.history.BRdbmsHistoryExport.doExecute(
at auto.com_tridium_rdb_sqlserver_history_BSqlServerHistoryExport.invoke(AutoGenerated)
at com.tridium.sys.schema.ComponentSlotMap.invoke(
at com.tridium.sys.engine.EngineUtil.doInvoke(
at javax.baja.sys.BComponent.doInvoke(
at javax.baja.util.ThreadPoolWorker$
Caused by: java.sql.BatchUpdateException: Invalid column name 'INTERVAL_'.
at net.sourceforge.jtds.jdbc.JtdsStatement.executeBatch(
at org.apache.commons.dbcp.DelegatingStatement.executeBatch(
at javax.baja.rdb.history.BRdbmsHistoryExport.insertMetaRecord(

... 8 more


G3 Niagara, 3.4 and later, SQL


The term INTERVAL was a keyword in some SQL dialects, so the column name was changed from INTERVAL to INTERVAL_ in the database schema. The database schema changed between 3.3 and 3.4.


The following changes needed to be made to the SQL database.

  1. Altered the existing HISTORY_CONFIG table in the SQL database to change the column to INTERVAL_.
  2. Altered the HISTORY_CONFIG table, added a column called SYSTEMTAGS, set up as VARCHAR(500).
  3. Changed SOURCE column length to VARCHAR(500) in the HISTORY_CONFIG table
Tags (1)
Labels (1)
Version history
Revision #:
1 of 1
Last update:
2 weeks ago
Updated by: