ITPub博客

首页 > 数据库 > Oracle > ORACLE_Enterprise_Manager_Ops_Center_12c_测试安装文档

ORACLE_Enterprise_Manager_Ops_Center_12c_测试安装文档

原创 Oracle 作者:jingwei269 时间:2014-04-15 11:06:23 0 删除 编辑

ORACLE Enterprise Manager Ops Center 12c 测试安装文档

参考文档:

Installation Guide for Linux Operating Systems  12c Release 1 (12.1.4.0.0) E25139-06

 

 

安装前准备工作:

  1. 操作系统RHEL5.4及以上版本,内存4G以上建议6Gswap建议8G及以上),磁盘根目录空间70G以上。

    安装光盘挂载到服务器上,便于安装缺失程序包。

  2. 数据库准备:装完数据库后再安装OPS。(数据库的安装略,使用Oracle11201 64位。)

  3. 数据库用户准备:使用Remote的方式进行安装的时候,需要运行Create Schema脚本。脚本位于OPS解压后的目录….xvmoc_full_bundle/Linux_i686/Product/installer/scripts/createOCSchema_remote.sql,运行脚本需要注意,表空间需要事先准备好。

 

环境介绍及安装包下载:

OEL6.4 64+Oracle1120164位,安装32位提示不兼容,ignore后安装过程中出错。)

OPS包:https://edelivery.oracle.com

 

准备安装,解压包后:

 

在数据库运行脚本:

脚本位于OPS解压后的目录….xvmoc_full_bundle/Linux_i686/Product/installer/scripts/createOCSchema_remote.sql

 

SQL> conn / as sysdba

Connected.

SQL> @/u01/app/createOCSchema_remote.sql

"SQLTrace: Entering createOCSchema_remote.sql"

Enter username for Ops Center database login: ops

Enter password for Ops Center database login:

Enter username for read only Ops Center database login: ops_ro

Enter password for read only Ops Center database login:

Enter default tablespace for Ops Center user: ops

Enter temporary tablespace for Ops Center user: temp

Enter Oracle Data Pump destination directory: /u01/app/pump

 

"Done creating OC_SYSTEM_ROLE and OC_RO_ROLE"

"Done creating OC_PROFILE"

"Done creating Schema 'ops'. Roles and privileges have been granted."

"Done creating Schema 'ops_ro'. Roles and privileges have been granted."

"Did not recreate directory OC_DUMP_DIR.  It exists at DATA_PUMP_DIR"

Elapsed: 00:00:00.02

"Done creating OC_DUMP_DIR at /u01/app/pump"

"Done granting privs"

"Testing connectivity to the new schema: 'ops'"

Connected.

"Testing connectivity to the new read only schema: 'ops_ro'"

Connected.

 

"Create is Complete. OC can now be used with the new schema: 'ops'"

 

 

"SQLTrace: Exiting createOCSchema_remote.sql"

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

 

完成后,编写DBprops文件:

[root@opscenter xvmoc_full_bundle]# cat /u01/remote.txt

mgmtdb.appuser=ops

mgmtdb.password=ops

mgmtdb.roappuser=ops_ro

mgmtdb.ropassword=ops_ro

mgmtdb.dburl=jdbc:oracle:thin:@opscenter:1521/bule

完成后运行install命令:

[root@opscenter xvmoc_full_bundle]# ./install  --remoteDBprops=/u01/remote1.txt

 

最终效果图如下:(期间省略若干缺失包的问题,自行安装之,需要仔细观察错误提示)

                            Ops Center Enterprise Controller Installer

                              (version 12.1.4.2319 on Linux)

 

 1. Check for installation prerequisites.                                        [Completed]

 2. Check that required RPM packages are present.                              [Completed]

 3. Configure file systems.                                                  [Completed]

 4. Install prerequisite packages.                                            [Completed]

 5. Install Agent components.                                                 [Completed]

 6. Create Deployable Proxy Bundles.                                          [Completed]

 7. Install application packages.                                             [Completed]

 8. Run postinstall tasks.                                                    [Completed]

 9. Install IPMI tool.                                                        [Completed]

10. Set database credentials.                                                 [Completed]

11. Install and Configure Oracle Database.                                    [Completed]

12. Seed Ops Center Database Schema                                           [Completed]

13. Install Service container components.                                     [Completed]

14. Install Core Channel components.                                          [Completed]

15. Install Proxy Core components.                                            [Completed]

16. Set Proxy database credentials.                                           [Completed]

17. Install Enterprise Controller components.                                 [Completed]

18. Install Update Connection - Enterprise.                                   [Completed]

19. Install Ops Center BUI components.                                        [Completed]

20. Install OS provisioning components.                                       [Completed]

21. Initialize and start services.                                            [Completed]

 

 

This installer has determined that some rpms currently installed on

this system have later versions than those currently required by Oracle

Enterprise Manager Ops Center. If you encounter any problems related to

these substitutions, you might need to obtain and install the exact

version of the software required by the installer before re-installing

Oracle Enterprise Manager Ops Center.

 

Ops Center Enterprise Controller installation is complete.

 

Please point your browser to:

 

       http://opscenter

 

to begin using Ops Center Enterprise Controller.

 

SO:可以登录http://opscenter查看效果:(注:opscenterhosts中配置的名字)

登录后进行一系列的配置,按照提示即可。(如果没有MOS或者无法连接Internet,则需要选择disconnect模式。)

配置完成后,效果图差不多如此:

 

 

 

 

 

 

 

 

 

 

 

 

SO:添加一个监控来看看。

客户端设置:

客户端需要安装agent后,才能被服务端监控。Agent安装包位于:

/var/opt/sun/xvm/images/agent目录,目前有SolarisLinuxagent包。

使用scp从服务器端拷贝至客户端后:

 

解压安装包:

bash-3.2# unzip OpsCenterAgent.Linux.i686.12.1.4.2319.zip

bash - 3 . 2 # cd OpsCenterAgent
bash
- 3 . 2 # ls
i386   install   README   utils   x86_64

[root@node3 bin]# cd /opt/sun/xvmoc/bin/

[root@node3 bin] # ls
agentadm   passwordfile
[root@node3 bin]
#
[root@node3 bin]
# cat passwordfile     # 指定用户的 password configure 命令密码采用密码文件。
cybertech

 

安装agent包:

使用命令进行配置 :使用 root 用户,监控中心地址 192.168.11.217 ,本地地址 192.168.11.218.
[root@node3 bin] # ./agentadm configure -u root -p /opt/sun/xvmoc/bin/passwordfile -x 192.168.11.217 -a 192.168.11.218
agentadm : Version 12 . 1 . 4 . 2319 launched with args : configure - u root - p / opt / sun / xvmoc / bin / passwordfile - x 192 . 168 . 11 . 217 - a 192 . 168 . 11 . 218
Validating step
: workarounds configure    - u root - p / opt / sun / xvmoc / bin / passwordfile - x 192 . 168 . 11 . 217 - a 192 . 168 . 11 . 218    
Validating step
: sc_console configure    - u root - p / opt / sun / xvmoc / bin / passwordfile - x 192 . 168 . 11 . 217 - a 192 . 168 . 11 . 218    
verified sc_console command is OK
Validating step
: setup_hmp configure      - u root - p / opt / sun / xvmoc / bin / passwordfile - a 192 . 168 . 11 . 218   
Validating step
: scn_agent configure    
Checking
if package 'sun-cacaome' exists.
scn_agent Common Agent Container environment is OK
Validating step
: uce_agent configure    
Validating step
: config_sysconfig configure    
End of validation
executing step
: workarounds
workaround   configuration
done .
executing step
: sc_console
verified sc_console command is OK
Configuring sc_console
checking existing sc_console connections
doing sc
- console registration
Certificate
:
Serial Number
:             1326735924
Version
:                   3
Issuer
:                   CN = opscenter_scn - proxy_agent
Subject
:                  CN = opscenter_scn - proxy_agent
Not valid before
:         Thu Jan 01 08 : 00 : 00 GMT + 08 : 00 1970
Not valid after
:          Mon May 02 10 : 05 : 51 GMT + 08 : 00 2033
Accept server
's certificate? (y|n)
y
Connection registered successfully.
sc-console registration done
executing step : setup_hmp
hwmgmtd service does not exist on this system
executing step : scn_agent
Checking if package ' sun - cacaome ' exists.
scn_agent Common Agent Container environment is OK
Configuring for an Agent Controller
Checking if the cacao scn-agent instance exists
creating cacao scn-agent instance
getting parameter value from cacao instance for micro-agent
getting parameter value from cacao instance for jmxmp-connector-port
setting the cacao scn-agent instance parameter java-flags to -Xmx48M -Xss192k -Dcom.sun.management.jmxremote -Dfile.encoding=utf-8 -Djava.endorsed.dirs=/usr/lib/cacao/lib/endorsed
setting the cacao scn-agent instance parameter jmxmp-connector-port to 0
setting the cacao scn-agent instance parameter micro-agent to true
Enabling scn-agent instance.
setting the cacao scn-agent instance parameter log-file-count to 10
setting the cacao scn-agent instance parameter log-file-limit to 10000000
setting log level for agent facade module
Checking AC log levels
Setting AC log levels
Daemon must be running in order to perform this operation.
Daemon must be running in order to perform this operation.
Starting scn-agent instance.
Waiting for instance scn-agent to be up.
Daemon is running but not available. Try again as it might be starting.
Daemon is running but not available. Try again as it might be starting.
scn-agent configuration done.
executing step : uce_agent
unconfiguring the uce agent
executing ' / etc / init.d / sun_scn_update_agent stop ' to stop the uce agent
uce_agent.bin is shutting down gracefully.   This may take a few minutes, please be patient.
Shutting down uce_agent.bin daemon ..., the daemon was not running, ...     [FAILED]
Command to stop uce_agent daemon returns [1].
Checking if UCE Agent process is still running, it may take a couple of minutes ...
Process is no longer running
UCE Agent is stopped.
configuring uce agent
chown: `uce-sds:uce-sds' : invalid user
rm : cannot remove ` / opt / sun / scn / update - agent // bin / .uce.rc. 11762 ': No such file or directory
Starting uce_agent.bin daemon, see /opt/sun/scn/update-agent//logs/error.log for details:      [   OK   ]
Checking if UCE Agent process is up and running ...
The process is up and running.
UCE Agent is started.
executing step : config_sysconfig
End of configuration.

 

至此客户端配置结束。

 

登录OPS-center查看效果:

 

登录后的初始界面:

点开Assets—>Services,看见node3,即为刚才添加的监控客户端:

点击node3查看详细,可见Dashboard,Analytics,Connectivity等页签:

点开Analytics页签,发现有SummaryProcessThresholds等页签:

该页签包含CPU,MEMORY,NETWORK,I/O的情况,并排序TOP5

点击AnalyticsàProcesses子页签,显示所有Process,并可以根据使用情况进行排序:

Kill一个Session

Kill session完成后,右下角弹出提示框,并可点击查看详细信息:

 

阀值监控:

History查看:

Incidents

 

试一下Reboot机器:

Node3重启:

重启任务完成:

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/15173958/viewspace-1142337/,如需转载,请注明出处,否则将追究法律责任。

请登录后发表评论 登录
全部评论

注册时间:2009-06-17

  • 博文量
    5
  • 访问量
    23237