BPM Enterprise (BPME) database schema is created by running the utility image. This can be executed either via a Docker command or a Kubernetes job. Below is an example for Oracle database - 

1. Setup the Oracle database and the BPME database user - 

v5.3.0 - https://docs.tibco.com/pub/bpme/5.3.0/doc/html/Default.htm#installation/create-configure-the-tibco-bpm-enterprise-database-oracle.htm?TocPath=Installation%257CInstalling%2520TIBCO%2520BPM%2520Enterprise%2520on%2520Kubernetes%257CCreating%2520the%2520TIBCO%2520BPM%2520Enterprise%2520Database%257C_____3

2. Create a namespace in Kubernetes - 

For example - 
kubectl create namespace bpme

3. Run the following to create a Kubernetes job - 

===========
cat <<EOF | microk8s kubectl apply -f -
apiVersion: batch/v1
kind: Job
metadata:
  name: utility
  namespace: bpme
spec:
  template:
    spec:
      hostPID: true
      containers:
      - name: utility
        image: tibco/bpm/utility:5.3.0
        command: ["utility", "-dbConfig", "url=jdbc:oracle:thin:@//<DB_hostname>:<DB_port>/<DB_serviceName>", "username=<DB_user>", "password=<DB_pass>", "-setupDatabase", "execute", "--verbose"]
      restartPolicy: Never
EOF
===========

where -
<DB_hostname> is the hostname or IP address of the Oracle database
<DB_port> - is the port number of the Oracle database
<DB_serviceName> - is the database service name that is associated with the pluggable database. 
<DB_user> - is the database user created in step # 1
<DB_pass> - is the database user's password as provided in step # 1

Please note this command only creates the Kubernetes job. If this is successful, the following message is seen - 
 

job.batch/utility created

4. To view result of the utility, the pod logs will need to be accessed - 

-- To know the pod_name created by the job. It is in the format - utility-*. 
kubectl get pods -n bpme