Skip to content Skip to sidebar Skip to footer

Database Instance Is Unavailable Fix the Ora Error Thrown and Run Em Configuration Assistant Again

Hello all.

I take managed to solve this upshot. For anyone else that may see this, I hope this helps.

Symptom: Trying to log into EM Console for Oracle was throwing a "503 Service Unavailable"

Reason: Checking into the contents of "emoms.properties" binder, information technology was discovered there were no entries. File was empty, so of course in that location was no reference's and or backdrop for the DBConsole.

Why this Critical file was trashed or stomped on is anyones guess. Bottom line, it is required or yous volition have no EMGC.

I tried numerous time's to "driblet and recreate" the repository. This failed each and every time, and my posts above are in reference to trying to go this running by doing the -repos drop/recreate action.

Knowing that everything else was in good shape except EMGC, I kept at this, a little more searching for clues, and here is what I managed to do to go this running again.

The binder where the emoms.backdrop file is located, fortunately had a "backup" copy of the file. If not, you can download a template and fill in the respective fields for your DB.

So....a few things take to happen, but thankfully users can keep to utilise Oracle while you lot practice this. The Only service we are concerned with is for the DBConsole. Also annotation that Windows does NOT always know whats going on with services. This was proved, by me using emctl to terminate DBConsole, and still in Windows services, it thinks its yet running even after a refresh.

Ok..so lets fix this. lets offset ostend a couple of things.

ane) HDD infinite yeah?

2) Hosts file, ensure y'all have entries for IP/Host. Not just the default loopback

3) is your emoms.properties file empty like mine?

iv) ensure DBAgent is OK  cmd>emctl status amanuensis. Make sure its running, and check the "Space" bachelor. If space is low, this will neglect.

Now the Prepare

five) close downwards dbconsole. cmd>emctl stop dbconsole

half-dozen) locate the emoms.properties file and rename it e.grand.: emoms.properties.EMPTY

seven) If you have a backup copy, make another copy and rename it as emoms.backdrop. Or your going to need the template to recreate it.

eight) edit the file.....locate the line: oracle.sysman.eml.mntr.emRepPwd=e9m74cdr8..bla bla bla. This is your SYSMAN password, which has been encrypted. Edit this and enter the P/W in plain text.

nine) detect the next line for P/westward encryption:oracle.sysman.eml.mntr.emRepPwdEncrypted=TRUE, and change True to FALSE. Save the changes.

ten) Beginning dbconsole: cmd>emctl start dbconsole

eleven) look for this to complete, now go back and wait at the emoms.backdrop file and bank check to come across if your P/W has been encrypted and the word FALSE is now Truthful. If not, go into Windows services.msc and restart DBConsole Service.

12) check encryption once again, if expert nosotros tin proceed. If not, you MAY need to reboot, or effort starting the service once more until it does.

13) we need to "unsecure" the dbconsole so we can upload the required files to the repository. cmd> emctl unsecure dbconsole    this take a couple min to complete

14) cmd> emctl upload    this should consummate and report successful

15) cmd> emctl secure dbconsole    this will re-secure the console and arrive available.

16) go check your :1158/em accost.

Wahoooo, I promise this works for someone other than me.

If your EM does non load correct abroad, give it a few min. What I as well had to do was delete cookies, and add together the EM's spider web address entered as a Trusted Site under Local Intranet. and so the login page came upward.

This will make my weekend much better at present this is working once again.

Cheers

Howard

Was this post helpful? thumb_up thumb_down

johnsonthemandiones.blogspot.com

Source: https://community.spiceworks.com/topic/451746-recreating-em-control

Post a Comment for "Database Instance Is Unavailable Fix the Ora Error Thrown and Run Em Configuration Assistant Again"