Oracle: 13c

Showing posts with label 13c. Show all posts

Saturday, December 3, 2022

Set OEM page to NOT Timeout

OEM page login session expires to the time what ever you have set in OEM properties and if we want to change to the time depending on your Organization policies then please follow below step

Here i'm trying to set it to NOT expire / Unlimited to do so

Check the current value from OMS server

[oracle@OMSHOSTSRVR bin]$ ./emctl get property -name oracle.sysman.eml.maxInactiveTime
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
SYSMAN password:
Value for property oracle.sysman.eml.maxInactiveTime for oms All Management Servers is null

Set the property value with "-1" which is unlimited

[oracle@OMSHOSTSRVR bin]$ ./emctl set property -name oracle.sysman.eml.maxInactiveTime -value -1
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
SYSMAN password:
Property oracle.sysman.eml.maxInactiveTime has been set to value -1 for all Management Servers
OMS restart is not required to reflect the new property value

[oracle@OMSHOSTSRVR bin]$ ./emctl get property -name oracle.sysman.eml.maxInactiveTime
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
SYSMAN password:
Value for property oracle.sysman.eml.maxInactiveTime at Global level is -1

BOUNCE the OMS to take affect the changes made

$ emctl stop oms -all
$ emctl start oms

Referrence:
EM 12c : How to Change the Timeout Window of an emcli Session (Doc ID 1589497.1)
How to Change the Default Login (Idle) Timeout Value for the Enterprise Manager Cloud Console Connections? (Doc ID 1385996.1)

Saturday, August 18, 2018

13c OEM Status Pending (Target addition is in Progress)

After discovering and adding database to my 13.2 OEM, target database is still in “status Pending (Target addition is in Progress)” even after few days

From OMS repo database……

SQL> select entity_name, entity_type, host_name, manage_status , promote_status, emd_url ,DISPLAY_NAME from SYSMAN.EM_MANAGEABLE_ENTITIES where entity_name like '%DEVDB%' and emd_url like '%oradev01%';

ENTITY_NAME ENTITY_TYPE HOST_NAME MANAGE_STATUS PROMOTE_STATUS

---------------------- ------------------------------------------------------ -------------------- ------------- --------------

EMD_URL

-------------------------------------------------------------
DISPLAY_NAME

------------------------------------------------------------DEVDB oracle_database oradev01.domain.com 2 1

https://oradev01.domain.com:3872/emd/main/

DEVDB

From the above output we can see that

managed_status=2 and promote_status=1 indicates that the target is not yet promoted to the agent side

Now from Target database (DEVDB) go to the agent and check below target status

oradev01:DEVDB:/home/oracle $ cd /opt/oracle/product/oemagent/agent13c/agent_13.2.0.0.0/bin

oradev01:DEVDB:/opt/oracle/product/oemagent/agent13c/agent_13.2.0.0.0/bin $ ./emctl config agent listtargets

Oracle Enterprise Manager Cloud Control 13c Release 2

[oradev01.domain.com, host]

[oradev01.domain.com:3872, oracle_emd]

If you check the above output, it doesn’t listed any of the databases existing ion the server and according to (Doc ID 2286993.1) root.sh has not been executed after the installation of Agent.

To check whether root.sh was executed on target DB

$ cd <AGENT_BASE_DIR>/sbin

oradev01:DEVDB:/opt/oracle/product/oemagent/agent13c/agent_13.2.0.0.0/sbin $ ls -ltr nm*

-rw-r----- 1 oracle dba 9615 Aug 1 2016 nmr_macro_list

-rwx--x--x 1 oracle dba 4786905 Sep 30 2016 nmo.0

-rwx--x--x 1 oracle dba 4703504 Sep 30 2016 nmoconf

-rwx--x--x 1 oracle dba 53058 Sep 30 2016 nmb.0

-rwx--x--x 1 oracle dba 50457 Sep 30 2016 nmgsshe.0

-rwx------ 1 oracle dba 104650 Sep 30 2016 nmr.0

-rwx------ 1 oracle dba 34522 Sep 30 2016 nmrconf

