DFC sysobject.save() issues.

Hi Everybody,

So let me start out with saying we have a very old repository running 5.3 ( sp4, linux, oracle backend database...) and we ARE in the process of upgrading, it just is a long process..

So we have some DFC code written in Java that saves documents to our repository for other applications that don't know or care about what DFC is or stands for. Recently in our QA environemtn we have a table_space issue, where the database was all fulled up. So the app would create the object, call the save() function, get the object id, and return it to the calling application. The custom TBO we have to file the document, and maybe launch a workflow then tries to process it and gets this exception:

DfException:: THREAD: PooledThread-0; MSG: [DM_OBJ_MGR_E_SAVE_FAIL]error: "save failed for object with handle 090fb770805acec3 of type XXXX: table on which save failed was DM_SYSOBJECT_S; error from database system was ORA-12096: error in materialized view log on "DOCMADMIN"."DM_SYSOBJECT_S"

ORA-01653: unable to extend table DOCMADMIN.MLOG$_DM_SYSOBJECT_S by 8192 in tablespace DCTM"

So my question is, why doesn't the initial DFC code throw an exception on save and handle it there, instead of kinda saving it and waiting for the TBO to find out something is wrong...

Thanks all!

Find more posts tagged with

Comments

Hartmut_Clausen

That is hard to say without knowing your code. I suspect that you have some kind of try/catch block in your code that only logs the problem but does nothing beside it.

DavidHaveman

That's actually what it turned out to be. Our TBO engineer told me that there is a block of code in the TBO doSave() method that was trying and trying again to handle exceptions like this but in error, it was only logging some of them and moving on. Thanks for your reply!