Re: "503 Service Unavailable" while connecting to Grid Control

OK, the story continues...
I am installing OMS in the different OMS home and it fails saying me lovely:
"OMS version 10.2.0.1 does not match with repository version 10.2.0.4.0" ...
Nice... Looks like I have to create 10201 DB too.. Kinda embarrassing..

May be there is a kind soul out there that would not mind to share his/her
emoms.properties with one stupid DBA like me? Pleeeease? I searched the net
for it but couldn't find the whole, from brace to brace file..

Or, hold on.. The Note says this bug fixed in 10205.. Will that help, if I
roll forward the broken-down OMS to 10205? What do you think?

Thanks for help, people.

On Tue, Dec 9, 2008 at 2:40 PM, Maria Gurenich <gurenich@xxxxxxxxx> wrote:

> Hi Alan,
>
>
> Thank you so much!!
> That is exactly my case, my emoms.properties is empty (0 bytes) and I have
> no backups... :(
>
> -rw-------  1 oracle oinstall    0 Dec  5 14:00 emoms.properties
>
> Thank you again!
> I am recreating the OMS and will let everybody know if it made the trick!
>
> Thanks again,
> M.
>
>
>
> On Tue, Dec 9, 2008 at 1:18 PM, Alan J. Gagne <alanjgagne@xxxxxxxxx>wrote:
>
>> Maria Gurenich wrote:
>>
>>> Hi all,
>>>
>>> I am having problems with getting Oracle Enterprise Grid Control up and
>>> running.
>>> It was working fine since October till December 5th. On Friday, one of
>>> the mount points ran out of space because of rapidly growing trace files in
>>> the OH. I didn't notice it on Friday and just left it over the week-end.
>>> Yesterday when I navigated to the OEM link i got the following:
>>>
>>>
>>>  *503 Service Unavailable*
>>>
>>> *Service is not initialized correctly. Verify that the repository
>>> connection information provided is correct.*
>>>
>>>
>>> I went to the server, cleaned the trace files (they actually contained
>>> nothing interesting or related to the existing problem) and tried the link -
>>> didn't work.
>>> I bounced the DB - no results.
>>> I checked the OMS_HOME/sysman/log/emoms.log & emoms.trc files - they both
>>> contain the following errors:
>>>
>>> <.........>
>>> 2008-12-09 12:15:16,676 [AJPRequestHandler-ApplicationServerThread-11]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:22,011 [AJPRequestHandler-ApplicationServerThread-6]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:24,885 [AJPRequestHandler-ApplicationServerThread-5]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:31,174 [AJPRequestHandler-ApplicationServerThread-11]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:35,735 [AJPRequestHandler-ApplicationServerThread-7]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:37,530 [AJPRequestHandler-ApplicationServerThread-8]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:38,935 [AJPRequestHandler-ApplicationServerThread-12]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:41,887 [AJPRequestHandler-ApplicationServerThread-7]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:44,098 [AJPRequestHandler-ApplicationServerThread-8]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>> 2008-12-09 12:15:45,309 [AJPRequestHandler-ApplicationServerThread-11]
>>> ERROR conn.ConnectionService verifyRepositoryEx.878 - Invalid Connection
>>> Pool. ERROR = User credentials doesn't match the existing ones
>>>
>>> I checked the SYSMAN credentials - it works.
>>> I checked listener - everything is OK.
>>> I bounced the server - no results.
>>> I went to Google and MetaLink - just one artikle in both places (posted
>>> by the same person, I believe) with the same error, but no answers for his
>>> question..
>>> Have anybody seen this trouble? How did you guys handle it? I don't wanna
>>> rebuild the whole thing, I believe there should be more elegant way to fix
>>> it.
>>>
>>> I would aprecciate your help and thoughts.
>>> Thank you in advance,
>>> M.
>>>
>> Check out this Metalink note:
>>
>> Subject:     Problem: Getting 503 Service Unavailable due to
>> emoms.properties being empty
>> Doc ID:     Note:418159.1
>>
>>
>>
>

Other related posts: