Upgrade your OEM12c to OEM13c -WHY?

In this blog I  have shared my recent webinar on Upgrade to OEM13c  -WHY?”. In this video I have explained few important features with example {screenshot} of Oracle Enterprise Manager 13c. These explained features are the one which were either missing or have been updated with some additional stuff.

This Webinar was done for AIOUG-North India Chapter for their monthly tech meet. This video is also shared on our Youtube channel as well. You can also find videos of all our previous webinar held in this year and last year.

G+ Link: https://plus.google.com/+DeepakSharmaEMDBA/posts/R3SfsVKJ1zo

Youtube Link: https://youtu.be/9Det73a2ZaI

Do share your feedback as it will help me do the improvement in my future posts.

 

Regards

ADDKS

 

 

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/09/upgrade-your-oem12c-to-oem13c-why/
LinkedIn
Instagram

Silent Installation of Oracle 12C Agent on Linux Server

I know its very late but it was pending from my side since long. This is step by step silent installation of Oracle12c Agent on any linux machine. I have tried by best to make your job easy.

Please follow the below mentioned steps to Install Oracle 12c agent.


 

Step 1: Login to OEM server and then swtich to “oracle” user, using “sudo su – oracle“. Navigate to OMS home.

cd “/app/oracle/product/middleware/OMS12CR4/oms/bin”.

 

Step 2: Create a temporary directory {setup} under “tmp” where agent setup will be downloaded.

“mkdir -p /tmp/setup”

 

Step 3: Download Agent setup using below mentioned procedure.

Procedure is mentioned below:-

————————————————

[oracle@testdb1 bin]$ pwd

/app/oracle/product/middleware/OMS12CR4/oms/bin

[oracle@testdb1 bin]$ ./emcli login -username=sysman -password=formula1

Login successful

 

[oracle@testdb1 bin]$ ./emcli sync

Synchronized successfully

 

[oracle@testdb1 bin]$ ./emcli get_supported_platforms

———————————————–

Version = 12.1.0.3.0

Platform = Linux x86-64

———————————————–

Version = 12.1.0.4.0

Platform = Linux x86-64

———————————————–

Platforms list displayed successfully.

 

[oracle@testdb1 bin]$ ./emcli get_agentimage -destination=/tmp/setup -platform=”Linux x86-64″ -version=12.1.0.3.0

 

=== Partition Detail ===

Space free : 3 GB

Space required : 1 GB

Check the logs at /app/oracle/product/middleware/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2016-08-05_00-57-38-AM.log

Downloading /tmp/setup/12.1.0.3.0_AgentCore_226.zip

File saved as /tmp/ setup /12.1.0.3.0_AgentCore_226.zip

Downloading /tmp/ setup /12.1.0.3.0_PluginsOneoffs_226.zip

File saved as /tmp/ setup /12.1.0.3.0_PluginsOneoffs_226.zip

Downloading /tmp/ setup /unzip

File saved as /tmp/ setup /unzip

Agent Image Download completed successfully.

[oracle@testdb1 bin]$ pwd

================================================================================

Step 4:  Copy setup from OEMAP1 server to LOCAL machine where agent needs to be installed. You can do this using WINSCP or any other file transfer.

 

==================================================================================

 

Step 5:  Login to server as “oracle” user and create folder of Agent Installation.

mkdir – /app/oracle/product/agent12cr3

==================================================================================

 

Step 6:  Navigate to location where agent setup was copied and run the below mentioned command.

 

[oracle@testdb1 agent_sw]$ ./agentDeploy.sh AGENT_BASE_DIR=/app/oracle/product/agent12cr3 OMS_HOST=oemap1.test.com EM_UPLOAD_PORT=4904 AGENT_REGISTRATION_PASSWORD=formula123

 

Validating the OMS_HOST & EM_UPLOAD_PORT

Executing command : /app/oracle/product/agent12cr3/core/12.1.0.3.0/jdk/bin/java -classpath /app/oracle/product/agent12cr3/core/12.1.0.3.0/jlib/agentInstaller.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12cr3/core/12.1.0.3.0 /app/oracle/product/agent_sw /app/oracle/product/agent12cr3 -prereq

Validating oms host & port with url: http://testdb1.oii.test.com:4903/empbs/genwallet

Validating oms host & port with url: https://testdb1.oii.test.com:4903/empbs/genwallet

Return status:3-oms https port is passed

Unzipping the agentcoreimage.zip to /app/oracle/product/agent12cr3 ….

12.1.0.3.0_PluginsOneoffs_226.zip

Executing command : /app/oracle/product/agent_sw/unzip -o /app/oracle/product/agent_sw/12.1.0.3.0_PluginsOneoffs_226.zip -d /app/oracle/product/agent12cr3

Executing command : /app/oracle/product/agent12cr3/core/12.1.0.3.0/jdk/bin/java -classpath /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/OraInstaller.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/xmlparserv2.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/srvm.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/emCfg.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/jlib/agentInstaller.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/share.jar oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12cr3/core/12.1.0.3.0 /app/oracle/product/agent_sw /app/oracle/product/agent12cr3 /app/oracle/product/agent12cr3/agent_inst AGENT_BASE_DIR=/app/oracle/product/agent12cr3

 

Executing agent install prereqs…

Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -prereqchecker -silent -ignoreSysPrereqs -waitForCompletion  -prereqlogloc /app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy -entryPoint oracle.sysman.top.agent_Complete -detailedExitCodes PREREQ_CONFIG_LOCATION=/app/oracle/product/agent12cr3/core/12.1.0.3.0/prereqs  -J-DAGENT_BASE_DIR=/app/oracle/product/agent12cr3

