facebook twitter youtube facebook facebook facebook

E-Mail : info@askmlabs.com

Phone : +1.215.353.8306

Home » , , , » OEM Grid Control 11g(11.1.0.1.0) Installation

OEM Grid Control 11g(11.1.0.1.0) Installation

Written By askMLabs on Monday, May 16, 2011 | 11:06 PM

This article explains the OEM grid control 11g ( 11.1.0.1.0 ) installation on Linux 5.4 (32-bit) OS with 11gR2 database.

Software Requirements:


SUN JDK 1.6_18 ( for 32/64 bit Linux OS) : Download
WebLogic Server 10.3.2(32bit) : Download
Oracle Database 11gR2 : Download
OEM 11g Grid Control( 11.1.0.1.0 ) : Download

Grid Control 11g uses WebLogic Server instead of OC4J which was traditional with Grid Control versions 10.1 and 10.2. Grid Control 11g will deploy from an existing Weblogic Server during the Grid Control Installation. Weblogic server installation requires a JDK 1.6_18 as a pre requisite. A database for repository use must exist at the time of Grid Control 11.1.0.1.0 installation. The option to "Install Grid Control with a new database" is no longer offered. So we need to have  the database created before starting the grid control 11g installation. Please review the Oracle Enterprise Manager Grid Control Certification Checker @ 412431.1 for the database version.

So the sequence of steps to install 11g grid control including all the external components are ..
1) Create Linux Machine
2) Prepare the linux machine for OEM grid control 11g installation.
3) Install JDK 1.6_18
4) Install Weblogic server 10.3.2
5) Install database 11.2.0.1
6) Prepare the database for OEM 11g Installation.
7) Install OEM grid control 11.1.0.1.0
8 ) Status Check
9) Issues and Resolutions


1.Create Linux Machine:


If you are planning to install OEM grid control in a vmware linux machine, Please follow the article VMware Server - Linux installation  and complete the linux machine creation. You can omit this point if you are directly provided with linux machine with OS linux 5.4(32-bit).

2.Prepare the linux machine for OEM grid control 11g installation:


Prepare the linux machine ( Linux 5.4 ) for the OEM grid control 11g installation. Please use the article Prepare Linux virtual machine for 11gR2 installation on Linux 5.x. Though this is to prepare the linux machine for 11gR2 database, it hold good for OEM 11g installation also. You can also refer the installation document here.

Check the following RPMs and make sure all the RPMs are installed.

[sourcecode language="bash"]
[oracle@oem11gmach01 ~]$ rpm -qa | egrep -i "binutils|compat-libstdc|elfutils-libelf|glibc|glibc-common|ksh|libaio|libgcc|libstdc|make"
libgcc-4.1.2-48.el5
automake16-1.6.3-8.el5.1
elfutils-libelf-devel-static-0.137-3.el5
compat-libgcc-296-2.96-138
libstdc++-4.1.2-48.el5
imake-1.0.2-3
compat-libstdc++-33-3.2.3-61
glibc-headers-2.5-49
automake14-1.4p6-13.el5.1
ksh-20100202-1.el5
glibc-common-2.5-49
glibc-2.5-49
elfutils-libelf-0.137-3.el5
binutils-2.17.50.0.6-14.el5
compat-libstdc++-296-2.96-138
glibc-devel-2.5-49
automake-1.9.6-2.3.el5
automake17-1.7.9-7.el5.2
make-3.81-3.el5
libaio-0.3.106-5
automake15-1.5-16.el5.2
elfutils-libelf-devel-0.137-3.el5
libstdc++-devel-4.1.2-48.el5
MAKEDEV-3.23-1.2
[oracle@oem11gmach01 ~]$

[oracle@oem11gmach01 ~]$ rpm -qa | egrep -i "elfutils-libelf-devel|kernel-headers|glibc-headers|glibc-devel|libstdc++-devel|libgomp|gcc-|gcc-c++|libaio-devel|sysstat|unixODBC"
kernel-headers-2.6.18-194.el5
libgcc-4.1.2-48.el5
gcc-gfortran-4.1.2-48.el5
elfutils-libelf-devel-static-0.137-3.el5
compat-libgcc-296-2.96-138
glibc-headers-2.5-49
libgomp-4.4.0-6.el5
glibc-devel-2.5-49
gcc-4.1.2-48.el5
gcc-c++-4.1.2-48.el5
elfutils-libelf-devel-0.137-3.el5
[oracle@oem11gmach01 ~]$ rpm -qa | grep libstdc++-devel
libstdc++-devel-4.1.2-48.el5
[oracle@oem11gmach01 ~]$ rpm -qa | grep libaio-devel
[oracle@oem11gmach01 ~]$

