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:
| Product Version |
General Availability (GA) |
Release Notes |
| Database Activity Monitoring 5.2.2 |
February 7, 2017 |
Release Notes |
| Database Activity Monitoring 5.2.0 |
June 29, 2016 |
Release Notes |
NOTE: There was no public release of version 5.2.1.
NOTE: DAM 5.2.x is in the End of Life (EOL) cycle. We recommend that you upgrade to the latest available 4.8.x version.
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,
go to the Product Downloads site.
| 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 Enterprise product tries to send more than 10 MB of data via the agent data channel, the agent sends an invalid package to ePolicy Orchestrator (ePO). When the agent sends the invalid package, ePO logs the following message:
Failed to parse input buffer, possible bad format.
Resolution: Install MA 4.8.0 Update 3.
|
| 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 issue is a known IBM issue.
Workaround: IBM has verified and offers the following workaround:
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. So, 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 issue is with MA and is documented in the McAfee Agent Product Guide.
|
| |
|
Issue: Sensor on AIX is not released yet. The reason is 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 Sensor received the event and not when the event initiated on the database. This fact might cause confusion if clocks are not synchronized.
Resolution: Make sure 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 can't be removed.
Resolution: The old dashboard is replaced with a new default dashboard.
|
| |
|
Issue: (Upgrades only) Previously created custom queries might 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.
|
