Skip to content

Latest commit

 

History

History
111 lines (85 loc) · 4.24 KB

import.md

File metadata and controls

111 lines (85 loc) · 4.24 KB
Raw

DataPump: Import data from one PDB into another one

The following variables used in the examples below:

export NAMESPACE=<kubernetes namespace where the instance was created>
export PATH_TO_EL_CARRO_RELEASE=<the complete path to the downloaded release directory>

Running Oracle Data Pump import utility - impdp - is supported via a declarative Kubernetes-based API. An import operation takes a dump file at a Google Cloud Storage location and applies it to an existing PDB. A dump file contains db data and metadata in an Oracle proprietary binary format which is produced by the Oracle Data Pump export utility - expdp.

Note: the PDB name the data was exported from, and the destination PDB name the dump file is imported to, must match.

  1. Prepare a dump file and set permissions

    Upload a dump file to a Google Cloud Storage location, for example: gs://example-bucket/imports/pdb1/tables.dmp Make sure the El Carro operator has read access to the bucket containing the dump file:

    a. If you're not using workload identity, use the Compute Engine default service account for GCS access.

    b. If you have enabled workload identity on GKE, you can configure the Kubernetes service account to act as a Google service account.

    You can run the following command to see whether workload identity is enabled for the GKE cluster or not:

    gcloud container clusters describe $CLUSTER --zone=$ZONE  --project=$PROJECT | grep workload

workloadMetadataConfig:
  workloadMetadataConfig:
workloadIdentityCon fig:
   workloadPool: $PROJECT.svc.id.goog

    Grant permissions using the appropriate service account:

     gsutil iam ch serviceAccount:$service_account_email:objectViewer gs://example-bucket

    Optionally

    There is an optional parameter you can pass to an import with the GCS location of the import operation log file that you can inspect later, and which is produced by the impdputility with the import process details. If you request an import log, make sure the operator can write to the destination GCS bucket

    gsutil iam ch serviceAccount:$gke_cluster_service_account_email:objectCreator gs://example-log-bucket

  2. Create and apply Import CR

    Edit the gcsPath and optionally the gcsLogPath attributes in the sample import resource:

    cat $PATH_TO_EL_CARRO_RELEASE/samples/v1alpha1_import_pdb1.yaml
    apiVersion: oracle.db.anthosapis.com/v1alpha1
kind: Import
metadata:
  name: import-pdb1
spec:
  instance: mydb
  databaseName: pdb1
  type: DataPump
  # Service account should have read access to the destination bucket,
  # sample command to grant read access (replace with actual SA email):
  # > gsutil iam ch serviceaccount:SA@PROJECT.iam.gserviceaccount.com:objectViewer gs://ex-bucket
  gcsPath: "gs://example-bucket/import/pdb1/import.dmp"
  # Uncomment to enable import log upload to Google Cloud Storage.
  # Service account should have write access to the destination bucket,
  # sample command to grant access (replace with actual SA email):
  # > gsutil iam ch serviceaccount:SA@PROJECT.iam.gserviceaccount.com:objectCreator gs://ex-bucket
  #  Add .gz as Google Cloud Storage object file extension to enable compression.
  gcsLogPath: "gs://example-log-bucket/import/pdb1.log"

    instance and databaseName must refer to existing Instance and Database custom resources names in the namespace the Import resource will be created in.

    After the manifest is ready, submit it to the cluster as follows:

    kubectl apply -f $PATH_TO_EL_CARRO_RELEASE/samples/v1alpha1_import_pdb1 -n $NAMESPACE

  3. (Optional) Inspect the result of creating an Import resource

    Check the Import custom resource status:

    kubectl get imports.oracle.db.anthosapis.com -n $NAMESPACE