Archives of the TeradataForum

Message Posted: Sat, 05 Apr 2003 @ 18:39:54 GMT

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

Hi,

If you are out of physical diskspace then there will also be

MINICYLPACK

error messages in the event log indicating a potential for being out of diskspace.

5141 -- means we are able to keep up with demand

5142 -- Means we had to PAUSE the AWTMAINS requesting the diskspace while we searched causing the response time to increase. However we eventually found some diskspace and the query was able to continue.

5143 -- Means we searched the whole disk and were unable to locate a cylinder and aborted the transaction with an out of disk condition.

MINICYLPACK is a drain on system resources because it causes a lot of additional I/O's while it coalesces (garbage collects) the datablocks to free up a cylinders worth of contigous sectors. (a Free cylinder )

If you are completely out of cylinders MINICYLPACK will run completly through the disk reading every datablock.

If Minicylpack gets all the way through the disk without being able to FREE up cylinder you will get an OUT OF DISK message.

You should try to avoid minicylpacks by following the recommendations of the previous post by Huw Lewis and his combinations of

showspace, ShowFSP and packdisk.

packdisk runs the same code that minicylpack does but you can schedule when to run (and specify options to) it to as to not impact your production workload.

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