Installation and Configuration

Installation and Configuration
Page 1
1
Objectives
After this lesson you should be able to

understand:
• New features of the Enterprise Manager
Configuration Assistant
• Certification Requirements
• Intelligent Agent Installation and Configuration
Page 2
2
Enterprise Manager Configuration
Assistant
• Supports creation of new database instance
for the repository
• Object support required for 9i repository
Enterprise Manager Configuration Assistant

When EM Configuration Assistant detects database software already installed
in the same $ORACLE_HOME as the Management Server, it prompts user to
choose between creating a repository via Typical or via Custom.
•Typical does not prompt for more information from user; logical
defaults are already specified, and at the end the defaulted
information (i.e. new database SID, repository user name/password,
default repository tablespace, etc.) is displayed to user.
•Custom prompts user for detailed information; any defaults that are
supplied can be edited.
When EM Configuration Assistant detects database software already installed
in the same $ORACLE_HOME as the Management Server, it will call
Database Configuration Assistant to actually create the new database instance.
In this new database instance, the Enterprise Manager repository will be
created.
Note: When Database Configuration Assistant is spawned by EM
Configuration Assistant, the user is not prompted with additional pages to
respond to; only the progress/status dialog of Database Configuration
Assistant will appear.
The following database versions are certified to contain a 9i repository:
Enterprise Edition or standard edition server release 9.0
Enterprise Edition or standard edition server release 8.1.7 or 8.1.6
Enterprise Edition server release 8.0.6
While releases 9.0, 8.1.7, and 8.1.6 all support objects by default; release
8.0.6 does not. Prior to creating your 9i repository in an Enterprise Edition
8.0.6 database, ensure that the Objects Option has been installed and enabled.
Page 3
3
Enterprise Manager Migration Assistant
• Oracle Enterprise Manager Migration

Assistant supports migrating data for both
Oracle Enterprise Manager and Oracle
Enterprise Manager Management Packs
• Direct Migration of repository from Release 1.x
to Release 9i is not supported
• How to Migrate from 1.x to 9i?
1. Migrate from Release 1.x to Release 2.x with
Migration Assistant Release 2.x
2. Upgrade from Release 2.x to Release 9i by
using Enterprise Manager Configuration
Assistant Release 9i
Migration
Before migrating or upgrading a Management Server and repository to
Release 9i, ensure that all Enterprise Manager products you intend to use with
the repository are of Release 9i.
For instance, do not upgrade the Management Server and repository to release
9i if you plan to use Release 2.2 Packs (e.g. Diagnostics Pack Release 2.2). If
you upgrade your Management Server and repository to Release 9i before
obtaining the Release 9i Pack software you intend to use, you will not be able
to use the older Pack product(s).
Page 4
4
Certifications
Console Integ Thin OMS Mgt Other EM EM

Apps client Pack Packs Web Paging
for Site Server
SAP
R/3
Win NT Yes Yes Yes Yes Yes Yes Yes Yes
4.0/
Serv
Pack 6a
Win 2000 Yes Yes Yes Yes Yes Yes Yes Yes
Win 98 Yes Yes Yes No Yes Yes No No
Sun Yes Yes No Yes No Yes Yes No

Sparc
Solaris
2.6,
2.7,
2.8
Certifications
Integrated Applications include the following:
•Oracle Forms Server Manager
•Oracle Policy Manager
•OLAP Services
•Oracle Cube Viewer
•Oracle Directory Manager
Thin client includes the folowing:
•Base Enterprise Manager Console (including database
applications, Data Guard Manager, LogMiner Viewer, Spatial
Index Advisor, SQL*Plus Worksheet and Text Manager)
•Enterprise Security Manager
•Entire Change Management Pack
•Performance Manager, Lock Monitor, Performance Overview,
Top SQL, and Top Sessions of Diagnostics Pack
•Tablespace Map, Reorg wizard, Outline Manager, and
Graphical Explain Plan of Tuning Pack
Note:
Refer to Oracle Enterprise Manager Configuration Guide and
Installation Guide for System and Hardware requirements.
Page 5
5
Certifications
Console Integ Thin OMS Mgt Other EM EM
Apps client Pack Packs Web Paging
for Site Server
SAP
R/3
Intel Yes Yes No Yes No Yes Yes No
Solaris
HP-UX Yes Yes No Yes No Yes Yes No

64-bit
IBM AIX Yes Yes No Yes No Yes Yes No

64-bit
Compaq Yes Yes No Yes No Yes Yes No

Tru64
Intel Yes Yes No Yes No Yes Yes No

Linux
32/64
bit
Certifications (continued)
Other Packs include the following:
•Tuning Pack
•Diagnostics Pack
•Change Management Pack
•Standard Management Pack
•Management Pack for Oracle Apps
Note
The following components of the Packs listed above (Other Packs) will
not be ported to UNIX platforms:
•SQL Analyze
•Expert
•Index Tuning Wizard
•Trace Data Viewer
Page 6
6
Intelligent Agent Installation
Installation
• Agent contains functionality previously
present in the Data Gatherer
• No separate service/process for Data Gatherer
Intelligent Agent Installation

The 9i Intelligent Agent contains the functionality that was present in the
Oracle Data Gatherer product in prior releases ie, data collections are handled
by the Agent.
Starting the Agent will start a process that responds to requests from OMSs
and Performance Manager/Capacity Planner.
The install of the Agent will place the configuration files for both the agent
and the collection services together. Tracing information will go into the
same directory.
Benefits
•Simpler Configuration
•Easier to trace and troubleshoot
•The integration of the collection service into the agent allows it to
use the Agent’s scheduler to provide more flexible collection
schedules. In prior releases, collections were separated by intervals.
Now, collections can be scheduled for specific times. Different
collection requests can be scheduled separately.
•The agent provides a host environment for collection cartridges that
collect data about different kinds of targets, and retrieves data by
calling into these cartridges when it receives a request from its clients.
Since different collection requests can be scheduled separately,
clients can now request different schedules for different data points
on the same service.
•Agent can also leverage the resources and functionality of the Data
Gatherer.
Page 7
7
Intelligent Agent Migration
• Run nmumigr8 utility to migrate existing jobs,

events and data collections
• Helps users to retain existing data after
upgrading to 9i Agent
• Set ORACLE_HOME environment variable
Intelligent Agent Migration

When upgrading from Agent version 8.0.6/8.1.6/8.1.7 to Agent version 9i,
users can run a migration utility called "nmumigr8" located under the Agent's
ORACLE_HOME/bin directory, to migrate existing jobs, events and data
collections to a format recognized by Agent version 9i.
This allows users to retain existing data after upgrading to Agent version 9i.
Set the ORACLE_HOME environment variable to point to the 9i Agent's
ORACLE_HOME prior to running nmumigr8.
Usage:
nmumigr8 [ -source_home <source ORACLE_HOME>] [ -
password <password>][ -verbose]
where:
source_home is the source Oracle Home which contains existing Agent queue
and data collection files. If source_home is not supplied then the value
defaults to the destination Oracle Home which is the value of the
ORACLE_HOME environment variable.
password is the password used by the Agent to encrypt its queue files. If not
supplied a default encryption password is used.
verbose indicates that detailed migration information should be written to the
trace file nmumigr8.trc located under the Agent's
ORACLE_HOME/network/trace directory. If this flag is not set, then
only the summary information is written to the trace file.
Page 8
8
Startup and Shutdown the Agent
Startup and shutdown of the agent performed

through agentctl utility.
• Startup the Agent
– agentctl start agent
• Stop Agent
– agentctl stop agent
• Status
– agentctl status agent
• Restart
– agentctl restart agent
Startup and Shutdown the Agent

On starting the Agent, a single “dbsnmp” process is started. A watchdog script
“dbsnmpwd” also starts. This watchdog script keeps a watch on the dbsnmp
process. If dbsnmp goes down, it attempts to restart it.
Page 9
9
Intelligent Agent – Log files
• Log Files
– dbsnmp.log (unless config parameter
points to another)
– dbsnmp.nohup (unless environment
variable points to another)
– dbsnmpj.log (unless config parameter
points to another)
– nmiconf.log
Intelligent Agent – Log files

The above parameters are default parameters. They are located under the
Agents $ORACLE_HOME/network/log directory.
•The log file dbsnmp.log is written by the Agent at every startup , even if
tracing is not turned on. It contains the name and version of the Agent and the
name and location of the Agents configuration files. If tracing is turned on it
also contains problems encountered with the database and listener
connections.
•dbsnmp.nohup is the log for dbsnmpwd watchdog script.
•dbsnmpj.log is for job process spawned by the Agent for executing a Job
•nmiconf.log gives detailed information of a specific error, if any. For
example, if multiple services of a particular type, say HTTP server, are
discovered by the Agent. The Agent ignores one of them and an entry is made
in nmiconf.log file. In general, nmiconf.log shows problems related to auto
discovery.
Example of dbsnmp.log
DBSNMP for Solaris: Version 9.0.0.0.0 – Development
on 23-Feb-2001 16:29:35
…..
System parameter file is
/private/app/ora9i/network/admin/ snmp_ro.ora
Log messages written to
/private/app/ora9i/network/log/ dbsnmp.log
Trace information written to
Page 10
/private/app/ora9i/network/trace/ dbsnmp.trc
Trace level currently 0 10
Summary
After this lesson you should understand:

