Troubleshooting Replication-Related

Error/Symptom

 

Reason

 

Impact

 

Remedy

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

maximum time lag

 

 

 

 

 

 

 

 

from the replication

 

 

 

 

 

 

 

 

monitor among all the

 

 

 

 

 

 

 

 

consumers.

 

 

 

 

 

 

 

 

Irrespective of what

 

 

 

 

 

 

 

 

the purge threshold

 

 

 

 

 

 

 

 

is, no change will be

 

 

 

 

 

 

 

 

purged before it is

 

 

 

 

 

 

 

 

replayed by all the

 

 

 

 

 

 

 

 

consumers.

 

 

 

 

 

 

 

 

 

 

 

The Replication

 

The SSL port is

 

 

 

Map the SSL port to a

 

 

Monitor is not

 

specified in some

 

 

 

non-SSL port in the

 

 

responding. (For

 

replication

 

 

 

configuration file of

 

 

information on

 

agreement, but the

 

 

 

the Replication

 

 

Replication Monitor,

 

certificate database is

 

 

 

Monitor. For example,

 

 

see Section 17,

 

not specified or not

 

 

 

if 636 is the SSL port

 

 

“Monitoring

 

accessible by the

 

 

 

and 389 is the

 

 

Replication Status”.)

 

Replication Monitor. If

 

 

 

non-SSL port, add the

 

 

 

 

there is no SSL port

 

 

 

following line in the

 

 

 

 

problem, one of the

 

 

 

[connection]

 

 

 

 

servers in the

 

 

 

section:

 

 

 

 

replication topology

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

might hang.

 

 

 

*:636=389:*:password

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

In the Replication

 

No change has

 

 

 

There is nothing

 

 

Monitor, some

 

originated from the

 

 

 

wrong if there is no

 

 

consumers show just

 

corresponding

 

 

 

change originated

 

 

the header of the

 

suppliers. In this

 

 

 

from a supplier.

 

 

table. (For information

 

case, the MaxCSN: in

 

 

 

 

 

 

on Replication

 

the header part

 

 

 

 

 

 

Monitor, see

 

should be "None".

 

 

 

 

 

 

Section 17,

 

 

 

 

 

 

 

 

“Monitoring

 

 

 

 

 

 

 

 

Replication Status”.)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Table 8.7. Replication Errors

351

Page 371
Image 371
HP UX Red Hat Direry Server Software manual Replication Errors, See Section, Monitoring, Replication Status