Empty emoms.properties - The Solution
When Oracle Management Service (OMS) filesystem is 100% full, you may loose <oms_home>/sysman/config/emoms.properties
Actually the file will remain empty with size of zero bytes.
A small file that can cause Grid Control not to function.
emctl start oms
.
.
.
.
Could not find Console Server Port in /software/oracle/OEM10gR2/oms10g/sysman/config/emoms.properties
Could not find Console Server Port in /software/oracle/OEM10gR2
Oracle claims that you have to install a new OMS instead of the old one. (Notes: 418453.1, 418159.1)
After some struggles looking for the undocumented syntax of the file,
I managed to make OMS working again ;))
The lesson
1. Always BACKUP
2. Monitor the filesystem of OMS itself
3. Create some jobs for deleting old logs and unneeded archives.
4. Don't belive everything is written on Metalink.
Anyway, here is my file
Enjoy :)
emoms.properties
#Sun Apr 15 19:12:18 IDT 2007
oracle.sysman.emSDK.svlt
oracle.sysman.eml.mntr.emdRepPw
emdrep.ping.pingCommand=/bin
oracle.sysman.eml.mntr.emdRepPo
oracle.sysman.eml.mntr.emdRepDB
oracle.sysman.eml.mntr.emdRepPw
oracle.sysman.emRep.dbConn
(ADDRESS\=(PROTOCOL\=TCP)(HOST
oracle.sysman.db.isqlplusUrl
oracle.sysman.emSDK.svlt
oracle.sysman.eml.mntr.emdRepRA
oracle.sysman.emSDK.emd.rt
oracle.sysman.eml.mntr.emdRepPw
oracle.sysman.db.isqlplusWebDBA
oracle.sysman.emSDK.svlt
oracle.sysman.emSDK.svlt
oracle.sysman.eml.mntr.emdRepSI
oracle.sysman.eml.mntr.emdRepSe
oracle.sysman.emSDK.sec
oracle.sysman.eml.mntr.emdRepCo
oracle.sysman.emkeyfile=
oracle.sysman.eml.mntr.emdRepUs
oracle.sysman.db.adm.conn
oracle.sysman.db.perf.conn
Very helpfull, thank you very much - you saved me :-)
ReplyDelete