| Reference Number |
Related Article |
Found in
Version |
Fixed in
Version |
Associated Products |
Issue Description |
| DBSEC-15861 |
- |
4.8.3 |
- |
DAM |
Issue: On AIX 7.2, the log "Got signal [4]" in dbs.log.std indicates that an invalid instruction is sent to the CPU. It's still unclear as to what instruction the Database Security Sensor is sending. All tested queries are observed to be reported as alerts throughout testing. |
| DBSEC-13592 |
- |
4.8.2 |
- |
|
Issue: The XML API that lists database groups by name in the Database Security server only returns one database group if there are multiple groups with the same name. |
| DBSEC-13559 |
- |
4.8.2 |
- |
|
Issue: In the Database Security Server, a custom database group created pre-v4.8.2 with the same name as a new system group introduced in v4.8.2 can't be deleted in v4.8.2 of the Database Security Server.
Workaround: To delete the custom group after upgrading the server to v4.8.2, rename the custom group to a unique name before you delete it. |
| DBSEC-9857 |
- |
4.7 and later |
4.8.3 |
DAM |
Issue: Local connections from the Oracle 19 client aren't monitored with Network Monitoring enabled.
Solution: Use memory monitoring. |
| 1258722 |
- |
4.6.6–5.2.6 |
- |
DAM |
Issue: Solaris SPARC and DB2 10.x.x.x – Some alert details are intermittently missing and display blank information for alert details for endUserName and endUserIp. |
| 1258168 |
- |
4.6.6–5.2.6 |
- |
DAM |
Issue: SQL2008 Sniffer – No alerts are reported and sensor restart is seen in logs. |
| 1200780 |
- |
4.6.3–5.2.3 |
- |
DAM |
Issue: Elements display random nonsensical characters. |
| 1248335 |
- |
4.6.5 |
- |
DAM, DVM |
Issue: The BETWEEN operator keyword doesn't function correctly on Oracle. |
| - |
- |
- |
- |
DAM, DVM |
Issue: Monitoring of Oracle 12.2 with Memory Monitoring isn't supported on HP-UX and AIX. |
| 1246067 |
- |
4.6.4 |
- |
DAM, DVM |
Issue: Monitoring of Oracle 12.2 with Network Monitoring technology (network sniffer) fails on supported operating system platforms and you see no alerts generated. In logfile.log_sniffer_parsers, you see the error below:
Got OUT OF SYNC in the protocol handshake process, session will be dropped
|
| - |
- |
- |
- |
DAM |
Issue: Installing the Sensor on HP-UX in a non-default location (using flag -R) is not supported. |
| 1269343 |
KB91450 |
4.6.6 |
As designed |
DAM, DVM |
Issue: Report generation fails for most of the formats after you upgrade to 4.6.6 Update 1 or later. This issue is as designed. |
| DBSEC-5138 |
- |
4.6.6, 4.7 |
- |
|
Issue: The osUSer element is missing in some circumstances on some platforms. |
| DBSEC-4987 |
- |
4.6.6, 4.7 |
- |
|
Issue: Change container alert isn't reported in some circumstances. |
| DBSEC-4259 |
- |
4.6.6, 4.7 |
- |
|
Issue: In some circumstances, the Select and Insert into statements are reported with incorrect bind variables. |
| DBSEC-5135 |
- |
4.6.6, 4.7 |
- |
|
Issue: The Rows element is missing in some circumstances. |
| DBSEC-5911 |
- |
4.7.1 |
- |
|
Issue: In MongoDB 3.0, find alerts aren't displayed correctly. |
| DBSEC-5471 |
- |
4.6.6, 4.7.1 |
- |
|
Issue: Teradata Common_sanity test fails on SUSE10 when tested on sensor build from GIT (using pcap 1.8.1). But, Teradata on SUSE11 passes on the said build. |
| DBSEC-5755 |
- |
4.7.1 |
4.8.0 |
|
Issue: MySQL jdbc installation help link doesn't work properly. |
