Configuring the Database for SSSE

SSSE relies on the presence of certain database triggers in your Enterprise database. You can use an Oracle-provided script to create these triggers. A script is also included for removing database triggers. The following information lists the script names for various database environments. These scripts are located in the siebsrvr/BIN directory on your Siebel Server.

This task is an optional step in Roadmap for Configuring SSSE.

Database Type	Script to Add Database Triggers	Script to Remove Database Triggers
DB2	ssse_triggers_db2.sql	ssse_drop_triggers_db2.sql
DB2 390	ssse_triggers_db2_390.sql	ssse_drop_triggers_db2_390.sql
MS SQL Server	ssse_triggers_mssql.sql	ssse_drop_triggers_mssql.sql
Oracle	ssse_triggers_ora9.sql	ssse_drop_triggers_ora9.sql

If your SSSE implementation includes a significant number of customizations, then you might have to add custom database triggers. For more information about custom triggers, see Process of Customizing SSSE.

Note: SSSE also includes triggers for position change, synchronization level change, and visibility change. For help with changing these triggers, contact your Oracle sales representative for Oracle Advanced Customer Services to request assistance from Oracle's Application Expert Services.

The following procedure briefly describes how to use the scripts that create standard database triggers for SSSE.

To create standard database triggers for SSSE

1. Determine the names of the following items:

   • The Table Owner for tables in your Siebel database

   • The script to remove SSSE database triggers from your Siebel database

   • The script to add SSSE database triggers to your Siebel database

2. In case old triggers are present, run the script to remove SSSE database triggers from your Siebel database.

3. Run the script to add SSSE database triggers to your Siebel database.

Provide the Table Owner name when you are prompted to do so.