Tag Archives: Enterprise Manager

Eerste indruk Oracle Enterprise Manager Grid Control 11G

Posted on by
Reply

Bij de eerste installatie stappen rijzen er gelijk een aantal vragen.

  • Vreemd dat er in de te downloaden installatie set geen middleware en database wordt meegeleverd, terwijl de installatie set weer gegroeid is ten opzichte van 10.2.0.5.0, die 10.2.0.3.0 minstens als basis nog had.
  • Nu is de applicatie Enterprise Manager Grid Control vrij te gebruiken, als je de management packs maar niet inschakeld, maar hoe zit dit dan met de weblogic server en de enterprise database die je nodig hebt.

Hieronder staan wat screenshots van de installatie procedure van EM 11g. Voordat je dit kan uit voeren heb je een Weblogic Server nodig, dit kan een kale installatie zijn zonder domein en je hebt een database nodig met partitioning. In mijn geval heb ik de database en de weblogic server op dezelfde machine geïnstalleerd op 64 bits Oracle Enterprise Linux 5.5. Deze machine heeft in totaal 4 GB geheugen waarvan er 512 MB is toegekend aan de database.

Nadat de database gecreëerd is moet je er nog even voor zorgen dat het aantal ‘processes’, ‘session_cached_cursors’ en ‘log_buffers’ goed staan. Verder moet er minimaal 200 MB aan undotablespace beschikbaar zijn.

SQL> alter system set processes=500 scope=spfile;

System altered.

SQL> alter system set session_cached_cursors=200 scope=spfile;

System altered.

SQL> alter system set log_buffer=10485760 scope=spfile;

System altered.

SQL> alter database datafile 'UNDO_DATAFILE' resize 200M;

Database altered

SQL> shutdown immediate
SQL> startup

Installatie:

Eerste indruk:

Op het eerste gezicht lijkt er niet veel aangepast, anders dan dat er onder de motorkap veel gewijzigd is. De applicatie reageert snel, verder zijn er wel wat iconen anders opgemaakt, maar alle functies zijn nog terug te vinden onder de wel bekende locaties.

Waar je vooral ziet dat dit de nieuwe Enterprise manager is, is in de management console voor de Weblogic applicatie server. De interface zoals je die gewend bent in de Admin Server van Weblogic is in EM overgenomen. Dit werkt zeer prettig.

503 Service Unavailable when opening OEM

Posted on by
Reply

Today I had to solve a problem with one of our clients Oracle Enterprise Manager Grid Control. When they went to the console, they got the following error:

503 Service Unavailable
Servlet error: Service is not initialized correctly. Verify that the repository connection information provided is correct.

When I looked in the emoms.log in $ORACLE_HOME/sysman/log I found an error mentioning that the user credentials where incorrect. When I checked the status of the database, listener and opmn, everything was up and running. After some searching a found that the file emoms.properties was empty. I found 2 Metalink notes (418159.1 and 733401.1) concerning this issue and it appears to be a bug in OEM 10.2.0.4.0.

I did the following to solf this:
I created a new emoms.properties in $ORACLE_HOME/sysman/config with the following

oracle.sysman.emSDK.svlt.ConsoleServerName=:_Management_Service
emdrep.ping.pingCommand=</bin/ping -c 3 -w 30
em_oob_shutdown=false
LargeRepository=false
oracle.sysman.eml.mntr.emdRepPort=1521
em_email_address=_NOT_AVAILABLE_
em_oob_crash=false
em.oms.dumpModules=omsThread,repos
oracle.sysman.emRep.dbConn.statementCacheSize=50
oracle.sysman.db.isqlplusUrl=%ISQLPLUS_PROTOCOL%://%ISQLPLUS_HOST%:%ISQLPLUS_PORT%/isqlplus/dynamic
em_oob_startup=false
oracle.sysman.emSDK.svlt.ConsoleServerPort=4889
em_from_email_address=_NOT_AVAILABLE_
em_from_email_name=_NOT_AVAILABLE_
oracle.sysman.emSDK.svlt.ConsoleServerHost=
oracle.sysman.db.isqlplusWebDBAUrl=%ISQLPLUS_PROTOCOL%://%ISQLPLUS_HOST%:%ISQLPLUS_PORT%/isqlplus/dba/dynamic
oracle.sysman.emSDK.svlt.ConsoleServerHTTPSPort=1159
em_email_gateway=_NOT_AVAILABLE_
oracle.sysman.eml.mntr.emdRepSID=
oracle.sysman.eml.mntr.emdRepServer=
oracle.sysman.eml.mntr.emdRepConnectDescriptor=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=)))
oracle.sysman.emkeyfile=/sysman/config/emkey.ora
em.ip.ui.enable=true
oracle.sysman.emSDK.svlt.PublicServletEnabled=true
oracle.sysman.eml.mntr.emdRepPwd=
oracle.sysman.eml.mntr.emdRepUser=sysman
oracle.sysman.eml.mntr.emdRepPwdEncrypted=FALSE
oracle.sysman.eml.mntr.emdRepPwdSeed=4100593566537048326

Normally the password is encrypted, but by setting emdRepPwdEncrypted to FALSE you can put in your password as cleartext. After restarting opmn the password will by encrypted and emdRepPwdEncrypted set to TRUE. You can use this to change the password od sysman as well. Just change the password in the existing emoms.properties and set emdRepPwdEncrypted to FALSE and restart opmn.

So in sort:
- Change / create emoms.properties
- opmnctl shutdown
- opmnctl startall
And everything should be working again.

Install Enterprise Manager on OEL5.3 x86_64

Posted on by
Reply

Today I had to install Oracle Enterprise Manager Grid Control 10.2.5.0 on an Oracle Enterprise Linux 5.3 64 bit machine, which I installed also. I installed a base install of linux, I hate to have X installed on a server where it’s not used. Basically I ran a default install, but deselected Gnome, X Server and all those other X tools like Firefox.

After I have done that I had to install some extra packages beside the standard packages Oracle needs. Below the commands that I used so I got start the OEM installation.

First add the public yum of Oracle to your repository

Install needed packages

yum install libXp.x86_64 compat-db.x86_64 control-center.x86_64 gcc.x86_64 gcc-c++.x86_64 libstdc++-devel.i386 libstdc++-devel.x86_64 openmotif.x86_64 openmotif.i386 sysstat.x86_64 glibc-devel.i386 gdbm.i386

Gdbm, glibc and libXp are extra packages, otherwise you get errors that the HTTP_Server couldn’t start, or the setup is unable to continue.

Create link libdb

ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
chmod 755 /usr/lib/libgdbm.so.2.0.0
chmod 755 /usr/lib/libdb.so.2

Add oracle user

groupadd oinstall
groupadd dba
useradd -m -g oinstall -G dba oracle

change /etc/sysctl.conf

cat >> /etc/sysctl.conf <<eof
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=262144
EOF
/sbin/sysctl -p

Change /etc/security/limits.conf

cat >> /etc/security/limits.conf <<eof
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 1024
oracle hard nofile 65536
EOF

Change /etc/pam.d/login

cat >> /etc/pam.d/login <<eof
session required /lib/security/pam_limits.so
EOF

Change /etc/profile

cat >> /etc/profile <<eof
if [ $USER = "oracle" ]; then
if [ $SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
umask 022
fi
EOF

Change /etc/csh.login

cat >> /etc/csh.login <<eof
if ( $USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
umask 022
endif
EOF