If you upgrade that same 10.2 database directly to 10.3.1.3, which has DERBY-2896 fixed, do you see this problem?
10.3.1.1 and 10.3.1.2 are not official releases, and apart from the testing (I assume that's what you're doing, thanks!) should not be used. Note, that for 10.3.1.3 we also have a blocker issue, so that one's not the last of the 10.3 candidates... Myrna
