Regarding timezone setting of Enterprise Manager Control

hi all,
I m using Oracle 10g on linux .i have installed Oracle enterprise manager on my linux system. it worked successfully.but from so many days, i got a error while starting DBConsole.
"AGENT IS NOT RUNNING".The error arise due to time zone mismatch.i corrected my timezone
inspite that the agent is not successfully running.
the log file is here:
2008-03-24 04:42:44 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:42:50 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:1158): Connection refused (error = 111)
2008-03-24 04:43:03 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:07 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:11 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:15 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:19 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:22 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:26 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:30 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:34 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:38 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:42 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:45 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:49 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:53 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:43:56 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:00 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:04 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:08 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:12 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:16 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:18 Thread-4136380640 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 04:44:19 Thread-4136380640 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 04:44:20 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:23 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:27 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:31 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:35 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:39 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:42 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:46 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:50 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:54 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:44:58 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:02 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:05 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:09 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:13 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:17 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:21 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:25 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:28 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:32 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:36 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:40 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:44 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:48 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:52 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:55 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:45:59 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:03 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:07 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:11 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:14 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:18 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:22 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:26 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:30 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:34 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:37 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:41 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:45 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:49 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:53 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:46:57 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:01 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:05 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:09 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:13 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:16 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:20 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:24 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:28 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:32 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:36 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:40 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:43 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:47 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:51 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:55 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:47:59 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:03 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:07 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:10 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:14 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:18 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:21 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:24 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:28 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:32 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:36 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 04:48:40 Thread-4136380640 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 05:01:22 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 05:01:23 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 05:01:39 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 05:01:39 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 05:01:40 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 05:12:46 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 05:18:39 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 05:18:52 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 05:18:53 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 05:19:29 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 07:13:13 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 07:57:09 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 08:05:15 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 08:14:53 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 08:37:04 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-24 08:37:04 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 08:37:05 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-24 23:32:07 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 00:48:55 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 00:49:02 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-25 00:49:03 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-25 00:49:13 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 00:49:23 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 00:49:23 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 00:49:23 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 00:49:32 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-25 00:49:33 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-25 00:57:24 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 00:59:56 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 01:05:13 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
2008-03-25 01:05:24 Thread-16384
2008-03-25 01:05:25 Thread-16384 ERROR main: nmectl.c: nmectl_validateTZRegion, agentTZoffset =-240,and testTZoffset for US/Eastern:-300 do not match
2008-03-25 01:05:39 Thread-16384 WARN http: snmehl_connect: connect failed to (physicalstandby.abc.com:3938): Connection refused (error = 111)
can any one help me out!
thanx's in advance.......
bye
Message was edited by:
Rocky

Hi Rocky,
Try these links
Re: Time Zone Problem in Linux RedHat
Oracle 10g EM DB console Host Preferred Credentials for Windows
http://www.oracle.com/technology/obe/obe10gemgc_10203/patchwizard/patchwizard.htm
Maybe this will give you an idea about how to resolve this problem.
Regards
R....

Similar Messages

Bringing oralce vm for x86 server in enterprise manager control

Hello All,
Greetings of the day.
We have deployed oracle enterprise manager opscenter 11g on solaris x86 and deployed a proxy controller on the same machine.
Query: How to discover and bring into oracle enterprise manager control oracle VM x86 machine which is already built and alive.
My perception is to install oracle virtual management pack on proxy controller machine and oracle vm server. I have the binaries with me. I could not find a doc to install the same.
Quick response is much appreciated.
Regards,
Hameed

Hameed,
Your questions sounds like it is specific to Ops Center. As a side note, there is an Ops Center forum and MOS community here:
https://communities.oracle.com/portal/server.pt/community/oracle_enterprise_manager_ops_center/505
Enterprise Manager Ops Center
Ops Center 11g does not have any awareness of OVMx86. Oracle introduced support for OVMx86 into Ops Center 12c.
http://www.oracle.com/technetwork/oem/ops-center/oem-ops-center-188778.html
The way you accomplish this in Ops Center 12c is to discover a OVM Manager. Once you have an OVM Manager discovered, you can discover OVS hypervisors and connect them to the OVM Manager through Ops Center. Then they will appear in the Ops Center user interface and you will be able to control them from Ops Center.
You can also do this in Enterprise Manager Cloud Control 12c.
Thanks,
Mike

