Client copy between service packs is inconsistent in 12.3.x

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

Client copy between service packs is inconsistent in 12.3.x, doc is not clear
The documentation states that a prerequisite is to "Ensure that both AE databases are of the same version."
It's not always consistent whether this work or not.  For example, you can copy between 12.3.1 and 12.3.2, but not between 12.3.1 and 12.3.3.
The assumption is that this is because there was a change to the db tables between 12.3.2 and 12.3.3, but the doc says this should be okay.

Tested in-house on all versions of 12.3.x - steps to reproduce:

1) Have a system on 12.3.x and 12.3.y
2) Update the ucybdbcc.ini file to have one of these as source and one as destination
3) Run client copy

Expected behavior:
Based on doc https://docs.automic.com/documentation/webhelp/english/AA/12.3/DOCU/12.3/Automic%20Automation%20Guides/help.htm#Utilities/admin_AE_DB_ClientCopy.htm#link3, these should all work since they are on the same version

Actual behavior:
12.3.1 utility does allow copy between 12.3.1 and 12.3.2 
12.3.1 utility does not allow between 12.3.1 and 12.3.3+ 
12.3.2 utility does allow between 12.3.1 and 12.3.2
12.3.2 utility does not allow between 12.3.2 and 12.3.3+ 
12.3.3 utility does not allow between 12.3.2 and 12.3.3+
12.3.3 utility does allow between 12.3.3 and 12.3.3+ 
12.3.4 utility does not allow between 12.3.2 and 12.3.3+
12.3.5 utilty does allow between 12.3 and 12.3.5
12.3.5 utility does not allow between 12.3.2 and 12.3.5
The following error shows:
U00036002 The two databases do not have identical database versions.
U00036079 Error when connecting to the database, please check the connection string and the database versions.

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

This behavior is as designed and the documentation will be updated to reflect this.  If there are changes to the database structure, the client copy will not work between service packs even on the same version.

Workaround:
Use a transport case instead if going from an older service pack to a newer service pack