Prereq Logs Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/prereq<timestamp>.log

Agent install prereqs completed successfully

 

Cloning the agent home…

Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12cr3/core/12.1.0.3.0   AGENT_BASE_DIR=/app/oracle/product/agent12cr3 AGENT_BASE_DIR=/app/oracle/product/agent12cr3 OMS_HOST=testdb1.oii.test.com EM_UPLOAD_PORT=4903 AGENT_REGISTRATION_PASSWORD=formula123 -noconfig  ORACLE_HOME_NAME=agent12c4 -force b_noUpgrade=true AGENT_PORT=-1

Clone Action Logs Location:/app/oracle/oraInventory//logs/cloneActions<timestamp>.log

Cloning of agent home completed successfully

 

Attaching sbin home…

Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -attachHome -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12cr3/sbin ORACLE_HOME_NAME=sbin12c4 -force

Attach Home Logs Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/AttachHome<timestamp>.log

Attach home for sbin home completed successfully.

 

Updating home dependencies…

Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST={/app/oracle/product/agent12cr3/sbin:/app/oracle/product/agent12cr3/core/12.1.0.3.0} -invPtrLoc /app/oracle/product/agent12cr3/core/12.1.0.3.0/oraInst.loc -force

Update Home Dependencies Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/UpdateHomeDeps<timestamp>.log

Update home dependency completed successfully.

 

Performing the agent configuration…

Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runConfig.sh ORACLE_HOME=/app/oracle/product/agent12cr3/core/12.1.0.3.0 RESPONSE_FILE=/app/oracle/product/agent12cr3/core/12.1.0.3.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true

Configuration Log Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/cfgfw/CfmLogger<timestamp>.log

Agent Configuration completed successfully

 

The following configuration scripts need to be executed as the “root” user.

#!/bin/sh

#Root script to run

/app/oracle/product/agent12cr3/core/12.1.0.3.0/root.sh

To execute the configuration scripts:

  1. Open a terminal window
  2. Log in as “root”
  3. Run the scripts

Agent Deployment Successful.

Agent deployment log location:

/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/agentDeploy_2016-08-05_01-06-08-AM.log

Agent deployment completed successfully.

 

==================================================================================

 

Step 7:  Secure Agent using below mentioned command.

 

[oracle@testdb1 agent_sw]$ cd /app/oracle/product/agent12cr3/agent_inst/bin/

[oracle@testdb1 bin]$ ./emctl secure agent

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Agent successfully stopped…   Done.

Securing agent…   Started.

Enter Agent Registration Password :

Agent successfully restarted…   Done.

EMD gensudoprops completed successfully

Securing agent…   Successful.

 

==================================================================================

 

Step 7:  Add internal targets existing on the server and upload.

[oracle@testdb1 bin]$ ./emctl config agent addinternaltargets

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

 

[oracle@testdb1 bin]$ ./emctl upload

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

—————————————————————

EMD upload completed successfully

[oracle@testdb1 bin]$

 

Thanks

ADDKS

 

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/08/silent-installation-of-oracle-12c-agent-on-linux-server/
LinkedIn
Instagram

OMS decided to shutdown the agent : EM_PLUGIN_MISMATCH_AND_AGENT_NOT_YET_MANAGED

Yesterday I came across an issue when I was installing Oracle Agent 12cR3 on my TEST  environment,  the installation ended with a new error message for me this time. It was for the first time in 3 years while working on Oracle Enterprise Manager I faced this Issue.

This was the error message:- ” ERROR: Agent Configuration Failed SEVERE: emctl start agent command has failed with status1

I have added the complete installation logs to make picture more clear.

[oracle@testdb1 linux_x64]$ ./agentDeploy.sh OMS_HOST=testdb1.oii.test.com EM_UPLOAD_PORT=4903 AGENT_BASE_DIR=/app/oracle/product/agent12c AGENT_REGISTRATION_PASSWORD=formula123