Oracle 10g Enterprise Manager Control for Database

Hi,
I have a question. I have installed Oracle 10g Application server and Database server. Now, I am able to start OEM for database using "emctl start dbconsole". And I am able to browse it on port 5500. But everytime it shows me database "orcl". I have two databases. So, what to do if I want to manage another database using OEM for databse control. I have checked ports.ini file and it shows me that OEM port for another database is 5501. But when I try to browse it, I am getting nothing. So, please guide me.
Thanks,
Sanket.

Sanket,
If you go to $ORACLE_HOME/install, you will see the file portlist.ini. If you open this file, you will see one or more entries in the format
Enterprise Manager Console HTTP Port <SID_NAME> = <PORT_NUMBER>
In my case, my SID, TEST is running on the port 5501, and therefore the following entry appears in ports.ini :
Enterprise Manager Console HTTP Port (TEST) = 5501
In order for this entry to be added automatically, I think you have to use the database configuration assistant (dbca) to create the database.
When I open the following location, http://127.0.0.1:5501/em/, in my browser I can see the enterprise management console for the SID. Similarly, the URL http://127.0.0.1:5500/em/ is the management console for another SID that is running on the same machine.
If you are using Linux, make sure that that 127.0.0.1, or the hostname (in the url) in the portlist.ini file is in the /etc/hosts* file.
Good Luck!
Regards,
Rudi

Problem in setting up Enterprise Manager in 11g version 2

