This error can occur due to one of the following reasons: 1. SSH port 22 is blocked by proxy / firewall on the Target machine 2. SSH is not running on the Target machine 3. SSH daemon is running on non-default port (other than 22) 1. Verify that the SSH port 22 is not blocked…
I ran into this “exception”: Agent has disabled full monitoring of this target. Only target Status is being monitored”: After a couple of researches, I’ve found that this is a Bug and therefor I needed to follow Doc ID 2207479.1. First you need to make sure that you’re patching the right ORACLE_HOME: export ORACLE_HOME=/u01/app/oracle/product/agent12cR5/core/12.1.0.5.0 [server1 25104978]$ $ORACLE_HOME/OPatch/opatch…
Well, as nothing is perfect, it happened to me too…..I had a “never seen before” failed EM12c upgrade on a test environment (fortunately :)) and this helped me to do it from scratch: Note: this is documented on Doc ID 1395423.1 (useful for one who has access, for those who don’t ….you can check it below)…
I followed the steps below: # backup the rule sets To make a copy, from the Setup menu, select Incidents, then select Incident Rules. On the Incident Rules – All Enterprise Rules page, in the table, select the out-of-box rule set you want to copy. Then, from the Actions menu, select Create Like Rule Set.…
./emcli create_credential_set -target_type=oracle_database -set_name=PERSONALset -supported_cred_types=DBCreds
A couple of months ago I got this error and below you can find the solution: I regenerated the file cwallet.sso as per KM Article # 1204133.1 and found below files that don’t have proper permissions. I set the permissions and started the services. jazn-data369504759xml.lck pki_data-966350115.lck.tmp
Some time ago I had this issue and below is what I did to fix it: sql>conn [email protected]_REP sql>exec emd_maintenance.submit_em_dbms_jobs; ./emctl stop agent ./emctl start agent
-rw-r—– 1 oracle oinstall 6571 Oct 22 07:32 emd.properties located in path like this: /u01/app/oracle/product/12.1.0.2/agent_inst/sysman/config/emd.properties increase the Xmx memory limit. Before this operation shutdown agent (emctl stop agent). And start him again after change. # # These are the optional Java flags for the agent # agentJavaDefines=-Xmx140M -XX:MaxPermSize=96M and increase Xmx parameter, like: agentJavaDefines=-Xmx256M -XX:MaxPermSize=96M
Sometimes we don’t want to have the EM12c agent started up after a server reboot. Here is how you can do something about it: mv /etc/oragchomelist /etc/oragchomelist_bak
$AGENT_HOME/bin/emctl stop agent rm -rf $AGENT_HOME/sysman/emd/recv rm -rf $AGENT_HOME/sysman/emd/collection rm -rf $AGENT_HOME/sysman/emd/state rm -rf $AGENT_HOME/sysman/emd/upload rm -rf $AGENT_HOME/sysman/emd/lastupld.xml $AGENT_HOME/bin/emctl clearstate agent $AGENT_HOME/bin/emctl start agent