Validating the OMS_HOST & EM_UPLOAD_PORT
Executing command : /app/oracle/product/agent12c/core/12.1.0.4.0/jdk/bin/java -classpath /app/oracle/product/agent12c/core/12.1.0.4.0/jlib/agentInstaller.jar:/app/oracle/product/agent12c/core/12.1.0.4.0/oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12c/core/12.1.0.4.0 /app/oracle/product/agent_sw/linux_x64 /app/oracle/product/agent12c -prereq
Validating oms host & port with url: http://testdb1.oii.test.com:4903/empbs/genwallet
Validating oms host & port with url: https://testdb1.oii.test.com:4903/empbs/genwallet
Return status:3-oms https port is passed
Unzipping the agentcoreimage.zip to /app/oracle/product/agent12c ....
12.1.0.4.0_PluginsOneoffs_226.zip
Executing command : /app/oracle/product/agent_sw/linux_x64/unzip -o /app/oracle/product/agent_sw/linux_x64/12.1.0.4.0_PluginsOneoffs_226.zip -d /app/oracle/product/agent12c
Executing command : /app/oracle/product/agent12c/core/12.1.0.4.0/jdk/bin/java -classpath /app/oracle/product/agent12c/core/12.1.0.4.0/oui/jlib/OraInstaller.jar:/app/oracle/product/agent12c/core/12.1.0.4.0/oui/jlib/xmlparserv2.jar:/app/oracle/product/agent12c/core/12.1.0.4.0/oui/jlib/srvm.jar:/app/oracle/product/agent12c/core/12.1.0.4.0/oui/jlib/emCfg.jar:/app/oracle/product/agent12c/core/12.1.0.4.0/jlib/agentInstaller.jar:/app/oracle/product/agent12c/core/12.1.0.4.0/oui/jlib/share.jar oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12c/core/12.1.0.4.0 /app/oracle/product/agent_sw/linux_x64 /app/oracle/product/agent12c /app/oracle/product/agent12c/agent_inst AGENT_BASE_DIR=/app/oracle/product/agent12c
Executing agent install prereqs...
Executing command: /app/oracle/product/agent12c/core/12.1.0.4.0/oui/bin/runInstaller -debug -ignoreSysPrereqs   -prereqchecker -silent -ignoreSysPrereqs -waitForCompletion  -prereqlogloc /app/oracle/product/agent12c/core/12.1.0.4.0/cfgtoollogs/agentDeploy -entryPoint oracle.sysman.top.agent_Complete -detailedExitCodes PREREQ_CONFIG_LOCATION=/app/oracle/product/agent12c/core/12.1.0.4.0/prereqs  -J-DAGENT_BASE_DIR=/app/oracle/product/agent12c
Agent install prereqs completed successfully
Cloning the agent home...
Executing command: /app/oracle/product/agent12c/core/12.1.0.4.0/oui/bin/runInstaller -debug -ignoreSysPrereqs   -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12c/core/12.1.0.4.0   AGENT_BASE_DIR=/app/oracle/product/agent12c OMS_HOST=testdb1.oii.test.com EM_UPLOAD_PORT=4903 AGENT_BASE_DIR=/app/oracle/product/agent12c AGENT_REGISTRATION_PASSWORD=formula123 -noconfig  ORACLE_HOME_NAME=agent12c3 -force b_noUpgrade=true AGENT_PORT=-1
Cloning of agent home completed successfully
Attaching sbin home...
Executing command: /app/oracle/product/agent12c/core/12.1.0.4.0/oui/bin/runInstaller -debug -ignoreSysPrereqs   -attachHome -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12c/sbin ORACLE_HOME_NAME=sbin12c3 -force
Attach home for sbin home completed successfully.
Updating home dependencies...
Executing command: /app/oracle/product/agent12c/core/12.1.0.4.0/oui/bin/runInstaller -debug -ignoreSysPrereqs   -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST={/app/oracle/product/agent12c/sbin:/app/oracle/product/agent12c/core/12.1.0.4.0} -invPtrLoc /app/oracle/product/agent12c/core/12.1.0.4.0/oraInst.loc -force
Update home dependency completed successfully.
Executing command: /app/oracle/product/agent12c/core/12.1.0.4.0/oui/bin/runConfig.sh ORACLE_HOME=/app/oracle/product/agent12c/core/12.1.0.4.0 RESPONSE_FILE=/app/oracle/product/agent12c/core/12.1.0.4.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true

ERROR: Agent Configuration Failed SEVERE: emctl start agent command has failed with status1
Agent Deploy Log Location:/app/oracle/product/agent12c/core/12.1.0.4.0/cfgtoollogs/agentDeploy/agentDeploy_2016-08-04_22-40-59-PM.log

[oracle@testdb1 linux_x64]$

I checked the log file as mentioned in the last line and this I what I came across.

——————————————————————————————————————————————

INFO: Executing command: /app/oracle/product/agent12c/core/12.1.0.4.0/oui/bin/runConfig.sh ORACLE_HOME=/app/oracle/product/agent12c/core/12.1.0.4.0 RESPONSE_FILE=/app/oracle/product/agent12c/core/12.1.0.4.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true
INFO: Setting the invPtrLoc to /app/oracle/product/agent12c/core/12.1.0.4.0/oraInst.loc
INFO:
INFO: perform - mode is starting for action: configure
INFO:
INFO: ** Agent Port Check completed successfully.**
INFO: SEVERE: emctl start agent command has failed with status1
INFO: Follow the below steps to manually start the agent and add the host and agent targets:
INFO: 1. Start the agent by executing the command: /app/oracle/product/agent12c/agent_inst/bin/emctl start agent
INFO:  2. Add the targets by executing the command:/app/oracle/product/agent12c/agent_inst/bin/emctl config agent addinternaltargets.
INFO:
INFO: perform - mode finished for action: configure
INFO:
INFO: You can see the log file: /app/oracle/product/agent12c/core/12.1.0.4.0/cfgtoollogs/oui/configActions2016-08-04_10-41-54-PM.log
INFO: Plugin homes:
INFO: Plugin homes:
INFO: /app/oracle/product/agent12c/core/12.1.0.4.0/oui/bin/runConfig.sh ORACLE_HOME=/app/oracle/product/agent12c/core/12.1.0.4.0 RESPONSE_FILE=/app/oracle/product/agent12c/core/12.1.0.4.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true completed with status=3
SEVERE:
ERROR: Agent Configuration Failed
SEVERE:
ERROR: Agent Deployment Failed

 

I followed the steps as mentioned in the log file and tried to start the agent. It failed again, to be honest I was expecting that.   😉

My Concern:-

Same setup is working fine for my production OEM why it is failing again and again for Test OEM environment. I used the same setup to install and configure agent on multiple servers which were being monitored by my PRODUCTION OEM12c and they were installed and configured successfully without any errors.

