Loading...

Knowledge Center


Database Activity Monitoring 5.2.x Known Issues
Technical Articles ID:   KB87368
Last Modified:  4/7/2017
Rated:


Environment

McAfee Database Activity Monitoring (DAM) 5.2.x

Summary

This article contains important information about known issues of high or medium rating that are outstanding with this product release. This article will be updated if new issues are identified post-release, or if additional information becomes available. To read the Release Notes, see: 
 
Release Notes Version Release to World (RTW)
PD26904 Database Activity Monitoring 5.2.2 February 7, 2017
PD26640  Database Activity Monitoring 5.2.0 June 29, 2016
NOTE: There was no public release of version 5.2.1.
 
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, visit the Product Downloads site at http://www.mcafee.com/us/downloads/downloads.aspx.


Known Issues

CRITICAL: There are no critical issues at this time.

Non-critical:
Reference Number Related Article Issue Description
   

Minimum requirement update

  • Windows 8 and Windows Server 2012 are supported as of McAfee Agent (MA) 4.8.0 Patch 1 and later.
  • Sensor on AIX requires MA 4.8 Patch 2.
1086251   Issue: Access objects are not collected from Teradata databases on select statements for lob data types (clob, blob).
962282  

Issue: Quick search does not include enum columns. The enum columns are:

  • Severity
  • Exceed row count
  • EXCESSIVE
1128093   Issue: The Sensor fails to attach to Oracle 12, with the following error:
 
ERROR Couldn't find enough FFs in the shared memory
 
Resolution: 
Install Sensor build 17794 or later.
925606  

Issue: The following MA issue affects DAM: If a McAfee product attempts to send more than 10 MB of data via the agent data channel, the agent sends an invalid package to ePolicy Orchestrator (ePO). When this occurs, ePO logs the following message:

Failed to parse input buffer, possible bad format.

Resolution: Install MA 4.8.0 Patch 2 Hotfix HF943449, which is available only by contacting Technical Support. For contact details, see the Related Information section of this article.
1104333   Issue: Sensor installation on AIX is not supported for non-default locations. 
   
Issue: When you set up a connection to DB2 on HP-UX, the connection fails if the database uses the default character set. This is a known IBM issue. 

Workaround: The following workaround is offered and verified by IBM:

HP-UX servers: The IBM DB2 Driver for JDBC and SQLJ does not support databases that are in the HP-UX default character set, Roman8. Therefore, when you create a database on an HP-UX server that you plan to access with the IBM DB2 Driver for JDBC and SQLJ, you must create the database with a different character set than Roman8.
    Issue: The Run Now functionality does not work for Sensors installed on Linux and UNIX systems. This is an issue with MA and is documented in the McAfee Agent Product Guide (PD25736).
    Issue: Sensor on AIX is not released yet. This is caused by an issue with MA.
    Issue: (HP-UX): MA does not report IP address.
Resolution: This issue is resolved in MA 4.8.0 Build 1659.
    Issue: DB2 z/OS (Tomium integration): New Session/End Session events display a time stamp according to when the event was received by the Sensor and not when initiated on the database.
This might cause confusion if clocks are not synchronized.
Resolution: Ensure the clock on the computer where the Sensor is installed is synchronized with the DB2 z/OS database clock.
   
Issue: (Upgrades only) The old database security dashboard does not display any databases and cannot be removed.
Resolution: The old dashboard is replaced with a new default dashboard.
   
Issue: (Upgrades only) Previously created custom queries may be deleted because of a combination and modification of Result Types.
Resolution: Create new queries according to the new and improved Result Types.
   
Issue: Failed Login monitoring on Oracle 12.1.0.2 is not supported via memory monitoring.
Resolution: Failed Login can be monitored by enabling Network Monitoring.
 

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms


 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.