Thank you.

This seems like a database specific issue - we haven't seen anything like that before.
The easiest workaround would be to create a new user and give him the standard ID (and remove that standard ID from original user and disable that original user so that it doesn't use a licence)