Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 1: Overview The Teradata TPump Task updates of other columns. A reflexive update of a column computes the new value as the result of an expression that involves the current value of one or more columns. Teradata TPump processes and validates all statements from the BEGIN LOAD through the END LOAD statements. Teradata TPump control and processing sessions are established and Teradata SQL requests are transmitted to Teradata Database. Teradata TPump creates a single error table and a set of macros, one for each DML statement. Nothing protects target tables from concurrent access. Teradata TPump imports data, evaluating each record according to specified apply conditions. For each satisfied apply condition, a record is sent to Teradata Database. If the record causes an error, this sequence number is available in the error table so that the record can be identified. When the task completes, all locks are released, all macros dropped and, if empty, the error table is dropped. Statistics concerning the outcome of the IMPORT task are reported. Access logging can cause a severe performance penalty. If all successful table updates are logged, a log entry is made for each operation. The primary index of the access logging table may then create the possibility of row hash conflicts. Fallback vs. Nonfallback Tables Target tables can be either fallback or nonfallback. Table 10 lists the differences between, and characteristics of, these tables. Table 10: Comparison of Fallback and Nonfallback Target Tables Fallback Tables Teradata TPump task continues to execute even if AMPs are down, as long as there is not more than one AMP down, either logically or physically in a cluster. If two or more AMPs in a cluster are logically or physically down, or both, the task does not run, or terminates if running. During the task, if AMPs are down to the extent that data on the disk is corrupted, the affected tables must be restored. Not applicable. Not applicable. Nonfallback Tables If one or more AMPs are down prior to entering the task and if one or more target tables are nonfallback, Teradata TPump terminates. The Teradata TPump task may be restarted as soon as all AMPs are back up. If an AMP goes down once the task has started, the task cannot be restarted until all AMPs are back up. If more than one AMP in the same cluster is down, Teradata Database cannot come up. Certain I/O errors during the task corrupt the target table so that it must be restored. In this case, Teradata TPump terminates. 36 Teradata Parallel Data Pump Reference
CHAPTER 2 Using Teradata TPump This chapter provides detailed information about using the Teradata TPump utility. Topics include: • Invoking Teradata TPump • Terminating Teradata TPump • Restart and Recovery • Program Considerations • Writing a Teradata TPump Job Script • View Teradata TPump Output • Monitor Teradata TPump Jobs • Estimating Space Requirements Invoking Teradata TPump Teradata TPump Support Environment This section describes those Teradata TPump functions that are invoked from the Teradata TPump support environment on the client system. The Teradata TPump support environment is a platform from which Teradata TPump and a number of standard Teradata SQL, DDL, and DML operations can be performed. This client program includes a facility for executing Teradata SQL and is separate from Teradata TPump tasks that run in Teradata Database. Teradata TPump support environment functionality includes: • Providing access to the data manipulation and data definition functions of the Teradata SQL language. • User-defined variables and variable substitution. • System-defined variables (for example, date and time). • Conditional execution based on the value of return codes and variables. • Expression evaluation. • Redirection of command input. • Runtime parameters for Teradata TPump invocation, foreign language support, and error logging functions. • Character set selection options for IBM mainframe and UNIX client-based systems. Teradata Parallel Data Pump Reference 37
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 23 and 24: Chapter 1: Overview Operating Featu
Page 25 and 26: Chapter 1: Overview Operating Featu
Page 33 and 34: Chapter 1: Overview The Teradata TP
Page 35: Chapter 1: Overview The Teradata TP
Page 39 and 40: 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 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
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

Create successful ePaper yourself

Delete template?

Save as template?