Best Of
Re: OEM for storing passwords
Hello Mr C,
** You cannot store your credentials in OEM Cloud Control.
Once you store the credential in OEM Cloud Control, only the username is shows on the OEM Console. The password is only shown as ********.
Regards,
Satya
Re: inode Metric
Hello Mr C,
The Enhancement has not yet been approved and implemented by Development Team. Development is working on it but we don't have ETA as of now. You can create a Metric Extension for it.
EM 13c : Can Inode value parameter be monitored through OEM (Doc ID 2894420.1)
Regards,
Satya
Re: Does Oracle Database Agent Is Using TLS1.2?
Hello @User_EJKEZ ,
You can follow the below MOS note to configure all OEM Cloud Control Components to use TLS 1.2
EM 13c: Enterprise Manager 13c Cloud Control Configuration to Support Transport Layer Security Protocol:TLSv1.2 only (Doc ID 2212006.1)
Regards,
Satya
Re: upgrade java/jre from 1.7.0_111-b13 to latest available version
Hello @User_E4DOJ ,
For EM 13.2 : JDK 1.7 Update 261 is the latest certified JDK for 13.2 OMS.
JDK 1.8 is only supported 13.4 and 13.5 Agents.
How to Use Latest Certified JDK 7 Update with EM 13.2 / 13.3 OMS (Doc ID 2241358.1)
EM 13c: How to Use Latest Certified JDK 7 Update with Enterprise Manager 13.2 or 13.3 Cloud Control Agent (Doc ID 2241373.1)
EM 13.2 / 13.3 : How to Use the Latest Certified IBM JDK 7 Update With EM OMS / Agent ? (Doc ID 2606247.1)
Regards,
Satya
Re: Upgrade OEM 13.2 to latest version
Hello @User_E4DOJ .
The minimum version supported for upgrading to EM 13.5 is 13.3. If the OMS is at 12.1.0.x, 13.1 or 13.2, it is mandatory that it is first upgraded to 13.3.0.0.0 or 13.4.0.0.0. Please check the respective checklists and upgrade guides for the version you are upgrading to.
It will be a 2 step process in your case.
Step 1 ) Upgrade from 13.2 to 13.3/13.4
EM 13c: Checklist for Upgrading Enterprise Manager Cloud Control from Version 13.2/13.3 to 13.4 (Doc ID 2625646.1)
Step 2) Upgrade from 13.3/13.4 to 13.5.
13.5: Checklist for Upgrading Enterprise Manager Cloud Control from Version 13.3/13.4 to 13.5 (Doc ID 2761728.1)
Regards,
Satya
Re: About Oracle Created Accounts
But, remember above, my question was: which of those users are actually no longer in use ?
When you create the database, you can install additional components that may not be used / required. First thing would be to install just what you need rather than just clicking next next next :-).
If there are components that are not used, and you want to remove them, here is a guide by Mike Dietrich explaining how to do that
https://mikedietrichde.com/2017/07/26/remove-clean-components-oracle-11-2-12-2/
Re: About Oracle Created Accounts
In fact, there should be documentation about each account. Oracle does not need to detail each account, they can say: "account for internal usage, may be locked or not but do NOT remove it".
They kinda do...run this:
select * From dba_users where oracle_maintained='Y';
Any user with Y in this column should not be dropped or otherwise modified unless you know exactly what you are doing. Most will be locked. But some may be unlocked like SYS, SYSTEM, and DBSNMP.
Option to "Mark as Read" without having to open the item
At the moment the only way to mark an item as read is to open it and close it again. I work in a small localization and much of the content published is not applicable to me. It would be great if there was a "Mark as Read" function available so that I do not have to open and close all items. I use the bold titles to let me know whether I have read an item or not. This is to make sure I do not miss something. So the ability to "Mark as Read" that would work in the same way as the "Dismiss" function does would be great.
