> what did you mean about "we don't touch ZDU at this time anymore"?
Hm, how can I phrase this without getting in trouble?
We've performed a number of ZDU attempts over the last two years. Some worked wonderfully. Then there was the other kind. We had issues with ZDU where we couldn't finish it and also not roll back to the previous version (at least not without a db restore and accompanying data losses from backups) because that's the rarely mentioned inherit nature of the ZDU: once you commit to it, you need to finish it. Not today, but eventually.
When we further inquired into the various issues we encountered, we initially got responses about a supposedly correct procedure that didn't match up with the other materials published by Automic. For the record, this part should at least be rectified by now because I have been assured in the aftermath of it the support engineers have now received additional briefings on the procedures by the development, but I'm not in a position to attest to either.
Memory of what all the issues were exactly is rather hazy. You might find some threads here where I reported or inquired on some issues, it's quite likely actually :)
I do distinctly remember that at the core of one failed ZDU, we tried to get information on UC4 objects that supposedly had (or had not) to be deactivated before our ZDU could be finalized, and that we couldn't finalize it for weeks because of an error message about some table not being empty. We were fully commited to get to the bottom of this, but the issue (and any change of the support call) was eventually resolved when the monthly patch cycle rebooted the AE servers, thus cycling the whole thing at once - the exact avoidance of which is, imho, the point of the ZDU :)
So all things considered, and even with presumably issues fixed and processes improved since the early days of ZDU (please don't ban me from the forums just yet, Broadcom, mkay?), the lost trust in the mechanism has led us to conclude that when waging our options, we will only perform "classical" updates for the forseeable future. While that does incur about 1-2 hours of downtime for us, the impact of the downtime has been judged as more acceptable over the uncertainty.
Best regards,
Carsten
Original Message:
Sent: 08-06-2019 02:21 PM
From: Albrecht
Subject: New & changed ucsrv.ini options in v12.3
@Carsten Schmitz - what did you mean about "we don't touch ZDU at this time anymore"?