• New features of the Enterprise Manager
Configuration Assistant
• Certification Requirements
• Intelligent Agent Installation and Configuration
Page 11
11
Database Administration Using Enterprise Manager
1
Objectives
After this lesson, you should be able to:

• Explain Enterprise Manager functionality which
supports Oracle9i Database features
• Use the new capabilities of Replication
Management
• Use the OLAP Summary Management interface
• Generate HTML Reports
2
Enterprise Manager Support for
Oracle9i Database Features
• Persistent init.ora
• Automatic Undo Management
• Unicode
• Dynamic Memory Management and Buffer
Cache Sizing Advice
• Default temporary tablespace
• Multiple block sizes
• Mean Time to Recovery (MTTR)
• Backup and Recovery enhancements
• Advanced Queuing
Enterprise Manager Support for Oracle9i Database Features

The Console has been enhanced to support new features within the database management
system.
3
Persistent Parameter File (SPFILE)
SPFILE
• stores instance parameters persistently by the
server
• is initially created from an init.ora file
• resides on the server side and is in binary
format
Persistent Parameter File (SPFILE)

Benefits:
• All changes made to the values of parameters using the ALTER SYSTEM command persist
across shutdown and startup. This eliminates the need to manually update initialization
parameters to make changes effected by ALTER SYSTEM statements persistent
• Allows use of a single parameter file by all members of a Real Application cluster
The SPFILE resides on the Server side and the default location is $ORACLE_HOME/dbs directory.
The default name is SPFILE<SID>.ora
4
Creating the SPFILE
Creating the SPFILE

The SPFILE is initially created from the initialization parameter file. SYSDBA or SYSOPER
privileges is required to create an SPFILE.
• Right-click on the Configuration folder under Instance and click Import spfile, or select the
Configuration folder and click Import spfile from the Object menu
• Enter the location of the pfile. Use the browse button to search for the files on the database
machine. Enter the name of the spfile you want to create. Both the pfile and the spfile must be
located on the same machine as the database
• Click the OK button to create the spfile.
5
Creating init.ora file from SPFILE
Creating init.ora file from SPFILE

You can export an SPFILE to create a text initialization parameter file. This may be necessary to
modify the SPFILE, which is in binary format or create backups of the SPFILE. SYSDBA or
SYSOPER privileges is required to create an init.ora file from SPFILE.
• Right-click on the Configuration folder under Instance and click Export spfile, or select the
Configuration folder and click Export spfile from the Object menu
• Enter the name and location for the pfile you want to create. Use the browse button to search
for the files on the database machine. Enter the name and location of the spfile. Both the pfile
and the spfile must be located on the same machine as the database
• Click the OK button to create the init.ora file.
6
Changing Parameters
Changing Parameters
The All Parameters page lists all initialization parameters.
•For 9i databases, you must be connected as SYSDBA to edit static initialization parameters. To edit
dynamic parameters SYSDBA privileges are not required.
•For non-9i databases you must be connected as SYSDBA to edit all parameters.
Changing Running and Configured Parameters
Running Parameters show the parameters that are currently running. If you change a dynamic
parameter, the change is effected immediately. If the database is restarted, you start up with the
original parameter value since it has not been saved to the spfile. If you change a static parameter,
the changes are saved to a pfile or spfile and the database is restarted.
Configured parameters are stored in the server-side persistent file (spfile). If you change a dynamic
parameter, the changes are saved to an SPFILE and take place immediately.
7
Startup Using the SPFILE
Startup Using the SPFILE

You can use the startup dialog to start the instance.
•Right-click on the database folder and select startup, or select startup from the Object menu
•If you want to startup the database using SPFILE, check the Use Configured Parameters box.
Oracle reads the initialization parameters from a server parameter file in a platform-specific default
location
•If you want to use a init.ora file to start the database, uncheck the Use Configured Parameters box
and supplying the init.ora file to start the database.
8
Undo Tablespace Support
• Simplifies and automates the management of

rollback segments
• DBA has the choice of managing rollback
segments or have Oracle automatically
manage undo data in an undo tablespace.
• The rollback mode is set by the initialization
parameter UNDO_MANAGEMENT
• New “undo” clause in the Create Tablespace
dialog
• Instance Management Undo tab displays all
details about the undo tablespace
Undo Tablespace
•In Oracle9i a new approach for undo space management called Automatic Undo Management is
introduced. With this new architecture undo segments are managed via an UNDO tablespace.
•The rollback mode is set by the initialization parameter UNDO_MANAGEMENT with the values
of {AUTO/MANUAL}
• If AUTO the instance is started in AUTOMATIC mode
• If MANUAL the instance is started in the default MANUAL mode
•For each Oracle instance, a DBA will allocate enough disk space for the workload of the instance in
the UNDO tablespace versus allocating a number of undo segments in different sizes.
Enterprise Manager allows you to determine if a database is in Automatic Undo
Management mode. You specify whether or not the database is using rollback segments or
an undo tablespace in the init.ora. You should also specify which tablespace is the undo
tablespace.
When you create a new tablespace, you can make it an undo tablespace by selecting the
Undo radio button in the Create Tablespace dialog. For an undo tablespace, all storage
options are disabled since they are handled automatically.
In addition, in Instance Management a new "Undo" tab displays all details about the undo
tablespace including the name of the current undo tablespace and retention time. The
retention time is the time of the longest transaction or the farthest back you want to go with
the server flashback feature.
9
Undo Tab
Creating an Undo Tablespace

There are two methods of creating an undo tablespace:
1. Create Undo Tablespace when creating a database with CREATE DATABASE statement
2. Create Undo Tablespace for an existing database. This method is explained below.
• Create a new tablespace and make it an undo tablespace by selecting the undo radio button in
the create tablespace dialog. For an undo tablespace all storage options are disabled since
they are handled automatically by the database
• Set the following initialization parameters in the Instance Management Configuration’s
general page
• UNDO_MANAGEMENT to AUTO – for starting the instance in Automatic Undo
Management mode
• UNDO_TABLESPACE to the name of the undo tablespace created
• Restart the database
Undo Tab
The Undo tab in Instance Management displays all details about the undo tablespace including the
name of the current undo tablespace and the retention time. The retention time specifies the
length of time to retain undo information. Committed undo information is normally lost when
the undo space is overwritten by newer transactions. For consistent read consistency purposes if
long running queries might require old undo information, the Undo Retention provides a means
of specifying the amount of undo information to retain.
10
Unicode
• Used to represent characters in any language

• With Unicode support you can specify column
length in characters
• Specified using the column length drop down
list while creating table/cluster
Unicode
Unicode can represent characters in any language. You do not need to know whether the character
set is single-byte or multi-byte when defining columns.
With Unicode support you can specify the length of character columns in characters. In the Create
Table or Cluster dialog, the column length drop down list will allow you to specify the length in
characters or bytes.
By default, the column length will be as specified by the NLS_LENGTH_SEMANTICS init.ora
parameter.
11
Unicode
Defining Unicode Columns

•When connected to a unicode database, the length can be specified in byte or characters. For
example, instead of specifying “10” as the length of the column, you can enter “10char” or “10byte”
•If byte/char is not specified, then the default value set by NLS_LENGTH_SEMANTICS is used
•Default is byte
12
Buffer Cache Sizing Advice
• Oracle9i includes an advisory mechanism for

optimally sizing the buffer cache
• New fixed view V$DB_CACHE_ADVICE
• Use EM Buffer Cache Size Advice Display
Buffer Cache Sizing Advice

Oracle9i includes an advisory mechanism that can be used to determine an optimal size for the buffer
cache. A new fixed view V$DB_CACHE_ADVICE will contain “miss” rate predictions for 20
cache sizes ranging from 10% to 200% of the current cache size. This view can be used to
determine whether the cache needs to be shrunk or grown for the present workload.
You can view the same information in the Enterprise Manager Buffer Cache Size Advice display to
determine if buffer cache should be grown or shrunk for your present workload. The Enterprise
Manager display includes a chart of the information which makes it much easier to view and
interpret the data.
13
Buffer Cache Size Advice View
Buffer Cache Size Advice View

