Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1662038.1
Update Date:2014-05-09
Keywords:

Solution Type  Technical Instruction Sure

Solution  1662038.1 :   ODA (Oracle Database Appliance): How To make onecommand.params compatible  


Related Items
  • Oracle Database Appliance Software
  •  
  • Oracle Database Appliance
  •  
Related Categories
  • PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
  •  




In this Document
Goal
Solution
 How To make onecommand.params compatible 
 Bare Metal environment type
 Virtualized Platform (VP) environment type
References


Applies to:

Oracle Database Appliance Software - Version 2.2.0.0 to 2.9.0.0 [Release 2.2 to 2.9]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

The onecommand.params (/opt/oracle/oak/onecmd/onecommand.params) file is compatible only with the Oracle Appliance Manager Configurator version that was used to generate it. If you updated oak after the initial deployment then you should generate onecommand.params with the corresponding Configurator. The note will show what to change making the original onecommand.params compatible with the new configurator.

Solution

Loading the onecommand.params (/opt/oracle/oak/onecmd/onecommand.params) file with a not compatible Oracle Appliance Manager Configurator version, the following error message will appears:

File_Load_Error

Note as the recommended way is to re-create the onecommand.params with the compatible Oracle Appliance Manager Configurator version. If for any reason this is not possible you can proceed with the following steps

 

How To make onecommand.params compatible 

Based on environment type (BareMetal or Virtualized Platform), in the below tables you can see the parameters differences between onecommand.params. As example, lets suppose you are running on ODA v.2.4.0.0.0 BM and you are going on 2.9.0.0.0, you should make the following changes:

from

#onecommand.params generated by GUI tool
# Confuration information
CONFIGVERSION=2.4.0.0.0
(...)

to

#onecommand.params generated by GUI tool
# Confuration information
CONFIGVERSION=2.9.0.0.0
HWTYPE=V1
ENVTYPE=BM
ApplicationType=Generic
DeploymentMode=Basic
(...)

 

Bare Metal environment type

The following is conversion table for a BareMetal configuration that is reporting the onecommand.params settings you need change/add to make it compatible with an early Oracle Appliance Manager Configurator version

from\to2.22.32.42.52.62.72.82.9 2.10
2.2 no changes no changes CONFIGVERSION=2.4.0.0.0

CONFIGVERSION=2.5.0.0.0

 

CONFIGVERSION=2.6.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)

CONFIGVERSION=2.7.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)

CONFIGVERSION=2.8.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

CONFIGVERSION=2.9.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

CONFIGVERSION=2.10.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

2.3 NA no changes CONFIGVERSION=2.4.0.0.0

CONFIGVERSION=2.5.0.0.0

CONFIGVERSION=2.6.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
CONFIGVERSION=2.7.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)

CONFIGVERSION=2.8.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

CONFIGVERSION=2.9.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

CONFIGVERSION=2.10.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

2.4  NA NA no changes

CONFIGVERSION=2.5.0.0.0

CONFIGVERSION=2.6.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
CONFIGVERSION=2.7.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)

CONFIGVERSION=2.8.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

CONFIGVERSION=2.9.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

CONFIGVERSION=2.10.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

2.5  NA  NA NA no changes CONFIGVERSION=2.6.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
CONFIGVERSION=2.7.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
CONFIGVERSION=2.8.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic
CONFIGVERSION=2.9.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

CONFIGVERSION=2.10.0.0.0
HWTYPE=V1 (*)
ENVTYPE=BM
ApplicationType=Generic (**)
DeploymentMode=Basic

2.6  NA  NA  NA NA no changes CONFIGVERSION=2.7.0.0.0 CONFIGVERSION=2.8.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.9.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.10.0.0.0
DeploymentMode=Basic
2.7  NA  NA  NA  NA NA no changes CONFIGVERSION=2.8.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.9.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.10.0.0.0
DeploymentMode=Basic
2.8  NA  NA  NA  NA NA  NA no changes CONFIGVERSION=2.9.0.0.0 CONFIGVERSION=2.10.0.0.0 
2.9  NA  NA  NA  NA NA  NA  NA no changes CONFIGVERSION=2.10.0.0.0 
2.10 NA NA NA NA NA NA NA NA no changes

(*) HWTYPE= <version>, it could be 'V1', 'V2', 'V3'

(**) ApplicationType= <type>, it could be "Generic" or "SAP"

 

Virtualized Platform (VP) environment type

The following is conversion table for a Virtualized Platform configuration that is reporting the onecommand.params settings you need change/add to make it compatible with an early Oracle Appliance Manager Configurator version

from\to2.52.62.72.82.9 2.10
2.5 no changes CONFIGVERSION=2.6.0.0.0
HWTYPE=V1 (*)
ENVTYPE=VM
ApplicationType=Generic
CONFIGVERSION=2.7.0.0.0
HWTYPE=V1 (*)
ENVTYPE=VM
ApplicationType=Generic
CONFIGVERSION=2.8.0.0.0
HWTYPE=V1 (*)
ENVTYPE=VM
ApplicationType=Generic
DeploymentMode=Basic
CONFIGVERSION=2.9.0.0.0
HWTYPE=V1 (*)
ENVTYPE=VM
ApplicationType=Generic
DeploymentMode=Basic
CONFIGVERSION=2.10.0.0.0
HWTYPE=V1 (*)
ENVTYPE=VM
ApplicationType=Generic
DeploymentMode=Basic
2.6 NA no changes CONFIGVERSION=2.7.0.0.0 CONFIGVERSION=2.8.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.9.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.10.0.0.0
DeploymentMode=Basic
2.7  NA NA no changes CONFIGVERSION=2.8.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.9.0.0.0
DeploymentMode=Basic
CONFIGVERSION=2.10.0.0.0
DeploymentMode=Basic
2.8  NA  NA NA no changes CONFIGVERSION=2.9.0.0.0 CONFIGVERSION=2.10.0.0.0
2.9  NA  NA  NA NA no changes CONFIGVERSION=2.10.0.0.0
2.10 NA NA NA NA NA no changes

(*) HWTYPE= <version>, it could be 'V1', 'V2', 'V3'

 

References

<BUG:17820010> - LNX64-112-CMT: UPGRADE ONECOMMAND.PARAMS FILE WHEN UPGRADING ODA (INFRA)

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback