TIBCO BusinessEvents (BE) 3.0.1, what is the rationalebehind using the lob datatype for workItems table?
Article ID: KB0088332
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessEvents Enterprise Edition | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
TIBCO BusinessEvents (BE) 3.0.1, what is the rationale behind using the lob datatype for workItems table?
Environment:
==========
o TIBCO BusinessEvents 3.0.1
o Oracle 10g
Symptoms:
=========
Resolution:
==========
The BLOB field in WorkItems stores Work entry (serialized form of Event with additional attributes) and heterogeneous tasks (work objects) like SMTimeout or TimerEvent, etc. The main reason of making that field a BLOB is to support these different types of objects.
Description:
============
TIBCO BusinessEvents (BE) 3.0.1, what is the rationale behind using the lob datatype for workItems table?
Environment:
==========
o TIBCO BusinessEvents 3.0.1
o Oracle 10g
Symptoms:
=========
Resolution:
==========
The BLOB field in WorkItems stores Work entry (serialized form of Event with additional attributes) and heterogeneous tasks (work objects) like SMTimeout or TimerEvent, etc. The main reason of making that field a BLOB is to support these different types of objects.
Issue/Introduction
TIBCO BusinessEvents (BE) 3.0.1, what is the rationalebehind using the lob datatype for workItems table?
Feedback
Yes
No
Powered by