Hello,
I am facing some problem in starting Oracle enterprise manager. Oracle EM Grid control is not installed.
OS = Linux x86_64
Oracle version = 11.2.0
Following is the output in while providing "set" command and TNS listener is running.
A__z='"*SHLVL'
BASH=/bin/bash
BASHOPTS=cmdhist:expand_aliases:extquote:force_fignore:hostcomplete:interactive_comments:progcomp:promptvars:sourcepath
BASH_ALIASES=()
BASH_ARGC=()
BASH_ARGV=()
BASH_CMDS=()
BASH_LINENO=()
BASH_SOURCE=()
BASH_VERSINFO=([0]="4" [1]="1" [2]="2" [3]="1" [4]="release" [5]="x86_64-redhat-linux-gnu")
BASH_VERSION='4.1.2(1)-release'
CLASSPATH=/opt/oracle/product/11.2.0/db_1/jlib:/opt/oracle/product/11.2.0/db_1/rdbms/jlib
COLUMNS=157
DIRSTACK=()
DISPLAY=local_host:0.0
EUID=502
GROUPS=()
G_BROKEN_FILENAMES=1
HISTCONTROL=ignoredups
HISTFILE=/opt/oracle/.bash_history
HISTFILESIZE=1000
HISTSIZE=1000
HOME=/opt/oracle
HOSTNAME=ariane
HOSTTYPE=x86_64
IFS=$' \t\n'
LANG=en_US.UTF-8
LD_LIBRARY_PATH=:/usr/openwin/lib:/usr/local/lib:/usr/local/lib:/usr/lib:/usr/lib64:/lib:/lib64:/opt/oracle/product/11.2.0/db_1/lib
LESSOPEN='|/usr/bin/lesspipe.sh %s'
LINES=46
LOGNAME=oracle
MACHTYPE=x86_64-redhat-linux-gnu
MAIL=/var/spool/mail/oracle
MAILCHECK=60
OLDPWD=/opt/oracle/product/11.2.0/db_1/jlib
OPTERR=1
OPTIND=1
ORACLE_BASE=/opt/oracle
ORACLE_DOC=/opt/oracle/product/11.2.0/db_1/doc
ORACLE_HOME=/opt/oracle/product/11.2.0/db_1
ORACLE_SID=SIDB
OSTYPE=linux-gnu
PATH=/bin:/usr/bin:/usr/ccs/bin:/usr/local/bin:/opt/bin:/opt/oracle/product/11.2.0/db_1/bin:/opt/oracle/orasql/SIDB:/opt/oracle/orarepl/SIDB/scripts/conf:/opt/oracle/orarepl/SIDB/scripts/monitor:/opt/oracle/backup/bin
PIPESTATUS=([0]="127")
PPID=41740
PS1='\s-\v\$ '
PS2='> '
PS4='+ '
PWD=/opt/oracle/product/11.2.0/db_1/bin
SHELL=/bin/ksh
SHELLOPTS=braceexpand:emacs:hashall:histexpand:history:interactive-comments:monitor
SHLVL=2
TERM=xterm
TZ=Asia/Kolkata
UID=502
USER=oracle
_=oracle/sysman/emd/targetIntg/agent/AgentTargetInstaller
*After providing the command "./emctl start dbconsole", I'm getting following error.*
Can't locate CompEMdbconsole.pm in @INC (@INC contains: %s_javapOracleHome%/sysman/admin/scripts %s_javapOracleHome%/bin /opt/oracle/product/11.2.0/db_1/perl/lib/5.10.0/x86_64-linux-thread-multi /opt/oracle/product/11.2.0/db_1/perl/lib/5.10.0 /opt/oracle/product/11.2.0/db_1/perl/lib /opt/oracle/product/11.2.0/db_1/perl/lib/site_perl/5.10.0/x86_64-linux-thread-multi /opt/oracle/product/11.2.0/db_1/perl/lib/site_perl/5.10.0 /opt/oracle/product/11.2.0/db_1/perl/lib/site_perl /opt/oracle/product/11.2.0/db_1/perl/libwww-perl/lib /opt/oracle/product/11.2.0/db_1/perl/ext/POSIX /opt/oracle/product/11.2.0/db_1/perl/URI /opt/oracle/product/11.2.0/db_1/perl/HTML_Parser /opt/oracle/product/11.2.0/db_1/perl/HTML-Parser/lib /opt/oracle/product/11.2.0/db_1/sysman/admin/scripts /opt/oracle/product/11.2.0/db_1/bin /opt/oracle/product/11.2.0/db_1/sysman/admin/scripts/Net-DNS-0.48/lib/ /opt/oracle/product/11.2.0/db_1/sysman/admin/scripts/libnet-1.19/ .) at /opt/oracle/product/11.2.0/db_1/bin/EmctlCommon.pm line 597.
*Running only "./emctl" provides :*
OC4J Configuration issue. /opt/oracle/product/11.2.0/db_1/sysman/j2ee not found.
*Running " ./emca -config dbcontrol db -repos recreate", gives the output*
"STARTED EMCA at Sep 26, 2012 1:07:55 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: SIDB
Exception in thread "main" java.lang.NoClassDefFoundError: oracle/sysman/emd/targetIntg/agent/AgentTargetInstaller
at oracle.sysman.emcp.target.TargetManager.getAgentTargetInstaller(TargetManager.java:1008)
at oracle.sysman.emcp.target.TargetManager.getLocalHost(TargetManager.java:1033)
at oracle.sysman.emcp.ParamsManager.getLocalHost(ParamsManager.java:1037)
at oracle.sysman.emcp.ParamsManager.getHost(ParamsManager.java:3020)
at oracle.sysman.emcp.DatabaseChecks.checkDbAvailabilityImpl(DatabaseChecks.java:118)
at oracle.sysman.emcp.DatabaseChecks.checkDbAvailability(DatabaseChecks.java:163)
at oracle.sysman.emcp.DatabaseChecks.getDbServiceName(DatabaseChecks.java:582)
at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1267)
at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:573)
at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:521)
Could anyone please let me know the corrective actions to be taken? Whether installing OEM Grid control is mandatory?
Thanks,
Deb

