DSAuditor 4.6 ReadMe

Welcome to DSAuditor Version 4.6.8

DSAuditor Home | DSAuditor Documentation | Embarcadero Technical Support | www.embarcadero.com

Thank you for using Embarcadero DSAuditor, the award-winning product that provides real-time and historical insight into who is using your data, when, and from where. Before you use DSAuditor, please read the information below.

What's New in Version 4.6

Release Theme: Web Client Hardening and Encrypted Session Monitoring

Web Client: Performance, Reliability and Scalability Improvements

Windows Collector: Support for Encrypted Network Sessions

Data Capture Enhancements

Database Upgrades

Operating System Upgrades

Release Notes

Important Advisory Notes (read before upgrading DSAuditor on UNIX)

Known Issues

Bug Fixes

Embarcadero Technologies Web Resources

Licensing Your Embarcadero Product

Embarcadero Technologies Product Support

Embarcadero Technologies Technical Support

Embarcadero Technologies on the Web

What's New in Version 4.6

Web Client: Performance, Reliability and Scalability Improvements

The Web client now generates reports faster and handles very large reports more gracefully. The installation process has also been improved. Numerous smaller improvements are included as well. (These changes were actually released early, in the V4.5.5 build.)

Windows Collector: Support for Encrypted Network Sessions

The DSAuditor Collector for Windows can now monitor encrypted network sessions. While this enhancement was required to fully support SQL Server 2005, it also extends to SQL Server 2000 installations having encryption enabled.

Data Capture Enhancements

The site-definable query_band field has been expanded to 255 characters (formerly 32).

The query_return_code is now available in Activity Tracker (as in Usage Tracker).

New options are available for controlling the persistence of embedded SQL overrides. See the DSAuditor Technical Reference for details.

Additional enhancements added in version 4.6.5:

Handle unusual bursts in network traffic more gracefully
Accommodate VLAN tags in ethernet headers.
On AIX systems, better packet capture and a reduction in memory and CPU overhead.

Database Upgrades

DSAuditor Collector for Windows now supports SQL Server 2005 as a monitored database (it was already supported as a repository).

All components now support Oracle 11gR1.

DSAuditor version 4.6.3 adds support for monitoring Informix 11.5.

DSAuditor version 4.6.5 adds support for PostgreSQL as a repository (Linux only).

DSAuditor version 4.6.6 adds limited support for monitoring SQL Server 2008 (excludes named pipes sessions on Windows Server 2008).

Operating System Upgrades

DSAuditor Collector for Windows now supports 64-bit Windows systems.

DSAuditor Server now supports SUSE Linux 9 in addition to 10.

DSAuditor Server now supports Red Hat Enterprise Linux 5 in addition to 3 & 4.

DSAuditor version 4.6.0 drops support for Solaris 7.

DSAuditor version 4.6.2 drops support for AIX 5.2.

Release Notes

Important Advisory Notes

Upgrade sequence:

The 4.6 Collectors and SQL Traps are not compatible with 4.5 Dispatchers. For existing installations that are running the Dispatchers on a separate machine from the Collectors or SQL Traps, the Dispatcher installation should be upgraded to 4.6 before upgrading the Collectors or SQL Traps.
The 4.6 Activity Tracker Server is not compatible with 4.5 Activity Tracker Clients. The Activity Tracker Client should be upgraded before upgrading the Activity Tracker Server (which is part of the core server kit).
In summary, the correct upgrade sequence is: 1) Upgrade clients, 2) Upgrade core server components, 3) Upgrade remote Collectors & Traps, if any.

To upgrade DSAuditor Server for UNIX to 4.6 on a system already running the DSAuditor Management Console, do the following:

Download the DSAuditor Server kit for your platform (dsauditor_multikit_<platform>_<version>.tar) from embarcadero.com to /tmp (or other location having at least 200MB free space) on the system running DSAuditor Server for UNIX.
The remaining steps are performed using DSAuditor's browser-based Management Console. If you are working locally on the system, open a supported Web browser (Firefox 2.x or Microsoft Internet Explorer 6.x or later) and browse to http://localhost:2780. If you are working on another computer, replace localhost with the IP address or network name of the system running DSAuditor Server for UNIX.
If the browser cannot display the webpage, but you know the DSAuditor Management Console has been installed, it may have been configured for single-session mode. If so, you will need to start the console manually from the root account before each browser session (/usr/local/sbin/dsauditor/bin/rc.shttpd start).
When prompted, enter the username and password you have previously applied to the console (the default values were Admin/Admin). Then click OK to log in.
If you have logged into the Admin account, you should update the console before updating the core software.

