Enterprise Manager Generic (MOSC)

MOSC Banner

Fixing a partial de-installation of OEM

edited Sep 8, 2018 4:38AM in Enterprise Manager Generic (MOSC) 2 commentsAnswered ✓
If you've hardened your Oracle 11gR2 database and attempt to drop OEM using EMCA, you can wind up with a partial deinstallation which leaves the SYSMAN account with no Database Control directory under ORACLE_HOME.  I have found no easy way to fix this!

Symptoms:  (1) "emca -deconfig dbcontrol db -repos drop" fails.  The <host>_<oracle_sid> directory is removed (and perhaps the oc4j/j2ee file as well), but the SYSMAN account remains.  If you attempt to create the repository at this point, it fails with the error "SYSMAN already exists". (2) if you attempt to fix this by issuing "SQL> drop user sysman cascade;" and attempt to create the repository, you get the error "MGMT_USER" conflicts (this is a ROLE which wasn't dropped); (3) if you drop the "MGMT_USER" role and attempt to create the repository, you get "Object already exists" in the emca log (nothing

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center