EM 12c configuration records

OMS server is Linux, install and configure agent on Windows.
1.Add the patch to support the platform.

2.Setup->Add Target->Add Targets Manually->Add Host Targets
Because the OMS default use commands under c:/cygwin/bin so I changed the following file to use commands in c:/mksnt/mksnt or
c:/mksnt/bin.
/opt/ora/middleware/oms/oui/prov/resources/ssPaths_msplats.properties

If the configuration failed, then on the agent node, delete the old service and run the command on agent manually.
(1)sc delete Oracleagent12c1Agent
(2)c:/app/agent12c/ADATMP_2014-03-02_17-45-13-PM/agentDeploy.bat -ignorePrereqs ORACLE_HOSTNAME=******
AGENT_BASE_DIR=c:/app/agent12c OMS_HOST=****** EM_UPLOAD_PORT=4900 AGENT_INSTANCE_HOME=c:/app/agent12c/agent_inst
b_doDiscovery=false b_startAgent=false b_forceInstCheck=true AGENT_PORT=3872 AGENT_REGISTRATION_PASSWORD=******
(3)c:/app/agent12c/core/12.1.0.3/bin/emctl start agent

3.Setup->Add Target->Auto Discovery Results
Select the agent and “Prompt”.

4.Then I found that only agent online in OMS but no hosts and others. Then on agent node, run following command and refresh the
interface.
C:\app\agent12c\core\12.1.0.3.0\bin>emctl config agent addinternaltargets

5.Setup->Extensibility->Plug-ins
Databases->Oracle Database(Right click)->Deploy On->Management Agent
Note: This step Seems can automatically completed when add cluster.

6.Add the cluster.
Set->Add Target->Add Targets Manually->Add Targets Using Guided Process(Also Adds Related Targets)
Choose “Target Types” as “Oracle Cluster and High Availability Service”.

7.Add database instances.
Choose “Target Types” as “Oracle Database,Listener and Automatic Storage Management”.

8.Enable QoS.
(1)Change the password for “qosadmin”
On agent node:
srvctl stop oc4j
qosctl qosadmin -setpasswd qosadmin
srvctl start oc4j
(2)Enable QoS for cluster.
Cluster name->Administration->Quality of Service Management->Create Policy Set
(3)Enable Qos for database.

9.If you add new services or databases, add performance classes in QoS of the cluster.

Some problems and solutions:
SCENARIO 1:
C:\app\agent_12c\core\12.1.0.3.0\bin>emctl pingOMS
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
—————————————————————
EMD pingOMS error: OMS sent an invalid response: “ERROR- Failed to update Target type Metadata”

In C:/app/agent_12c/agent_inst/sysman/log/gcagent.log:
2014-02-28 02:02:04,173 [109:9255CBDA] INFO – attempting initial heartbeat
2014-02-28 02:02:04,219 [109:9255CBDA] WARN – improper ping interval (EM_PING_NOTIF_RESPONSE: ERROR- Failed to update Target type
Metadata)
2014-02-28 02:02:04,221 [109:9255CBDA] WARN – Ping protocol error

In /opt/ora/gc_inst/em/EMGC_OMS1/sysman/log/emoms_pbs.log
2014-02-27 19:44:31,182 [[ACTIVE] ExecuteThread: ’12’ for queue: ‘weblogic.kernel.Default (self-tuning)’] ERROR gcloader.Receiver
logp.251 – Error occurred while accessing to repository
java.sql.SQLException: ORA-20238: Target ***:3872:oracle_emd is currently in the process of being deleted
ORA-06512: at “SYSMAN.EM_TARGET”, line 3049
ORA-06512: at “SYSMAN.EM_TARGET”, line 3317
ORA-06512: at “SYSMAN.EM_TARGET”, line 3992
ORA-06512: at line 1

OPERATION:
$ ./emcli login -username=SYSMAN
$ ./emcli get_targets -target=’***:3872:oracle_emd’
$ ./emcli delete_target -name=’***:3872″ -type=”oracle_emd’ -delte_monitored_targets -async
$ ./emcli sync
$ ./emcli logout

SCENARIO 2:
The agent appears KEY MISMATCH.
In emoms_pbs.log:
2014-02-27 00:17:44,971 [[ACTIVE] ExecuteThread: ’23’ for queue: ‘weblogic.kernel.Default (self-tuning)’] ERROR
receiver.AbstractOMSHandshake logp.251 – OMSHandshake failed.(AGENT URL = https://***:3872/emd/main/)(ERROR =
KEY_MISMATCH as Last AgentURL is null and the Agent Key in repos is not same as that sent by the Agent)

