Upgrade of ASM from 11.2.0.4 to 12.1.0.2 failing - no GRID on this server

From: Sandra Becker <sbecker6925_at_gmail.com>
Date: Tue, 2 Aug 2016 14:27:46 -0600
Message-ID: <CAJzM94BN2xwvvXJm5f2m0Yj1N2BvXf=dyxDoPNnO0ELxb2iHgQ_at_mail.gmail.com>



ASM: 11.2.0.4, no interim patches
Red Hat Linux: Ver 5.11

We have three database servers that have only ASM installed, no GRID. We have been trying to upgrade ASM to 12.1.0.2 without any success. All the databases and ASM were down before we started runInstaller. The process always stops when running the configuration script, rootupgrade.sh. We have tried the following options:

  • Run the script manually when prompted - stops progressing at 81% complete; waited 3 hours before we killed it.
  • Check "Automatically run configuration scripts" with the sudo as oracle option; after about 90 minutes it fails with the following:

[image: Inline image 1]

*Full text of "Details":*

Cause - Installer is unable to connect to a node for executing the script using specified configuration method. Action - Review the log file '/local/cots/oracle/oraInventory/logs/installActions2016-08-02_02-48-26PM.log' for further details. More Details

Exception details - PRCC-1021 : One or more of the submitted commands did not execute successfully.

PRCC-1025 : Command submitted on node dbs01 did not complete within 3,600 seconds - PRCC-1021 : One or more of the submitted commands did not execute successfully.

PRCC-1025 : Command submitted on node dbs01 did not complete within 3,600 seconds - PRCC-1021 : One or more of the submitted commands did not execute successfully.

PRCC-1025 : Command submitted on node dbs01 did not complete within 3,600 seconds - PRCC-1025 : Command submitted on node dbs01 did not complete within 3,600 seconds

After clicking *Next*, we get a message saying the software installation was successful, which we can see, but some configuration assistants failed, were cancelled or skipped. We elected not to continue at this point.

  • We tried to do the alternative way to upgrade ASM standalone config from Doc ID 1964405.1, but it didn't work either.

I've got a ticket open with Oracle support. They haven't responded with anything yet, but it's been only 3 hours since I opened the Sev 2 ticket. Has anyone encountered this error? If yes, how did you fix it?

I appreciate any guidance you can provide. Thank you.

-- 
Sandy B.



-- http://www.freelists.org/webpage/oracle-l
Received on Tue Aug 02 2016 - 22:27:46 CEST

Original text of this message