Pillar Axiom: MaxRep Daily Change Rates are not displayed in the MaxRep UI

Asset ID:	1-72-1995805.1
Update Date:	2018-04-25
Keywords:

Solution Type Problem Resolution Sure

Solution 1995805.1 : Pillar Axiom: MaxRep Daily Change Rates are not displayed in the MaxRep UI

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 2.0 to 2.0 [Release 2.0]
Information in this document applies to any platform.

Symptoms

Maxrep UI Monitor -> Statistics --> Data Change Rates and Monitor --> Reports --> Health Report

If there are no recent timestamps and the rates are being successfully updated but the graphical statistics are not being displayed then there may be an issue with rrd.

Changes

Any implementations running MaxRep R1.x.x or MaxRep R2.x.x can be affected.

MaxRep 3.0.2 and higher is not impacted by this issue.

Cause

By default MaxRep R1.x.x and R2.x.x uses rrd for showing the statistics.

Rrd has dependency commands to fetch data from the rrd and health check reports. If these files are not updated then rrd will display errors and the daily change rates will not be updated in the Graphical User Interface (GUI).

It was detected that the rrd files were not being updated due to a "Bad file descriptor".

Support need to check the tman_monitor_reports.log for any errors listed under the health reports for rrd files.

Line 338123: 2015-02-24 13:37:02 EXCEPTION : MONITOR_REPORTS : Unable to update /home/svsystems/22bd0f10-fc02-4eb0-b4be-c4fd51e6ddca/dev/mapper/2000b0826c1002899/perf.rrd: Bad file descriptor at /home/svsystems/pm/ConfigServer/Trending/HealthReport.pm line 810

Line 338143: 2015-02-24 13:42:02 EXCEPTION : MONITOR_REPORTS : Unable to update /home/svsystems/22bd0f10-fc02-4eb0-b4be-c4fd51e6ddca/dev/mapper/2000b0826c1002899/perf.rrd: Bad file descriptor at /home/svsystems/pm/ConfigServer/Trending/HealthReport.pm line 810

Line 338163: 2015-02-24 13:47:02 EXCEPTION : MONITOR_REPORTS : Unable to update /home/svsystems/22bd0f10-fc02-4eb0-b4be-c4fd51e6ddca/dev/mapper/2000b0826c1002899/perf.rrd: Bad file descriptor at /home/svsystems/pm/ConfigServer/Trending/HealthReport.pm line 810

Line 338183: 2015-02-24 13:52:02 EXCEPTION : MONITOR_REPORTS : Unable to update /home/svsystems/22bd0f10-fc02-4eb0-b4be-c4fd51e6ddca/dev/mapper/2000b0826c1002899/perf.rrd: Bad file descriptor at /home/svsystems/pm/ConfigServer/Trending/HealthReport.pm line 810

Line 338203: 2015-02-24 13:57:02 EXCEPTION : MONITOR_REPORTS : Unable to update /home/svsystems/22bd0f10-fc02-4eb0-b4be-c4fd51e6ddca/dev/mapper/2000b0826c1002899/perf.rrd: Bad file descriptor at /home/svsystems/pm/ConfigServer/Trending/HealthReport.pm line 810

Solution

Please open a new Service Request and refer to this Knowledge Article. Oracle Support will initiate a WebEx Support Session to apply a workaround.

Log into the Control Service Engine as root.

Run the rrd_tune.pl script to tune rrd:

# perl /home/svsystems/bin/rrd_tune.pl

If there is a time difference between the local time of the users’s browser and the local time of the Control Service Engine, or if there is a difference between the local time of the Control Service Engine and the local time of the Process Service of the other Engine in Asynchronous replication, the following change rrd timestamp script must be run.

# perl /home/svsystems/bin/change_rrd_timestamp.pl

The tmanagerd service must be restarted for the changes to take effect.

# service tmanagerd restart

Attachments

This solution has no attachment