Reporting
By default IBM® Sterling Control Center Monitor limits reports to 5000 rows. You can increase the report limit by updating IBM Sterling Control Center Monitor engine property values. And when you increase the report limit, you may also need to allow more memory to be allocated to Event Processor (EP) to avoid out of memory errors from occurring.
To increase the report limit, edit the ReportService.xml
property
reportRecordLimit
.
The engine.properties
value for DB_BATCH_SIZE
specifies the
number of records to use for batch insertion when temporary tables are created for use by Reports.
Valid values are 1 through 2,147,483,647. This value must contain an integer greater than or equal
to 1 and default is 1000 rows. Increasing the batch size above the default of 1000 rows might
improve the speed of the report by one or two seconds. However, increasing the batch size could
result in out of memory errors occurring.
The engine.properties
value for JDBC_DRIVER_MAX_ROWS
controls
how many records are read at one time from the database when paging through tables with large
amounts of data for Sterling File Gateway Detail by Producer reports. The default for this property
is 10000 and it is only used for this one report. You may get better performance for this report by
increasing this value.
ERROR SimpleFontExtensionHelper - Error loading font family
net.sf.jasperreports.engine.fonts.InvalidFontException: Error loading font "net/sf/jasperreports/fonts/dejavu/DejaVuSans-BoldOblique.ttf".
at net.sf.jasperreports.engine.fonts.SimpleFontFace.loadFont(SimpleFontFace.java:206) ~[jasperreports-6.7.0.jar:6.6.0]
. . . . . . .Caused by: java.io.IOException: There is not enough space in the file system.
at java.io.FileOutputStream.write(FileOutputStream.java:342) ~[?:1.8.0]
at java.awt.Font.createFont0(Font.java:963) ~[?:1.8.0]
at java.awt.Font.createFont(Font.java:888) ~[?:1.8.0]
at net.sf.jasperreports.engine.fonts.SimpleFontFace.loadFont(SimpleFontFace.java:198) ~[jasperreports-6.7.0.jar:6.6.0]
This
may occur when temp space (/tmp) is full. To solve the issue review the Control Center Engine log
and clean up /tmp
directory, recycle Control Center, and rerun the reports.