How to run Oracle ASH Report for Oracle performance Tuning
ASH Report or Active Session History report is a very useful tool available in Oracle 11g provided for Oracle Performance Tuning.
This report was introduced in Oracle 10gR2.
By running this you can get a report of your oracle database performance very quickly. The different sections in the report help to identify performance tuning related issues quickly.
This report is usually run when you need to tune a SQL or you want to investigate performance bottlenecks in your Oracle database.
The report can be run from Oracle Enterprise Manager Database Control or Grid Control (OEM). It can also be run from command line.
The steps below shows how to run the ASH report using OEM
1. Login to Oracle Enterprise Manager 11g Grid Control
2. Go to Targets and then from the menu below select All Targets.
3. Find the Database Instance where you want to run ASH report
4. Click on the database Instance Link. Now the Database instance page will be displayed.
5. Click on the tab called Performance
6. It should ask for username/password. If you want to can select to login as SYSDBA
7. When the performance Tab is displayed find the Run ASH Report link from top right corner on the screen and click on it.
8. Now Run Ash Report will be displayed
9. Here you select the date and time for the period you want to run the ASH report for. Select Date and Time.
10. There is no need to enter a value for SID but if you want you can enter if you want to run this for a particular SID.
11. Then click on the Generate Report button.
12. You will see a message saying that the report is now running. After a few seconds the report will be displayed.
The ASH report contains a wide range of information which is very useful for performance tuning. Basically based on the purpose of your running the ASH report you can directly go to relevant sections. For example if you are looking for tuning SQL performance then you can go directly to Top SQL section.
In Top SQL sections you can identify top five SQL statements which are