So why now it was failing for OMS in my TEST OEM12c environment.

Then last option left for me was to explore the trace files and see what exactly is causing issue. So I started digging deeper in the log and trace files until I reached common error message in all of them.


 

My findings.

— EMState agent

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

----- Thu Aug  4 23:01:15 2016::27430::Auto tuning the agent at time Thu Aug  4 23:01:15 2016 -----
----- Thu Aug  4 23:01:16 2016::27430::Finished auto tuning the agent at time Thu Aug  4 23:01:16 2016 -----
----- Thu Aug  4 23:01:16 2016::27430::Launching the JVM with following options: -Xmx128M -server -Djava.security.egd=file:///dev/./urandom -Dsun.lang.ClassLoader.allowArraySyntax=true -XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC -XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops -----
----- Thu Aug  4 23:01:16 2016::27430::Agent Launched with PID 27484 at time Thu Aug  4 23:01:16 2016 -----
----- Thu Aug  4 23:01:16 2016::27484::Time elapsed between Launch of Watchdog process and execing EMAgent is 1 secs -----
----- Thu Aug  4 23:01:16 2016::27430::Previous Thrash State(-1,-1) -----
2016-08-04 23:01:16,750 [1:main] WARN - Missing filename for log handler 'wsm'
2016-08-04 23:01:16,757 [1:main] WARN - Missing filename for log handler 'opss'
2016-08-04 23:01:16,759 [1:main] WARN - Missing filename for log handler 'opsscfg'
OMS decided to shutdown the agent because of the following reason sent from OMS:  EM_PLUGIN_MISMATCH_AND_AGENT_NOT_YET_MANAGED
----- Thu Aug  4 23:01:29 2016::27430::Checking status of EMAgent : 27484 -----
----- Thu Aug  4 23:01:29 2016::27430::EMAgent exited at Thu Aug  4 23:01:29 2016 with return value 0. -----
----- Thu Aug  4 23:01:29 2016::27430::writeAbnormalExitTimestampToAgntStmp: exitCause=NORMAL : restartRequired=0 -----
----- Thu Aug  4 23:01:29 2016::27430::EMAgent was shutdown normally. -----
----- Thu Aug  4 23:01:29 2016::27430::Exiting watchdog loop
-----

gcagent.log

----------------------
2016-08-04 23:01:19,441 [49:905DEBE9] WARN - improper ping interval (EM_PING_NOTIF_RESPONSE: SHUTDOWN EM_PLUGIN_MISMATCH_AND_AGENT_NOT_YET_MANAGED)
2016-08-04 23:01:19,443 [57:CB968A7D:GC.SysExecutor.2 (ShutdownFromPing)] INFO - OMS decided to shutdown the agent because of the following reason sent from OMS:  EM_PLUGIN_MISMATCH_AND_AGENT_NOT_YET_MANAGED
2016-08-04 23:01:19,443 [1:3305B9] INFO - Agent is shutting down
2016-08-04 23:01:19,444 [49:905DEBE9] WARN - improper ping interval (EM_PING_NOTIF_RESPONSE: SHUTDOWN EM_PLUGIN_MISMATCH_AND_AGENT_NOT_YET_MANAGED)
2016-08-04 23:01:19,444 [1:3305B9] INFO - Invoking SHUTDOWN (1) on Internal Metrics
2016-08-04 23:01:19,444 [1:3305B9] INFO - Done: SHUTDOWN (1) on Internal Metrics
2016-08-04 23:01:19,444 [1:3305B9] INFO - Invoking SHUTDOWN on Miscellaneous
2016-08-04 23:01:19,444 [1:3305B9] INFO - Done: SHUTDOWN on Miscellaneous


I gave one try more but this time with proper procedure. So I followed my own document (blog) for “Silent Installation of Agent” and this time it worked and agent was installed and configured successfully.

What was the issue ? as OMS mentioned in the Error logs.  “ OMS decided to shutdown the agent because of the following reason sent from OMS:  EM_PLUGIN_MISMATCH_AND_AGENT_NOT_YET_MANAGED

SOLUTION:- 

The setup which I used earlier was downloaded from the production environment this was the compatible with EM Plugin in the production not with test environment and this was the reason why it was giving error again and again.

When I downloaded agent from the test environment and deployed it got configured successfully.

 

Procedure is mentioned below:-

————————————————

[oracle@testdb1 bin]$ pwd
/app/oracle/product/middleware/OMS12CR4/oms/bin
[oracle@testdb1 bin]$ ./emcli login -username=sysman -password=formula1
Login successful

[oracle@testdb1 bin]$ ./emcli sync
Synchronized successfully

[oracle@testdb1 bin]$ ./emcli get_supported_platforms
-----------------------------------------------
Version = 12.1.0.3.0
Platform = Linux x86-64
-----------------------------------------------
Version = 12.1.0.4.0
Platform = Linux x86-64
-----------------------------------------------
Platforms list displayed successfully.

[oracle@testdb1 bin]$ ./emcli get_agentimage -destination=/tmp/deepak -platform="Linux x86-64" -version=12.1.0.3.0

