To change this default behavior: 1. Allocate a new TS_ID for the new Setting record to be added by updating the TS_ LASTIDS table. UPDATE TS_LASTIDS SET TS_LASTID = TS_LASTID + 1 WHERE TS_TABLEID = 56;
TS_DATATYPE = 1 TS_LONGVALUE = the desired limit for POST data (in bytes) Increment the last ID for the TS_SYSTEMSETTINGS row in the TS_ LASTIDS table by 1.
If you detect a spike in memory usage by Application Engine, perform the following steps: 1. Allocate a new TS_ID for the new setting record by updating the TS_ LASTIDS table. UPDATE TS_LASTIDS SET TS_LASTID = TS_LASTID + 1 WHERE TS_TABLEID = 56;
Korean KS_C_5601-1987 2. TS_SYSTEMSETTINGS table, set "Pre-Unicode Charset' value to correct character set, for example, GB2312. If there is no such entry in the TS_SYSTEMSETTINGS table, add this entry and set value to correct character set, also you need to modify TS_ LASTIDS table to reflect the changed lastID number for TS_SYSTEMSETTINGS table as well.
To workaround run the following sql queries against the Application Engine database. Update TS_ LASTIDS set TS_ LASTID =2 where TS_TABLEID = 230 Insert TS_MAILSUBMITREGISTRY values (1, null, 0);
To disable this warning: 1. Allocate a new TS_ID for the new Setting record by updating the TS_ LASTIDS table. UPDATE TS_LASTIDS SET TS_LASTID = TS_LASTID + 1 WHERE TS_TABLEID = 182;
When attempting to calculate " lastid " values for AE tables, the SQL used could sometimes cause deadlocks and slowing down of the AE interface. Upgrading to 10.1.5 clears up the issue by modifying the queries used when updating tables.
