Forum Home › Forums › Understanding the Software › Export data module manual exist?
Tagged: Data export, SQL
- This topic has 11 replies, 4 voices, and was last updated 4 years ago by
Mikhail.
-
AuthorPosts
-
August 30, 2015 at 4:24 pm #334
Romiros
ParticipantHi, Mikhail.
How to use Export data module?
I connect ModDBExport.dll.
Could you please write an example of SQL queryAugust 31, 2015 at 12:09 pm #359Romiros
ParticipantThank you.
September 1, 2015 at 6:43 am #370Romiros
ParticipantHi, I’ve read manual
Current data and Events work.
Archive data dont work. There may be additional options?September 1, 2015 at 8:48 am #371Mikhail
ModeratorPlease, write more info.
September 1, 2015 at 9:59 am #379Romiros
ParticipantSQL query from tab “Arh Data” (Архивные данные) in the export module dont work
in Scada minute and hour records are present.
I use MySQL.September 1, 2015 at 2:40 pm #384Mikhail
ModeratorIs there a error in C:\SCADA\ScadaServer\Log\ModDBExport.log ?
If so, please post here a error message.September 1, 2015 at 3:55 pm #388Romiros
Participantfrom log:
2015-09-01 18:34:05 Ошибка при экспорте текущих данных в БД MySQL – localhost: Duplicate entry ‘2015-09-01 18:32:42-1’ for key ‘PRIMARY’
from log 2:
Модуль экспорта данных
———————-
Состояние: нормаИсточники данных
—————-
1. MySQL – localhost; состояние: ошибка экспорта; в очереди тек/арх/соб: 5/0/0; экспортировано тек/арх/соб: 18/0/11; пропущено тек/арх/соб: 0/0/0Current data is written normally, although the error log. Archives no. Another question – historical data are written into the same table, or need to create another?
Прошу прощения за мой английский
Текущие данные пишутся нормально, хотя в логе ошибка. Архивов нет. Еще вопрос – архивные данные пишутся в ту же таблицу или надо создавать отдельную?September 1, 2015 at 6:13 pm #389Mikhail
ModeratorI think, it works as expected.
Export current data error occurs because you send the same data twice.
Export archive data is executed, for example, when you select Generator in SCADA-Server and send archive data.Current and historical data are stored in the same data table in case of using SQL from the manual.
May 6, 2016 at 7:53 am #1091fahrur
Participanthi mikhail,
i cant find any documentations using ModDBExport modul, and database / table configuration inside mysql,i try to export to my sql heres the log:
ModDBExport.log :
____________——————————————————————————–
2016-05-06 14:41:37 Start ModDBExport module
2016-05-06 14:43:20 Module ModDBExport is stopped
——————————————————————————–
——————————————————————————–
2016-05-06 14:43:22 Start ModDBExport module
2016-05-06 14:44:30 Unable to enqueue current data. The maximum size of the queue 100 is exceeded
2016-05-06 14:44:30 Unable to enqueue current data. The maximum size of the queue 100 is exceeded
2016-05-06 14:44:31 Unable to enqueue current data. The maximum size of the queue 100 is exceeded
2016-05-06 14:44:31 Unable to enqueue current data. The maximum size of the queue 100 is exceeded____________
and
ModDBExport.txt :
____________
Export Data Module
——————
State: normalData Sources
————
1. MySQL – 192.168.10.71; state: normal; in queue cur/arc/ev: 100/0/0; exported cur/arc/ev: 0/0/0; skipped cur/arc/ev: 1149/0/0____________
thks.-
This reply was modified 9 years, 3 months ago by
fahrur.
May 6, 2016 at 9:35 am #1093Mikhail
ModeratorHi,
The manual is inside the installation package. The file name is Doc\dbexport_en.pdf
Try using database model and scripts from the manual.July 29, 2021 at 2:43 am #9309Sergei
ParticipantWhich pdf manual? Is it the same as the online documentation available today? (as of 2021.07.28)
July 29, 2021 at 12:52 pm #9313 -
This reply was modified 9 years, 3 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.