Click Manage this console.
Click Update admin software, then click Next. (This update option only appears for the Admin account.)
You should see the multikit you just downloaded; if not, you may need to move it to another location. The console will search the location originally used for installation, and also the root directories of any DSAuditor instances you have subsequently defined.
Click Unpack unless you already unpacked the multikit at the UNIX command prompt.
Click Install > Install. Installation may take a few minutes. If your browser has trouble reconnecting, refreshing the page may help.
Click Done > Done.

Click Manage software instances.
If your software instance is not already defined:

Click New instance. This is to create a new definition for your existing DSAuditor installation.
Enter a name for your existing DSAuditor instance and the corresponding DSAuditor user name and other requested info, then click Next > Finish. Choose a user whose home directory is on a local drive; DSAuditor will not work correctly on an NFS mount.

When the Manage software instances page appears, click Install > Next > Install. Installation may take a few minutes. When the Manage software instances page reappears, the upgrade is complete.

To upgrade (or install) DSAuditor Server for UNIX to 4.6 on a system not yet running the DSAuditor Management Console, do the following:

Download the DSAuditor Server kit for your platform (dsauditor_multikit_<platform>_<version>.tar) from embarcadero.com to /tmp (or other location having at least 200MB free space) on the system running DSAuditor Server for UNIX.
Open a terminal session under the root account. This is only required once; root privileges are necessary to set up boot-time startup links and file ownership and protection bits. This is mandatory for proper functioning of the software. Future upgrades will not require logging into a root account.
Change to the directory containing the multikit.
Extract the contents of the multikit (tar �xvf dsauditor_multikit_<platform>_<version>.tar). This will extract two kit files and an installation script into the current folder.
Execute the extracted installation script (./install.sh) under the root account. This will install the DSAuditor Management Console.
- The console is used to install, monitor and manage the core DSAuditor software.
- It also includes role-based security, which separates administration of the console from administration of the core DSAuditor software.
- Additionally, the console can either be available at all times or can be switched to single-session mode after installation to require human intervention before each use.
- For more information, see the DSAuditor Installation Guide.
The remaining steps are performed using DSAuditor's browser-based Management Console. If you are working locally on the system, open a supported Web browser (Firefox 2.x or Microsoft Internet Explorer 6.x or later) and browse to http://localhost:2780. If you are working on another computer, replace localhost with the IP address or network name of the system running DSAuditor Server for UNIX.
When prompted, enter Admin (with a capital A) as the user name and password, then click OK to log in.
Click Manage software instances.
Click New instance. This is to create a new definition for your new or existing DSAuditor installation.
Enter a name for your new or existing DSAuditor instance and the corresponding DSAuditor user name and other requested info, then click Next > Finish. Choose a user whose home directory is on a local drive; DSAuditor will not work correctly on an NFS mount.
When the Manage software instances page appears, click Install > Next > Install. Installation may take a few minutes. When the Manage software instances page reappears, the upgrade is complete.

DSAuditor Collector for Windows:
- To capture encrypted network activity for SQL Server, the Windows Server hosting the database must use a provisioned certificate for encryption rather than a self-signed certificate. For more information, see the DSAuditor Installation Guide.
- Complete instructions for provisioning a server certificate can be found at msdn.microsoft.com/en-us/library/ms191192
- In a SQL Server Cluster, the provisioned server certificate must be created with the fully qualified DNS name of the virtual server.
- In a SQL Server Cluster, the Connection Node Name must be set to the cluster�s logical server name.
- To collect Oracle data, you must either set the Oracle parameter USE_SHARED_SOCKET = TRUE or configure Oracle Shared Server Dispatchers to use a specified range of port numbers. For more information, see Oracle's documentation.
Current version numbers:

