Versions Compared

Old Version 16

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version Current

changes.mady.by.user Nadja Pollard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Support file creation using new Admin Point GUI creates invalid archive [PRECISE-19035]

  • Precise for Oracle - Current Tab Locks data does not show up [PRECISE-19046]

  • psdn_ba_WIN.zip is considered potential malware [PRECISE-19053]

  • Incorrect oracle container name is being displayed in Application dashboard and Activity tab for Oracle 12.2.0.1.0. [PRECISE-19055]

  • Running the manual schema script is asking for additional parameter in Precise FW installation with manual schema creation. [PRECISE-19057]

  • Oracle event mapping change [PRECISE-19065]

  • Some of the required files for listener/instance installation in HP UX machine are missing in Precise 9.9.0 build. [PRECISE-19069]Precise Manual Schema Installation Error. [PRECISE-18985]

  • Precise for Oracle - Container name captured as NA when container number is not continuous on a monitored instance. [PRECISE-19044]

  • AIX OS agent fails due to missing binaries. [PRECISE-19045]

  • Load Processes showing GMT time on new Admin Point GUI. [PRECISE-19036]

  • Running the manual schema script is asking for additional parameter in Precise FW installation with manual schema creation. [PRECISE-19057]

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 warehouse processes (Under Adminpoint -> Warehouse Processes). In such cases, a restart of the Oracle 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

  • Some of the binaries from the Precise 10.0.0 installer show 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.

  • There are several known issues and limitations in the new Precise GUI which have been documented in Precise new user interface.

...