The synchronized data is too large, leading to shareplex timeout, and the synchronization session is automatically killed.

Source: Internet
Author: User

Database migration, where there is an index for a table with a large amount of data. during migration, the synchronization times out.

Notice 15:14:54. 856107 14240 3892311808 poster: Operation odr_ddl on table "cmuser ". "tbl_cm_packagepushsession_r" is taking longer than 5 seconds. SID/SERIAL: 719/35771 subqueue: 1. (posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:15:11. 425538 14240 3838027520 S: 1 poster: Replicated DDL ". alter table cmuser. tbl_cm_packagepushsession_r. add constr... "(posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:19:12. 820272 14240 3838027520 S: 1 poster: Replicated DDL ". alter table tbl_cm_userservice logging. "(posting from dbuis, queue dbuissplex, todbuis) [module OPO] Notice 15:19:49. 960636 14240 3892311808 poster: Operation odr_ddl on table is taking longer than 5 seconds. SID/SERIAL: 719/35771 subqueue: 1. (posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:19:57. 267446 14240 3838027520 S: 1 poster: Replicated DDL ". create index cmuser. idx_wlvi_fk_date on cmuser. tbl_cm_white... "(posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:20:23. 243563 14240 3838027520 S: 1 poster: Replicated DDL ". create index cmuser. idx_rere_uid_fk_type on cmuser. tbl_cm_r... "(posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:20:59. 973385 14240 3892311808 poster: Operation odr_ddl on table is taking longer than 5 seconds. SID/SERIAL: 719/35771 subqueue: 1. (posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:21:38. 667181 14240 3838027520 S: 1 poster: Replicated DDL ". create index cmuser. idx_cm_packagespush_h_n on cmuser. tbl_c... "(posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:26:13. 815592 14240 3892311808 poster: Operation odr_ddl on table is taking longer than 5 seconds. SID/SERIAL: 719/35771 subqueue: 1. (posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Warning 15:27:08. 728807 14240 8869728 poster: main thread is waiting 59 seconds for session-1 to commit before processing next operation. (posting fromdbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:27:08. 855210 14240 8869728 poster: no locks found (posting from dbuis, queue dbuissplex, to dbuis) [module OSP] Notice 15:27:09. 412913 14240 3892311808 poster: Operation odr_ddl on table is taking longer than 61 seconds. SID/SERIAL: 719/35771 subqueue: 1. (posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Warning 15:28:08. 864055 14240 8869728 poster: main thread is waiting 119 seconds for session-1 to commit before processing next operation. (posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Notice 15:28:08. 983965 14240 8869728 poster: no locks found (posting from dbuis, queue dbuissplex, to dbuis) [module OSP] Notice 15:28:09. 508029 14240 3892311808 poster: Operation odr_ddl on table is taking longer than 121 seconds. SID/SERIAL: 719/35771 subqueue: 1. (posting from dbuis, queue dbuissplex, to dbuis) [module OPO] Show post view operationstarget status posted since total backlog. dbuis running 0 19-aug-14 13:05:42 10321921 10318726 the value of Operations posted was found to be null, indicating that it was not uploaded and viewed from the database, it is found that the transmission is interrupted because the synchronization is not completed within 900 seconds, so it will be disconnected. You can modify sp_ctrl> set Param sp_opo_max_oexn_time 3600 to change the time to 3600 seconds, at this time, the post process does not need to be stopped. After the next timeout, the post process will resume normal after the modification is restarted.

The synchronized data is too large, leading to shareplex timeout, and the synchronization session is automatically killed.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.