You can view the Buffer Cache Size Advice information in Enterprise Manager as an alternative to
querying V$DB_CACHE_ADVICE. The Enterprise Manager display includes a chart of the
information which makes it much easier to view and interpret the data.
How to Launch Buffer Cache Size Advice
• Click on Memory tab under Instance ->Configuration
• Click on Buffer Cache Size Advice to see the advice for choosing the size of the buffer cache
• If the db_cache_advice initialization parameter has not been changed, a dialog will appear
prompting whether you want to change the db_cache_advice initialization parameter. If ‘Yes’
the parameter will be changed
How to interpret the graphical display
As you move the mouse over the graphical display of Physical Reads vs. Cache Size there will be a
text helping you interpret the data. For example, “If you set cache size to 5 MB the physical reads
will increase by 2%”.
14
Default Temporary Tablespace
• Specify default temporary tablespace to store

temporary data for a user
• Eliminates the use of SYSTEM tablespace for
storing temporary data
• Use Storage Management to set default
temporary tablespace
Default Temporary Tablespace

A default temporary tablespace can be created at database creation time or at a later time with the
ALTER DATABASE command. If it is created during the database creation, it is a locally managed
tablespace.
Benefits
• Users, both existing and future users, not explicitly assigned to a temporary tablespace are
assigned to the default temporary tablespace.
• Eliminates the use of SYSTEM tablespace for holding temporary data.
Using Storage Management you can either create a new tablespace and set as the default temporary
tablespace or define an existing temporary tablespace as the default temporary tablespace.
15
Creating Default Temporary Tablespace
Creating Default Temporary Tablespace

•Under the Create Tablespace folder, select the Type as temporary. This enables the Set as Default
Temporary Tablespace checkbox
•Check this box to make this tablespace as the Default temporary tablespace
•You can also reassign the default temporary tablespace to another one
•You cannot make the default temporary tablespace offline or make it permanent.
16
Multiple Block Size Support
• Oracle9i supports the creation of databases

with multiple block sizes
• Supports a standard block size and up to five
non-standard block sizes
• Drop down list with block sizes provided in in
Storage Management
Multiple Block Sizes

Benefits
• Ability to locate objects in tablespaces of appropriate block size in order to maximize I/O
performance
• Ability to transport tablespaces between databases with different block sizes (for example, an
OLTP database to an Enterprise Data Warehouse)
Oracle9i allows you to use block sizes of 2K, 4K, 8K, 16K, and 32K in the same database.
Tablespaces can simply be plugged-in from one database to another.
In the init.ora file you specify how much space (memory) in the database buffer cache should be
allocated for each block size. If you specify space for 2K and 8K block sizes, that also implies that
you have selected only those two block sizes as options in your database.
When you create tablespaces, you can specify which block size to use for the tablespace from a
Block Size drop down list. The list will only contain those sizes you specified in the init.ora file.
17
Mean Time to Recovery
• Controls the time to recover from an instance

crash
• Controlled by FAST_START_MTTR_TARGET
initialization parameter

Instance or crash recovery recovers a database to its transaction-consistent state just before instance
failure. Recovery from instance failure is automatic, requiring no DBA intervention.
18
Mean Time to Recovery (continued)

•Controls the time required to recover from an instance crash
•Specifies the maximum time you would like to spend to recover from an instance crash
•When you specify a value for this field, the initialization parameter
FAST_START_MTTR_TARGET is changed automatically.
For example, you are running an e-commerce site and have an instance crash. You know the
downtime can only be say, 5 minutes of unavailability. You would set the MTTR to be 5 minutes.
The database then assures it can recover in that time.
Note:
If this field is set to short time can have negative impact on database performance.
19
Backup and Recovery Enhancements
• RMAN scripts can be submitted and scheduled

via the job system
• RMAN Image Copy option support
• Requires 9i Intelligent Agent
• Can be enabled in pre-9i Agents using rman.tcl
file
Backup and Recovery Enhancements

To enhance the flexibility of the Backup and Recovery facility, the Job System supports an RMAN-
specific job task. You can simply input any RMAN script and submit it via the job system.
How to enable RMAN script in pre-9i Agents
The RMAN script feature is only available with the 9i Oracle Intelligent Agent. If you have older
versions of the Intelligent Agent, you can enable this feature by adding rman.tcl file into
$ORACLE_HOME/network/agent/jobs/oracle/rdbms/generaldirectory.
RMAN Parameters
Valid RMAN parameters include the following:
• debug
• msglog
• trace
• Append
For more information on RMAN parameters, see the Oracle9i Recovery Manager Users Guide and
Reference.
20
Advanced Queuing
• Topology map displaying individual queues

and their states on the database selected
• View errors and drill down to diagnostic detail
• Schedule details and messages can be viewed
Advanced Queuing
Advanced Queuing support is provided by introducing a new topology map that displays individual
queues and their states on the database selected, including dblink status. You can see where there
are errors and drill down to additional diagnostic detail.
21
Topology Map
Topology Map
The topology map specifies whether the database link specified is valid, if the remote database is
available, or if the remote queue is enabled for enqueuing.
In the map shown above:
• A black arrow indicates a working database link between two destinations
• Broken red arrow indicates a broken database link
22
Replication Enhancements
• Support for single master quiesce for

snapshots
• Wizards to create templates and generate
template scripts
• Generation of comprehensive HTML reports on
the replication environment status
• Fully integrated with the Console
• Topology map which includes error
information
Replication Enhancements
The new version of replication management introduces support for single master quiesce for
snapshots along with an improved "Templates" Wizard to help in setting up snapshot sites more
easily. In addition, replication management adds the capability to generate and save comprehensive
HTML reports on the replication environment status.
Replication management is now fully integrated with the Console. A new topology map of your
replicated environment is included. It shows error information to assist you in diagnosing and
resolving problems in your replication environment.
Replication management is integrated into the Navigator tree and structured to follow a typical
workflow.
23
Topology Map
Topology Map
A new topology map of your replicated environment is provided. It shows error information to assist
you in diagnosing and resolving problems in your replication environment.
In the slide shown above:
•The database IDDB1
• is functioning both as a master site and a materialized view site
• has one administrative request to process. The blue figure indicates administrative requests
• has one error. Red icon indicates errors
•Master databases IDDB2 and OREM have no administrative requests to process and no local errors
•IDDB1 has four deferred transaction in its deferred transaction queue that will be applied at OREM.
It has 17 registered materialized views and 1 registered materialized view group.
24
Error Investigation
Error Investigation
If a deferred transaction cannot execute properly, Oracle logs the transaction as a local error
transaction. An error may occur due to a database problem, such as lack of space in the table you
are attempting to update or may be the result of unresolved replication conflict.
Displaying error transactions
• Expand the replication folder under the database that contains errors
• Select Administration
• Select the Errors tab. All local errors are displayed in the right pane
• To obtain more information on a particular error transaction, select the individual error
transaction and click the Details button to open the Error Calls dialog box
Resolving Error Transactions
After correcting the error, perform the following steps:
1. Re-execute the error transaction – If the error transaction executes successfully, Oracle
automatically removes the transaction from the replication catalog at the local site.
2. Remove the error transaction
How to re-execute an error transaction
• Expand Replication folder from the database node that contains errors
• Select Administration and click on the Errors tab on the detail side of the Console
• Select the individual error transaction and click Retry
Removing Error Transactions – When you re-execute an error transaction, Oracle automatically
deletes the transaction from the local site. However, at times it may be necessary to manually
resolve an error transaction. In such cases, you must delete the error transaction from the local 25
site.
Materialized Views
• Know what aspects of Summary Management

a materialized view supports
• Enhancements to support materialized view
DDL
• Explain materialized view feature
Materialized Views
Enterprise Manager has a facility for explaining what aspects of Summary Management a particular
materialized view supports so that you know exactly what to expect from the materialized view.
Enhancements have been made to support materialized view DDL, such as:
•Pre-build tables
•Storage options
•Submit as a job
The Explain Materialized View feature provides detail regarding what aspects of a materialized
view are not complete.
26
Summary Advisor Wizard
• Recommends and builds summaries to

optimize query performance against a cube
• Bases recommendations on characteristics of
data or workload
• Workload data collected from SQL cache,
Oracle Trace or external source
• Displays chart showing space vs. performance
tradeoff
Summary Advisor Workload

The Summary Advisor Wizard provides an interactive environment to recommend and build
materialized views.
Recommendations are based on the characteristics of data including cardinality and data distribution
or the workload.
Prior to version Oracle9i, Summary Advisor used row cardinalities on base tables as a basis for
recommending materialized views. In the new version the Summary Advisor has been enhanced to
use workload data collected from SQL cache, Oracle Trace or an external source.
27
Summary Recommendations
Summary Recommendations
This screenshot displays a chart showing the trade off between the space it would take to create
summaries vs. the performance gain you get. You can specify how much space you want to allocate
to summaries. Then Oracle will generate a script to create summaries that fix that space. It will
always create the most useful summaries for the space available. Hence you maximize the
performance gain for the amount of space you devote to the summary. You can move that slider
(triangle) to put yourself on the desired point on the graph.
28
OLAP Management
• Oracle9i provides integrated data warehousing

