oem

SQL Tuning Advisor - what profile am I accepting?

Submitted by dave on Thu, 10/13/2011 - 13:35

When working on a SQL Tuning issue I often kick off a SQL Tuning Advisor job on the SQL while I gather info about statistics and other things I like to check when tuning. After I get an idea of where performance might be suffering I use the SQL Tuning Advisor results for a second opion. Unfortunately more often than not the SQL Tuning Advisor reports it can dramatically improve the performance of a SQL Statement by using a SQL Profile to force a different plan.

[node:read-more:link]

Tags:

sql

oem

tuning

"There was a problem creating a SQL tuning task. ORA-13780: SQL statement does not exist. ORA-06512"

Submitted by dave on Tue, 07/26/2011 - 14:30

I recently got this error while trying to run a SQL Tuning Task against a SQL statement that was available in AWR but not currently in the library cache.

I got around it by locating the SQL in OEM and using SQL Worksheet to execute it:

[node:read-more:link]

Tags:

sql

oem

tuning

Recording User Defined Metrics in Oracle Enterprise Manager OEM

Submitted by dave on Wed, 07/21/2010 - 15:52

Did you know that OEM has a built in interface for executing simple ad-hoc queries and recording the results? Here is how I set up a recurring query to find the number of user logins every 15 minutes and record the data. 1) Navigate to a database instance in OEM
2) Select the Related Links -> User Defined Metrics link from the bottom of the Database Instance Home tab.
3) Select the Create button to create a new User Defined Metric a. Enter the Metric Name

[node:read-more:link]

Tags:

oem

Oracle Enterprise Manager

oracle.sysman.emSDK.emd.comm.OperationException: could not write to targets.xml.bak file

Submitted by dave on Mon, 01/26/2009 - 15:19

I had some trouble adding a new database to an OEM Grid installation this weekend.

I didn't find too many references to the above error so I wanted to post about it here. Of course Metalink was all doom and gloom. Note 745795.1 says to stop the agent, run fsck on the AGENT_HOME filesystem, then start the agent. After that you should be able to add new targets.

targets.xml lives in AGENT_HOME/sysman/emd. At the OS prompt I changed to that directory I was able to create new files there but for some reason the above error kept popping up when Grid tried to save a new target.

[node:read-more:link]

Tags:

oracle

oem

grid