Enterprise Manager Generic (MOSC)

MOSC Banner

"emca -deconfig dbcontrol db -repos drop" does not remove the SYSMAN account, problems ensue

edited Feb 7, 2013 12:03AM in Enterprise Manager Generic (MOSC) 2 commentsAnswered
11.2.0.1 running on Windows Server 2008R2.

Question:  What do you do when "emca -deconfig..." doesn't drop the SYSMAN user (and other user objects)?  What is there to do after you attempt "SQL> drop user sysman cascade;"?

Current status:  Database won't open (I recovered it many times before it stopped being cooperative).  Error when I attempt "emca -config..." is "ORA-00955: name is already in use by an existing object".

Most of the aggravation came from hardening the database, but OEM was working great until the SYSMAN account became LOCKED (not sure how that happened).

Mike

Detail:

The first indication of a problem was not being able to get to OEM, even though "emctl status dbconsole" showed it was running.

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