One of my customer is running on Oracle 19c. They want to use OEM for can see database usage by OEM.
Most of customers are use se Enterprise Manager Database Express for performance monitoring, administrators jobs.
If you are not able to access Enterprise Manager , it might be not configured yet or your wallet file has no permission of 600 or some other errors which located in log files.
PS: In this case related OEM already configured on database side.
Now Let us check some values from database
SQL> select dbms_xdb_config.gethttpsport from dual; GETHTTPSPORT ------------ 0 SQL> select dbms_xdb_config.gethttpport from dual; GETHTTPPORT ------------ 0
If you see 0 both of them, execute these procedures.
SQL> exec dbms_xdb_config.sethttpsport(5500);
SQL> exec dbms_xdb_config.sethttpport(5550);
If you still cannot connect, check the wallet files.
Check the directory of wallet files, run this command fist;
[oracle@helios]# lsnrctl stat | grep HTTP
output is;
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=localhost)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/admin/orcl/xdb_wallet))(Presentation=HTTP)(Session=RAW))
copy the my_wallet_directory directory and run ls -l command.
[oracle@helios]# cd /u01/app/oracle/admin/orcl/xdb_wallet
[oracle@helios xdb_wallet]# ls -l
-rw——-. 1 oracle oracle 3880 Mar 10 07:52 cwallet.sso
-rw——-. 1 oracle oracle 3835 Mar 10 07:52 ewallet.p12
You will see they have -rw permisson. You have to set with -rw-r . Changing mode to 640 to allow for group oinstall to read the wallet files makes the EM Express page available via browser.
[root@helios xdb_wallet]#chmod 640 ewallet.p12
[oracle@helios xdb_wallet]#chmod 640
[oracle@localhost xdb_wallet]# ls -l
-rw-r—–. 1 oracle oracle 3880 Mar 10 07:52 cwallet.sso
-rw-r—–. 1 oracle oracle 3835 Mar 10 07:52 ewallet.p12
Now you can connect with browser.
Yorum bırakın
Comments feed for this article