At times Post is observed to be slow and heavily backlogged on one target instance though it is running fine on other targets. The question arises as to whether Post needs to be tuned on the problem target though in many cases the target databases are perceived to be identical.
General information about probable factors affecting the problematic target.
The following are some of the plausible causes that may be causing one target to behave in a problematic manner relative to other targets:
Shareplex factors:
1. Check the event_log. Post on the problem target is encountering some error conditions.
2. Check the paramdb file. Shareplex parameters on the problem target are configured differently and need to be tuned to deal with present situation. Sometimes the debug left turned on inadvertently may also cause performance issues. All this can happen even though the databases may have been configured identically.
3. Database factors:
A. Objects not analyzed on problem target database for some time.
B. Reporting or other user activity is more on the problem target than on the other targets.
C. Structures (indexes, constraints, etc) changed on one target relative to other targets.
D. Though the databases may have been configured identically to begin with, this is no guarantee that they will remain this way permanently. Their parameters and physical structures can change over a period of time because of tuning efforts carried out independently.
4. Hardware factors: Disk, network and other hardware problems on one target may not be present on other targets, though all targets may be identical or similar in all other respect.
