OEM Grid Control 10.2.0.5 has been released for more than a month. After being installed and running for a month, both the installation and configuration feel much more stable than 10.2.0.4, and there will not be so many problems. It is strongly recommended to install it.
In addition, 10.2.0.5 is a patch package, which is usually upgraded after installing 10.2.0.1.
Reference: http://www.oracle.com/technology/global/cn/pub/articles/revitt-oem.html
Table of contents
1 Overview 1
2 Pre-installation work 2
2.1 Software download 2
2.2 /etc/hosts file confirmation 2
2.3 Configure kernel parameters 2
2.4 Creating groups and users 3
2.5 Create software directory 3
2.6 Configure oracle user environment 3
3 Install 10.2.0.1 3
3.1 Unzip the installation files 3
3.2 Start installation 4
4 Upgrade to 10.2.0.5 5
4.1 Pre-upgrade work 5
4.2 Unzip the patch package 5
4.3 Upgrade OMS and database 5
4.4 Upgrade Agent 6
5 GC usage 7
5.1 GC component ports 7
5.2 Log in to the GC console 7
6 Install Agent 8
6.1 Delete Agent 8 first
6.2 Installation method one (local installation) 9
6.3 Installation method two (remote installation) 10
6.4 Installation method three (page deployment) 11
6.5 Configure monitoring database 11
7 Routine maintenance 13
7.1 Start and stop all GC processes 13
7.2 OMS process management 13
7.3 Agent process management 13
7.4 Delete GC 14
8 FAQ 15
8.1 Agent search target process 15
Overview
The components of Grid Control include Management Agent, Management Service (OMS), and Management Repository. The system architecture is as follows:
The principle and working method of Grid Control:
All data collection on the agent side is completed through perl scripts. The extension is *.pl. These scripts can be found under $AGENT_HOME/sysman/admin/scripts/. The agent program will first write the collected information to the local xml file. , the generated file can be found under $AGENT_HOME/sysman/admin/upload. Then upload the file to the oms side, and the oms service writes the xml file into the oms own repository.
How the Agent-side program works:
When the Agent is deployed to a node, it first searches for all Oracle products installed under $ORACLE_BASE/oraInventory to determine the information about those products that need to be collected. For example, if only one database product is found, then it will only run to collect database and host information. Script. For a node, the information that the agent determines what content needs to be collected is written in the following file $AGENT_HOME/sysman/emd/targets.xml. This file can be modified manually. Another important file is $AGENT_HOME/sysman/ config/emd.properties is the configuration file of each agent. All the properties of the agent are in it, such as the url/TZ of OMS, etc. This file can also be modified manually. After modification, execute ./emctl reload agent to use it. takes effect.
SSH is used to access each target host, so in the Grid Control system, it is necessary for the host to enable SSH.
Tip: # followed by command means operating as root user, $ followed by command means operating as oracle user.
Download working software before installation
GC download address: [url]http://www.oracle.com/technology/software/products/oem/htdocs/linuxsoft.html[/url]
3 installation files: Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.1) for Linux x86
Linux_Grid_Control_full_102010_disk1.zip
Linux_Grid_Control_full_102010_disk2.zip
Linux_Grid_Control_full_102010_disk3.zip
1 PatchSet package: Oracle Enterprise Manager 10g Grid Control Release 5 (10.2.0.5) for Linux x86
gc_10205_part2of2.zip
Agent download address: [url]http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html[/url]
Download the Agent software for each platform, for example, the agent software under Linux
/etc/hosts file confirmation
$ more /etc/hosts
#<IP-address> <fully-qualified-machine-name> <machine-name>
127.0.0.1 localhost.localdomain localhost
xxx.xxx.xxx.170dbaone
Configure kernel parameters
# vi /etc/sysctl.conf
kernel.shmall = 2097152
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
rmem_default = 262144
rmem_max = 262144
wmem_default = 262144
wmem_max = 262144
# /sbin/sysctl -p (make the parameters effective after modification)
# vi /etc/selinux/config (set SELINUX to disabled)
SELINUX=disabled
Create groups and users
# more /etc/oraInst.loc (check whether the product list group oinstall exists)
# more /etc/oratab (This file will exist if Oracle related software has been installed)
# /usr/sbin/groupadd oinstall (if the oinstall group does not exist, create a new one)
# /usr/sbin/groupadd dba (If the dba group does not exist, create a new one. This group has SYSDBA permissions)
# useradd -g oinstall -G dba oracle -d /orahome (create a new user if it does not exist)
# passwd oracle (set password)
Create the software directory. If the Oracle Base directory does not exist, create it:
# mkdir -p /u01/app/oracle
# chown -R oracle:oinstall /u01/app/oracle
# chmod -R 775 /u01/app/oracle
When configuring the oracle user environment, be sure to set NLS_LANG to the Chinese environment, otherwise the Chinese language will be partially garbled when you log in to the Grid console in the future.
#su-oracle
$ vi ~/.bash_profile
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/OracleHomes/db10g
export OMS_HOME=$ORACLE_BASE/OracleHomes/oms10g
export AGENT_HOME=$ORACLE_BASE/OracleHomes/agent10g
export ORACLE_SID=emrep
export ORACLE_HOSTNAME=dbaone
export ORACLE_OWNER=oracle
export NLS_LANG="SIMPLIFIED CHINESE_CHINA.ZHS16GBK"
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/X11R6/lib:$LD_LIBRARY_PATH
export PATH=.:/usr/sbin:$ORACLE_HOME/bin:$ORACLE_HOME/jdk/bin:$PATH
export CLASSPATH=$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib:$CLASSPATH
export LC=en_US
Install 10.2.0.1
Unzip the installation files
$ cd /orahome/wangnc
$ unzip Linux_Grid_Control_full_102010_disk1.zip
$ unzip Linux_Grid_Control_full_102010_disk2.zip
$ unzip Linux_Grid_Control_full_102010_disk3.zip
Start installation
$ ./runInstaller
At this time, you can check the latest installation log file installActionsxxx.log under $ORACLE_BASE/oraInventory/logs to understand the installation progress. The installation steps are as follows:
Specify Installation Type: Enterprise Manager 10g Grid Control Using a New Database
Installation Location: $ORACLE_BASE/OracleHomes
Language Selection: Select Simplified Chinese as well, otherwise the default is only English. This means that the language of GC is not the software itself.
Specify Inventory Directory and Credentials: oraInventory directory -> $ORACLE_BASE/oraInventory, Operating System group name -> oinstall
Product-Specific Prerequisite Checks: Pre-installation check process, go to the next step
Specify Configuration: Database Name -> emrep; Database File Location -> $ORACLE_BASE/oradata, OSDBA and OSOPER group -> dba
Specify Optional Configuration: disabled by default
8) Specify Security Options: Secure Management Server Password -> iamENCY000; Repository Database Passwords -> iamENCY000
Requirements for setting a password: 5-30 characters long, cannot be the same as the user name, must contain uppercase and lowercase letters and numbers, must start with a letter, and cannot contain Oracle reserved words. Oracle's own password prompt here is not completely correct.
Summary: Click install to start the installation (about 2-3 minutes)
10) Execute Configuration Scripts: First log in as root to execute the prompted script, then return to the interface and click OK.
# /u01/app/oracle/oraInventory/orainstRoot.sh
# /u01/app/oracle/OracleHomes/db10g/allroot.sh (just keep hitting Enter)
After execution, the /etc/oratab file should contain the following two lines:
*:/u01/app/oracle/OracleHomes/db10g:N
*:/u01/app/oracle/OracleHomes/oms10g:N
Configuration Assistants: It takes a long time to perform multiple configurations (about 10 minutes, mainly slow in the two steps of OMS Configuration and Agent Configuration).
At this time, you can go to $OMS_HOME/sysman/log or $AGENT_HOME/sysman/log to learn the installation details and error messages of each component. After installation, each service has been automatically started.
Upgrade to 10.2.0.5
Work before upgrading
--Stop all GC processes first
$ $OMS_HOME/bin/emctl stop oms
$ $OMS_HOME/opmn/bin/opmnctl stopall
$ ps -ef | grep "opmn -d" | grep -v grep (it may take a few minutes to confirm that the process is gone)
$ $AGENT_HOME/bin/emctl stop agent
--Backup database
$ sqlplus/as sysdba
SQL> shutdown immediate;
SQL> exit;
$ cd $ORACLE_BASE/oradata/
$ tar -zcvf emrep.tar.gz ./emrep
$ sqlplus/as sysdba
SQL> startup;
--Inspection database
$ cd $OMS_HOME/sysman/admin/emdrep/sql/core/latest/admin/
$ sqlplus/as sysdba
SQL> select object_name, object_type from all_objects where owner='SYSMAN' and status <> 'VALID';
SQL> @admin_recompile_invalid.sql SYSMAN (executed if there is an invalid object)
SQL> show parameter job_queue_processes;
SQL> ALTER SYSTEM SET job_queue_processes=0; (If this parameter is not 0, change it to 0)
SQL> exit;
Unzip the patch package
$ cd /orahome/wangnc
$ unzip gc_10205_part2of2.zip
After decompression, there are the following files:
p3731593_10205_LINUX.zip is the Grid Control 10.2.0.5 patch package, including the patch file of database/OMS/Agent
Upgrade OMS and database
$ cd /orahome/wangnc
$ unzip p3731593_10205_LINUX.zip
$ cd 3731593/Disk1
$ export ORACLE_HOME=$ORACLE_BASE/OracleHomes/oms10g
$ ./runInstaller
When you first enter, the default is the new OracleHome. Select the original oms10g in the name to upgrade. At this time, the database and monitoring are enabled. The upgrade steps are as follows:
Prompt to enter Metalink user and password: ignore it and do not write it
Product-Specific Prerequisite Checks: Pre-installation check process
prompts for the SYS password of the repository database: iamENCY000
prompts for the ias_admin password of AS: Same as sysman password iamENCY000
The prompt will interrupt AS, press OK to continue.
Summary: Press Install to start installing OMS components.
7) Execute the following script as root user
# /u01/app/oracle/OracleHomes/oms10g/root.sh
Configuration Assistants: Start upgrading the database and configuring OMS components (about 12 minutes).
At this time, you can check the latest installation log file installActionsxxx.log under $ORACLE_BASE/oraInventory/logs to understand the installation progress. Go to $OMS_HOME/sysman/log to understand the installation details and error messages. After the upgrade, each OMS service has started automatically.
Upgrade Agent
$ export ORACLE_HOME=$ORACLE_BASE/OracleHomes/agent10g
$ ./runInstaller
When you first enter, the default is the new OracleHome. Select the original agent10g in the name to upgrade. The upgrade steps are as follows:
Prompt to enter Metalink user and password: ignore it and do not write it
Product-Specific Prerequisite Checks: Pre-installation check process
Summary: Press Install to start installing the Agent component
4) Execute the following script as root user
# /u01/app/oracle/OracleHomes/agent10g/root.sh
At this time, you can check the latest installation log file installActionsxxx.log under $ORACLE_BASE/oraInventory/logs to understand the installation progress. Go to $AGENT_HOME/sysman/log to understand the installation details and error messages. After the upgrade, the Agent service has started automatically.
GC uses
For port information of each GC component, please refer to the following files after installation:
$OMS_HOME/install/setupinfo.txt contains the prompt information after the installation is completed.
$OMS_HOME/install/portlist.ini contains various port information.
$AGENT_HOME/sysman/setupinfo.txt contains GC login information.
The default port information is as follows ($OMS_HOME/install/portlist.ini):
Oracle HTTP Server port = 7777
Oracle HTTP Server Listen port = 7778
Oracle HTTP Server SSL port = 8250
Oracle HTTP Server Listen (SSL) port = 4444
Oracle Notification Server Request port = 6003
Oracle Notification Server Local port = 6102
Oracle Notification Server Remote port = 6201
ASG port = 7890
Oracle HTTP Server Diagnostic port = 7200
Application Server Control RMI port = 1850
Log Loader port = 44000
Java Object Cache port = 7000
DCM discovery port = 7100
Oracle Management Agent Port = 1157
Application Server Control port = 1156
Web Cache HTTP Listen port = 7777
Web Cache HTTP Listen (SSL) port = 8250
Web Cache Administration port = 9400
Web Cache Invalidation port = 9401
Web Cache Statistics port = 9402
Enterprise Manager Central Console Port = 4889
Enterprise Manager Central Console Secure Port = 1159
Log in to the GC console
GC Console URL:
http://<oms_hostname>.<domain>:<port>/em or https://<oms_hostname>.<domain>:<port>/em
For example, the login URL in this example is: http://dbaone:4889/em
The username and password are sysman/iamENCY000. After entering the GC, the web interface will be displayed according to the browser's preferred language.
If you log in in Windows, remember to add the corresponding relationship between the server IP and the host name in the C:WINDOWSsystem32driversetchosts file.
After logging in, the home page is as follows (by default, there is an unknown target called generic_mom_managed_host, which is a configuration of Microsoft Operations Management. You can delete it if it is not needed):
Install Agent
If you want to monitor the database or application on a certain server, you need to install Agent software on the server.
Delete Agent first
View agent:
$ $AGENT_HOME/bin/emctl status agent
Stop agent:
$ $AGENT_HOME/bin/emctl stop agent
Remove software (silent mode):
$ $AGENT_HOME/oui/bin/runInstaller -silent -deinstall -removeallfiles -removeAllPatches REMOVE_HOMES="{/u01/oracle/OracleHomes/agent10g}"
Delete oraInventory information:
$ more /etc/oraInst.loc
inventory_loc=/u01/app/oraInventory
inst_group=oinstall
$ cd /u01/app/oraInventory/ContentsXML
$ vi inventory.Xml (delete the entry whose name is agent10g in <HOME_LIST>)
<HOME NAME="agent10g" LOC="/u01/app/oracle/OracleHomes/agent10g" TYPE="O" IDX="2" REMOVED="T"/>
Delete directory OracleHomes:
$ rm -rf $ORACLE_BASE/OracleHomes
Installation method one (local installation)
This method is applicable when the monitored target and the OMS host are not on the same operating system platform. The following uses the Linux platform as an example.
$ more /etc/oratab (should have monitored database instance information)
WENDING:/u01/app/oracle/product/10.2.0/db_1:N
$ more /etc/hosts (there should be a corresponding relationship between OMS host and IP)
127.0.0.1 localhost.localdomain localhost
xxx.xxx.xxx.170dbaone
xxx.xxx.xxx.171 dbatwo
$ echo $PATH (make sure $ORACLE_HOME/jdk/bin is put in PATH, because the jar command is used)
$ cd /orahome/wangnc
$ unzip Linux_Grid_Control_agent_download_10_2_0_5_0.zip
$ cd /orahome/wangnc/linux/agent
$ export ORACLE_HOME=$ORACLE_BASE/OracleHomes/agent10g
$ ./runInstaller
The installation steps are as follows:
Installation Location: $ORACLE_BASE/OracleHomes
Language Selection: Select Simplified Chinese as well, otherwise the default is only English. This means that the language of GC is not the software itself.
Prompt to enter Metalink user and password: ignore it and do not write it
Product-Specific Prerequisite Checks: Next
Specify Oracle Management Service Location: host name -> dbaone, port -> 4889
Specify Agent Registration Password: iamENCY000
Summary: Start installation
8) Execute the following script as root user
# /u01/app/oracle/OracleHomes/agent10g/root.sh (just keep hitting Enter)
Configuration Assistants: Automatically configures and completes the installation.
At this time, you can go to $AGENT_HOME/sysman/log to understand the installation details and error messages. After installation, the agent service should start automatically. If it does not start, just start it manually, and then go to the "Target" tab of the GC console. You can see the monitored host. If there is instance information in /etc/oratab, you can also see the monitored database information. You just need to configure the dbsnmp user password first (see the "Configuring Monitoring Database" chapter).
View Agent status information:
$ $AGENT_HOME/bin/emctl status agent
Installation method two (remote installation)
This method is applicable to the same operating system platform of the monitored target and the OMS host. The following will take the Linux platform as an example.
OMS host (just do it once):
Enter the software storage directory and extract the 10.2.0.5 version file to the $OMS_HOME/sysman/agent_download/10.2.0.5.0 directory.
$ cd /orahome/wangnc
$ unzip Linux_Grid_Control_agent_download_10_2_0_5_0.zip -d $OMS_HOME/sysman/agent_download/10.2.0.5.0
Agent host:
$ more /etc/oratab (should have monitored database instance information)
WENDING:/u01/app/oracle/product/10.2.0/db_1:N
$ more /etc/hosts (there should be a corresponding relationship between OMS host and IP)
127.0.0.1 localhost.localdomain localhost
xxx.xxx.xxx.170dbaone
xxx.xxx.xxx.171 dbatwo
$ echo $PATH (make sure $ORACLE_HOME/jdk/bin is put in PATH, because the jar command is used)
$ cd /orahome/wangnc
$ wget http://dbaone:4889/agent_download/10.2.0.5.0/linux/agentDownload.linux
$ chmod u+x agentDownload.linux
$ export ORACLE_HOME=$ORACLE_BASE/OracleHomes/agent10g
$ ./agentDownload.linux -b /u01/app/oracle/OracleHomes -m dbaone -r 4889
(-b is the BASE directory where the agent is installed, -m refers to the OMS host name, and -r refers to the OMS communication port)
...
Enter Agent Registration Password: <Enter the OMS security password iamENCY000>
...
At this time, you can go to $AGENT_HOME/sysman/log to view the installation log.
During the installation, you will be prompted to execute the script as the root user, just press Enter:
# /u01/app/oracle/OracleHomes/agent10g/root.sh
After the Agent is installed and started by default, you can see the monitored host in the "Target" tab of the GC console. Then you can see the monitored host in the "Target" tab of the Grid Control console. If There is instance information in /etc/oratab, and you can also see the monitored database information. You just need to configure the dbsnmp user password first (see the "Configuring Monitoring Database" chapter).
If it is not started, you can set it manually and start it:
$ $AGENT_HOME/bin/emctl secure agent (performs security authentication)
Enter Agent Registration password: <Enter OMS security password iamENCY000>
$ $AGENT_HOME/bin/emctl start agent (start agent)
$ $AGENT_HOME/bin/emctl status agent (check agent status)
$ $AGENT_HOME/bin/emctl upload (try to upload xml manually)
Installation method three (page deployment)
This method is suitable for batch deployment and installation of multiple hosts, but requires that the installation username and password of each host are the same.
OMS host (just do it once):
Enter the software storage directory and extract the 10.2.0.5 version file to the $OMS_HOME/sysman/agent_download/10.2.0.5.0 directory.
$ cd /orahome/wangnc
$ unzip Linux_Grid_Control_agent_download_10_2_0_5_0.zip -d $OMS_HOME/sysman/agent_download/10.2.0.5.0
Then enter the GC console, select "Deployment", click "Install Agent" in the agent installation column, and then select "New Installation" or "Clone Agent". On the subsequent page, follow the prompts and enter the user logged in to the target host. After entering the name, password and other information, the installation begins.
Configure monitoring database
1) First unlock the DBSNMP user of the target database and change the password if necessary;
SQL> select password,account_status from dba_users where username = 'DBSNMP';
SQL> alter user DBSNMP identified by "iamENCY000" account unlock;
Make sure there is only one hc_$ORACLE_SID.dat file in the $ORACLE_HOME/dbs directory of the target library. Note that it is case-sensitive.
3) Then enter the GC console, select "Target", select "Database", click "Add", select a host, if the database cannot be found automatically, click "Manual Add" and enter the instance name /Oracle Home/ After entering the dbsnmp user password/port 1521/sid and other information, click "Test Connection". If it prompts "Connection Test Successful", click "Next" and click "OK" twice, thus adding the new monitored database. Now it should You can see the complete display information of the target library.
4) If the database target cannot be added manually on the console page, or the database information automatically added by default needs to be modified, manually edit the targets. Actual circumstances change).
$ vi $AGENT_HOME/sysman/emd/targets.xml
<Targets AGENT_TOKEN="23ac7375a26b142e008c18121ef19afebe5096e6">
<Target TYPE="oracle_emd" NAME="game:3872"/>
<Target TYPE="host" NAME="game"/>
<Target TYPE="oracle_listener" NAME="lsnr_171_listener">
<Property NAME="ListenerOraDir" VALUE="/u01/app/oracle/product/10.2.0/db_1/network/admin"/>
<Property NAME="LsnrName" VALUE="LISTENER"/>
<Property NAME="Machine" VALUE="game"/>
<Property NAME="OracleHome" VALUE="/u01/app/oracle/product/10.2.0/db_1"/>
<Property NAME="Port" VALUE="1521"/>
</Target>
<Target TYPE="oracle_database" NAME="db_171_WENDING">
<Property NAME="OracleHome" VALUE="/u01/app/oracle/product/10.2.0/db_1"/>
<Property NAME="UserName" VALUE="dbsnmp"/>
<Property NAME="MachineName" VALUE="game"/>
<Property NAME="Port" VALUE="1521"/>
<Property NAME="SID" VALUE="WENDING"/>
<Property NAME="ServiceName" VALUE="WENDING.LK"/>
<Property NAME="password" VALUE="6bea6440ffec0f38cea99c413c363a975423987053f4f0b3ae0a7e0807380071" ENCRYPTED="TRUE"/>
<Property NAME="Role" VALUE="NORMAL"/>
</Target>
</Targets>
5) Finally reload the configuration file:
$ $AGENT_HOME/bin/emctl reload agent
At this time, go to the Grid Control console and you can see the database target information you just configured, but the dbsnmp password will be reconfigured according to actual requirements. If you modify the information, you may also need to delete the old configuration in the console page.
Routine maintenance starts and stops all GC processes
--Stop everything, including AS/OMS/WebCache
$ $OMS_HOME/opmn/bin/opmnctl stopall
$ ps -ef | grep "opmn -d" | grep -v grep
--Start everything, including AS/OMS/WebCache
$ $OMS_HOME/opmn/bin/opmnctl startall
--View status
$ $OMS_HOME/opmn/bin/opmnctl status
--view log
$ cd $OMS_HOME/opmn/logs/
$ll
OMS process management
--Stop the Management Service
$ $OMS_HOME/bin/emctl stop oms
--Start the Management Service
$ $OMS_HOME/bin/emctl start oms
--View status
$ $OMS_HOME/bin/emctl status oms
--view log
$ cd $OMS_HOME/sysman/log/
$ tail -500f emoms.trc
Agent process management
--Stop the Management Agent
$ $AGENT_HOME/bin/emctl stop agent
--Start the Management Agent
$ $AGENT_HOME/bin/emctl start agent
--View status
$ $AGENT_HOME/bin/emctl status agent
--view log
1) Central Agent log and trace file description (under $ORACLE_HOME/agent/sysman/log)
emagent.nohup : Agent watchdog log file
emagent.log : Main Agent log file
emagent.trc : Main Agent trace file
emagentfetchlet.log: Log file for Java Fetchlets
emagentfetchlet.trc: Trace file for Java Fetchlets
NOTE: Startup errors are recorded in the emagent.nohup file.
$ cd $ORACLE_HOME/agent/sysman/log
$ tail -500f emagent.trc
2) AS Control Agent log and trace file description (under $ORACLE_HOME/sysman/log)
$ cd $ORACLE_HOME/sysman/log
$ tail -500f emdctl.trc
3) DB Control Agent log and trace file description (under $ORACLE_HOME/<hostname_sid>/sysman/log)
$ cd $ORACLE_HOME/`hostname`_$ORACLE_SID/sysman/log
$ tail -500f emdctl.trc
Remove GC
Stop database/OMS/Agent (root user):
# /etc/init.d/gcstartup stop
Remove software (silent mode):
$ $OMS_HOME/oui/bin/runInstaller -silent -deinstall -removeallfiles -removeAllPatches REMOVE_HOMES="{/u01/app/oracle/OracleHomes/db10g,/u01/app/oracle/OracleHomes/oms10g,/u01/app/oracle/ OracleHomes/agent10g}"
Delete database files (default location):
$ rm -rf $ORACLE_BASE/oradata/$ORACLE_SID
Delete directory OracleHomes:
$ rm -rf $ORACLE_BASE/OracleHomes
Delete oraInventory information:
$ more /etc/oraInst.loc
inventory_loc=/u01/app/oracle/oraInventory
inst_group=oinstall
$ vi /u01/app/oracle/oraInventory/ContentsXML/inventory.xml (delete the entry whose name is db10g/oms10g/agent10g in <HOME_LIST>)
<HOME NAME="db10g" LOC="/u01/app/oracle/OracleHomes/db10g" TYPE="O" IDX="1" REMOVED="T"/>
<HOME NAME="oms10g" LOC="/u01/app/oracle/OracleHomes/oms10g" TYPE="O" IDX="2" REMOVED="T"/>
<HOME NAME="agent10g" LOC="/u01/app/oracle/OracleHomes/agent10g" TYPE="O" IDX="3" REMOVED="T"/>
Delete related entry information in oratab:
$ vi /etc/oratab
*:/u01/app/oracle/OracleHomes/db10g:N
*:/u01/app/oracle/OracleHomes/oms10g:N
emrep:/u01/app/oracle/OracleHomes/db10g:N
FAQ
Agent search target process
When installing and configuring the Agent, execute the perl script listed in $ORACLE_HOME/sysman/admin/discover/discovery.lst to find the monitored target, and then place it in $ORACLE_HOME/sysman/emd/targets.xml, so that in the Grid console Here you can see the monitored target.
The host is the host where the Agent runs. The configuration in Targets.xml is as follows:
<Target TYPE="host" NAME="name" TYPE_DISPLAY_NAME="Host" VERSION="version" GUID="guid"/>
2) Listen for the listener.ora files in $TNS_ADMIN and $ORACLE_HOME/network/admin to obtain the listener name. The configuration in Targets.xml is as follows:
<Target>
<Target TYPE="oracle_listener" NAME="name_hostName">
<Property NAME="ListenerOraDir" VALUE="$oraDir" />
<Property NAME="LsnrName" VALUE="$name"/>
<Property NAME="Machine" VALUE="$hostName" />
<Property NAME="OracleHome" VALUE="$oHome" />
<Property NAME="Port" VALUE="$port" />
</Target>
3) The database instance obtains each SID and $ORACLE_HOME from /etc/oratab, then obtains the listening list and port number from the listener.ora file in $TNS_ADMIN and $ORACLE_HOME/network/admin, and then obtains the listening list and port number from $ORACLE_HOME/dbs/init< Obtain the instance name in sid>.ora (note that if the instance uses spfile, the pfile must be generated first, this will be automatically generated). The found target will be set to the format of db_name.db_domain or sp_name.db_domain (in the case of Dataguard) Name, if the name is not unique, the version number will be added. If the spfile cannot be read, the target will be set to a name in the format of <sid>_<hostname>, the service_name parameter will be left blank and the default port number 1521 will be assigned. Configure in Targets.xml as follows:
<Target>
<Target TYPE="oracle_database" NAME="name" TYPE_DISPLAY_NAME="Database" VERSION="version" GUID="guid">
<Property NAME="MachineName" VALUE="node database runs on" />
<Property NAME="Port" VALUE="listener port for this database" />
<Property NAME="SID" VALUE="identifier of this database" />
<Property NAME="OracleHome" VALUE="location Oracle software" />
<Property NAME="UserName" VALUE="database user for monitoring" ENCRYPTED="TRUE" /> <<<<<<By default this is DBSNMP and cannot be changed in this release
<Property NAME="password" VALUE="password of the database user doing the monitoring" ENCRYPTED="TRUE" />