When running database collections in any of the following types of cartridges
Users may encounter warning messages similar to:
WARN [AGENTNAME-lowPriorityPool-3-[DBO_DatafilesStorage][DATETIME]]
com.quest.qsi.fason.core.collection.processor.AbstractQueryProcessor -
Numbers of submitted rows [1000] have exceeded the configured limit [1000] for processor [DBODataFileProcessor],
collection [DBO_DatafilesStorage]. Submitting the first [1000] rows.
These messages indicate that the number of rows collected for a specific processor or collection has reached a maximum limit, and only the first 1000 rows are being processed. This may affect collections with many rows of output such as DBO_DatafilesStorage, DBO_Datafile_IO_Activity, or DBO_TablespacesStorage.
This warning is generated because the global parameter agmMaxRowsToSubmit is set to a value (e.g., 1000) that restricts the number of rows submitted per collection, regardless of the collection’s individual colMaxRows setting (which may be higher, such as 5000). When the number of rows returned by a query exceeds agmMaxRowsToSubmit, only the first 1000 rows are submitted, and the rest are ignored.
For example:
agmMaxRowsToSubmit=1000
colMaxRows=5000
In this case, the effective limit is 1000 rows, due to the global parameter.
agmMaxRowsToSubmit: agentName variable in line 3 to your target agent's name.agmMaxRowsToSubmit for the specified agent.agmMaxRowsToSubmit if necessary: agmMaxRowsToSubmit for your agent. You must be logged into Supportlink to access and download the script. agentName variable on line 4 to your target agent's name.agmMaxRowsToSubmit value in the script on line 9 to the desired row limit (e.g., 5000, 10000, 50000, etc.).agmMaxRowsToSubmit: Note: The lower value between agmMaxRowsToSubmit and colMaxRows will always take precedence.
Supportlink Access: You must be logged in to Supportlink to download the provided scripts.