Activity count zero for TPump UPDATE or DELETE

Database
Enthusiast

Activity count zero for TPump UPDATE or DELETE

Dear Team,

I am loading tables in teradata using Tpump loader (through Informatica).

Created error table with  "Activity count zero for TPump UPDATE or DELETE."

Can someone tell me if there is any way to fix issue 

Info from TPUMP manual

1: Error 2818: Activity count zero for TPump UPDATE or DELETE.

Sometimes, you want to know if a data row that was supposed to be updated or deleted wasn’t!

That is when you want to know that the activity count was zero, indicating that the UPDATE or DELETE did not occur. To see this error, you must have used one of the following parameters:

·       MARK MISSING UPDATE ROWS

·       MARK MISSING DELETE ROWS

Can someone tell me what is the issue for same

1 REPLY
Enthusiast

Re: Activity count zero for TPump UPDATE or DELETE


i have changed below two things

1) first change

.DML LABEL LABELA

MARK MISSING UPDATE ROWS ;

2) second change

Error limt has been increased with 20 still we are facing below mentioned problem, PLease anyone help

     ========================================================================

     =                                                                      =

     =          TPump Import(s) Beginning                                   =

     =                                                                      =

     ========================================================================

**** 13:18:20 UTY6630 Options in effect for following TPump Import(s):

     .       Tenacity:    4 hour limit to successfully connect load sessions.

     .   Max Sessions:    30 session(s).

     .   Min Sessions:    24 session(s).

     .     Checkpoint:    60 minute(s).

     .       Errlimit:    1 rejected record(s).

     .   Restart Mode:    SIMPLE.

     .  Serialization:    OFF.

     .        Packing:    15 Statements per Request.

     .   StartUp Rate:    UNLIMITED Statements per Minute.

**** 13:18:21 UTY6608 Import 1 begins.

**** 13:35:53 UTY2813 Error limit exceeded while processing record number 49006,

     ending load.

**** 13:35:53 UTY6641 Since last chkpt., 49741 recs. in, 49081 stmts., 3273

     reqs

**** 13:35:53 UTY6647 Since last chkpt., avg. DBS wait time: 0.32

**** 13:35:53 UTY6606 Beginning checkpoint...

**** 13:36:08 UTY6641 Since last chkpt., 49741 recs. in, 49743 stmts., 3332

     reqs

**** 13:36:08 UTY6647 Since last chkpt., avg. DBS wait time: 0.32

**** 13:36:08 UTY6607 Checkpoint Completes with 49741 rows sent.

     ========================================================================

     =                                                                      =

     =          Logoff/Disconnect                                           =

     =                                                                      =

     ========================================================================

**** 13:36:08 UTY6215 The restart log table has NOT been dropped.

**** 13:36:11 UTY6212 A successful disconnect was made from the RDBMS.

**** 13:36:11 UTY2410 Total processor time used = '2.34053 Seconds'

     .       Start : 13:18:17 - TUE APR 30, 2013

     .       End   : 13:36:11 - TUE APR 30, 2013

     .       Highest return code encountered = '12'.