This content has been marked as final. Show 2 replies
Let me share some details on TZ issue. The bug that you are referring 14184260 is well known to us and is a JDK bug. The above bug is just a workaround for the jdk bug on only windows2003 hosts. Since Asia/Calcutta time zone has been deemed obsolete. It has been replaced by Asia/Kolkata. On windows, java returns a GMT offset timezone value and EMcode tries to find a supported timezone that maps to this GMT offset timezone. Failing to this it throw you the above TZ error. This all I can share with you on this forum if you are keen to know more pls log an SR and support will explain you in detail. We have fixed this bug for our next EM release
On Unix/Linux: set TZ=Asia/Calcutta in the environment and execute: "emctl resettz agent". Then follow the instructions that are displayed after the command executes and it will solve the problem.
For agent deploy on windows host we have documented the exact steps in MOS note 1530571.1. The note was just created a day back so it you cant see it yet, drop me an email and i can send u the steps. The steps are tried by another customer for agent deploy and works fine.
Now to your usecase, once we confirm that you are running into same TZ issue while doing the EM fresh install on win 2003, i need to verify the steps for fresh install and have some internal discussions /testing. I request you to open an Sr so that we can move forward and help you.