Oracle Enterprise Manager Grid Control 11g Installation:Before installing the grid control, we need to install weblogic server.

Oracle Weblogic Installation:

Go to Weblogic dump location and invoke the installer.

[oradb@prithvi 11gGrid_32]$ cd /u01/softwares/weblogic

[oradb@prithvi weblogic]$ ./wls1032_linux32.bin

Extracting 0%....................................................................................................100%

The weblogic Admin server console URL is: https://prithvi.bangalore.bedford.local:7101/console

Pre-requisites for Installing Oracle Enterprise Manager 11g Grid Control:1. Create Operating System Groups and users Check if the Oracle Inventory exists# more /etc/oraInst.loc Creating Oracle inventory group, OSDBA group, OPER group and Oracle software user

# /usr/sbin/groupadd oinstall

# /usr/sbin/groupadd dba

# /usr/sbin/groupadd oper

# /usr/sbin/useradd -g oinstall -G dba[,oper] oracle

2. Install OS packages

The following packages must be installed from the Oracle Linux 5 or RHEL 5 distribution media: Package Requirements for Oracle Management Servicerng-utils-2

make-3.81

binutils-2.17.50.0.6

gcc-4.1.1

libaio-0.3.106

glibc-common-2.3.4-2.9

compat-libstdc++-296 -2.96-132.7.2

libstdc++-4.1.1

libstdc++-devel-4.1.1

setarch-1.6-1

sysstat-5.0.5-1

compat-db-4.1.25-9

Package Requirements for Oracle Management Agent make-3.81binutils-2.17.50.0.6gcc-4.1.1libstdc++-4.1.1Libaioglibc-devel (64-bit)glibc-devel (32-bit) Kernel Parameter Requirements for Oracle Management Service and Oracle Management AgentIf we have to install a new Enterprise Manager system, an additional OMS, or a standalone Management Agent on any Linux operating sytem (Red Hat Enterprise Linux 4 or 5, Oracle Linux 4 or 5, Asianux Linux 3, and SUSE Linux Enterprise Server 10), then we have to set the kernel.shmmax parameter to a value that is not greater than 4 GB. This parameter is present in the /etc/sysctl.conf file. Library Requirements for Oracle Management Service

GLIBC-2.5-12 library is required for installing new Enterprise Management System or an additional OMS.

3. Unique Host Name and Static IP Address Requirements

Ensure that we check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network.Note: You must use only a static IP address. If you use a dynamic IP address, the installation will fail.

4. File Descriptor Requirements

/bin/sh -c "ulimit -n"

4096

If the current value is not 4096, then as a root user, update the /etc/security/limits.conf file with the following entries:

soft nofile 4096

hard nofile 4096

5. JDK Requirements

For Linux (64 bit) SUN JDK 1.6_18+ is to installed separately. (On Linux 32-bit platforms, you need not install JDK because it is packaged by default with Oracle WebLogic Server)

To check JDK installed, query the following to get version of JDK

Java fullversion

6. Oracle WebLogic Server Requirements

Oracle weblogic 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1)only should be installed prior to the installation of Oracle Enterprise Manager Grid Control. While Installing the weblogic select installation type Typical and no other Fusion Middleware products or components should be installed in the Middleware Home directory where Oracle WebLogic Server 10.3.2 is installed.

Oracle WebLogic Server Patch Requirements: We have to apply patch ID WDJ7 on Oracle WebLogic Server using the Oracle Smart Update utility. This patch fixes bugs 8990616, 9100465, and 9221722.

For information on applying this patch, see My Oracle Support note 1072763.1.

7. Database Partitioning RequirementsThe Database must have partitioning enabled. To verify this, connect to the database as SYSDBA and run the following query:

select value from v$option where parameter = 'Partitioning';

8. Existing Database Not to Be in QUIESCE Mode

The Database must not be quiesce state. To verify this, run the following query.

select active_state from v$instance;

9. Existing Database Not to Have Database Control

We need to check that the Existing Oracle Database does NOT have Database Control SYSMAN schema. If it has, that is, if your existing database is configured with Database Control, then deconfigure it.

To verify whether your database has Database Control SYSMAN schema, run the query.

SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME='SYSMAN';

If the query results 1, then the database has this schema and we need to de-configure the database control. Before deconfiguring the database control, set the ORACLE_SID and ORACLE_HOME parameters and run the following command as database user.

$ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD -SYSMAN_PWD[oradb@prithvi bin]$ emca -deconfig dbcontrol db -repos drop -aux11g -aux11g

STARTED EMCA at Aug 17, 2012 4:31:35 AM

EM Configuration Assistant, Version 11.2.0.0.2 Production

Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the following information:

Database SID: aux11g

Listener port number: 1565

Password for SYS user:

Password for SYSMAN user:

----------------------------------------------------------------------

WARNING : While repository is dropped the database will be put in quiesce mode.

----------------------------------------------------------------------