[oracle@oem11gmach01 ~]$ rpm -qa | egrep -i "rng-utils|make|binutils|gcc|libaio|glibc-common|compat-libstdc++|libstdc++|setarch|compat-db"
libgcc-4.1.2-48.el5
automake16-1.6.3-8.el5.1
gcc-gfortran-4.1.2-48.el5
compat-libgcc-296-2.96-138
libstdc++-4.1.2-48.el5
imake-1.0.2-3
compat-libstdc++-33-3.2.3-61
automake14-1.4p6-13.el5.1
rng-utils-2.0-1.14.1.fc6
glibc-common-2.5-49
binutils-2.17.50.0.6-14.el5
compat-libstdc++-296-2.96-138
automake-1.9.6-2.3.el5
automake17-1.7.9-7.el5.2
make-3.81-3.el5
setarch-2.0-1.1
libaio-0.3.106-5
automake15-1.5-16.el5.2
gcc-4.1.2-48.el5
gcc-c++-4.1.2-48.el5
libstdc++-devel-4.1.2-48.el5
MAKEDEV-3.23-1.2
[oracle@oem11gmach01 ~]$ rpm -qa | grep -i compat-db
[oracle@oem11gmach01 ~]$

[root@oem11gmach01 sf_Shared_folder]# rpm -ivh libaio-devel-0.3.106-3.2.i386.rpm
warning: libaio-devel-0.3.106-3.2.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing...                ########################################### [100%]
1:libaio-devel           ########################################### [100%]
[root@oem11gmach01 sf_Shared_folder]# rpm -qa | grep -i libaio-devel
libaio-devel-0.3.106-3.2
[root@oem11gmach01 sf_Shared_folder]# rpm -ivh compat-db-4.2.52-5.1.i386.rpm
warning: compat-db-4.2.52-5.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing...                ########################################### [100%]
1:compat-db              ########################################### [100%]
[root@oem11gmach01 sf_Shared_folder]# rpm -qa | grep -i compat-db
compat-db-4.2.52-5.1
[root@oem11gmach01 sf_Shared_folder]# rpm -ivh sysstat-7.0.0-3.el5.i386.rpm
warning: sysstat-7.0.0-3.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing...                ########################################### [100%]
1:sysstat                ########################################### [100%]
[root@oem11gmach01 sf_Shared_folder]# rpm -ivh unixODBC-2.2.11-7.1.i386.rpm unixODBC-devel-2.2.11-7.1.i386.rpm
warning: unixODBC-2.2.11-7.1.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
Preparing...                ########################################### [100%]
1:unixODBC               ########################################### [ 50%]
2:unixODBC-devel         ########################################### [100%]
[root@oem11gmach01 sf_Shared_folder]#
[/sourcecode]

Create Directory Structure:

Create following directories and make sure you give read / write permission to oracle user.


[sourcecode language="bash"]
/u01/app/OEM11g/Middleware
/u01/app/OEM11g/Middleware/oms11g
/u01/app/OEM11g/Middleware/agent11g
/u01/app/OEM11g/Middleware/Oracle_WT
/u01/app/OEM11g/Middleware/oracle_common
/u01/app/OEM11g/gc_inst
/u01/app/oracle/oradata/OEMDB
[/sourcecode]

3.Install JDK 1.6_18:


Installing JDK depends on the OS bit version you are using. If you are using 32-bit version OS, you will find weblogic server bundled with JDK. But if you are using 64-bit OS,you must install an appropriate jdk to support the WebLogic Server and Grid Control 11.1.0.1.0 installations on 64bit platforms, since the required jdk is not bundles with the installer as it is with the 32bit platforms.
In this demo, i am using a 32-bit OS and i can skip this part of installing JDK. For those we need to install JDK 1.6_18 for 64-bit OS, Please follow the detailed procedure explained with screen shots here. For more details, Please follow the MOS ID : 1063587.1.

