Oracle Enterprise Manager Cloud Control 12c(12.1.0.1.1) Agent install
2013-01-23 09:55
323 查看
Oracle Enterprise Manager Cloud Control 12c(12.1.0.1.1) Agent install:
安装前准备：
下载最新版本EM Cloud Control Agent【Linux_Grid_Control_agent_download_11_1_0_1_0.zip】上传至<OMS_HOME>/sysman/agent_download/11.1.0.1.0/下。关于这一个步骤可以参考EM Cloud Control Agent安装程序的【instructions.txt】文件说明，参考如下：
Instructions for installing the agent
Download the Linux_Grid_Control_agent_download_11_1_0_1_0.zip file from OTN.
1. Methods for mass deployment of agents
a. Copy the downloaded file to <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory.(create <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory, if it doesn't exist.)
b. cd <OMS_HOME>/sysman/agent_download/11.1.0.1.0
c. <OMS_HOME>/bin/unzip Linux_Grid_Control_agent_download_11_1_0_1_0.zip
Once the agent software the is staged in the above mentioned directory either of the following methods can be used for mass agent deployment:
-- agentDownload script.
If agent_download.rsp doesn't exists at <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory then execute the following:
mv agent_download.rsp.bak agent_download.rsp
Then follow the instructions in section 10 of the Enterprise Manager Grid Control Basic Installation and Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
-- Agent Deploy Application. Details on using this method can be found in Enterprise Manager Grid Control Basic Installation and Configuration Guide.
Additionally, refer to section 10 of the the Enterprise Manager Grid Control Basic Installation and Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
2. Silent installation of the agent
For silent installation using DVD, copy the <DVD>/response/additional_agent.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly. Invoke the runInstaller by executing:
<DVD>/<runInstaller> -silent -responseFile <location>/additional_agent.rsp
For silent installation using the extracted agent download zip file, copy the <UNZIP_DIR>/response/additional_agent.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly. Invoke the runInstaller by executing:
<UNZIP_DIR>/<runInstaller> -silent -responseFile <location>/additional_agent.rsp
For detailed information on using silent installation method to install the Management agent please refer to .Enterprise Manager Silent Installations. described in the Enterprise Manager Grid Control Basic Installation available at:
http://www.oracle.com/technology/documentation/oem.html
3. NFS Mounted Agent Installation
Enterprise Manager 11g R1 allows you to install a single Agent on a shared NFS filesystem, and then have multiple hosts share that same ORACLE_HOME. Details on installing a NFS mounted agent can be found in section "NFS Agent Installation" of the Enterprise
Manager Grid Control Basic Installation Guide available at:
http://www.oracle.com/technology/documentation/oem.html
This URL takes you to the Enterprise Manager documentation library page. Click View Library and on the page that comes up, click the Documentation tab, and then click the name of the document you want to access.
-------------------------------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------
开始安装配置：
useradd -g oinstall oem
export DISPLAY=:1.0
alter system set processes= 500 scope=spfile;
alter system set session_cached_cursors=500 scope=spfile;
alter system set shared_pool_size=650M scope=spfile;
alter system set job_queue_processes=22 scope=spfile;
--alter database add logfile size 320M;
alter system set open_cursors=350 scope=spfile;
--alter system set sga_target=1400m scope=spfile;
--ALTER SYSTEM SET pga_aggregate_target=1G SCOPE=SPFILE;
unset ORACLE_HOME ORACLE_BASE ORACLE_SID
export DISPLAY=:0
alter database add logfile group 4 ('/u01/oradata/db12c/redo04.log') size 350m;
alter database add logfile group 5 ('/u01/oradata/db12c/redo05.log') size 350m;
alter database add logfile group 6 ('/u01/oradata/db12c/redo06.log') size 350m;
alter database drop logfile group 1;
alter database drop logfile group 2;
alter database drop logfile group 3;
alter database add logfile group 1 ('/u01/oradata/db12c/redo01.log') size 350m reuse;
alter database add logfile group 2 ('/u01/oradata/db12c/redo02.log') size 350m reuse;
alter database add logfile group 3 ('/u01/oradata/db12c/redo03.log') size 350m reuse;
alter system set shared_pool_size=650M scope=spfile;
create spfile='/u01/app/oracle/product/11.2.0/db/dbs/spfiledb12c.ora' from pfile='/home/dbuser/pfile.ora';
*.memory_target=871859200
SQL> startup
ORA-00845: MEMORY_TARGET not supported on this system
[dbuser@em12c ~]$ oerr ora 845
00845, 00000, "MEMORY_TARGET not supported on this system"
// *Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.
// *Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.
[root@em12c ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 89355588 30211108 54532224 36% /
/dev/sda5 295561 16082 264219 6% /boot
tmpfs 517368 0 517368 0% /dev/shm
/dev/sda1 40313964 5166748 33099332 14% /orasoft
[root@em12c ~]# umount /dev/shm
[root@em12c ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 89355588 30211112 54532220 36% /
/dev/sda5 295561 16082 264219 6% /boot
/dev/sda1 40313964 5166748 33099332 14% /orasoft
[root@em12c ~]# vi /etc/fstab
tmpfs /dev/shm tmpfs defaults,size=1024m 0 0
[root@em12c ~]# mount -a
[root@em12c ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 86G 29G 53G 36% /
/dev/sda5 289M 16M 259M 6% /boot
/dev/sda1 39G 5.0G 32G 14% /orasoft
tmpfs 1.0G 0 1.0G 0% /dev/shm
SQL> startup
ORACLE instance started.
Total System Global Area 870457344 bytes
Fixed Size 1348384 bytes
Variable Size 486542560 bytes
Database Buffers 377487360 bytes
Redo Buffers 5079040 bytes
Database mounted.
Database opened.
SQL> show parameter memory
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
hi_shared_memory_address integer 0
memory_max_target big integer 832M
memory_target big integer 832M
shared_memory_address integer 0
SQL>
SQL> alter user sysman identified by weblogic1;
exec DBMS_AUTO_TASK_ADMIN.DISABLE(client_name => 'auto optimizer stats collection',operation => NULL,window_name => NULL);
http://micate.me/linux-unzip-2g-large-zip-file-error.note
Archive: End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on
http://downloads.sourceforge.net/project/p7zip/p7zip/9.13/p7zip_9.13_src_all.tar.bz2?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fp7zip%2Ffiles%http://downloads.sourceforge.net/project/p7zip/p7zip/9.13/p7zip_9.13_src
/article/8564422.html
http://www.bitscn.com/pdb/oracle/200807/146636.html
http://space.itpub.net/519536/viewspace-682820
/article/3752967.html
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
oem agent install
Instructions for installing the agent
Download the Linux_Grid_Control_agent_download_11_1_0_1_0.zip:
Download the Linux_Grid_Control_agent_download_11_1_0_1_0.zip file from OTN.
1. Methods for mass deployment of agents
a. Copy the downloaded file to <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory.(create <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory, if it doesn't exist.)
b. cd <OMS_HOME>/sysman/agent_download/11.1.0.1.0
c. <OMS_HOME>/bin/unzip Linux_Grid_Control_agent_download_11_1_0_1_0.zip
Once the agent software the is staged in the above mentioned directory either of the following methods can be used for mass agent deployment:
-- agentDownload script.
If agent_download.rsp doesn't exists at <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory then execute the following:
mv agent_download.rsp.bak agent_download.rsp
groupadd oinstall
useradd -g oinstall oem
If you have an Oracle RAC Cluster with multiple nodes, then you must install a Management Agent on each of the nodes separately. In other words, in the Add Host Targets Wizard, you must add each node explicitly as a destination host.
The Add Host Targets Wizard uses SSH to establish connectivity between Oracle Management Service (OMS) and the remote hosts where you want to install the Management Agents.
Only SSH1 (SSH version 1) and SSH2 (SSH version 2) protocols offered by OpenSSH are supported for deploying a Management Agent.
make-3.81
binutils-2.17.50.0.6
gcc-4.1.1
libstdc++-4.1.1
libXtst-1.0.1-3.1(i386)
Destination Host Time Zone Requirements
export TZ='Asia/Shanghai'
<AGENT_HOME>/sysman/admin/supportedtzs.lst
/m01/oracle/agent/core/12.1.0.2.0/sysman/admin/supportedtzs.lst
Verify whether the SSH server can access the TZ environment variable by logging in to the OMS host, and running the following command:
ssh em12c echo $TZ
ssh xpli $TZ
sudo/pbrun/sesu/su SSH Requirements:
If you are using sudo as your privilege delegation tool, and you do not want to set the oracle.sysman.prov.agentpush.enablePty property to true, do one of the following:
Include Defaults visiblepw in the /etc/sudoers file, or enter the sudo command with the -S option for Privileged Delegation Setting on the Installation Details page.
For information on how to access the Installation Details page, see Installation Procedure.
Comment out Defaults requiretty in the /etc/sudoers file.
sudo/pbrun/sesu/su Requirements (for Root User):
Ensure that the installing user has the privileges to invoke the id command and the agentdeployroot.sh script as root. Grant the privileges in the configuration file of your privilege delegation tool.
For example, if you are using sudo as your privilege delegation tool, include the following in the /etc/sudoers file to grant the required privileges:
oracle ALL=(root) /usr/bin/id, /home/oracle/agentibd/*/agentdeployroot.sh
Here, oracle is the installing user, and /home/oracle/agentibd is the agent base directory.
Unset the CLASSPATH environment variable.You can always reset the variable to the original value after the installation is complete.
Central Inventory (oraInventory) Requirements:
Ensure that you have read, write, and execute permissions on oraInventory on all remote hosts. If you do not have these permissions on the default inventory (typically at /etc/oraInst.loc) on any remote host, then ensure that you specify the path to an alternative
inventory location by using one of the following options in the Additional Parameters field of the Add Host Targets Wizard. However, note that these parameters are supported only on UNIX platforms, and not on Microsoft Windows platforms.
INVENTORY_LOCATION=<absolute_path_to_inventory_directory> -invPtrLoc <absolute_path_to_oraInst.loc>
Installing User Requirements:
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group.
Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory.
For example, if the inventory owner is abc and the user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory.
Browser Requirements:
If you use Microsoft Internet Explorer 8 or 9, do the following:
Turn off the compatibility view mode. To do so, in Microsoft Internet Explorer, from the Tools menu, click Compatibility View to disable it if it is enabled. Also, click Compatibility View Settings and deregister the Enterprise Manager Cloud Control console
URL.
Enable XMLHTTP. To do so, from the Tools menu, click Internet Options. Click the Advanced tab, and under the Security heading, select Enable native XMLHTTP support to enable it.
INVENTORY_LOCATION=/m01/oracle -invPtrLoc /m01/oracle/emagent_oraInst.loc
[oem@xpli oracle]$ cat /m01/oracle/emagent_oraInst.loc
inventory_loc=/u01/app/oraInventory
[oem@xpli oracle]$
-----------------------------------------------------------------------------
$OMS_HOME/bin/emctl stop oms -all
$AGENT_HOME/bin/emctl stop agent (-all)
$OMS_HOME/bin/emctl start oms
$AGENT_HOME/bin/emctl start agent
自动发送邮件设置：
在Management Repository server和OMS server的/etc/hosts文件中加入smtp服务器域名解析：
[root@em12c ~]# cat /etc/hosts
127.0.0.1 localhost
192.168.128.216 xpli
123.58.178.204 smtp.163.com
192.168.128.212 em12c
[oem@em12c .ssh]$ ssh vm10g date
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for vm10g has changed,
and the key for the according IP address 192.168.128.220
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
ce:bd:31:55:44:c0:44:76:60:db:6c:a4:05:72:03:85.
Please contact your system administrator.
Add correct host key in /home/oem/.ssh/known_hosts to get rid of this message.
Offending key in /home/oem/.ssh/known_hosts:3
RSA host key for vm10g has changed and you have requested strict checking.
Host key verification failed.
[oem@em12c .ssh]$
[oem@em12c .ssh]$ ssh vm10g date
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
ce:bd:31:55:44:c0:44:76:60:db:6c:a4:05:72:03:85.
Please contact your system administrator.
Add correct host key in /home/oem/.ssh/known_hosts to get rid of this message.
Offending key in /home/oem/.ssh/known_hosts:3
RSA host key for vm10g has changed and you have requested strict checking.
Host key verification failed.
[oem@em12c .ssh]$
问题原因：之前/etc/hosts文件中vm10g主机ip配置错误，原IP指向em server IP所致，变更IP后原来的ssh认证不可用。
解决：删除EM server和agent服务器oem用户下【.ssh】目录下/home/oem/.ssh/known_hosts文件中vm10g部分，然后重新配置vm10g主机ssh认证即可。
[oem@em12c .ssh]$ cat known_hosts
xpli,192.168.128.216 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA9xVX1fmBi1ICO0xjAxVuK/BMhX1/H5Xn3M5R7mEYpsjSuHBOfGpvbfnSAJikEqW+EYaPZGQzf6Y/z+OP0sYInfgMOxlOxwSEUyjD26K/2ZJmwho2UbRPLS68P30caY4mvEXFesbO2EsZeIl5MvhnHZ52+ItwVDna8ZYUY2aYIK0FjydcnBm3H831mGSyeCM8eh09oCRkRTvMujw5UJRvz5X71ECj/rKMN6y/sYENB9OqW7n1fbYr03WA3Ml1+CdMBIXO1bV4PQlUqCf89j/5BqiVyqlVQPyUtWnLpLMohkNd/Fa5IhZm3m3bPXUiislFbqq2nqTkm5DJZnsKOj3PrQ==
em12c,192.168.128.212 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAl8rWGXROurrpfK4/Nx+8F449ayxx+KynX1SwIhcV/12rdmA9uzJ7Wueq4K8NGZpfPZux1D3Udmfu/goWoynf/ERWO8zr00Wzh9mFQjFX1egBTlJ7B+39kN5pPIZuAaWR1nhNySR2/x8pruTdz9tG0IkTdc8Lul4y2uJtZUUlnEXFWllpCSMtPpQWyQez7LwWXfqa8Z9/wKX+PQ7SXix0xbxRIO75qX7mkpMRLuc5Mse+yWpBsssrGWhRLOJsd+SPWctqHm0vP+JkLlaImrJ9q0yRQ8q6ynXlU53GZHksoFDV8mrTykRdiooExCF2CjpQMmqA929mWtAsXnsU9bfgEQ==
vm10g,192.168.128.220 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA9dxRS0fa3smSJKtzljkStfDEuSR7R0mQkFM764z+jaRomdFvPlgY0ZZ3vhsqUhJyRMva5bXW+HqHrbh6iNn3ifUBO/feYNHAgaJ/4ODKNwEdObstD7hgknUB/ORTYvtaqG54UjGAqZ8BDVNFvmPbMRQ9rcTEHvBxSHZLTLCnza0=
-------------------------------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------
em cloud control agent deinstall:
rm -rf $EM_AGENT_DIR
OMS DB:
select t.TARGET_NAME,
t.TARGET_TYPE,
DECODE(a.current_status,1,'Up','Down') Status
from mgmt_targets t,
mgmt_current_availability a
WHERE t.target_guid = a.target_guid
and target_type='oracle_emd'
order by 1,2
exec mgmt_admin.cleanup_agent('192.168.128.220:3872');
SQL>
SQL> select t.TARGET_NAME,
2 t.TARGET_TYPE,
3 DECODE(a.current_status, 1, 'Up', 'Down') Status
4 from mgmt_targets t, mgmt_current_availability a
5 WHERE t.target_guid = a.target_guid
6 and target_type = 'oracle_emd'
7 order by 1, 2
8 /
TARGET_NAME
--------------------------------------------------------------------------------
TARGET_TYPE STAT
---------------------------------------------------------------- ----
192.168.128.220:3872
oracle_emd Down
em12c:3872
oracle_emd Up
vm10g:3872
oracle_emd Up
TARGET_NAME
--------------------------------------------------------------------------------
TARGET_TYPE STAT
---------------------------------------------------------------- ----
xpli:3872
oracle_emd Up
SQL> show user
USER is "SYS"
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[dbuser@xpli ~]$ sqlplus sysman/weblogic1
SQL*Plus: Release 11.2.0.3.0 Production on Tue Jan 22 15:07:35 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> exec mgmt_admin.cleanup_agent('192.168.128.220:3872');
PL/SQL procedure successfully completed.
SQL> select t.TARGET_NAME,
2 t.TARGET_TYPE,
3 DECODE(a.current_status, 1, 'Up', 'Down') Status
from mgmt_targets t, mgmt_current_availability a
WHERE t.target_guid = a.target_guid
4 5 6 and target_type = 'oracle_emd'
order by 1, 2 7
8 /
TARGET_NAME
--------------------------------------------------------------------------------
TARGET_TYPE STAT
---------------------------------------------------------------- ----
em12c:3872
oracle_emd Up
vm10g:3872
oracle_emd Up
xpli:3872
oracle_emd Up
SQL>
references ：
Agent Upload to OMS Fails if Multiple Agents are Installed and Targets are Discovered as Duplicates in the Grid Console [ID 416898.1]
Grid Control Target Maintenance: How to Manually Remove a De-commissioned Host / Agent from the Grid Control Repository Database? [ID 454081.1]
Details about 'Agent Misconfiguration' Alerts in Grid Console 10.2 and How to Resolve them [ID 741595.1]
How to Cleanly De-Install the EM 10g Agent on Windows and Unix [ID 438158.1]
Grid Control Target Maintenance: Understanding the Target Deletion / Removal Process in the Enterprise Manager Grid Control [ID 271691.1]
Grid Control Target Maintenance: How to Manually Remove a De-commissioned Host / Agent from the Grid Control Repository Database? [ID 454081.1]
Grid Agent Configuration: How to Modify the Port on Which Grid Agent is Running/Installed? [ID 404924.1]
http://blog.csdn.net/wangya822/article/details/7654582
安装前准备：
下载最新版本EM Cloud Control Agent【Linux_Grid_Control_agent_download_11_1_0_1_0.zip】上传至<OMS_HOME>/sysman/agent_download/11.1.0.1.0/下。关于这一个步骤可以参考EM Cloud Control Agent安装程序的【instructions.txt】文件说明，参考如下：
Instructions for installing the agent
Download the Linux_Grid_Control_agent_download_11_1_0_1_0.zip file from OTN.
1. Methods for mass deployment of agents
a. Copy the downloaded file to <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory.(create <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory, if it doesn't exist.)
b. cd <OMS_HOME>/sysman/agent_download/11.1.0.1.0
c. <OMS_HOME>/bin/unzip Linux_Grid_Control_agent_download_11_1_0_1_0.zip
Once the agent software the is staged in the above mentioned directory either of the following methods can be used for mass agent deployment:
-- agentDownload script.
If agent_download.rsp doesn't exists at <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory then execute the following:
mv agent_download.rsp.bak agent_download.rsp
Then follow the instructions in section 10 of the Enterprise Manager Grid Control Basic Installation and Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
-- Agent Deploy Application. Details on using this method can be found in Enterprise Manager Grid Control Basic Installation and Configuration Guide.
Additionally, refer to section 10 of the the Enterprise Manager Grid Control Basic Installation and Configuration Guide available at:
http://www.oracle.com/technology/documentation/oem.html
2. Silent installation of the agent
For silent installation using DVD, copy the <DVD>/response/additional_agent.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly. Invoke the runInstaller by executing:
<DVD>/<runInstaller> -silent -responseFile <location>/additional_agent.rsp
For silent installation using the extracted agent download zip file, copy the <UNZIP_DIR>/response/additional_agent.rsp file to a location on the local machine and modify the Value Unspecified entries accordingly. Invoke the runInstaller by executing:
<UNZIP_DIR>/<runInstaller> -silent -responseFile <location>/additional_agent.rsp
For detailed information on using silent installation method to install the Management agent please refer to .Enterprise Manager Silent Installations. described in the Enterprise Manager Grid Control Basic Installation available at:
http://www.oracle.com/technology/documentation/oem.html
3. NFS Mounted Agent Installation
Enterprise Manager 11g R1 allows you to install a single Agent on a shared NFS filesystem, and then have multiple hosts share that same ORACLE_HOME. Details on installing a NFS mounted agent can be found in section "NFS Agent Installation" of the Enterprise
Manager Grid Control Basic Installation Guide available at:
http://www.oracle.com/technology/documentation/oem.html
This URL takes you to the Enterprise Manager documentation library page. Click View Library and on the page that comes up, click the Documentation tab, and then click the name of the document you want to access.
-------------------------------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------
开始安装配置：
useradd -g oinstall oem
export DISPLAY=:1.0
alter system set processes= 500 scope=spfile;
alter system set session_cached_cursors=500 scope=spfile;
alter system set shared_pool_size=650M scope=spfile;
alter system set job_queue_processes=22 scope=spfile;
--alter database add logfile size 320M;
alter system set open_cursors=350 scope=spfile;
--alter system set sga_target=1400m scope=spfile;
--ALTER SYSTEM SET pga_aggregate_target=1G SCOPE=SPFILE;
unset ORACLE_HOME ORACLE_BASE ORACLE_SID
export DISPLAY=:0
alter database add logfile group 4 ('/u01/oradata/db12c/redo04.log') size 350m;
alter database add logfile group 5 ('/u01/oradata/db12c/redo05.log') size 350m;
alter database add logfile group 6 ('/u01/oradata/db12c/redo06.log') size 350m;
alter database drop logfile group 1;
alter database drop logfile group 2;
alter database drop logfile group 3;
alter database add logfile group 1 ('/u01/oradata/db12c/redo01.log') size 350m reuse;
alter database add logfile group 2 ('/u01/oradata/db12c/redo02.log') size 350m reuse;
alter database add logfile group 3 ('/u01/oradata/db12c/redo03.log') size 350m reuse;
alter system set shared_pool_size=650M scope=spfile;
create spfile='/u01/app/oracle/product/11.2.0/db/dbs/spfiledb12c.ora' from pfile='/home/dbuser/pfile.ora';
*.memory_target=871859200
SQL> startup
ORA-00845: MEMORY_TARGET not supported on this system
[dbuser@em12c ~]$ oerr ora 845
00845, 00000, "MEMORY_TARGET not supported on this system"
// *Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.
// *Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.
[root@em12c ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 89355588 30211108 54532224 36% /
/dev/sda5 295561 16082 264219 6% /boot
tmpfs 517368 0 517368 0% /dev/shm
/dev/sda1 40313964 5166748 33099332 14% /orasoft
[root@em12c ~]# umount /dev/shm
[root@em12c ~]# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda7 89355588 30211112 54532220 36% /
/dev/sda5 295561 16082 264219 6% /boot
/dev/sda1 40313964 5166748 33099332 14% /orasoft
[root@em12c ~]# vi /etc/fstab
tmpfs /dev/shm tmpfs defaults,size=1024m 0 0
[root@em12c ~]# mount -a
[root@em12c ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda7 86G 29G 53G 36% /
/dev/sda5 289M 16M 259M 6% /boot
/dev/sda1 39G 5.0G 32G 14% /orasoft
tmpfs 1.0G 0 1.0G 0% /dev/shm
SQL> startup
ORACLE instance started.
Total System Global Area 870457344 bytes
Fixed Size 1348384 bytes
Variable Size 486542560 bytes
Database Buffers 377487360 bytes
Redo Buffers 5079040 bytes
Database mounted.
Database opened.
SQL> show parameter memory
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
hi_shared_memory_address integer 0
memory_max_target big integer 832M
memory_target big integer 832M
shared_memory_address integer 0
SQL>
SQL> alter user sysman identified by weblogic1;
exec DBMS_AUTO_TASK_ADMIN.DISABLE(client_name => 'auto optimizer stats collection',operation => NULL,window_name => NULL);
http://micate.me/linux-unzip-2g-large-zip-file-error.note
Archive: End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on
http://downloads.sourceforge.net/project/p7zip/p7zip/9.13/p7zip_9.13_src_all.tar.bz2?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fp7zip%2Ffiles%http://downloads.sourceforge.net/project/p7zip/p7zip/9.13/p7zip_9.13_src
/article/8564422.html
http://www.bitscn.com/pdb/oracle/200807/146636.html
http://space.itpub.net/519536/viewspace-682820
/article/3752967.html
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------
oem agent install
Instructions for installing the agent
Download the Linux_Grid_Control_agent_download_11_1_0_1_0.zip:
Download the Linux_Grid_Control_agent_download_11_1_0_1_0.zip file from OTN.
1. Methods for mass deployment of agents
a. Copy the downloaded file to <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory.(create <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory, if it doesn't exist.)
b. cd <OMS_HOME>/sysman/agent_download/11.1.0.1.0
c. <OMS_HOME>/bin/unzip Linux_Grid_Control_agent_download_11_1_0_1_0.zip
Once the agent software the is staged in the above mentioned directory either of the following methods can be used for mass agent deployment:
-- agentDownload script.
If agent_download.rsp doesn't exists at <OMS_HOME>/sysman/agent_download/11.1.0.1.0 directory then execute the following:
mv agent_download.rsp.bak agent_download.rsp
groupadd oinstall
useradd -g oinstall oem
If you have an Oracle RAC Cluster with multiple nodes, then you must install a Management Agent on each of the nodes separately. In other words, in the Add Host Targets Wizard, you must add each node explicitly as a destination host.
The Add Host Targets Wizard uses SSH to establish connectivity between Oracle Management Service (OMS) and the remote hosts where you want to install the Management Agents.
Only SSH1 (SSH version 1) and SSH2 (SSH version 2) protocols offered by OpenSSH are supported for deploying a Management Agent.
make-3.81
binutils-2.17.50.0.6
gcc-4.1.1
libstdc++-4.1.1
libXtst-1.0.1-3.1(i386)
Destination Host Time Zone Requirements
export TZ='Asia/Shanghai'
<AGENT_HOME>/sysman/admin/supportedtzs.lst
/m01/oracle/agent/core/12.1.0.2.0/sysman/admin/supportedtzs.lst
Verify whether the SSH server can access the TZ environment variable by logging in to the OMS host, and running the following command:
ssh em12c echo $TZ
ssh xpli $TZ
sudo/pbrun/sesu/su SSH Requirements:
If you are using sudo as your privilege delegation tool, and you do not want to set the oracle.sysman.prov.agentpush.enablePty property to true, do one of the following:
Include Defaults visiblepw in the /etc/sudoers file, or enter the sudo command with the -S option for Privileged Delegation Setting on the Installation Details page.
For information on how to access the Installation Details page, see Installation Procedure.
Comment out Defaults requiretty in the /etc/sudoers file.
sudo/pbrun/sesu/su Requirements (for Root User):
Ensure that the installing user has the privileges to invoke the id command and the agentdeployroot.sh script as root. Grant the privileges in the configuration file of your privilege delegation tool.
For example, if you are using sudo as your privilege delegation tool, include the following in the /etc/sudoers file to grant the required privileges:
oracle ALL=(root) /usr/bin/id, /home/oracle/agentibd/*/agentdeployroot.sh
Here, oracle is the installing user, and /home/oracle/agentibd is the agent base directory.
Unset the CLASSPATH environment variable.You can always reset the variable to the original value after the installation is complete.
Central Inventory (oraInventory) Requirements:
Ensure that you have read, write, and execute permissions on oraInventory on all remote hosts. If you do not have these permissions on the default inventory (typically at /etc/oraInst.loc) on any remote host, then ensure that you specify the path to an alternative
inventory location by using one of the following options in the Additional Parameters field of the Add Host Targets Wizard. However, note that these parameters are supported only on UNIX platforms, and not on Microsoft Windows platforms.
INVENTORY_LOCATION=<absolute_path_to_inventory_directory> -invPtrLoc <absolute_path_to_oraInst.loc>
Installing User Requirements:
If the central inventory owner and the user installing the Management Agent are different, then ensure that they are part of the same group.
Also ensure that the inventory owner and the group to which the owner belongs have read and write permissions on the inventory directory.
For example, if the inventory owner is abc and the user installing the Management Agent is xyz, then ensure that abc and xyz belong to the same group, and they have read and write access to the inventory.
Browser Requirements:
If you use Microsoft Internet Explorer 8 or 9, do the following:
Turn off the compatibility view mode. To do so, in Microsoft Internet Explorer, from the Tools menu, click Compatibility View to disable it if it is enabled. Also, click Compatibility View Settings and deregister the Enterprise Manager Cloud Control console
URL.
Enable XMLHTTP. To do so, from the Tools menu, click Internet Options. Click the Advanced tab, and under the Security heading, select Enable native XMLHTTP support to enable it.
INVENTORY_LOCATION=/m01/oracle -invPtrLoc /m01/oracle/emagent_oraInst.loc
[oem@xpli oracle]$ cat /m01/oracle/emagent_oraInst.loc
inventory_loc=/u01/app/oraInventory
[oem@xpli oracle]$
-----------------------------------------------------------------------------
$OMS_HOME/bin/emctl stop oms -all
$AGENT_HOME/bin/emctl stop agent (-all)
$OMS_HOME/bin/emctl start oms
$AGENT_HOME/bin/emctl start agent
自动发送邮件设置：
在Management Repository server和OMS server的/etc/hosts文件中加入smtp服务器域名解析：
[root@em12c ~]# cat /etc/hosts
127.0.0.1 localhost
192.168.128.216 xpli
123.58.178.204 smtp.163.com
192.168.128.212 em12c
[oem@em12c .ssh]$ ssh vm10g date
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: POSSIBLE DNS SPOOFING DETECTED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
The RSA host key for vm10g has changed,
and the key for the according IP address 192.168.128.220
is unknown. This could either mean that
DNS SPOOFING is happening or the IP address for the host
and its host key have changed at the same time.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
ce:bd:31:55:44:c0:44:76:60:db:6c:a4:05:72:03:85.
Please contact your system administrator.
Add correct host key in /home/oem/.ssh/known_hosts to get rid of this message.
Offending key in /home/oem/.ssh/known_hosts:3
RSA host key for vm10g has changed and you have requested strict checking.
Host key verification failed.
[oem@em12c .ssh]$
[oem@em12c .ssh]$ ssh vm10g date
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
ce:bd:31:55:44:c0:44:76:60:db:6c:a4:05:72:03:85.
Please contact your system administrator.
Add correct host key in /home/oem/.ssh/known_hosts to get rid of this message.
Offending key in /home/oem/.ssh/known_hosts:3
RSA host key for vm10g has changed and you have requested strict checking.
Host key verification failed.
[oem@em12c .ssh]$
问题原因：之前/etc/hosts文件中vm10g主机ip配置错误，原IP指向em server IP所致，变更IP后原来的ssh认证不可用。
解决：删除EM server和agent服务器oem用户下【.ssh】目录下/home/oem/.ssh/known_hosts文件中vm10g部分，然后重新配置vm10g主机ssh认证即可。
[oem@em12c .ssh]$ cat known_hosts
xpli,192.168.128.216 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA9xVX1fmBi1ICO0xjAxVuK/BMhX1/H5Xn3M5R7mEYpsjSuHBOfGpvbfnSAJikEqW+EYaPZGQzf6Y/z+OP0sYInfgMOxlOxwSEUyjD26K/2ZJmwho2UbRPLS68P30caY4mvEXFesbO2EsZeIl5MvhnHZ52+ItwVDna8ZYUY2aYIK0FjydcnBm3H831mGSyeCM8eh09oCRkRTvMujw5UJRvz5X71ECj/rKMN6y/sYENB9OqW7n1fbYr03WA3Ml1+CdMBIXO1bV4PQlUqCf89j/5BqiVyqlVQPyUtWnLpLMohkNd/Fa5IhZm3m3bPXUiislFbqq2nqTkm5DJZnsKOj3PrQ==
em12c,192.168.128.212 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAl8rWGXROurrpfK4/Nx+8F449ayxx+KynX1SwIhcV/12rdmA9uzJ7Wueq4K8NGZpfPZux1D3Udmfu/goWoynf/ERWO8zr00Wzh9mFQjFX1egBTlJ7B+39kN5pPIZuAaWR1nhNySR2/x8pruTdz9tG0IkTdc8Lul4y2uJtZUUlnEXFWllpCSMtPpQWyQez7LwWXfqa8Z9/wKX+PQ7SXix0xbxRIO75qX7mkpMRLuc5Mse+yWpBsssrGWhRLOJsd+SPWctqHm0vP+JkLlaImrJ9q0yRQ8q6ynXlU53GZHksoFDV8mrTykRdiooExCF2CjpQMmqA929mWtAsXnsU9bfgEQ==
vm10g,192.168.128.220 ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAIEA9dxRS0fa3smSJKtzljkStfDEuSR7R0mQkFM764z+jaRomdFvPlgY0ZZ3vhsqUhJyRMva5bXW+HqHrbh6iNn3ifUBO/feYNHAgaJ/4ODKNwEdObstD7hgknUB/ORTYvtaqG54UjGAqZ8BDVNFvmPbMRQ9rcTEHvBxSHZLTLCnza0=
-------------------------------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------------------------------
em cloud control agent deinstall:
rm -rf $EM_AGENT_DIR
OMS DB:
select t.TARGET_NAME,
t.TARGET_TYPE,
DECODE(a.current_status,1,'Up','Down') Status
from mgmt_targets t,
mgmt_current_availability a
WHERE t.target_guid = a.target_guid
and target_type='oracle_emd'
order by 1,2
exec mgmt_admin.cleanup_agent('192.168.128.220:3872');
SQL>
SQL> select t.TARGET_NAME,
2 t.TARGET_TYPE,
3 DECODE(a.current_status, 1, 'Up', 'Down') Status
4 from mgmt_targets t, mgmt_current_availability a
5 WHERE t.target_guid = a.target_guid
6 and target_type = 'oracle_emd'
7 order by 1, 2
8 /
TARGET_NAME
--------------------------------------------------------------------------------
TARGET_TYPE STAT
---------------------------------------------------------------- ----
192.168.128.220:3872
oracle_emd Down
em12c:3872
oracle_emd Up
vm10g:3872
oracle_emd Up
TARGET_NAME
--------------------------------------------------------------------------------
TARGET_TYPE STAT
---------------------------------------------------------------- ----
xpli:3872
oracle_emd Up
SQL> show user
USER is "SYS"
SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[dbuser@xpli ~]$ sqlplus sysman/weblogic1
SQL*Plus: Release 11.2.0.3.0 Production on Tue Jan 22 15:07:35 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> exec mgmt_admin.cleanup_agent('192.168.128.220:3872');
PL/SQL procedure successfully completed.
SQL> select t.TARGET_NAME,
2 t.TARGET_TYPE,
3 DECODE(a.current_status, 1, 'Up', 'Down') Status
from mgmt_targets t, mgmt_current_availability a
WHERE t.target_guid = a.target_guid
4 5 6 and target_type = 'oracle_emd'
order by 1, 2 7
8 /
TARGET_NAME
--------------------------------------------------------------------------------
TARGET_TYPE STAT
---------------------------------------------------------------- ----
em12c:3872
oracle_emd Up
vm10g:3872
oracle_emd Up
xpli:3872
oracle_emd Up
SQL>
references ：
Agent Upload to OMS Fails if Multiple Agents are Installed and Targets are Discovered as Duplicates in the Grid Console [ID 416898.1]
Grid Control Target Maintenance: How to Manually Remove a De-commissioned Host / Agent from the Grid Control Repository Database? [ID 454081.1]
Details about 'Agent Misconfiguration' Alerts in Grid Console 10.2 and How to Resolve them [ID 741595.1]
How to Cleanly De-Install the EM 10g Agent on Windows and Unix [ID 438158.1]
Grid Control Target Maintenance: Understanding the Target Deletion / Removal Process in the Enterprise Manager Grid Control [ID 271691.1]
Grid Control Target Maintenance: How to Manually Remove a De-commissioned Host / Agent from the Grid Control Repository Database? [ID 454081.1]
Grid Agent Configuration: How to Modify the Port on Which Grid Agent is Running/Installed? [ID 404924.1]
http://blog.csdn.net/wangya822/article/details/7654582
内容来自用户分享和网络整理，不保证内容的准确性，如有侵权内容，可联系管理员处理 
相关文章推荐
- Oracle 12c Study之--Enterprise Manager Cloud Control Install
- Oracle Enterprise Manager Cloud Control 12c(12.1) OMS&Agent安装图文指南
- Oracle Enterprise Manager Cloud Control 12c(12.1) OMS&Agent安装图文指南
- Oracle Enterprise Manager Cloud Control 12c(12.1.0.2.0) install
- Oracle Enterprise Manager Cloud Control 12c 概述
- Oracle Enterprise Manager Cloud Control 12c 概述
- Oracle Enterprise Manager Cloud Control 12c 概述
- Oracle Enterprise Manager Cloud Control 12c R4 安装配置
- Oracle Enterprise Manager Cloud Control 12c 概述
- Oracle Enterprise Manager Cloud Control 12c R4 安装配置
- Oracle Enterprise Manager Cloud Control 12c Release 1 Installation on Oracle Linux 5.7 and 6.1
- EM 12c R2: How to Install Enterprise Manager Cloud Control 12.1.0.2 using GUI Mode [ID 1488154.1]
- Oracle Enterprise Manager Cloud Control 12c Installation Guide
- Oracle Enterprise Manager Cloud Control 12c 概述
- Oracle Enterprise Manager Cloud Control 12c 概述
- Oracle Enterprise Manager Cloud Control 12c Release 1 Installation on Oracle Linux
- Oracle Enterprise Manager Cloud Control 12c 概述
- 快速部署Enterprise Manager Cloud Control 12c(12.1) Agent
- Oracle Enterprise Manager Cloud Control 12c 概述
- Oracle Enterprise Manager Cloud Control 12c 概述