日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問 生活随笔!

生活随笔

當前位置: 首頁 > 编程资源 > 编程问答 >内容正文

编程问答

【搜索引擎】Smartsys部署ES的准备工作

發布時間:2025/5/22 编程问答 30 豆豆
生活随笔 收集整理的這篇文章主要介紹了 【搜索引擎】Smartsys部署ES的准备工作 小編覺得挺不錯的,現在分享給大家,幫大家做個參考.
1. 擴展表空間

擴展SMARTSYS_HISTORY和SMARTSYS_HISTORY表空間,使當前使用率降至40%或以下。

2. 將現有歷史事項表重命名
ALTER TABLE scada_event rename to scada_event_bak; ALTER INDEX SCADA_EVENT_INDEX rename to SCADA_EVENT_INDEX_BAK; ALTER INDEX SCADA_EVENT_INDEX2 rename to SCADA_EVENT_INDEX2_BAK;
3. 創建新的帶自增字段的歷史事項表
CREATE TABLE "SMARTSYS"."scada_event" ( "ID" BIGINT IDENTITY(1,1) CLUSTER PRIMARY KEY, "KEY_ID_TAG" VARCHAR(100) DEFAULT 'dummy' NOT NULL, "TAG_ID" BIGINT NOT NULL, "OCCUR_TIME" TIMESTAMP(0), "MILLI_SECOND" INTEGER NOT NULL, "SOE_TIME" TIMESTAMP(0), "SOE_MSECOND" INTEGER, "DOMAIN_ID" INTEGER, "STATION_ID" BIGINT NOT NULL, "REGION_ID" INTEGER, "INFER_NAME" VARCHAR(64), "ALARM_PRIORITY" INTEGER, "STATUS" INTEGER, "CONTENT" VARCHAR(256), "CONFIRM_TIME" TIMESTAMP(0), "CONFIRM_NODE_NAME" VARCHAR(64), "ALARM_TYPE" INTEGER NOT NULL, "APP_ID" INTEGER, "CONTAINER1_ID" BIGINT, "CONTAINER2_ID" BIGINT, "DEV_ID" BIGINT, "CONFIRM_USER_NAME" VARCHAR(64), "CONTEXT" INTEGER, "SYSID" INTEGER DEFAULT 1 NOT NULL, "AREA_RESP" INTEGER DEFAULT (-1) NOT NULL, "OBJ_ID" BIGINT, "REASON_CODE" INTEGER, "DICTIONARY" CHARACTER VARYING(512), "VALUE" DOUBLE) STORAGE(ON "SMART_HISTORY", CLUSTERBTR); CREATE INDEX "SCADA_EVENT_INDEX" ON "SMARTSYS"."scada_event"("DEV_ID" ASC,"OCCUR_TIME" ASC,"OBJ_ID" ASC,"STATION_ID" ASC,"CONTAINER1_ID" ASC,"ALARM_TYPE" ASC,"STATUS" ASC) STORAGE(ON "SMART_HISTORY_INDEX", CLUSTERBTR) ; CREATE INDEX "SCADA_EVENT_INDEX2" ON "SMARTSYS"."scada_event"("OCCUR_TIME" ASC,"ALARM_TYPE" ASC,"STATUS" ASC,"STATION_ID" ASC,"CONTAINER1_ID" ASC,"CONTAINER2_ID" ASC) STORAGE(ON "SMART_HISTORY_INDEX", CLUSTERBTR) ;

經過對金倉和達夢數據庫的測試,在執行步驟1和2的時候不需要停Smartsys系統,切換過程持續幾秒鐘,事項可能會存在及少量的丟失,但不會影響切換結果。