NOTE: jdk 1.6.0_18 is recommended due to potential problems with newer versions.

jdk 1.6.0 updates 19 and higher do not allow subsequent patching with required WLS patch WDJ7, so these versions are not effective and must be avoided. They may be used when a cacerts file that allows Smartupdate can be appropriately substituted for the native one.

[sourcecode language="bash"]
[root@oem11gmach01 Grid Control 11g]# mkdir -p /u01/app/OEM11g/Middleware
[root@oem11gmach01 Grid Control 11g]# chown -R oracle:oinstall /u01/app/OEM11g/Middleware/
[root@oem11gmach01 Grid Control 11g]# chmod -R 755 /u01/app/OEM11g/Middleware/
[root@oem11gmach01 Grid Control 11g]# cd /u01/app/OEM11g/Middleware/
[root@oem11gmach01 Middleware]# mkdir jdk
[root@oem11gmach01 Middleware]# chown -R oracle:oinstall jdk
[root@oem11gmach01 Middleware]# chmod 755 jdk
[root@oem11gmach01 Middleware]# cd -
/media/sf_Shared_folder/Grid Control 11g
[root@oem11gmach01 Grid Control 11g]# cp jdk-6u18-linux-i586.bin /u01/app/OEM11g/Middleware/jdk/
[root@oem11gmach01 Grid Control 11g]# chown oracle:oinstall /u01/app/OEM11g/Middleware/jdk/jdk-6u18-linux-i586.bin
[root@oem11gmach01 Grid Control 11g]# chmod 755 /u01/app/OEM11g/Middleware/jdk/jdk-6u18-linux-i586.bin
[root@oem11gmach01 Grid Control 11g]# su - oracle
/u01/app/oracle/product/11.2.0/db_1
OEMDB
[oracle@oem11gmach01 ~]$ cd /u01/app/OEM11g/Middleware/jdk/
[oracle@oem11gmach01 jdk]$

[oracle@oem11gmach01 bin]$ ./jdk-6u18-linux-i586.bin

[oracle@oem11gmach01 jdk]$ pwd
/u01/app/OEM11g/Middleware/jdk
[oracle@oem11gmach01 jdk]$ ls
jdk1.6.0_18  jdk-6u18-linux-i586.bin
[oracle@oem11gmach01 jdk]$ cd jdk1.6.0_18/
[oracle@oem11gmach01 jdk1.6.0_18]$ ls
bin        db    include  lib      man          README_ja.html     register.html     register_zh_CN.html  src.zip
COPYRIGHT  demo  jre      LICENSE  README.html  README_zh_CN.html  register_ja.html  sample               THIRDPARTYLICENSEREADME.txt
[oracle@oem11gmach01 jdk1.6.0_18]$ cd bin
[oracle@oem11gmach01 bin]$ ./java -version
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode, sharing)
[oracle@oem11gmach01 bin]$
[oracle@oem11gmach01 ~]$ java -fullversion
java full version "1.6.0_18-b07"
[oracle@oem11gmach01 ~]$
[/sourcecode]

4.Installing Weblogic Server 10.3.2:


The only version of the WebLogic Server that can be used to deploy Grid Control is 10.3.2.The WebLogic Server associated with Oracle products such as SOA Suite or Identity Management is not appropriate for use in deploying Grid Control.

