Hello,
I've hit an odbc error using the Scheduler_Test app against an experimental
instance on Teradata.
When I turn on the scheduler monitoring I sometimes get:
Error: ('HY000', '[HY000] [Teradata][ODBC Teradata Driver] Beyond
SQL_ACTIVE_STATEMENTS limit')
I've improved things a bit by setting a pool_size and increasing the scheduler
poll interval but it still occurs. I think the time to complete a login on
Teradata (on my system anyway) may contribute - perhaps the next poll cycle
comes up while the last one is still running.
I've found that it has to do with the hstmt limit being reached in the odbc
driver. Not really sure what that means.
*This isn't necessarily a web2py, scheduler, or pyodbc error, but maybe one of
controlling the odbc activity to within limits. Has anyone seen this before
and been able to manage it ?It may be a limitation in the Teradata odbc driver
that may limit its effectiveness for high concurrency web apps.*
*Thanks*
*Andrew W*
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