Hello,
Yes. Both are ruuning. Output of lsnrctl status :
LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 26-SEP-2012 13:32:36
Copyright (c) 1991, 2009, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=SIDB))
STATUS of the LISTENER
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 15-SEP-2012 19:58:20
Uptime 10 days 17 hr. 34 min. 16 sec
Trace Level off
Security ON: Password or Local OS Authentication
SNMP OFF
Listener Parameter File /opt/oracle/product/11.2.0/db_1/network/admin/listener.ora
Listener Log File /opt/oracle/diag/tnslsnr/ariane/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=SIDB)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=arian)(PORT=1521)))
Services Summary...
Service "SIDB" has 1 instance(s).
Instance "SIDB", status UNKNOWN, has 1 handler(s) for this service...
Service "SIDB.10.54.159.32" has 1 instance(s).
Instance "SIDB", status READY, has 1 handler(s) for this service...
The command completed successfully

Error Enterprise Manager configuration failed ( Oracle 10.2.0.4 )

Hi All,
I am getting an error at Completing Database Creation Step, regarding Starting Database Control. I have multiple databases on the same server but every time I am trying to create a new database through DBCA I am getting the same error again and again.
Database configuration Assistant: Warning
Enterprise manager configuration failed due to the following error-
Error updating E:\oracle\product\10.2.0\db_1\sysman\emd\targets.xml
Refer to log file at E:\oracle\product\10.2.0\db_1\cfgtoollogs\dbca\test1\emConfig.log for more details.
You can try configuring his database with enterprise Manager laterby manually running E:\oracle\product\10.2.0\db_1\bin\emca script.
Here are the logs of emConfig.log
Oct 15, 2010 11:02:06 AM oracle.sysman.emcp.EMConfig perform
SEVERE: Error starting Database Control
Refer to the log file at C:\oracle\product\10.2.0\db_1\cfgtoollogs\dbca\qa54b17\emConfig.log for more details.
Oct 15, 2010 11:02:06 AM oracle.sysman.emcp.EMConfig perform
CONFIG: Stack Trace:
oracle.sysman.emcp.exception.EMConfigException: Error starting Database Control
at oracle.sysman.emcp.EMDBPostConfig.performConfiguration(EMDBPostConfig.java:646)
at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:224)
at oracle.sysman.emcp.EMDBPostConfig.invoke(EMDBPostConfig.java:193)
at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:184)
at oracle.sysman.assistants.util.em.EMConfiguration.run(EMConfiguration.java:436)
at java.lang.Thread.run(Thread.java:595)
The Operating system that I am using is Windows Server 2008 Enterprise with Service Pack 1.
If anyone can explain me the reason why I am getting the Warning again and again.
Thanks & Regards
Deepak
Edited by: Deepak30539 on Oct 27, 2010 3:45 PM

I would suggest to create database without enterprise manager control option and once database is created successfully , you can manually configure OEM later on.
Regards
Rajesh

Unable to connect to Enterprise Manager

Hello:
I successfully installed 10g on my laptop. I was able to access the enterprise manager control panel without a problem. Today, I tried to access the control panel and I'm unable to connect. I'm receiving a Page Cannot Be Displayed screen.
I'm running Windows XP. I don't understand why it worked once and not now.
Can someone help me out? Thank you.

Can you confirm that the service OracleDBConsoleSID is running? Any errors in the event log?

Enterprise management console 10g

Where can I find instructions on how to set up enterprise management console 10g?
Does anyone have a link?

Hi,
enter emca (enterprise manager configuration assistent) at the commandline.
This will show you the options you have.
You can create a dbconsole and also reconfigure a dbconsole container with it.
Hope this helps,
Lutz

Please provide the patch set for Oracle Enterprise Manager Grid Control 10

Hi,
please provide the patch set for Oracle Enterprise Manager Grid Control 10.2.0.1 and 10.2.0.5 for AIX 5.3
patch set for Oracle Enterprise Manager Grid Control for 11.2.0.2 OS AIX 5.3
Thanks,
Vishal Hande.

user12009184 wrote:
Hi,
please provide the patch set for Oracle Enterprise Manager Grid Control 10.2.0.1 and 10.2.0.5 for AIX 5.3
patch set for Oracle Enterprise Manager Grid Control for 11.2.0.2 OS AIX 5.3
Thanks,
Vishal Hande.you must obtain all patches directly from
http://support.oracle.com

