Oracle Enterprise Manager Plug-In for PostgreSQL Product Overview

The Oracle Enterprise Manager Plug-in for PostgreSQL expands Oracle EM13c’s native database management capabilities to the popular PostgreSQL database platform.

Product features include:

  • Native EM13c thresholds and incidents for common PostgreSQL problems
  • Visibility into PostgreSQL high availability via replication monitoring
  • Details in the health, size, usage, and activity of and within tables, indices, triggers, prepared transactions, and sequences
  • Configuration settings of the PostgreSQL server both now and after next reboot

Product Version Information

VersionRelease DateDescription
April 29, 2019
  • Enterprise Manager 13.3 support
  • PostgreSQL 11 support
  • New HTML/JavaScript user interface
  • Threshold configurations for more metrics
  • Individual collection schedules for each metric group
  • Security updates 11, 2018
  • Added licensing
  • Added support for PostgreSQL 10 8, 2017
  • Added support for PostgreSQL hosted on Amazon RDS
  • Added support for PostgreSQL versions 9.5 & 9.6
  • Deprecated support for PostgreSQL versions 9.0 – 9.2
  • Added the ability to set thresholds for Database, Table, and Index Size
    columns in Megabytes (MB) rather than Bytes (B) 2016Verified compatibility for EM13c 2015Initial release for EM12c

Applicable Platforms

Notable Features

The version of the OEM Plug-in for PostgreSQL now supports licensing as well as configuration against version 10 of PostgreSQL databases.

Installation Prerequisites & Instructions

Known Issues/Limitations

  • When upgrading from version (or earlier) of the plug-in, thresholds cannot be set for the new Database, Table, and Index Size (MB) columns for existing targets. To correct this limitation, we recommend creating a new target, or using the pre-existing Size column thresholds (which are measured in Bytes rather than Megabytes).
  • Query and tablespace data currently is not returned for PostgreSQL read-only users. Assigning a user/role the “super user” attribute will correct this limitation