You will see the following message in the Gatway error log in the $EM_HOME/log directory: [08@20:29:32.999:] ===> ERROR: Update from Data Center upctm received with wrong update sequence number, received = 10000000, should be = 100000000, communication stopped Note the exact numbers for the update sequence number for "received" and "should be" - they will be 10000000 and 100000000 exactly, not other (random/mixed) numbers. And then these numbers will increment by only 1 (e.g. 10000001), however will remain "out of sync". And you then sometimes expect to receive Database Update ERRORs. CONTROL-M/Enterprise Manager (version 6.3.01)
CONTROL-M/Enterprise Manager (version 6.4.01) |
Legacy ID:KA306796 CAR ID: CAR00039953 for the situation where communication between CONTROL-M/Server and CONTROL-M/EM is broken as the Update level exceeds 100 million (i.e. 100000000) and it fails to recover.
The CONTROL-M/EM Gateway log file contains the following message: ERROR: Update from Data Center <XXX> received with wrong update sequence number, received = 10000000, should be = 100000000, communication stopped
The Update level should be reset to zero as a result of a Download however this does not happen.
The root-cause of this problem is that fact the counter for Updates from CONTROL-M/Server to CONTROL-M/EM is never reset to 0. The size of this field in our communication protocol allows only a number as high as 99999999. Therefore when that number is reached, the next Update gets a truncated number and CONTROL-M/EM closes the communication. A new Download will not help since the counter remains too high to be contained in the field size.
The counter is only reset when the communication between CONTROL-M/Server and CONTROL-M/EM is stopped (e.g. the Gateway is Down) and the CONTROL-M/Server continues to work and generate Updates. When the total number of Updates accumulated is more than CD_MAX_DBU (default 1000), all of the Updates are cleared from the CONTROL-M/Server Database. When the Gateway is again Up and the CONTROL-M/EM again connects to the CONTROL-M/Server a new Download is initiated and the counter returns to 0. (It seems that Customer who keeped their CONTROL-M/EM working without the Gateway ever going down for long periods of time would eventually encounter this problem - depending of course on the rate the CONTROL-M/Server produces Updates).
You can detect if a CONTROL-M/Server is in danger of the counter getting too large with the following SQL command: SQL> select max(DBULVL) from CMR_DBLOG; Check to see if the figure received is getting close to 100000000
The preventive action if the Update counter is too close, or indeed if the problem has occurred, is the following: 1). shut down the Gateway while the CONTROL-M/Server continues to work (e.g. from the CONTROL-M/EM Administrator Facility/CCM GUI) 2).run the utility reset_ecs on the CONTROL-M/Server side or force download option in the troubleshooting menu of CONTROL-M/server .
(Please note that it is generally not a good idea to reduce the CD_MAX_DBU value from the default of 1000, and changes at New Day do NOT contribute to Updates so this period cannot be used for this purpose).
This "workaround" is generally preferred over deleting the CONTROL-M/Server DataCenter and defining it with a new Code in order to zero the Counter. ************************* This Item has been corrected in Control-M/Server version 6.4.01 Fix Pack 3 ************************* Related Products:
|