-rwx--x--x 1 oracle dba 4708480 Sep 30 2016 nmopdpx.0

-rwx--x--x 1 oracle dba 105929 Sep 30 2016 nmhs.0

-rwx--x--x 1 oracle dba 585242 Feb 10 2017 nmosudo.0

Hmmm looks like it is NOT

Solution:

Run Root.sh script on target server (oradev01) as a ROOT user

Verify again owner for nm* files

[root@oradev01 root] # /opt/oracle/product/oemagent/agent13c/agent_13.2.0.0.0/root.sh

Finished product-specific root actions.

/etc exist

oradev01:DEVDB:/opt/oracle/product/oemagent/agent13c/agent_13.2.0.0.0/sbin $ ls -lrth

total 30M

-rw-r----- 1 root dba 9.4K Aug 1 2016 nmr_macro_list

-rwx--x--x 1 oracle dba 4.6M Sep 30 2016 nmo.0

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmoconf

-rwx--x--x 1 oracle dba 52K Sep 30 2016 nmb.0

-rwx--x--x 1 oracle dba 50K Sep 30 2016 nmgsshe.0

-rwx------ 1 oracle dba 103K Sep 30 2016 nmr.0

-rwx------ 1 oracle dba 34K Sep 30 2016 nmrconf

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmopdpx.0

-rwx--x--x 1 oracle dba 104K Sep 30 2016 nmhs.0

-rwx--x--x 1 oracle dba 572K Feb 10 2017 nmosudo.0

-rwx--x--x 1 root root 4.6M Aug 6 13:11 nmo.new.bak

-rw-r----- 1 root dba 188 Aug 6 13:11 nmo_public_key.txt

-rwsr-x--- 1 root dba 4.6M Aug 6 13:11 nmo

-rwsr-x--- 1 root dba 104K Aug 6 13:11 nmhs

-rwsr-x--- 1 root dba 52K Aug 6 13:11 nmb

-rwx------ 1 root root 103K Aug 6 13:11 nmr.new.bak

-rwsr-x--- 1 root dba 103K Aug 6 13:11 nmr

-rwxr-xr-x 1 root dba 572K Aug 6 13:11 nmosudo

-rwxr-xr-x 1 root dba 50K Aug 6 13:11 nmgsshe

-rwxr-xr-x 1 root dba 4.5M Aug 6 13:11 nmopdpx

Now Delete the Target database from OEM and rediscover again and this time it will show as up and Running Cheers !!!!

Check This : WARNING: NMO notsetuid-root (Unix-only) 13c OEM

EM 13c : After Discovery, Targets Are Stuck In "Status Pending (Target Addition In Progress)" Status (Doc ID 2286993.1)

Tuesday, May 29, 2018

WARNING: NMO not setuid-root (Unix-only) 13c OEM

For the past Few days my OEM jobs on my DEV server are getting SUSPENDED , tried to schedule multiple time after failure and still they are NOT running they are all in SUSPENDED State.

Agent is up and running and I tried stop, start ,clear, secure, upload, reload all sort of agent commands and still my jobs getting SUSPENDED

From the server all looks good.

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_inst/bin $ ./emctl status agent

Oracle Enterprise Manager Cloud Control 13c Release 2

---------------------------------------------------------------

Agent Version : 13.2.0.0.0

OMS Version : 13.2.0.0.0

Protocol Version : 12.1.0.1.0

Agent Home : /opt/oracle/product/oemagent/agent13c_dev/agent_inst

Agent Log Directory : /opt/oracle/product/oemagent/agent13c_dev/agent_inst/sysman/log

Agent Binaries : /opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0

Core JAR Location : /opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/jlib

Agent Process ID : 261231

Parent Process ID : 261232

Agent URL : https://mydev01.domain.local:3872/emd/main/

Local Agent URL in NAT : https://mydev01.domain.local:3872/emd/main/

Repository URL : https://mydevoms.domain.local:4903/empbs/upload

Started at : 2018-03-21 12:25:23

Started by user : oracle

