日韩性视频-久久久蜜桃-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的准备工作的全部內容,希望文章能夠幫你解決所遇到的問題。

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

主站蜘蛛池模板: 人人夜| 91视频最新入口 | 香蕉视频免费在线播放 | 已满18岁免费观看电视连续剧 | 91打屁股 | 精品动漫一区二区 | 男女男精品视频站 | 欧美日韩亚洲激情 | 色欲一区二区三区精品a片 在线观看黄网站 | av电影中文字幕 | 黄色小说网站在线观看 | 福利一区福利二区 | 青娱乐国产在线视频 | 人人干人人搞 | 国产一区二区三区久久久 | 麻豆毛片| 特a级黄色片 | 日本高清有码视频 | av在线你懂的 | 香蕉视频色版 | 欧美一区精品 | 麻豆久久久午夜一区二区 | 久久在线精品 | 精品午夜一区二区 | 亚洲一二三四五 | 国内一级黄色片 | 亚洲成熟女性毛茸茸 | 欧美成人h版| 欧美一区二区三区视频在线观看 | 亚洲无码乱码精品国产 | 成人欧美一区二区三区黑人孕妇 | 夜夜撸小说 | 日韩欧美亚洲国产 | 脱女学生小内内摸了高潮 | 天天躁夜夜躁av天天爽 | 毛茸茸多毛bbb毛多视频 | 黄色三级网 | 姐姐你真棒插曲快来救救我电影 | 国产一区二区在线观看免费 | 成年人免费在线观看视频网站 | 波多野吉衣一区 | 色综合视频在线 | 亚洲一区二区三区中文字幕 | 亚洲精品乱码久久久久久久久久久久 | 在线电影一区二区三区 | 潘金莲一级淫片aaaaaa播放 | 脱女学生小内内摸了高潮 | 亚洲熟妇无码久久精品 | 国产绿帽刺激高潮对白 | 91香蕉在线看 | 香蕉黄视频 | 91av视频| 伦理片一区二区三区 | 日韩三级视频在线 | 在线观看免费的av | 日本欧美国产 | 丝袜一级片 | 色婷婷成人网 | 欧美三级中文字幕 | 超碰人人草人人干 | 天堂av亚洲 | 午夜精品久久久久久久99热黄桃 | 亚洲91视频 | 成人av网站免费 | 女人被男人操 | 香蕉av在线| 牛牛影视一区二区 | 米奇狠狠干 | 国产免费无码一区二区 | 天天射天天操天天干 | 欧美日韩视频一区二区三区 | 影视av | 国产成人午夜高潮毛片 | 91黄瓜| 爱情岛亚洲品质自拍极速福利网站 | 欧美视频精品在线 | 乱岳| 91丨porny丨对白 | 男生操女生免费网站 | 欧洲成人在线视频 | 丁香六月久久 | 激情六月丁香 | 国产大片一区 | 中国 免费 av | 黑人精品一区二区三区 | 成人午夜电影网站 | 97精品国产97久久久久久春色 | 美女在线一区 | 成人免费网站www网站高清 | 亚洲欧洲在线视频 | 亚洲一区观看 | 亚洲色图二区 | 国产97视频| 欧美xxxx83d| 国产性猛交xxxⅹ交酡全过程 | 国产成人啪精品午夜在线观看 | 91福利视频在线观看 | 欧美成人天堂 | 亚洲精品电影在线 |