Can I Truncate CUBE_INSTANCE and Other Tables in the ORABPEL Schema?
(Doc ID 1220711.1)
Last updated on MAY 15, 2023
Applies to:
Oracle(R) BPEL Process Manager 10g - Version 10.1.3.1 and laterInformation in this document applies to any platform.
Goal
When purging old BPEL instances using the purge scripts provided with the product you may have encountered issues in the database with a lot of cluster waits in the system. Due to the waits the user may have to abort the purging. As a result some of the tables have data that has not been deleted. So question is can you truncate all the following tables in orabpel schema?
native_correlation
cube_scope
work_item
wi_exception
scope_activation
dlv_subscription
audit_trail
audit_details
sync_trail
sync_store
xml_document
document_dlv_msg_ref
document_ci_ref
attachment
attachment_ref
ci_indexes
wi_fault
cube_instance
dlv_message
invoke_message
And if so what would be the impact of truncating?
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |