grid control em console推送安装agent

gdpr-dba

grid control em console无法在win64位操作系统安装64位的agent，会报如下错误：
java.lang.UnsatisfiedLinkError: Can't load library: c:/DOCUME~1/ADMINI~1/LOCALS~1/Temp/OraInstall2012-03-21_11-05-26AM/oui/lib/win32/oraInstaller.dll
但是却可以在win64操作系统安装32位的agent，只不过安装后em界面会显示操作系统位数为32位。
目前的解决办法是在客户端用命令行静默安装agent：setup.exe -silent -responseFile f:\additional_agent.rsp
但是始终想不明白为什么在em console安装不了。

Maclean Liu(刘相兵

1. msinfo32.exe 命令确认 Windows是64 bit的

2. 使用静默方式安装AGENT，如使用agent_download 脚本：

How to use the Grid Control agent_download script for a different target OS

OR

http://docs.oracle.com/cd/E11857 ... _agent_agtdwnld.htm

Maclean Liu(刘相兵

How to use the Grid Control agent_download script for a different target OS


Applies to:
Enterprise Manager Grid Control - Version: 10.1.0.2.0 to 10.1.0.5.0
Information in this document applies to any platform.
Goal

The agent_download script is used to install the Oracle Management Agent with Grid Control installed on a different Operating System than the target.
Solution

This note is intended to clarify exactly how to stage the files for the agent_download script for a Grid Control on one O/S and a target on another O/S.

For example: Grid Control on HP, with AIX for the target where the Management Agent is to be installed.

Note: for Unix without RAC, this works for any Grid Control and any target O/S combination.
(See Windows note and RAC note below.)


1. Review the Note 235287.1 for general details.

Note 235287.1: How To Install The Downloadable Central Management Agent in EM
10g Grid Control

For the Silent Install option, the Note 235287.1 assumes in that the O/S-specific Agent files have already been downloaded to the OMS.


2. To get the O/S-specific Agent files, use OTN and download the "Mass Depoly Agent" option for the target O/S, eg AIX.

    Reference (as of time of publication):
    URL = http://www.oracle.com/technology/software/products/oem/index.html
    Mass Agent Deployment
    Oracle Enterprise Manager 10g Grid Control Management Agent Release 1

Download to a temporary location allows file copying into the OMS directory structure as required.


3. Expand as per the note on the page, and copy the files into the Directory as per the README.

    Copy the files into the $O_H/sysman/agent_download-- for example:
    README.aix
    agent_download.aix
    aix (this expands into a directory)


4. Follow the README and modify the script as directed.

This step is O/S-specific so it will differ, but basically you're identifying the OMS and the download method for pulling the files.

Be sure that the program called in the script to do the download is supported on the target O/S.

The script provided by Oracle uses the wget utility to perform the actual file transfer, and this is the expected method.
Other protocols may be used, such as ftp or http, but Oracle does not provide scripting for alternaitve transfer methods.
The provided script must be manually customized based on the target O/S, in this case.

5. After adapting the script for the OMS name and port, open a browser on the on the AIX target and enter this browser URL:

    URL = http://<grid_node>:4889/agent_download/

Download the O/S-appropriate script to the AIX node, usually using browser access, if allowed:

    Example: download the script
    agentDownload.aix

6. If there is no browser on the target then download the script manually, by ftp for example:

    ftp <aix-host>
    mget $Grid_ORACLE_HOME/sysman/agent_download/agentDownload.aix


7. Run the agentDownload.aix script on the target node to pull the files from the O/S.

This will install the Agent by copying over the needed files from the Grid Control $ORACLE_HOME/sysman/agent_download/aix directory, and running the required executables on the target node where the agent will be installed. Configuration is done based on the values provided for Grid Control hostname, port, etc. in the script configuration step #4 above.

No manual installation of the Oracle Universal Installer (OUI) is needed on the target node when using this method. The agent_download script installs the needed software.




Note #1: for Windows the downloadable Agent is not available in 10.1.0.3.0.

Note #2: The agent_download script does not work for RAC targets due to unpublished Bug 4369095, projected to be fixed in 10gRelease2. Workaround is to do the install Manually, using the OUI.
Bug 4369095: IN RAC MACHINE AGENT DOWNLOAD SCRIPT DOESN'T COPY THE FILE IN REMOTE NODE

Maclean Liu(刘相兵

你可以debug OUI看一下原因

如何启用OUI的debug和trace功能？

    OUI工具存在”-debug”选项
        将启用最精细级别的信息日志
        将显示启动阶段的信息（例如抽取JRE)
        在对OUI进行可能由java引起的问题诊断时十分有效
        举例来说: ./runInstaller -debug
    另一方面可以对OUI启用系统调用跟踪trace,一般我们使用操作系统提供的tracing工具
        举例而言:truss -aefo /tmp/oui_trace.log ./runInstaller
        参考文档：Note 110888.1 介绍了如何trace Unix下的系统调用
        绝大多数OUI意外终止的问题可以从.ERR文件中找到相关问题
        OUI: “Abnormal program termination” with java.io.IOException in .err file [ID 798338.1]


http://www.oracledatabase12g.com ... aller-oui-text.html

gdpr-dba

谢谢，不过我还有疑问，就是debug具体该怎么做？
因为直接在客户端安装agent是可以的，所以在客户端直接debug应该是没什么意义的，唯一不行的是用em来推送安装，如何跟踪em的推送安装过程才是关键吧。

Maclean Liu(刘相兵

"因为直接在客户端安装agent是可以的" “grid control em console无法在win64位操作系统安装64位的agent，会报如下错误”

看来存在misunderstanding， 我理解你是在TARGET SERVER上安装 AGENT MEDIA失败， 如果你是在GRID CONTROL 的页面上尝试安装AGENT失败的话，可能是 GC 的BUG， 我本人也不建议这样安装，而建议通过介质或者agent_download安装代理。 或者至少升级 OMS到LATEST RELEASE。