Bpel Orabpel-04004

[jbarranza]

Hi all,
i got an error from BPELConsole after its repository had performed the offline backup.
No processes were running during the database backup and no log messages appear in domain log until a new process (when database is up) starts.
It is invoked a new bpel process and it doesn't start, every involved db is up, the domain log shows the following error :

<2007-11-14 09:51:14,059> <ERROR> <QA.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "cube engine": Cannot insert audit trail.
The process domain was unable to insert the current log entries for the instance "21008" to the audit trail table. The exception reported is: OALL8 is in an inconsistent state.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usize, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )

ORABPEL-04004

Cannot insert audit trail.
The process domain was unable to insert the current log entries for the instance "21008" to the audit trail table. The exception reported is: OALL8 is in an inconsistent state.
Please check that the machine hosting the datasource is physically connected to the network. Otherwise, check that the datasource connection parameters (user/password) is currently valid.
sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usize, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )

at com.collaxa.cube.engine.adaptors.oracle.AuditTrail PersistenceAdaptor$TrailHandler.store(AuditTrailPe rsistenceAdaptor.java:291)
at com.collaxa.cube.engine.adaptors.common.BaseAuditT railPersistenceAdaptor.store(BaseAuditTrailPersist enceAdaptor.java:134)
at com.collaxa.cube.engine.adaptors.oracle.AuditTrail PersistenceAdaptor.store(AuditTrailPersistenceAdap tor.java:63)
at com.collaxa.cube.engine.data.AuditTrailPersistence Mgr.store(AuditTrailPersistenceMgr.java:239)
at com.collaxa.cube.engine.adaptors.common.BaseCubeIn stancePersistenceAdaptor.store(BaseCubeInstancePer sistenceAdaptor.java:466)
at com.collaxa.cube.engine.adaptors.oracle.CubeInstan cePersistenceAdaptor.store(CubeInstancePersistence Adaptor.java:80)
at com.collaxa.cube.engine.data.CubeInstancePersisten ceMgr.store(CubeInstancePersistenceMgr.java:391)
at com.collaxa.cube.engine.CubeEngine.store(CubeEngin e.java:5210)
at com.collaxa.cube.engine.CubeEngine.endRequest(Cube Engine.java:5446)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke (CubeEngine.java:1217)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.cr eateAndInvoke(CubeEngineBean.java:120)
at com.collaxa.cube.engine.ejb.impl.CubeEngineBean.sy ncCreateAndInvoke(CubeEngineBean.java:153)
at ICubeEngineLocalBean_StatelessSessionBeanWrapper0. syncCreateAndInvoke(ICubeEngineLocalBean_Stateless SessionBeanWrapper0.java:486)
at com.collaxa.cube.engine.delivery.DeliveryHandler.i nitialRequestAnyType(DeliveryHandler.java:520)
at com.collaxa.cube.engine.delivery.DeliveryHandler.i nitialRequest(DeliveryHandler.java:435)

I had to bounce the console and everything works fine.
But i would like to know if any workaround exist to avoid the bounce(always better).

Thanks in advance,
Matteo

[chrisplough]

Re: Bpel Orabpel-04004

Matteo,

To my knowledge, there isn't a way to handle this, other than restarting the BPEL instance. The cause of the error, is that taking the DB down kills the connection between BPEL and the dehydration store (database), and it isn't able to re-create that connection automatically. For existing EBS/OTM integration customers, they've had to restart their BPEL instance also.

--Chris