4.3.14.1 DEPLOY EXASCALE
This command performs Exascale deployment actions.
Syntax
DEPLOY EXASCALE
ACTION = action
WHERE
{ CLUSTERNUMBER = clusternumber [ DATABASENAME = databasename ] |
CLUSTERNAME = clustername [ DATABASENAME = databasename ] |
CLUSTERID = clusterid [ DATABASENAME = databasename ] |
DATABASENAME = databasename }
Arguments
-
ACTION
: Specifies the Exascale deployment action, which is one of the following:CONFIGURECELLS
,CONFIGURECOMPUTES
,CREATEDBWALLET
,CREATEGIVAULT
,CREATEDBVAULT
,UNDOCONFIGURECELLS
,UNDOCONFIGURECOMPUTES
,UNDOCREATEDBWALLET
,UNDOCREATEGIVAULT
,UNDOCREATEDBVAULT
.
The following arguments are available in the WHERE
clause:
-
CLUSTERNUMBER
: Specifies the cluster number in the OEDA configuration file (es.xml
), starting at 1. -
CLUSTERNAME
: Specifies the name of the cluster. -
CLUSTERID
: Specifies the OEDA configuration file (es.xml
) ID of the cluster. -
DATABASENAME
: Specifies the name of the database.
Usage Notes
-
The
CONFIGURECELLS
action must be performed before theCONFIGURECOMPUTES
action. -
The
CONFIGURECELLS
andCONFIGURECOMPUTES
actions must be performed before any wallet or vault actions. -
The
CONFIGURECOMPUTES
action creates an Exascale wallet for the Oracle Grid Infrastructure operating system (OS) owner. This wallet also supports Oracle Database in a non-role-separated Exadata configuration, where the Oracle Grid Infrastructure OS owner is the same as the Oracle Database OS owner. -
The
CREATEDBWALLET
action only creates an Exascale wallet for an Oracle Database OS owner in a role-separated Exadata configuration, where the Oracle Database OS owner is not the same as the Oracle Grid Infrastructure OS owner. -
Undo actions must be performed in the following order:
UNDOCREATEDBVAULT
,UNDOCREATEGIVAULT
,UNDOCREATEDBWALLET
,UNDOCONFIGURECOMPUTES
andUNDOCONFIGURECELLS
.
Parent topic: EXASCALE