DSAuditor Server (UNIX & Linux): 4.6.8
DSAuditor Server (Appliance): 4.6.8
DSAuditor Collector for Windows: 4.6.8
DSAuditor Activity Tracker client: 4.6.6
DSAuditor Usage Tracker client: 4.6.8
DSAuditor GEM client: 4.6.2
DSAuditor Web client: 4.6.3

Known Issues

DSAuditor Collector for Unix: The Solaris version collects only remote traffic, not local traffic. This is a limitation in the Solaris operating system which may be removed in a future Solaris version. To work around this limitation, configure a SQLTrap as described in the DSAuditor Technical Reference.
DSAuditor Collector for Windows:
- The current release can be configured to collect either SQL Server or Oracle data, but not both concurrently.
- To capture all database sessions on Windows Server 2008, you should disable the "named pipes" protocol in the SQL Server Configuration Manager. This release does not capture named pipes sessions on Windows Server 2008. (Named pipes sessions are still captured on earlier Windows versions.)
DSAuditor Collector for Linux: Some sites may receive an error message indicating that libstdc++.so can't be loaded. To fix this, copy file libstdc++.so.5 from $PINECONE/lib to /usr/lib.
DSAuditor on SELinux: The current release of DSAuditor is not compatible with SELinux running in enforcing mode. To work around this, SELinux can be run in permissive mode.

Bug Fixes

Bugs Fixed in Version 4.6.0
Bug #	Description
DSC-724	STIReader: Handle quoted incomplete comments in stored procedures
DSC 726	STIReader: Handle function names that start with a single quote that caused instances of TDS error 102 for the STIWriter on Sybase & SQL Server
DSC-736	Parser: Strip brackets from table and column names in SQL Server
	SQLHandler on Linux: Properly format IP addresses containing zero octets
	UT Client: Handle selection filter text containing the "=" character
Bugs Fixed in Version 4.6.1
Bug #	Description
DSC-740	DBWriter: Support long port band fields in the .SQL files
	DBWriter: Trim reference data before it is stored to ensure that the parser can match column and table names
	DBWriter: Avoid truncating parameter (PRM) records that have commas in the text
	DBUpdater: Increase the size of the query_band fields in the summary tables.

Bugs Fixed in Version 4.6.2
Bug #	Description
	Parser: Handle deprecated TODAY(*) syntax for Sybase IQ, which led to invalid duplicate data for the QUERY_COLUMN_TBL.
	DBWriter: Avoid reprocessing .SQL files if they contain invalid duplicate data for the QUERY_COLUMN_TBL.
	DBUpdater: Make the QUERY_PROC_TBL keys/indexes for Sybase and SQL Server match the other database types.
	Management Console: Limit the default number of SQL handlers to no more than 16.
	Management Console: Avoid browser errors caused by a race condition in the use of temp files.
	SQLHarvester: When device=auto is specified, check for devices of the form nxge* on Solaris, and extend the device range from 9 to 19 for appropriate device classes.
	SQLHandler: Fix a bug that could lead to failsafe logs for Sybase IQ.
Bugs Fixed in Version 4.6.3
Bug #	Description
	DBWriter: Fix a bug writing data to the repository that was caused by single quotes in text fields.
	SQLHarvester: Report heap allocation failures on heavily loaded systems.
	Management Console: During reboots on HP-UX, ensure the PATH variable is always adequate for the startup script.
DSC-765	Management Console: Fix a bug introduced in 4.6.2 that allowed excess messages to be written to the shttpd.log file on some systems.
DSC-697	Management Console: During console installation on Solaris, also install the membuf driver.
	Web Client: Fix a problem connecting to some Sybase repositories.
	Windows Collector: Monitor traffic on dynamic ports and when multiple listener ports have been configured for SQL Server.
DSC-752	DBPing: Add support for Informix on Linux and for Sybase IQ on Solaris, HP-UX and AIX.
	STIReader: Add support for Informix on Linux.
	STIWriter: Improve the algorithm for matching STI files to monitored databases in the repository.
