Skip to content

Latest commit

 

History

History
35 lines (24 loc) · 2.09 KB

clone_from_database.md

File metadata and controls

35 lines (24 loc) · 2.09 KB

Clone DB System from Existing Database of DB System in OCI Oracle Base Database System (OBDS)

In this use case, an existing OCI OBDS system deployed earlier with existing Database is going to be cloned in OCI Base OBDS Service using existing Database ID.

As an pre-requisite, get the details of OCID of database of an existing OBDS System which you want to clone.

NOTE: We are assuming that before this step, you have followed the prerequisite steps to create the configmap and the secrets required during the deployment.

This example uses clone_dbcs_system_from_database.yaml to clone a Single Instance OBDS VMDB using Oracle DB Operator OBDS Controller with:

  • OCID of existing as databaseId
  • OCI Configmap as oci-cred
  • OCI Secret as oci-privatekey
  • setupDBCloning: as true
  • Specification of dbClone as - Details of new DB system for cloning dbAdminPasswordSecret,tdeWalletPasswordSecret, dbName,hostName,displayName,licenseModel,domain,sshPublicKeys,subnetId, initialDataStorageSizeInGB NOTE: For the details of the parameters to be used in the .yaml file, please refer here.

Use the file: clone_dbcs_system_from_database.yaml for this use case as below:

  1. Deploy the .yaml file:
[root@docker-test-server OBDS]# kubectl apply -f clone_dbcs_system_from_database.yaml
dbcssystem.database.oracle.com/dbcssystem-clone created
  1. Monitor the Oracle DB Operator Pod pod/oracle-database-operator-controller-manager-665874bd57-g2cgw for the progress of the OBDS VMDB creation of PDBs.

NOTE: Check the DB Operator Pod name in your environment.

[root@docker-test-server OBDS]# kubectl logs -f pod/oracle-database-operator-controller-manager-665874bd57-g2cgw -n  oracle-database-operator-system

Sample Output

Here is the sample output for cloning an existing OBDS System deployed in OCI using Oracle DB Operator OBDS Controller.