=== Partition Detail ===
Space free : 3 GB
Space required : 1 GB
Check the logs at /app/oracle/product/middleware/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2016-08-05_00-57-38-AM.log
Downloading /tmp/deepak/12.1.0.3.0_AgentCore_226.zip
File saved as /tmp/deepak/12.1.0.3.0_AgentCore_226.zip
Downloading /tmp/deepak/12.1.0.3.0_PluginsOneoffs_226.zip
File saved as /tmp/deepak/12.1.0.3.0_PluginsOneoffs_226.zip
Downloading /tmp/deepak/unzip
File saved as /tmp/deepak/unzip
Agent Image Download completed successfully.
[oracle@testdb1 bin]$ pwd

[oracle@testdb1 agent_sw]$ ./agentDeploy.sh AGENT_BASE_DIR=/app/oracle/product/agent12cr3 OMS_HOST=testdb1.oii.test.com EM_UPLOAD_PORT=4903 AGENT_REGISTRATION_PASSWORD=formula123

Validating the OMS_HOST & EM_UPLOAD_PORT
Executing command : /app/oracle/product/agent12cr3/core/12.1.0.3.0/jdk/bin/java -classpath /app/oracle/product/agent12cr3/core/12.1.0.3.0/jlib/agentInstaller.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12cr3/core/12.1.0.3.0 /app/oracle/product/agent_sw /app/oracle/product/agent12cr3 -prereq
Validating oms host & port with url: http://testdb1.oii.test.com:4903/empbs/genwallet
Validating oms host & port with url: https://testdb1.oii.test.com:4903/empbs/genwallet
Return status:3-oms https port is passed
Unzipping the agentcoreimage.zip to /app/oracle/product/agent12cr3 ....
12.1.0.3.0_PluginsOneoffs_226.zip
Executing command : /app/oracle/product/agent_sw/unzip -o /app/oracle/product/agent_sw/12.1.0.3.0_PluginsOneoffs_226.zip -d /app/oracle/product/agent12cr3
Executing command : /app/oracle/product/agent12cr3/core/12.1.0.3.0/jdk/bin/java -classpath /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/OraInstaller.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/xmlparserv2.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/srvm.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/emCfg.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/jlib/agentInstaller.jar:/app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/jlib/share.jar oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12cr3/core/12.1.0.3.0 /app/oracle/product/agent_sw /app/oracle/product/agent12cr3 /app/oracle/product/agent12cr3/agent_inst AGENT_BASE_DIR=/app/oracle/product/agent12cr3

Executing agent install prereqs...
Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -prereqchecker -silent -ignoreSysPrereqs -waitForCompletion  -prereqlogloc /app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy -entryPoint oracle.sysman.top.agent_Complete -detailedExitCodes PREREQ_CONFIG_LOCATION=/app/oracle/product/agent12cr3/core/12.1.0.3.0/prereqs  -J-DAGENT_BASE_DIR=/app/oracle/product/agent12cr3
Prereq Logs Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/prereq<timestamp>.log
Agent install prereqs completed successfully

Cloning the agent home...
Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12cr3/core/12.1.0.3.0   AGENT_BASE_DIR=/app/oracle/product/agent12cr3 AGENT_BASE_DIR=/app/oracle/product/agent12cr3 OMS_HOST=testdb1.oii.test.com EM_UPLOAD_PORT=4903 AGENT_REGISTRATION_PASSWORD=formula123 -noconfig  ORACLE_HOME_NAME=agent12c4 -force b_noUpgrade=true AGENT_PORT=-1
Clone Action Logs Location:/app/oracle/oraInventory//logs/cloneActions<timestamp>.log
Cloning of agent home completed successfully

Attaching sbin home...
Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -attachHome -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12cr3/sbin ORACLE_HOME_NAME=sbin12c4 -force
Attach Home Logs Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/AttachHome<timestamp>.log
Attach home for sbin home completed successfully.

Updating home dependencies...
Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runInstaller -debug   -ignoreSysPrereqs -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST={/app/oracle/product/agent12cr3/sbin:/app/oracle/product/agent12cr3/core/12.1.0.3.0} -invPtrLoc /app/oracle/product/agent12cr3/core/12.1.0.3.0/oraInst.loc -force
Update Home Dependencies Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/UpdateHomeDeps<timestamp>.log
Update home dependency completed successfully.

Performing the agent configuration...
Executing command: /app/oracle/product/agent12cr3/core/12.1.0.3.0/oui/bin/runConfig.sh ORACLE_HOME=/app/oracle/product/agent12cr3/core/12.1.0.3.0 RESPONSE_FILE=/app/oracle/product/agent12cr3/core/12.1.0.3.0/agent.rsp ACTION=configure MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true
Configuration Log Location:/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/cfgfw/CfmLogger<timestamp>.log
Agent Configuration completed successfully

The following configuration scripts need to be executed as the "root" user.
#!/bin/sh
#Root script to run
/app/oracle/product/agent12cr3/core/12.1.0.3.0/root.sh
To execute the configuration scripts:
  1. Open a terminal window
  2. Log in as "root"
  3. Run the scripts
Agent Deployment Successful.
Agent deployment log location:
/app/oracle/product/agent12cr3/core/12.1.0.3.0/cfgtoollogs/agentDeploy/agentDeploy_2016-08-05_01-06-08-AM.log
Agent deployment completed successfully.

[oracle@testdb1 agent_sw]$ cd /app/oracle/product/agent12cr3/agent_inst/bin/
[oracle@testdb1 bin]$ ./emctl secure agent
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
Agent successfully stopped...   Done.
Securing agent...   Started.
Enter Agent Registration Password :
Agent successfully restarted...   Done.
EMD gensudoprops completed successfully
Securing agent...   Successful.

