Getting com.glide.db.GlideSQLException after increasing max length of the field

[timofeevbog]

I have created an update set where max length of 2 fields (u_ip_address and u_ip_address2) of table cmdb_ci are increased from 40 to 80. When trying to edit ip address via form, u_ip_address2 is ok (it can be up to 80 signs), while u_ip_address field is still no longer than 40. I had checked logs and discovered that there is an error

Unable to change column length: ip_address: com.glide.db.GlideSQLException: FAILED TRYING TO EXECUTE ON CONNECTION 16: CREATE TRIGGER zdelcmdb_ci AFTER DELETE ON cmdb_ci FOR EACH ROW DELETE IGNORE FROM tmp_c576071758i WHERE tmp_c576071758i.sys_id = OLD.sys_id

Syntax Error or Access Rule Violation detected by database (This version of MySQL doesn't yet support 'multiple triggers with the same action time and event for one table')

for ip_address and ip_address2 (but u_ip_address2 length is checked fine).

This update set works ok fine on our other 2 instances.

How can I solve this?

Thanks.

[timofeevbog]

There are 310872 items in cmdb_ci -table. No 'transaction cancelled' logs can be found.

jan_m wrote:

Hi,

Can you trace the update set in the logs and see if you got any other error/warning messages? 

Field length changes can last for a while and one issue you might run into are transaction quotas rules and timeouts. I have seen this happen on very large tables.

Are there any "transaction cancelled" text strings in your logs at the time of the update?

How many rows of data do you have in the cmdb_ci -table.

- Jan

[JC Moller]

Hi,

If you trace all actions related to this transaction in the node log file browser or directly from the localhost log, can you find anything relevant?

How long was the duration from start to the error message. Anything else worth mentioning in the logs?

- Jan

You should be able to find data similar to this image in the node logs (log browser).

[timofeevbog]

I've found this message (some amount of similar messages with another codes too):

Cancelling transaction #4806334 /xmlhttp.do (cancelled by other transaction): Thread Default-thread-6 (003227, B3181E934FF79E00A5C62558D310C7B5), after 577ms

[JC Moller]

Hi,

Have you managed to proceed with this issue, ie did you contact the Customer support?

Post some comments back here, if the case is resolved. Thanks.

Best regards,

Jan Möller