support
• Enterprise Manager provides an interface to:
– Define and manage metadata objects
– Automatically determine the summaries
that would best optimize performance
OLAP Management
Business decision makers need fast access to data, powerful computational, analytical capabilities
and the flexible viewing capabilities of analysis-based decision-oriented systems. These systems are
called OLAP systems. In Oracle9i, OLAP capabilities are seamlessly integrated with the database
server, using source and aggregated data from the relational source (ROLAP). Oracle now becomes
a single platform for OLTP, Warehousing and OLAP needs.
Enterprise Manager provides the graphical user interface that guides you in the definition and
management of metadata objects. You can generate pre-computed data elements of the OLAP model
using Oracle Summary Management.
29
OLAP Support - Cubes
• Easy-to-use wizard to create cubes

• Wizard launches Summary Advisor wizard for
optimizing
• Cube topology viewer to display model
• Display of invalid cube
• Star and Snowflake schema support
• Measure folders - collections of measures
Support for OLAP Cubes

An easy-to-use wizard is provided to assist in the creation of cubes. The wizard launches the
Summary Advisor wizard to optimize the cube.
Property pages provide Create/Edit Cube support.
Invalid cubes are displayed and diagnostic information is provided to help you repair the cube.
OEM includes support for Star and Snowflake schemas.
You can create collections or sub-collections of measures as Measure Folders.
30
Cube Topology Viewer
Cube Topology Viewer

You can use the Cube Topology viewer to display the model of the cube. The structure above
illustrates the relationship between the fact table, which contains the base information for the cube’s
measures, and the dimension tables, which contain the base information for the cubes dimensions.
31
OLAP Support - Dimensions
• Easy-to-use wizard to create normal and time

dimensions
• Ensures a dimension is OLAP-ready
• Hierarchical view to display dimension
structure
Support for OLAP Dimensions

An easy-to-use wizard helps you create normal and time dimensions.
A hierarchical view enables you to display the dimension’s structure.
32
HTML Database Reports
Report generation enhancements allow you to

generate fully formatted reports. You can
generate:
• Complete Database configuration report
• Report of only the properties of an Object
selected in the navigator tree
• Report of Object dependencies
HTML Database Reports

Report generation enhancements allow you to generate fully formatted reports with just the
information you need.
You can generate complete database configuration properties reports, or reports that contain only the
properties of an object selected in the navigator tree.
When you launch report generation, the dialog menus that appear are appropriate to the currently
selected object in the navigator tree.
These reports are available in standalone mode
33
Database Configuration Report
Database Configuration Report

You can extract information from the database and save it in different formats (text, HTML, or
Comma-Separated Values). For example, you can save the Instance, Storage, Schema information to
an HTML file.
How to generate an HTML report?
• Highlight Database in the navigator tree
• Click on the ‘Create Report’icon in the toolbar, or right-click the database folder and click
Create Report, or select Create Report from the Object menu
• Specify the desired contents of the report
• Click ‘OK’to generate the report or click ‘view’to generate and immediately view the report
User Defined SQL
The User Defined SQL enables you to optionally provide a SQL script to be added as an item under
the Report content`s User Defined category.
Note: Each user defined SQL statement must be <=2k.
34
Summary
In this lesson, you should have learned how to:

• Use Enterprise Manager capabilities which
supports Oracle9i Database features
• Use the new capabilities of Replication
Management
• Use the OLAP Summary Management interface
• Generate HTML Reports
Summary
35
Console
Page 1
1
Objectives
After this lesson, you should be able to:

• Understand the new look and feel of the
Console
• Use the Console in Standalone mode
• Restrict access to Node Discovery
• Control access to Nodes and Targets
• Define Management Regions
• Customize, schedule and publish reports
• View Published Reports from EM Reporting
Website
• Discover multiple listeners on a single node
Page 2
2
New Console Look-and-Feel
• Two pane, master/detail view of the environment

• Events, Jobs and Groups functionality integrated
in the Navigator tree
• Database administration features fully integrated
with Console
New Console Look-and-Feel

When user clicks on an item in the Navigator tree, the details of what has been
selected appear on the right-hand side of the console.
For example, when user clicks on Events in the Navigator tree on the left, the detail
side will show the Alerts, Registered and History tabs which contain details of
Events for all targets.
Page 3
3
Groups
Groups
•Groups form part of the navigator tree
•To create a Group, either:
• Click Create from the Object menu, or
• Right-click on the Groups folder and click Create
•You can also create a Group from an existing Group by selecting Create Like
•When users select a created group in the navigator tree, it displays on the detail side
a window with View, General and Access tabs
•The View tab shows a graphical view of the network making it easy to locate,
diagnose, and act on encountered conditions
•From the General tab (shown in the screen shot), users can add or remove targets to
the group, change the background image, description and size of icons
•From the Access tab the current access levels can be viewed. The Super
Administrator can also change the access level for other administrators from this
page or the administrator who owns the Group can change access level on it. Access
levels assigned on this page supersede any default access levels assigned with
Administrator preferences.
Page 4
4
Launching Enterprise Manager Console
Launching Enterprise Manager Console

When you launch the Console, choose between standalone or login to the middle
tier Oracle Management Server (OMS).
If the Management Server has not yet been installed nor configured, then you can
launch the Console standalone and connect directly to target databases to perform
administrative tasks such as deleting a table or creating a new database user. When
launching standalone, you can only connect directly to Oracle databases; no other
types of targets are currently supported for release 9i.
If the Management Server has been installed and configured, then you can launch
the Console through the Management Server. By connecting through a Management
Server, you have access to more comprehensive management capabilities.
(discussed in the forthcoming slides)
Note:
The choice between launching standalone or through the Oracle Management Server
is also available through other Enterprise Manager applications.
Page 5
5
Console launched Standalone
Console launched Standalone

When you launch the 9i Console in standalone mode, it looks something similar to DBA Studio in
release 2.1 or 2.2 but with more features and enhancements.
This is a screenshot of Console in standalone mode. The only targets in the navigator tree are
databases. You add databases to the navigator tree as follows:
Adding databases to the navigator tree
• Launch Console standalone
• Add the databases you wish to manage using the Add Database to Tree dialog box. This dialog
appears automatically when you start the Console in standalone mode for the first time. It is also
available from the Navigator main menu. You can manually enter the Net service names or add
them from the local tnsnames.ora file.
There is no support for discovering nodes with Intelligent Agents when the Console is launched
standalone.
Page 6
6
Connections using OMS
Connections using OMS

This is a screenshot of The Console logged into the middle tier Oracle Management
Server. There are several types of discovered targets in the navigator tree (e.g.
databases, HTTP Servers, Listeners etc) as well as Events, Jobs, Reports
Definitions. These additional types of targets and functionality would not be
available if the Console were launched standalone; only connecting directly to
databases is supported in standalone mode.
Page 7
7
Standalone Connection Benefits
• Available out-of-the-box
• Does not require install/config of middle tier
Management Server
• Does not require install of Intelligent Agent on
administered database
• Connect directly to managed target (only
databases supported for Release 9i)
Standalone Connection Benefits

Allows a single user to use one or more applications without the need of Oracle Management Server
or Intelligent Agent. If you want to perform certain administrative tasks that do not require the job,
event, or group system the standalone Console can be used.
Page 8
8
Standalone Connection Restrictions
• Only supports direct administration of Oracle
databases (ie, no management of other target
types)
• No access to Events, Jobs and Groups
• Cannot share administrative information
• Cannot use web-enabled applications
• No Paging and Email blackouts
• Cannot store and access preferences (e.g.
enhanced notifications, schedule )
• Cannot use Backup and Data Management
Tools
• Cannot customize, schedule and Publish
reports
Standalone Connection Restrictions

If you need access to any features that are not available in standalone mode then you must install and
configure the middle tier Management Server and launch the Console through the Management
Server.
As there is no use of a Management Server and its repository in standalone mode, there is no sharing
of administrative data, no paging and email blackouts, no web browser support etc.
Note:
As only databases are supported for Oracle9i, Management Pack for Oracle Applications and
Management Pack for SAP R/3 do not support standalone mode.
Page 9
9
Standalone Repository
When launching Console standalone, some

functionality requires standalone repository
Standalone Repository
Standalone repository is a single user database repository schema that stores
management information for the targets you are managing while using the Console
in standalone mode.
When launching the Console standalone and accessing certain Management Pack
applications (e.g. Oracle Change Manager, Oracle SQL Analyze, Oracle Index
Tuning Wizard, Oracle Tablespace Map, and Oracle Expert) for the very first time,
you will be prompted to create a single-user database repository schema to store
management information for targets being managed. Once this standalone repository
schema is created, it can be used by all five applications listed above; each
application does not require its own standalone repository schema.
This single-user database repository schema is separate from the repository that is
created when you install and configure a Management Server. This single-user
database repository schema is for a single administrator and does not require a
Management Server; while the repository used by a Management Server is for
multiple administrators and is required by the middle tier. Furthermore, interaction,
including migration or sharing of repository data, between the ‘standalone repository
schema’and the ‘Management Server repository’is not supported.
The following database versions are certified to contain a 9i standalone repository:
• Enterprise Edition or standard edition server release 9.0
• Enterprise Edition or standard edition server release 8.1.7 or 8.1.6
• Enterprise Edition server release 8.0.6
While releases 9.0, 8.1.7, and 8.1.6 all support objects by default; release 8.0.6 does
not. Prior to creating your 9i repository in an Enterprise Edition 8.0.6 database,
ensure that the Objects Option has been installed and enabled.
Refer to Enterprise Manager online help or documentation for further details.
Page 10
Before you create a standalone repository schema, Oracle recommends creating a
new tablespace for the standalone repository and a new database user who will own 10
the standalone repository. Oracle also recommends not using an existing tablespace
Connections using Oracle Management
Server
• Requires install/config of Oracle Management

Server/Repository
• No interaction between standalone and Oracle
Management Server repositories
• Removes the restrictions of standalone mode
Connections using Oracle Management Server

No migration between standalone repository and Management Server repository.
The user cannot create a standalone repository and later migrate it to a Management
Server repository and vice versa.
Page 11
11
Restricted Access to Node Discovery
• Discovery restricted to Super Administrators

• Discovered Targets
– Appear in all Super Admin views
– In regular admin views only if specified by
the Super Admin
Restricted Access to Node Discovery

Only Super Administrators can discover, refresh or remove nodes from the Console.
When a Super Administrator discovers nodes, these nodes automatically appear in all other
Super Administrators Console Views.
After target discovery or when adding/editing administrators, a Super Administrator may allow
a target to appear on a Regular Administrator's Console.
When launching the Console by connecting to the Management Server, you login as an
Enterprise Manager administrator (which is separate from a database user).
Enterprise Manager administrators can:
•Create events to monitor for problems in their environment
•Be proactively notified, via pager or e-mail, of potential problems
•Create, schedule and publish reports to the Web
•Create jobs to automate routine administrative tasks
In addition, if you are classified as a Super Administrator, you can also:
•Create new administrator accounts
•Discover, refresh and remove nodes
•Grant access to discovered nodes to other non-Super Administrators (aka Regular
Administrators)
•View, modify or delete any event, job or group
•Configure paging and e-mail servers
Page
•Define and modify Management 12
Regions
•Set paging and e-mail blackouts 12
Control Access to Nodes and Targets
• Super Administrators control what targets

appear to regular administrators
• Regular administrators can access only such
targets they are given access
Control Access to Nodes and Targets

When launching the Console by logging into a Management Server, Super
Administrators are able to discover nodes via a Discovery Wizard. As Regular
Administrators do not have access to this functionality, Super Administrators grant
them access to nodes and targets for which they are responsible.
If Super Administrators do not give explicit access to targets to regular
administrators, regular administrators will see no targets when they log onto the
Console by connecting to an OMS.
Super Administrators cannot specify what other Super Administrators can see. By
default, Super Administrators can see all targets discovered.
Example
• Super Administrator, SYSMAN launches the Console by connecting to
Management Server
• SYSMAN discovers nodes N1 and N2. These discovered nodes appear by
default in all other Super Administrator’s Console views
• No nodes appear for other regular administrators, say Tom and Joe
• In order for Tom and Joe to see the nodes and targets in their Console,
SYSMAN would have to grant them explicit access to the nodes and targets that
they should manage.
Note:
Administrators can launch the Console in standalone mode and add/remove
databases to/from the tree. In standalone mode there is no concept of Super
Administrator or Regular Administrator. You only connect to the database as a
database user (e.g. SYSTEM or SYS ) to perform administrative tasks.
Page 13
13
Grant Access to Targets
Grant Access to Targets

To assign or remove targets to regular administrators:
• Click Manage Administrators from the Configuration menu
• Click Grant Access to Targets
• Check the Targets that need to be assigned or removed to the Regular
administrators and click OK
Once a Super Administrator selects targets to assign or hide , the change is not
immediately seen in the Regular Administrators window. The change is applied on
collapse and re-expand of the Administrators Navigator trees.
But any new actions the Regular Administrators perform after customization include
the changes made. For example, if Super Administrator hides a target from
administrator Tom, the change does not get applied immediately to Tom`s Navigator
tree. The change is applied after collapse/re-expand of the tree. However, when Tom
creates a Job or an Event, that target remains hidden.
Demo:
Assigning Targets to Regular Administrators via the Discovery Wizard [http://stc-
sun07:7777/viewlet/assign_targets_discovery.html]
Super Administrators can also grant access to discovered nodes and targets via the
discovery wizard.
• Select Discover Nodes from the Navigator menu and click Next
• Enter the name of the node(s) to be discovered and click Next
• Click Next after discovering the nodes
Page 14
• Select the targets to be assigned to regular administrators and click Finish
14
Note: To grant access during discovery, you must have regular administrators
Management Regions
• Management Region is a grouping of

