[NOTICE] parser get to the max number of loops on the same packet

Technical Articles ID: KB87426
Last Modified: 2022-09-26 05:02:47 Etc/GMT

Environment

Database Activity Monitoring 5.x, 4.x

Problem

You create a rule that defines a minimum number of rows before an alert is triggered. But when this threshold is met, the rule isn't triggered. The rule works as expected if a minimum row count isn't specified. You also see the following event in the sensor log logfile.log_sniffer_parsers:

[NOTICE] parser get to the max number of loops on the same packet, Session [SESSIONID] will be dropped (out of sync).

Cause

This condition is a known condition that can occur with tables that have many rows and columns to be parsed. For example, a table with 1024 rows and 100 columns.

Solution

You must configure the Sensor with an advanced parameter to properly count the number of rows returned. The needed parameter is shown below:

sniffer.parser_max_num_of_loop_on_same_packet=6

For larger tables, you must increase this value. Increase the value by 6–10 and then test the rule, repeating until the issue is resolved.

For more information, see KB83070 - How to add an advanced parameter to a Database Activity Monitoring sensor.

Affected Products

Languages:

This article is available in the following languages:

Knowledge Center

[NOTICE] parser get to the max number of loops on the same packet

Environment

Problem

Cause

Solution

Affected Products

Languages:

Title

Title

Knowledge Center

[NOTICE] parser get to the max number of loops on the same packet

Environment

Problem

Cause

Solution

Affected Products

Languages:

Choose your region

Title

Title