Re: Upgrade EM from 12.1.0.3 to 12.1.0.5 - emkey issues
Date: Thu, 3 Mar 2016 15:26:51 -0800
Message-ID: <CAKsxbLp9dqzGfjv5x5DpGm5fnaAKFRFsRJPMhjnK3=eEz7_EZw_at_mail.gmail.com>
Ok thanks I'll take your word for it and sit back and relax.
On Thu, Mar 3, 2016 at 3:20 PM, Kellyn Pot'Vin-Gorman <dbakevlar_at_gmail.com> wrote:
> I actually blogged about this, as it annoys me, too. It is running the
> upgrade. There are some serious changes to the sysman schema and it TAKES
> a LONG time. Think of that percentage window like Microsoft window for
> completion. Go get a coffee and relax...it's going to be awhile. I'm
> about to take on an upgrade for one of our premier customers where they
> shut off their rollup jobs on raw metric data a year ago and I'm not
> looking forward to that step for 13c. My estimates are sitting at 72hrs,
> but yours may be upwards of about 3-4 hrs for the upgrade to complete,
> easily. I know Courtney had one that took a very long time, too.
>
> Sorry, wish I had a better answer....:(
>
> Kellyn
>
>
>
> [image: Kellyn Pot'Vin on about.me]
>
> Kellyn Pot'Vin-Gorman
> about.me/dbakevlar
> <http://about.me/dbakevlar>
>
> On Thu, Mar 3, 2016 at 4:09 PM, Jeff Chirco <backseatdba_at_gmail.com> wrote:
>
>> Maybe you can answer one last question. The upgrade process is stuck at
>> 62% on the Repository Upgrade. The log keeps repeating this:
>> "INFO: oracle.sysman.top.oms:Still Running..."
>>
>> What does that mean?
>>
>> On Thu, Mar 3, 2016 at 3:05 PM, Jeff Chirco <backseatdba_at_gmail.com>
>> wrote:
>>
>>> Yeah they usually are pretty good. I just wish the database support team
>>> was as fast as the EM support.
>>>
>>> On Thu, Mar 3, 2016 at 3:02 PM, Kellyn Pot'Vin-Gorman <
>>> dbakevlar_at_gmail.com> wrote:
>>>
>>>> Glad to hear they got you an answer and got it to you quick! :)
>>>>
>>>> Kellyn
>>>>
>>>>
>>>>
>>>> [image: Kellyn Pot'Vin on about.me]
>>>>
>>>> Kellyn Pot'Vin-Gorman
>>>> about.me/dbakevlar
>>>> <http://about.me/dbakevlar>
>>>>
>>>> On Thu, Mar 3, 2016 at 3:31 PM, Jeff Chirco <backseatdba_at_gmail.com>
>>>> wrote:
>>>>
>>>>> Hi Kellyn yeah tested the sysman connection and the weblogic. I ended
>>>>> up opening a SR and they actually got back to me pretty quickly. They
>>>>> suggested I just run
>>>>> All worked
>>>>> $<OMS_HOME>/bin/emctl config emkey -copy_to_repos [-sysman_pwd
>>>>> <sysman_pwd>]
>>>>> $<OMS_HOME>/bin/emctl status emkey
>>>>>
>>>>> All worked
>>>>>
>>>>> On Thu, Mar 3, 2016 at 1:45 PM, Kellyn Pot'Vin-Gorman <
>>>>> dbakevlar_at_gmail.com> wrote:
>>>>>
>>>>>> Hi Jeff,
>>>>>> Please verify that you can connect to each the Repository and the
>>>>>> Weblogic console with the passwords you believe are correct.
>>>>>> The information for the weblogic console is included in the following
>>>>>> command:
>>>>>> ./emctl status oms -details
>>>>>>
>>>>>> Ensure that you're able to connect to the OMR with the password via
>>>>>> SQL Plus using a tns connection, (i.e. the listener must be up...)
>>>>>> And make sure that all environment variables are set correctly for
>>>>>> homes and sid.
>>>>>>
>>>>>> Hope this helps!
>>>>>> Kellyn
>>>>>>
>>>>>>
>>>>>>
>>>>>> [image: Kellyn Pot'Vin on about.me]
>>>>>>
>>>>>> Kellyn Pot'Vin-Gorman
>>>>>> about.me/dbakevlar
>>>>>> <http://about.me/dbakevlar>
>>>>>>
>>>>>> On Thu, Mar 3, 2016 at 1:03 PM, Jeff Chirco <backseatdba_at_gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Ok after I opend cmd as Administrator and ran the command it
>>>>>>> starting writing to the secure.log file.
>>>>>>> Here is the message after running the command
>>>>>>>
>>>>>>> Oracle Enterprise Manager Cloud Control 12c Release 3
>>>>>>> Copyright (c) 1996, 2013 Oracle Corporation. All rights reserved.
>>>>>>> Enter Admin User's Password :
>>>>>>> Error occurred. Check the log
>>>>>>> C:/Oracle/EM/gc_inst/em/EMGC_OMS1\sysman\log\secur
>>>>>>> e.log
>>>>>>>
>>>>>>> And here is the contents of secure.log file.
>>>>>>> 2016-03-03 12:00:35,287 [main] ERROR oms.EMKeyCmds logp.251 - Failed
>>>>>>> to get connection to repos : IO Error: SO Exception was generated
>>>>>>> java.sql.SQLRecoverableException: IO Error: SO Exception was
>>>>>>> generated
>>>>>>> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:458)
>>>>>>> at
>>>>>>> oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:546)
>>>>>>>
>>>>>>> at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:236)
>>>>>>> at
>>>>>>> oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:32)
>>>>>>>
>>>>>>> at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:521)
>>>>>>> at java.sql.DriverManager.getConnection(DriverManager.java:582)
>>>>>>> at java.sql.DriverManager.getConnection(DriverManager.java:154)
>>>>>>> at
>>>>>>> oracle.sysman.emctl.config.oms.EMKeyCmds.getReposConnection(EMKeyCmds.java:468)
>>>>>>>
>>>>>>> at
>>>>>>> oracle.sysman.emctl.config.oms.EMKeyBRCmds.processEmKeyBRCmd(EMKeyBRCmds.java:239)
>>>>>>>
>>>>>>> at
>>>>>>> oracle.sysman.emctl.config.oms.EMKeyBRCmds.main(EMKeyBRCmds.java:293)
>>>>>>>
>>>>>>> Caused by: oracle.net.ns.NetException: SO Exception was generated
>>>>>>> at
>>>>>>> oracle.net.resolver.AddrResolution.resolveAddrTree(AddrResolution.java:629)
>>>>>>>
>>>>>>> at
>>>>>>> oracle.net.resolver.AddrResolution.resolveAndExecute(AddrResolution.java:423)
>>>>>>>
>>>>>>> at oracle.net.ns.NSProtocol.establishConnection(NSProtocol.java:687)
>>>>>>>
>>>>>>> at oracle.net.ns.NSProtocol.connect(NSProtocol.java:247)
>>>>>>> at oracle.jdbc.driver.T4CConnection.connect(T4CConnection.java:1102)
>>>>>>>
>>>>>>> at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:320)
>>>>>>> ... 9 more
>>>>>>> 2016-03-03 12:00:35,287 [main] ERROR oms.EMKeyBRCmds logp.251 -
>>>>>>> Either Sysman password is invalid or there was a problem in connecting to
>>>>>>> the DB
>>>>>>> java.sql.SQLException: Either Sysman password is invalid or there
>>>>>>> was a problem in connecting to the DB
>>>>>>> at
>>>>>>> oracle.sysman.emctl.config.oms.EMKeyCmds.getReposConnection(EMKeyCmds.java:479)
>>>>>>>
>>>>>>> at
>>>>>>> oracle.sysman.emctl.config.oms.EMKeyBRCmds.processEmKeyBRCmd(EMKeyBRCmds.java:239)
>>>>>>>
>>>>>>> at
>>>>>>> oracle.sysman.emctl.config.oms.EMKeyBRCmds.main(EMKeyBRCmds.java:293)
>>>>>>>
>>>>>>>
>>>>>>> On Thu, Mar 3, 2016 at 10:43 AM, Jeff Chirco <backseatdba_at_gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I am trying to upgrade my EM from 12.1.0.3 to 12.1.0.5 but during
>>>>>>>> the upgrade processes a prerequisite comes up about emkey needs to be
>>>>>>>> copied to the repository. I found related topic in the upgrade guide and
>>>>>>>> it says to run this.
>>>>>>>>
>>>>>>>>
>>>>>>>> $<OMS_HOME>/bin/emctl config emkey -copy_to_repos_from_file
>>>>>>>> -repos_conndesc '"<conndesc>"' -repos_user <username> [-repos_pwd <pwd>]
>>>>>>>> -emkey_file <OMS_HOME>/sysman/config/emkey.ora
>>>>>>>>
>>>>>>>>
>>>>>>>> Which I do but it is asking for an Admin password in addition to
>>>>>>>> the sysman password. I have the sysman password and I believe the Admin
>>>>>>>> password it is refering to is the WebLogic admin account which I have as
>>>>>>>> well. But errors out and tells me to check a log file which is not even
>>>>>>>> updated.
>>>>>>>>
>>>>>>>> My EM is running on Windows Server 2008 R2 64bit
>>>>>>>> I am stuck and don't know what to do. Any suggestions?
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Jeff
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-- http://www.freelists.org/webpage/oracle-lReceived on Fri Mar 04 2016 - 00:26:51 CET