[oracle@testdb1 bin]$ ./emctl config agent addinternaltargets
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

[oracle@testdb1 bin]$ ./emctl upload
Oracle Enterprise Manager Cloud Control 12c Release 3
Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
---------------------------------------------------------------
EMD upload completed successfully
[oracle@testdb1 bin]$

This time as well I learnt something new and I thought of sharing it with you so I did. Hope this will help you some time in future.

Thanks
ADDKS
Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/08/oms-decided-to-shutdown-the-agent-em_plugin_mismatch_and_agent_not_yet_managed/
LinkedIn
Instagram

Add Targets in OEM12c Declaratively specifying target monitoring properties.

In my last blog I have explained a step by step procedure, how we can add a target in Oracle Enterprise Manager 12c using “GUIDED” process. In this blog I have explained how we can add target in OEM12c using “DECLARATIVE” process. Let first understand what is the difference between “GUIDED” and “DECLARATIVE” process first.

In GUIDED process we have seen that agent on that host helps this process to discovers the target of particular type  that meets the selection criteria like in this case “Oracle Database, Listener and Automatic Storage Management”, once all these targets are discovered you just need to put the credentials and other monitoring configuration will be already filled during discovery.

However if we talk about the “DECLARATIVE” process, in this process we limit our input information and we want OEM to discover targets based on the limited information supplied to it. Lets see how this process works. Mentioned below are the steps:

Step 1: Navigate to the page “Add Targets Manually“.

image1

Step 2: Select method “Add Targets Declaratively by Specifying Target Monitoring Properties” and select the “Target Type” .

 

image4

Step 3: Select the Monitoring Agent. {The host on which the database instance/target (in this case) is located.}

image5

Step 4: Click on “Add Manually” to proceed further.

image6

Step 5: Add database instance properties, this includes not only the Monitoring configuration but also the “Target Name” and “Database System“.

image7

 Note:  The major difference between GUIDED Process and Declarative Process comes at this step. In Guided Process we just have to specify the password for monitoring user{DBSNMP}, rest of the information was filled automatically when Agent discovers the target. However while adding target by declaratively specifying the properties, we have to manually enter all these values.

Step 6: Test Connection, once you have filled all the values and make sure the connection is successful. Click NEXT to proceed further.

image8

Step 7: Review details and click on “Submit” to add this target.

image9

Now you can find the target listed under the “Targets -> Databases“.

 

Regards

ADDKS

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/07/add-targets-in-oem12c-declaratively-specifying-target-monitoring-properties/
LinkedIn
Instagram

Add Targets in OEM12c Using Guided Process

In this Blog I have explained step by step procedure to discover and add targets  on a HOST on which Agent is already installed.

Note: Oracle Agent installation is mandatory on the host for which you want to discover and push targets in OEM.

  • Navigate to the “Add Targets Manually” screen using the menu at the top-right of the screen (Setup > Add Target > Add Targets Manually).

image1

  • Select the “Add Targets using Guided Process” option, select the target types to be discovered (eg. lets say in this blog I have taken “Oracle Database, Listener and Automatic Storage Manager”) and click the “Add Using guided Discovery…” button.

image10

 

  • Under “Database Discovery: Search Criteria Agent” enter the host name on which target exists and agent in installed. Click the “Continue” button.

image11

 

  • Click on “Next” button.

image12

  • Click the “Configure” icon for any discovered targets and enter the required details.

image13

image14

  • Specifying Global Target Properties for Notifications and Administrations Groups and click “OK”.

image15

  • When all the configuration steps are complete, click the “Submit” button, followed by the “Save” button, then finally the “OK” button.

image9

You can now see the recently added “database Instance” target listed on the relevant target {Databases} screen (Targets > Databases).

 

Thanks

ADDKS

 

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/07/add-targets-in-oem12c-using-guided-process/
LinkedIn
Instagram

Say Hello! to Oracle Enterprise Manager 13c

In this blog I have shared one of my recent presentations with you on “Introduction to new features in OEM13c”. I delivered this session in one of our Tech-Day named as OTNYathra2016. It covers small Introduction of Oracle Enterprise Manager, Architecture of Enterprise Manager and What are all the components involved. As far as New & Enhanced features are concerned I have included “Infrastructure & Framework”,  “Enterprise Monitoring & Incident Management” and few “Database Management” features.
I have just started exploring this new release and will soon be posting more stuff on OEM13c.

 OEM13c_Intro_Blog

Thanks

Deepak Sharma

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/05/say-hello-to-oracle-enterprise-manager-13c/
LinkedIn
Instagram

OTNYathra2016 – My first Experience as Speaker

In this blog I have share my experience of OTNyathra2016 as a SPEAKER.

It was for the first time when beside the managing the entire event along with my Gurus Mr. Aman Sharma and Mr Navneet Upneja, I was there as a Speaker in the same event. Yes for the first time in a National Level Event I was nominated as Speaker and I had to deliver session on “Oracle Enterprise Manager 13c“.

Was I worried, YES a lot. It would sound weird but there were lots of ups and downs going on in my mind. I thought many  times to take my name back but then I took it as challenge and  thought no matter what I will speak. I knew some day I have to start so why not now.

Moreover it was for the first time being the Regional chapter of parental body AIOUG, AIOUG-North India Chapter took the responsibility for conducting this event. There was lot of pressure on our minds but yes with the hard work of entire team of North India Chapter our event was a GRAND SUCCESS. We broke the record of last 7 years with attendance of 130 delegates.