discovered nodes and Management Servers
• Multiple Management Regions can be defined
in a single repository
• Only Super Administrators have access to
Management Regions functionality
Management Regions
There can be multiple Management Regions defined in a single repository, but a particular node
is a member of one and only one management region. You can assign the Management Server to
be in one and only one management region. However, a Management Region may contain
multiple Management Servers as long as all Management Servers share the same repository.
Page 15
15
Benefits of Management Regions
Useful for:
• Global deployments of Enterprise Manager
framework
• Deployments across LANs and WANs
• Mapping nodes within firewall boundaries
Benefits of Management Regions

You use Management Regions functionality when you have global deployments of
the Enterprise Manager framework or when you have deployments of the
framework across a mixture of LANs and WANs. In these two scenarios,
Management Regions can improve performance over slow networks by allowing
you to assign a subset of Management Servers and a subset of discovered nodes to a
Management Region to prevent cross-regional or cross-network communication.
Example
Company XYZ has an OMS running in England and monitored targets in England.
Also It has an OMS running at its HQ in California and monitored targets in
California.
With previous releases of EM, the Management Server in England could actually
monitor the targets in California. There was no way to bind a Management Server to
the targets. Additionally, if there is a firewall between the Management Server in
England and the monitored node in California, the Management Server and the
nodes will not interact with each other. Management Regions functionality prevents
this cross regional communication and allows users to specify that the Management
Server in England should only monitor targets in England (within a firewall). It
should not monitor the targets in California.
Page 16
16
Create a Management Region
Create Management Regions

To create / edit Management Regions, select Define Management Regions from the
Configuration menu. If you are not a Super Administrator this menu item will not appear.
Select the Add Region icon and enter the name of the management region to be created.
Default Management Region called DEFAULT is created by EMCA
EMCA can also be used to create a new Management Region while configuring a Management
Server.
Note: Only Management Regions without an active Management Server(s) and assigned
node(s) can be deleted.
Page 17
17
Assign Management Servers
Assign Management Servers to a Management

Region
Assign Management Servers

Screen shot above shows how you assign Management Servers to Management
Regions.
A Management Server can belong to only one management region. However,
multiple Management Servers can be in a Management region.
Note:
You cannot remove the last Management Server from a Management Region as it
would leave the Management Region unmonitored.
Page 18
18
Assign Nodes
• Assign Nodes to a Management Region
Assign Nodes
Screen shot above shows how you assign discovered Nodes to Management Region.
Each node can only be in one Management Region. A node cannot be added to a
Management Region unless the Management Region has an active running
Management Server.
Demo:
Creating a Management Region [http://stc-
sun07:7777/viewlet/management_reg.html]
Page 19
19
Comprehensive Reporting
Out-of-the-box reports include:

• Reports identifying current status of
environment, such as
– Service Level Availability
– Outstanding Alerts
– Registered Events
• Reports detailing setup and configuration of
environment, such as
– Events in Library
– Database Instance Configuration
The predefined reports bundled with base Enterprise Manager allow administrators to track the
health of their entire system.
Additional reports available with licensable Packs:
-Application Health Assessment reports allow administrators to see how their system is
performing in real-time, compare that to the past, and trend out to the future. Available
reports with separately licensable Oracle Diagnostics Pack includes
-Real-time System Performance reports such as
-System State at a Glance
-Processes at a Glance
-I/O at a Glance
-Wait Analysis Overview
-Trending reports such as
-Memory Sort Percentage
-Library Cache Hit Percentage
Page 20
20
• Reports are accessible from central location in

Console
– Click ‘Report Definitions’in the navigator
tree to list available reports
– View, edit and publish reports
Comprehensive Reporting (cont’d)

Reporting functionality (i.e. customizing, scheduling and publishing of reports) is only available
when users launch the Console by connecting to an Oracle Management Server; it is not
available when in standalone mode.
A number of predefined reports are supplied with Enterprise Manager. Predefined reports
include:
•Instance Configuration – displays database instance information, SGA and initialization
parameters
•Instance Status – displays database and instance information, number of current users, session
statistics
•Schema – displays available schema objects and disk space used by tables
•Security – displays user information and roles
•Service Level Details – displays detailed service level information for a service or set of
services
•Topology – displays a topological overview of all monitored targets and services.
Note: Reports are also accessible from a central reporting website - this will be discussed in a
later slide.
Page 21
21
Creating Custom Reports
• Create custom reports from either existing