In C:/app/agent_12c/agent_inst/sysman/log/gcagent.log:
2014-02-27 02:05:06,446 [148:HTTP Listener-148 – /emd/lifecycle/main/] ERROR – unspecified request header Client-Type
oracle.sysman.gcagent.comm.ProtocolException: unspecified request header Client-Type

OPERATION:
emctl stop agent
emctl unsecure agent (maybe not needed)
emctl secure agent

SCENARIO 3:
In emdctlj.log:
2014-03-06 00:35:30,598 [main] INFO – unable to connect to http server at https://***:3872/emd/lifecycle/mai
n/. [peer not authenticated]
oracle.sysman.emSDK.agent.comm.exception.VerifyConnectionException: unable to connect to http server at https://***:3872/emd/lifecycle/main/. [peer not authenticated]
at oracle.sysman.gcagent.comm.http.ClientConnection.verifySecureConnection(ClientConnection.java:858)
at oracle.sysman.gcagent.comm.http.ClientConnection.makeConnection(ClientConnection.java:829)
at oracle.sysman.gcagent.comm.oms.http.TMClientConnection.<init>(TMClientConnection.java:88)
at oracle.sysman.gcagent.comm.oms.http.HTTPClientTerminus.connect(HTTPClientTerminus.java:239)
at oracle.sysman.gcagent.oms.TMRemoteClientFactory.getCommunicatingClient(TMRemoteClientFactory.java:162)
at oracle.sysman.gcagent.util.clients.emdctlj.EmdCtlClientFactory.createEmdCtlClient(EmdCtlClientFactory.java:55)
at oracle.sysman.gcagent.clients.emdctlj.commands.EmdCtlAgentStatusCommand.execute(EmdCtlAgentStatusCommand.java:98)
at oracle.sysman.gcagent.clients.emdctlj.EmdCtlParsedCommandHandler.executeCommand(EmdCtlParsedCommandHandler.java:88)
at oracle.sysman.gcagent.clients.emdctlj.EmdCtl.parseAndExecute(EmdCtl.java:160)
at oracle.sysman.gcagent.clients.emdctlj.EmdCtl.main(EmdCtl.java:399)
Caused by: javax.net.ssl.SSLPeerUnverifiedException: peer not authenticated
at com.sun.net.ssl.internal.ssl.SSLSessionImpl.getPeerCertificateChain(SSLSessionImpl.java:401)
at oracle.sysman.gcagent.comm.http.BaseHttpsContext.verifyConnection(BaseHttpsContext.java:119)
at oracle.sysman.gcagent.comm.http.ClientConnection.verifySecureConnection(ClientConnection.java:854)
… 9 more

In emoms_pbs.log:
2014-03-06 00:49:28,887 [Job Critical Pool:JobWorker Step 14458741] WARN emSDK.comm setInstanceReadTimeout.10608 – unable to set
the instance read timeout: unable to connect to http server at https://***:3872/emd/main/. [peer not
authenticated]

In gcagent.log:
2014-03-06 00:40:55,826 [224:980F9148] INFO – attempting another heartbeat
2014-03-06 00:41:54,388 [230:GC.SysExecutor.3 (AgentSystemMonitorTask)] ERROR – 313.035 seconds have passed without any
incoming (status) requests; the HTTP listener is not functioning properly
2014-03-06 00:41:54,388 [230:EA402D23:GC.SysExecutor.3 (AgentSystemMonitorTask)] INFO – agent status is being changed to
ABORT_AGENT

OPERATION:
(1)emctl stop agent
(2)Edit the file emd.properties and change: AgentListenOnAllNICs=TRUE to AgentListenOnAllNICs=FALSE
This will start the Agent so that the HTTP listener listens only on the hostname and port mapping the Agent hostname.
(3)emctl start agent
(4)Resync the agent on OMS.

REFERENCE:
EM12c Cloud Console Agent: Agent Heartbeat Status “OMS is unreachable bad response” “ORA 20500 Multiple agents detected for” (Doc
ID 1586918.1)
EM 12c Emctl Start Agent Fails With Error :HTTP Listener failed at Startup (Doc ID 1513571.1)

Advertisements
This entry was posted in Oracle. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s