I am using OEM DBConsole (database version 11.2) and it keeps logging me out after so many minutes of inactivity unless I happen to be in one of the performance monitoring screen that automatically refreshes every xx seconds.
I've had the same issue with OEM Grid Control.
Is there a setting someplace to turn this off so it doesn't continue to log me out?

Yes. See MOS note 1170373.1 for DBControl and note 234875.1 for Grid Control. It's also in the Grid Control documentation at http://docs.oracle.com/cd/E11857_01/install.111/e16847/addnl_tasks.htm#i1025313 .

Well, crud... I tried what the paper suggested, but it did not work. Also, it said to edit the $OH/sysman/config/emoms.properties file, but we don't have that on any of our servers using DBConsole. Instead, we have emoms.properties.emca, and an emd.properties.

I edited the emoms.properties.emca file and added the lines below, but it did not fix the logging out. I just tested it again and it logged out in less than one hour.

For DBConsole the file should be in $ORACLE_HOME/[hostname_sid]/sysman/config according to note 1170373.1, but it has been a while since I used DBConsole. Editing that file, assuming it exists, then restarting DBConsole should do it. If I remember right, the emoms.properties.emca file is a set of defaults created when you use emca to configure DBConsole, and you can copy that file and save the copy as emoms.properties, then make your edits in the copy. I don't think DBConsole actually looks at the content of the emoms.properties.emca file.

I think I may have figured it out.
Very strange, because I'm not as familiar with dbconsole as I am with Grid.
Anyway, so for kicks, I decided to execute the command: $OH/bin/emctl status agent
Not thinking it would work because I don't have an OMS Grid agent installed.
But, low and behold, it gave me typical status as if it were showing me the status of the Grid agent.
Now this is strange, but then I noticed it is showing me:

Yep, I think you are right Brian. I haven't used dbconsole in a while.
I've mainly used OMS Grid. DBConsole lacks a lot of functionality and reports and things that Grid is much better at.
Oh well.... more for that later.

Well darn... now I have problems to get it started again.
I made copies of the file(s) before making changes, and even copied back the original files.
But when I attempt to start the dbconsole, it says "Failed" and I cannot connect to it using my browser.
Something is obviously wrong.
When I check the emctllog file, it shows

I'm not aware of any clearstate functionality in dbconsole, but it's looking like something else is going on here. Hopefully somebody else with more recent 11g dbconsole experience can help you out. I apologize if I've somehow sent you down a bad path!

user12159859 wrote:
I am using OEM DBConsole (database version 11.2) and it keeps logging me out after so many minutes of inactivity unless I happen to be in one of the performance monitoring screen that automatically refreshes every xx seconds.
I've had the same issue with OEM Grid Control.
Is there a setting someplace to turn this off so it doesn't continue to log me out?

When I looked in the emagent log file, I saw: OALL8 is in an inconsistent state

I had stopped and restarted the DBConsole agent several times, but every time it still failed.
I even restarted the database, but still the same results.

After Goggling several sites, I found that this may be related to a bug that causes memory leaks and restarting the server solves the problem.
I did that, and everything worked again, which apparently proves it was related to a memory problem.

When I looked in the emagent log file, I saw: OALL8 is in an inconsistent state

I had stopped and restarted the DBConsole agent several times, but every time it still failed.
I even restarted the database, but still the same results.

After Goggling several sites, I found that this may be related to a bug that causes memory leaks and restarting the server solves the problem.
I did that, and everything worked again, which apparently proves it was related to a memory problem.