Adobe Flash End-of-Life Impact on Oracle Enterprise Manager Cloud Control

Adobe Flash End-of-Life

Cause :

The Adobe Flash EOL is December 31, 2020.
Adobe has announced that the Flash player will be blocked from running after the EOL date.

 

Adobe Flash Plug-in End-of-Life and Enterprise Manager

Many database performance screens in Enterprise Manager were implemented using Adobe Flash technology in versions prior to Enterprise Manager 13.3.2.0.   These database performance pages include ‘Performance Home’, ‘Top Activity’, ‘ASH Analytics’, ‘Real-time SQL Monitoring’ among others.

These Flash pages were replaced with the Oracle JET UI in Enterprise Manager 13.3.2.0 (EM 13.3 PG), released in 2019, and were later enhanced in Enterprise Manager 13.4.

Adobe Flash is being de-supported by Adobe on December 31, 2020.   If you are running versions of Enterprise Manager 13.3.1 or older and use the database performance pages with Adobe Flash goto solution.

DBSNMP Account Locked ORA-28000 in the Standby Database

 

This is because the standby is open read-only and cannot update any tables.

When a user's account has to be locked on the standby database, it is locked only in memory there.

 

OEM13c – The page has expired. Click OK to continue.

If you are getting an error message or Pop-UP which says “The page has expired. Click OK to continue.” This means that your Cloud Control session has expired or timeout as there was no activity in your session.

 

The default value for session timeout is 45 minutes. Can we increase this session timeout frame, YES! You can. You set this value as per requirement of your company’s security policy. It may vary for different clients or companies.

 

As per your requirement you can increase the Session Timeout time by changing the value of “oracle.sysman.eml.maxInactiveTime” parameter. Also note that the value for this parameter is always defined in Minutes. In-my case the requirement was to keep the session active unless the user itself does not logs out from the application. So I set the value of “oracle.sysman.eml.maxInactiveTime” parameter to -1. But if let’s say you want the session to be active for 10 hours you can set the value to 600. However if you want your session be active forever like in my case, you can set its value to -1.

NOTE: Zero means that the value is set to default than 45 minutes.