EM login slowness issue

1. Navigate to fmwc System mBean browser.
   
   
       
   
   
   
   
   

Access following AdminServer mBean for setting the cache property.

• emoms.props:Location=AdminServer,name=emoms.properties,type=Properties,Application=em

Setting following three properties. Unless using non-default values, the last two properties are optional.

# Enable caching of FMw Discovery data and use it for other subsequent users.
# Values=true/false Default=false
oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_USE_CACHED_RESULTS=true

# If caching of discovery data is true, this parameter indicates how long the discovery data
# from cache should be used before requiring a fresh discovery.
# Time value is in milliseconds. Default is 7200000 milliseconds.
oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_CACHE_AGE=7200000

# If caching of discovery data is true, a user logs in and a discovery session is in progress,
# this parameter indicates how long the user can wait for current discovery to complete.
# After this wait time is elapsed and discovery is still not finished: If there is already data
# in cache it will be used, else the user will launch a new discovery session.
# Time value is in milliseconds. Default is 10000 milliseconds.
oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_MAX_WAIT_TIME=10000

• Following is example of setting oracle.sysman.emas.discovery.wls.FMW_DISCOVERY_USE_CACHED_RESULTS=true

If new targets are added after enabling discovery cache and new targets are not displayed in fmwc, perform a manual refresh of the Farm to update the discovery cache.

weblogic domain target configuration in OEM 12c

Middleware target configuration  in OEM 12c

In OEM console go to>>setup >>add target>>configure auto discovery

sql server plugin deployment on OEM 12c

Sql server plugin deployment :

Go to setup>>extensibility >>plug-in>>database>>sql server>>rightclick on plugin for optiondeploy then screen will come  as cited below,

database target configuration on OEM

Inorder to add new Db hosts and instance to OEM follow the below steps:

And keep agent as source OEM agent , in my case it was 164 machine (hostname:optimebs64.estuate) and agent is residing on same machine and we just have to add database instance which will be monitoring by OEM on OEM installed machine.

                                                                                                                                                                    

    

        

select agent it will add database instance as database target on OEM console ...        

OEM server reconfiguration after statis IP change

OEM_server_issue _ after static IP change:

Step-1 Changes  ip address in /etc/hosts file as root user

Step-2 restarted oms from backend with command :

./emctl stop oms

And again ./emctl start oms

Step-3 restart agent with command :

./emctl stop agent

And again ./emctl start agent

target status is pending on OEM CONSOLE

Issue: FROM oeM CONSOLE  target status is pending .

Solution:increased job_queue_process to 20 in target db and restarted OMS services and restarted agent .

OMS and agent in  machine1 and  DB in machine2.

Sol:

SQL> alter system set job_queue_processes=20;

System altered.

SQL> sho parameter job_queue_processes;

NAME                                 TYPE        VALUE

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

job_queue_processes                  integer     20

SQL>

Then come to OMS installed machine and restart oms on $OMS_HOME/bin

./emctl  stop oms

Ans then

./emctl  start oms.

And then restart agent  go to >$AGENT_HOME/bin

./emctl  stop agent

Then

./emctl  start agent

Authentication failed ,if it persists check with system administrator

Issue: OEM login Authentication failed ,if it persists check with system administrator .

Root Cause : ERROR audit.AuditLogHandler auditLog.381 – Could not log the audit record java.sql.SQLException: ORA-14400: inserted partition key does not map to any partition ORA-06512: at “SYSMAN.MGMT_AUDIT”, line 873 ORA-06512: at “SYSMAN.MGMT_AUDIT”, line 402 ORA-06512: at line 1 Log: $MIDDLEWARE_HOME/gc_inst/em/EMGC_OMS1/sysman/log/emoms.trc   Estive quebrando a cabeça com o erro acima, […

Solution:

SQL> update mgmt_audit_master set prepopulate_days=5 where prepopulate_days is null;

0 rows updated.

SQL> commit;

Commit complete.

SQL>

SQL> conn SYSMAN

Enter password:

Connected.

SQL> exec mgmt_audit_admin.add_audit_partition;

PL/SQL procedure successfully completed.

SQL> update mgmt_audit_master set prepopulate_days=5 where prepopulate_days is null;

0 rows updated.

SQL> commit;

Commit complete.

SQL> show parameter job_queue_processes;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
job_queue_processes                  integer     20
SQL> alter system set job_queue_processes=200 scope=both;

System altered.

SQL> show parameter job_queue_processes;

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
job_queue_processes                  integer     200

SQL>exit

////////////////restart OMS////////////////////////////////////////////

[oracle@optimebs64 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@optimebs64 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

[oracle@optimebs64 bin]$

Now check URL  you will be able to login OEM page.... :)