How to configure Enterprise Manager Database Control (EMDC) to make it work on 2 servers working (primary and standby) under DG rules

Hello everybody i use Oracle Database EE 11.2.0.4 with DG.
In those cases i need to get Enterprise Manager Database Control running against DB with no RAC and no DG i perform the following steps:
I Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and management objects:
DECLARE
CURSOR c1 IS
SELECT owner, synonym_name name
FROM dba_synonyms
WHERE table_owner = 'SYSMAN';
BEGIN
FOR r1 IN c1 LOOP
IF r1.owner = 'PUBLIC' THEN
EXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name;
ELSE
EXECUTE IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name;
END IF;
END LOOP;
END;
DROP USER mgmt_view CASCADE;
DROP ROLE mgmt_user;
DROP USER sysman CASCADE;
After that i run
emca -config dbcontrol db -repos recreate
But what should i do in cases i have 2 servers working (primary and standby) under DG rules?

Hi ,
It is not possible to monitor/administer a Logical or Physical Standby database, i.e Data Guard, using Enterprise Manager Database Control. This is primarily due to the fact that Database Control is designed to monitor 1 database and a Data Guard environment, by definition, includes more than 1 database.
If you attempt to run emca against a standby Database, you will get an error like (i.e. ORA-01219: database not open).
Database Control, can, of course, be used to monitor the current Primary database (with no ability to administer or monitor Data Guard related functionality). In such a case, when failover occurs Database Control must be reconfigured to run on the new Primary database using the commands detailed in Note 278100.1 How To Drop, Create And Recreate DB Control In A 10g Database, section C. Recreate/ReConfig DB Control, Option 2. Recreate the DB Control Configuration Files and Repository.
Enterprise Manager Grid Control or Cloud Control provides the functionality for viewing, monitoring, and administering primary and standby databases in a Data Guard configuration.
Reference: Is it Possible to Configure Database Control for a Logical or Physical Standby Database? (Doc ID 315116.1)
You can use EM 12c cloud control to monitor and manager Standby DB effectively
Ref to below link for details
Set Up and Manage Oracle Data Guard using Oracle Enterprise Manager Cloud Control 12c
Regards,
Rahul

Oracle VM and Oracle VM Template for Enterprise Manager Cloud Control 12c M

Hello!
After installation of *"Oracle VM 3.1.1 Media Pack v1 for x86_64 (64 bit)"* to bare hardware
can I install Oracle VM Template for Enterprise Manager Cloud Control 12c Media Pack ?
Is it the wrong plan ?
What to do if I need to set VLAN №1 ? (according note of installer I have to choose number between 2 and 4094 )
Thanks and regards,
Pavel
Edited by: Pavel on Jul 30, 2012 5:01 AM

Yes, you can install Oracle VM Manager, create a server pool with the one parent Oracle VM server in it, and then deploy the Oracle VM template in the pool. Once EM VM is up and running, you can register the same Oracle VM Manager with EM, to manage the pool.
In general, it is not recommended that you use the OVM server backend directly. But for bootstrapping the EM environment, you can also try the following:
Download the OVM Template on the Oracle VM server. From the OVM server terminal itself you can do "xm create" to spin a new virtual machine using the Oracle VM teamplate. Once the VM comes up, VNC into the VM and configure the EM OMS and agent.

The OMS is not set up for Enterprise Manager Security

