Teradata Parallel Data Pump

More documents

Recommendations

Info

Glossary P parameter: A variable name in a macro for which an argument value is substituted when the macro is executed. parser: A program executing in a PE that translates Teradata SQL statements entered by a user into the steps that accomplish the user’s intensions. PE: Parsing engine. The vprocs that receive SQL requests from the client and break the requests into steps. The PE sends the steps to the AMPs and subsequently returns the answer to the client. primary key: The field (column) in a database table that is indexed and maintains the main sequence of the table. For example, account numbers are typically primary keys. A "composite primary key" is made up of two or more fields (columns) such as region + account number. A primary key is also known as a unique identifier. privilege: A user’s right to perform read, write, and execute operations against a table, database, user, macro, or view. R RDBMS (Relational Database Management System): A database management system in which complex data structures are represented as simple two-dimensional tables consisting of columns and rows. For Teradata, RDBMS is referred to as Teradata Database. records: When using Teradata utilities, both formatted and unformatted records are accepted for loading. A formatted record, in the Teradata Database world, consists of a record created by a Teradata utility, such as BTEQ, where the record is packaged with begin- and endrecord bytes specific to Teradata Database. Unformatted records are any data file, such as a text file, that does not have various properties such as a consistent structure with regard to record length and order of data elements. These files must be defined before loading onto Teradata Database. request: Database. In host software, a message sent from an application program to Teradata restart log table: paused job. One of four restart tables that the Teradata utilities require for restarting a result: The information returned to the user to satisfy a request made of Teradata Database. row: The fields that represent one entry under each column in a table. The row is the smallest unit of information operated on by data manipulation statements. S schema: Used for identifying the structure of data. Producers have an output schema to define what the source data will look like in the data stream. Consumers have an input schema to define what is read from the data stream. If the input and output schemas are the same, the schema need only be defined once. 266 Teradata Parallel Data Pump Reference
Glossary script: or job. A file that contains a set of commands and SQL statements that initiates an operation separator: A character or group of characters that separates words and special symbols in Teradata SQL. Blanks and comments are the most common separators. server: The computer system running Teradata Database. Typically, a Teradata Database server has multiple nodes, which may include both TPA and non-TPA nodes. All nodes of the server are connected via the Teradata BYNET or other similar interconnect. session: A session begins when the user logs on to Teradata Database and ends when the user logs off Teradata Database. Also called a Teradata Database session. In client software, a logical connection between an application program on a host and Teradata Database that permits the application program to send one request to and receive one response from Teradata Database at a time. source: The table designated to receive data that is moved or copied from some other source file, table, or database. SQL: Structured Query Language. An industry-standard language for creating, updating and, querying relational database management systems. SQL was developed by IBM in the 1970s for use in System R. It is the de facto standard as well as being an ISO and ANSI standard. It is often embedded in general purpose programming languages. The programming language used to communicate with Teradata Database. SSO: Single Sign On. An authentication option that allows Teradata users on Windows systems to access Teradata Database based on authorized network usernames and passwords. This feature simplifies the procedure requiring users to enter an additional username and password when logging on to Teradata Database using client applications. statement: A request for processing by Teradata Database that consists of a keyword verb, optional phrases, operands, and is processed as a single entity. statistics: The details of the processes used to collect, analyze, and transform the database objects used by a given query. T table: A set of one or more columns with zero or more rows that consist of fields of related information. target database: The database designated to receive data that is moved or copied from some other source file, table, or database. target table: the table designated to receive data that is moved or copied from another table, source file, or database. TDPID: accessed. Teradata Director Program Identifier. The name of the Teradata Database being Teradata Parallel Data Pump Reference 267
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:
Page 215 and 216: 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 and 264: Glossary data loading: The process
Page 265: Glossary join: result. A SELECT ope
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?