This documentation supports the 9.0 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

Table updates when changing character field lengths

The following sections describe how each database changes the length of a character field.

Note

The operation of changing character field lengths logs the entire table that is modified. If this table is large, it consumes a large amount of log space. You might need to expand your system's log space.

Table updates for Microsoft SQL Server when changing character fields

In Microsoft SQL Server databases, if the field is created in BMC Remedy AR System 5.1 and later, the length of a character field is changed in one of these ways:

  • If the original size is <= 8000 bytes and you decrease the length, no change is made to the table.
  • If the original size is > 8000 bytes and the new length is > 8000 bytes, no change is made to the table.
  • For any other change in length, a column is created with the new length restriction. All data from the original column is copied to the new column, and the original column is deleted from the main table.

If the field is created in a version of BMC Remedy AR System earlier than 5.1, the length of a character field is changed in one of these ways:

  • If the original size is <= 255 bytes and the new length is <=8000 bytes, no change is made to the table.
  • If the original size is > 255 bytes and the new length is > 8000 bytes, no change is made to the table.
  • For any other change in length, a column is created with the new length restriction. All data from the original column is copied to the new column, and the original column is deleted from the main data table.

Note

In Microsoft SQL Server 2005, when the underlying database table is marked for database replication, you cannot change the field length. If you try to do so, the ALTER TABLE command returns this error: Cannot rename the table because it is published for replication. (SQL Server 15051). To resolve this, turn off database replication, change the field size, and then turn database replication on. For more information, see the Microsoft SQL Server documentation.

Table updates for Oracle when changing character fields

The following table shows the changes that BMC Remedy AR System makes to Oracle databases when you change the length of character fields. The way that field length changes are handled depends on the initial size of the field and whether the field was created in the current version or a previous version of BMC Remedy AR System.



Changing character field lengths for Oracle

Administrator Action

BMC Remedy AR System Action

Decreases the length of a field from > 4000 bytes to <= 4000 bytes.

Adds a varchar column to the main data table; copies the data from the clob column to the new column; deletes the old column.

Decreases the length of a field from <= 4000 bytes to less than 4000 bytes.

Performs no restructuring.

Increases the length of a field from <= 4000 bytes to > 4000 bytes.

Adds a clob column to the main data table; copies the data from the varchar column to the new column; deletes the old column.

Increases the length of a field from > 4000 bytes to another value also > 4000 bytes.

Performs no restructuring.

 

Server actions when changing full text indexed fields

If the length of a full text indexed field is changed, the full text index might be restructured. The following table describes the server actions that can occur.



Server actions when full text indexed fields are changed

If the administrator does this

BMC Remedy AR System server does this

Shortens a field that is <= 32K.

Performs no restructuring.

Lengthens a field that is <= 32K. The new length is <= 32K

Alters the index to increase the index size and preserve the existing data.

Lengthens a field that is <= 32K. The new length is > 32K.

Reindexes the field to generate a new index. a

Shortens a field that is > 32K. The new length is <= 32K.

Reindexes the field to generate a new index. a

Lengthens a field that is > 32K.

Performs no restructuring.

 

a The following warning appears after the length change is saved: A rebuilding of the corresponding full text index has been initiated due to the field length change (ARWARN 681)

Was this page helpful? Yes No Submitting... Thank you

Comments