[youtube http://www.youtube.com/watch?v=B2EJfoC0aS8&hl=en&fs=1]

After completing the installation, we need to apply the recommended patches to WLS for grid control installation. Either use SmartUpdate tool or use offline method to install patch. Download the WLS patch WDJ7 manually and place it in the directory WLS_ORACLE_HOME/utils/bsu/cache_dir.

Offline Method:

[sourcecode language="bash"]

Apply the patch by running the following command:-
./bsu.sh -prod_dir=WLS_ORACLE_HOME/wlserver_10.3 -patchlist=patch number -verbose -install
For example:
./bsu.sh -prod_dir=/scratch/gc/Oracle/Middleware/wlserver_10.3 -patchlist=WDJ7 -verbose -install

You can view the report of applied patched by running the following command:-
./bsu.sh -report -patch_id_mask=patch number
For example: ./bsu.sh -report -patch_id_mask=WDJ7

[/sourcecode]

Using SmartUpdateTool(please watch the demo)

Watch this demo which shows how to apply the recommended patches to weblogic server.

[youtube http://www.youtube.com/watch?v=ejnKK6BpzNs&hl=en&fs=1]

A step-by-step description with graphical representation of the installer progress is available here.

5.Install Database 11.2.0.1:


The option to "Install Grid Control with a new database" is no longer offered. So we need to have  the database created before starting the grid control 11g installation.

Please follow the article "Installing 11gR2 Single Instance Database With Non-ASM Storage" for installling 11g database software and creating a database for OEM grid control repository.

[youtube http://www.youtube.com/watch?v=ePitGvp_zDs&hl=en&fs=1]

This procedure with step-by-step screen shot graphics can be found here.  ( This guide installs 11.1.0.7 Database, but we are installing 11gR2 in our demo ).

6.Prepare the database for OEM 11g Installation.


[sourcecode language="sql"]
SQL> select active_state from v$instance;

ACTIVE_ST
---------
NORMAL

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

COUNT(*)
----------
1

SQL> SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS');

COUNT(*)
----------
1

SQL> !

=>Deconfigure DB console :

[oracle@oem11gmach01 database]$ $ORACLE_HOME/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD welcome1 -SYSMAN_PWD welcome1

STARTED EMCA at Apr 27, 2011 10:38:10 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle.  All rights reserved.

Enter the following information:
Database SID: OEMDB
Listener port number: 1521

Do you wish to continue? [yes(Y)/no(N)]: Y
Apr 27, 2011 10:38:48 PM oracle.sysman.emcp.EMConfig perform
INFO: This operation is being logged at /u01/app/oracle/cfgtoollogs/emca/OEMDB/emca_2011_04_27_22_38_10.log.
Apr 27, 2011 10:38:49 PM oracle.sysman.emcp.util.DBControlUtil stopOMS
INFO: Stopping Database Control (this may take a while) ...
Apr 27, 2011 10:39:23 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Dropping the EM repository (this may take a while) ...
Apr 27, 2011 10:43:19 PM oracle.sysman.emcp.EMReposConfig invoke
INFO: Repository successfully dropped
Enterprise Manager configuration completed successfully
FINISHED EMCA at Apr 27, 2011 10:43:34 PM
[oracle@oem11gmach01 database]$ exit
exit

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

COUNT(*)
----------
0

SQL> SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS');

COUNT(*)
----------
0

SQL> select value from v$option where parameter='Fine-grained access control';

VALUE
----------------------------------------------------------------
TRUE

SQL>
SQL> select sum(decode(autoextensible,'YES',200*1024*1024+1,bytes)) total from dba_data_files f, dba_tablespaces s
2  where s.contents='UNDO' and s.tablespace_name=f.tablespace_name;

TOTAL
----------
209715201

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

COUNT(*)
----------
0

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

COUNT(*)
----------
0

SQL> select log_mode from v$database;

LOG_MODE
------------
NOARCHIVELOG

SQL>
[/sourcecode]

Optional : Verify the init.ora parameters as specified in the installation document

7.Install OEM grid control 11.1.0.1.0:


There are three ways to install Enterprise Manager.
1) Installing Enterprise Manager System with graphical mode including all configuration tools
2) Installing Enterprise Manager Software Only in Graphical Mode and Configuring Later
3) Installing Enterprise Manager Software Only in Silent Mode and Configuring Later

In the present demo i am choosing option 2 to install Enterprise Manager.

Go to the directory where the software is unzipped and start the installation with the following command ...

[sourcecode language="bash"]
<Software_Location>/runInstaller -noconfig
[/sourcecode]

After successful installation of the OEM grid control 11g software, install the configuration tools using

[sourcecode language="bash"]
$<OMS_ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl
Ex : /u01/app/OEM11g/Middleware/oms11g/perl/bin/perl /u01/app/OEM11g/Middleware/oms11g/sysman/install/ConfigureGC.pl
[/sourcecode]

Watch the video to install OEM grid control 11g software.

