Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 3: Teradata TPump Commands IMPORT Syntax Element AXSMOD name Description Name of the access module file to be used to import data The names of the access module files are: Teradata OLE DB Access Module oledb_axsmod.dll on Microsoft® Windows platforms Named Pipes Access Module • np_axsmod.sl on Hewlett-Packard® HP-UX platforms • np_axsmod.so on IBM® AIX®, Sun® Solaris® SPARC®, Sun® Solaris® Opteron®, and Novell® SUSE® Linux Enterprise and Red Hat® Enterprise Linux® Advanced Server platforms, z/Linux,] • np_axsmod.dll on Windows platforms Note: When using Teradata TPump latency option with Named Pipe Access Module, the Named Pipe Access Module parameter file should use need_full_block = no option. Teradata WebSphere® MQ Access Module (client version) • libmqsc.sl on HP-UX platforms • libmqsc.so on IBM AIX, z/Linux, Sun Solaris SPARC, Solaris Opteron, and Linux platforms • libmqsc.dll on Windows platforms Teradata WebSphere® MQ Access Module (server version) • libmqs.sl on HP-UX platforms • libmqs on IBM z/OS/ESA platforms • libmqs.so on IBM AIX, z/Linux, Sun Solaris SPARC, Solaris Opteron, and Linux platforms • libmqs.dll on Windows platforms A custom shared library file name can be used for a custom access module. The AXSMOD option is not required for importing: • Disk files on either network- or channel-attached client systems • Magnetic tape files on channel-attached client systems It is required for importing magnetic tape and other types of files on network-attached client systems. Refer to Teradata Tools and Utilities Access Module Reference for more information about the specific access modules. Teradata Access Module for JMS • libjmsam.so on IBM AIX, Sun Solaris SPARC, Solaris Opteron, and Red Hat Linux platforms • libjmsam.sl on HP-UX • libjmsam.dll on Windows platforms 'init-string' Optional initialization string for the access module 148 Teradata Parallel Data Pump Reference
Chapter 3: Teradata TPump Commands IMPORT Syntax Element INFILE filename HOLD FREE INMOD modulename Description Fully qualified UNIX or Windows path name for an input file on networkattached client systems If the path name has embedded white space characters, the entire path name must be enclosed in single or double quotes. To specify the INFILE filename, the data is read from the specified source. To specify the INMOD modulename, the data is passed to the specified module. Default condition to not deallocate the input tape device specified by ddname when the import operation completes on channel-attached client systems Instead, the HOLD specification deallocates the device when the entire Teradata TPump operation completes. Deallocation of the tape input device specified by ddname when the import operation completes on channel-attached client systems When de-allocated, any attempt to open the input device, either in the same Teradata TPump utility task or in another task within the same script, produces an undefined ddname error. The default is to not deallocate the device. Optional user-written routine for preprocessing the input data In z/OS, the modulename is the name of a load module. In UNIX and Windows, it is the pathname for the INMOD executable code file. The modulename must obey the applicable rules of the external system. A modulename must obey the same construction rules as Teradata SQL column names except that on channel-attached client systems: • The “at” character (@) is allowed as an alphabetic character • The underscore character (_) is not allowed When both the INFILE fileid and the INMOD modulename parameters are specified, the input file is read and the data is passed to the INMOD routine for preprocessing. If the INFILE fileid parameter is not specified, the INMOD routine must provide the input data record. Note: When an INMOD routine is used with the INFILE specification, Teradata TPump performs the file read operation, and the INMOD routine acts as a pass-through filter. Because the FDL-compatible INMOD routine must always perform the file read operation, an FDL-compatible INMOD routine cannot be used with the INFILE specification of a Teradata TPump IMPORT command. Note: On some versions of UNIX, ./ prefix characters may have to be added to the modulename specification if the module is in the current directory. Teradata Parallel Data Pump Reference 149
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: Chapter 3: Teradata TPump Commands
Page 147: Chapter 3: Teradata TPump Commands
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?