report definition or creating new report
definition

In addition to predefined reports discussed earlier, Enterprise Manager gives the flexibility to
create Custom Reports from either existing report definitions or creating new report definitions
Creating a Report Definition
•Choose Create from the Object menu. The Create Object dialog is displayed
•Select Report Definitions and click Create
•Enter the requisite information
•Click OK to save the report definition or Show Report to view the generated report.
•Create a report like an existing report by selecting Create Like functionality from the
Object main menu.
You need to be connected to the Management Server for this functionality.
Page 22
22
From the Create Report dialog, users can:

• Define SQL queries to specify the data used for
the reports
• Specify how data should be displayed
– Table or chart (pie, bar or line)
– Vertical or horizontal orientation
• Include images in reports (only GIF images)
• Customize reports further with HTML and
JavaScript functions
Page 23
23
Publishing Reports
• Published Reports can be

– Generated on demand
– Scheduled at predefined intervals
• Published reports can be accessed from a
central Enterprise Manager Reporting web site
Publishing Reports
Users should choose to publish a report on demand if it is critical that the reporting website
always contains up-to-date information. This on demand capability allows end users, via the
reporting website, to generate reports real-time. With on demand reports, users know that they
are viewing current information on their monitored enterprise.
Users should choose to publish a report on a scheduled basis if it isn’t critical that the reporting
website remain up-to-date. In addition, scheduling a report to run on a regular or repeated
schedule allows administrators to run time- and/or CPU-expensive reports during non-business
hours.
The Oracle HTTP Server is packaged with the OMS to act as a webserver to serve the published
reports on EM Reporting website.
Configuring Reporting Website
Enterprise Manager automatically installs a preconfigured Oracle HTTP Server with the
Management Server installation. This Oracle HTTP Server will act as the reporting webserver
for the Enterprise Manager Reporting Website. While the HTTP Server is preconfigured, there
are two additional steps that the user must perform in order to access published reports from the
Reporting Website.
Prior to accessing the EM reporting website, user must:
•Change the default password of the Enterprise Manager Administrator
REPORTS_USER
•From the machine running both the OMS and reporting webserver, manually run
oemctl configure rws script – providing the appropriate answers to its
questions.
Page 24
24
Navigating Published Reports
• From the Enterprise Manager Reporting

website home page, users can navigate to a
variety of reports
Page 25
25
Comprehensive Reporting - Example
Comprehensive Reporting – Example

