Archives of the TeradataForum
Message Posted: Wed, 29 Mar 2006 @ 19:27:49 GMT
| Subj: | | Re: Try to see fonctionnement of mini-cylpack |
| |
| From: | | Anomy Anom |
<-- Anonymously Posted: Wednesday, March 29, 2006 14:28 -->
| | In the configuration mini-cylpack is fixed by default at 20, | |
| | How can we interpret the value of 20 ? | |
| | How can we see in the database in a table like software_event_log or hardware_event_log this information without ferret the automatic mini-
cylpack ? | |
Your DBSCONTORL (see utility reference manual) must have the FSP set at 20% or you have ferret set at FSP=20 which mean each block will only
fill to 80%.
Mini-cylpack is a automated process by TERADATA software like defrag in window operating system to re-allocate space to allow the task at hand
to complete. It usually signal the system think it had ran out of space and need to search and perform packdisk including defragmentation to make
room for the current task to complete. This is not necessary good since it could delay the current process to appear to run longer.
Packdisk is a manual process perform similar task as mini-cylpack and it is recommended when a system is running low in space and can be
scheduled prior to a operation that would move large amount of data in and out of the system.
Showspace will allow you to see how close are you to run out of space.
The teradata manager alert policy has an item to allow you to see mini-cylpack. You can use that number to search against dbc.sw_event_log for
the occurrence in the past. The best way is not to have mini-cylpack by running packdisk to may be lower FSP number. The FSP number need to be
higher only if your system handle mostly update type of operation.
Anyway, more details can be found in utility reference manual under dbscontrol section for the FSP value or ferret section for packdisk.
| 
