Teradata Parallel Data Pump

More documents

Recommendations

Info

Glossary extract: The process of copying a subset of data from a source to a target environment. exit routines: Specifies a predefined action to be performed whenever certain significant events occur during a utility job. F failure: Any condition that precludes complete processing of a Teradata SQL statement. Any failure will abort the current transaction. FastExport: Teradata FastExport utility. A program that quickly transfers large amounts of data from tables and views of Teradata Database to a client application. FastLoad: Teradata FastLoad utility. A program that loads empty tables on Teradata Database with data from a network-attached or channel-attached client. field: The basic unit of information stored in Teradata Database. A field is either null, or has a single numeric or string value. See also column, database, row, table. I import: The process of pulling system information into a program. To add system information from an external source to another system. The system receiving the data must support the internal format or structure of the data. INMOD Routine: User-written routines that can be used by load/export utilities to preprocess input records before they are sent to Teradata Database. Routines can be written in C language (for network-attached platforms), orIBM C, (for channel-attached platforms). A routine can read and preprocess records from a file, generate data records, read data from other database systems, validate data records, and convert data record fields. instance: In object-oriented programming, the relationship between an object and its class. The object is an instance of the class. I/O: Input/output J JCL: Job Control Language. A language for describing jobs (units of work) to the OS/390, z/ OS, and VSE operating systems, which run on IBM's OS/390 and z800/900 large server (mainframe) computers. These operating systems allocate time and space resources among the total number of active jobs. Jobs in turn break down into job steps, which are the statements required to run a particular program. Jobs are background (sometimes called batch) units of work that run without requiring user interaction (for example, print jobs). In addition, the operating system manages interactive (foreground) user requests that initiate units of work. In general, foreground work is given priority over background work. job script: A set of commands and Teradata SQL statements that can initiate an operation that inserts new rows, updates existing rows, and deletes rows in specified target tables and views in Teradata Database. 264 Teradata Parallel Data Pump Reference
Glossary join: result. A SELECT operation that combines information from two or more tables to produce a L locks: Teradata load/unload utilities automatically lock any table being loaded and free a lock only after an END LOADING statement is entered. Therefore, tables are only available when the operation is complete. log: A record of events. A file that records events. Many programs produce log files. Often a log file is looked at to determine what is happening when problems occur. Log files have the extension “.log”. M macro: A file created and stored on Teradata Database and executed in response to a Teradata SQL EXECUTE statement. Each macro execution is implicitly treated as a transaction. methods: In object-oriented programming, programming routines by which objects are manipulated. MultiLoad: Teradata MultiLoad utility. A command-driven utility that performs fast, highvolume maintenance functions on multiple tables and views of Teradata Database. multiset tables: Tables that allow duplicate rows. N name: A word supplied by the user that refers to an object, such as a column, database, macro, table, user, or view. network-attached: A computer that communicates over the LAN with a server (for example, Teradata Database). notify exit: A user-defined exit routine that specifies a predefined action to be performed whenever certain significant events occur during a job. For example, by writing an exit in C (without using CLIv2) and using the NotifyExit attribute, the routine can detect whether a job succeeds or fails, the number of loaded records, the return code for a failed job, and so on. null: The absence of a value for a field. O object: In object-oriented programming, a unique instance of a data structure defined according to the template provided by its class. Each object has its own values for the variables belonging to its class and can respond to the messages, or methods, defined by its class. owner: In Teradata SQL, the user who has the ability to grant or revoke all privileges on a database. By default, the creator of the database is the owner, but ownership can be transferred from one user to another by the GIVE statement. Teradata Parallel Data Pump Reference 265
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:
Page 47 and 48:
Page 49 and 50:
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 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Chapter 2: Using Teradata TPump Wri
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Chapter 2: Using Teradata TPump Vie
Page 77 and 78:
Page 79 and 80:
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: Chapter 5: Using INMOD and Notify E
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 247 and 248: APPENDIX C INMOD and Notify Exit Ro
Page 249 and 250: Appendix C: INMOD and Notify Exit R
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: Glossary data loading: The process
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?