Hi Experts
We are working with a client that has, due to high daily msg flow, a BC_MSG_LOG table around 30 TB. Due to size restrictions a reorg is not possible.
One solution would be to drop the table, but as I understand XMLDAS is running a pretty sophisticated syncing of these control tables when doing its deletion process
- BC_MSG_DUP_CHECK
- BC_MSG_SEQ_STAT
- BC_MSG_SEQ_NBR
- BC_MSG_BLIST
- XI_AF_SVC_ID_MAP
We are trying to understand if e.g. msg sequencing will be broken -
What would be an alternative solution for reducing the BC_MSG_LOG table size besides reorg and dropping?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.