Document ID: 45412.1
Subject: Enterprise manager 1.2.2 install + config
Last Modified: 21 Apr 97
Author: COAKSHOT
Oracle Enterprise Manager
OEM 1.2.2 Installation and Configuration
This document covers two possible setups for OEM 1.2.2:
-Setting up OEM on a laptop/PC with a local repository and a local NT
Intelligent Agent
-(one machine complete configuration)
-Setting up OEM with a remote repository and/or a remote managed node
-(multiple machine configuration)
Setting up OEM on a PC with a local repository and a local NT Intelligent Agent
(one machine complete configuration)
Installation and configuration of EM 1.2.2 on a single Windows NT machine
System Requirements
- Windows NT 3.51 or 4.0 (with TCP/IP services)
- Pentium, 32Mb memory (recommended)
- Approximately 50Mb disk space (suggested)
Oracle Software needed:
- EM 1.2.2 CD (includes SQL*Net 2.3 Client and the Intelligent Agent for NT)
- Oracle Enterprise Server for Windows NT v7.3.2 CD
Pre-installation steps
1. Install the Oracle Server version 7.3.2 and create a starter database.
This database will be used to create the repository.
2. Install SQL*Net Server 2.3 only.
EM Installation
== ============
1. Install the following from the EM 1.2.2 CD (32 bit)
a. Enterprise Manager 1.2.2
Oracle Intelligent Agent
answer "yes" to the software distribution question if you'd like to have the
software you install with Oracle Software Manager to
be shared by clients (i.e. a "shared" 16-bit oracle_home)
answer "no" to the software distribution question if you'd like to have a stand-
alone 16-bit oracle_home (recommended if you are
not familiar with OSM)
SQL*Net Client 2.3.x (note: install this component from the EM CD even if you
have a newer version already installed)
TCP/IP Adapter 2.3.x (note: install this component from the EM CD even if you
have a newer version already installed)
EM Performance Pack, EM Documentation, Replication Manager etc. (optional)
Note: you may get warnings that you don't have a topology.ora or tnsnames.ora
file.
Ignore them.
2. Install Network Manager 3.1.0.3 (run the Installer from WINDOWS\INSTALL
directory; Network Manager is a 16 bit application,
install it in your local 16 bit oracle_home)
EM Repository setup
Start the local database services (from the Control Panel Services applet)
Launch the Security Manager tool against your local database logging in as
sys/change_on_install.
This is a standard database application distributed with EM, installed in the
EM Program Group.
Open the "Users" folder
Highlight SYSTEM user
From the menu select "User" "Create Like..." and create a new user with system
privileges.
After user has been created.
Run the 32-bit Installer from the CDROM and select "Repository Builder"
Select "Create EM Repository" and "Create Performance Pack Repository" (if you
installed Performance Pack)
Select as the owner of the repository the database user you created above.
Leave the database alias blank (it will default to the
local database).
Console Configuration
1. Generate the configuration files. Using Network Manager
is strongly recommended in order to generate consistent files.
Ideally you should use Version 3.1.0.3
For easy instructions on creating a minimum configuration with Network Manager
see section below entitled
"USING NETWORK MANGER FOR ORACLE ENTERPRISE MANGER"
Locally managed node configuration
======= ======= ==== =============
1. Use SQL*Worksheet from the EM Program Group and connect as
sys/change_on_install or internal to the local database.
2. Run catsnmp.sql from oracle_home\network\agent\config
(i.e. type @c:\orant\network\agent\config\catsnmp)
3. From the NT User Manager tool create a new user (or use an
existing one) and grant it 'login as batch job' privilege.
Here are the steps to create this NT user:
Bring up the "User Manager" from the Administrative Tools program group.
Create a new NT local user (make sure this user does not have to change their
password at next logon)
Under Policies User Rights, click on "Show Advanced User Rights" . Look for
"Logon as a batch job" and select it. Add this right to
the user above.
--------------------------------------------------------------------------------
-----------
To complete:
Start the TNSListener and the Oracle Intelligent Agent from the Services
panel.
2. Bring up the EM Console (login as the owner of the Repository) and verify
that the services you have (the database and listener)are listed in the
Navigator.
3. Under FilePreferences set the preference for your node to the user you
gave the "logon as batch job" privilege above.
4. To verify the communication between the Console and the managed node,
register an UpDown Node event for your host. Start the Daemon Manager and:
- in the Navigator Tree choose Monitored Notes, highlight the appropriate
node
- in the Menu choose Node and Ping Agent
You should receive a message about the daemon contacting the Agent.
5. Schedule a simple Job (Node type, for ex.) and verify that it runs and
completes correctly.
Setting up OEM with a remote repository and/or a remote managed node
(multiple machine configuration)
System Requirements
For the Windows NT/ Win95 Console
- NT 3.51 or Win 95 (with TCP/IP services)
- Pentium, 16Mb memory (32 MB recommended)
- Approximately 20 Mb disk space (suggested)
For repository:
- any Oracle database, on any platform (tests have been performed only with
Oracle 7.2 and up versions of the database)
For the Oracle Intelligent Agent
- see platform specific documentation (the Intelligent Agent README)
Pre-installation steps
1. Install the Oracle Server version 7.2.x or 7.3.x on a remote machine and
create a database OR, use an existing remote database.
This database will be used to create the repository.
2. Install SQL*Net Server 2.x on the above machine; if you plan to also
manage this database via EM jobs and events you MUST install SQL*Net
3. Decide what platform/databases you will be managing (can be on Win NT or
UNIX, platforms that have Oracle Intelligent Agent available). If you plan
to also manage these databases via EM jobs and events you MUST install
SQL*Net 2.3
EM Console Installation
1. Install the following from the EM 1.2.2 CD (32 bit)
Enterprise Manager 1.2.2
SQL*Net Client 2.3.x (note: install this component from the EM CD even if you
have a newer version already installed)
TCP/IP Adapter 2.3.x (note: install this component from the EM CD even if you
have a newer version already installed)
EM Performance Pack, EM Documentation Replication Manager etc. (optional)
2. Install Network Manager 3.1.0.3 (run the Installer from WINDOWS\INSTALL
directory; Network Manager is a 16 bit application,
install it in your local 16 bit oracle home)
Generate the configuration files. Using Network Manager
is strongly recommended in order to generate consistent files.
Ideally you should use Version 3.1.0.3
For easy instructions on creating a minimum configuration with Network Manager
Agent Installation
For Win NT: install the Intelligent Agent from the EM 1.2.2 CD
answer "yes" to the software distribution question if you'd like to have the
software you install with OSM to be shared by clients
(i.e. a "shared" 16-bit oracle_home)
answer "no" to the software distribution question if you'd like to have a stand-
alone 16-bit oracle_home (recommended if you are
not familiar with OSM)
For UNIX: install the Intelligent Agent from the 7.3.2.x Server distribution
Verify that there are no additional patches available for that
platform.
EM Repository setup
1. Start up the database used for repository.
Start the listener for this database.
Launch the Security Manager tool against your local database logging in as
system/manager. This is a standard database application
distributed with EM, installed in the EM Program Group.
Open the "Users" folder
Highlight SYSTEM user
select UserCreate Like and create a new user with SYSTEM privileges
Run the 32-bit Installer from the CDROM and select "Repository Builder"
Select "Create EM Repository" and "Create Performance Pack Repository" (if you
installed Performance Pack)
Select as the owner of the repository the database user you created above.
Enter the repository database alias.
Note: the alias to the repository should be in the tnsnames.ora you created
above.
Managed node configuration
1. Use SQL*Worksheet from the EM Program Group and connect as
sys/change_on_install or internal to all the databases to be managed.
Run catsnmp.sql from oracle_home\network\agent\config against all these
databases.
3. For NT only: From the NT User Manager tool create a new user (or use an
existing one) and grant it 'login as batch job' privilege.
Here are the steps to create this NT user:
Bring up the "User Manager for Domains" from the Administrative Tools program
group.
Create a new NT local user (make sure this user does not have to "change
password at next logon")
Under Policies User Rights, click on "Show Advanced User Rights" . Look for
"Logon as a batch job" and select it. Add this right to
the user above.
4. Start the Oracle Intelligent Agent:
On Win NT: from the Services Panel start OracleAgent
On UNIX: use the lsnrctl utility - lsnrctl dbsnmp_start
Start the Oracle TNSListener(s) (lsnrctl start or,
on Win NT , from Control Panel Services)
To complete:
Bring up the EM Console and verify that the services you have (the databases
and listeners) are listed in the Navigator.
Under FilePreferences set the preferences for all your Win NT nodes to the
user(s) you gave the "log on as batch" privilege above.
To verify the communication between the Console and the managed node,
register an UpDown Node event for your host. Start the Daemon Manager and:
- in the Navigator Tree choose Monitored Notes, highlight the appropriate node
- in the Menu choose Node and Ping Agent
You should receive a message about the daemon contacting the Agent.
Schedule a simple Job (Node type, for ex.) and verify that it runs and
completes correctly.
================================================================================
========
USING NETWORK MANGER FOR ORACLE ENTERPRISE MANGER
================================================================================
========
A few easy steps to create the minimum required configuration files.
Start Network Manager
1. Select "New" from the File menu.
2. Answer YES to "Would you like a walk through a configuration of a network
definition?"
3. Select:
Flat naming space with no domains
Single Protocol: select TCP/IP
Addresses resolved via configuration file
OK
4. "The next property sheet allows configuration of a node" OK
Name of your node/machine (e.g. MY-PC)
Note: Use capital letters for the node names, to be consistent with
the naming requirements for OSM
Domain: world
Type: select User defined (for a Win NT node)
Click on the Communities tab:
select TCP.world
Add
OK
5. Would you like to create another node? No
"Next property sheet allows configuration of a listener OK
Fill out the following tabs:
General-Name: LISTENER (leave the default)
Node: should list the node you defined, leave it selected
Leave the rest as default (no password etc.)
Addresses tab - select Create OK (it will take the TCP community and port)
Databases tab - since you have not created one, select Create.
Name- for e.g. mydb
Node- should list the node you created in step 4.
SID- e.g. ORCL
Listeners tab - should list LISTENER_<node>.<world>
(leave it selected)
Next tab, SNMP, click on SNMP visible
(service index should be 2)
Leave the rest of the options as default
OK
This will place the new database in the Selected list
and return you to the "Listener" definition folder.
Tracing tab - Trace level: OFF
Trace file name: leave blank, it will take the default
Trace Directory: C:\orant\network\trace (or, your
ORACLE_HOME\network\admin)
SNMP tab - check "SNMP visible" checkbox (service index for the listener should
be 1)
Leave the rest of the tabs as default
OK
6. Would you like to create another listener? NO
"Configuration of the network is now complete" select OK
Save changes to the configuration? NO (not yet). A warning will be displayed
that "generate failed because the network has not been
saved"
That's OK.
8. Select from the menu CreateOEM Agent
General- Agent name: default is AGENT (leave it)
Node: select from the pull down menu the node you just
created (e.g. MY-PC.world)
Addresses tab - click on Create
Community: should be TCP.world (leave it)
Host: leave the one selected (ex: MY-PC)
Port: use 1999 (it can be any port not in use; 1999 is the default)
OK
click on Create again, same as above but use port 1998
Administration tab - Agent trace level: OFF
Agent trace mask: 106
Agent trace directory: c:\orant\network\trace
Agent trace file: can leave blank, will take default. OK
9. File Validate
If "All object are valid" go to step 10.
10. Select File Generate
Save changes to "Untitled1"? YES
Save Network definition: File OK
Select a directory you have write access to. (e.g.c:\orawin\network\tmp)
Note: it doesn't matter what directory you write these files to, you are
moving them to the proper locations later.
enter a file name (e.g. mynet.net) OK
This will generate all the required files.
11. Use File Manager to look at all the files and make some minor
modifications:
a) take a look at the topology.ora file. All the node names have
a ".world" appended to them. Remove that domain ONLY.
For example: MY-PC.world should be MY-PC, to be
consistent with all the other files.
Note: this step is optional, it is just for consistency reasons.
b) optional- add these daemon tracing parameters to sqlnet.ora:
daemon.trace_mask = (106)
daemon.trace_directory = c:\orant\network\trace
daemon.trace_level = OFF
c) Network manager does not add the ORACLE_HOME info in snmp.ora.
This is required ONLY if you have multiple oracle homes on the
same machine (host). If you do, add by hand the following for each
database/instance you have. For example:
snmp.oraclehome.test.world = c:\orant
snmp.oraclehome.mydb.world = c:\orant
Note: step 11 will not be needed in the future; Network Manager 3.1.0.5 will
fix 11 a), b) and c) above.
2. Verify the files you just created with the following sample files.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
################
# Filename......: listener.ora
# Name..........: my-pc.world
# Date..........:
################
SQLNET.AUTHENTICATION_SERVICES = (NONE)
USE_PLUG_AND_PLAY_LISTENER = OFF
USE_CKPFILE_LISTENER = OFF
LISTENER =
(ADDRESS_LIST =
(ADDRESS=
(PROTOCOL=IPC)
(KEY= mydb.world)
)
(ADDRESS=
(PROTOCOL=IPC)
(KEY= ORCL)
)
(ADDRESS =
(COMMUNITY = TCP.world)
(PROTOCOL = TCP)
(Host = MY-PC)
(Port = 1526)
)
)
STARTUP_WAIT_TIME_LISTENER = 0
CONNECT_TIMEOUT_LISTENER = 10
TRACE_LEVEL_LISTENER = OFF
TRACE_DIRECTORY_LISTENER = c:\orant\network\admin
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = mydb.world)
(SID_NAME = ORCL)
(PRESPAWN_MAX = 10)
)
)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
################
# Filename......: tnsnames.ora
# Name..........: LOCAL_REGION.world
# Date..........:
################
mydb.world =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = TCP.world)
(PROTOCOL = TCP)
(Host = MY-PC)
(Port = 1526)
)
)
(CONNECT_DATA =
(SID = ORCL)
(GLOBAL_NAME = mydb.world)
)
)
########### Agent Addresses ###########
AGENT_MY-PC.world =
(DESCRIPTION =
(ADDRESS =
(COMMUNITY = TCP.world)
(PROTOCOL = TCP)
(Host = MY-PC)
(Port = 1999)
)
)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
################
# Filename......: sqlnet.ora
# Name..........: TCP.world
# Date..........:
################
AUTOMATIC_IPC = ON
TRACE_LEVEL_CLIENT = OFF
SQLNET.EXPIRE_TIME = 0
NAMES.DEFAULT_DOMAIN = world
NAME.DEFAULT_ZONE = world
SQLNET.CRYPTO_SEED = "-1426537372-1418125346"
daemon.trace_mask = (106)
daemon.trace_directory = c:\orant\network\trace
daemon.trace_level = 16
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
################
# Filename......: topology.ora
# Name..........: LOCAL_REGION.world
# Date..........:
################
#
#
# Services for node: MY-PC.world
#
LISTENER_MY-PC.world = (ORACLE_LISTENER, MY-PC)
mydb.world = (ORACLE_DATABASE, MY-PC, LISTENER_MY-PC.world)
agent_MY-PC.world = (ORACLE_AGENT, MY-PC)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
################
# Filename......: snmp.ora
# Name..........: my-pc.world
# Date..........:
################
NMI.TRACE_LEVEL = OFF
NMI.TRACE_MASK = (106)
NMI.TRACE_DIRECTORY = c:\orant\network\trace
NMI.TRACE_FILE = agent.trc
DBSNMP.ADDRESS = (DESCRIPTION=(ADDRESS=(COMMUNITY=TCP.world)(PROTOCOL=TCP)
(Host=MY-PC)(Port=1999)))
DBSNMP.SPAWNADDRESS = (DESCRIPTION=(ADDRESS=(COMMUNITY=TCP.world)(PROTOCOL=TCP)
(Host=mfulford-PC)(Port=1998)))
SNMP.VISIBLESERVICES =(LISTENER_MY-PC.world,dh_db.world)
SNMP.INDEX.LISTENER_mfulford-PC.world = 1
SNMP.INDEX.dh_db.world = 2
SNMP.SID.dh_db.world = ORCL
#optional parameter:
snmp.oraclehome.dh_db.world = c:\orant
+++++++++++++++++++++++++++++++++++++++++++++++++++
Copy the configuration files (tnsnames.ora, sqlnet.ora, listener.ora,
snmp.ora, topology.ora) to the ORACLE_HOME\NETWORK\ADMIN directory.