Special thanks to our Volunteers who helped us promoting this event on Social Media. Thank You so much guys. {Pavan Mishra, Vijay, Vinay and Anoop}

 

Back to experience as Speaker. 🙂

My session was at the last, when people are in mood of just rushing back to their homes. Few of them already left,  well I would say it was not actually a BAD start, there were around 20 people sitting in that room to attend my session. Before starting my session I had made my mind that I will not get confused, worried or shiver and I guess I succeeded in that. My both Gurus Mr Aman Sharma and Mr Navneet Upneja, came there in my session one by one.

The topic was new “Oracle Enterprise Manager 13c – New Features”, of course this release has a lot of new feature but I just took three domain and explain new or enhanced things in them. There were many cross questioning from the delegates some of which I was able to answer and some of them I did not know as I myself had not explored that feature. Overall it all went well and I would say my first experience was not that Bad to get upset.

My mentors Aman and Navneet both told me about some flaws and area of improvements, and I’ll  make sure not to make those mistakes again. I would like to thank both of them for there forever support and guidance.

 

Will be back soon with stuff on OEM13c, till then TC.

 

DSC_0315

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/05/otnyathra2016/
LinkedIn
Instagram

Service Test failed on OEM12c due to JAVA7 upgrade

 

Recently I faced issue with my Service Tests created for ENOVIA application. Java was upgraded from Java 1.6_24 to Java1.7_79 on our Enovia Servers.

Everytime when I perform verify Service test I get “Remote host closed connection during handshake– https://chapxxx.oii.xxx.com:9010/enovia/emxLogin.jsp” Error message .

Since then all the Service Test for ENOVIA were showing down but on the contrary all other Service tests for other applications are working fine.

Now OEM12c supports only till Java 6 Update 95, and this java upgrade was causing the Service Test to failed at every run. So the only workaround I was thinking was either upgrade my OEM to 13c which support JAVA or if possible lower the version of JAVA on ENOVIA servers.

What I did to resolve this Issue.

Issue:

Service test failed: “Remote host closed connection during handshake– https://chapxxx.oii.xxx.com:9010/enovia/emxLogin.jsp” Error message .

Cause:

Java upgrade from Java 1.6_24 to Java1.7_79

Resolution:

Steps for Implementing TLSv1 with OEM 12.1.0.4 to Fix Poodle Attack (Doc ID 2059368.1)

Steps to be followed:

  1. Applied recommended patches and update java on OMS to jdk 6 update 95.
  2. Update Java on the agent {Beacon Agent} host to jdk 6 update 95.
    1. [NOTE: This step is required only when the agents are monitoring TLSv1 enabled 12.1.3 middleware targets]
    2. Download the Patch 20418674 from Doc ID 1439822.1 All Java SE Downloads on MOS
    3. Follow the instructions as per the example given in Doc ID 1944044.1 EM12c: How to Use / Update JDK 1.6u Version on Agent.
  3. Configure the Agent to switch to TLSv1 as per the following document under the section “Oracle Management Agent”.
    1. Doc ID 1938799.1 CVE-2014-3566 Instructions to Mitigate the SSL v3.0 Vulnerability (aka “Poodle Attack”) in Oracle Enterprise Manager Grid / Cloud Control

Once you have performed all the steps make you your result look like this.

[oracle@hanoemxxx1 ~]$ openssl s_client -connect hanoemxxx1 .oii.xxx.com:3872 -tls1
CONNECTED(00000003)
depth=1 O = EnterpriseManager on hanoemxxx1 .oii.xxx.com, OU = EnterpriseManager on hanoemxxx1 .oii.xxx.com, L = EnterpriseManager on hanoemxxx1 .oii.xxx.com, ST = CA, C = US, CN = hanoemxxx1 .oii.xxx.com
verify error:num=19:self signed certificate in certificate chain
verify return:0

Certificate chain
0 s:/CN=hanoemxxx1 .oii.xxx.com
i:/O=EnterpriseManager on hanoemxxx1 .oii.xxx.com/OU=EnterpriseManager on hanoemxxx1 .oii.xxx.com/L=EnterpriseManager on hanoemxxx1 .oii.xxx.com/ST=CA/C=US/CN=hanoemxxx1 .oii.xxx.com
1 s:/O=EnterpriseManager on hanoemxxx1 .oii.xxx.com/OU=EnterpriseManager on hanoemxxx1 .oii.xxx.com/L=EnterpriseManager on hanoemxxx1 .oii.xxx.com/ST=CA/C=US/CN=hanoemxxx1 .oii.xxx.com
i:/O=EnterpriseManager on hanoemxxx1 .oii.xxx.com/OU=EnterpriseManager on hanoemxxx1 .oii.xxx.com/L=EnterpriseManager on hanoemxxx1 .oii.xxx.com/ST=CA/C=US/CN=hanoemxxx1 .oii.xxx.com

