Introduction to Precise 9.8.0
Introducing Precise 9.8.0
Precise 9.8.0 is a complete Precise version, which includes and provides enhancements and fixes for Precise 9.7.0. This document describes the new features introduced, the technologies supported and de-supported, and the issues resolved by version 9.8.0.
Installing Precise 9.8.0
Precise 9.8.0 can be installed in the following ways, depending on the currently-installed Precise version:
- If this is the first time you are installing Precise, install Precise 9.8.0 as described in Clean installation of the Precise Framework.
- If Precise 9.7.0 is currently installed, upgrade directly to version 9.8.0 as described in Upgrading Precise.
New Features and Enhancements for Precise 9.8.0
In Precise 9.8.0, support is added for the following technologies and components:
- Support for the Precise framework on:
- Windows Server 2016
- AIX 7.2
- Support for monitoring:
- Oracle 12.2.0.1 on Linux and Solaris
- DB2 10.5 on AIX
- DB2 11.0
In Precise 9.8.0, the following new features and enhancements are added:
- Multiple enhancements are made for monitoring Oracle 12c R2 containerized databases. For more information, see Containerized Database Support.
- Additional wait events are incorporated in Precise for SQL Server monitoring.
- Added the ability to reduce privileges for Precise for the Oracle PMDB user after installation. See the following solution for details: https://idera.secure.force.com/precise/5010b000000XwCf?srPos=0&srKp=501
Resolved Issues
| Issue # | Description |
|---|---|
| PRECISE-18942 | Issue when using email option in Custom Portal (ASD) |
| PRECISE-18887 | Oracle "SQL*Net message from dblink" event categorized incorrectly in Precise for Oracle |
| PRECISE-18797 | For Oracle 12c Monitoring on 9.6.4 and later, wrong values are shown in the OWNER Column in Objects Tab |
| PRECISE-18938 | Precise for Oracle installation: verify_user script fails with ora-12547 |
| PRECISE-18910 | Incorrect version number in installer |
| PRECISE-18744 | While entering the thresholds for customized alerts, precise GUI asked to save several times the thresholds, and Near-Critical Threshold value is saved in the Include and Exclude list which is greyed out. |
| PRECISE-18881 | Custom reports not showing query text longer than 4000 characters |
| PRECISE-18933 | Lock tree in Current tab gets displayed after sometime |
| PRECISE-18721 | ArrayIndexOutOfBounds error while instrumenting RMI calls in Weblogic V12 |
| PRECISE-18939 | createalertsmib.bat gives class not found error, fails to generate mib file |
| PRECISE-18879 | Registry edit of pools.xml for proxy node in case of federated nodes causes corruption has been successfully created |
| PRECISE-18944 | Fix to avoid the case when there are multiple DB2 versions in SYSIBM.SYSVERSIONS table. This happens in an upgraded DB2 environment |
| PRECISE-18947 | Tuxedo installer advanced window led to unhandled exception. And the checkboxes would reset on each new advanced window |
Known Issues
- The Precise focal point needs to be restarted after an upgrade if using remote instances. This would also need starting of the SQL agents after the focal point restart.
- When an Oracle monitoring instance is created immediately after framework installation, errors are sometimes seen in Oracle/SQL Server warehouse processes (Under Adminpoint -> Warehouse Processes). In such cases, a restart of the Oracle/SQL Server focal point and PMDB focal point fixes the problems.
- After a fresh install or upgrade, it is required to restart the Precise GUI service before using the Custom Portal.
- Issue with injdn.dll and injdn_x64.dll on Windows Server 2008 R2 with .NET monitoring. When a .NET instance is installed on Windows Server 2008 R2, a “Bad Image” error pops up. The problem can be resolved by installing a windows security update on the machine. The security update can be downloaded from https://technet.microsoft.com/en-us/library/security/3033929.aspx
- One of the binaries from the Precise 9.8.0 installer (psin_ba_WIN.exe) shows up as a threat under AVG antivirus. This is a false positive with AVG and does not cause any problems. It might have to be whitelisted when using AVG as antivirus.