Teradata Parallel Data Pump

More documents

Recommendations

Info

Chapter 4: Troubleshooting Reading Teradata TPump Error Tables Avoiding Data Errors Acquisition Error Table The following data-related conditions can all cause records to be written to the error table: • A non-existent target table • Inadequate privileges to the target table • Mismatched table schema and Teradata TPump DML • Attempting to store NULL value in a NOT NULL table column • Out-of-range values • Data conversion errors, which require input data to be corrected To help prevent performance issues, it is important to ensure that your data sources generate data records that are valid for the characteristic of the target tables. The error table is primarily used to hold information about errors that occur while Teradata Database is trying to redistribute the data during the acquisition phase. If Teradata Database is unable to build a valid primary index, some application phase errors may be put into this table. Table 30 defines the Acquisition Error Table, with column entries comprising the unique primary index. Table 30: Acquisition Error Table Column Data Type Definition ImportSeq byteint Sequence number assigned to the IMPORT command in which the error occurred. DMLSeq byteint Sequence number assigned to the DML command in which the error occurred. SMTSeq byteint Sequence number of the DML statement in the DML command that was being executed while this error occurred. ApplySeq byteint Sequence number of apply clause in IMPORT command executing when error occurred. SourceSeq integer The data row number in the client file that the DBC was building when the error occurred. DataSeq byteint The data source where the record resides. ErrorCode char(255) The database code for the error. ErrorMsg char The corresponding error message for the error code. ErrorField smallint The number of the field in error if it can be determined. HostData varbyte (63677) The first 63,677 bytes of client data associated with the error. LoadStartTime The beginning of the job time. On restart, LoadStartTime is the beginning of the restart time. 200 Teradata Parallel Data Pump Reference
Chapter 4: Troubleshooting Reading Teradata TPump Error Tables Interpreting Error Table Information The following Teradata TPump task describes how to interpret the error table information to isolate and fix the problem. This task is greatly abbreviated, containing only the DML command and the IMPORT command. A probable sequence of actions for locating and fixing the problem follows the task. SEQ TYPE SEQ # Statement -------- --- ------------------------------------------------------- DML 001 .DML LABEL FIRSTDML; STMT 001 INSERT INTO table1 VALUES( :FIELD1, :FIELD2 ); STMT 002 UPDATE table2 SET field3 = :FIELD3 WHERE field4 =:FIELD4; DML 002 .DML LABEL SECNDDML; STMT 001 DELETE FROM table3 WHERE field3 = :FIELD3; IMPORT 001 .IMPORT INFILE file1 LAYOUT layout1 APPLY 001 APPLY FIRSTDML; IMPORT 002 .IMPORT INFILE file2 LAYOUT layout2 APPLY 001 APPLY FIRSTDML APPLY 002 APPLY SECNDDML; In this example, the Statement column represents the user entry. The SEQ # and SEQ TYPE columns are the Sequence Number and Sequence Type assigned to each statement. If an error occurs while using this task and the information in the following error table is displayed, where the error occurred and what was being executed at the time of the error can be determined. ImportSeq DMLSeq SMTSeq ApplySeq SourceSeq DBCErrorCode DBCErrorField --- --- --- --- --------- ----- ------------ 002 001 002 001 20456 2679 field3 The following sequence provides a series of analytical steps for extracting and interpreting the information in this row of the error table. 1 Check the DMLSeq field to find the statement being executed. It contains the sequence number 001. 2 Check the SMTSeq field. The sequence number 002 in this field indicates that the error occurred while executing: change this statement of the first DML command, which is the UPDATE statement in the above task. 3 Verify that the script shows that the DML command is used twice, once in each IMPORT. 4 The value of 002 in the ImportSeq field shows that the error occurred in the second IMPORT clause. 5 The value of 001 in the ApplySeq field indicates that the error occurred in the first apply of that clause, which was being executed when the error occurred. 6 The value of 2679 in the DBCErrorCode field shows: The format or data contains a bad character which indicates that bad data is coming from the client. Teradata Parallel Data Pump Reference 201
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: 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: 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 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 251 and 252:
Appendix C: INMOD and Notify Exit R
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

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

Delete template?

Save as template?