Hi, I'm trying to add an agent to grid control and its not connecting with the management server because i cant secure it...
bash-2.05$ ../../bin/emctl secure agent <password>
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent is already stopped... Done.
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Failed.
The OMS is not set up for Enterprise Manager Security.
i have tried this on two seperate servers, both do the exact same thing. However, on my repository server where the OMS is housed, i can secure the agent no problem. Does anyone know what the problem could be? My OMS is on a Linux (SuSE 10.2) 32-bit machine.
heres the emdctl.trc on the agent machine:
2007-07-11 11:00:20 Thread-1 ERROR main: nmectla_agentctl: Error connecting to http://cbldb3:3872/emd/main/. Returning status code 1
2007-07-11 11:00:21 Thread-1 WARN http: snmehl_connect: connect failed to (cbldb3:3872): Connection refused (error = 239)
2007-07-11 11:00:21 Thread-1 ERROR main: nmectla_agentctl: Error connecting to http://cbldb3:3872/emd/main/. Returning status code 1
2007-07-11 11:00:21 Thread-1 WARN http: snmehl_connect: connect failed to (cbldb3:3872): Connection refused (error = 239)
2007-07-11 11:00:21 Thread-1 ERROR main: nmectla_agentctl: Error connecting to http://cbldb3:3872/emd/main/. Returning status code 1
2007-07-11 11:00:22 Thread-1 WARN http: snmehl_connect: connect failed to (cbldb3:3872): Connection refused (error = 239)
2007-07-11 11:00:22 Thread-1 ERROR main: nmectla_agentctl: Error connecting to http://cbldb3:3872/emd/main/. Returning status code 1
2007-07-11 11:05:10 Thread-1 WARN http: snmehl_connect: connect failed to (cbldb3:3872): Connection refused (error = 239)
2007-07-11 11:05:10 Thread-1 ERROR main: nmectla_agentctl: Error connecting to http://cbldb3:3872/emd/main/. Returning status code 1
2007-07-11 11:10:08 Thread-1 WARN http: snmehl_connect: connect failed to (cbldb3:3872): Connection refused (error = 239)
2007-07-11 11:10:08 Thread-1 ERROR main: nmectla_agentctl: Error connecting to http://cbldb3:3872/emd/main/. Returning status code 1
bash-2.05$ lsof | grep 3872
bash-2.05$
seems to be failing the connect but nothing is running on the port so i'm not sure why
Thanks in advance
Message was edited by:
user581869

some further information and hopefully someone can help me...
I went to the OMS binary folder (fmc45712:$OMS_HOME/bin) and executed the following commands...
$OMS_HOME/opmn/bin/opmnctl stopall
$OMS_HOME/bin/emctl stop oms
$OMS_HOME/bin/emctl secure oms
$OMS_HOME/bin/emctl start oms
$OMS_HOME/opmn/bin/opmnctl startall
then i go to $AGENT_HOME on the OMS machine (fmc45712:$AGENT_HOME/bin) and execute..
$AGENT_HOME/bin/emctl status agent -secure
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Checking the security status of the Agent at location set in /opt/oracle/OracleHomes/agent10g/sysman/config/emd.properties... Done.
Agent is secure at HTTPS Port 3872.
Checking the security status of the OMS at http://fmc45712:4889/em/upload/... Done.
OMS is secure on HTTPS Port 1159
I then to go the server i deployed the agent on that i want to get communicating wtih my OMS...
$AGENT_HOME/bin/emctl status agent -secure
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Checking the security status of the Agent at location set in /u101/em/agent10g/sysman/config/emd.properties... Done.
Agent is unsecure at HTTP Port 3872.
Checking the security status of the OMS at http://fmc45712:4889/em/upload/... Done.
OMS is running but has not been secured. No HTTPS Port available.
same command, different computer, but on the same network, and it just doesn't work. The OMS is on Linux x86 and the agent on the alternate computer is on HP-UX. If anyone has any help it'd be much appreciated.

Install Enterprise Manager Grid Control 11R1 Failed at OMS Configuration

