Row size too large

[manojjain4328]

Hello Friends,

I got one starange issue in my end when i am creating new form so system generates one error

"Syntax Error or Access Rule Violation detected by database (Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs)"

please help me to find out the solution of this error.

Thanks,
Manoj

[shris]

Hi.

I am getting a similar error in our LDAP import. It seems as though the Active directory record suddenly grew too large, and the values can no longer be inserted into the import table (ldap_import) for the users whose accounts have grown. Other users import fine.

Not sure if your issue was related to importing, but this seems to be what our issue is.

shris

[dbrown1]

Currently looking into a solution myself; I'll post here if/when I find one, but did either of you find a solution?

[shris]

Hi.

We got our error on the LDAP import. We were importing ALL fields from LDAP that it would send us. For most users this was fine, but we started getting a few users whose AD accounts had 'too much stuff' in them.

Our solution was to set attributes on the LDAP import so it would ONLY import the fields we need. That has resolved the issue for the users whose accounts were too big.

There is a description of how to do attributes on ldap imports in the wiki in the troubleshooting section, I think. We backed it down to 10-15 fields and all is well. Coincidentally, it now takes much less time to get our data from the LDAP server--wish it had also trimmed the transform time, but of course it doesn't change that.

shris

[Michael Kaufman]

In case anyone reads this topic and receives this error. Here is more information on this topic.

If you decided to use the "com.glide.loader.verify_target_field_size" property and received this error, here is a way to fix it:

1. Set System Property "com.glide.loader.verify_target_field_size" to false

2. Set the LDAP attributes if needed to limit fields that are imported.

3. Delete the columns in the ldap_import table that are too large.   Might be 2 or 3 large fields.

4. Reimport the ldap users.   The columns will be recreated in smaller sizes.

Import User Photo from LDAP — ServiceNow ELITE.com