ORACLE EM DBA

Problems, Solutions, Test Cases from my professional and personal experience in technologies like Oracle Enterprise Manager 13 c,Oracle Enterprise Manager 12c, Oracle Configuration Manager and some other stuff.

Month: November 2014

Agent12c startup failed “A service specific error occurred: 2” {Common Error}

Hi All,

I was recently working on some issue, where my agent12c service which was up and running fine from last month suddenly failed to startup after the maintenance activity which took place at my company.
When i tried to startup agent using “emctl start agent” it failed and I was returned with error message:

Agent Service could not be started
A service specific error occurred: 2

Digging deep into the log files, I came across that change in the time zone of my server during the maintenance activity led to this issue. Due to change in the timezone there was mis-match in the current system timezone and the one mentioned in the emd.properties file.

Below mentioned are some of the log which I captured from the log files like {agabend.log, Oracleagent12c2Agentsrvc.log etc} :

— EMState agent
—– Fri Nov 21 21:29:23 2014::2940::Mismatch detected between timezone in env (America/New_York) and in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties (America/Chicago). Forcing value to latter.. —–
—– Fri Nov 21 21:29:23 2014::2940::The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository. —–
— EMState agent
—– Mon Nov 24 10:15:48 2014::3496::Mismatch detected between timezone in env (America/New_York) and in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties (America/Chicago). Forcing value to latter.. —–
—– Mon Nov 24 10:15:48 2014::3496::The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository. —–
— EMState agent
—– Mon Nov 24 10:16:49 2014::768::Mismatch detected between timezone in env (America/New_York) and in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties (America/Chicago). Forcing value to latter.. —–
—– Mon Nov 24 10:16:49 2014::768::The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository. —–
— EMState agent
—– Mon Nov 24 10:38:21 2014::3724::Mismatch detected between timezone in env (America/New_York) and in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties (America/Chicago). Forcing value to latter.. —–
—– Mon Nov 24 10:38:21 2014::3724::The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository. —–

The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository.
The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository.
The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository.
The agentTZRegion value in D:\app\oracle\product\agent\agent_inst/sysman/config/emd.properties is not in agreement with what agent thinks it should be.Please verify your environment to make sure that TZ setting has not changed since the last start of the agent.
If you modified the timezone setting in the environment, please stop the agent and exectute ’emctl resetTZ agent’ and also execute the script mgmt_target.set_agent_tzrgn(, ) to get the value propagated to repository.

RESOLUTION:
Changing the timezone in emd.properties file to the current timezone helped me out. After making these changes Agent was started successfully.

This was the quick update from my recent issues which I faced. Will post more day by day.

Thanks
Deepak

“Partial Blackout – Stop Failed” in EM12c

I have created this document explaining how to overcome error reporting “Partial Blackout – Stop Failed”. This is a step by step document to clear blackout successfully.Partial Blackout – Stop Failed

Sangam14, “AIOUG-NIC hardwork, 771 people acknowledged”

Just came back yesterday from Sangam 14, well this was the first time I went to such event and it was surprise for me and other founders of our NIC of AIOUG for being rewarded for our hardwork in front of more than 700 people.

I got chance to meet great speakers sharing their knowledge and their experiences, well this was first time I felt that great people like “Murli, Satyendra, PS Jankiram, Vijay Sehgal and many more..”

It was wonderful experience meeting few EM experts like Gagan Chawla, Nilesh Agrawal, Jim, Bhavin Desai, I shared my experience and discussed issue I had come across and listen their thoughts as well..

Last but not the least this event ended with inspiring speech from Dr. Rajdeep Manwani, sharing his experience and motivating us with speech.

Soon will share and write something new from my experience. Till then take care..

© 2017 ORACLE EM DBA

Theme by Anders NorenUp ↑