Do you wish to continue? [yes(Y)/no(N)]: Y

Aug 17, 2012 4:31:50 AM oracle.sysman.emcp.EMConfig perform

INFO: This operation is being logged at /u02/app/oradb/cfgtoollogs/emca/aux11g/emca_2012_08_17_04_31_35.log.

Aug 17, 2012 4:31:51 AM oracle.sysman.emcp.util.GeneralUtil initSQLEngineLoacly

WARNING: ORA-01017: invalid username/password; logon denied

Aug 17, 2012 4:31:51 AM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl

WARNING: Error initializing SQL connection. SQL operations cannot be performed

Aug 17, 2012 4:31:51 AM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration

WARNING: EM is not configured for this database. No EM-specific actions can be performed. Some of the possible reasons may be:

1) EM is configured with different hostname then physical host. Set environment variable ORACLE_HOSTNAME= and re-run EMCA script

2) ORACLE_HOSTNAME is set. Unset it and re-run EMCA script

Aug 17, 2012 4:31:51 AM oracle.sysman.emcp.EMReposConfig invoke

INFO: Dropping the EM repository (this may take a while) ...

Aug 17, 2012 4:43:55 AM oracle.sysman.emcp.EMReposConfig invoke

INFO: Repository successfully dropped

Enterprise Manager configuration completed successfully

FINISHED EMCA at Aug 17, 2012 4:43:55 AM10. Existing Database Not to Have SYSMAN and SYSMAN_MDS SchemaWe need to check that the existing Database does NOT have SYSMAN and SYSMAN_MDS schema.

To verify whether your database has Enterprise Manager Grid Control SYSMAN schema and MDS schema.

SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS'); If the result of this query is 1, then the database has these schemas, so we need to drop them. Drop the schema by running the following commandDrop user SYSMAN_MDS cascade;

Check for entries in the table SCHEMA_VERSION_REGISTRY. Delete entries where comp_name='Metadata Services'.

delete from SCHEMA_VERSION_REGISTRY where COMP_NAME='Metadata Services';If you find any invalid objects then run "admin_recompile_invalid.sql" for users 'DBSNMP' and 'MGMT_VIEW'.

11. Database Initialization Parameters RequirementsThese are the required settings:Parameter Value

Compatible 10.2.0 or higherremote_login_passwordfile EXCLUSIVE

statistics_level TYPICALtimed_statistics TRUEundo_management AUTOworkarea_size_policy AUTOdb_block_size 8192 or higher

job_queue_processes 10 or higher

log_buffer 10485760 or greateropen_cursors 300 or higher

processes 500 or greater

session_cached_cursors 200 or greater

12. Fine-Grained Access Control Requirements

The fine-grained access control option is set to TRUE, for the Oracle Database so that the Management Repository can be created.select value from v$option where parameter = 'Fine-grained access control';

13. UNDO Tablespace and Temporary Tablespace Settings RequirementsThe UNDO tablespace should have a minimum space of 200 MB. To verify this run the following query.

SELECT SUM(DECODE(autoextensible,'YES',200*1024*1024+1,bytes)) total FROM dba_data_files f, dba_tablespaces s WHERE s.contents = 'UNDO' AND s.tablespace_name = f.tablespace_name;Also we need to check that the UNDO tablespace and the TEMP tablespace have Autoextensible enabled.

select count(*) from dba_temp_files where tablespace_name='TEMP' and AUTOEXTENSIBLE 'YES';

select count(*) from dba_data_files where tablespace_name='UNDOTBS' and AUTOEXTENSIBLE 'YES';

14. Archive Logging Settings RequirementsThe Archivelog should be enabled for the database.

Select log_mode from v$database;

Installation Instructions:

1. No environment variable specific to Enterprise Manager Grid Control needs to be set prior to installation. The ORACLE_HOME and ORACLE_SID variables should not be set; Oracle directories should not appear in the PATH.2. While installing on hosts having multiple IP addresses, the host name is derived from the ORACLE_HOSTNAME variable that is passed while invoking the installer.3. Go to the 11g grid software location and invoke the following command.

[oradb@prithvi ~]$ cd /u02/old_downloads/11gGrid_32/

[oradb@prithvi 11gGrid_32]$ ./runInstallerOR

[oradb@prithvi 11gGrid_32]$ ./runInstaller ORACLE_HOSTNAME=prithvi.bangalore.bedford.local

The Enterprise Manager Grid Control URL is : https://prithvi.bangalore.bedford.local:7799/em

Refer:http://docs.oracle.com/cd/E11857_01/install.111/e15838/install_em_exist_db.htm#CHDJDCAGhttp://shibudharmapalan.blogspot.in/2011/04/oracle-enterprise-manager-111010.htmlhttp://balakumarnair.wordpress.com/2011/02/13/oracle-11gr1-enterprise-manager-grid-control-oem-installation-part-1/

OEM 11g Grid Control 8