Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 1: Overview Operating Features and Capabilities There are restrictions imposed by Teradata Database on using the UTF-8 or UTF-16 character set. Refer to International Character Set Support for restriction details. UTF-8 Character Sets Teradata TPump supports UTF-8 character set on network-attached platforms and IBM z/OS. On IBM z/OS, the job script must be in Teradata EBCDIC when using UTF-8 client character set. Teradata TPump will translate commands in the job script from Teradata EBCDIC to UTF-8 during the load. Be sure to examine the definition in International Character Set Support to determine the code points of any special characters which might be required in the job script. Different versions of EBCDIC do not always agree as to the placement of these characters. Refer to the mappings between Teradata EBCDIC and Unicode in Appendix E of International Character Set Support. Currently, UTF-8 Byte Order Mark (BOM) is not supported on the z/OS platform when using access modules or data files. See Chapter 3 for complete information on Teradata TPump commands. Refer to • parameters commands nullexpr • fieldexpr • VARTEXT format delimiter • WHERE condition • CONTINUEIF condition for additional information on using UTF-8 client character set on the mainframe. UTF-16 Character Sets Teradata TPump supports UTF-16 character set on network-attached platforms. In general, the command language and the job output should be the same as the client character set used by the job. However, for user’s convenience and because of the special property of Unicode, the command language and the job output are not required to be the same as the client character set when using UTF-16 character set. When using UTF-16 character set, the job script and the job output can either be in UTF-8 or UTF-16 character set. This is provided by specifying runtime parameters "-i" and "-u" when the job is invoked. For more reference information on runtime parameters “-i” and “-u”, see parameters -i scriptencoding and -u outputencoding on “-u outputencoding” on page 46. Also refer to parameters commands fieldexpr “fieldexpr” on page 135, nullexpr on “nullexpr” on page 134, WHERE condition on “WHERE condition” on page 111 and CONTINUEIF condition on “CONTINUEIF condition” on page 161 for additional information on using UTF-16 client character set. Client Character Set/Client Type Compatibility Table 6 is a general guideline for choosing client character sets that may work better for the client environment. 26 Teradata Parallel Data Pump Reference
Chapter 1: Overview Teradata TPump Commands Table 6: General Guidelines for Choosing Client Character Sets Client Type Best Client Character Sets Channel-attached • EBCDIC • EBCDIC037_0E • KANJIEBCDIC5026_0I • KANJIEBCDIC5035_0I • KATAKANAEBCDIC • SCHEBCDIC935_2IJ • TCHEBCDIC937_3IB • HANGULEBCDIC933_1II • UTF-8 Network-attached running UNIX • ASCII • KANJIEUC_0U • LATIN1_0A • LATIN9_0A • UTF-8 • UTF-16 • SCHGB2312_1T0 • TCHBIG5_1R0 • HANGULKSC5601_2R4 Network-attached running Windows • ASCII • KANJISJIS_0S • LATIN1252_0A • UTF-8 • UTF-16 • SCHGB2312_1T0 • TCHBIG5_1R0 • HANGULKSC5601_2R4 Site-Defined Character Sets When the character sets defined by Teradata Database are not appropriate for a site, custom character sets can be defined. Refer to Teradata Database International Character Set Support for information on defining custom own character set. Teradata TPump Commands Teradata TPump accepts both Teradata TPump commands and a subset of Teradata SQL statements. These are described in the following sections: Teradata Parallel Data Pump Reference 27
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: Chapter 1: Overview Operating Featu
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 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 77 and 78:
Chapter 2: Using Teradata TPump Vie
Page 79 and 80:
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?