Archives of the TeradataForum

Message Posted: Tue, 26 Oct 2004 @ 09:15:14 GMT

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

Anomy,

Always remember with Teradata that the space you allocate is divided amongst all amps. If you give a database 100 GB on a 100 amp system, then each amp receives 1 GB. Being out of space on one amp is still treated as out of space for the database, even though it appears as though there's lots of free space left. This will occur when the data in a given table is badly skewed, i.e. all PI values hash to the same amp. Have a look at all the rows for database DBC in dbc.diskspace. If you have access logging turned on, the accesslog table can cause issues when the same session performs a large number of activities.

Hope this helps.

JL

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