Troubleshooting ReportCaster Log Reports

If you do not receive a log report because there is an insufficient amount of memory available, this may be because the report is too large or you have too many windows open. Information Builders recommends closing all widows and attempting to run the log report again. If you are still unsuccessful, consider the following troubleshooting steps.

Top of page

Procedure: How to Troubleshoot ReportCaster Log Reports

Rerun a schedule that successfully created a log report. If you are successful in running the log report, this confirms that the original log report that did not run was too large to be processed. Proceed to step 2.
Note: To complete the following steps, you must be a ReportCaster Administrator.

Set the Log Purge Period setting in the ReportCaster Server Configuration tool to the minimum number of days that the log reports are needed. Although the default is 30 days, you may not need to retain the log file for such a long period of time.
Set the Log Purge Time setting in the ReportCaster Server Configuration tool to the time you want to purge the log file. By default, log purging occurs at 1:00 A.M.

You should verify that your ReportCaster Distribution Server is running at the time of the log purging. You can review the log information for the 'system' ID to confirm log purge processing results.

For more information about the Log Purge Period and Log Purge Time settings, see ReportCaster Server Configuration.

Note: Library expiration purging occurs one hour after the Log Purge Time. By default, library purging occures at 2:00 A.M. each day. Be aware that log and library purging may overlap depending on the number of log reports you are purging.
If you are using a FOCUS Repository, verify the organization and size of the repository. You may need to rebuild or reorganize the BOTLOG and BOTLOG2 repository tables. For more information, see Maintenance Functions for a FOCUS Repository.
Verify the memory (heap size) available for the Java Virtual Machine (JVM) on the Application Server. The size of ReportCaster log reports is limited by the amount of memory available to the JVM. When the memory of the JVM is exceeded, an OutOfMemoryException message occurs. In such a case, you may want to increase the amount of JVM memory configured. To verify the amount of JVM memory configured, see your Web server servlet configuration.
If the Distribution Server experiences a Java out of memory error, you must increase the amount of memory (heap size) available to Java on the Distribution Server. You can do this through a command line entry or using the Registry Editor, depending on how you started the Distribution Server.

To change the heap size using the command line, use one of the following:
- Pass the heap size parameters on the Java command line, as follows:
```
java -Xms<initial
heap size> -Xmx<maximum heap size>
```
  For example,
```
java -Xms256m -Xmx512m
```
- If the Distribution Server is running from the command line, then edit the schbkr file located in the ReportCaster bin directory.
If the Distribution Server is running as a service on Windows, then use the Registry Editor to change the value of the JAVAOPTIONS registry key.

Restart the Distribution Server to enable the change.