Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 3: Teradata TPump Commands BEGIN LOAD BEGIN LOAD Purpose The BEGIN LOAD command initiates or restarts a Teradata TPump task, specifying the number of sessions to use and any other parameters needed to execute the task. Syntax .BEGIN LOAD SESSIONS number threshold A A ERRORTABLE tname dbname. ERRLIMIT errcount errpercent APPEND NODROP QUEUETABLE CHECKPOINT frequency SERIALIZE OFF ON DATAENCRYPTION OFF ON ARRAYSUPPORT OFF ON TENACITY hours PACK statements PACKMAXIMUM LATENCY seconds NOTIMERPROCESS RATE statement_rate RETRYTIMES nn SLEEP minutes NOATOMICUPSERT NOMONITOR ROBUST ON OFF MACRODB dbname NOTIFY OFF LOW MEDIUM HIGH ULTRA EXITname TEXT ' string ' MSG ' string ' 3021G017 96 Teradata Parallel Data Pump Reference
Chapter 3: Teradata TPump Commands BEGIN LOAD where Syntax Element SESSIONS number threshold ERRORTABLE APPEND NODROP QUEUETABLE Description Keyword for the number of Teradata TPump sessions. Number of sessions to be logged on for update purposes for Teradata TPump. A Teradata TPump task logs on and uses the number of sessions specified. One additional session is used for performing various utility functions. There is no default value for number; it must be specified. Neither is there a maximum value, except for system-wide session limitations, which vary among machines. Limiting the number of sessions conserves resources on both the external system and Teradata Database. This conservation is at the expense of a potential decrease in throughput and increase in elapsed time. Minimum number of sessions to be logged on for update purposes for the utility. When logging on sessions, if the limits are reached above the threshold value, Teradata TPump stops trying to log on, and uses whatever sessions are already logged on. If the sessions run out before the threshold is reached, Teradata TPump logs off all sessions, waits for the time determined by the SLEEP value, and tries to log on again. Optional keyword for identifying a database and error table. Use a database name as a qualifying prefix to the error tables. Specifying a database that is not the production database avoids cluttering the production system with error tables. This means that because the database should have been allocated a lot of PERM space, that space will not have to be increased for all databases with tables involved in the Teradata TPump task. Caution: It is the user’s responsibility to ensure that the error table sharing was meaningful. Two jobs targeting different tables with different input record layouts cannot share the same error table. Specifies the existing error table. If the specified error table does not exist, Teradata TPump will create it. If the structure of the existing error table is not compatible with the error table Teradata TPump creates, the job will run into an error when Teradata TPump tries to insert or update the error table. Specifies to retain (not DROP) the error table, even it is empty at the end of a job. NODROP can be used with APPEND to persist the error table or alone. Selects the error table as a Queue Table. Teradata Parallel Data Pump Reference 97
Page 1 and 2:
Teradata Parallel Data Pump Referen
Page 3 and 4:
Preface Purpose This book provides
Page 5 and 6:
Preface Additional Information Date
Page 7 and 8:
Table of Contents Preface. . . . .
Page 9 and 10:
Table of Contents Teradata TPump St
Page 11 and 12:
Table of Contents Teradata TPump/No
Page 13 and 14:
List of Tables Table 1: Teradata TP
Page 15 and 16:
CHAPTER 1 Overview This chapter pro
Page 17 and 18:
Chapter 1: Overview Teradata TPump
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Chapter 1: Overview Operating Featu
Page 25 and 26:
Chapter 1: Overview Operating Featu
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Chapter 1: Overview The Teradata TP
Page 35 and 36:
Chapter 1: Overview The Teradata TP
Page 37 and 38:
CHAPTER 2 Using Teradata TPump This
Page 39 and 40:
Chapter 2: Using Teradata TPump Inv
Page 41 and 42:
Page 43 and 44:
Page 45 and 46: Chapter 2: Using Teradata TPump Inv
Page 51 and 52: Chapter 2: Using Teradata TPump Ter
Page 53 and 54: Chapter 2: Using Teradata TPump Res
Page 55 and 56: Chapter 2: Using Teradata TPump Res
Page 57 and 58: Chapter 2: Using Teradata TPump Pro
Page 69 and 70: Chapter 2: Using Teradata TPump Wri
Page 75 and 76: Chapter 2: Using Teradata TPump Vie
Page 81 and 82: Chapter 2: Using Teradata TPump Mon
Page 83 and 84: Chapter 2: Using Teradata TPump Mon
Page 85 and 86: Chapter 2: Using Teradata TPump Est
Page 87 and 88: Chapter 2: Using Teradata TPump Est
Page 89 and 90: CHAPTER 3 Teradata TPump Commands T
Page 91 and 92: Chapter 3: Teradata TPump Commands
Page 95: Chapter 3: Teradata TPump Commands
Page 147 and 148:
Chapter 3: Teradata TPump Commands
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
CHAPTER 4 Troubleshooting This chap
Page 197 and 198:
Chapter 4: Troubleshooting Error Me
Page 199 and 200:
Chapter 4: Troubleshooting Reading
Page 201 and 202:
Chapter 4: Troubleshooting Reading
Page 203 and 204:
CHAPTER 5 Using INMOD and Notify Ex
Page 205 and 206:
Chapter 5: Using INMOD and Notify E
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
APPENDIX A How to Read Syntax Diagr
Page 231 and 232:
Appendix A: How to Read Syntax Diag
Page 233 and 234:
Appendix A: How to Read Syntax Diag
Page 235 and 236:
APPENDIX B Teradata TPump Examples
Page 237 and 238:
Appendix B: Teradata TPump Examples
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
APPENDIX C INMOD and Notify Exit Ro
Page 249 and 250:
Appendix C: INMOD and Notify Exit R
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
APPENDIX D User-Defined-Types and U
Page 259 and 260:
Appendix D: User-Defined-Types and
Page 261 and 262:
Glossary A abend: Abnormal END of a
Page 263 and 264:
Glossary data loading: The process
Page 265 and 266:
Glossary join: result. A SELECT ope
Page 267 and 268:
Glossary script: or job. A file tha
Page 269 and 270:
Glossary z/OS (MVS (Multiple Virtua
Page 271 and 272:
Index Symbols - 46 &SYSAPLYCNT syst
Page 273 and 274:
Index function 30 syntax 186 usage
Page 275 and 276:
Index FastLoad 215 IBM interface 21
Page 277 and 278:
Index reduced print output runtime
Page 279 and 280:
Index THRU keyword IMPORT command 1
show all

Teradata Parallel Data Pump

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?