emnoseed.rsp

Attempting to Launch the Installer for 11.1.0.1 Grid Control Agent on Linux x86_64 Results in "Error: emnoseed.rsp file does not exists" [ID 1109397.1]

Applies to:

Enterprise Manager Base Platform - Version: 11.1.0.1 to 11.1.0.1 - Release: 11.1 to 11.1
Linux x86-64

Symptoms

Invoking the 11.1.0.1 installer from the Agent-only software onLinux x86_64 returns the following error:

./runInstaller
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 150 MB. Actual 4077 MB Passed
Checking swap space: must be greater than 150 MB. Actual 16386 MB Passed
Checking monitor: must be configured to display at least 256 colors. Actual 65536 Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010-05-25_04-47-57PM. Please wait ...-sh-3.2$
ERROR: /u01/product/stage/agent/linux_x64/agent//install/response//emnoseed.rsp file does not exists.

Cause

Attempting to install the 11.1.0.1 Grid Agent by simply invoking the runInstaller from the Agent software causes this error and has been logged in the internal Bug: OUI SHOULD GIVE CLEAR MESSAGE THAT AGENT INSTALL IS SUPPORTED IN SILENT MODEONLY

On other platforms, the installer will warn the user that the GUI-based OUI is not a valid option for the 11.1.0.1 Agent installation.

Solution

In the 11.1.0.1 release, it is not possible to install the Grid Agent by invoking the installer in the GUI mode. Various supported methods of Agent installation are mentioned in the following link and reference:

Oracle Enterprise Manager Grid Control Advanced Installation and Configuration Guide 11g Release 1 (11.1.0.1.0), Part Number E16847-07, Part III Installing Oracle Management Agent

Install the agent using this command with the agentDownload script (generic format):
./agentDownload.linux_x64 –b <base directory> -m <OMS hostname> -r <OMS upload port> -y
The “-y” option will bypass the update configuration for those who do not desire security or software updates.
Example:
./agentDownload.linux_x64 –b /u01/app/agent –m em-64lnx1.us.oracle.com –r 7799 –y
In this example, the 7799 port is used because it is the secure upload port and the OMS is locked, so it is the only port that can be used. When working with an unlocked OMS, other port numbers can be used also.