The propvalue column size of various table is 2000, but the actual values may be larger than that. It appears like this may lead to problems with Oracle databases. A particular issue is the "serialized" property of scheduler objects which can be much larger than 2000. This could be addressed individually for specific properties, like changing the schedulerobjects table so that "serialized" is not searchable (for which there seems no good reason), but other tables and properties may be affected as well, like managedobjects or specifically the /jsonconfig/configurationProperties/privateKey property. Another option might be to specifically truncate propvalue before inserting in in the properties tables.