[youtube http://www.youtube.com/watch?v=VmhzWjgsprg&hl=en&fs=1]

For detailed explanation, verify MOS ID 1064495.1 and for step by step screen shot explanation of the installation, refer the the document here.

8.Status Check:


[sourcecode language="bash" highlight="015,023,054,063,091,101,102"]
[oracle@oem11gmach01 ~]$ echo $ORACLE_HOME
/u01/app/oracle/product/11.2.0/db_1
[oracle@oem11gmach01 ~]$ echo $ORACLE_SID
OEMDB
[oracle@oem11gmach01 ~]$ sqlplus '/as sysdba'

SQL*Plus: Release 11.2.0.1.0 Production on Sat Apr 30 02:27:52 2011

Copyright (c) 1982, 2009, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> select instance_name,status from v$instance;

INSTANCE_NAME    STATUS
---------------- ------------
OEMDB            OPEN

SQL>


[oracle@oem11gmach01 ~]$ lsnrctl status listener

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 30-APR-2011 02:28:14

Copyright (c) 1991, 2009, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     listener
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                29-APR-2011 23:55:06
Uptime                    0 days 2 hr. 33 min. 9 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/oem11gmach01/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oem11gmach01.localdomain)(PORT=1521)))
Services Summary...
Service "OEMDB.localdomain" has 1 instance(s).
Instance "OEMDB", status READY, has 1 handler(s) for this service...
Service "OEMDBXDB.localdomain" has 1 instance(s).
Instance "OEMDB", status READY, has 1 handler(s) for this service...
The command completed successfully
[oracle@oem11gmach01 ~]$



[oracle@oem11gmach01 bin]$ pwd
/u01/app/OEM11g/Middleware/oms11g/bin
[oracle@oem11gmach01 bin]$ ./emctl status oms
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
WebTier is Up
Oracle Management Server is Up
[oracle@oem11gmach01 bin]$



