Archives of the TeradataForum

Message Posted: Tue, 04 Jun 2013 @ 12:42:59 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

The user that you are running the procedures is possible the same user that is running a batch process or some other overnight process.

As far as I know the spool limit for a user X is the maximum for all sessions not each individual session. Check that there are no other sessions with the same user ID.

Another possibility is that spool is taken from the free space. If there is lots of other activity and not much free space then you can also run out of spool if freespace is low. Just because you have a maxspool of X doesn't mean you will get X is the freespace on the system is less than X.

Another possibility is that the queries being run in the procedure are skewed slightly. Combined with the other symptoms and overnight processes, it is possible that you are hitting a limit.

Does your procedure include some sort of time based criteria that captures more data if you run it at night (e.g. where transaction_date = current_date?) Maybe it is capturing more data because it is running at a later time. More data = more spool requirements.

Perhaps you could post your procedures.

	<Prev	Next>		<<First	<Prev	Next>	Last>>