Skip to content
Keep Learning Keep Living
Keep Learning Keep Living
Keep Learning Keep Living

EM Express Basic Troubleshooting

Mustafa, 2019-06-092019-06-10

After 12c, unfortunately, we lost Enterprise Manager Console but we have pre-installed EM Express now. if you remember EM console you would install it with emca utility with many parameters. EM express save you from this because it is embedded. you just need to set a few things in your DB. if you already try to start em express and failed I hope this article will give the basic idea about it.

First, EM express runs on an specific port obviously. to learn this port:

select dbms_xdb_config.getHttpsPort() from dual;

this will give you the port for EM and you can just simply run your EM using this link:

https://10.0.0.1:5050/em

please change 10.0.0.1 with your database ip address and it should work. it is just that simple.  I also want you to remind that you can also use http ports not https. simply use sethttpport and gethttport in dbms_xdb_config.

but if you don’t see em page here then you should follow these:

1- if you didn’t see any port from dbms_xdb_config.gethttpsport() function, you might need to set it first using:

exec dbms_xdb_config.sethttpsport(5050);

you can change 5050 with any port you want.

2- you set the port and can see it as a result of gethttpsport() function but em express page still not working.

check your database parameters first:

show parameter shared_servers

you must see at least 1 for shared_servers parameter, if you see zero or non set it to 1.

EM express calls are handled by LISTENER process so your listener should be aware of your em express service:

lsnrctl status

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=Mustylaptop)(PORT=1521)))
STATUS of the LISTENER
————————
Alias LISTENER
Version TNSLSNR for 64-bit Windows: Version 12.2.0.1.0 – Production
Start Date 08-JUN-2019 23:32:44
Uptime 0 days 23 hr. 34 min. 43 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File C:\app\musta\product\12.2.0\dbhome_1\network\admin\listener.ora
Listener Log File C:\app\musta\diag\tnslsnr\MustyLaptop\listener\alert\log.xml
Listening Endpoints Summary…
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=MustyLaptop)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=MustyLaptop)(PORT=5500))(Security=(my_wallet_directory=C:\APP\MUSTA\admin\orcl12\xdb_wallet))(Presentation=HTTP)(Session=RAW))
Services Summary…
Service “CLRExtProc” has 1 instance(s).
Instance “CLRExtProc”, status UNKNOWN, has 1 handler(s) for this service…
Service “orcl12” has 1 instance(s).
Instance “orcl12”, status READY, has 1 handler(s) for this service…
Service “orcl12XDB” has 1 instance(s).
Instance “orcl12”, status READY, has 1 handler(s) for this service…
The command completed successfully

as you can see my database name is “orcl12” and necessary service name for em express is “orcl12XDB”. your listener should be listing this. if your listener is not on 1521 port (default) then your local_listener parameter in your DB should be pointing this listener (by it’s name) or should be null for default listener.

since EM uses a shared connection your dispatchers parameter should set properly:

show parameter dispatchers

dispatchers string (PROTOCOL=TCP) (SERVICE=orcl12XDB)

again, orcl12XDB (<sid>XDB) is indicated in dispatchers parameter.

so this should be enough but one common mistake is if there are more than one DB on the server they might be trying to use same port be sure every database has it’s own http/https port for EM Express.

EM express is very useful but I will be missing EM console at 11g and most important reason is the performance page. Please consider that “performance hub” in EM Express requires “diagnostic pack” so that means extra cost!

thanks.

edit: by mistake I used dbms_xdb instead of dbms_xdb_config. corrected.

12c Administration 12c18c19cem_Express

Post navigation

Previous post
Next post

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recent Posts

  • Sessions with details
  • DBMS_PIPE Connecting the Sessions
  • DBCA Templates and Dangerous “General Purpose” Template
  • NON-CDB to PDB Migration Horror
  • 23c is Finally Here!
  • Not Deploying is also Important!
  • Damaged rowid is referenced! Health Monitor
  • Old Obsolete Backup is not Deleted

Recent Comments

  • Mustafa on DBMS_PIPE Connecting the Sessions
  • Hemant K Chitale on DBMS_PIPE Connecting the Sessions
  • Mustafa on DBMS_PIPE Connecting the Sessions
  • Hemant K Chitale on DBMS_PIPE Connecting the Sessions
  • Phong on ORA-00942: table or view does not exist and sequences as default value

Categories

  • 11g
  • 12c
  • 18c
  • 19c
  • 21c
  • 23c
  • Administration
  • Compression
  • Development
  • Materialized View
  • Multi-tenant
  • Performance
  • Security
  • SQL / PLSQL
  • Uncategorized
  • Undocumented
  • Useful Scripts

Archives

  • September 2023
  • August 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • October 2021
  • September 2021
  • August 2021
  • April 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • July 2019
  • June 2019
  • May 2019
  • March 2019
  • February 2019
  • June 2018

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

RSS Follow This Blog

  • Sessions with details
  • DBMS_PIPE Connecting the Sessions
  • DBCA Templates and Dangerous “General Purpose” Template
  • NON-CDB to PDB Migration Horror
  • 23c is Finally Here!
  • Not Deploying is also Important!
  • Damaged rowid is referenced! Health Monitor
  • Old Obsolete Backup is not Deleted
  • Autoupgrade doesn’t Upgrade Timezone Version While RU Patching
  • Unique Columns For V$Sql

Archives

  • September 2023
  • August 2023
  • May 2023
  • April 2023
  • March 2023
  • February 2023
  • January 2023
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • October 2021
  • September 2021
  • August 2021
  • April 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • July 2019
  • June 2019
  • May 2019
  • March 2019
  • February 2019
  • June 2018

RSS Follow This Blog

  • Sessions with details
  • DBMS_PIPE Connecting the Sessions
  • DBCA Templates and Dangerous “General Purpose” Template
  • NON-CDB to PDB Migration Horror
  • 23c is Finally Here!
  • Not Deploying is also Important!
  • Damaged rowid is referenced! Health Monitor
  • Old Obsolete Backup is not Deleted
  • Autoupgrade doesn’t Upgrade Timezone Version While RU Patching
  • Unique Columns For V$Sql
RSS Error: A feed could not be found at `http://www.mywebsite.com/feed/`; the status code is `200` and content-type is `text/html; charset="utf-8"`
©2023 Keep Learning Keep Living | WordPress Theme by SuperbThemes