What are the different session modes used by Teradata adapter services (Publication service, Subscription service and Request Response service) in order to connect to the database?
Article ID: KB0092657
Updated On:
| Products | Versions |
|---|---|
| TIBCO Adapter for Teradata | - |
| Not Applicable | - |
Description
Resolution:
The TIBCO adapter for Teradata mainly uses two session modes to connect to the Teradata database:
- ANSI mode
- Teradata mode.
Teradata Adapter uses theses session modes for Teradata transaction, like executing SQL statements, stored procedures etc.It won't affect if the mode in which table is created is different from the mode in which Teradata adapter is running.
The following is the details of the respective session modes used by various adapter services
Publication service:
------------------------
It always use Teradata mode.
Subscription service:
--------------------------
1. If subscription service has child table, it use ANSI mode whether “Service Level Logon” is set or not.
2. If subscription service has no child table, it use Teradata mode whether “Service Level Logon” is set or not.
RPC service:
----------------
1. If “Use Custom Operation” option is NOT check, RPC service use ANSI mode.
2. If “Use Custom Operation” option is check, you can choose session mode in “AESchemas->ae->Teradata->CustomOps->TeradataConfiguration->TeradataServer->Operation (you create) ->Classes->INPUT_OPTIONS->PROCMODE”
Unless PROCMODE is configured to “ANSI” explicitly, the operation will execute as Teradata mode.
Also the stored procedures created in one session mode can not be executed in other session mode. For example stored procedure created in ANSI mode cannot be executed in Teradata mode; it will result in the following error
TeradataAdapterConfiguration.TeradataAdapterConfiguration Error [Database] AETD-000005 SQL Error - Invalid session mode for procedure execution
The TIBCO adapter for Teradata mainly uses two session modes to connect to the Teradata database:
- ANSI mode
- Teradata mode.
Teradata Adapter uses theses session modes for Teradata transaction, like executing SQL statements, stored procedures etc.It won't affect if the mode in which table is created is different from the mode in which Teradata adapter is running.
The following is the details of the respective session modes used by various adapter services
Publication service:
------------------------
It always use Teradata mode.
Subscription service:
--------------------------
1. If subscription service has child table, it use ANSI mode whether “Service Level Logon” is set or not.
2. If subscription service has no child table, it use Teradata mode whether “Service Level Logon” is set or not.
RPC service:
----------------
1. If “Use Custom Operation” option is NOT check, RPC service use ANSI mode.
2. If “Use Custom Operation” option is check, you can choose session mode in “AESchemas->ae->Teradata->CustomOps->TeradataConfiguration->TeradataServer->Operation (you create) ->Classes->INPUT_OPTIONS->PROCMODE”
Unless PROCMODE is configured to “ANSI” explicitly, the operation will execute as Teradata mode.
Also the stored procedures created in one session mode can not be executed in other session mode. For example stored procedure created in ANSI mode cannot be executed in Teradata mode; it will result in the following error
TeradataAdapterConfiguration.TeradataAdapterConfiguration Error [Database] AETD-000005 SQL Error - Invalid session mode for procedure execution
Issue/Introduction
What are the different session modes used by Teradata adapter services (Publication service, Subscription service and Request Response service) in order to connect to the database?
Feedback
Yes
No
Powered by
