No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


EnpowerDB of the N2000 BMS Is Always Full Because of Overmuch History Data

Publication Date:  2012-07-25 Views:  60 Downloads:  0
Issue Description
The EnpowerDB is always full. The problem is not solved thoroughly after a dumping mechanism is used or the database capacity is expanded. 
Alarm Information
As the EnpowerDB is full, certain parameters of environment monitoring fail to be displayed on the N2000 BMS. The monitoring system prompts that the space usage of the EnpowerDB exceeds the threshold. 
Handling Process
To effectively solve the problem, you can run the following scripts so that the system does not generate history data any more.
The scripts are as follows:
use EnpowerDB
truncate table tbl_EnpHistoryDataTab
drop trigger EnpEnvStatusTrigger
drop trigger EnpPowerAcInputTrigger
drop trigger EnpPowerBatteryLoopTrigger
drop trigger EnpPowerBatteryGroupTrigger
drop trigger EnpPowerDcOutTrigger
To restore the capacity of producing history data of the system, run the scripts in the Appendix.
This method avoids database expansion and is not restricted by versions. 
 R8 and R11 BMS are available this case.
Root Cause
The EnpowerDB is used for saving the environment monitoring data. A large amount of redundant history data leads to full capacity of the EnpowerDB.
The history data is produced by the trigger and does not make sense for customers.