Why exception table is needed when database reconnection is used?
Article ID: KB0089647
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks Plug-in for Database | - |
| Not Applicable | - |
Description
Resolution:
ProductVersionText: TIBCO Adapter For ActiveDatabase 5.2.1,TIBCO Adapter For ActiveDatabase 5.2.0
Platform: ALL
Answer: In order to detect the status of database connect, ADB need send a dummy query to the database. If subscriber service send such a query for each database error, it will degrade performance greatly. For this reason, detection of connection is set to the last resort: subscriber only checks connection status after the insert into exception table fails. So if no exception table is defined, subscriber will treat the disconnected error in the same way as it does to any database error: to terminate the agent.
ProductVersionText: TIBCO Adapter For ActiveDatabase 5.2.1,TIBCO Adapter For ActiveDatabase 5.2.0
Platform: ALL
Answer: In order to detect the status of database connect, ADB need send a dummy query to the database. If subscriber service send such a query for each database error, it will degrade performance greatly. For this reason, detection of connection is set to the last resort: subscriber only checks connection status after the insert into exception table fails. So if no exception table is defined, subscriber will treat the disconnected error in the same way as it does to any database error: to terminate the agent.
Issue/Introduction
Why exception table is needed when database reconnection is used?
Feedback
Yes
No
Powered by
