1. Configuring Siebel Business Applications
  2. Guidelines for Creating a LONG Column

Guidelines for Creating a LONG Column

If you create a LONG column, then use the following guidelines:

  • Only one LONG column can exist for each table.

  • You can add a LONG column only to a one-to-one extension table whose Base Table property includes a valid base table.

  • You cannot add a LONG column to a one-to-many extension table because it is a Data (Public) table.

  • You cannot add a LONG column to a Data (Public) table, such as the S_EVT_ACT table. Only Oracle can create a LONG column in a Data (Public) table.

  • You can use a LONG column to store a maximum of 16 KB or 16383 characters.

  • Querying a LONG column starts more input and output operations in your RDBMS that are not necessary with other types of column data. This extra input and output increases the time Siebel CRM requires to get each row of data from the database. This increase can add up to a noticeable reduction in performance if Siebel CRM gets many rows of data from the database.

  • For DB2 on z/OS, use a 32K tablespace if 16K is too small. If 32K is too small, then convert the LONG type to a CLOB type. For more information, see Implementing Siebel Business Applications on DB2 for z/OS.