Stop the Agent, OMS, and Database Using Line Commands
You should these commands, in this sequence, to stop the Enterprise Manager Agent, the OMS, and the Oracle database using by Enterprise Manager prior to deinstalling any product.
On the machine where the database that is being used by Enterprise Manager is running, stop the database using these commands:
sqlplus '/as sysdba'shutdown immediateOn the machine where the database that is being used by Enterprise Manager is installed, stop the database listener using the
lsnrctl stopcommand. This command is run from the/oracle/home/bindirectory. For example, your/oracle/home/bindirectory and command line might be:/u01/app/oracle/home/bin/lsnrctl stopStop OMS using the
stop omscommand, which stops both the Admin Server and the OMS Server. This command is run from theoms/bindirectory. For example, youroms/bindirectory and command line might be:/u01/app/emgc12/oms/bin/emctl stop omsStop the Management Agent using the
stop Agentcommand. This command is run from the bin directory of the agent installation directory. For example, your/bindirectory and command line might be:/u01/app/emgc12/agent/agent_inst/bin/emctl stop agentVerify there no additional Oracle processes are running using this command:
ps –r | grep oracleNote: A likely example of an Oracle process that might be running is for the WebLogic Server Node Manager.Kill any Oracle-based java process which are listed as results from the above command.