Troubleshooting Why EM Express is not Working (Doc ID 1604062.1)
APPLIES TO:
Oracle Database - Enterprise Edition - Version 12.1.0.1 to 12.1.0.1 [Release 12.1]
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.1.0.2 [Release 12.1]
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
PURPOSE
This Note is Created to Troubleshoot EM Express not working issues and also lists EM Express known issues and bugs.
本說明的創建是為了解決EM Express無法正常工作的問題，並列出了EM Express的已知問題和錯誤。
TROUBLESHOOTING STEPS
1- Review the Basic EM Express Configuration 查看基本EM Express配置
Users can configure EM Express both at the root and the PDB containers, with each container using a different HTTP/HTTPS port. When connected to the root container, the information displayed is for the entire database including all PDBs. When connected to a PDB, the information displayed is restricted to data for the PDB Simply login to the container and set the HTTPS/HTTP port.
用戶可以在root容器和PDB容器上配置EM Express，每個容器使用不同的HTTP/HTTPS端口。 連接到root容器時，顯示的信息適用於整個數據庫，包括所有PDB。 連接到PDB時，顯示的信息僅限於PDB的數據。只需登錄到容器並設置HTTPS/HTTP端口。
By default, DBCA picks a free port from the 5500 to 5599 range to use as the EM Express port.
默認情況下，DBCA選擇5500到5599范圍內的空閑端口作為EM Express端口。
If you want a particular port to be used as the EM Express port, specify that port using the DBEXPRESS_HTTPS_PORT operating system environment variable prior to starting OUI or DBCA.
如果希望將特定端口用作EM Express端口，請在啟動OUI或DBCA之前使用DBEXPRESS_HTTPS_PORT操作系統環境變量指定該端口。
To start EM Express, use the EM Express URL provided by DBCA when DBCA configured your database, 要啟動EM Express，請在DBCA配置數據庫時使用DBCA提供的EM Express URL，
use the following query while connected to CDB or PDB to generate the URL : 連接CDB或PDB時使用以下查詢生成URL
For HTTPS :
SQL> SELECT 'https://'||SYS_CONTEXT('USERENV','SERVER_HOST')||'.'||SYS_CONTEXT('USERENV','DB_DOMAIN')||':'||dbms_xdb_config.gethttpsport()||'/em/' from dual;
SQL> SELECT 'https://'||SYS_CONTEXT('USERENV','SERVER_HOST')||':'||dbms_xdb_config.gethttpsport()||'/em/' from dual;
For HTTP :
SQL> SELECT 'http://'||SYS_CONTEXT('USERENV','SERVER_HOST')||'.'||SYS_CONTEXT('USERENV','DB_DOMAIN')||':'||dbms_xdb_config.gethttpport()||'/em/' from dual;
SQL> SELECT 'http://'||SYS_CONTEXT('USERENV','SERVER_HOST')||':'||dbms_xdb_config.gethttpport()||'/em/' from dual;
When EM Express prompts you for your username and password, log in as a user with DBA privilege (such as SYS).
當EM Express提示您輸入用戶名和密碼時，以具有DBA特權的用戶（例如SYS）身份登錄。
Note: The first time you enter the URL for EM Express in your web browser, your browser may display warning messages.
注意：首次在Web瀏覽器中輸入EM Express的URL時，瀏覽器可能會顯示警告消息。
EM Express is a servlet built on top of Oracle XML DB. The Oracle XML DB default wallet has a self-signed certificate, and some existing browsers consider self-signed certificates as untrusted because they are not signed by a trusted CA (certificate authority). However, the self-signed certificate is still secure, as it ensures that the traffic is encrypted between the Oracle XML DB server and the client (browser).
EM Express是基於Oracle XML DB構建的servlet。 Oracle XML DB默認錢包具有自簽名證書，並且某些現有的瀏覽器將自簽名證書視為不受信任的，因為它們不是由受信任的CA（證書頒發機構）簽名的。但是，自簽名證書仍然是安全的，因為它可以確保在Oracle XML DB服務器與客戶端（瀏覽器）之間對通信進行加密。
Therefore, enter a security exception for the EM Express URL in your web browser.
因此，在Web瀏覽器中輸入EM Express URL的安全例外。
To manually configure the HTTP/HTTPS port for EM Express:
要為EM Express手動配置HTTP/HTTPS端口，請執行以下操作：
1- If the listener is running on a nonstandard port (for example, not 1521), then the init.ora file for the database you want to manage using EM Express must contain a local_listener entry so that the HTTP/HTTPS port can register with the correct listener. The local_listener entry references a TNSNAMES entry that points to the correct listener. For example:
1- 如果偵聽器在非標准端口（例如，不是1521）上運行，則要使用EM Express管理的數據庫的init.ora文件必須包含local_listener條目，以便HTTP/HTTPS端口可以向其中注冊正確的聽眾。 local_listener條目引用了指向正確偵聽器的TNSNAMES條目。例如：
local_listener=inst1
where inst1 is a TNSNAMES entry defined in tnsnames.ora that points to the listener. For example:
其中inst1是tnsnames.ora中定義的TNSNAMES條目，它指向偵聽器。例如：
inst1= (ADDRESS = (PROTOCOL = TCP)(HOST = HOSTNAME_OR_IP )(PORT = 1522))
2- Enable the TCP dispatcher by adding the following entry to the init.ora file for the database you want to manage using EM Express:
2- 通過將以下條目添加到要使用EM Express管理的數據庫的init.ora文件中，來啟用TCP調度程序：
dispatchers="(PROTOCOL=TCP)(SERVICE=<DB_NAME>XDB)"
For example, if the database DB_NAME is ORCL : 例如，如果數據庫DB_NAME是ORCL
SQL> alter system set dispatchers="(PROTOCOL=TCP)(SERVICE=ORCLXDB)";
Also Make Sure that SHARED_SERVERS is greater than Zero : 同時確保SHARED_SERVERS大於零：
SQL> show parameter shared_servers NAME TYPE VALUE ------------------------------------ ----------- ------ shared_servers integer 1 max_shared_servers integer
3- Use the PL/SQL procedure DBMS_XDB_CONFIG.SETHTTPSPORT to set the HTTPS port for EM Express. This will update the HTTPS port in the Oracle XML DB Repository. You must connect as SYS / AS SYSDBA to run the procedure. For example:
3- 使用PL/SQL過程 DBMS_XDB_CONFIG.SETHTTPSPORT 設置EM Express的 HTTPS 端口。 這將更新Oracle XML DB存儲庫中的HTTPS端口。 您必須以SYS / AS SYSDBA身份連接才能運行該過程。 例如：
SQL> connect sys/<password>@<container> as sysdba SQL> exec DBMS_XDB_CONFIG.SETHTTPSPORT(5500);
or Use the PL/SQL procedure DBMS_XDB_CONFIG.SETHTTPPORT to set the HTTP port for EM Express. This will update the HTTP port in the Oracle XML DB Repository.
或使用PL/SQL過程 DBMS_XDB_CONFIG.SETHTTPPORT 設置EM Express的 HTTP 端口。 這將更新Oracle XML DB存儲庫中的HTTP端口。
You must connect as SYS / AS SYSDBA to run the procedure. For example: 您必須以SYS / AS SYSDBA身份連接才能運行該過程。 例如
SQL> connect sys/<password>@<container> as sysdba SQL> exec DBMS_XDB_CONFIG.SETHTTPPORT(2200);
2- Make Sure the XML Database option is installed and valid 2-確保XML數據庫選項已安裝且有效
EM Express is a servlet built on top of Oracle XML DB . EM Express是基於Oracle XML DB構建的servlet。
Make Sure That the XML Database option is installed and valid : 確保XML數據庫選項已安裝且有效：
Enter the following command to verify that the XML DB option is installed: --輸入以下命令以驗證是否已安裝XML DB選項：
SQL> DESC RESOURCE_VIEW If XML DB is not installed, this command returns an "object does not exist" error. --如果未安裝XML DB，此命令將返回"object does not exist" error。 col comp_name for a20
col version for a15 SQL> -- Check status of XDB 檢查XDB的狀態 SQL> select comp_name, version, status from dba_registry where comp_id = 'XDB'; SQL> -- Check for invalid objects 檢查無效的對象 SQL> select owner, object_name, object_type, status from dba_objects where status = 'INVALID' and owner in ('SYS', 'XDB');
You should also see the following in the alert log file upon startup : 啟動后，您還將在警報日志文件中看到以下內容：
XDB installed. XDB initialized.
3- Make Sure that the Listener Register the XML DB : 3- 確保偵聽器注冊XML DB：
The Listener Log Will show the following after startup : 啟動后，偵聽器日志將顯示以下內容：
Started with pid=n ... Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=xxx.us.oracle.com)(PORT=5500))(Security=(my_wallet_directory=$ORACLE_BASE\admin\$ORACLE_SID\xdb_wallet))
(Presentation=HTTP)(Session=RAW)) --> This is For HTTPS Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.us.oracle.com)(PORT=8080))(Presentation=HTTP)(Session=RAW)) --> This is For HTTP
or From lsnrctl utility : 或從lsnrctl實用程序
lsnrctl status | grep HTTP (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=xxx.us.oracle.com)(PORT=5500))(Security=(my_wallet_directory=$ORACLE_BASE\admin\$ORACLE_SID\xdb_wallet))
(Presentation=HTTP)(Session=RAW)) --> this is For HTTPS (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.us.oracle.com)(PORT=8080))(Presentation=HTTP)(Session=RAW)) --> this is For HTTP
which would appear under "Listening Endpoints Summary" from lsnrctl stat command .
它會顯示在lsnrctl stat命令的"Listening Endpoints Summary"。
4- Make sure the SYSTEM account are not Locked or Expired : 4- 確保SYSTEM帳戶未鎖定或過期：
SQL> select USERNAME,NAME,ACCOUNT_STATUS,LOCK_DATE from cdb_users u,v$containers c where u.CON_ID=c.CON_ID and USERNAME ='SYSTEM' ;
The SYSTEM account needs to be unlocked for the EM Express to work , Because this user is Used Internally by the EM Express connections ,
需要解鎖SYSTEM帳戶才能使EM Express正常工作，因為EM Express連接在內部使用了該用戶，
If the SYSTEM account is locked , you will not be able to use the EM Express and the following error will appear while trying to log in to EM Express :
如果SYSTEM帳戶已鎖定，則您將無法使用EM Express，並且嘗試登錄EM Express時將出現以下錯誤：
Internal Server Error
Also the following will Appear in the Alert log file : 同樣，以下內容也會出現在警報日志文件中
ORA-28000: the account is locked
To Unlock the SYSTEM account you can use : 要解鎖系統帳戶，您可以使用
SQL> alter user system account unlock;
Note : Logging to EM Express/Sqlplus with user SYS as sysdba is possible even when the SYS account is locked.
注意：即使SYS帳戶已鎖定，也可以使用sysdba用戶SYS身份登錄到EM Express/Sqlplus。
Note : The SYSTEM account needs to be unlocked even when logging to EM Express with SYS .
注意：即使使用SYS登錄到EM Express，也需要解鎖SYSTEM帳戶。
5- Connect to the XDB service as the SYSTEM user 5- 以SYSTEM用戶身份連接到XDB服務
Make sure that You can connect to the XDB service as the SYSTEM user from sqlplus , 確保可以從sqlplus以SYSTEM用戶身份連接到XDB服務
First You need to create a tnsnames.ora entry for the XDB service referenced in the DISPATCHERS parameter , for example :
首先，您需要為DISPATCHERS參數中引用的XDB服務創建一個tnsnames.ora條目，例如：
SQL> show parameter dispa NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ dispatchers string (PROTOCOL=TCP) (SERVICE=orcl12XDB)
Also Make Sure that SHARED_SERVERS is greater than Zero : 還要確保SHARED_SERVERS大於零
SQL> show parameter shared_servers NAME TYPE VALUE ------------------------------------ ----------- ------ shared_servers integer 1 max_shared_servers integer
Then create a tnsnames.ora entry for the XDB service : 然后為XDB服務創建一個tnsnames.ora條目：
ORCL12XDB =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = orcl12XDB)
)
)
Then connect from sqlplus :
SQL> conn system/sys@ORCL12XDB
Connected.
also you should see a similar entry in the listener.log file : 您還應該在listener.log文件中看到類似的條目：
6- Try Different Browsers (IE,Chrome,FireFox) and/or Try To Disable all Browser Addons and/or Try old versions of Browsers which were available at db release 6- 嘗試使用不同的瀏覽器(IE,Chrome,FireFox) 和/或嘗試禁用所有瀏覽器插件和/或嘗試在數據庫版本中可用的舊版本的瀏覽器
Some Browser addons blocks Flash like Flashblock and Plugins Toggler , ... 一些瀏覽器插件阻止Flash，例如 Flashblock and Plugins Toggler，...
which also blocks EM Express , Try To Disable such Browser Addons and re-try to open EM Express. 這也會阻止EM Express，嘗試禁用此類瀏覽器插件，然后重試以打開EM Express。
Try old version of browsers which were available at db release, there are cases where recent version of browsers might implement some feature, which may cause EM Express to stop working. 嘗試使用數據庫版本中可用的舊版本瀏覽器，在某些情況下，最新版本的瀏覽器可能實現某些功能，這可能會導致EM Express停止工作。
Try to use 32 bit version instead of 64 bit (visa versa) version of the browsers, there are known issues reported and solved by this action Refer Note 2540271.1
嘗試使用32位版本而不是64位（反之亦然）版本的瀏覽器，此操作報告並解決了已知問題，請參閱Note 2540271.1
Note 2540271.1 EM Express Throws Error Message Login_Fail_Accessibility and Fail to parse the data returned by server errors (Doc ID 2540271.1)
Note 2540271.1 EM Express 引發錯誤消息 Login_Fail_Accessibility，並且無法解析服務器錯誤返回的數據 (Doc ID 2540271.1)
7- Check if Flash Plugin is Enabled 7- 檢查是否啟用了Flash插件
Web browsers Requirements Web瀏覽器要求
Web browsers must support Java Script, and the HTML 4.0 and CSS 1.0 standards and Flash. For a list of browsers that meet these requirements see the Enterprise Manager certification matrix on My Oracle Support:
Web瀏覽器必須支持Java Script，HTML 4.0和CSS 1.0標准以及Flash。有關滿足這些要求的瀏覽器的列表，請參見My Oracle Support上的企業管理器認證矩陣
https://support.oracle.com
See Also: Oracle Enterprise Manager Cloud Control Basic Installation Guide for steps on how to access the Enterprise Manager certification matrix
另請參閱：《 Oracle企業管理器雲控制基礎安裝指南》，以獲取有關如何訪問企業管理器認證矩陣的步驟
From Firefox
From Add-ons Menu , Make sure that Shockwave Flash is Always Activate 在“附加菜單”中，確保“ Shockwave Flash”始終處於激活狀態
To Make sure its Activated , Type about:plugins in the address bar to open the Plug-ins page. 要確保其已激活，請在地址欄中鍵入about:plugins以打開“ Plug-ins”頁面。
Make Sure that Shockwave Flash , Adobe Flash plugins are enabled 確保Shockwave Flash和Adobe Flash插件已啟用
From Google Chrome
Type chrome://plugins/ in the address bar to open the Plug-ins page. (chrome://plugins/ is not working in latest Chrome)
在地址欄中輸入 chrome://plugins/ 以打開“插件”頁面。 （chrome://plugins/ 在最新的Chrome中不起作用）
On the Plug-ins page that appears, find the "Flash" listing. 在出現的“插件”頁面上，找到“ Flash”列表
To enable Adobe Flash Player, click the Enable link under its name. 要啟用Adobe Flash Player，請單擊其名稱下的“啟用”鏈接
Check Always allowed 選中始終允許
In Windows 2012 server, Flash player is embedded so you don't have to install it. 在Windows 2012 Server中，Flash Player是嵌入式的，因此您無需安裝它。
There is a Feature labelled "Desktop Experience" under "User Interfaces and Infrastructure" that is not checked by default. You check that box and the server will restart twice , Once that is complete the flash will appear. 默認情況下，“用戶界面和基礎結構”下沒有標記為“桌面體驗”的功能。 選中該框，服務器將重新啟動兩次，完成后，將顯示閃存。
8- Check The Alert Log file and Listener Log file for errors logged around the time of launching the URL for EM Express 8- 檢查警報日志文件和偵聽器日志文件中是否存在啟動EM Express URL時記錄的錯誤
Normally you should see about 20 entries similar to the following in the listener.log file for a successful EM Express login If Using HTTPS:
通常，如果使用HTTPS，則在EM Express成功登錄后，您應該在listener.log文件中看到類似於以下內容的20個條目
And about 7 entries similar to the following in the listener.log file for a successful EM Express login If Using HTTP:
如果使用HTTP，則成功偵聽EM Express時，在listener.log文件中大約有7個類似於以下內容的條目
9- Check the listener end points of the XML DB HTTP server 9- 檢查XML DB HTTP服務器的偵聽器端點
DBMS_XDB_CONFIG.SETLISTENERLOCALACCESS Procedure Restricts all listener end points of the XML DB HTTP server to listen either only on the localhost interface (TRUE) or to listen on both localhost and non-localhost interfaces (FALSE)
DBMS_XDB_CONFIG.SETLISTENERLOCALACCESS 過程限制XML DB HTTP服務器的所有偵聽器端點僅偵聽localhost接口（TRUE）或偵聽localhost和非localhost接口（FALSE）
DBMS_XDB.SETLISTENERLOCALACCESS Procedure do the same functionality, This procedure is deprecated in Release 12c.
DBMS_XDB.SETLISTENERLOCALACCESS 過程執行相同的功能，此過程在版本12c中已棄用。
This functionality is replaced by the DBMS_XDB_CONFIG package - the SETLISTENERLOCALACCESS Procedure.
此功能已由DBMS_XDB_CONFIG包-SETLISTENERLOCALACCESS過程代替。
Make Sure the following PLSQL block returns 'localhost and non-localhost' :
確保以下PLSQL塊返回 'localhost and non-localhost' ：
For HTTPS :
set serveroutput on
DECLARE
hval VARCHAR2(30);
pval NUMBER;
lval NUMBER;
BEGIN
dbms_xdb_config.getListenerEndPoint(dbms_xdb_config.xdb_endpoint_http2, hval, pval, lval);
dbms_output.put_line('Host: ' || NVL(hval,'localhost and non-localhost'));
dbms_output.put_line('Port: ' || TO_CHAR(pval));
dbms_output.put_line('Protocol: ' || CASE TO_CHAR(lval) WHEN 2 THEN 'https' WHEN 1 THEN 'http' ELSE TO_CHAR(lval) end);
END;
/
For HTTP :
set serveroutput on
DECLARE
hval VARCHAR2(30);
pval NUMBER;
lval NUMBER;
BEGIN
dbms_xdb_config.getListenerEndPoint(dbms_xdb_config.xdb_endpoint_http, hval, pval, lval);
dbms_output.put_line('Host: ' || NVL(hval,'localhost and non-localhost'));
dbms_output.put_line('Port: ' || TO_CHAR(pval));
dbms_output.put_line('Protocol: ' || CASE TO_CHAR(lval) WHEN 2 THEN 'https' WHEN 1 THEN 'http' ELSE TO_CHAR(lval) end);
END;
/
If This Returns 'localhost' so the EM Express can only be accessed using : 如果此返回 'localhost' ，則只能使用以下命令訪問EM Express：
https://localhost:portnumber/em/
If This Returns 'localhost and non-localhost' so the EM Express can be accessed using both : 如果此返回 'localhost and non-localhost'，則可以使用以下兩種方式訪問EM Express：
https://localhost:portnumber/em/
https://database-hostname:portnumber/em/
To Allow the EM Express to listen on both localhost and non-localhost interfaces : 要允許EM Express在localhost和非localhost接口上偵聽
exec DBMS_XDB_CONFIG.SETLISTENERLOCALACCESS(false);
10- Wallet file permissions when RDBMS sits on top of GI with role separation -- This case is only applicable to UNIX platform. 10- RDBMS位於具有角色分離的GI之上的錢包文件權限-這種情況僅適用於UNIX平台。
The wallet files should have permission 0600, and that doesn't allow successful display of the EM Express page when RDBMS sits on top of GI with role separation.
錢包文件應具有權限0600，並且當RDBMS位於具有角色分離的GI之上時，不允許成功顯示EM Express頁面。
The XDB wallet is stored in the $ORACLE_BASE/admin/<db_name>/xdb_wallet directory . If ORACLE_BASE is not defined, the XDB wallet is stored in $ORACLE_HOME/admin/<db_name>/xdb_wallet, where <db_name> is the unique database name.
XDB錢包存儲在$ORACLE_BASE/admin/<db_name>/xdb_wallet目錄中。 如果未定義ORACLE_BASE，則XDB錢包存儲在$ORACLE_HOME/admin/<db_name>/xdb_wallet中，其中<db_name>是唯一的數據庫名稱。
ls -l would show -rw------- 1 oracle asmadmin 3926 Jun 28 13:45 cwallet.sso -rw------- 1 oracle asmadmin 3881 Jun 28 13:45 ewallet.p12
changing mode to 640 to allow for group asmadmin to read the wallet files makes the EM Express page available via browser.
如果將模式更改為640以允許組asmadmin讀取錢包文件，則可以通過瀏覽器訪問EM Express頁面。
The wallet can also be recreated with : 還可以使用以下方式重新創建錢包
SQL> exec DBMS_XDB_ADMIN.INSTALLDEFAULTWALLET;
11- Known errors which can affect EM Express : 11-可能影響EM Express的已知錯誤
ORA-00600: internal error code, arguments: [kziaulslt: lid], [1821]
The "1821" refers to: ORA-01821: date format not recognized , which means that NLS_TIMESTAMP_FORMAT and/or NLS_DATE_FORMAT parameters values are incorrect .
"1821" 是指：ORA-01821：無法識別日期格式，這意味着NLS_TIMESTAMP_FORMAT和/或NLS_DATE_FORMAT參數值不正確。
for example : NLS_TIMESTAMP_FORMAT = 'YYYY-MM-DD HH24:MIS.FF'
Please change NLS_TIMESTAMP_FORMAT and/or NLS_DATE_FORMAT to a valid value , for example :
請將NLS_TIMESTAMP_FORMAT和/或NLS_DATE_FORMAT更改為有效值，例如：
SQL> alter system set NLS_TIMESTAMP_FORMAT = 'YYYY-MM-DD HH:MI:SS.FF' scope=spfile; SQL> alter system set NLS_DATE_FORMAT = 'MM/DD/YYYY' scope=spfile;
You may need also to set this parameter as OS Environmental variable in the user profile starting the database .
您可能還需要在啟動數據庫的用戶配置文件中將此參數設置為OS Environment變量。
then restart the database and the listener and re-try to open EM Express . 然后重新啟動數據庫和偵聽器，然后重試以打開EM Express。
ORA-00600: internal error code, arguments: [kziaulslt: lid], [1818]
The "1818" refers to: ORA-01818: HH24' precludes use of meridian "1818"是指：ORA-01818：HH24'禁止使用子午線
which means that NLS_TIMESTAMP_FORMAT and/or NLS_DATE_FORMAT parameters values , 這意味着NLS_TIMESTAMP_FORMAT和/或NLS_DATE_FORMAT參數值，
reference a date value using both the 24 hour indicator (hh24) and the meridian indicator (AM or PM). 使用24小時指示器（hh24）和子午指示器（AM或PM）來參考日期值。
for example : NLS_TIMESTAMP_FORMAT = 'DD/MON/YY HH24:MI:SSXFF AM'
lease change NLS_TIMESTAMP_FORMAT and/or NLS_DATE_FORMAT to a valid value , for example : SQL> alter system set NLS_TIMESTAMP_FORMAT = 'YYYY-MM-DD HH:MI:SS.FF' scope=spfile;
SQL> alter system set NLS_DATE_FORMAT = 'MM/DD/YYYY' scope=spfile;
You may need also to set this parameter as OS Environmental variable in the user profile starting the database . then restart the database and the listener and re-try the EM Express .
您可能還需要在啟動數據庫的用戶配置文件中將此參數設置為OS Environment變量。然后重新啟動數據庫和偵聽器，然后重試EM Express。
Bug 16527374 : CDB:ORA-07445:EM EXPRESS HOME GOT IO ERROR
In Container Database environment, after login with EM Express to the Root , No such issue in Non-cdb environment.
在Container Database環境中，使用EM Express登錄到Root之后，在Non-cdb環境中沒有此問題。
The Bug Symptoms can be any of the following : 錯誤症狀可能是以下任何一種
Connection Fail : Connection with database failed. Database instance might be down. Try again once it is up
Detail : [IOErrorEvent type='ioError' bubbles=false cancelable=false eventPhase=2 text='Error #2032']
ORA-07445: exception encountered: core dump [qervwRowProcedure()+] [SIGSEGV] [ADDR:0x5] [PC:0xB5C0C21] [Address not mapped to object]
ORA-07445: exception encountered: core dump [qervwFetch()+] [ACCESS_VIOLATION] [ADDR:0x8] [PC:0x1464D2038] [UNABLE_TO_READ] []
after successfully login to EM Express the chart of [Resources] & [SQL Monitor] Charts can not be loaded , and stays loading forever
All the other sections on the main page are displayed correctly , The other tabs such as configuration, storage, security, performance, etc., are also displayed properly.
主頁上的所有其他部分均正確顯示，其他選項卡（如配置，存儲，安全性，性能等）也正確顯示。
This is Caused By Unpublished Bug 16527374 : [12100-LIN64-130318]CDB:ORA-07445:EM EXPRESS HOME GOT IO ERROR
Please Apply Patch 16527374
on Windows Platforms , The Fix for this Bug is Included in 12.1.0.1 Bundle Patch 3 and upwards Bundle Patches
在Windows平台上，此錯誤的修復程序包含在12.1.0.1 Bundle Patch 3 和更高版本的Bundle Patch中。
Bug 16102371 : EM EXPRESS URL DOES NOT WORK
The Oracle Enterprise Manager Database Express (EM Express) URL may not work on an Oracle RAC node.
Oracle Enterprise Manager Database Express（EM Express）URL可能不適用於Oracle RAC節點。
Workaround: This bug may be encountered during Oracle RAC installation. If the EM Express URL does not work on an Oracle RAC node, restart the Node Listener on that machine.
解決方法：在Oracle RAC安裝過程中可能會遇到此錯誤。如果EM Express URL在Oracle RAC節點上不起作用，請在該計算機上重新啟動節點偵聽器。
Bug 16219867 : EM Express URL displayed by the DBCA summary may not work
When an Oracle RAC policy-managed database is created by the Database Configuration Assistant (DBCA), the EM Express URL displayed by the DBCA summary may not work. This can happen if the local node is not part of the server pool hosting the database. This issue happens only for policy-managed Oracle RAC databases.
由數據庫配置助手（DBCA）創建Oracle RAC策略管理的數據庫時，由DBCA摘要顯示的EM Express URL可能不起作用。如果本地節點不是托管數據庫的服務器池的一部分，則會發生這種情況。僅對策略管理的Oracle RAC數據庫會發生此問題。
EM Express is configured and accessible from nodes where database instances are running. It can also be accessed using the scan name.
已配置EM Express，並且可以從運行數據庫實例的節點訪問EM Express。也可以使用scan名稱進行訪問。
Workaround: Use the scan name for the host name in the EM Express URL. For example, consider the following EM Express URL (where racnode1 is the node name):
解決方法：將scan名稱用作EM Express URL中的主機名。例如，考慮以下EM Express URL（其中racnode1是節點名稱）：
https://racnode1.oracle.com:5500/em
You can specify the following (where scan1 is the scan name of the cluster):
您可以指定以下內容（其中scan1是集群的掃描名稱）：
https://scan1.oracle.com:5500/em
REFERENCES
NOTE:1601454.1 - EM Express 12c Database Administration Page FAQ
BUG:17837856 - ORA-600 [KZIAULSLT: LID], [1821]