| OMS Start error [message #52135] |
Thu, 04 July 2002 03:23  |
Alan
Messages: 68
Registered: October 1999
|
Member |
|
|
I've received this error with using"oemctrl start oms" on my Redhat7.2:
"Could not connect to the OMS:possible error in the configuration file"
I did create a repository using "emca", startup the listener successfully.
**However, I received a warning message when using dbsnmp_start in lsnrctl. When i check the log in nmiconfig.log, and return with 3 warnings
Using oratab file /etc/oratab
Warning: LISTERNER defined in /u01/...listener.ora will be skipped, because it does not monitor any of the valid SIDs {myoracle myoracle.mylinux}
Warning: No Listener found for SID myoracle myoracle will be skipped.
Warning: No Listener found for SID myoracle.mylinux. myoracle.mylinux will be skipped.
---Configuration initsid.ora---
db_name = "myoracle"
db_domain = mylinux
instance_name = myoracle
service_names = myoracle.mylinux
Pls advise. Thank you.
|
|
|
|
| Re: OMS Start error [message #52141 is a reply to message #52135] |
Thu, 04 July 2002 11:50  |
 |
Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille
|
Senior Member
Account Moderator |
|
|
1- Check that the repository database was started.
2- Using the oms credentials, check whether you can login to that
repository instance using a tool like sqlplus
3- make sure that the oms hostname is resolved correctly
Edit the OMSCONFIG.PROPERTIES file located in $ORACLE_HOME/sysman/config
directory.
1. At the OMS system, type: hostname
This is the TCP/IP Hostname of the system.
2. Edit the parameter Oem.BootHost=localhost
Change the parameter to read: Oem.BootHost=<hostname returned in step 1>
3. Save file
4. Restart the Managment Server
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