Bugs Fixed in Version 4.6.4
Bug #	Description
	SQLHandler: Account for additional Informix data stream variations.
	Parser: Allow configuration of quoted_identifier for Informix parsing; affects Dispatcher, STIReader, and DBWriter.
Bugs Fixed in Version 4.6.5
Bug #	Description
	Parser: Fix a memory leak in parsing of literals; affects Dispatcher, STIReader, and DBWriter. This is an important fix that affects all customers and should be installed ASAP.
	Parser: Fix a potential program fault when resolving aliases; affects Dispatcher, STIReader, and DBWriter.
	Windows Collector: Add a digital signature to the kernel driver to accommodate stricter security requirements in R2 of 64-bit Windows Server 2008.
	Windows Collector: Handle potential security exceptions when writing to the event log.
	SQLHandler: Fix some issues handling certain Informix data streams.
	Management Console: Fix a bug during core kit installation for instances having a symbolic link for the "pinecone" directory.
	AT Client: Fix a bug that prevented playback from working for "session" datasets.
Bugs Fixed in Version 4.6.6
Bug #	Description
	SQLHarvester: Fix bugs in VLAN tag recognition, which was a new feature added in 4.6.5.
	STIReader: Account for create procedure statements that include square brackets around the procedure name.
	AT Server: Fix a problem introduced in 4.06.00 preventing normal playback of "session" datasets.
	AT Client: Fix a bug affecting "NOT" operator functionality in boolean expression WHERE & HAVING clauses.
	Windows Collector: Avoid a crashing bug on Windows Server 2008 by disabling capture of named pipes database sessions (still enabled for earlier Windows versions, and will eventually be re-enabled for Windows Server 2008).
Bugs Fixed in Version 4.6.7
Bug #	Description
	STIReader: Account for larger column names.
Bugs Fixed in Version 4.6.8
Bug #	Description
	DBEraser: Reduce Teradata spool usage triggered by high-frequency queries.
	DBEraser: Lock Teradata tables for WRITE access to minimize DBWriter deadlocks.
	DBEraser: Retry deletion operations rather than exiting after deadlocks.
DSC-787	Dispatcher: Only honor comments in the exclude.txt file if the # is in the first column. This allows exclusions to be specified that include the # character such as INSERT INTO #TEMP *.
	SQLHarvester: Fix a race condition in fifo locks that could produce a deadlock.
DSC-798	Parser: Fix a bug in handling a larger number of "--" end-of-line comments; affects Dispatcher, STIReader, and DBWriter.
	Parser: Add a safety check on the recursive call depth; affects Dispatcher, STIReader, and DBWriter.
	STIReader: Recognize logical_db_node when defined in a monitoring rule.
	STIReader: Accommodate view definitions up to 128K in length. Note - Sybase users also need to set "text size = 131000" in freetds.conf to retrieve large view text (default is 64512).
DSC-674	Windows Collector: Avoid assigning incorrect "client node" for named pipes sessions not having an explicit client node.
DSC-797	Windows Collector: Improve user interface for specifying logical database node name.
DCC-340	UT Client: Filter and display db_instance in uppercase to fix filtering inconsistencies.

Additional Resources

Licensing Your Embarcadero Technologies Product

All Embarcadero Technologies products include a 14-day trial period. To continue using the product without interruption, we recommend that you license it as soon as possible. To license DSAuditor, contact sales@embarcadero.com, or uk.sales@embarcadero.com for sales in the EMEA region.

Embarcadero Technologies Product Support

The Embarcadero Technologies Web site is an excellent source for additional product information, including white papers, articles, discussion forums, and the Embarcadero Knowledge Base. Visit www.embarcadero.com/support, or click any of the links below, to find:

Embarcadero Technologies Technical Support

If you have a valid maintenance contract with Embarcadero Technologies, the Embarcadero Technical Support team is available to assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of Embarcadero Technologies products to download free software upgrades during the active contract period. Evaluators receive free technical support for the term of their evaluation (14 days).

We encourage you to open technical support cases via the Technical Support request form. For additional information about Embarcadero Technologies Technical Support, visit the Support section of our Web site.

Embarcadero Technologies on the Web

To download evaluations of other Embarcadero Technologies products or to learn more about our company and our products visit us at www.embarcadero.com.