Teradata Parallel Data Pump
Teradata Parallel Data Pump Reference - Teradata Developer ...
Teradata Parallel Data Pump Reference - Teradata Developer ...
- No tags were found...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Chapter 3: <strong>Teradata</strong> T<strong>Pump</strong> Commands<br />
PARTITION<br />
Syntax Element<br />
statements<br />
threshold<br />
Description<br />
Number of statements, as a positive integer of up to 2430, to pack into a<br />
multiple-statement request<br />
Default value is 20 statements per request.<br />
Note: Under certain conditions, <strong>Teradata</strong> T<strong>Pump</strong> may determine that the<br />
pack factor has been set too high. <strong>Teradata</strong> T<strong>Pump</strong> then automatically<br />
lowers the pack setting to an appropriate value and issues warning message<br />
UTY6625, for example:<br />
“UTY6625 WARNING: Packing has been changed to 12 statements per<br />
request”, and continues.<br />
Packing improves network/channel efficiency by reducing the number of<br />
sends/receives between the application and the database.<br />
The packing factor is validated by sending a fully packed request to<br />
<strong>Teradata</strong> <strong>Data</strong>base using a prepare. This test checks for syntax problems<br />
and requests that are excessively large and overwhelm the parser.<br />
To simplify the script development process, <strong>Teradata</strong> T<strong>Pump</strong> ignores<br />
certain errors returned by an overloaded parser, shrinks the request, retries<br />
the prepare until it executes successfully and finally, issues a warning noting<br />
the revised packing factor size.<br />
When this happens, the <strong>Teradata</strong> T<strong>Pump</strong> script should be modified to<br />
eliminate the warning, which avoids the time-consuming process of<br />
shrinking the request.<br />
Note: A packing failure may occur if the source parcel length does not<br />
match the data defined. If this happens, <strong>Teradata</strong> T<strong>Pump</strong> issues the<br />
message:<br />
“UTY2819 WARNING: Packing may fail because input data does not<br />
match with the data defined.”<br />
To resolve this problem, increase the packing factor and resubmit the job.<br />
Minimum number of sessions to be logged on for the partition<br />
When logging on sessions, if system limits are reached above the threshold<br />
value, <strong>Teradata</strong> T<strong>Pump</strong> stops trying to log on, and uses whatever sessions<br />
are already logged on.<br />
If the sessions run out before the threshold is reached, <strong>Teradata</strong> T<strong>Pump</strong><br />
logs off all sessions, waits for the time determined by the SLEEP value<br />
(specified in the BEGIN LOAD command), and tries to log on again.<br />
Example<br />
A sample script that uses partitioning follows:<br />
.LOGTABLE TPLOG01;<br />
.LOGON cs4400s3/cfl,cfl;<br />
DROP TABLE TPTBL01;<br />
DROP TABLE TPTBL02;<br />
DROP TABLE TPERR01;<br />
CREATE TABLE TPTBL01, FALLBACK(<br />
C1 CHAR(12) not null,<br />
<strong>Teradata</strong> <strong>Parallel</strong> <strong>Data</strong> <strong>Pump</strong> Reference 177