2 Instance Life Cycle Tasks

This section includes all life cycle operations for the BDDCS instance. You can see the status, start, stop, run a backup on demand, configure scheduled backups, and restore from backups. You can also apply a patch, reset and re-enable your instance if provisioning fails, and update credentials for the Studio database and WebLogic Server.

• The Overview page
  Use the Overview page to view the current status of your BDDCS instance, obtain the host name of the BDCS node that is hosting your BDDCS instance, and check subscription ID, service start and stop dates.
• The Administration page
  The Administration page has two tabs: Backup and Maintenance. It lets you configure, run and view backups and access the page for downloading BDDCS patches.
• Starting and stopping an instance
  After you provision a BDDCS instance, it is automatically started. In the dashboard, you can stop and restart an already provisioned instance.
• Accessing Studio
  You access Studio by using Open BDDCS Studio button in the BDDCS console. Studio is the front-end application for your BDDCS instance.
• Scheduling backups
  To configure a backup, specify the automated backup frequency as backup policy. Also specify how long you want to retain the backup data and the location of your backup storage.
• Creating a backup on demand
  Use Back up Now to run a backup on demand.
• Restoring an instance from a backup
  You can restore your BDDCS instance from backup using the bdd-cloud.sh script.
• About loading data into your service
  You can load data either in Studio by uploading a personal file, or you can run DP CLI to load and update data in the service.
• Patching the service
  When a patch is available, the Maintenance tab displays a notification and a link to download the patch files. Once you have the files, you can copy them to your node and apply the patch. You can also apply WebLogic patches at the same time.
• Rolling back a failed patch
  If the patch fails, you should run the rollback script to remove the patch and restore your old instance. You can then fix the errors that caused the failure and reapply the patch.
• Resetting and re-enabling an instance
  If enabling of the BDDCS instance fails, the life cycle operations menu displays two options to help you recover: Reset and Re-enable.
• Updating credentials
  In some instances, for example if you changed credentials outside of the BDDCS instance (for Hadoop, Studio, or WebLogic Server), you need to update these credentials in the BDDCS instance configuration to reflect the changes.
• Deleting an instance
  When you delete an instance, an automatic backup of your configuration is created and your configuration is removed.
• Termination
  When your subscription period is close to expire, you, as a service administrator, receive a notification email from Oracle Cloud Services and the service is terminated at the expected date. To continue with your subscription and prevent the termination, contact your Oracle Service representative before your subscription expires.