EM Express不起作用的故障排除 (Doc ID 1604062.1)

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_BASEadmin$ORACLE_SIDxdb_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_BASEadmin$ORACLE_SIDxdb_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 :  同样，以下内容也会出现在警报日志文件中

Errors in file $ORACLE_BASEdiag dbmsdb_nameinstance_name racedb_name_s0nn_*.trc:
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文件中看到类似的条目：

TIMESTAMP * (CONNECT_DATA=(SERVICE_NAME=orcl12XDB)(CID=(PROGRAM=$ORACLE_HOMEBINsqlplus.exe)(HOST=MREHEEM-EG)(USER=mreheem))) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=50330)) * establish * orcl12XDB * 0

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.  默认情况下，“用户界面和基础结构”下没有标记为“桌面体验”的功能。 选中该框，服务器将重新启动两次，完成后，将显示闪存。

Reference: https://social.technet.microsoft.com/Forums/windowsserver/en-US/4a178833-1fe0-4cec-81b0-bb8769f0ea03/how-do-i-install-flash-player-in-server-2012?forum=winserver8gen 

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个条目

<Time_Stamp> * http * (ADDRESS=(PROTOCOL=tcps)(HOST=<IP_ADRESS>)(PORT=n)) * handoff * http * 0

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个类似于以下内容的条目

<Time_Stamp> * http * (ADDRESS=(PROTOCOL=tcp)(HOST=<IP_ADRESS>)(PORT=n)) * handoff * http * 0

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]