Erasing Logging Policy Data

If you do not need to retain the logging policy data, drop the table, LOGGINGPOLICYPROPERTY from the database, and recreate it using the ActiveMatrix Policy Director DDL scripts. Use the DDL_Script_Generator utility located under TIBCO_HOME/administrator/3.3/samples/ddl to erase old and create new tables.

1. Configure the drivers for the database using TIBCO Configuration Tool.
2. Navigate to TIBCO_HOME/administrator/3.2/samples/ddl. For more information on DDL Script Generator, refer to the section, DDL Script Generator.
3. Modify generate_ddl.xml as follows:

   <DDLGeneratorTask
   action="action"
   targetDirectory="path_to_the_samples_directory"
   targetFilePrefix="targetFilePrefix"
   modelProfiles="modelProfiles"
   dbType="dbtype"
   dialect="dialect"
   username="username"
   password="password"
   dbUrl="dbUrl"/

   where

   • action is the action to be performed by the script. The values can be either create to create tables and related database objects or drop to delete tables.
   • path_to_the_samples_directory points to the location where the generated scripts are located. The default location is TIBCO_HOME/administrator/3.2/samples/ddl.
   • targetFilePrefix is used to create or drop tables; the values taken by targetFilePrefix can be create or drop based on the action that needs to be performed.
   • dbType is the type of the database for which scripts are generated. Valid values are sqlserver2005, sqlserver2008, oracle10g, oracle11g, and db2.
     Note: If you are using HSQLDB, restart the nodes and the new tables will be created automatically.
   • dialect is the dialect of the database.
   • dbURL is the URL used to connect to the database.
   • modelProfiles should always be set to commonlogging so as to point to the logging policy database.
4. Execute the command, ant -f generate_ddl.xml to generate the scripts to be executed on the database.