Teradata Parallel Data Pump

More documents

Recommendations

Info

Glossary to interact with Teradata Database. BTEQ commands control sessions, submit Teradata SQL requests, format results, and handle output data. BTEQ can also be used to verify the installation of Teradata client utilities. C CLIv2: Call-Level Interface Version 2. A collection of callable service routines that provide an interface to Teradata Database. Specifically, CLI is the interface between the application program and the Micro Teradata Directory Program (for network-attached clients) or the Micro Operating System Interface (for network-attached clients). CLIv2 provides the application with a pointer to each of the parcels returned from Teradata Database. channel-attached: Peripheral devices directly attached to a computer via a channel or bus. The term is used in contrast with devices that are reached remotely over a network character set: A grouping of alphanumeric and special characters used by computer systems to support different user languages and applications. Various character sets have been codified by the American National Standards Institute (ANSI). checkpoint rate: The interval between checkpoint operations during the acquisition phase of an import task, expressed as either the number of rows read from the client system or sent to Teradata Database, or as an amount of time, in minutes. client: A computer that can access Teradata Database. cluster: Logical, table-level archive whereby only those rows residing on specific AMPs, and which are members of the specified cluster, are archived onto a single tape data set. This allows multiple jobs to be applied for backup of large tables, to reduce the backup window. This method is used to affect a parallel archive/restore operation via a “divide and conquer” backup strategy. column: In the relational model of Teradata SQL, databases consist of one or more tables. In turn, each table consists of fields, organized into one or more columns by zero or more rows. All of the fields of a given column share the same attributes. D DDL: Data Definition Language. In Teradata SQL, the statements and facilities that manipulate database structures (such as CREATE, MODIFY, DROP, GRANT, REVOKE, and GIVE) and the Data Dictionary information kept about those structures. Data Dictionary: In Teradata Database, the information automatically maintained about all tables, views, macros, databases, and users known to Teradata Database, including information about ownership, space allocation, accounting, and privilege relationships between those objects. Data Dictionary information is updated automatically during the processing of data definition statements, and is used by the parser to obtain information needed to process all Teradata SQL statements. 262 Teradata Parallel Data Pump Reference
Glossary data loading: The process of loading data from a client platform to a Teradata Database server. For Teradata TPump, data loading includes any combination of INSERT, UPDATE, DELETE, and UPSERT operations. data manipulation: In Teradata SQL, the statements and facilities that change the information content of the database. These statements include INSERT, UPDATE, and DELETE. data warehouse: A subject oriented, integrated, time-variant, non-volatile collection of data in support of management’s decision making process. A repository of consistent historical data that can be easily accessed and manipulated for decision support. DBA: Database administrator. Generally, a person responsible for the design and management of one or more databases and for the evaluation, selection, and implementation of database management systems. DD: Data dictionary or data definition. See also Data Dictionary. DEFINE statement: A statement preceding the INSERT statement that describes the fields in a record before the record is inserted in the table. This statement is similar to the SQL USING clause. DELETE statement: A task that uses a full file scan to remove a large number of rows from a single Teradata Database table. A delete task is composed of three major phases: preliminary, application, and end. The phases are a collection of one or more transactions that are processed in a predefined order according to utility protocol. delimiter: In Teradata SQL, a punctuation mark or other special symbol that separates one clause in a Teradata SQL statement from another, or that separates one Teradata SQL statement from another. DLL: Dynamic link library. A feature of the Windows family of operating systems that allows executable routines to be stored separately as files with .dll extensions and to be loaded only when needed by a program. DML: Data manipulation language. In Teradata SQL, the statements and facilities that manipulate or change the information content of the database. These statements include SELECT, INSERT, UPDATE, and DELETE. E EBCDIC: Extended binary coded decimal interchange code. An IBM code that uses 8 bits to represent 256 possible characters. It is used primarily in IBM mainframes, whereas personal computers use ASCII. error tables: Tables created during processing that capture any errors that occurred. The Teradata convention is to name the tables ET and UV. An ET table contains errors that occur during the Acquisition Phase related to data and the data environment (such as constraint violations and unavailable AMPs). A UV table contains errors that occur during the Application Phase related to violations of unique primary indexes. Teradata Parallel Data Pump Reference 263
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: 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: Glossary A abend: Abnormal END of a
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?