Refresh the Cloud Target After Discovery

You can refresh the cloud target after discovery in any of the following scenarios:

  • To associate those additional database targets that were discovered after cloud target discovery

  • To associate any new storage server cells added to Exadata Cloud Service after discovery

  • To add a VM Guest or host

  • To remove a VM Guest or host

  1. Create the property file, for example refresh_exacc_fin.txt with the list of hosts to add or remove.
    configMap.targetName=ExaCC_Finance  
    
    credMap.cellCredSet=SYSMAN:EXADATA_CRED  
    
    host.add.name.0=addhost0.example.com
    host.add.name.1=addhost1.example.com  
    
    host.remove.name.0=removehost0.example.com
    host.remove.name.1=removehost1.example.com

    In the above example,

    • configMap.targetName: Name of the cloud target that you want to refresh
    • credMap.cellCredSet: The credential set which was used to discover the cloud target. This must be a named credential that provides explicit grant to you, and of the type ExaCLI or RESTful API.
    • host.add.name.x: The host names on which the databases that must be associated with the cloud target, are run. Here, x is the host name number which should start with 0, and must be incremented by 1 for every additonal host name added to the add list.
    • host.remove.name.x: The host names that must be removed from the cloud target association. Here, x is the host name number which should start with 0, and must be incremented by 1 for every additonal host name added to the remove list. Note that all the databases that are running on the specified host are removed.
  2. Run the following emcli command by specifying the property file in the form of data <property_file>:
    emcli submit_procedure -name=ExaCloudServiceRefresh -input_file=data:<property_file> -notification="scheduled, action required, running" ;

    Here's an example output after the command is executed by using the example property file refresh_exacc_fin.txt:

    $ emcli submit_procedure -name=ExaCloudServiceRefresh -input_file=data:refresh_exacc_fin.txt -notification="scheduled, action required, running" ;
    Schedule not specified, defaults to immediate.
    94100035C07141DCE053010011AC4000
    Deployment procedure submitted successfully
  3. You can view the status of the refresh activity in the Procedure Activity page. Go to Enterprise Manager Home page > click the Enterprise icon Enterprise icon > click Provisioning and Patching. The Procedure Activity page is displayed.
After the refresh activity is complete, you can visit the cloud target home page to view the new database targets / hosts added to the cloud target or notice that the hosts that you removed are absent. See Explore the Cloud Target Home Page.