The first column shows the SQL IDs. Click on that link will display the actual statement that is being run.
The report also identified the following:
Top Events
Load Profile
Top SQL
Top PL/SQL
Top Java
Top Call Types
Top Sessions
Top Objects/Files/Latches
Activity Over Time
and much more
ORA-01882: timezone region not found error in Oracle Enterprise Manager 11g Grid Control
ORA-01882: timezone region not found is displayed when accessing “Response and Load” Graph for Weblogic Server Targets.
I get the this when I try to access Oracle WebLogic Server from Oracle Enterprise Manager 11g Grid Control and then try to
access ADMINSERVER graphs.
The …/Middleware/gc_inst/em/EMGC_OMS1/sysman/log/emoms.trc file show the error as
java.sql.SQLDataException: ORA-01882: timezone region not found
ORA-06512: at “SYSMAN.MGMT_GLOBAL”, line 8at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:79)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1035)
fter looking on the internet and Oracle metalink I could not find a satisfactory answer. I searched for
ORA-01882 and ORA-01882: timezone region not found. But this error code ORA-01882 looks like can appear in other
Oracle products too.
The metalink id 1148503.1 does exactly the same issue. But for me the solution did not work.
My OS time zone shows like this:
cat /etc/sysconfig/clock
ZONE="Etc/GMT"
UTC=true
ARC=false
And Oracle also understand this time zone as shown below:
$sqlplus / as sysdbaSQL*Plus: Release 11.2.0.2.0 Production on Wed Dec 7 17:07:16 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL> SELECT CAST(FROM_TZ(CAST('12-JUL-2010 08:00:00' as TIMESTAMP), 'GMT') AT TIME ZONE 'Etc/GMT' AS DATE) from dual;
CAST(FROM
---------
12-JUL-10SQL>
Resolution:
To solve the issue add “-Duser.timezone=Etc/GMT” (without the quotes) in JAVA_PROPERTIES of your file
…/Middleware/gc_inst/user_projects/domains/GCDomain/bin/setDomainEnv.sh
Then do:
cd OMS_HOME/bin
emctl stop oms
emctl start oms
Then try. It should now work.
Oracle Enterprise Manager 11g Segment Advisor consumes significant CPU time
Oracle Enterprise Manager 11g is no doubt a very useful tool for database administrators. Whoever has used it can testify that it makes life so easier. For example the Oracle Enterprise Manager 11g Segment Advisor can give very useful information at the click of buttons. Getting these information through command line will need significant effort as well as knowledge.
But we must also be aware that it can also have significantly detrimental effect on your production database if you do not control usage.
If you maintain a database in a corporate environment it may be sometime necessary to give access to your Oracle Enterprise Manager 11g to management stuff who may not be too tech savvy or at least with Oracle technologies. What they may be looking for is just to monitor activities or trends. But if they start running different advisors then it may impact a production database.
Today I was running Segment Advisor for just two tablespaces. One of them was 125G and another 32G. While running the segment advisor from one Oracle Enterprise Manager session I monitored the impact of this activity from another session through the database instance performance tab.
The impact looks significant to me. Note that this database is a non production database and was quite (meaning no serous activity happening at the time of running).
This is how looks in Top Activity screen

Oracle Enterprise Manager 11g Grid Control
The Oracle Enterprise Manager 11g Grid Control is Oracle solution to manage Grid environment that allows businesses to heighten application performance and deliver unparalleled IT infrastructure reliability.
All kings of business, small, medium or large can attain measurable IT cost savings by extending the availability of computing resources, cultivating more productive and effective administrators, and achieving higher quality of service. This can all be achieved by installing Oracle Enterprise Manager 11g Grid control to manage your Oracle technology stack.
In previous versions of Oracle Enterprise Manager (before 10g), it was mostly used for Oracle database management But the latest versions introduced Oracle Enterprise Manager 11g Grid Control capabilities of managing your infrastructure by monitoring/managing
- oracle databases
- oracle database servers or hosts
- application management
- application performance monitoring
- process monitoring
- streams
- active dataguard
- database replication
- cost-effective and easy automated configuration management
- oracle provisioning
Oracle Enterprise Manager 11g Grid Control has three major components which are
- Oracle WebLogic Server
- Oracle Management Service (OMS)
- Repository Database
- Oracle Management Agent
Oracle Weblogic Server is Oracle’s replacement for Oracle Application Server which was used till Oracle Enterprise Manager 10g. but 11g introduced
Oracle Weblogic Server, a more robust and stable application server. The Main engine or software for OEM is the OMS. That is a Java application
that sits on Oracle Webologic Server. The OMS interacts with Oracle repository database, Agents on targets, and Oracle Weblogic Server and provides an efficient web browser based Grid Control environment.
Oracle Repository database is an Oracle database that stores all the configuration data and stats sent from the agents. This data is displayed on users
logic and Oracle Enterprise Manager through Grid Control.
Other functionalities that Oracle Enterprise Manager 11g Grid Control includes
- Run ADDM Report
- Run ASH Report
- Capability to chaneg system parameters
- Run SQL Advisor
- Run Segment Advisor
- Run MTTR advisor
- SQL Performance Analyzer
- Streams Performance Advisor
- SQL Advisors
- Memory Advisors
- Automatic Undo Management
- Maximum Availability Architecture (MAA) Advisor
- Segment Advisors
- Viewing, purging and archiving Alert logs
- Viewing, purging and archiving Trace files
- Blackouts
- Apply Patch
- Scheduler Central
- SQL Worksheet
- Export to Export Files
- Import from Export Files
- Import from Database
- Load Data from User Files
- Monitor Export and Import Jobs
Granting Access To Non-DBA Users to the Oracle Enterprise Manager 11g Grid Control Performance Tab
Normally users who do not have DBA roles can not access Oracle 11g Performance related information using OEM 11g Grid Control.
Normally only Oracle 11g DBAs are allowed to view these tabs and they use them to do performance tuning or to identify problematic SQL or session etc.
However there is a way to grant access to OEM 11g Grid Control performance tab to users who do not have DBA roles. In this case the user means the users in the target database. This is helpful when you as a Oracle 11g DBA wants to grant access to the performance tab to management users who would like to have access to these data.
This is done by assigning OEM_MONITOR role to those users.
Caution: Please not that OEM_MONITOR role comes with a number of powerful privileges. So really give a thought if you need to assign OEM_MONITOR to not so technical users.
A way to avoid that is to create another role and assign OEM_MONITOR role like privileges to that role.
Here is a list of the privileges that OEM_MONITOR role has in Oracle 11g database:
SQL> select ROLE, TABLE_NAME, PRIVILEGE from ROLE_TAB_PRIVS where ROLE=’OEM_MONITOR’ order by 3,2;
ROLE TABLE_NAME PRIVILEGE
—————————— —————————— —————————————-
OEM_MONITOR ALERT_QUE DEQUEUE
OEM_MONITOR BSLN EXECUTE
OEM_MONITOR BSLN_INTERNAL EXECUTE
OEM_MONITOR BSLN_METRIC_SET EXECUTE
OEM_MONITOR BSLN_METRIC_T EXECUTE
OEM_MONITOR BSLN_OBSERVATION_SET EXECUTE
OEM_MONITOR BSLN_OBSERVATION_T EXECUTE
OEM_MONITOR BSLN_STATISTICS_SET EXECUTE
OEM_MONITOR BSLN_STATISTICS_T EXECUTE
OEM_MONITOR BSLN_VARIANCE_SET EXECUTE
OEM_MONITOR BSLN_VARIANCE_T EXECUTE
OEM_MONITOR DBMS_AQ EXECUTE
OEM_MONITOR DBMS_AQADM EXECUTE
OEM_MONITOR DBMS_DRS EXECUTE
OEM_MONITOR DBMS_MONITOR EXECUTE
OEM_MONITOR DBMS_SERVER_ALERT EXECUTE
OEM_MONITOR DBMS_SYSTEM EXECUTE
OEM_MONITOR DBMS_WORKLOAD_REPOSITORY EXECUTE
OEM_MONITOR MGMT_RESPONSE EXECUTE
OEM_MONITOR MGMT_UPDATE_DB_FEATURE_LOG EXECUTE
OEM_MONITOR BSLN_BASELINES SELECT
OEM_MONITOR BSLN_METRIC_DEFAULTS SELECT
OEM_MONITOR BSLN_STATISTICS SELECT
OEM_MONITOR BSLN_THRESHOLD_PARAMS SELECT
OEM_MONITOR BSLN_TIMEGROUPS SELECT
OEM_MONITOR MGMT_BASELINE SELECT
OEM_MONITOR MGMT_BASELINE_SQL SELECT
OEM_MONITOR MGMT_BSLN_BASELINES SELECT
OEM_MONITOR MGMT_BSLN_DATASOURCES SELECT
OEM_MONITOR MGMT_BSLN_INTERVALS SELECT
OEM_MONITOR MGMT_BSLN_METRICS SELECT
OEM_MONITOR MGMT_BSLN_STATISTICS SELECT
OEM_MONITOR MGMT_BSLN_THRESHOLD_PARMS SELECT
OEM_MONITOR MGMT_HISTORY SELECT
OEM_MONITOR MGMT_HISTORY_SQL SELECT
OEM_MONITOR MGMT_LATEST SELECT
OEM_MONITOR MGMT_LATEST_SQL SELECT
Recent Comments