We have an existing Cognos 8 environment (running on Windows 32bit) connecting to Teradata via ODBC driver using a Teradata account with 2GB/amp in spool setting, and the report is working fine.
When they export the content from Cognos 8 to to Cognos 10 new environmetn (running on Windows 64bit) connecting to Teradata via ODBC driver using the same Teradata account with 2GB/amp in spool setting, and the report fails for not enough SPOOL.
We have tried increasing the SPOOL to 4GB/amp and it runs longer but fails. We have also upgraded the ODBC driver on Cognos 10 to be 64bit drivers, and we are still failing.
Trying to understand why the Cognos 8 content when migrated to Cognos 10 would cause a change to the query being submitted which is consuming more spool?
Here is a link to pretty good document published by IBM which might help you.