Skip to content

Latest commit

 

History

History
34 lines (24 loc) · 1.98 KB

provisioning_without_db_gold_image.md

File metadata and controls

34 lines (24 loc) · 1.98 KB

Provisioning Oracle Database Sharding Topology Without Database Gold Image

In this use case, the database is created automatically using DBCA during the provisioning of the shard databases and the catalog database when the Oracle Sharding topology is deployed using Oracle Sharding controller.

NOTE In this use case, because DBCA creates the database automatically during the deployment, the time required to create the database is greater than the time it takes when the database is created by cloning from a Database Gold Image.

This example uses shard_prov.yaml to provision an Oracle Database sharding topology using Oracle Sharding controller with:

  • Primary GSM Pods gsm1 and standby GSM Pod gsm2
  • Two sharding Pods: shard1 and shard2
  • One Catalog Pod: catalog
  • Namespace: shns

In this example, we are using pre-built Oracle Database and Global Data Services container images available on Oracle Container Registry

  • To pull the above images from Oracle Container Registry, create a Kubernetes secret named ocr-reg-cred using your credentials with type set to kubernetes.io/dockerconfigjson in the namespace shns.
  • If you plan to use images built by you, you need to change dbImage and gsmImage tag with the images you have built in your enviornment in file shard_prov.yaml.
  • To understand the Pre-requisite of Database and Global Data Services docker images, refer Oracle Database and Global Data Services Docker Images

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

  1. Deploy the shard_prov.yaml file: 
    kubectl apply -f shard_prov.yaml
  2. Check the status of the deployment: 
    # Check the status of the Kubernetes Pods:
kubectl get all -n shns

# Check the logs of a particular pod. For example, to check status of pod "shard1-0":
kubectl logs -f pod/shard1-0 -n shns