| Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback |
| Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
||
 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Predictive Self-Healing Sure Solution 2027830.1 : ODA HA (High Availability) Deployment Step Descriptions -- A List of Deployment Version Specific Steps Used for Each ODA HA Version Using GridInst.pl
There are up to 26 identifiable steps executed during an ODA HA deployment. Some of these steps will change between ODA versions based on new, altered or deprecated functionality. This note lists and briefly describes the version specific steps used during a deployment depending on ODA version. This note provides the command which can be used to confirm the current ODA version steps. NOTE: Some steps can also be used after a deployment for very targeted changes to the ODA if using specific guidance from ODA Documentation, MOS (My Oracle Support) notes or based on ODA Support guidance. Applies to:Oracle Database Appliance Software - Version 2.1.0.1 to 12.1.2.9 [Release 2.1 to 12.1]Oracle Database Appliance - Version All Versions to All Versions [Release All Releases] Information in this document applies to any platform. ODA, GridInst.pl, Deployment, ODAVP, ODAHA, ODA HA, deployment steps,onecommand.params PurposeThis Oracle Database Appliance* (ODA-HA) note can be used as a reference for reviewing deployment steps which can change between versions. While deployment steps can be unique to the ODA software version used, the steps are generic for the hardware used. oakcli show env_hw -- Confirms the ODA Hardware type and if using Bare Metal (BM) or Virtualized Platform (ODAVP)
oakcli show version -detail -- Confirms ODA version as well as details confirming of the current versions used are up-to-date ( or for FW if exceeding the current expected version )
To confirm the deployment steps run the following from the /opt/oracle/oak/onecmd directory as root: #./GridInst.pl -l < Bare Metal installations
#./GridInst.pl -o -l < from ODA Base on virtualized platforms
IMPORTANT This note helps to confirm the order of the deployment steps by ODA version:
This note does not discuss when to consider running steps manually. Incorrectly running steps manually can wipe out all existing databases and storage structures. Do NOT run GridInst steps manually without consulting the ODA Support group first or following published information that confirms the step by function and not by step#. Knowing the exact deployment steps and order is critical if manual steps are executed for any reason. ScopeWhile not all ODA deployment steps are unique to each version, there are several differences between many of the ODA versions. ODA Deployment steps can be reviewed and as appropriate executed manually to help troubleshoot problems, correct missed steps or to finish steps that previously had not been executed. DetailsUse the command ./GridInst.pl -l to confirm the current steps for the specific version used. This command is found in the /opt/oracle/oak/onecmd directory and reads values from the onecommand.params file. [root@oda1 onecmd]# ./GridInst.pl -l
Steps in BOLD highlight unique order for the respective version(s) CreateASMDiskgroups - Is destructive = Never use after a deployment *( X6-2S/M/L does not use the configurator. ./GridInst.pl steps do not apply to ODA Lite ) Attachments This solution has no attachment |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||