Hello:
I have installed Oracle 11g (11.2.0.1) and WebLogic Server (WLS) 10.3.6.0 and currently I am in the process of installing Enterprise Manager Grid Control 11R1 on a Linux RedHat 5.8 and it fails at OMS Configuration.
I have read the following thread and they suggested to use WLS 10.3.2:
Trouble installing EM GC -- installer patch 9329357 fails
I was looking for WLS 10.3.2 in Oracle's website and I could not find it.
Any help would be greatly appreciated.
Here is the log regarding the error:
The patch has more than one Archive Action but there is no Make Action.
ApplySession applying interim patch '9367763' to OH '/dbs0/product/fmw/oms11g'
Running prerequisite checks...
You selected -local option, hence OPatch will patch the local system only.
Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
(Oracle Home = '/dbs0/product/fmw/oms11g')
Is the local system ready for patching? y
Y (auto-answered by -silent)
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '9367763' for restore. This might take a while...
Backing up files affected by the patch '9367763' for rollback. This might take a while...
Patching component oracle.ldap.rsf, 11.1.1.2.0...
Updating archive file "/dbs0/product/fmw/oms11g/lib/libldapclnt11.a" with "lib/libldapclnt11.a/gslu.o"
ApplySession adding interim patch '9367763' to inventory
Verifying the update...
Inventory check OK: Patch ID 9367763 is registered in Oracle Home inventory with proper meta-data.
Files check OK: Files from Patch ID 9367763 are present in Oracle Home.
Execution of 'sh /dbs0/product/fmw/oms11g/install/oneoffs/111010/9367763/custom/scripts/post -apply 9367763 ':
Return Code = 0
The local system has been patched and can be restarted.
OPatch succeeded.
This config tool has failed. Please re-run this config tool manually from another terminal as
<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/install/oneoffs/apply_NewOneoffs.pl <ORACLE_HOME> <oneoff_numbers>
Eg: /scratch/EM/agent10g/perl/bin/perl /scratch/EM/agent10g/install/oneoffs/apply_NewOneoffs.pl /scratch/EM/agent10g 5632264,5961654
Finished one-offs apply...
Deleting the files...
Finished deleting the above files...
Configuration assistant "OMS Oneoff Patch Application" Succeeded
Running Configuration assistant "Repository Configuration"
Calling the EMSCHEMA MANAGER: CREATE
Please check the Repository Configuration Assistant logs at: /dbs0/product/fmw/oms11g/sysman/log/schemamanager
The create is completed now running the MOS
Configuration assistant "Repository Configuration" Succeeded
Running Configuration assistant "MDS Schema Configuration"
Configuration assistant "MDS Schema Configuration" Succeeded
Running Configuration assistant "OCM EM Repository Instrumentation"
Configuration assistant "OCM EM Repository Instrumentation" Succeeded
Running Configuration assistant "OMS Configuration"
Executing the OMSCA command...
Check the OMS Configuration Assistant logs at: /dbs0/product/fmw/oms11g/cfgtoollogs/omsca
INFO: Required tool's Execution failed
Configuration assistant "OMS Configuration" Failed
INFO: ***Configuration Assistants Action END ***
*** The installation was Successful, but some configuration assistants were failed or cancelled or skipped. ***

