Starting with Oracle ESS version 18c and OEDA August 2017 release Oracle introduced a new feature OEDA command-line (oedacli). The new OEDA command line interface allows you to update an existing es.xml file. These updates are called Actions and an action is a single atomic task.
OEDA command-line interface (oedacli) can help you with various Exadata life cycle management tasks, such as:
- Add node to or remove node from a Virtual Cluster on Exadata
- Add database home to or remove database home from physical cluster
- Add or remove Storage cell
- Resize Oracle ASM disk groups
- Add or remove additional Databases
- Add or remove additional database homes to an Oracle VM cluster
Software requirement:
- OEDA, August 2017 release
You can operate oedacli in 2 mode:
- Edit mode
- Deploy mode
Using OEDACLI utility
oedacli utility can be used for various routine tasks on Exadata Database Machine.
Prerequisites
- OEDA August 2017 release or later
- Original OEDA configuration XML file used for deployment
- Use default password for root, oracle and grid users on the compute nodes in cluster
To start the oedacli navigate to the directoy containing the oeda software.
# cd /u01/app/oracle/software/oeda
# unzip p26964044_181000_Linux-x86-64.zip
# cd linux-64
# ./oedacli
For more details read the OEDA Command-Line interface at:
http://docs.oracle.com/cd/E80920_01/DBMIN/exadata-deployment-assistant.htm#DBMIN-GUID-CCACB268-C707-4897-8C1C-0F3568FA456C
- To Load an original OEDA xml Configuration file
[root@dm01db01 linux-x64]# ./oedacli
oedacli> LOAD FILE name=/u01/app/oracle/software/oeda/Netsoftmate-dm01.xml
SUCCESS - file loaded OK
Customer : Netsoftamte - QED -QA -IND
- To List xmlactions
oedacli> list xmlactions
There are no actions in this XML file
- To Display help using oedacli
[root@dm01db01 linux-x64]# ./oedacli
oedacli> help
HELP [topic]
Available Objects:
ACFSVOLUME
ADD ACFSVOLUME
ALTER ACFSVOLUME
DELETE ACFSVOLUME
LIST ACFSVOLUMES
CELL
CLONE CELL
DELETE CELL
LIST CELLS
CLUSTER
ALTER CLUSTER
UPGRADE CLUSTER
LIST CLUSTERS
DISKGROUP
ADD DISKGROUP
ALTER DISKGROUP
ALTER DISKGROUPS
DELETE DISKGROUP
LIST DISKGROUPS
DATABASE
ADD DATABASE
ALTER DATABASE
DELETE DATABASE
LIST DATABASES
DATABASEHOME
ADD DATABASEHOME
ALTER DATABASEHOME
CLONE DATABASEHOME
DELETE DATABASEHOME
LIST DATABASEHOMES
DOM0
LIST DOM0S
ES
ALTER ES
GUEST
CLONE GUEST
DELETE GUEST
LIST GUESTS
ILOM
ALTER ILOM
LIST ILOMS
MACHINE
ALTER MACHINE
LIST MACHINES
NETWORK
ADD NETWORK
ALTER NETWORK
DELETE NETWORK
LIST NETWORKS
SCAN
ADD SCAN
ALTER SCAN
DELETE SCAN
LIST SCANS
SWITCH
ALTER SWITCH
LIST SWITCHES
VIP
ADD VIP
ALTER VIP
DELETE VIP
LIST VIPS
CLI COMMANDS
LOAD FILE
SAVE FILE
SAVE FILES
DELETE XMLACTION
LIST XMLACTIONS
SAVE ACTION
MERGE ACTIONS
DEPLOY ACTIONS
- To Display help add database
oedacli> help add database
Usage:
ADD DATABASE
BLOCKSIZE = <blocksize> |
CHARSET = <characterset> |
DATADG = <datadg> |
DBLANG = <dblang> |
DBNAME = <dbname> |
DBTEMPLATE = <dbtemplate> |
DBTYPE = <dbtype> |
HOSTNAMES = <hostnames> |
RECODG = <recodg>
WHERE
DBHOMEID = <databasehomeid> |
CLUSTERNUMBER = <clusternumber> DBHOMELOC = <databasehomelocation> |
CLUSTERNAME = <clustername> DBHOMELOC = <databasehomelocation> |
CLUSTERID = <clusterid> DBHOMELOC = <databasehomelocation> |
CLUSTERNUMBER = <clusternumber> CDBNAME = <containerdbname>
CLUSTERNAME = <clusternumber> CDBNAME = <containerdbname>
CLUSTERID = <clusternumber> CDBNAME = <containerdbname>
Purpose:
Adds a database or a CDB or a PDB to an existing CDB
Arguments:
<blocksize> : Default: 8192, not required for PDB
<characterset> : Default: AL32UTF8, not required for PDB
<datadg> : *The DATA diskgroup, not required for PDB
<dblang> : Default: all_langs, not required for PDB
<dbname> : *Database name
<dbtemplate> : Default: ADMIN, otherwise ADMIN or DW, not required for PDB
<dbtype> : Default: normal DB, otherwise CDB or PDB
<hostnames> : Default: list of nodes from db home
<recodg> : *The RECO diskgroup, not required for PDB
Where:
<databasehomeid> : The es id for the databasehome
<clusternumber> : The cluster number in the es xml, starting at 1
<clustername> : The name of the cluster
<clusterid> : The es xml id of the cluster
<databasehomelocation> : The path for the target database home
<containerdbname> : The database name for the container - only required when DBTYPE is PDB
Comments: * indicates a mandatory parameter
- To Display help add ASM Diskgroup
oedacli> help add diskgroup
Usage:
ADD DISKGROUP
ACFSNAME = <acfsname>
ACFSPATH = <acfspath>
ACFSSIZE = <acfssize>
CELLLIST = '<cellist>'
*DISKGROUPNAME = <diskgroupname>
*DISKGROUPSIZE = <diskgroupsize>
OCRVOTE = <ocrvote>
QUORUMDISK = <quorumdisk>
*REDUNDANCY = <redundancy>
*SLICESIZE = <slicesize>
SPARSE = <sparse>
SPARSEVIRTUALSIZE = <sparsevirtualsize>
TYPE = <diskgrouptype>
[DATABASENAME = <databasename>]
WHERE
CLUSTERNAME = <clustername> |
CLUSTERNUMBER = <clusternumber> |
CLUSTERID = <clusterid>
Purpose:
Adds a diskgroup
Arguments:
<acfsname> : The name of the acfs volume on this diskgroup
<acfspath> : The path for the acfs filesystem
<acfssize> : The size of the acfs volume
<cellist> : A comma separated list of cells for this diskgroup, the list enclosed in '
<diskgroupname> : The new name for the diskgroup
<ocrvote> : true if this diskgroup will host the ocrvote for clusterwear
<quorumdisk> : true if this diskgroup will require quorum
<redundancy> : Redundancy for this diskgroup : NORMAL or HIGH
<diskgroupsize> : The size of the diskgroup, specify in G or T. Only slice or diskgroup size, not both
<slicesize> : The slice size on disk for each griddisk for this diskgroup
<sparse> : true if this diskgroup has sparse enabled
<sparsevirtualsize> : The sparsevirtual size
<type> : Diskgroup type, DATA, RECO, DBFS or OTHER, default is other. If you want the database to be built using this diskgrouptype must be set to DATA or RECO
<databasename> : If type is DATA or RECO, the dbname of the target database
Where:
<clusternumber> : The cluster number in the es xml, starting at 1
<clustername> : The name of the cluster
<clusterid> : The es xml id of the cluster
Comments: * indicates a mandatory field
oedacli>
Conclusion:
In this article we have learned about new OEDA command-line (oedacli) utility. The new OEDA command line interface to update an existing es.xml file. These updates are called Actions and an action is a single atomic task.
No comments:
Post a Comment