Harriet_Kim_1764

A non-ZDU hotfix upgrade simulates a cold start

Discussion created by Harriet_Kim_1764 on Jan 12, 2018
A user does not want a cold start to occur after a manual hotfix upgrade because it causes a negative impact on their AE system.
Is it possible to avoid this?

Investigation
A review of the DB Load log shows a simulated cold start occurs prior to loading the new initial data:

20180109/132542.237 - U00038042 Simulate Startmode=COLD
20180109/132542.237 - U00038082 delete from MQ1CP001
20180109/132542.240 - U00038082 delete from MQ1CP002
20180109/132542.244 - U00038082 delete from MQ1CP003
20180109/132542.246 - U00038082 delete from MQ1CP004
20180109/132542.369 - U00038082 delete from MQ1CP005
20180109/132542.373 - U00038082 delete from MQ2CP001
20180109/132542.375 - U00038082 delete from MQ2CP002
20180109/132542.379 - U00038082 delete from MQ2CP003
20180109/132542.383 - U00038082 delete from MQ2CP004
20180109/132542.385 - U00038082 delete from MQ2CP005
20180109/132542.388 - U00038082 delete from MQ1DWP
20180109/132542.391 - U00038082 delete from MQ1JWP
20180109/132542.394 - U00038082 delete from MQ2DWP
20180109/132542.396 - U00038082 delete from MQ2JWP
20180109/132542.534 - U00038082 delete from MQLS
20180109/132542.543 - U00038082 delete from MQMEM
20180109/132542.547 - U00038082 delete from MQ1OWP
20180109/132542.608 - U00038082 delete from MQ1PWP
20180109/132542.612 - U00038082 delete from MQ1QWP
20180109/132542.614 - U00038082 delete from MQ1RWP
20180109/132542.618 - U00038082 delete from MQ2OWP
20180109/132542.620 - U00038082 delete from MQ2PWP
20180109/132542.621 - U00038082 delete from MQ2QWP
20180109/132542.623 - U00038082 delete from MQ2RWP
20180109/132542.627 - U00038082 delete from MQSRV
20180109/132542.633 - U00038082 delete from MQ1WP
20180109/132542.828 - U00038082 delete from MQ2WP
20180109/132542.830 - U00038042 Loading Initialdata ... 

Cause
This behavior is by design because there are possible different message structures used in old WPs that do not match with the new WPs structure. As a result, jobs will not process.

Solution
Use ZeroDowntime Upgrade because it does not require a cold start.



Outcomes