WARN: Row Overflow in collection [CollectionName] maxRows NNNN (4294976)

When collecting data from database instances using Foglight cartridges (Oracle, SQL Server, DB2, etc.), you may encounter a warning message such as:

YYYY-MM-DD HH:MM:SS.SSS WARN [Thread-Name] com.quest.qsi.fason.core.collection.reader.JdbcReader - 
Row Overflow in collection [CollectionName] maxRows NNNN
    

This warning indicates that the number of rows returned by the SQL query for the specified collection has exceeded the configured maxRows limit (in this example, NNNN). Only the first NNNN rows are being processed; additional rows are ignored.

Each Foglight database cartridge collection has a configurable maximum number of rows (colMaxRows) that can be processed per collection execution. If a collection’s SQL query returns more rows than this limit, the JDBC reader will only process up to maxRows rows, and this warning is logged.

For example, if your database contains more records than the colMaxRows setting for a given collection, you will see this warning and only the first NNNN rows for that collection will be collected.

Resolution 1

1. Restart the database agent, then view the agent log file to review the current maxrows settings for each database collection. 
   • The log file section will look like the following (the key fields have been highlighted below)
         colDisplayName=Datafile Storage
         colName=DBO_DatafilesStorage
         colMaxRows=5000
         colEnable=1
         colTimeout=300
         colDescription=A list of all datafiles and their overall properties and storage detailed
         colFrequencyHigh=900
         colFrequencyLow=3600
         colFrequencyFast=900 
2. Download and review the attached scripts:
   • Download the script from the Attachments section of this article. You must be logged into Supportlink to access the script downloads.
3. Customize the script:
   • Open the script in a text editor.
   • Set the desired maxRows value.
   • Specify the collection names to update (if applicable).
   • Replace the agent name with the actual name of your agent.
   • (For global/bulk update scripts) Optionally, adjust the script to update all collections or all agents of a certain type.
4. Apply the script using the Foglight Script Console:
   • Go to Administration > Tool > Script Console in the Foglight Web Console.
   • Click Add, copy and paste the script into the text block, and click Run.
   • Review the output to confirm the changes were applied.
5. Restart the agent to ensure the new configuration is recognized.

DISCLAIMER:
The information in the script provided is known to work successfully; however, it has not been officially tested by Quest Quality Control. If any of these instructions are changed and/or incorrectly used, intentionally or unintentionally, this solution becomes unsupported by Quest Support and Development.
Quest Support and Development recommend always making a backup of the current Foglight installation and database prior to execution of any scripts that may modify it.

Performance Note:
Please note that increasing the maxRows beyond the default (e.g., 1000) is possible; however, it can have a detrimental effect on the performance of monitored hosts, FglAM, and FMS due to the increased amount of data collected. Increasing the amount of data collected may necessitate additional hardware resources.

agmMaxRowsToSubmit:

Please review knowledgebase article 4379932 to review and possibly increase the agmMaxRowsToSubmit value. This is a global maximum rows limit defined in Oracle, MySQL PI, PostgreSQL PI, DB2, and Azure SQL agents. This value must be higher than the highest value set of the maxrows among all of the collections.

Resolution 2

Enhancement ID FOGGENERAL-I-274 was logged to add the hidden maxRows values to the Agent Status Properties to be more easily adjusted by end users. This will be reviewed by Product Management and considered for future releases of the database cartridges.