Server certificate
—–BEGIN CERTIFICATE—–
MIIC4DCCAkmgAwIBAgIJBBqdIBqYL6a0MA0GCSqGSIb3DQEBDQUAMIH5MTswOQYD
VQQKEzJFbnRlcnByaXNlTWFuYWdlciBvbiBoYW5vZW1hcDEub2lpLm9jZWFuZWVy
aW5nLmNvbTE7MDkGA1UECxMyRW50ZXJwcmlzZU1hbmFnZXIgb24gaGFub2VtYXAx
Lm9paS5vY2VhbmVlcmluZy5jb20xOzA5BgNVBAcTMkVudGVycHJpc2VNYW5hZ2Vy
IG9uIGhhbm9lbWFwMS5vaWkub2NlYW5lZXJpbmcuY29tMQswCQYDVQQIEwJDQTEL
MAkGA1UEBhMCVVMxJjAkBgNVBAMTHWhhbm9lbWFwMS5vaWkub2NlYW5lZXJpbmcu
Y29tMB4XDTE1MDUxMjIxMDA1MVoXDTI1MDUxMDIxMDA1MVowKDEmMCQGA1UEAxQd
aGFub2VtYXAxLm9paS5vY2VhbmVlcmluZy5jb20wgZ8wDQYJKoZIhvcNAQEBBQAD
gY0AMIGJAoGBAMZGbWxsmL+/HraSuevWybcBI2zY+3rgFOQTbRijL7pyO1jQV9bX
6NodoTBTrHp8l+s1+OWfy6SsBgz5EYwxBtsSMpmMd3zWy1b8hWeuZLBk77tPKYZL
JgMg2RY/QMjRe7l5i3rcdyNigpwBLR9VB4UI04Hhj7TDcHSzrR9QiNA3AgMBAAGj
QDA+MAwGA1UdEwEB/wQCMAAwDwYDVR0PAQH/BAUDAwfoADAdBgNVHQ4EFgQUJbLM
QJPLTX0/RlaijJ3qT05BGxowDQYJKoZIhvcNAQENBQADgYEAVmBOWk2rIZX5Ew6I
iTt1xQujqPk4EtJUPwy2iGhHhCeYvr4SDoqXD6A2za7hlqD79tENYLPZOWWHnw9H
ZihRye9vqQkQ1k+fqLyXlPCpVpUaYZnL+kjVJVGShx69Tv1Xjl4lobemcXidbIiY
mNYNa9USae70oZdlJ+63hYbcU8E=
—–END CERTIFICATE—–
subject=/CN=hanoemxxx1 .oii.xxx.com
issuer=/O=EnterpriseManager on hanoemxxx1 .oii.xxx.com/OU=EnterpriseManager on hanoemxxx1 .oii.xxx.com/L=EnterpriseManager on hanoemxxx1 .oii.xxx.com/ST=CA/C=US/CN=hanoemap1.oii.xxx.com

No client certificate CA names sent

SSL handshake has read 1815 bytes and written 345 bytes

New, TLSv1/SSLv3, Cipher is DES-CBC3-SHA
Server public key is 1024 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
Protocol : TLSv1
Cipher : DES-CBC3-SHA
Session-ID: 56FB0E61209B62179FB5E17A9DBF49D882EB5A5BB8F4E77ACC1753E5D8050467
Session-ID-ctx:
Master-Key: 3F6A0D03114C02914B757164F843DB8F2A8A17124445E2DB77ADFA5F21CB94A6012D92D5D771898C5FB3701F3058CD55
Key-Arg : None
Krb5 Principal: None
PSK identity: None
PSK identity hint: None
Start Time: 1459293793
Timeout : 7200 (sec)
Verify return code: 19 (self signed certificate in certificate chain)

Now re-run your Service Test, it application URL which was being monitored will show as Up and Running now.

 

Thanks

Deepak Sharma

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/04/service-test-failed-on-oem12c-due-to-java7-upgrade/
LinkedIn
Instagram

I’m Speaking @ OTN Yathra 2016

OTN Yatra Noida-2016 , Dated 01-May-2016,at BirlaSoft , H–9, Sector 63, NOIDA – 201306.
Speaker: Deepak Sharma, working as SR. Application Administrator with experience of 6+ years has worked on technologies like Oracle Enterprise Manager 11g Grid Contol, Oracle Enterprise Manager 12c Cloud Control, Oracle Enterprise Manager 13c, Oracle Database. He is currently working with “Oceaneering International Inc.” from last 4 years and before that he has been employee of “Bebo Technologies” for 2 years. He is Co-Founder of AIOUG-North India Chapter and core team member of AIOUG itself {http://www.aioug.org/aiougnichapter.php}. He has presented at various Oracle conferences organized by AIOUG i.e. OTNYathra and Monthly Tech Days etc.

He also shares his research and findings over his Oracle blog (https://deepaksharmaem12c.wordpress.com). He can be easily reachable at { sharma.deepak345@gmail.com} and {https://in.linkedin.com/in/dksharmaemdba}

There are the details. http://www.otnyathra.info/ ,
Click on Link to see the Agenda http://www.otnyathra.info/index.php…,
Click on link to register your self ( only Limited seats are available)http://www.meraevents.com/previewevent

Mishra Airy's photo.DSC_0568

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/04/im-speaking-otn-yathra-2016/
LinkedIn
Instagram

Monitoring Best Practices in OEM12c

This blog highlights some of the important features which if used effectively can help you to monitor you environment.

Best practice includes :

  • Metric Thresholds
  • Monitoring Templates
  • Administrations Groups
  • Template collections
  • Synchronization Schedules
  • Incident Management

To know more about them in details you can check my presentation from one of my sessions for AIOUG-North India Chapter.

Managing &Monitoring Best Practices

Thanks

DKSHARMA

Please follow and like us:
RSS
Follow by Email
Facebook
Google+
http://emdeepaksharma.com/2016/03/monitoring-best-practices-in-oem12c/
LinkedIn
Instagram