AnsweredAssumed Answered

Issue with upgrading Dell R320 appliance to 7.0.1 from 6.9.1

Question asked by Philip Martinez on Nov 4, 2016
Latest reply on Nov 16, 2016 by Philip Martinez

Like • Show 0 Likes0
Comment • 8

I'm trying to upgrade our development environment which is running on an Dell R320 appliance from 6.9.1 Patch 14 to 7.0.1.

I kicked off the installation script by entering:

install.sh -afx

Thing seemed to be going well until it got to the Oracle deinstall point.

############ ORACLE DEINSTALL & DECONFIG TOOL START ############

######################### CHECK OPERATION START #########################
## [START] Install check configuration ##
The deinstall tool cannot determine the home type needed to deconfigure the selected home. Please select the type of Oracle home you are trying to deinstall.
Single Instance database - Enter 1
Real Application Cluster database - Enter 2
Grid Infrastructure for a cluster - Enter 3
Grid Infrastructure for a stand-alone server - Enter 4
Client Oracle Home - Enter 5
Transparent Gateways Oracle Home - Enter 6

If I enter 1 it results in

The product version number of the specified home cannot be determined. Is the product version at least 11.2.0.1.0 (y - yes, n - no)? [n]

If I click on y then

Checking for existence of the Oracle home location /u01/app/11.2.0/grid
Oracle Home type selected for deinstall is: Oracle Single Instance Database
Oracle Base selected for deinstall is:
Checking for existence of central inventory location /home/oracle/oraInventory
Checking for sufficient temp space availability on node(s) : (omitting due to posting in forum)

## [END] Install check configuration ##

Network Configuration check config START

Network de-configuration trace file location: /tmp/deinstall2016-11-04_09-37-18AM/logs/netdc_check2016-11-04_09-41-07-AM.log

Network Configuration check config END

Database Check Configuration START

Database de-configuration trace file location: /tmp/deinstall2016-11-04_09-37-18AM/logs/databasedc_check2016-11-04_09-41-08-AM.log

Database Check Configuration END

Enterprise Manager Configuration Assistant START

EMCA de-configuration trace file location: /tmp/deinstall2016-11-04_09-37-18AM/logs/emcadc_check2016-11-04_09-41-08-AM.log

Enterprise Manager Configuration Assistant END
Oracle Configuration Manager check START
OCM check log file location : /tmp/deinstall2016-11-04_09-37-18AM/logs//ocm_check6689.log
Oracle Configuration Manager check END

######################### CHECK OPERATION END #########################

####################### CHECK OPERATION SUMMARY #######################
Oracle Home selected for deinstall is: /u01/app/11.2.0/grid
Inventory Location where the Oracle home registered is: /home/oracle/oraInventory
Following Oracle Restart enabled listener(s) will be de-configured: LISTENER
No Enterprise Manager configuration to be updated for any database(s)
No Enterprise Manager ASM targets to update
No Enterprise Manager listener targets to migrate
Checking the config status for CCR
Oracle Home exists but CCR directory does not exists and also CCR is not configured
CCR check is finished
A log of this session will be written to: '/tmp/deinstall2016-11-04_09-37-18AM/logs/deinstall_deconfig2016-11-04_09-37-27-AM.out'
Any error messages from this session will be written to: '/tmp/deinstall2016-11-04_09-37-18AM/logs/deinstall_deconfig2016-11-04_09-37-27-AM.err'

############# ORACLE DEINSTALL & DECONFIG TOOL END #############

Philip Martinez Nov 16, 2016 9:47 AM

Correct Answer

Updating to include resolution.

Support ended up recommending just uninstalling 6.9.1 and then doing a fresh install of 7.0.1. That worked without needing to make any configuration changes.

See the reply in context

No one else had this question

Outcomes

Nasreen Mathias

Nov 4, 2016 11:18 AM

Did you run the appliance updater for the OS? if so check to see if you created the folder

/opt/appliancePatches/ and set the permissions

Actions

Philip Martinez @ Nasreen Mathias on Nov 4, 2016 11:28 AM

Hi Nasreen,

I did run the appliance updater for Q2.

rsaimg_updater_2016Q2_SLES11-11G.tar.bz2

Actions

Nasreen Mathias

Nov 4, 2016 11:41 AM

How about

rsaimg_updater_<release_quarter>_SLES11_

12C.tar.bz2

Did you create the /home/oracle/security folder and set the permission? I am not sure if

rsaimg_updater_2016Q3_SLES11_11G.tar.bz2 is released yet, but you would need that as well. However, for that you will get a missing asmlib error message. Check the ASM partition and make sure it is what you are entering during the installation.

grep ASM_PARTITION /tmp/Aveksa_System.cfg

Actions

Philip Martinez @ Nasreen Mathias on Nov 4, 2016 11:59 AM

So you need an updater that isn't released yet to upgrade to 7.0.1? When I talked to support they said it was supposed to be getting released sometime soon.

Actions

Nasreen Mathias

@ Philip Martinez on Nov 4, 2016 12:07 PM

You should still be able to do the install without the Q3 updater as long as you have applied both rsaimg_updater_2016Q2_SLES11_12C.tar.bz2 and rsaimg_updater_2016Q2_SLES11-11G.tar.bz2, and make sure you have the oracle_12.1.0.2_patches_v001 in your packages folder

