Thanks again for the information. I didn't know all that.
No, the update statement still doesn't work.
Could not execute 'UPDATE _sys_repo.active_object SET change_number = 65835, released_at = '2015-09-02 ...' in 5.482 seconds .
[129]: transaction rolled back by an internal error: TrexUpdate failed on table '_SYS_REPO:ACTIVE_OBJECT' with error: commitOptimizeAttributes() failed with rc=6900, Attribute engine failed; table '_SYS_REPO:ACTIVE_OBJECT$delta_1$', rc=6900 - enforce TX rollback
I guess I'm dealing with a memory issue. The instance I'm having trouble with is installed locally on a VM with more or less 35GB of RAM.
We have another instance in CAL (Amazon) and I could enable change recording on the first try. Now, I'm reading OSS 1999997 - FAQ: SAP HANA Memory which an incredible number of 150 versions. This note indicates that "SQL error 129 while accessing table <table_name>" my be a memory issue.
I'm comparing all configuration from the administration panel from both systems to check if something memory related is substantially different.