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>

Reminder

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

upgrade

iManager N2000BMS EnpowerDB always becomes full because of larger numbers of data

Publication Date:  2012-07-24 Views:  36 Downloads:  0
Issue Description
EnpowerDB usually becomes full . The problem can't be solved absolutely by dumping and expanding the database. 
Alarm Information
The part of environment monitor parameter can’t be displayed because of the full EnpowerDB. The sysmonitor prompts that the EnpoweDB occupy exceed the restrict.
Handling Process
After excute the follow script , there will not produce history data forever , then the EnpowerDB space problem can be sloved.
The script:
use EnpowerDB
go
truncate table tbl_EnpHistoryDataTab
drop trigger EnpEnvStatusTrigger
go
drop trigger EnpPowerAcInputTrigger
go
drop trigger EnpPowerBatteryLoopTrigger
go
drop trigger EnpPowerBatteryGroupTrigger
go 
drop trigger EnpPowerDcOutTrigger
go
If you want to recover the ability to produce the history data,  please refer to the script in adjunct.
This method avoids to expand database and not be limited by version.
Root Cause
EnpowerDB is used to save the environment monitor data , larger numbers of history data will lead the full of EnpowerDB. The triggers produced the history data and it is no meaning to customer.
Suggestions
Null

END