[oracle@oem11gmach01 bin]$ pwd
/u01/app/OEM11g/Middleware/agent11g/bin
[oracle@oem11gmach01 bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
Agent Version     : 11.1.0.1.0
OMS Version       : 11.1.0.1.0
Protocol Version  : 11.1.0.0.0
Agent Home        : /u01/app/OEM11g/Middleware/agent11g
Agent binaries    : /u01/app/OEM11g/Middleware/agent11g
Agent Process ID  : 10432
Parent Process ID : 10400
Agent URL         : https://oem11gmach01.localdomain:3872/emd/main/
Repository URL    : https://oem11gmach01.localdomain:4900/em/upload
Started at        : 2011-04-30 02:04:10
Started by user   : oracle
Last Reload       : 2011-04-30 02:05:44
Last successful upload                       : 2011-04-30 02:25:26
Total Megabytes of XML files uploaded so far :    21.91
Number of XML files pending upload           :        0
Size of XML files pending upload(MB)         :     0.00
Available disk space on upload filesystem    :    25.10%
Last successful heartbeat to OMS             : 2011-04-30 02:24:52
---------------------------------------------------------------
Agent is Running and Ready
[oracle@oem11gmach01 bin]$



[oracle@oem11gmach01 bin]$ pwd
/u01/app/OEM11g/gc_inst/WebTierIH1/bin
[oracle@oem11gmach01 bin]$ ./opmnctl status

Processes in Instance: instance1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
ohs1                             | OHS                |    7870 | Alive

[oracle@oem11gmach01 bin]$


Access the URL:

https://oem11gmach01.localdomain:4900/em/
[/sourcecode]

9.Issues and Resolutions


During Enterprise Manager installation, the configuration tool "Repository Configuration Assistant" failed.

Reviewed the following logfiles:
$<OMS_ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log
$<OMS_ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

Following information found in various logfiles under the directories mentioned above:

[sourcecode language="bash"]
[Initializing the EM RCU Runner, Failed Parameter Validation]
action logger path calculated finally: /u01/app/OEM11g/Middleware/oms11g/sysman/log/schemamanager/m_042911_1243_AM/m_042911_1243_AM.TRANSX/

==================================================

2011-04-29 00:56:36,991 [vd92mfm9eocy] INFO  emschema.vd92mfm9eocy - not found repos connection
2011-04-29 00:56:36,992 [vd92mfm9eocy] INFO  emschema.vd92mfm9eocy - error: not found repos connection for transx repos user exists: false mgmt_messages exists: false; found connection for repos user: false
2011-04-29 00:56:36,992 [vd92mfm9eocy] ERROR emschema.vd92mfm9eocy - Failed Parameter Validation
2011-04-29 00:56:36,992 [vd92mfm9eocy] ERROR emschema.vd92mfm9eocy - NULL Exception was thrown!
2011-04-29 00:56:36,992 [vd92mfm9eocy] ERROR emschema.vd92mfm9eocy - Failed Parameter Validation
"/u01/app/OEM11g/Middleware/oms11g/sysman/log/schemamanager/m_042911_1243_AM/m_042911_1243_AM.TRANSX/emschema.log.TRANSX" 407L, 44064C     407,1         Bot

========================

INFO: oracle.sysman.top.oms:[Initializing the EM RCU Runner, Failed Parameter Validation]
INFO: oracle.sysman.top.oms: action logger path calculated finally: /u01/app/OEM11g/Middleware/oms11g/sysman/log/schemamanager/m_042911_0115_AM/m_042911_0115_AM.TRANSX/
INFO: oracle.sysman.top.oms:The transx command execution is completed with the status 0
INFO: oracle.sysman.top.oms:process_id:
INFO: oracle.sysman.top.oms:The Process ID: [] does not exist.  Either it has been completed, or this is not the executing JVM
INFO: oracle.sysman.top.oms:The plug-in Repository Configuration has failed its perform method

====================

2011-04-29 01:29:44,272 [xkdp7xnv3zx2] INFO  emschema.xkdp7xnv3zx2 - not found repos connection
2011-04-29 01:29:44,272 [xkdp7xnv3zx2] INFO  emschema.xkdp7xnv3zx2 - error: not found repos connection for transx repos user exists: false mgmt_messages exists: false; found connection for repos user: false
2011-04-29 01:29:44,273 [xkdp7xnv3zx2] ERROR emschema.xkdp7xnv3zx2 - Failed Parameter Validation
2011-04-29 01:29:44,273 [xkdp7xnv3zx2] ERROR emschema.xkdp7xnv3zx2 - NULL Exception was thrown!
2011-04-29 01:29:44,273 [xkdp7xnv3zx2] ERROR emschema.xkdp7xnv3zx2 - Failed Parameter Validation

===========================

INFO: oracle.sysman.top.oms:The command run for transx is /u01/app/OEM11g/Middleware/oms11g/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=oem11gmach01.localdomain)(PORT=1521)))(CONNECT_DATA=(SID=OEMDB))) -action transx  -repos_user SYSMAN -dbUser SYS -mwHome /u01/app/OEM11g/Middleware -mwOraHome /u01/app/OEM11g/Middleware/oms11g
INFO: oracle.sysman.top.oms:processing arguments
INFO: oracle.sysman.top.oms:compiling arguments for validation
INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
INFO: oracle.sysman.top.oms: Enter SYSMAN repository password :
INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
INFO: oracle.sysman.top.oms:stty: standard input: Invalid argument
INFO: oracle.sysman.top.oms:Verify :
INFO: oracle.sysman.top.oms:Enter password for: SYSMAN
INFO: oracle.sysman.top.oms:^H ^Hdone checking required user credentials...
INFO: oracle.sysman.top.oms:done creating arguments...
[/sourcecode]

Solution:

[sourcecode language="bash"]
Clean up the Management Repository by running the following command
/u01/app/OEM11g/Middleware/oms11g/sysman/admin/emdrep/bin/RepManager oem11gmach01.localdomain 1521 OEMDB -action dropall -dbUser SYS -dbPassword xxxxxxx -dbRole sysdba -mwHome /u01/app/OEM11g/Middleware -mwOraHome /u01/app/OEM11g/Middleware/oms11g -oracleHome /u01/app/OEM11g/Middleware/oms11g  -continueOnError

Then re-run the configuration tool script.
/u01/app/OEM11g/Middleware/oms11g/perl/bin/perl /u01/app/OEM11g/Middleware/oms11g/sysman/install/ConfigureGC.pl
[/sourcecode]

If there are any failed configuration tools, please refer the document here.

Reference MOS IDs :  1067438.1 , 1106105.1 , 1063587.1 , 1063112.1 , 1064441.1 , 1064495.1 , Install Guide

Thanks
SRI
Share this article :

Related Articles By Category



+ comments + 16 comments

Mohan
July 18, 2011 at 4:09 PM

Hello srikrish Murty, good job. It is helpfull, how to install grid control 11g and where to begin and how to start. Complete doc at one location.
Thanks --Mohan

