RE: New EM12c timeout message in 12.1.0.3.0. DB Perf pages
- From: Peter Sharman <pete.sharman@xxxxxxxxxx>
- To: rjoralist3@xxxxxxxxxxxxxxxxxxxxx, oracle-l@xxxxxxxxxxxxx
- Date: Tue, 17 Dec 2013 09:39:30 -0800 (PST)
The browser will only affect the Adobe issue not the timeout (since the timeout
is set at the OMS). But another question for you - how are you setting this
"globally" as you mentioned? Leaving off the module in the emctl command or
similar? Just trying to see how you are doing that so I can reproduce it.
Pete
Pete Sharman
Principal Product Manager
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA
Phone: +61262924095 | | Fax: +61262925183 | | Mobile: +61414443449
"Controlling developers is like herding cats."
Kevin Loney, Oracle DBA Handbook
"Oh no, it's not, it's much harder than that!"
Bruce Pihlamae, long term Oracle DBA
-----Original Message-----
From: Rich Jesse [mailto:rjoralist3@xxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, December 18, 2013 4:27 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: RE: New EM12c timeout message in 12.1.0.3.0. DB Perf pages
I replied:
> With your info here, it looks like it makes sense for me to spend a
> little time to test other browser configurations. I see that the
> hateable v26 is available at portableapps.com, as well as Chrome, and
> I have IE 9(?) I think as well.
I tried Chrome Version 31.0.1650.63 using the same Flash and timed it: 10
minutes and then timeout. Rats.
Rich
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
