Friday, February 11, 2005

WLI DB Cleanup

If you want to clean out your WLI database you can use the following script to clean it out.

NOTE: after you run this, start your server... it will hang and thats OK. Cancel the server start and start the server again it should be fine.

DELETE FROM weblogicjmsstate;
DELETE FROM weblogicjmsstore;
DELETE FROM wli_b2b_decoder;
DELETE FROM wli_b2b_encoder;
DELETE FROM wli_b2b_java_class;
DELETE FROM wli_b2b_logic_plugin;
DELETE FROM wli_b2b_unique_key;
DELETE FROM wli_message_broker_dynamic;
DELETE FROM wli_process_def;
DELETE FROM wli_process_document;
DELETE FROM wli_process_doc_reference;
DELETE FROM wli_process_event;
DELETE FROM wli_process_instance_info;
DELETE FROM wli_process_tracking;
DELETE FROM wli_scheduler_info;
DELETE FROM wli_tpm_ebxml_binding;
DELETE FROM wli_tpm_rosettanet_binding;
DELETE FROM wli_tpm_trading_partner;
DELETE FROM wli_tpm_trading_partner_mgmt;
DELETE FROM wli_tpm_transport;
DELETE FROM wli_b2b_business_protocol_defn;
DELETE FROM wli_b2b_configuration;

After you run these you need to find the tables that start with JP and JC... run this Oracle sql to get that list:
select 'DROP TABLE ' || table_name || ';'
from tabs
where table_name like 'JPD%' or table_name like 'JCX%';

The result will be a series of drop statements that you can run.

NOTE: Stateless JPD tables will need to be created in all databases that are not referenced by Workshop (i.e. QA, Prod).

CREATE TABLE JPD_PROCESSES_MYWORKFLOW
(cg_id VARCHAR2(768) NOT NULL,
last_access_time NUMBER(19,0),
cg_data BLOB);

0 Comments:

Post a Comment

<< Home