Operating System : Linux version 2.6.32-696.23.1.el6.x86_64 (amd64)

Number of Targets : 23

Last Reload : (none)

Last successful upload : 2018-03-21 12:59:32

Last attempted upload : 2018-03-21 12:59:32

Total Megabytes of XML files uploaded so far : 0.37

Number of XML files pending upload : 0

Size of XML files pending upload(MB) : 0

Available disk space on upload filesystem : 38.65%

Collection Status : Collections enabled

Heartbeat Status : Ok

Last attempted heartbeat to OMS : 2018-03-21 13:00:45

Last successful heartbeat to OMS : 2018-03-21 13:00:45

Next scheduled heartbeat to OMS : 2018-03-21 13:01:45

---------------------------------------------------------------

Agent is Running and Ready

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_inst/bin $ ./emctl upload agent

Oracle Enterprise Manager Cloud Control 13c Release 2

---------------------------------------------------------------

EMD upload completed successfully

FROM my OEM I see Agent is fine and up and running (but with additional warning)

WARNING:

NMO not setuid-root (Unix-only). Run root.sh script to correct this problem. The next OS Command Job submitted will clear this alert.

According to (Doc ID 1465278.1) this is what I have followed

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/sbin $ ls -lrht

total 33M

-rw-r----- 1 oracle dba 9.4K Aug 1 2016 nmr_macro_list

-rwx--x--x 1 oracle dba 4.6M Sep 30 2016 nmo.0

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmoconf

-rwx--x--x 1 oracle dba 52K Sep 30 2016 nmb.0

-rwx--x--x 1 oracle dba 50K Sep 30 2016 nmgsshe.0

-rwx------ 1 oracle dba 103K Sep 30 2016 nmr.0

-rwx------ 1 oracle dba 34K Sep 30 2016 nmrconf

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmosudo.0

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmopdpx.0

-rwx--x--x 1 oracle dba 104K Sep 30 2016 nmhs.0

-rwxr-x--- 1 oracle dba 103K Feb 23 2017 nmr

-rwxr-xr-x 1 oracle dba 4.5M Feb 23 2017 nmosudo

-rw-r----- 1 oracle dba 188 Feb 23 2017 nmo_public_key.txt

-rwxr-xr-x 1 oracle dba 4.5M Feb 23 2017 nmopdpx

-rwxr-x--- 1 oracle dba 4.6M Feb 23 2017 nmo

-rwxr-x--- 1 oracle dba 104K Feb 23 2017 nmhs

-rwxr-xr-x 1 oracle dba 50K Feb 23 2017 nmgsshe

-rwxr-x--- 1 oracle dba 52K Feb 23 2017 nmb

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0 $ ls -lrth root*

-rwxr-xr-x 1 oracle dba 4.7K Feb 23 2017 root.sh.template

-rwxr-xr-x 1 oracle dba 4.8K Feb 23 2017 root.sh

[root@mydev01 root] # /opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/root.sh

Finished product-specific root actions.

/etc exist

Once Root.sh script ran, I see permissions now changed.

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0 $ cd sbin/

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/sbin $ ls -lrht

total 37M

-rw-r----- 1 root dba 9.4K Aug 1 2016 nmr_macro_list

-rwx--x--x 1 oracle dba 4.6M Sep 30 2016 nmo.0

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmoconf

-rwx--x--x 1 oracle dba 52K Sep 30 2016 nmb.0

-rwx--x--x 1 oracle dba 50K Sep 30 2016 nmgsshe.0

-rwx------ 1 oracle dba 103K Sep 30 2016 nmr.0

-rwx------ 1 oracle dba 34K Sep 30 2016 nmrconf

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmosudo.0

-rwx--x--x 1 oracle dba 4.5M Sep 30 2016 nmopdpx.0

-rwx--x--x 1 oracle dba 104K Sep 30 2016 nmhs.0

-rwx--x--x 1 root root 4.6M Mar 21 13:20 nmo.new.bak

-rw-r----- 1 root dba 188 Mar 21 13:20 nmo_public_key.txt

