Teradata Parallel Data Pump

More documents

Recommendations

Info

Appendix D: User-Defined-Types and User-Defined-Methods User-Defined-Types and User-Defined-Methods User-Defined-Methods (UDMs) Teradata Database developer-created custom functions, which are explicitly connected to UDTs are known as User-Defined-Methods (UDMs). All UDMs must reside on server. UDMs can be used to create an interface to the UDT that is independent of the UDT's internal representation. This makes it possible to later enhance a given UDT even in cases where the internal representation of the UDT must be changed to support the enhancement, without changing all of the database applications which use the UDT. Creating UDTs with Teradata TPump Teradata TPump cannot create a custom UDT. Inserting and Retrieving UDTs with Client Products External Types A UDT can only exist on the Teradata Database server. Each UDT has an associated “from-sql routine” and “to-sql routine”. • Insert - The “to-sql routine” constructs a UDT value from a pre-defined type value. The “to-sql routine” is automatically invoked when inserting values from a client system into a UDT on the Teradata Database server. • Retrieve - The “from-sql routine” generates a pre-defined type value from a UDT. The “from-sql routine” is automatically invoked when a UDT is retrieved from the Teradata Database server to a client system. The “from-sql routine” and the “to-sql routine” create a mapping between a UDT and a predefined type. This pre-defined type is called the external type of a UDT. A client application only deals with the external type; it does not deal with UDT value directly. External Type Example For example, if the following conditions exist: • UDT named FULLNAME exists • The external type associated with FULLNAME is VARCHAR(46) Then, during an retrieve of FULLNAME values, the Teradata Database server converts the values from FULLNAME values to VARCHAR(46) values by invoking the “from-sql routine” associated with the FULLNAME UDT. Note: The client must expect to receive the data in the same format as it receives VARCHAR(46) values. Similarly, when values are provided by the client for insert into a FULLNAME UDT, the client must provide values in the same way it would provide values for a VARCHAR(46) field. The Teradata Database server will convert the values from VARCHAR(46) to FULLNAME values using the “to-sql routine” associated with the FULLNAME UDT. 258 Teradata Parallel Data Pump Reference
Appendix D: User-Defined-Types and User-Defined-Methods User-Defined-Types and User-Defined-Methods Inserting UDTs with Teradata TPump Teradata Parallel Data Pump program can insert values into tables containing UDT columns in the same manner as is done for other tables. • Input Records - The input records to Teradata TPump must have the column data for UDT columns in its external type format. When the input record format is defined, the external type must be used for the UDT columns. Also, if the “TABLE” command is used to define the input record format and columns in the referenced tables contain UDTs, then the external types corresponding to the UDTs will be used in the input record format for those columns • Table Command - If the “TABLE” command is used to define the input record format, and columns in the referenced TABLEs contain UDTs, then the external types corresponding to the UDTs will be used in the input record format for those columns. Retrieving UDTs with Teradata TPump UDTs cannot be retrieved with Teradata TPump. Retrieving UDT Metadata with Teradata TPump UDT metadata cannot be retrieved with Teradata TPump. Teradata Parallel Data Pump Reference 259
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: 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: APPENDIX D User-Defined-Types and U
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?