Enterprise Manager Agent Installation fails with emnoseed.rsp file doesnot exists. Error

##########################
## Error
##########################

emnoseed.rsp file doesnot exists.

### Full Error

ERROR:  /u01/app/oracle/product/11.2.0.3/linux_x64/agent//install/response//emnoseed.rsp file doesnot exists.

##########################
#  Error Occurred
##########################

Error occured while trying to install Enterprise Manager Grid Agent of 11.1.0.1.0 version using Oracle Universal Installer ( OUI ) in Linux Platform

##########################
## Command Executed
##########################

In terminal,

./runInstaller

##########################
## Issue Description.
##########################

### 11.1.0.1.0

#########################################
# AGent Installation Logs
#########################################

Error occured while trying to install Enterprise Manager Grid Agent of 11.1.0.1.0 version using Oracle Universal Installer ( OUI ) in Linux Platform.

no_sid @ hostp20:/u01/app/oracle/product/11.2.0.3/linux_x64/agent
> ./runInstaller
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 150 MB.   Actual 1834 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 32765 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 32768    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-12-03_12-07-46AM. Please wait ...no_sid @ hostp20:/u01/app/oracle/product/11.2.0.3/linux_x64/agent
>
ERROR:  /u01/app/oracle/product/11.2.0.3/linux_x64/agent//install/response//emnoseed.rsp file doesnot exists.

#### Note :

In 11.1.0.1 versions, Agent installation is not possible in GUI mode.

when we try the same in Other platforms of 11.1.0.1 version, OUI will warn that the GUI-based OUI is not a valid option for the 11.1.0.1 Agent installation.

In Linux Platforms, there is a internal BUG due to which this message is not being displayed to user and emnoseed.rsp file doesnot exists error occurs.

##########################
## Solution
##########################

Try a silent mode of installation. Below are the methods available for Agent Installation. Oracle Documentation is available for these methods.

I will try to post the detailed steps for different methods of agent installation.

1) Installing Oracle Management Agent on a Cluster Using Agent Deployment Wizard

2) Installing Oracle Management Agent Using Shared Oracle Home

3) Cloning Oracle Management Agent Using Agent Cloning Wizard

4) Installing Oracle Management Agent Using Response File

5) Installing Oracle Management Agent Using agentDownload Script

6) Installing Oracle Management Agent on a Cluster Using Response File or agentDownload Script

7) Installing Oracle Management Agent Using Shared Oracle Home Using nfsagentinstall Script

8) Cloning Oracle Management Agent Using ZIP File

9) Cloning Oracle Management Agent on Clusters Using ZIP File

PRCD-1229 : An attempt to access configuration of database mydb was rejected because its version 11.2.0.3.0 differs from the program version 11.2.0.2.0. Instead run the program from /u01/app/oracle/product/11.2/db_11.

##########################
## Error
##########################

mydb_1 @ siodserver4:/u01/app/oracle/diag/rdbms/mydb/mydb_1/trace
> srvctl status database -d mydb
PRCD-1027 : Failed to retrieve database mydb
PRCD-1229 : An attempt to access configuration of database mydb was rejected because its version 11.2.0.3.0 differs from the program version 11.2.0.2.0. Instead run the program from /u01/app/oracle/product/11.2/db_11.


##########################
## Cause
##########################

Error occured while trying to check the status of the database using srvctl command in 11.2.0.3.0 version

##########################
## Command Executed
##########################

srvctl status database -d mydb

##########################
## Solution
##########################

### 11.2.0.3.0

The above error has occurred because of the environment settings. Recently we have upgraded this database from 11.2.0.2.0 version to 11.2.0.3.0 version.

Eventhough CRS is updated with the latest 11.2.0.3.0 home, oratab file is still pointing to 11.2.0.2.0 home. so i have modified it to use 11.2.0.3.0 home and srvctl commands worked like a charm.

mydb_1 @ siodserver4:/u01/app/oracle/diag/rdbms/mydb/mydb_1/trace
> cat /etc/oratab |grep -i mydb
#mydb:/u01/app/oracle/product/11.2/db_4:N             # line added by Agent
#mydb_1:/u01/app/oracle/product/11.2/db_4:N   ## Commented by Sri on 30-nov-2012
#mydb_2:/u01/app/oracle/product/11.2/db_4:N   ## Commented by Sri on 30-nov-2012

mydb:/u01/app/oracle/product/11.2/db_11:N             # line added by Agent
mydb_1:/u01/app/oracle/product/11.2/db_11:N
mydb_2:/u01/app/oracle/product/11.2/db_11:N

mydb_1 @ siodserver4:/u01/app/oracle/diag/rdbms/mydb/mydb_1/trace
> srvctl status database -d mydb
Instance mydb_1 is running on node siodserver4
Online relocation: INACTIVE

If Oracle clusterware keys are not updated then use below command to update this information in cluster.

<11 .2.0.3_home=".2.0.3_home">/bin/srvctl upgrade database -d -o <11 .2.0.3_home=".2.0.3_home">

Command to check the database home :
-------------------------------------

+ASM2 @ siodserver4:/u01/app/oracle/diag/rdbms/mydb/mydb_1/trace
> srvctl config database -d mydb
Database unique name: mydb
Database name: mydb
Oracle home: /u01/app/oracle/product/11.2/db_11
Oracle user: oracle
Spfile: +mydb_DATA/mydb/spfilemydb.ora
Domain: corp.mycompany.com
Start options: open
Stop options: immediate
Database role: PRIMARY
Management policy: AUTOMATIC
Server pools: mydb
Database instances:
Disk Groups: mydb_DATA,mydb_RECO
Mount point paths:
Services: mydb_svc
Type: RACOneNode
Online relocation timeout: 10
Instance name prefix: mydb
Candidate servers: siodserver3,siodserver4
Database is administrator managed