The reason is usually given just before the first line in your log on the
source server, so the line above the one with the ANR0986I code.


On Wed, Jul 26, 2017 at 8:07 PM, Tim Brown <TBrown AT cenhud DOT com> wrote:

> TSM node replication fails , no indication why on source or target server?
>
> Source server
>
> 07/26/2017 13:25:49      ANR0986I Process 385 for Replicate Node running
> in the
>                           BACKGROUND processed 3,782,768 items for a total
> of
>                           777,525,123,113 bytes with a completion state of
> FAILURE
>                           at 13:25:49. (SESSION: 21075, PROCESS: 385)
> 07/26/2017 13:25:49      ANR1893E Process 385 for Replicate Node completed
> with a
>                           completion state of FAILURE. (SESSION: 21075,
> PROCESS:
>                           385)
>
> Target server
>
> 07/26/2017 13:25:51      ANR0514I Session 486 closed volume
>                           N:\ECM_PRIM2\01BC04E0.BFS. (SESSION: 486)
> 07/26/2017 13:26:22      ANR0408I Session 605 started for server
> TSMPOK_SERVER1
>                           (Windows) (Tcp/Ip) for replication.  (SESSION:
> 605)
> 07/26/2017 13:26:22      ANR0409I Session 486 ended for server
> TSMPOK_SERVER1
>                           (Windows). (SESSION: 486)
> 07/26/2017 13:26:22      ANR0409I Session 605 ended for server
> TSMPOK_SERVER1
>                           (Windows). (SESSION: 605)
> 07/26/2017 13:26:41      ANR0985I Process 51 for Replicate Node ( As
> Secondary )
>                           running in the BACKGROUND completed with
> completion state
>                           FAILURE at 13:26:41. (SESSION: 410, PROCESS: 51)
> 07/26/2017 13:26:41      ANR1893E Process 51 for Replicate Node ( As
> Secondary )
>                           completed with a completion state of FAILURE.
> (SESSION:
>                           410, PROCESS: 51)
>
> Tim
>