If you are using any other RDBMS, empty the data store
tables by using the administration tools of your RDBMS. You
can either remove all data from the tables, or drop and recreate the
tables. Most RDBMS support the TRUNCATE TABLE statement
that removes all data from the tables. This is the preferred way of
emptying the data store tables because it leaves the tables and their
authorizations intact.
If you RDBMS does not support the TRUNCATE
TABLE statement (for example, DB2® does
not), you can use the DELETE statement to delete
all of the rows from all of the tables. However, if the tables contain
a lot of data, this might not be practical because of resource limitations
in the RDBMS. In this case, drop the tables and recreate them with
the required indices and authorities.
Tip: If you have
enabled WebSphere Application Server to
create the data store tables, you can drop the tables by using the DROP
TABLE statement. When the messaging engine is next started,
it creates empty tables to replace them. If you have not enabled WebSphere Application Server (base) to create
the data store tables, you must recreate the tables that you drop
before you start the messaging engine.
Tip: You
can use the -drop option of the sibDDLGenerator command
to generate DDL to drop the tables.
Optional: If you have deleted the messaging engine by removing
it from the bus, you can now recreate it.