The screen shot above gives an example of Reports for a database
Preferred credentials must be set for the database in order for the report to be generated
successfully.
Examples of Database Reports:
Instance Report [ http://stc-sun07:7777/instance.htm]
Schema Report [http://stc-sun07:7777/schema.htm]
Security Report [http://stc-sun07:7777/security.htm]
Storage Report [http://stc-sun07:7777/storage.htm]
Page 26
26
Discover Multiple Listeners
Discover multiple Listeners on single node

• If multiple listeners are being used within a
database, the Intelligent Agent will discover all
such Listeners
• Requires Intelligent Agent Release 9i
Discover Multiple Listeners

Prior to Oracle9i, if multiple listeners are being used within a database, the
Intelligent Agent would discover the 1st Listener that it discovered for the database.
However, if listeners are running in multiple databases, it would discover all the
listeners.
But, with Oracle9i, if a database has more than one listener the Intelligent Agent
discovers all such listeners.
Page 27
27
Summary
In this lesson you would have understood the

following new features in the Console:
• New look and feel of the Console
• Use the Console in Standalone mode
• Restrict Access to Node Discovery
• Control access to Nodes and Targets
• Management Regions
• Support for Comprehensive Reporting
(customizing, scheduling and publishing
reports)
• Discover multiple listeners on single node.
Page 28
28
Events and Jobs
Page 1
1
Objectives
After this lesson, you should be able to use:

• Event creation enhancements
• Modify events dynamically
• Create user-defined events
• Use the Event Handler enhancements
• Control Blackouts for specific targets
• Use Job System enhancements
Page 2
2
Event Creation Enhancements
• Ability to schedule event evaluations at off-

peak times
• Ability to create a fixit job from the events
dialog
• Ability to register Unsolicited Events like any
other event test
– the option to specify filters for unsolicited
events is now available as an event test
Event Creation Enhancements

These concepts are discussed in the following slides.
Page 3
3
Event Schedules
In EM 9i:
• Events can be evaluated at a specified time
• Resource-intensive events can be scheduled
at off-peak times
Event Schedules
Prior to Enterprise Manager 9i, users control event evaluations through time
intervals. The frequency of time intervals determines how often the event
condition is evaluated. In Enterprise Manager 9i, users have even greater
control over the frequency of event evaluations. Users can specify the
schedule on which the event is evaluated. This is helpful in cases wherein the
administrator may want some resource intensive event conditions to be
evaluated at off-peak times.
Page 4
4
Event Schedules
Event Schedules
The Schedule page allows you to schedule the evaluation of an event. This
could be one of the following:
•On Interval – This allows you to schedule an event evaluation either
immediately after registration or at a specific time. The interval can be a
combination of hours and minutes, or number of days
•On Day of Week – schedule an event on one or more multiple days of the
week (Monday, Tueday )
•On Day of Month – schedule an event on one or more multiple days (1-31)
of the month
Note: Event monitoring is done based on the system time of the Agent.
Page 5
5
Unsolicited Events
• Unsolicited events are events that are detected

and raised by 3rd party scripts
• Third party script notifies Agent via oractl verb
or command
• An event must be registered specifying filters
for the unsolicited event(s) of interest
Unsolicited Events
Unsolicited events provide a way to integrate third party events into the
Enterprise Manager Event system. Such events could be monitoring
conditions that is specific to your environment. You might want to tie these
events into the Enterprise Manager event system in order to leverage its
lights-out, notification capabilities. You can accomplish this by using
Unsolicited Events.
Unsolicited Events are events that are checked by 3rd party scripts and are not
monitored by the Oracle Intelligent Agent. Once these conditions are
detected, the scripts can then send commands to the Agent to let it know that
an event occurred, thereby triggering an unsolicited event.
You can determine which unsolicited events you want to be notified about. To
do this, you should register an unsolicited event via the Console.
In EM9i, when creating the event, you should select the event test called
"Unsolicited Event Test". The parameter for this event test allows you to
specify a filter based on event name. Putting a wildcard value of "*" means
you want all unsolicited events (regardless of name) to be accepted and
passed through.
In EM9i, you can also associate a fixit job for unsolicited events.
This feature requires that you use the Intelligent Agent version 9i.
Page 6
6
Unsolicited Events
Unsolicited Events
In EM 2.x, the option to specify filters for unsolicited events was available as
a checkbox option in the General tab of the Create Event dialog. In EM 9i, the
option to specify filters for unsolicited events is now available as an event
test. The parameters for this unsolicited event test allow you to specify filters
on event name
Creating an unsolicited event
•From the Console’s event menu choose Create Event
•From the Tests page select Unsolicited Event under the Node folder
•Specify the event filter in the parameters page
•Complete the other property pages
•Register the Event
Page 7
7
Create Fixit Jobs From Events Dialog
While creating an event, the user can, from the

events dialog:
• Choose from a list of available fixit jobs
• Create a new fixit job for the event
Create Fixit jobs from Events Dialog

You can associate a fixit job with an event. A Fixit job runs when any event
test in the event triggers. A Fixit job is designed to correct a problem or get
more diagnostic information about a problem. For example, you may want the
Agent to run a job to start the database when the database instance is
shutdown unexpectedly.
Page 8
8
Create Fixit Jobs From Events Dialog
Create Fixit Jobs from Event Dialog

•The user can create a Fixit Job from the Events dialog by clicking the Create
button in the Fixit Jobs tab. This launches the Create Job dialog box pre-
populated with the selected targets
•The newly created job could then be selected as the fixit job for the event
•In order for the fixit job to be run when the event triggers, the newly created
job must be successfully submitted with a status of ‘Fixit’. You can check the
status of the job by selecting Jobs in the Console navigator pane and clicking
on the Active tab. The status ‘Fixit’indicates that the Intelligent Agent has
successfully completed the job submission process
Page 9
9
Investigating Event Occurrences
• If an event triggers, advice and /or related

charts are available to investigate and solve
the problem
• Requires 9i Agent

An example for the above feature is discussed in the next section.
Page 10
10
Investigating Event Occurrences- Example

For example you set up an event for monitoring the buffer cache hit %. When
an event triggers, you can do the following:
•Right-click the event in the Alerts page and select Edit Event Occurrence
•Select the event and click View Chart and /or Advice to solve the problem.
This requires the Oracle Diagnostic Pack Release 9i to be installed and needs
a 9i Intelligent Agent.
Page 11
11
Dynamic Modification of Events
• Allows modification of registered events

without de-registration / re-registration
• Full modification supported for 9i agents
• Limited modification allowed for pre-9i agents

Dynamic modification of events allows you to actively modify a registered
event without the need to de-register and re-register the event. For example,
you can add an additional database to be monitored to the existing event.
The extent of event attributes that can be modified depends on the version of
the agent used. If you have older versions (pre-9i) running on different targets,
they only support limited modification.
To modify a registered event:
•Select the Event that needs to be modified from the Registered tab of
the Events detailed page
•Right-click on the selected event and click Edit Event
•If additional targets are to be monitored, select the General tab and
add additional targets as required
•If additional tests are needed, select the Tests tab and add additional
tests as required. Click Apply
•Verify the Event modifications summary that is displayed and click
OK to effect the changes.
To find the version of the agent, look at the property page of the target node
that is running the agent.
Page 12
12
• Only the OWNER of the event can modify the

registered event.
• For event owners:
– Full modification allowed if all targets are
running with 9i agents
– Limited modification allowed if at least one
target is running with pre 9i agent (Common
denominator is used)
• Upgrade agents to 9i to allow full modification
Dynamic Modification of Events (continued)

•The Owner is shown under the “Owner” column of the Registered page of the events pane or via the
Owner field in the Access property page of the Edit Event dialog
•Other Administrators may only modify event permissions depending on their level of access to the
event
Demo:
Dynamic Modification of Events [ http://stc-sun07:7777/viewlet/dynamic_mod_events.html]
Page 13
13
Event Attributes that can be modified
Event All All Targets Targets

Attributes to Targets with 9i with pre-9i
be Changed with Agents or 9i
pre-9i Agents
Agents
Event Yes Yes Yes
Description
Monitored Yes Yes Yes
Targets
Adding or No Yes No
deleting
Event Tests
Changing No Yes No
Test
parameters

All modifications will be applied against all targets for the event
Since modifications apply to all targets, then when an event has some targets
running pre-9i agents and other targets running 9i agents, then only the
attributes that can be modified across all Agent versions will be allowed.
(Common denominator rule)
Pre-9i Agents allow only limited modification to existing registered events.
The only exception to this is if the target running pre-9i Agent has been newly
added to the list of monitored targets. In this case, full modification of that
target is allowed because it will essentially become a new event registered
against the target.
Page 14
14
Event All All Targets Targets

Attributes to be Targets with 9i with pre-9i
Changed with pre- Agents or 9i Agents
9i
Agents
Schedule – No Yes No
polling
frequency and
start time
Permissions Yes Yes Yes
Enabling/Disabl No Yes No
ing SNMP traps
Selecting or No Yes No
Creating Fixit
job for the
event
Event Attributes that can be modified (cont`d)

The Event dialog will automatically enable or disable property pages
depending on the changes supported. For example, if prior to any
modification,the event has a mix of targets ( some running pre 9i and
others running 9i agents) then the Tests, Parameters, Schedule, Access and
fixit Jobs property pages will be disabled for editing.
If, during the edit session you remove the targets running the pre 9i agents,
then the Tests, Parameters, Schedule, Access and Fixit Jobs property
pages will now allow editing since the remaining targets support editing of
those attributes.
If you would like to modify an attribute that is not dynamically modifiable by
a pre 9i Agent (e.g Test Parameters), then you can use the following
workaround when modifying the event:
(1) Allow full modification by removing all targets that are running pre- 9i
Agents
• In the General tab, remove the targets that are being monitored
by pre- 9i Agents. You can determine the Agent version running
on the target node by looking at the Node’s property page in the
Console
(2) Put in the changes required
• After the above step, all remaining targets should be running 9i
Agents, hence full modification should be allowed. You can now
put in the changes required
(3) Apply the changes
• Note this will causePagethe 15
event changes to be applied to all the 9i
targets, and the event to be de-registered from the targets you 15
removed in step (1)
User Defined Events
• Allows you to integrate any event monitoring
script (in any language) with the Event System
• Allows customization of monitoring
• Extends the benefits of the Event System to
existing user-defined monitoring scripts
User Defined Events

User Defined Events allow you to integrate any monitoring script with the Event System. The
Agent will run any specified script which you may define to check for conditions specific to
your environment. This allows much flexibility and customization to the type of event
conditions monitored by the Agent. This also extends the benefits of the Event System
(cooperative monitoring among different administrators, notifications, history etc) to existing
monitoring scripts.
The monitoring script itself should include the following:
•Logic to check the specific event condition or value of the monitored metric (e.g.
amount of free disk space)
•Logic to return the current value of the metric or status of the event and any associated
message
If the current value of the metric is returned, then in the Create event UI, the user must also
specify critical and warning thresholds against which the current value is compared.
Alternatively, the script can evaluate and return the status of the event (clear, critical, warning,
error) which is then propagated back and triggered accordingly.
The script itself can be written in any language, as long as the runtime requirements needed by
the Agent to run the script are available on the monitored node
Page 16
16
User Defined Event Tests
User Defined Event Tests

Script:
Specify the monitoring script. It can reside either on the monitored node or entered directly into
the Create Event UI.
If the script resides on the monitored node, enter the fully-qualified name of the script to be
executed.
If the script is to be entered directly into the UI, type in the script commands. Alternatively you
can use your favorite editor to type in the script and save it to a file, then load it into the Create
Event UI via the “Browse” button.
Script Result:
The script should return either the value of the monitored metric or the status of the event.
Select “Value” if the script returns the value of the monitored metric.
Select “Event State” if the script evaluates the event condition and returns an event status: clear,
critical, warning, error.
If “Value” is chosen for Script Result, the following additional parameters are required to
determine how the event is evaluated:
Operator: specify the operator Enterprise Manager should use to compare the monitored metric
value against the thresholds. Comparison operators include == (equal to), < (less than), >
(greater than), <= (less than or equal to), >= (greater than or equal to), != (not equal to).
Critical Threshold: the value against which the monitored metric is compared. If the
comparison holds true, the event triggers at a Critical level.
Warning Threshold: the value againstPage which 17
the monitored metric is compared. If the
comparison holds true, the event triggers at a Warning level 17
Event Handler
• Extends the Event System by allowing

customizable responses to event occurrence
• Allows the user to respond to a triggered
event by
– Logging event information to a file and/or
– Executing any O/S command
• Allows integration of 3rd party systems
• Implemented as a service inside Oracle
Management Server
– Takes advantage of load-balancing and
scalability features of Management Server
Event Handler
Business practices may dictate that responses to event occurrences be performed in certain
ways. For example, if the database updown event triggers, administrators may want an
inhouse trouble-ticket be opened to respond to this event occurrence. The ability to provide
customized responses to event occurrences can be achieved by using the Event Handler.
In EM9i, the Event Handler is a component of the Oracle Management Server (OMS) and has
been pre-configured with some default parameters. In order to start up the default
configuration, you do the following:
• Enable the Event Handler
Make sure the OMS is not running.
% oemctl stop oms <superuser>/<password>
To enable the Event Handler:
% oemctl enable eventhandler
• Start the Event Handler by starting the OMS
Because the Event Handler is part of the OMS, it starts whenever the OMS is started
and it stops whenever the OMS is stopped.
% oemctl start oms
• To find out the configuration of the Event Handler, run the following:
% oemctl dump eventhandler
The default configuration will log all events to a file called eventhandler.log. This file is
located in the %ORACLE_HOME/sysman/log directory.
Page 18
Note:
18
Refer to the Enterprise Manager Administrator's guide for more details on changing the
Blackouts
Blackouts allows users to:

• Suspend email and paging services with
reference to a managed target
• Suspend events, jobs and data collections on
targets in order to complete maintenance
operations
Blackouts
Paging/Email blackout deactivates email and paging, thus preventing Administrators from being
flooded with email and pages if a managed service is brought down. Super administrator
privileges are required to schedule paging/email blackout.
Example
A managed node is brought down for scheduled maintenance. In such a case the super
administrator can schedule a paging/email blackout for that target to prevent paging/email
notification during the maintenance period.
From the user interface, users can only suspend email and paging with reference to a managed
target. Suspension of monitoring activity on targets is done from the command line.
Page 19
19
Enabling Paging/Email Blackouts
Enabling Paging/Email Blackouts

To enable blackouts either select Paging/Email blackout from the menu bar or
right-click on the desired object and select Paging/Email blackout.
Select Occurrence – The administrator can set the occurrence for the blackout.
The options available are:
•Once
•On Interval
•On Day(s) of week
•On day(s) of month
When On Day(s) of week or On Day(s) of month option are selected, each
day terminates at 12 A.M. For example, if you wish to schedule a blackout
that begins on Wednesday for 4 hours and beginning at 11 P.M, then you
must define two blackout periods.
•Wednesday from 11 P.M to 11:59 P.M
•Thursday from 12:00 A.M to 3 A.M
Total Paging/Email blackout specifies that a blackout be started immediately
and with an indefinite duration.
Page 20
20
Target Blackout Options
Using the command line interface users can

blackout a target with the following options or
a combination of these:
• All jobs related to a target
• All events related to a target
• All collections related to a target
Target Blackout options (continued)

Blackouts and Jobs
When a user blacks out the job system for a target all registered and submitted
jobs will not get scheduled and run for the period of the black out.
If an Immediate job is submitted during the black out, it will fail. An interval
job, that is, a job submitted at regular intervals would be skipped during the
blackout. Job skipped notifications are sent to Oracle Management Server
until blackout is over.
If a job is submitted and gets scheduled prior to a blackout, then the job would
run.
E-mail and paging notification will be implicitly suspended for jobs against
the target
Blackouts and Events
When a user blacks out an event system for a target, all registered events
would not be evaluated.
E-mail and Paging services will be implicitly suspended for events against the
target
If the event system is not blacked out for a target but the job system is, all fix-
it jobs associated with the event would still be run
Blackouts and Collections
When a user blacks out collections for a target, all current historical
collections will be suspended. Loading of data collected prior to the blackout
would continue. Loading of such data will continue even if the Capacity
Page
Planner database is blacked out, yet is21
up and running. Loading of data into
Historical database is not affected by blackouts on collections. 21
Command Line Interface Tool
usage
agentctl start|stop|status blackout
[<target>][-d/uration <timefmt>]
[-s/ubsystem <subsystem>]
Usage
target – specifies the name of the target such as node, database, listener.
Default value is node
timefmt – duration is specified as [days] hh:mm
subsystem - jobs, events, collections are the subsystems. Defaults to all
subsystems if none is
specified
Page 22
22
Example
Start blackout
•agentctl start blackout
•agentctl start blackout wwed165-sun –d 1
2:15 –s events jobs
Stop blackout
•agentctl stop blackout
•agentctl stop blackout wwed165-sun
Show status of blackouts
•agentctl status blackout
•agentctl status blackout wwed165-sun
Example
•If you start a blackout without specifying a target or a subsystem, it implies blackout for all
subsystems for the entire node. A blackout on the node will apply to all discovered targets on
that node. The blackout will exist until you stop the blackout using the command, agentctl
stop blackout
•Specifying target and subsystems - blackout is started on a target database, wwed165-sun for a
time period of 1 day 2 hours and 15 minutes on events and jobs, as shown above.
Page 23
23
Compatibility
• Intelligent Agent 9i supports the full

functionality of blackouts
• If a user has Intelligent Agent older than
version 9i, then only e-mail and paging
blackouts are available
Page 24
24
Job System Enhancements
• Targets can be added/removed dynamically

from submitted jobs
• Override node preferred credentials
• Validation of credentials
• Skipped Job notification
Job System Enhancements

These concepts are discussed in the following slides.
Page 25
25
Add Targets Dynamically
Add Targets Dynamically

In some situations administrators might want to dynamically add targets to an
already submitted job.
Benefits
No need for de-registering jobs. This is particularly useful for long running
jobs for which additional targets are to be added.
Example
An administrator has setup weekly database backup jobs for all managed
databases. A new database comes online, and the administrator decides to
have weekly backups for this too Instead of creating a new job for this, he
may use the existing backup job and add the new database as new target for
the job.
This ability to dynamically add (or remove) targets from jobs is supported in
EM 9i.
This feature works with all supported versions of the Agent that may be
running against the various targets.
Demo:
Adding Job Targets Dynamically [http://stc-
sun07:7777/viewlet/dynamic_mod_jobs.html]
Page 26
26
Node Credentials Override
• Node Credentials used for the entire job can be

overridden
Node Credentials Override

In EM9i, the default node credentials used to execute a specific job can be
overwritten. This may be useful in situations wherein a particular job needs
to be run with special credentials that have more privileges than a regular
user. You would like to use these special credentials to run this job, but for
security reasons, you do not want these special credentials to be used as the
default credentials to run any other job.
Page 27
27
Validation of Credentials
• Required credentials are checked before the

job is submitted
• Required credentials include:
– Node credentials, required to run any job
– Additional credentials (e.g. database
credentials), may be required depending on
the job task
• Required credentials are specified using the
Configuration menu
Validation of Credentials
Both the Job and the Event System require that preferred credentials be set for
the targets or services against which jobs are run or events are registered. If
preferred credentials are not set, the registration of jobs and events fail.
When a job is submitted and the required credentials are not set, then an error
is raised and an option is provided to set the required credentials.
Demo:
Validation of Credentials [ http://stc-sun07:7777/viewlet/valid_cre.html]
For this demo, Preferred Credentials are not set against database and node.
Administrator TOM creates a Job and submits it
•Select Create Job from the Job menu
•Supply the Job Name, select database as the Target Type and select the
targets to be monitored
•Click on the Tasks tab
•Select Run SQL*Plus script as the Job Task
•Click on the Parameters tab and enter a SQL script in the Script Text box
•Click Submit
•You get a message stating that Preferred Credentials are not set and you are
prompted to set credentials
•Click Set Credentials. Select the targets for which preferred credentials are to
be set and supply the username and password. Click OK
PageCredentials
•Click Close to close the Preferred 28 Not Set dialog box
•Click Submit to re-submit the job. 28
Skipped Job Notifications
• A Notification is sent when a job is skipped

due to one of the following reasons:
– Agent unavailability
– Length of prior job executions
– Target blackout
Skipped Job Notifications

If the Agent is unavailable during a scheduled job execution, a skipped job
notification will be sent when the Agent becomes available.
If a blackout for a target was in effect during the period when a job was
scheduled to run, a skipped job notification will be sent each time the job was
supposed to run.
If a prior execution of a recurring job is not complete by the time the next
execution is scheduled to start, then the next execution is skipped. Only
when the execution of a job completes does the next scheduled execution
begin. Hence if a job takes some time to execute, there may be job
executions that are skipped. Notifications will be sent for all job executions
that were skipped due to this reason.
Example
If a job is scheduled every hour starting at 1 am, then if the first execution is
still running at 2 am, then the 2 am-scheduled job will be skipped. If the first
execution finally completes at 3:30 am, then notifications will be sent relating
to the 2 am and 3 am job executions that were skipped.
Page 29
29
Summary
In this lesson you would have understood the

following new features in Events and Jobs:
• Event creation enhancements
• Dynamic Modification of Events
• User-Defined Events
• Event Handler enhancements
• Blackout utility enhancements
• Job System enhancements
Page 30
30

Installation and Configuration

Uploaded by

Copyright:

Available Formats

Installation and Configuration

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation and Configuration

Uploaded by

Copyright:

Available Formats

Installation and Configuration

After this lesson you should be able to

Enterprise Manager Configuration Assistant

• Oracle Enterprise Manager Migration

Console Integ Thin OMS Mgt Other EM EM

Win 98 Yes Yes Yes No Yes Yes No No

Sun Yes Yes No Yes No Yes Yes No

HP-UX Yes Yes No Yes No Yes Yes No

IBM AIX Yes Yes No Yes No Yes Yes No

Compaq Yes Yes No Yes No Yes Yes No

Intel Yes Yes No Yes No Yes Yes No

Intelligent Agent Installation

• Run nmumigr8 utility to migrate existing jobs,

Intelligent Agent Migration

Startup and shutdown of the agent performed

Startup and Shutdown the Agent

Intelligent Agent – Log files

After this lesson you should understand:

After this lesson, you should be able to:

Enterprise Manager Support for Oracle9i Database Features

Persistent Parameter File (SPFILE)

Creating the SPFILE

Creating init.ora file from SPFILE

Startup Using the SPFILE

• Simplifies and automates the management of

Creating an Undo Tablespace

• Used to represent characters in any language

Defining Unicode Columns

• Oracle9i includes an advisory mechanism for

Buffer Cache Sizing Advice

Buffer Cache Size Advice View

• Specify default temporary tablespace to store

Default Temporary Tablespace

Creating Default Temporary Tablespace

• Oracle9i supports the creation of databases

Multiple Block Sizes

• Controls the time to recover from an instance

Mean Time to Recovery

Mean Time to Recovery (continued)

• RMAN scripts can be submitted and scheduled

Backup and Recovery Enhancements

• Topology map displaying individual queues

• Support for single master quiesce for

• Know what aspects of Summary Management

• Recommends and builds summaries to

Summary Advisor Workload

• Oracle9i provides integrated data warehousing

• Easy-to-use wizard to create cubes

Support for OLAP Cubes

Cube Topology Viewer

• Easy-to-use wizard to create normal and time

Support for OLAP Dimensions

Report generation enhancements allow you to

HTML Database Reports

Database Configuration Report

In this lesson, you should have learned how to:

After this lesson, you should be able to:

• Two pane, master/detail view of the environment

New Console Look-and-Feel