11g OEM with LogMiner Oracle 11g New Features Tips by Donald BurlesonJune 28, 2015

Oracle 11g New Features Tips

LogMiner has also continually been an important tool in the DBA arsenal for some time.  However, due to the lack of a more simple interface, this tool was often overlooked.  Previously, to avoid complications, DBAs would use a standalone interface for LogMiner, which even Oracle noted as ?cumbersome to install?. 

This new feature of 11g OEM provides an integrated interface for the DBA to use for LogMiner.  The graphical interface allows the DBA to extract transactions from the redo logs to examine and flashback a transaction if desired.  The LogMiner interface in OEM provides DBAs with an intuitive, easy to use tool for several purposes:

• To isolate transactions by time or SCN

• To isolate transactions by table or database user

• The advanced option for further filtering transactions

• To establish the appropriate steps needed for the recovery of unintentional changes, including dependent transactions

To access LogMiner, first click the Availability tab, then View and Manage Transactions, as shown in Figure 4.3.

Figure 4.3 Accessing LogMiner

Next, is the LogMiner interface, as shown in Figure 4.4.

Figure 4.4 LogMiner interface

Advanced Replication Interface

To assist with the setup and management of replication environments, the Advanced Replication interface in Oracle Enterprise Manager can now be used.  In previous releases, Advanced Replication was a trigger-based process of replication.  With 11g, this feature is now built-in to Enterprise Manager Database Control.  Figure 4.5 shows this Advanced Replication interface, which allows replications to be managed from within OEM.

Figure 4.5 Advanced Replication interface

Wait Activity Detail Enhancement

In previous versions, such as in OEM 10g, Oracle Enterprise Manager displayed the Wait Activity Drilldown detail in chart format as shown in Figure 4.6:

Figure 4.6 Chart format of the Wait Activity Drilldown detail

The best way to identify constraints and bottlenecks within the database is to analyze wait events.  11g OEM offers this ability to the DBA with less effort.  OEM 11g provides more detail for Wait Activity information. such as the enhanced drilldown detail, and ability to quickly select the Wait Class, as shown in Figure 4.7.

Figure 4.7 Wait Activity information page