close

Filter

loading table of contents...

Content Server Manual / Version 2401

Table Of Contents

4.3.8.2 Changing the Size of a StringProperty

Sometimes it might be necessary to change the size of a string property. For example, when the size exceeds a database limit.

Prerequisites

Be sure that you have a backup of your data. When you want to reduce the length, make sure that all existing content fits into the new size.

Caution

Caution

When the StringProperty is observed, the length must not exceed 256. Otherwise, the content server cannot start and you will see a log entry like the following in the content server log:

 2018-12-10 15:01:38 [ERROR] hox.corem.server.Server [] - \
Cannot startup due to malformed document type definition: \
The length 257 of the observed StringProperty 'observed' exceeds the allowed maximum length 256 (Init Process) 

Proceed as follows:

  1. Be sure to have a backup of your data.

  2. Stop the Content Server.

  3. Change the Length attribute to the new length.

  4. Make sure that property sql.schema.alterTable is set to true.

  5. Start the Content Server again.

You should see log entries like the following in the content server log.

 2018-08-22 13:33:11 [INFO] hox.corem.server.sql.SQLStore [] - \
SchemaValidator: validating document types (Init Process)
2018-08-22 13:33:11 [INFO] hox.corem.server.sql.SQLStore [] - DocumentTypeRegistry: altering table: \
ALTER TABLE CMAction MODIFY "teaserTitle" VARCHAR(300) (Init Process)
2018-08-22 13:33:11 [INFO] hox.corem.server.sql.SQLStore [] - DocumentTypeRegistry: altering table: \
ALTER TABLE ESDynamicList MODIFY "teaserTitle" VARCHAR(300) (Init Process) 

Example 4.8.  Log entries when string property has been changed


Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.