Re: Upgrade ASM and database to 12c - No GRID or RAC
Date: Thu, 26 May 2016 09:53:45 -0600
Message-ID: <CAJzM94ADDyveBUmjed8ZMmmy=wu3gUX-hCaB0J19t_mMPYKGng_at_mail.gmail.com>
Not sure why this worked, but we finally were able to upgrade ASM and then the database. We chose the option to automatically run the configuration scripts using sudo to the oracle user. ASM upgrade went through without a hitch. Worked well on our test system, but we didn't know the password for the oracle user on our secure system. Had to go through an approval process to get the password long enough to perform the upgrade.
Thanks for all the suggestions and advice.
Sandy
On Fri, May 13, 2016 at 10:57 AM, Sandra Becker <sbecker6925_at_gmail.com> wrote:
> Since I didn't have authorization to apply the latest PSU, it wasn't done
> (long, drawn-out process here). We did check the logs. No errors in the
> asm alert log. We know the last line in the roothas log was "asmca
> -silent -upgradeLocalASM". While tailing the roothas log, we pressed the
> <Enter> key a couple of times. The log shows our null "response" and then
> throws the error about a null response. We never see a prompt on the
> screen so we don't know what it's looking for.
>
> Still no useful response from Oracle, but they say they're working on it.
> I've been given a POC server with the same os, size, etc. and I'll be
> setting it up with ASM and a single-instance database, no GRID or RAC.
> Hopefully, I can work out and document the correct steps so we can get the
> ASM and databases upgraded before we miss our SLA. No one on the current
> team knows why it was set up this way. Seems the person who set it up
> passed away so we can't contact them either.
>
> Thanks for the suggestions. Very good information Andy.
>
> Sandy
>
> Sandy
>
> On Thu, May 12, 2016 at 4:18 PM, Andy Colvin <acolvin_at_gmail.com> wrote:
>
>> The rootupgrade.sh script should create a log file in
>> $GRID_HOME/cfgtoollogs/crsconfig/roothas_<timestamp>.log. That will most
>> likely tell you what was running and where the error lies. It's also
>> worthwhile to check the ASM alert log to see if it threw any specific
>> errors.
>>
>> One question - did you apply the latest GI PSU to the home before running
>> rootupgrade.sh? Normally, the procedure that I follow when upgrading GI is:
>>
>> - Apply latest PSU to the old GI home
>> - Install the new home with ./runInstaller
>> - When the files have been installed and the screen pops up telling
>> you to run rootupgrade.sh, install the latest GI PSU
>> - Run rootupgrade.sh
>> - After rootupgrade.sh completes, click the ok button on the window
>> - Let the installer finish the upgrade
>>
>> Note that the PSU on the new home needs to be installed manually, rather
>> than using opatch auto. This is because there isn't anything running out
>> of the home. MOS note #1591616.1 includes the order that you should apply
>> the various patches in:
>>
>> $ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local
>> <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%OCW TRACKING BUG%
>> $ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local
>> <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%ACFS TRACKING BUG%
>> $ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local
>> <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%DBWLM TRACKING BUG%
>> $ <GI_HOME>/OPatch/opatch apply -oh <GI_HOME> -local
>> <UNZIPPED_PATCH_LOCATION>/%BUGNO%/%RDBMS PSU TRACKING BUG%
>>
>> Thanks,
>>
>> Andy
>>
>> On Thu, May 12, 2016 at 2:51 PM, Sandra Becker <sbecker6925_at_gmail.com>
>> wrote:
>>
>>> We have an SR open with Oracle, but so far they haven't come back with
>>> anything useful.
>>>
>>> Sandy
>>>
>>> On Tue, May 10, 2016 at 8:17 PM, Andrew Kerber <andrew.kerber_at_gmail.com>
>>> wrote:
>>>
>>>> open an SR with Oracle.
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On May 10, 2016, at 5:12 PM, Sandra Becker <sbecker6925_at_gmail.com>
>>>> wrote:
>>>>
>>>> Current environment:
>>>>
>>>> - Oracle EE 11.2.0.4
>>>> - Linux x86-64
>>>> - ASM 11.2.0.4
>>>>
>>>> We have several environments that were set up as single-instance
>>>> databases using ASM, no GRID or RAC. We have been unsuccessful in trying
>>>> to upgrade ASM to 12.1.0.2. We have not attempted to upgrade the databases
>>>> since we were told that ASM must be upgraded to 12c first. Steps we have
>>>> taken:
>>>>
>>>> - unzip the grid files
>>>> - unset variables like ORACLE_HOME, ORA_CRS_HOME, etc.
>>>> - from the unzipped location, kick off runInstaller
>>>> - execute the rootupgrade.sh script
>>>>
>>>> The last step is where we have problems. The last entry in the log is
>>>> for "asmca -silent -upgradeLocalASM". After a couple of hours (had a
>>>> meeting in between), we just pressed the <Enter> key a few times to see if
>>>> it was waiting for something. Apparently, it was prompting for something,
>>>> but no prompts appeared on the screen so we have no idea what we should
>>>> have answered to the prompts. The log did show one prompt for "Enter
>>>> password". We did verify that the ASMSNMP user was in there and had the
>>>> sysdba privilege. We verified that the orapw+ASM password in the 11g OHome
>>>> was correct for SYS and ASMSNMP.
>>>>
>>>> Can someone point us to documentation or a step-by-step guide that will
>>>> guide us in upgrading this kind of environment? Unfortunately, this is a
>>>> secure system so I am unable to supply any logs.
>>>> Thank you for any suggestions and guidance.
>>>> --
>>>> Sandy B.
>>>>
>>>>
>>>
>>>
>>> --
>>> Sandy B.
>>>
>>>
>>
>
>
> --
> Sandy B.
>
>
-- Sandy B. -- http://www.freelists.org/webpage/oracle-lReceived on Thu May 26 2016 - 17:53:45 CEST