Overview
After I had enabled access to the OEM Console through configuring the fire wall rules as described in 08 Configure Firewall Rules , I encountered an issue with console time-outs.
I also patched the agent, and set up privilege delegation.
References
- EM 12c OMS startup fails due to insufficient ulimit value (Doc ID 1427402.1)
- 17513525 (EM-AGENT BUNDLE PATCH 12.1.0.3.5)
- Oracle® Enterprise Manager Cloud Control Basic Installation Guide 12c Release 3 (12.1.0.3)
- Oracle® Enterprise Manager Cloud Control Advanced Installation and Configuration Guide 12c Release 3 (12.1.0.3)
Procedure
Patched Agent
As recommended by OEM, I applied patch 17513525 (EM-AGENT BUNDLE PATCH 12.1.0.3.5) . The procedure was not documented.
Change the OEM Console Timeout
Following the advice given in 10.4 Configuring Timeout Values for Enterprise Manager Components from OMS timeout or Login timeout , I ran the following commands as oracle on CRONULLA , in order to set the time-out to one (1) day (1440 minutes):
cd /opt/app/oracle/em/middleware/oms/bin/ ./emctl set property -name oracle.sysman.eml.maxInactiveTime -value 1440 -module emoms ./emctl stop oms ./emctl start oms
The log of output is:
[oracle@cronulla ~]$ cd /opt/app/oracle/em/middleware/oms/bin/ [oracle@cronulla bin]$ ./emctl set property -name oracle.sysman.eml.maxInactiveTime -value 1440 -module emoms Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. SYSMAN password: Property oracle.sysman.eml.maxInactiveTime has been set to value 1440 for all Management Servers OMS restart is required to reflect the new property value [oracle@cronulla bin]$ ./emctl stop oms Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. Stopping WebTier... WebTier Successfully Stopped Stopping Oracle Management Server... Oracle Management Server Successfully Stopped Oracle Management Server is Down [oracle@cronulla bin]$ ./emctl start oms Oracle Enterprise Manager Cloud Control 12c Release 3 Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved. Starting Oracle Management Server... Starting WebTier... WebTier Successfully Started Oracle Management Server Successfully Started Oracle Management Server is Up WARNING: Limit of open file descriptors is found to be 1024. The OMS has been started but it may run out of descriptors under heavy usage. For proper functioning of OMS, please set "ulimit -n" to be at least 4096.
Reset Limits
When I restarted OMS in the previous section, I noted the following messages:
WARNING: Limit of open file descriptors is found to be 1024. The OMS has been started but it may run out of descriptors under heavy usage. For proper functioning of OMS, please set "ulimit -n" to be at least 4096.
MOS Doc ID 1427402.1 points to 8.3 Prerequisites . Using the procedure for File Descriptor Requirements , I update /etc/security/limits.conf as with the following:
oracle soft nofile 4096 oracle hard nofile 16384
Configuring Privilege Delegation Providers
Following the procedure in 10.7 Configuring Privilege Delegation Providers , I selected the following menu option:
And the next screen appeared:
I clicked the edit icon to get the next screen:
The following command was entered as the sudo command (this was based on the example given in
10.7 Configuring Privilege Delegation Providers
for
emcli
):
/usr/bin/sudo -S -u %RUNAS% %COMMAND%
Clicked Update to get the following confirmation panel:
Clicked Yes. Then I expanded the details for CRONULLA to get the following screen:
