Database Administration (MOSC)

MOSC Banner

What would cause an account status to change to "LOCKED(TIMED)" as opposed to "LOCKED"?

edited Jan 8, 2013 5:26PM in Database Administration (MOSC) 11 commentsAnswered ✓
Oracle 11.2.0.1, with terminal patch, running on Windows 2008R2.

I have a situation where the SYSMAN user account status was being changed (within seconds of unlocking it) to "LOCKED(TIMED)" by the Oracle Enterprise Manager process.  When I turned Database Control off, the SYSMAN account remained open.  What could cause that?

Other notes:  The system was running fine a couple of weeks ago, with Oracle recommended backups set up via OEM.  We ran out of space in the db_recovery_file_dest, and I resolved that by increasing the size, and was able to do a full backup of the database at that time.  However, the SYSMAN account status issue remained. 

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