We have been seeing an increasing number of alerts stating that OEM cannot ping an agent. These then generate alerts and incidents and potential callouts. The situation was getting increasingly worse and therefore we started some investigation as we had put it down to a busy network and the fact we have a lot of distributed agents.
The error message is Message=Agent is unable to communicate with the OMS. (REASON = Agent is Unreachable (REASON : Agent to OMS Communication is broken ). Severity=Unreachable Start
How To Install An Additional Management Service
This document will describe how to install an additional management service for Oracle Enterprise Manager Grid Control 10.2.0.5 on HP-UX. It was written by my colleague Carl Holmes.
You must first install the base release of Enterprise Manager (10.2.0.3) and patch it to 10.2.0.5
The recommended installation method is to install the software, patch it to 10.2.0.5 and then configure Enterprise Manager.
To do this, use these installer commands
I wish I knew is the short answer.
We are using a 3rd party tool which was ported from elsewhere to run on Oracle (probably SQLServer). Consequently there are a lot of column names that are Oracle resererved words and have to be double quoted in all the queries and reports that are written for it. This is a change/config/incident management product so as you can imagine there are a lot of reports /views in place and they are growing by the week.
The UKOUG Conference to be held in Birmingham (5th – 7th December 2011 ) is looking for presentations on: real life business experiences; in depth product analysis, new product overviews and everything else in between.
New for 2011: in order to enhance the agenda there are new topic listings, so to get familiar with what to submit your presentation under click here.
The reporting capabilities of OEM are very good, although sometimes it is hard to find which views the data you want is held in. This post is about sharing how to build a report which details how many databases are at each PSU patch. It will also show how to schedule a repeating report and save [...]
Firstly the background. I had a very large tablespace (3Tb with only about 20% used) so I re-organised all the objects, which all belonged to one schema for which this was the default tablespace, into a new tablespace, dropped the original which was now empty and renamed the new tablespace to become the old tablespace. alter tablespace MIS_ODS1 [...]
Problem Statement: rdbms version 220.127.116.11 – HPUX When partitions in a table have been explicitly locked, “lock_table_stats” and “unlock table_stats” do not override this behaviour. Question To Answer: Is what we are seeing expected behaviour/documented? I have a table (t1). It has two partitions (p1 and p2). I lock the statistics on p1 using dbms_stats.lock_partition_stats. I lock [...]
I have already posted about an issue that required me to drop and recreate standby log files so I thought I would post the scripts I used. Resize Standby Redo Logs 1. On primary defer log shipping (dynamic change) alter system set log_archive_dest_state_2 = defer scope = memory; 2. On standby database cancel managed recovery alter database [...]
When we have a situation where the standby redo logs on the standby database are not the same size as the online redo logs on the primary database, there is a strange redo log switching behaviour on the primary database. The primary continually switched online redo logs every 2 minutes no matter how little activity [...]
It is very easy to forget to resize the redo logs on standby after increasing the size on primary. These notes provide all the commands you need to quickly and easily resize the logs on standby Resize Standby Redo Logs On primary defer log shipping (dynamic change) alter system set log_archive_dest_state_2 = defer scope = memory; [...]