-rwsr-x--- 1 root dba 4.6M Mar 21 13:20 nmo

-rwsr-x--- 1 root dba 104K Mar 21 13:20 nmhs

-rwsr-x--- 1 root dba 52K Mar 21 13:20 nmb

-rwx------ 1 root root 103K Mar 21 13:20 nmr.new.bak

-rwsr-x--- 1 root dba 103K Mar 21 13:20 nmr

-rwxr-xr-x 1 root dba 4.5M Mar 21 13:20 nmosudo

-rwxr-xr-x 1 root dba 50K Mar 21 13:20 nmgsshe

-rwxr-xr-x 1 root dba 4.5M Mar 21 13:20 nmopdpx

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/sbin $ cd ../bin

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/bin $ ./emctl status agent

Oracle Enterprise Manager Cloud Control 13c Release 2

---------------------------------------------------------------

Agent Version : 13.2.0.0.0

OMS Version : 13.2.0.0.0

Protocol Version : 12.1.0.1.0

Agent Home : /opt/oracle/product/oemagent/agent13c_dev/agent_inst

Agent Log Directory : /opt/oracle/product/oemagent/agent13c_dev/agent_inst/sysman/log

Agent Binaries : /opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0

Core JAR Location : /opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/jlib

Agent Process ID : 261231

Parent Process ID : 261232

Agent URL : https://mydev01.domain.local:3872/emd/main/

Local Agent URL in NAT : https://mydev01.domain.local:3872/emd/main/

Repository URL : https://mydevoms.domain.local:4903/empbs/upload

Started at : 2018-03-21 12:25:23

Started by user : oracle

Operating System : Linux version 2.6.32-696.23.1.el6.x86_64 (amd64)

Number of Targets : 23

Last Reload : (none)

Last successful upload : 2018-03-21 13:19:32

Last attempted upload : 2018-03-21 13:19:32

Total Megabytes of XML files uploaded so far : 0.41

Number of XML files pending upload : 0

Size of XML files pending upload(MB) : 0

Available disk space on upload filesystem : 38.65%

Collection Status : Collections enabled

Heartbeat Status : Ok

Last attempted heartbeat to OMS : 2018-03-21 13:20:46

Last successful heartbeat to OMS : 2018-03-21 13:20:46

Next scheduled heartbeat to OMS : 2018-03-21 13:21:47

---------------------------------------------------------------

Agent is Running and Ready

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/bin $ ./emctl stop agent

Oracle Enterprise Manager Cloud Control 13c Release 2

Stopping agent ... stopped.

mydev01:NOTSET:/opt/oracle/product/oemagent/agent13c_dev/agent_13.2.0.0.0/bin $ ./emctl start agent

Oracle Enterprise Manager Cloud Control 13c Release 2

Starting agent ............. started.

Now I see Warning message is Gone in OEM.

Monday, February 26, 2018

E-Mail Notification grayed out OEM 13.2

My OEM: 13.2 version

Today while I’m trying to modify one of our existing job in my OEM 13c found some of the options are grayed out

Reason:

This is because I logged in as SYSMAN and trying to modify the job but SYSMAN user has NO Email setup in its configuration (Strange but this is our New OEM :) )

Solution:

Add EMAIL group in the SYSMAN configuration

Setup > Security > Administrators > [select SYSMAN and Edit]

Once you edit and save the SYSMAN email configuration then you can now able to modify the jobs

Refer same:

EM 13c: Email Notification Section is Grayed Out in Job Creation Access Page in Enterprise Manager 13.2 Cloud Control (Doc ID 2224915.1)

About this blog

The contents in my blog are uploaded purely according to my convenience & based on my results and should not be considered professional advice, official documentation, or a substitute for vendor‑supported guidance, viewers may or may not get same results ............Any actions you take based on the content of this blog are strictly at your own risk. I am not responsible for any losses, damages, outages, or issues arising from the use or misuse of the information provided here. All product names, trademarks, and registered trademarks are the property of their respective owners. I thank you everyone for visiting my blog