000032012 - Oracle database scan history shows less number of rows scanned than the actual count in RSA DLP 9.6

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000032012
Applies ToRSA Product Set: Data Loss Prevention (DLP)
RSA Version/Condition: 9.6 SP2, SP3
Platform: Oracle
IssueAfter running the oracle database scans the scan history shows the number of rows scanned less than the actual rows that existed in the table.
Steps to Reproduce
  1. Enable debugging for the sitecoordinator logs and run the oracle database scan.
  2. After the scan is completed, verify in the site coordinator logs the number rows that was read by the site coordinator and compare the number of rows read by the site coordinator with the scan details under the history tab in the Enterprise manager for that scan group.  You should see the number of rows scanned in the EM webpage ( in scan group ) less than the number of rows that was read by the site coordinator.

For example, the site coordinator shows in the logs below that it read 6463 rows from the database table.
9/28/2015 9:29 PM Debug-DBOra: Exit OracleAccess::ReadData. Completed reading row:6463
9/28/2015 9:29 PM Debug-DBOra: OracleAccess::ReadRowsStream. Bytes read to memory:22224
9/28/2015 9:29 PM Debug-DBOra: OracleAccess::ReadRowsStream. BytesrRead:22224, TotalBytesRead:22224, OutstandingBytes:2074928 and m_noofBytesToRead:0
9/28/2015 9:29 PM Debug-DBOra: OracleAccess::ReadRowsStream. Bytes read to memory:0

When we check the number of rows scanned in the Enterprise manager for the same scan, it shows only 6403.
 
ResolutionIf you are experiencing this issue, contact RSA Support and quote this article number to obtain a patch that corrects the functionality.
This issue has also been resolved in DLP 9.6 SP2 P4.

Attachments

    Outcomes