1. Using Siebel Tools
  2. Publishing Table in Source-to-Target Migration

Publishing Table in Source-to-Target Migration

In the source environment, a table needs to be published either by using the Apply/DDL button or by running the siebdev.exe utility command.

In the target environment, publishing a table is generated by the Incremental/Full source-to-target Runtime Repository migration. Hence, a table cannot be published explicitly in the target environment.

To publish a table using the Apply/DDL button (Siebel Tools)

  1. Update the required table schema changes as needed.

  2. Search for the table that you want to publish.

    The following image displays the S_AMGR_PRFL table and its corresponding Columns. The Apply/DDL button is available on the applet banner.


    This image is described in the surrounding text.

  3. Click the Apply/DDL button.

    The Choose Option dialog opens where you specify either to apply the schema changes to the database or create the DDL file.

  4. Select either Apply or Generate DDL, and then click OK.

    • If you select Apply, then the Apply Schema window opens where you can specify the table, database, and DDL details. When you click OK, the schema is applied to the tables and the tables are republished with the next version number. The table compiled-object definitions are present in the S_RR_TABLE table in the next table version, and the list of effected tables is present in the S_RR_OBJ_ITEM table.

    • If you select Generate DDL and then click OK, the table will not be published; however, it will generate the DDL in the specified location.

To publish a table using the siebdev.exe utility

  1. Open a Command Prompt window on your machine by clicking the Start button and selecting the Run option.

  2. In the Run window, enter the CMD value in the Open field.

  3. At the Command Prompt, run the following siebdev.exe utility command:

    siebdev /c tools.cfg /l <LANG> /d <ServerDataSrc> /u <username> /p <password> /
IncrementalTablePublish <FileName>

    The contents of <FileName> can be <TableName>:<Operation> where the operation can be Insert, Update, or Delete. These are the examples of the ddl_TableSchema.txt:

    • S_RR_OBJ_VER:Update

    • S_RR_TEST1:Insert

    • S_RR_TEST2:Delete

Note: The ddl_TableSchema.txt file is always auto-generated when the schema is applied using DDLIMP. This file is generated in the same location as the log file under the file name <log_File_Name>_TableSchema.txt. The name of the generated file cannot be changed.