| Lesson 7 | Start and stop the OEM agents on remote servers |
| Objective | Start and stop remote Intelligent Agents. |
Start and stop the OEM agents on Remote Servers
We need to distinguish between the SNMP agent and a standard Intelligent Agent. As a rule of thumb, an SNMP agent is used only for monitoring cross-protocol communications between Oracle servers that reside on different types of operating system platforms.
For example, the SNMP agent would be used to monitor an Oracle database running on an IBM mainframe.
The first step in starting the SNMP agent is to ensure that no other SNMP components are running.
The main components are the master_peer, encap_peer, and SNMPd. If any of these processes are running, use the ps command to find them, and the kill command to terminate them.
For example:
ps -ef | grep SNMP
checks to see if the SNMP Master Agent is running.
The agent must be started with “root” authority. This is performed by issuing the start_peer -a command.
For example:
cd $ORACLE_HOME/network/SNMP/peer
su root
./start_peer -a
This command starts three server processes. You can then use the ps command to determine if all three processes were started:
ps -aux |grep peer
ps -aux |grep SNMPd
ps -ef | grep SNMP
After executing this command you will see the standard UNIX process lists for all SNMP processes.
If you are in a non-SNMP environment you can use the listener control utility (lsnrctl) utility to start and stop the intelligent agent.
- To start the intelligent agent: issue the UNIX command
lsnrctl dbsnmp_start.
- To stop the intelligent agent issue the UNIX command
lsnrctl dbsnmp_stop.
The next lesson discusses how to customize Oracle alerts and reactions.
