First I want to inform you that I am the Warehouse Administrator and not the BOEXI Administrator. There are some anomolies when running reports against Teradata through ODBC and I would like to have your insite. When running a report using a web browser and BOEXI as the server, it will open a logon window for the requested report and after entering the user data the report will be run and returned. I would like to know if the following is "normal", and if not how to correct it.
** If the same report is run multiple times by the same user, a logon is requested and a new session
created for each run.
** When downloading of the report is complete the session remains open.
** If the web browser is closed, or a BOEXI query timeout occurs, Teradata will be continue in a response
mode sending the data somewhere(?).
** If the browser session is "signed-off", the web browser closed, and the client PC turned off the Teradata
session remains open for 60 minutes, then shows a normal sign-off in the DBC.LogonOnOff table.
Someone is suggesting update the ODBC driver on the server, but I see nothing in the set-up options to control the 60 minute session timeout exhibited by CE. I have also seen references to a MAX IDLE Timeout in older versions of Enterprise, but don't know how to adjust the parameter if it exists.
We are concerned that these issues could cause resource limits when using concurrent licensing.
Thanks for your help
>Bill H
>
>Bill Hassinger, DWA
** If the same report is run multiple times by the same user, a logon is requested and a new session
created for each run.
** When downloading of the report is complete the session remains open.
** If the web browser is closed, or a BOEXI query timeout occurs, Teradata will be continue in a response
mode sending the data somewhere(?).
** If the browser session is "signed-off", the web browser closed, and the client PC turned off the Teradata
session remains open for 60 minutes, then shows a normal sign-off in the DBC.LogonOnOff table.
Someone is suggesting update the ODBC driver on the server, but I see nothing in the set-up options to control the 60 minute session timeout exhibited by CE. I have also seen references to a MAX IDLE Timeout in older versions of Enterprise, but don't know how to adjust the parameter if it exists.
We are concerned that these issues could cause resource limits when using concurrent licensing.
Thanks for your help
>Bill H
>
>Bill Hassinger, DWA