4. 根據需要將部分舊的事項數據從SCADA_EVENT_BAK中,分批導入ES。
--1. 分批次遷移歷史數據,分批的目的在于將每次的數據提交量控制在5000 0000條以下,以防止臨時緩沖區不足。 insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-08-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-07-01' and occur_time < '2019-08-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-06-01' and occur_time < '2019-07-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-05-01' and occur_time < '2019-06-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-04-01' and occur_time < '2019-05-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-03-01' and occur_time < '2019-04-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-02-01' and occur_time < '2019-03-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time >= '2019-01-01' and occur_time < '2019-02-01'; commit;insert into SCADA_EVENT(KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME, CONFIRM_NODE_NAME,ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE") select KEY_ID_TAG,TAG_ID,OCCUR_TIME,MILLI_SECOND,SOE_TIME,SOE_MSECOND,DOMAIN_ID,STATION_ID,REGION_ID,INFER_NAME,ALARM_PRIORITY,STATUS,CONTENT,CONFIRM_TIME,CONFIRM_NODE_NAME, ALARM_TYPE,APP_ID,CONTAINER1_ID,CONTAINER2_ID,DEV_ID,CONFIRM_USER_NAME,"CONTEXT",SYSID,AREA_RESP,OBJ_ID,REASON_CODE,"DICTIONARY","VALUE" from scada_event_bak where occur_time < '2019-01-01'; commit;

這一步驟需要花費較長時間,根據實測數據顯示,插入效率大約為:4000 0000條/小時。完成后需要檢查執行日志(打印信息),確認每條語句都已經執行成功,并提交完成。

5. 運行ES遷移程序,將新SCADA_EVENT的內容遷移至ES中,并保持該遷移程序持續運行,按既定策略定期完成數據從SCADA_EVENT到ES的同步。

總結

以上是生活随笔為你收集整理的【搜索引擎】Smartsys部署ES的准备工作的全部內容,希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯,歡迎將生活随笔推薦給好友。

主站蜘蛛池模板: 欧美日韩国产成人 | 新中文字幕| 日韩精品片 | 麻豆最新 | 黑人一级女人全片 | 告诉我真相俄剧在线观看 | 久久综合久久鬼色 | 欧美你懂的 | 亚洲美女视频网 | 人与拘一级a毛片 | 超碰日日干| 亚洲色图 校园春色 | 国产裸体视频网站 | 精品久久无码中文字幕 | 手机看片99 | www.夜夜骑| 在线播放波多野结衣 | www天天干| 婷婷综合色 | 亚洲一级二级片 | 糖心logo在线观看 | 日本精品视频一区二区 | 伊人免费视频二 | 欧美激情一区二区三区免费观看 | 久久久精品久久久 | 精品三区 | 亚洲欧洲一二三区 | 国产污视频在线播放 | 色婷婷视频 | www.x日本| 国产草草浮力影院 | 一区二区视频播放 | 狠狠狠狠狠狠狠干 | 国产精品一区二区性色av | 熟睡人妻被讨厌的公侵犯 | 美日韩视频 | 亚洲一区二区三区四区五区xx | 亚洲欧美第一页 | 麻豆传媒一区二区三区 | 在线免费av观看 | 国产三级三级三级 | 日本高清视频网站 | www.精品国产 | 亚洲视频观看 | 国产精品久久欧美久久一区 | 国产一区二区小视频 | 中国爆后菊女人的视频 | 国产精品一区二区麻豆 | 亚洲中文字幕无码av | 精品嫩模一区二区三区 | 男女做网站 | 日韩久久久久久久久 | 射影院| 国产一区二区在线免费观看视频 | 国产成人三级在线观看 | 另类男人与善交video | 猛1被调教成公厕尿便失禁网站 | 久久加久久 | 老女人乱淫 | 免费观看黄色 | 欧美精品xx| 黄色三级av | 丝袜av网站 | 激情婷婷六月天 | 玖草视频在线 | 久久精品午夜 | a√天堂在线 | 欧美精品aa | 五月天一区二区 | 国产看真人毛片爱做a片 | 亚洲av无码一区二区三区在线观看 | 在线看视频 | 成人a毛片久久免费播放 | 久久久女人 | 男人久久久| 涩涩视频软件 | 丰满雪白极品少妇流白浆 | 国产精品久久久久久久久久久久 | 久伊人| 亚洲国产欧美一区 | 亚洲高h | 日韩精品视频免费在线观看 | 女性裸体不遮胸图片 | 北条麻妃一区二区三区 | 自拍三区| 色婷婷在线影院 | 欧美激情网 | 亚洲综合色视频 | 久草最新网址 | 国产视频福利 | youjizz.com日本| 国产美女一级视频 | 午夜成年视频 | 色在线免费视频 | 欧美无人区码suv | 黄色av影院| 欧美人成在线 | 天天宗合 | 五月婷婷开心中文字幕 |