August 7, 2011 at 5:40 AM

thats really nice apperciate your efforts

deepak
August 18, 2011 at 4:01 PM

good job dude!

learnwithme11g
August 27, 2011 at 6:08 PM

Hey Deepak, Thanks Man. How r u?

lalitha
November 19, 2011 at 4:12 PM

Hi Krishna Murthy,

Greatful for your effort ,is more usefull for newbies of GRID. explanation and method used is excellent. ThanQ. Appreciate your effort.

learnwithme11g
December 6, 2011 at 5:57 AM

Thank you :-)

reddy
December 6, 2011 at 11:17 PM

Hi Krishna Murthy, Good Work!!. I have not used yet , but looks like an awesome effort in putting all the steps together for base install of 11G GC.

learnwithme11g
December 7, 2011 at 4:06 AM

Thank you :-)

sree harsha
February 8, 2012 at 12:55 PM

Hi Krishna,

Nice to see another good post from you.

I've a question for you. I am about to install OEM11g along with AMP/ACMP. And the requirement is for end users to access the console with limited access.

I've a registered HTTPS URL which can be used for this purpose. Now at which point during the install/config do I configure this URL?

Can I change the URL once I install OEM with the default hostname value to the registered HTTPS URL?

Regards
Sree Harsha

sree harsha
February 8, 2012 at 1:01 PM

I mean to ask,

I would like to change the EM console URL from
https://hostname:port/em/console
to
https://https.registered.url:port/em/console

is it simply acheived by installing the OEM by having the URL as the first alias for the server IP in the "/etc/hosts" file?

Hope I am clear.

Regards
Sree harsha

learnwithme11g
February 14, 2012 at 9:24 AM

Hi Harsha,
You can change the access URL at any point after installation. It is not mandatory that we need to stick to the initial URL with which we installed grid.

Thanks
SRI

sree harsha
February 14, 2012 at 9:52 AM

Hi Sri,

Thanks for your reply. Do you have any idea how to change the URL after install?

Regards
Harsha

learnwithme11g
February 16, 2012 at 5:36 PM

Hi SreeHarsha, if i understood your question correctly on restricting the access and changing access URL, let me give you these steps ...

I) When the OMS is installed, the URL will be
https://hostname.domainname:/em
We can also use
http://hostname.domainname:/em
But to restrict the http access, we can issue the following command:
/bin>./emctl secure lock -console
This will allow only HTTPS console access

II) If you want to change the hostname in the URL, then only way is
1. have a virtual IP associated with virtual hostname
2. Secure the OMS as follows:
./emctl secure oms -sysman_pwd -reg_pwd -host
-secure_port
Note: if you do this, all the agents also must be secured with the OMS virtual hostname.
This will allow to access the console with the virtualhostname instead of physical hostname of the OMS.


III) If we want to restrict the access based on the IP address or if you want to allow the users only from a certain domain, we can do it by editing the configuration file httpd_em.conf

Thanks
SRI

Sue Meyer
July 26, 2012 at 5:14 PM

Hi, Great info on installing OEM 11g for Linux, but is there a similar article out their just like this, but for installing on Windows 32b?

learnwithme11g
August 15, 2012 at 7:02 AM

Hi Sue Meyer, Unfortunately i dont have any article for 11g, but have for 10g. You can refer MOS IDs 1067438.1 and 1091325.1 for oem 11g grid control installation on windows.
Thanks
SRI

Srikrishna Murthy Annam
December 5, 2012 at 8:14 AM

Hi Lokesh,
You have the option that you can manually drop the repository incase if we are not able to figure out the exact issue. Use following commands,
1) drop user sysman cascade;
2) drop user sysman_mds cascade;
3) drop user mgmt_view cascade;
4) drop role mgmt_user;
5) Use the following query to spool and drop all objects.
select 'drop ' || owner || ' synonym ' || synonym_name || '; from dba_synonyms where table_owner in ('SYSMAN','SYSMAN_MDS','MGMT_VIEW');

Then re-run the installation. You should be fine now.

Thanks
SRI

Post a Comment

Thank you for visiting our site and leaving your valuable comment.

 
Support :
Copyright © 2013. askMLabs - All Rights Reserved
Proudly powered by Blogger