|
|
Archives of the TeradataForum
Message Posted: Mon, 19 Dec 2005 @ 17:51:00 GMT
Subj: | | Re: Mini Cylpack |
|
From: | | David Wellman |
Hi Bill,
I've embedded some direct answers to your questions below.
Cheers,
Dave
Ward Analytics Ltd: Information in motion ( www.ward-analytics.com )
| -----Original Message-----
From: Hassinger, Bill
Sent: Monday, December 19, 2005 10:38
Subject: Mini Cylpack | |
| We received a mini cylpack(mcp)message on two of our 4 nodes late last
week. I have the following general questions: | |
| Can I identify the database/user causing the mcp by looking at active sessions when the mcp initiated? | |
DW: That's your best place to start, but typically you need to look at the big spool users at the time the mcp happened/was happening.
| Can a Select statement initiate a mcp? | |
DW: Yes
| Can skewed spool initiate a mcp? | |
DW: Very definitely !
| Can moving space with a modify db imitate a mcp? | |
DW: Very unlikely (if not impossible).
| Can collect statistics initiate a mcp? | |
DW: possible, but I think you'd already be suffering from them anyway.
| What utility is best to review details on the mcp? ie involved AMP, length of time for mcp process, possibility of another mcp
occurring? | |
DW: dbc.software_event_log shows which AMP had the mcp event as does dbc.resusagesvpr (if you're logging in detail mode). The
dbc.software_event_log view shows some more details than SVPR, but it's a bit messy unless you're eyeballing it.
| |