Actions

Philip Martinez @ Nasreen Mathias on Nov 4, 2016 1:38 PM

Thanks for your assistance thus far. I've confirmed all of the above.

When I tried re-running the installer this time I get

Checking for supported database version...
ERROR: ORA-12154: TNS:could not resolve the connect identifier specified SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where <logon> ::= <username>[/<password>][@<connect_identifier>] <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>] SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where <logon> ::= <username>[/<password>][@<connect_identifier>] <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>]

Error occurred when determining the Oracle version.

Detected Oracle is installed on this server, please use 'service aveksa_server startoracle' to bring Oracle online
and restart installation.

When I type in to startoracle it then results in

I'm going to work through a support ticket to hopefully get this resolved.

Actions

Nasreen Mathias

@ Philip Martinez on Nov 4, 2016 1:49 PM

sounds like the issue is related to network configuration. Check

sudo bash modifynetworksettings.sh and adjust it accordingly. Before doing this you may want to find the current Hostname, Server IP, gateway, subnet, DNS IPs.. before running the script.

Actions

Philip Martinez @ Nasreen Mathias on Nov 16, 2016 9:47 AM

Updating to include resolution.

Support ended up recommending just uninstalling 6.9.1 and then doing a fresh install of 7.0.1. That worked without needing to make any configuration changes.

Actions

8 Replies

Nasreen Mathias Nov 4, 2016 11:18 AM
Mark Correct
Correct Answer
Did you run the appliance updater for the OS? if so check to see if you created the folder
/opt/appliancePatches/ and set the permissions
Like • Show 1 Like1
Actions
- Philip Martinez @ Nasreen Mathias on Nov 4, 2016 11:28 AM
  Mark Correct
  Correct Answer
  Hi Nasreen,
  
  I did run the appliance updater for Q2.
  
  rsaimg_updater_2016Q2_SLES11-11G.tar.bz2
  Like • Show 0 Likes0
  Actions
Nasreen Mathias Nov 4, 2016 11:41 AM
Mark Correct
Correct Answer
How about
rsaimg_updater_<release_quarter>_SLES11_
12C.tar.bz2
Did you create the /home/oracle/security folder and set the permission? I am not sure if
rsaimg_updater_2016Q3_SLES11_11G.tar.bz2 is released yet, but you would need that as well. However, for that you will get a missing asmlib error message. Check the ASM partition and make sure it is what you are entering during the installation.

grep ASM_PARTITION /tmp/Aveksa_System.cfg
Like • Show 1 Like1
Actions
- Philip Martinez @ Nasreen Mathias on Nov 4, 2016 11:59 AM
  Mark Correct
  Correct Answer
  So you need an updater that isn't released yet to upgrade to 7.0.1? When I talked to support they said it was supposed to be getting released sometime soon.
  Like • Show 0 Likes0
  Actions
  - Nasreen Mathias @ Philip Martinez on Nov 4, 2016 12:07 PM
    Mark Correct
    Correct Answer
    You should still be able to do the install without the Q3 updater as long as you have applied both rsaimg_updater_2016Q2_SLES11_12C.tar.bz2 and rsaimg_updater_2016Q2_SLES11-11G.tar.bz2, and make sure you have the oracle_12.1.0.2_patches_v001 in your packages folder
    Like • Show 1 Like1
    Actions
    - Philip Martinez @ Nasreen Mathias on Nov 4, 2016 1:38 PM
      Mark Correct
      Correct Answer
      Thanks for your assistance thus far. I've confirmed all of the above.
      
      When I tried re-running the installer this time I get
      
      Checking for supported database version...
      ERROR: ORA-12154: TNS:could not resolve the connect identifier specified SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where <logon> ::= <username>[/<password>][@<connect_identifier>] <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>] SP2-0306: Invalid option. Usage: CONN[ECT] [{logon|/|proxy} [AS {SYSDBA|SYSOPER|SYSASM}] [edition=value]] where <logon> ::= <username>[/<password>][@<connect_identifier>] <proxy> ::= <proxyuser>[<username>][/<password>][@<connect_identifier>]
      Error occurred when determining the Oracle version.
      Detected Oracle is installed on this server, please use 'service aveksa_server startoracle' to bring Oracle online
      and restart installation.
      
      When I type in to startoracle it then results in
      
      I'm going to work through a support ticket to hopefully get this resolved.
      Like • Show 0 Likes0
      Actions
      - Nasreen Mathias @ Philip Martinez on Nov 4, 2016 1:49 PM
        Mark Correct
        Correct Answer
        sounds like the issue is related to network configuration. Check
        sudo bash modifynetworksettings.sh and adjust it accordingly. Before doing this you may want to find the current Hostname, Server IP, gateway, subnet, DNS IPs.. before running the script.
        
        Like • Show 1 Like1
        Actions
        Philip Martinez @ Nasreen Mathias on Nov 16, 2016 9:47 AM
        Unmark Correct
        Correct Answer
        Updating to include resolution.
        
        Support ended up recommending just uninstalling 6.9.1 and then doing a fresh install of 7.0.1. That worked without needing to make any configuration changes.
        Like • Show 0 Likes0
        Actions

Issue with upgrading Dell R320 appliance to 7.0.1 from 6.9.1

Outcomes

Related Content

Recommended Content