We use Oracle for our data warehouse and our BizO repositories. I have deleted documents via the Supervisor module. The rows associated with the documents in the OBJ_M_DOCUMENTS table are gone. When I run a Repair from Supervisor, it says that it successfully deleted these documents from the OBJ_X_DOCUMENTS table but it doesn’t really. The Oracle rollback segments get full and the documents don’t really get deleted from OBJ_X_DOCUMENTS.
Under these circumstances, can I safely delete the rows from OBJ_X_DOCUMENTS with SQLPlus? Are all ties severed with other tables at this point? Will it clobber the BizO repository? Or should I delete all but the first row of each document then re-run the Repair function in Supervisor?
The problem is, the SQL used by BizO tries to delete several documents simultaneously and completely without using intermediate commits. We don’t have unlimited room to keep increasing the rollback segments. Initially we had 128 MB of rollback and we increased it to 330 MB of rollback. That still isn’t enough to delete four documents of 90 MB each, simultaneously. Why can’t we delete one document at a time? Why doesn’t the Delete Document function use commits? Are there patches that can do this? I can’t believe I’m the only one having this problem.
Business Objects keeps telling me to increase my rollback segments. There’s got to be a better way. Any insight is appreciated.
If your using Doc Agent to run these there will be an entry in the DS_PENDING_JOB table for the documents that is the reason why there still in OBJ_X_DOCUMENTS table.
You can use SQLPlus to delete the documents from both these table.
If there’s no entry in DS_PENDING_JOB then you can delete unwanted rows from OBJ_X_DOCUMENTS using SQLPlus
Min
We use Oracle for our data warehouse and our BizO repositories. I have
deleted documents via the Supervisor module. The rows associated with the
documents in the OBJ_M_DOCUMENTS table are gone. When I run a Repair from
Supervisor, it says that it successfully deleted these documents from the
OBJ_X_DOCUMENTS table but it doesn’t really. The Oracle rollback segments
get full and the documents don’t really get deleted from OBJ_X_DOCUMENTS.
Under these circumstances, can I safely delete the rows from OBJ_X_DOCUMENTS with SQLPlus? Are all ties severed with other tables at
this point? Will it clobber the BizO repository? Or should I delete all but
the first row of each document then re-run the Repair function in Supervisor?
The problem is, the SQL used by BizO tries to delete several documents
simultaneously and completely without using intermediate commits. We don’t
have unlimited room to keep increasing the rollback segments. Initially we
had 128 MB of rollback and we increased it to 330 MB of rollback. That
still isn’t enough to delete four documents of 90 MB each, simultaneously.
Why can’t we delete one document at a time? Why doesn’t the Delete Document
function use commits? Are there patches that can do this? I can’t believe
I’m the only one having this problem.
Business Objects keeps telling me to increase my rollback segments. There’s
got to be a better way. Any insight is appreciated.