Hello:
For some reason after selecting the Retry button it successfully passed the Add-on OMS Side Configuration. Now I am failing at the "Agent Configuration Assistant". Here's the agent log:
log4j:ERROR No appenders could be found for category (oracle.sysman.emas.sdk.discovery.discover.WeblogicTargetDiscovery).
log4j:ERROR Please initialize the log4j system properly.
Total Discovery time is :1675milliseconds.
INFO: oracle.sysman.top.agent:AddingToTargetsXml: WLS targets
INFO: oracle.sysman.top.agent:Adding /oracle/product/agent11g/sysman/install//oraclewls.out file to /oracle/product/agent11g
INFO: oracle.sysman.top.agent:addToTargetsXML:TargetInstaller added target file= /oracle/product/agent11g/sysman/install//oraclewls.out to /oracle/product/agent11g successfully.
INFO: oracle.sysman.top.agent:AgentPlugIn:perform:Starting Agent with startAgent=true
INFO: oracle.sysman.top.agent:Starting the agent
INFO: oracle.sysman.top.agent:Starting the agent...
INFO: oracle.sysman.top.agent:Executing Command: /oracle/product/agent11g/bin/emctl start agent
INFO: oracle.sysman.top.agent:Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
INFO: oracle.sysman.top.agent:Copyright (c) 1996, 2010 Oracle Corporation. Allrights reserved.
INFO: oracle.sysman.top.agent:Agent is already running
INFO: oracle.sysman.top.agent:Requested Operation Completed with Status = 0
INFO: oracle.sysman.top.agent:
The Management Agent Configuration Assistant has failed. The following failureswere recorded:
Securing of the agent failed.
INFO: oracle.sysman.top.agent:Internal PlugIn for {Micro Step state:step:2:configuration in CfmAggregateInstance: oracle.sysman.top.agent:11.1.0.1.0:common:family=CFM:oh=/oracle/product/agent11g:label=10} failed with an unhandled exception:
java.lang.Exception:
The Management Agent Configuration Assistant has failed. The following failureswere recorded:
Securing of the agent failed.
at oracle.sysman.emcp.agent.AgentPlugIn.startProcessing(AgentPlugIn.java:269)
at oracle.sysman.emcp.agent.AgentPlugIn.invoke(AgentPlugIn.java:243)
at oracle.sysman.emCfg.core.PerformMicroStep.runJavaClass(PerformMicroStep.java:540)
at oracle.sysman.emCfg.core.PerformMicroStep.executeMicroStep(PerformMicroStep.java:120)
at oracle.sysman.emCfg.core.ActionPerformer.performMicroStep(ActionPerformer.java:917)
at oracle.sysman.emCfg.core.ActionPerformer$Performer.run(ActionPerformer.java:1038)
INFO: oracle.sysman.top.agent:The plug-in Agent Configuration Assistant has failed its perform method
Any help would be greatly appreciated.
Thanks,
Orivares

Apply CPU /PSU patches through Enterprise Manager Grid Control.

How to apply PSU patches from 10.2.0.5 GRID Grid Control to my test/development/qa environment.
Are there any step by step documents availible. Did any one applied these patches using Oracle Enterprise Manager Grid control.

Please read
Oracle® Enterprise Manager Administrator's Guide for Software and Server Provisioning and Patching
10g Release 5 (10.2.0.5.0)
3 Infrastructure Requirements
http://download.oracle.com/docs/cd/B16240_01/doc/em.102/e14500/infrastructure_setup.htm#BABEIFBC
For the correct setup to do you patching.
Regards
Rob
http://oemgc.wordpress.com

Oracle Enterprise Manager 10g Database Control Release 10.2.0.3.0

Oracle Enterprise Manager 10g Database Control Release 10.2.0.3.0 is one hour behiend on AIX 5.3.
I have installed the new timezone version 4 already by oracle DST path database is good OEM main page is showing one hour behiend.
I have done every possible effort last thing may be i have to update java home i have 1.4 IBM java on the server.
Please help me in this. Thanks.

See the Metalink Note *Impact Document for Daylight Saving Time Shift for Enterprise Manager Grid Control [ID 417939.1]* Appendix B - FAQ - point 18
What is the impact of not patching the JDK on the OMS for 10g Grid Control?
If you do not patch the JDK on the OMS page refreshed times and possibly other times displayed in the console will be incorrect (they will be off by 1 hour) during an affected period.
Oracle strongly recommends that you do patch the OMS JDK but we are not aware of any data corruption in the repository nor of any impact on critical EM functionalities (such as severities, notifications and jobs) when the JDK is not patched.

Oracle Enterprise Manager 11g Database Control log file location

Any one knows where the log file is for Oracle Enterprise Manager 11g Database Control. I am trying to set up EUS proxy authentication and running into issues when trying to search proxy user in my DB. The search returns no results and I am not sure where to look for. Please not my setup does work for EUS with shared or exclusive schema. I need to use Oracle DB proxy authentication for my application and that would need a setup of EUS with proxy permissions so please advice if you know where the log file is for Oracle Enterprise Manager 11g Database Control or if there is any logging I can turn on to see what search parameters are passed from Oracle Enterprise Manager 11g Database Control to my DB by using DB audit etc.
Thanks,

Be patient...wait for report.
If after some time report does not appear, go to Advisor Central and find it there.
:p

Regarding timezone setting of Enterprise Manager Control

Similar Messages

Maybe you are looking for