Carlos Furushima – Furushima https://furushima.com.br - Consultoria de Banco de Dados | Furushima Mon, 03 Nov 2025 22:02:24 +0000 pt-BR hourly 1 https://furushima.com.br/wp-content/uploads/2024/02/cropped-favicon-32x32.png Carlos Furushima – Furushima https://furushima.com.br 32 32 secondary_vnic_all_configure.sh https://furushima.com.br/blog/secondary_vnic_all_configure-sh/ Mon, 03 Nov 2025 21:25:56 +0000 https://furushima.com.br/?p=2917 Script oficial da Oracle Cloud que detecta e configura automaticamente todas as VNICs secundárias anexadas a uma VM Linux.

  • Sobe as interfaces correspondentes às VNICs secundárias;
  • Obtém o IP (via DHCP) ou aplica o IP estático já definido;
  • Cria rotas e regras de policy routing por interface, isolando o tráfego por sub-rede;
  • Persiste a configuração para sobreviver a reinicializações;
  • É idempotente (pode ser executado várias vezes) e dispensa reboot após anexar a VNIC.

Ideal para multihoming, separação de redes (app/backup), rotas dedicadas e cenários de alta disponibilidade.

Faça o Download do script abaixo :

vnicBaixar

https://raw.githubusercontent.com/oracle/terraform-examples/master/examples/oci/connect_vcns_using_multiple_vnics/scripts/secondary_vnic_all_configure.sh

#!/usr/bin/env bash

# Copyright (c) 2018, Oracle and/or its affiliates.
# The Universal Permissive License (UPL), Version 1.0
#
# Oracle OCI Virtual Cloud Networks IP configuration script
#
# 2017-10-24 initial release
# 2017-11-21 filter out VLANs if VM
# 2017-11-21 inhibit namespaces for ubuntu 16
# 2018-02-12 fix sshd typo in help
# 2018-02-20 update copyright notice
# 2018-03-21 fix to add src routing on primary VNIC when not using namespaces
# 2018-04-05 add note on multiple VCNs
# 2018-05-10 fix to delete config by deleting default route before deleting table, added -v option
# 2018-05-22 fix to ignore interfaces enslaved to a master device
# 2018-09-14 allow namespaces for Ubuntu 16 since problems with DHCP are fixed, and inhibit for all OL/Centos 6
# 2018-09-19 fix os name and version setting for centos 6 images
# 2018-09-19 fix ip addr parsing to remove MAC VLAN interfaces
# 2018-10-25 fix secondary private ip src routing
# 2018-10-31 fix misc routing setup, fix multiple ifaces on same subnet

declare -r THIS=$(basename "$0")
declare -r MD_URL='http://169.254.169.254/opc/v1/vnics/'
declare -r NA='-'
declare -r RTS_FILE='/etc/iproute2/rt_tables'
declare -ir RT_ID_MIN=10 # in case lower ones are reserved
declare -ir RT_ID_MAX=255
declare -r RT_FORMAT_BM='ort${nic}vl${vltag}'
declare -r RT_FORMAT_VM='ort${nic}'
declare -r DEF_NS_FORMAT_BM='ons${nic}vl${vltag}'
declare -r DEF_NS_FORMAT_VM='ons${nic}'
declare -r MACVLAN_FORMAT='${iface}.${vltag}' # note awk script looks for this (max 15 chars)
declare -r VLAN_FORMAT='${iface}v${vltag}' # (max 15 chars)
declare -ir MTU=9000
declare -r ADD='ADD'
declare -r DELETE='DELETE'
declare -r YES='YES'
declare -r CURL=$(which curl)
declare -r IP=$(which ip)
declare -r SSHD=$(which sshd)
declare -r MODPROBE=$(which modprobe)
declare -r OS_RELEASE='/etc/os-release'
if [ -f "$OS_RELEASE" ]; then
    declare -r OS_ID=$(grep -ws ID $OS_RELEASE | cut -f 2 -d '=' | tr -d '"' | tr '[:upper:]' '[:lower:]')
    declare -r OS_VERSION=$(grep -ws VERSION_ID $OS_RELEASE | cut -f 2 -d '=' | tr -d '"')
else
    declare -r OS_RELEASE_alt='/etc/redhat-release'
    if [ -f "$OS_RELEASE_alt" ]; then
        declare -r OS_ID=$(cat $OS_RELEASE_alt|cut -f 1 -d ' ' | tr '[:upper:]' '[:lower:]')
        declare -r OS_VERSION=$(cat $OS_RELEASE_alt | cut -f 3 -d ' ')
    fi
fi
if [ -n "$OS_VERSION" ]; then
    declare -r OS_MAJ_VERSION=$(echo $OS_VERSION | cut -f 1 -d '.')
fi
declare -r SYS_CLASS_NET='/sys/class/net'
declare -A VIRTUAL_IFACES
declare IS_VM=''
declare -a MACS # all (unique) macs
declare -A MD_I_BY_MAC # index into arrays by MAC
declare -a MD_MACS
declare -a MD_ADDRS
declare -a MD_VLTAGS
declare -a MD_SCIDRS
declare -a MD_SPREFIXS
declare -a MD_SBITSS
declare -a MD_VIRTRTS
declare -a MD_VNICS
declare -a MD_NIC_IS # not set at all if vm
declare -a MD_CONFIGS # $ADD if vnic added
declare -A DUP_ADDRS # hash of addrs that appear more than once
declare -A DUP_SADDRS # hash of subnet addrs that appear more than once
# items use $NA to mean null
declare -A IP_I_BY_MAC # index into arrays by MAC
declare -a IP_MACS # runs of dups if sec addrs
declare -a IP_NSS
declare -a IP_IFACES
declare -a IP_ADDRS
declare -a IP_SADDRS
declare -a IP_SBITSS
declare -a IP_VIRTRTS
declare -a IP_STATES
declare -a IP_VLANS
declare -a IP_VLTAGS # vltag (0 if phys iface)
declare -a IP_SECADS # set to $YES if secondary addr
declare -a IP_SRCS # set to $YES if src hint
declare -a IP_NIC_IS # nic index of iface
declare -a IP_CONFIGS # $DELETE if vnic deleted
declare -a NIC_IP_IS # index of physical iface for nic index
declare -A NIC_I_BY_PHYS_IP_I # nic index for physical iface ip_i
# be sure to clear any IP_ arrays above in the read function
# options:
declare QUIET=''
declare DEBUG=''
declare START_SSHD=''
declare USE_NS=''
declare NS_FORMAT=''
declare -a SEC_ADDRS
declare -a SEC_VNICS

declare -r IFACE_AWK_SCRIPT='/tmp/oci_vcn_iface.awk'
cat >$IFACE_AWK_SCRIPT <<'EOF'
function prtiface(mac, iface, addr, sbits, state, vlan, vltag, secad) {
    if (iface != "") printf "%s\t%s\t%s\t%s\t%s\t%s\t%s\t%s\n", mac, iface, addr, sbits, state, vlan, vltag, secad
}
BEGIN { iface = ""; addr = "-" }
/^[0-9]/ {
    # if not the first and prev was not a mac vlan then print previous (note print at end too)
    if (addr == "-") prtiface(mac, iface, addr, sbits, state, vlan, vltag, secad)
    addr = "-"
    sbits = "-"
    state = "-"
    macvlan = "-"
    vlan = "-"
    vltag = "-"
    secad = "-"
    if ($0 ~ /BROADCAST/ && $0 !~ /UNKNOWN/ && $0 !~ /NO-CARRIER/ && $0 !~ /master /) {
        i = index($2, "@")
        if (1 < i) {
            j = index($2, ".")
            if (j < i) { # mac vlan (not used, no addrs)
                macvlan = substr($2, 1, i - 1)
                iface = substr($2, i + 1, length($2) - i - 1) # skip : at end
                addr = "" # skip the mac vlan iface
            } else { # vlan
                vlan = substr($2, 1, i - 1)
                # extract iface/vltag from macvlan
                iface = substr($2, i + 1, j - i - 1)
                vltag = substr($2, j + 1, length($2) - j - 1) # skip : at end
            }
        } else {
            i = index($2, ":")
            if (i <= 1) { print "cannot find interface name"; exit 1 }
            iface = substr($2, 1, i - 1)
        }
        if ($0 ~ /LOWER_UP/) state = "UP"
        else state = "DOWN"
    } else iface = ""
    next
}
/ link\/ether / { mac = tolower($2) }
/ inet [0-9]/ {
    i = index($2, "/")
    if (i <= 1) { print "cannot find interface inet address"; exit 1 }
    if (addr != "-") secad = "YES"
    addr = substr($2, 0, i - 1)
    sbits = substr($2, i + 1, length($2) - i)
    prtiface(mac, iface, addr, sbits, state, vlan, vltag, secad)
}
END { if (addr == "-") prtiface(mac, iface, addr, sbits, state, vlan, vltag, secad) }
EOF

oci_vcn_err() {
    echo "Error: $1" >&2
    exit 1
}

oci_vcn_warn() {
    echo "Warning: $1" >&2
}

oci_vcn_info() {
    [ -n "$QUIET" ] || echo "Info: $1" >&2
}

oci_vcn_debug() {
    [ -z "$DEBUG" ] || echo "Debug: $1" >&2
}

oci_vcn_virtual_ifaces_read() {
    VIRTUAL_IFACES=()
    local iface
    for iface in $(ls $SYS_CLASS_NET); do
        if ls -l $SYS_CLASS_NET/$iface | grep -wq virtual; then
            VIRTUAL_IFACES[$iface]='t'
        fi
    done
}

oci_vcn_md_read() {
    # sets all MD data arrays and their index I_BY_MAC
    local -r tmpfile=$(mktemp /tmp/oci_vcn_md.XXXXX)

    # MD notes:
    # vnic order: primary first, then time created (and therefore vltag/nic)
    # BM notes: (1) may be interleaved wrt nic index (i.e. all nic 0 not guaranteed before all nic 1)
    # (2) nicIndex was supported starting around 8/23/17, but will not appear on previously
    # launched instances unless refreshed by a vnic attach or detach after that date

    # parse: force json fields on separate lines
    # WARNING: assumes no string values with commas or double quotes
    # WARNING: assumes no sub-objects with identical field names
    [ -n "$CURL" ] || oci_vcn_err "cannot find curl command"
    $CURL -s $MD_URL | tr , '\n' >"$tmpfile" || oci_vcn_err "cannot read metadata"
    MD_MACS=($(grep -w macAddr "$tmpfile" | cut -f 4 -d '"')) || exit $? # string
    local -i i
    for i in $(seq 0 $((${#MD_MACS[@]} - 1))); do
        MD_MACS[$i]="${MD_MACS[$i],,}"
    done
    MD_ADDRS=($(grep -w privateIp "$tmpfile" | cut -f 4 -d '"')) # string
    MD_VLTAGS=($(grep -w vlanTag "$tmpfile" | cut -f 2 -d ':' | tr -d ' ')) # integer
    MD_VIRTRTS=($(grep -w virtualRouterIp "$tmpfile" | cut -f 4 -d '"')) # string
    local s
    for s in $(grep -w subnetCidrBlock "$tmpfile" | cut -f 4 -d '"'); do # string
        MD_SCIDRS+=(${s})
        MD_SPREFIXS+=(${s%/*})
        MD_SBITSS+=(${s#*/})
    done
    MD_VNICS=($(grep -w vnicId "$tmpfile" | cut -f 4 -d '"'))
    MD_NIC_IS=($(grep -w nicIndex "$tmpfile" | cut -f 2 -d ':' | tr -d ' '))

    # do some validity checks on md data
    [ ${#MD_MACS[@]} -eq ${#MD_ADDRS[@]} ] || oci_vcn_err "invalid metadata: MAC or IP addresses are missing"
    [ ${#MD_MACS[@]} -eq ${#MD_VLTAGS[@]} ] || oci_vcn_err "invalid metadata: MAC or VLAN tags are missing"
    [ ${#MD_MACS[@]} -eq ${#MD_VIRTRTS[@]} ] || oci_vcn_err "invalid metadata: MAC or virtual router addresses are missing"
    [ ${#MD_MACS[@]} -eq ${#MD_SPREFIXS[@]} ] || oci_vcn_err "invalid metadata: MAC or subnets are missing"
    [ ${#MD_MACS[@]} -eq ${#MD_VNICS[@]} ] || oci_vcn_err "invalid metadata: MAC or VNIC ids are missing"
    for i in $(seq 0 $((${#MD_MACS[@]} - 1))); do
        [[ ${MD_ADDRS[$i]} =~ ^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+$ ]] || oci_vcn_err "invalid metadata: address IP format incorrect: ${MD_ADDRS[$i]}"
        [[ ${MD_VLTAGS[$i]} =~ ^[0-9]+$ ]] || oci_vcn_err "invalid metadata: VLAN tag incorrect: ${MD_VLTAGS[$i]}"
        [[ ${MD_VIRTRTS[$i]} =~ ^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+$ ]] || oci_vcn_err "invalid metadata: virtual router address format incorrect: ${MD_VIRTRTS[$i]}"
        [[ ${MD_SPREFIXS[$i]} =~ ^[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+$ ]] || oci_vcn_err "invalid metadata: subnet prefix format incorrect: ${MD_SPREFIXS[$i]}"
    done

    # set vm flag based on existence of nic index (see override in oci_vcn_ip_read)
    # get the virtual interfaces if VM
    if [ ${#MD_NIC_IS[@]} -eq 0 ]; then
        IS_VM='t'
        oci_vcn_virtual_ifaces_read
    fi

    # create reverse lookup
    for i in "${!MD_MACS[@]}"; do
        MD_I_BY_MAC[${MD_MACS[$i]}]=$i
    done
    rm "$tmpfile"

    # find the duplicate addrs, if any
    local -A addrs=()
    local addr
    for addr in "${MD_ADDRS[@]}"; do
        if [ -n "${addrs[$addr]}" ]; then DUP_ADDRS[$addr]='t'; fi
        addrs[$addr]='t'
    done

    # find the duplicate subnet addrs, if any
    local -A saddrs=()
    for addr in "${MD_SPREFIXS[@]}"; do
        if [ -n "${saddrs[$addr]}" ]; then DUP_SADDRS[addr]='t'; fi
        saddrs[addr]='t'
    done
}

oci_vcn_ip_route_table_name() {
    local -ir nic=$1 # format looks for "${nic}", note this is really $nic_i
    local -ir vltag=$2
    local format="$RT_FORMAT_VM"

    [ -n "$IS_VM" ] || format="$RT_FORMAT_BM"
    eval echo "$format"
}

oci_vcn_ip_route_table_name_ip_i() {
    # use only when ip already setup
    local -ir ip_i=$1
    local -ir nic_i=${IP_NIC_IS[$ip_i]}
    local -ir vltag=${IP_VLTAGS[$ip_i]}

    oci_vcn_ip_route_table_name $nic_i $vltag
}

oci_vcn_ip_route_table_exists() {
    local -r rt_name=$1
    if grep -qsw $rt_name $RTS_FILE; then
        echo "$rt_name"
    fi
}

oci_vcn_ip_route_table_find_unused_id() {
    # read all the current route table id/name pairs
    # mapfile will create array with each line an element
    local lines
    mapfile -t lines < <(cat $RTS_FILE | grep -E '^[0-9]' | tr '\t' ' ' | tr -s ' ' ' ') || oci_vcn_err "cannot read route tables file $RTS_FILE"
    local line
    local -A rt_by_id
    for line in "${lines[@]}"; do
        local -a pair=($line)
        local id=${pair[0]}
        local name=${pair[1]}
        rt_by_id[$id]=$name
    done

    # find first id not used
    local -i unused=-1
    local -i i
    for i in $(seq $RT_ID_MIN $RT_ID_MAX); do
        if [ -z "${rt_by_id[$i]}" ]; then
            unused=$i
            break
        fi
    done
    [ $unused -ne -1 ] ||  oci_vcn_err "cannot find unused id in route tables file $RTS_FILE"
    echo $unused
}

oci_vcn_ip_route_table_create() {
    local -ir nic_i=$1
    local -ir vltag=$2
    local -r skip_if_exists=$3
    local -r rt_name=$(oci_vcn_ip_route_table_name $nic_i $vltag)

    # Check if the route table exists
    local rt_exists
    rt_exists=$(oci_vcn_ip_route_table_exists $rt_name) || exit $?
    if [ -n "$rt_exists" ]; then # already exists
        if [ -n "$skip_if_exists" ]; then
            oci_vcn_debug "create route table $rt_name already exists, skipping"
            return
        fi
        oci_vcn_warn "route table $rt_name already exists, reusing"
    else # create
        local -i rt_id
        rt_id=$(oci_vcn_ip_route_table_find_unused_id) || exit $?
        oci_vcn_debug "create route table $rt_name ($rt_id)"
        echo "$rt_id    $rt_name" >> $RTS_FILE
    fi
    echo "$rt_name"
}

oci_vcn_ip_route_table_del() {
    local -r rt_name=$1
    local -r tmpfile=$(mktemp /tmp/oci_vcn_rt_tables.XXXXX)

    if ! grep -qsw $rt_name $RTS_FILE; then
        oci_vcn_debug "rt $rt_name not in $RTS_FILE"
        return
    fi
    oci_vcn_debug "rt $rt_name delete"
    cp -p $RTS_FILE "$tmpfile" # in case grep fails
    grep -vw $rt_name $RTS_FILE > "$tmpfile"
    mv "$tmpfile" $RTS_FILE
    echo 't'
}

oci_vcn_ip_routing_add() {
    local -ir md_i=$1
    local -ir nic_i=$2
    local -r iface=$3
    local -r ns=$4
    local -r skip_if_exists=$5
    local -ir vltag="${MD_VLTAGS[$md_i]}"
    local -r addr="${MD_ADDRS[$md_i]}"
    local -r sprefix="${MD_SPREFIXS[$md_i]}"
    local -r virtrt="${MD_VIRTRTS[$md_i]}"
    local -r scidr="${MD_SCIDRS[$md_i]}"

    # set a default route to the gateway/virtual router
    if [ -n "$ns" ]; then
        local -r nscmd="netns exec $ns $IP"
        # using a namespace: iface is assumed only one in namespace, so just set a
        # default route to the gateway in the main route table
        oci_vcn_debug "default route add"
        $IP $nscmd route add default via $virtrt || oci_vcn_err "cannot add namespace $ns default gateway $virtrt"
        oci_vcn_info "added namespace $ns default route to gateway $virtrt"
    else
        # the default route (in main route table) already defined through primary vnic.
        # this adds a rule to lookup a route table for any packets sourced from addr
        # and then the route table has the default route for that addr.
        # this allows packets from protocol services that reply with src addr
        # set to route back out through the iface (prevents asymmetric routing).

        # check for dup addrs and subnet addrs
        if [ -n "${DUP_ADDRS[$addr]}" ]; then
            oci_vcn_warn "IP address $addr is a duplicate, skipping creating source route rule"
            return
        fi
        [ -z "${DUP_SADDRS[$sprefix]}" ] || oci_vcn_warn "duplicate subnet prefix $sprefix"

        # create route table and add a default route via the gateway, and subnet route
        local rt_name
        rt_name=$(oci_vcn_ip_route_table_create $nic_i $vltag $skip_if_exists) || exit $?
        [ -n "$rt_name" ] || return
        oci_vcn_debug "route table add rules"
        $IP route add default via $virtrt dev $iface table $rt_name || oci_vcn_err "cannot add default route via $virtrt on $iface to table $rt_name"
        $IP route add $scidr dev $iface table $rt_name || oci_vcn_err "cannot add subnet $scidr route on $iface to table $rt_name"

        # create source-based rule to use table
        oci_vcn_debug "src rule add"
        $IP rule add from $addr lookup $rt_name || oci_vcn_err "cannot add rule from $addr use table $rt_name"
        oci_vcn_info "added rule for routing from $addr lookup $rt_name with default via $virtrt"
    fi
}

oci_vcn_ip_routing_del() {
    local -ir ip_i=$1
    local -r ns="${IP_NSS[$ip_i]#$NA}"
    local -r iface="${IP_IFACES[$ip_i]}"

    # for namespaces the subnet and default routes will be auto deleted with the namespace
    if [ -z "$ns" ]; then
        # delete rule
        local -r rt_name=$(oci_vcn_ip_route_table_name_ip_i $ip_i)
        local had_rule=''
        if $IP rule | grep -qsw $rt_name; then # rule(s) exists
            # note that there may be secondary private ips rules using the same table
            oci_vcn_debug "rules to table $rt_name delete"
            while $IP rule del lookup $rt_name 2>/dev/null; do true; done
            had_rule='t'
        fi

        # delete route table
        local had_table
        had_table=$(oci_vcn_ip_route_table_del $rt_name) || exit $?
        ([ -z "$had_rule" ] && [ -z "$had_table" ]) || oci_vcn_info "removed routing on interface $iface"
    fi
}

oci_vcn_ip_routing_sec_addr_add() {
    local -ir iface_ip_i=$1
    local -r addr=$2
    local -r ns="${IP_NSS[$iface_ip_i]#$NA}"

    # need to add source rule so reuse the routing table from the primary private ip
    # not needed if in namespace
    # not needed if on pri iface (uses main route table for dest and default route)
    if [ -z "$ns" ] && [ $iface_ip_i -ne 0 ]; then
        # create source-based rule to use iface's routing table
        local -r rt_name=$(oci_vcn_ip_route_table_name_ip_i $iface_ip_i)
        oci_vcn_debug "sec addr src rule add"
        $IP rule add from $addr lookup $rt_name || oci_vcn_err "cannot add rule from secondary $addr use table $rt_name"
        oci_vcn_info "added rule for routing from secondary IP address $addr lookup $rt_name"
    fi
}

oci_vcn_ip_routing_sec_addr_del() {
    local -ir ip_i=$1
    local -r addr=$2
    local -r ns="${IP_NSS[$ip_i]#$NA}"

    # deconfig the routing (see comments in add)
    if [ -z "$ns" ] && [ $ip_i -ne 0 ]; then
        $IP rule del from $addr 2>/dev/null # ok if already deleted
        oci_vcn_info "deleted rule for routing from secondary IP address $addr"
    fi
}

oci_vcn_ip_routes_read() {
    #ip r list 192.168.1.0/24
    local -ir ip_i=$1
    local -r ns="${IP_NSS[$ip_i]#$NA}"
    local -r iface="${IP_IFACES[$ip_i]}"
    local nscmd=''
    local virtrt="$NA"

    if [ -n "$ns" ]; then
        nscmd="netns exec $ns $IP"
    else
        # no namespace: check for route table
        local -r rt_name=$(oci_vcn_ip_route_table_name_ip_i $ip_i)
        local rt_exists
        rt_exists=$(oci_vcn_ip_route_table_exists $rt_name) || exit $?
        if [ -n "$rt_exists" ]; then # exists
            # check for rule
            if $IP rule | grep -qsw $rt_name; then # rule exists that uses route table
                # look for default route in table, note table may exist but be empty
                # "default via 10.0.0.1 dev ens3"
                local -a def_entry
                def_entry=($($IP route show table $rt_name | grep -sw ^default))
                if [ -n "${def_entry[2]}" ]; then
                    virtrt="${def_entry[2]}"
                    oci_vcn_debug "default route: $virtrt"
                else # emtpy table: delete rule and table
                    virtrt="$NA"
                    oci_vcn_ip_routing_del $ip_i
                fi
            else # clean up route table since no rule uses it
                $(oci_vcn_ip_route_table_del $rt_name)
            fi
        fi
    fi

    # read the routes
    local sprefix="$NA"
    local sbits="$NA"
    local src="$NA"
    # mapfile will create array with each line an element
    mapfile -t routes < <($IP $nscmd route | grep -w $iface) || oci_vcn_err "cannot read IP routes for interface $iface"
    local line
    for line in "${routes[@]}"; do
        local -a route=($line)
        if [ "${route[0]}" = 'default' ]; then
            # "default via 10.0.0.1 dev ens3"
            virtrt="${route[2]}"
            oci_vcn_debug "default route via: $virtrt"
        elif [ "${route[0]#169.}" = "${route[0]}" ]; then # not cavium route
            # "10.0.0.0/24 dev ens3 proto kernel scope link src 10.0.0.2"
            local -i i
            for i in $(seq 0 $((${#route[@]} - 1))); do
                local x="${route[$i]}"
                if [ $i -eq 0 ]; then
                    sprefix=${x%/*}
                    sbits=${x#*/}
                    if [ "$sprefix" = "$sbits" ]; then # not valid line
                        sprefix="$NA"
                        sbits="$NA"
                        break
                    else
                        oci_vcn_debug "subnet route: $sprefix/$sbits"
                    fi
                elif [ "$x" = 'src' ]; then src="$YES"
                fi
            done
        fi
    done
    IP_VIRTRTS[$ip_i]="$virtrt"
    IP_SADDRS[$ip_i]="$sprefix"
    IP_SBITSS[$ip_i]="$sbits"
    IP_SRCS[$ip_i]="$src"
}

oci_vcn_macvlan_name() {
    local -r iface=$1
    local -r vltag=$2
    eval echo "$MACVLAN_FORMAT"
}

oci_vcn_vlan_name() {
    local -r iface=$1
    local -r vltag=$2
    eval echo "$VLAN_FORMAT"
}

oci_vcn_ip_ns_name() {
    local -ir nic=$1 # format looks for "${nic}"
    local -ir vltag=$2

    if [ -n "$USE_NS" ] && [ -z "$NS_FORMAT" ]; then
        if [ -n "$IS_VM" ]; then NS_FORMAT="$DEF_NS_FORMAT_VM"
        else NS_FORMAT="$DEF_NS_FORMAT_BM"; fi
    fi
    eval echo "$NS_FORMAT"
}

oci_vcn_ip_ns_svcs_stop() {
    local -r ns=$1
    local pids
    pids=$($IP netns pids $ns) || oci_vcn_err "cannot get ids for processes in namespace $ns"
    if [ -n "$pids" ]; then
        kill -TERM $pids || oci_vcn_err "cannot terminate namespace $ns processes: $pids"
        oci_vcn_info "terminated namespace $ns processes: $pids"
    fi
}

oci_vcn_ip_ns_svcs_start() {
    local -r ns=$1
    if [ -n "$START_SSHD" ]; then # start SSH daemon
        $IP netns exec $ns $SSHD || oci_vcn_err "cannot start ssh daemon"
        oci_vcn_info "started namespace $ns ssh daemon"
    fi
}

oci_vcn_ip_ns_del() {
    local -r ns=$1
    # note also deletes vlans and routes
    $IP netns del $ns || oci_vcn_err "cannot delete namespace $ns"
    oci_vcn_info "deleted namespace $ns"
}

oci_vcn_ip_ns_create() {
    local -ir nic_i=$1
    local -ir vltag=$2

    [ -n "$MODPROBE" ] || oci_vcn_err "cannot find modprobe command"
    $MODPROBE 8021q || oci_vcn_err "failed to load 8021q module"
    local ns
    ns=$(oci_vcn_ip_ns_name $nic_i $vltag) || exit $?
    $IP netns add $ns || oci_vcn_err "cannot create namespace $ns"
    oci_vcn_info "created namespace $ns"
    echo "$ns"
}

oci_vcn_ip_addr_add_iface() {
    local -ir md_i=$1
    local -ir ip_i=$2 # index of physical iface/nic
    local -r ns=$3
    local iface="${IP_IFACES[$ip_i]}"
    local -r physns="${IP_NSS[$ip_i]#$NA}"
    local -r mac="${MD_MACS[$md_i]}"
    local -ir vltag="${MD_VLTAGS[$md_i]}"
    local -r addr="${MD_ADDRS[$md_i]}"
    local -r sbits="${MD_SBITSS[$md_i]}"
    local vlan=''

    # must be adding to physical iface/nic
    [ -z "${IP_VLANS[$ip_i]#$NA}" ] || oci_vcn_err "cannot add IP address $addr to virtual interface ${IP_VLANS[$ip_i]}"

    # create virtual interface if needed (bm cases)
    local macvlan=''
    if [ -z "$IS_VM" ] && [ $vltag -ne 0 ]; then
        # bm vnics need a virtual iface except for vltag=0
        # if physical iface/nic is in a namespace we must go there to create
        local physnscmd=''
        if [ -n "$physns" ]; then
            physnscmd="netns exec $physns $IP"
        fi

        # create a mac vlan from physical iface/nic
        oci_vcn_debug "macvlan link add $macvlan"
        macvlan=$(oci_vcn_macvlan_name $iface $vltag) || exit $?
        $IP $physnscmd link add link $iface name $macvlan address $mac type macvlan \
            || oci_vcn_err "cannot create MAC VLAN interface $macvlan for MAC address $mac"

        # if physical iface/nic is in a namespace pull out the created mac vlan
        if [ -n "$physns" ]; then
            $IP $physnscmd link set $macvlan netns 1
        fi

        # create an ip vlan on top of the mac vlan
        oci_vcn_debug "vlan link add"
        vlan=$(oci_vcn_vlan_name $iface $vltag) || exit $?
        $IP link add link $macvlan name $vlan type vlan id $vltag \
            || oci_vcn_err "cannot create VLAN $vlan on MAC VLAN $macvlan"
    fi

    # use namespace, if option
    local nscmd=''
    local -r dev="${vlan:-$iface}"
    if [ -n "$ns" ]; then
        nscmd="netns exec $ns $IP"
        # move the iface(s) to the target namespace
        if [ -n "$macvlan" ]; then
            oci_vcn_debug "macvlan link move $ns"
            $IP link set dev $macvlan netns $ns || oci_vcn_err "cannot move MAC VLAN $macvlan into namespace $ns"
        fi
        oci_vcn_debug "$dev link move $ns"
        $IP link set dev $dev netns $ns || oci_vcn_err "cannot move interface $dev into namespace $ns"
    fi

    # add IP address to iface:
    # the netmask is specified to create a route in the main route table
    # if this iface is on the same subnet as another iface then the route will not have an effect
    # (until the other iface is removed)
    oci_vcn_debug "addr $addr/$sbits add on $dev ns '$ns'"
    $IP $nscmd addr add $addr/$sbits dev $dev || oci_vcn_err "cannot add IP address $addr/$sbits on interface $dev"

    if [ -n "$macvlan" ]; then # set vlans up
        oci_vcn_debug "vlans set up"
        $IP $nscmd link set dev $macvlan mtu $MTU up || oci_vcn_err "cannot set MAC VLAN $macvlan up"
        $IP $nscmd link set dev $vlan mtu $MTU up || oci_vcn_err "cannot set VLAN $vlan up"
    else
        oci_vcn_debug "$iface set up"
        $IP $nscmd link set dev $iface mtu $MTU up || oci_vcn_err "cannot set interface $iface MTU"
    fi

    oci_vcn_info "added IP address $addr on interface $dev with MTU $MTU"
    echo "$dev"
}

oci_vcn_ip_addr_del_iface() {
    local -ir ip_i=$1
    local -r iface="${IP_IFACES[$ip_i]}"
    local -r ns="${IP_NSS[$ip_i]#$NA}"
    local -r vlan="${IP_VLANS[$ip_i]#$NA}"
    local -r secad="${IP_SECADS[$ip_i]#$NA}"
    local nscmd=''

    if [ -n "$ns" ]; then
        nscmd="netns exec $ns $IP"
    fi
    if [ "$secad" != "$YES" ] && [ -n "$vlan" ]; then
        # delete vlan and macvlan, removes the addrs (pri and sec) as well
        oci_vcn_debug "$ns link delete"
        local -ir vltag="${IP_VLTAGS[$ip_i]}"
        local macvlan
        macvlan=$(oci_vcn_macvlan_name $iface $vltag) || exit $?
        $IP $nscmd link del link $vlan dev $macvlan || oci_vcn_err "cannot remove VLAN $vlan"
        oci_vcn_info "removed VLAN $vlan"
    else
        # delete addr from phys iface
        # deleting namespace will move phys iface back to main
        # note that we may be deleting sec addr from a vlan here
        local -r addr="${IP_ADDRS[$ip_i]#$NA}"
        local -r dev="${vlan:-$iface}"
        local bits="${IP_SBITSS[$ip_i]#$NA}"

        [ "$secad" != "$YES" ] || bits=32
        oci_vcn_debug "addr $addr del ns '$ns' dev $dev"
        $IP $nscmd addr del $addr/$bits dev $dev || oci_vcn_err "cannot remove IP address $addr/$bits from interface $dev"
        oci_vcn_info "removed IP address $addr from interface $dev"
    fi
}

oci_vcn_ip_addr_add() {
    local -ir md_i=$1
    local -r mac="${MD_MACS[$md_i]}"
    local -r addr="${MD_ADDRS[$md_i]}"
    local ns=''
    local iface=''
    local -i nic_i
    local -i vltag

    # note that when adding an addr to a physical iface ip_i will be the index of the
    # addr, but when creating a vlan for addr ip_i will not be the vlan iface but its phys one
    local -i ip_i

    if [ -z "$IS_VM" ]; then
        # bm vnics' physical ifaces are identified by nic index
        nic_i=${MD_NIC_IS[$md_i]}
        [ $nic_i -lt ${#NIC_IP_IS[@]} ] || oci_vcn_err "cannot find interface for NIC $nic_i"
        ip_i=${NIC_IP_IS[$nic_i]}
        iface="${IP_IFACES[$ip_i]}"
        vltag=${MD_VLTAGS[$md_i]}
    else
        # vm vnics' physical ifaces are identified by matching mac
        local found=''
        ip_i=0
        local ip_mac
        for ip_mac in "${IP_MACS[@]}"; do
            if [ "$ip_mac" = "$mac" ]; then
                found='t'
                break
            fi
            ip_i+=1
        done
        [ -n "$found" ] || oci_vcn_err "cannot find interface matching VNIC MAC $mac"
        iface="${IP_IFACES[$ip_i]}"
        nic_i=${IP_NIC_IS[$ip_i]}
        vltag=0
    fi

    # check that there is no current addr on iface
    if [ -n "$IS_VM" ] || [ "${MD_VLTAGS[$md_i]}" = "0" ]; then # putting addr directly on iface
        local -r ip_addr="${IP_ADDRS[$ip_i]#$NA}"
        [ -z "$ip_addr" ] || oci_vcn_err "IP address $ip_addr already added on interface $iface"
    fi

    # make sure physical iface/nic is up
    if [ "${IP_STATES[$ip_i]}" != "UP" ]; then
        $IP link set dev $iface up || oci_vcn_err "cannot set interface $iface up"
    fi

    # create namespace if requested
    local ns=''
    if [ -n "$USE_NS" ]; then
        ns=$(oci_vcn_ip_ns_create $nic_i $vltag) || exit $?
        # if working on a physical iface we need to set its namespace so that any
        # vlan created subsequently will know how to find it
        [ $vltag -ne 0 ] || IP_NSS[$ip_i]="$ns"
    fi

    # add addr to iface (possibly creating vlan)
    local dev
    dev=$(oci_vcn_ip_addr_add_iface $md_i $ip_i $ns) || exit $?

    # setup routes
    oci_vcn_ip_routing_add $md_i $nic_i $dev $ns

    # if namespace then wait for changes and start services
    if [ -n "$ns" ]; then
        sleep 1 # namespace changes seem to take time
        oci_vcn_ip_ns_svcs_start $ns
    fi
}

oci_vcn_ip_sec_addr_add() {
    local -ir iface_ip_i=$1
    local -r addr=$2
    local -r iface="${IP_IFACES[$iface_ip_i]}"
    local -r vlan="${IP_VLANS[$iface_ip_i]#$NA}"
    local -r dev="${vlan:-$iface}"
    local -r ns="${IP_NSS[$iface_ip_i]#$NA}"
    local nscmd=''
    local nsinfo=''

    # config routing
    oci_vcn_ip_routing_sec_addr_add $iface_ip_i $addr

    # config the addr on the iface
    if [ -n "$ns" ]; then
        nscmd="netns exec $ns $IP"
        nsinfo=" in namespace $ns"
    fi
    oci_vcn_info "adding secondary IP address $addr to interface (or VLAN) $dev$nsinfo"
    $IP $nscmd addr add $addr/32 dev $dev || oci_vcn_err "cannot add secondary IP address $addr on interface $dev$nsinfo"
}

oci_vcn_ip_sec_addr_del() {
    local -ir ip_i=$1
    local -r deconfig_all=$2
    local -r addr=${IP_ADDRS[$ip_i]}
    local -r iface=${IP_IFACES[$ip_i]}
    local -r vlan="${IP_VLANS[$ip_i]#$NA}"
    local -r dev="${vlan:-$iface}"
    local -r ns="${IP_NSS[$ip_i]#$NA}"
    local nscmd=''
    local nsinfo=''

    [ "${IP_SECADS[$ip_i]}" = "$YES" ] || oci_vcn_err "not a secondary IP address: $addr"

    # remove the addr on the iface (see comments in add)
    # no need if deconfig all and on a vlan or in namespace
    if [ -z "$deconfig_all" ] || ([ -z "$vlan" ] && [ -z "$ns" ]); then
        if [ -z "$deconfig_all" ] && [ -n "$ns" ]; then
            nscmd="netns exec $ns $IP"
            nsinfo=" in namespace $ns"
        fi

        oci_vcn_info "removing secondary IP address $addr from interface (or VLAN) $dev$nsinfo"
        $IP $nscmd addr del $addr/32 dev $dev || oci_vcn_err "cannot remove IP address $addr on interface $dev"
    fi

    # remove the routing (see comments in add)
    oci_vcn_ip_routing_sec_addr_del $ip_i $addr
}

oci_vcn_sec_addr_is_provisioned() {
    local -r find_addr=$1
    local -r find_vnic=$2
    local -i i
    local found=''

    for i in $(seq 0 $((${#SEC_ADDRS[@]} - 1))); do
        local addr=${SEC_ADDRS[$i]}
        local vnic=${SEC_VNICS[$i]}
        if [ "$find_addr" = "$addr" ] && [ "$find_vnic" = "$vnic" ]; then
            found='t'
            break
        fi
    done
    echo "$found"
}

oci_vcn_ip_addr_del() {
    local -ir ip_i=$1
    local -r ns="${IP_NSS[$ip_i]#$NA}"
    local -r secad="${IP_SECADS[$ip_i]#$NA}"

    [ $ip_i -ne 0 ] || oci_vcn_err "cannot remove primary VNIC"

    if [ "$secad" != "$YES" ]; then
        if [ -n "$ns" ]; then
            # stop services in namespace
            oci_vcn_ip_ns_svcs_stop $ns
        fi

        # remove routing
        oci_vcn_ip_routing_del $ip_i
    fi

    # remove addr
    oci_vcn_ip_addr_del_iface $ip_i

    if [ "$secad" != "$YES" ] && [ -n "$ns" ]; then
        # delete namespace
        oci_vcn_ip_ns_del $ns
        sleep 1 # namespace changes seem to take time
    fi
}

oci_vcn_ip_ifaces_read() {
    local -r ns="$1"
    local nscmd=''
    local -a iface_datas

    if [ -n "$ns" ]; then # change ip command to use namespace
        nscmd="netns exec $ns $IP"
    fi

    # read the interfaces in namespace (if any)
    # mapfile will create array with each line an element
    mapfile -t iface_datas < <($IP $nscmd addr show | awk -f $IFACE_AWK_SCRIPT) || oci_vcn_err "cannot read IP addresses"
    if [ ${#iface_datas[@]} -eq 0 ]; then
        # if reading physical ifaces, must be at least 1
        [ -n "$ns" ] || oci_vcn_err "cannot locate interfaces"
        # empty namespace: probably result of a VM VNIC delete
        # note empty namespaces do not survive reboot
        $IP netns del $ns || oci_vcn_err "cannot delete empty namespace $ns"
        oci_vcn_warn "deleted empty namespace $ns"
    else
        local -r nsna="${ns:-$NA}"
        local -i ip_i=${#IP_MACS[@]} # continue from previous ns (if any)
        local line
        for line in "${iface_datas[@]}"; do
            # line items are in order printed by awk script print
            # note that $NA is used to mean null (i.e. not set)
            oci_vcn_debug "iface line: $line"
            local -a iface_data=($line)
            local iface="${iface_data[1]}"
            # filter out virtual interfaces if VM (assume created by user for other purpose)
            if [ -z "$IS_VM" ] || [ -z "${VIRTUAL_IFACES[$iface]}" ]; then
                local mac="${iface_data[0]}"
                IP_MACS+=("$mac")
                IP_NSS+=("$nsna")
                IP_IFACES+=("$iface")
                IP_ADDRS+=("${iface_data[2]}")
                IP_SBITSS+=("${iface_data[3]}")
                IP_STATES+=("${iface_data[4]}")
                IP_VLANS+=("${iface_data[5]}")
                IP_VLTAGS+=("${iface_data[6]}")
                local secad="${iface_data[7]}"
                IP_SECADS+=("$secad")
                [ "$secad" = "$YES" ] || IP_I_BY_MAC["$mac"]=$ip_i # primary addrs only
                ip_i+=1
            fi
        done
    fi
}

oci_vcn_ip_read() {
    IP_I_BY_MAC=()
    IP_MACS=()
    IP_NSS=()
    IP_IFACES=()
    IP_ADDRS=()
    IP_SADDRS=()
    IP_SBITSS=()
    IP_VIRTRTS=()
    IP_STATES=()
    IP_VLANS=()
    IP_VLTAGS=()
    IP_SECADS=()
    IP_SRCS=()
    IP_NIC_IS=()
    NIC_IP_IS=()
    NIC_I_BY_PHYS_IP_I=()

    # read the non-namespace ifaces and any addrs on them
    oci_vcn_ip_ifaces_read
    # read ifaces in all the namespaces (if any), note some os's don't support netns
    mapfile -t nss < <($IP netns 2>/dev/null)
    local ns
    for ns in "${nss[@]}"; do
        oci_vcn_ip_ifaces_read $ns
    done

    # set vltag 0 (for phys ifaces) and read os routes for all ifaces
    local -i ip_i
    for ip_i in $(seq 0 $((${#IP_MACS[@]} - 1))); do
        # any iface w/o vltag has tag 0
        [ -n "${IP_VLTAGS[$ip_i]#$NA}" ] || IP_VLTAGS[$ip_i]=0
        oci_vcn_ip_routes_read $ip_i
    done

    # find the "physical" iface indices: vltag 0 and not secondary addr
    # note vm ifaces are considered physical
    # these may not be in nic index order due to inclusion in namespaces (see next)
    local -r tmpfile=$(mktemp /tmp/oci_vcn_ifaces.XXXXX)
    local -A ip_i_by_phys_iface
    for ip_i in $(seq 0 $((${#IP_MACS[@]} - 1))); do
        if [ ${IP_VLTAGS[$ip_i]} -eq 0 ] && [ "${IP_SECADS[$ip_i]}" != "$YES" ]; then
            # physical iface/nic
            local iface=${IP_IFACES[$ip_i]}
            ip_i_by_phys_iface[$iface]=$ip_i
            echo "$iface" >> "$tmpfile"
        fi
        NIC_I_BY_PHYS_IP_I[$ip_i]=-1
    done

    # sort physical ifaces by first number (either at end or in middle) in iface name
    # this will provide the nic index
    local -i nic_i=0
    local iface
    for iface in $(cat "$tmpfile" | awk -- '{ match($1, /[0-9]+/); print substr($1, RSTART, RLENGTH), $1 }' | sort -n | cut -f 2 -d ' '); do
        local ip_i=${ip_i_by_phys_iface[$iface]}
        NIC_IP_IS+=($ip_i)
        NIC_I_BY_PHYS_IP_I[$ip_i]=$nic_i
        nic_i+=1
    done
    rm "$tmpfile"

    # for each iface (phys or vlan) get nic index
    for ip_i in $(seq 0 $((${#IP_MACS[@]} - 1))); do
        local iface=${IP_IFACES[$ip_i]}
        local -i phys_ip_i=${ip_i_by_phys_iface[$iface]}
        IP_NIC_IS[$ip_i]=${NIC_I_BY_PHYS_IP_I[$phys_ip_i]}
    done

    # fix up missing nic index for bms (see also oci_vcn_md_read): bms will be missing nic index metadata
    # if they were created before and have not had a vnic attached or detached since 8/23/17.
    # if there is a secondary vnic created and configured (before 8/23/17) we can tell it is a bm
    # because there will either be configured vlans or more vnics than physical ifaces.
    # note that gen 2 shapes are post 8/23/17 and, hence, will have nic indices already set.
    # a missing nic index for an old bm will not matter if there are no vnics to configure.
    if [ ${#MD_NIC_IS[@]} -eq 0 ] && [ ${#NIC_IP_IS[@]} -eq 1 ] && \
        ([ ${#IP_MACS[@]} -gt 1 ] || [ ${#MD_MACS[@]} -gt 1 ]); then # configured or new secondaries
        local -i md_i
        for md_i in $(seq 0 $((${#MD_MACS[@]} - 1))); do
            MD_NIC_IS+=(0)
        done
        oci_vcn_info "legacy BM instance detected"
        IS_VM=''
    fi
}

oci_vcn_read() {
    # assumes md info is already read
    # reads ip configs and creates single array of all macs
    # (fixes vm interfaces if random mac)
    [ -n "$IP" ] || oci_vcn_err "cannot find ip command"
    local warn_ifaces=''
    local -i attempt
    for attempt in 1 2; do
        # initialize md/ip shared arrays
        MACS=("${MD_MACS[@]}")
        # read all of ip config info and see if it matches md info
        oci_vcn_ip_read
        MD_CONFIGS=()
        local -i md_i=0
        local mac
        for mac in "${MD_MACS[@]}"; do
            MD_CONFIGS[$md_i]="$NA"
            local -i ip_i=${IP_I_BY_MAC[$mac]:--1}
            if [ $ip_i -lt 0 ]; then
                # if there is no corresponding iface mac: add
                # note ifaces with random macs will be detected below and this will be retried
                MD_CONFIGS[$md_i]="$ADD"
            else
                local addr="${IP_ADDRS[$ip_i]#$NA}"
                if [ -z "$addr" ]; then
                    # matching mac iface does not have address: add
                    # make sure it is not a (corrupted) vlan that had been configured previously
                    [ ${IP_VLTAGS[$ip_i]} -eq 0 ] || oci_vcn_err "VLAN (with MAC $mac) configured but missing IP address (must manually fix)"
                    MD_CONFIGS[$md_i]="$ADD"
                fi
            fi
            md_i+=1
        done
        local -i ip_i=0
        IP_CONFIGS=()
        local retry=''
        warn_ifaces=''
        local -A new_macs=() # for deduping secondary addr macs
        for mac in "${IP_MACS[@]}"; do
            IP_CONFIGS[$ip_i]="$NA"
            local addr="${IP_ADDRS[$ip_i]#$NA}"
            # note that the primary vnic will be matched up (permanently)
            local -i md_i=${MD_I_BY_MAC[$mac]:--1}
            if [ $md_i -lt 0 ]; then
                # no metadata mac corresponding to ip mac
                local iface="${IP_IFACES[$ip_i]}"
                if [ -n "$addr" ]; then
                    # addr is configured: should be deleted
                    # bm case (in vm case ifaces are auto-deleted when vnic is detached)
                    IP_CONFIGS[$ip_i]="$DELETE"
                elif [ -z "$IS_VM" ]; then
                    # bm iface mac w/o addr and w/o md mac:
                    # skip if phys iface, else addr deleted w/o deleting vlan?
                    if [ ${IP_VLTAGS[$ip_i]} -ne 0 ]; then
                        IP_CONFIGS[$ip_i]="$DELETE"
                        warn_ifaces="$warn_ifaces $iface"
                    fi
                else
                    # vm iface mac w/o addr and w/o md mac: assume random mac
                    ([ $attempt -eq 1 ] && [ "${IP_STATES[$ip_i]}" = 'DOWN' ]) || oci_vcn_err "interface $iface with MAC $mac does not have corresponding metadata"
                    # assume vm case 1st since less likely addr was deleted
                    # attempt mac fix by turning iface up, then retry
                    # this is probably an Intel driver problem
                    # could look at /sys/class/net/<iface>/addr_assign_type
                    $IP link set dev $iface up || oci_vcn_err "cannot set interface $iface up"
                    retry='t'
                fi
                if [ -z "${new_macs[$mac]}" ]; then
                    new_macs[$mac]='t'
                    MACS+=("$mac") # accumulate all unique macs
                fi
                # TODO else validate for consistency?: addr, vltag, subnet, virtrt
            elif [ "${IP_SECADS[$ip_i]}" = "$YES" ]; then
                local is_prov=$(oci_vcn_sec_addr_is_provisioned $addr "${MD_VNICS[$md_i]}")
                if [ -z "$is_prov" ]; then
                    IP_CONFIGS[$ip_i]="$DELETE"
                fi
            fi
            ip_i+=1
        done
        [ -n "$retry" ] || break
    done

    if [ -n "$warn_ifaces" ]; then
        oci_vcn_warn "no VNIC (or MAC does not match) and no address, interfaces will be marked for delete:$warn_ifaces"
    fi
}

oci_vcn_config_or_deconfig_sec_addrs() {
    local -r do_config="$1" # config if not empty, else deconfig
    local found=''
    # vnics must be configured, whether config or deconfig secondary addrs
    local -i i
    for i in $(seq 0 $((${#SEC_ADDRS[@]} - 1))); do
        local addr=${SEC_ADDRS[$i]}
        local vnic=${SEC_VNICS[$i]}
        # find vnic's mac
        local mac=''
        local -i md_i
        for md_i in $(seq 0 $((${#MD_MACS[@]} - 1))); do
            if [ "$vnic" = "${MD_VNICS[$md_i]}" ]; then
                mac="${MD_MACS[$md_i]}"
                break
            fi
        done
        [ -n "$mac" ] || oci_vcn_err "cannot find VNIC for secondary IP address $addr on $vnic"
        # find mac in ip config
        local -i iface_ip_i=-1
        local already_config=''
        local -i ip_i
        for ip_i in $(seq 0 $((${#IP_MACS[@]} - 1))); do
            if [ "$mac" = "${IP_MACS[$ip_i]}" ]; then # put on this iface if not already configured
                [ $iface_ip_i -ge 0 ] || iface_ip_i=$ip_i # 1st is interface (secondary addrs come after)
                if [ "$addr" = "${IP_ADDRS[$ip_i]}" ]; then # already configured
                    already_config='t'
                    break
                fi
            fi
        done
        [ $iface_ip_i -ge 0 ] || oci_vcn_err "cannot find interface for secondary IP address $addr on $vnic"
        if [ -n "$do_config" ] && [ -z "$already_config" ]; then # configure
            oci_vcn_ip_sec_addr_add $iface_ip_i $addr
            found='t'
        elif [ -z "$do_config" ] && [ -n "$already_config" ]; then # deconfigure
            # note this path is only if deconfiguring just the secondaries
            oci_vcn_ip_sec_addr_del $ip_i
            found='t'
        fi
    done
    echo "$found"
}

oci_vcn_config() {
    local found=''
    local mac
    local -A configed

    # fix up config: md will indicate adds, ip deletes
    local -i md_i
    for md_i in $(seq 0 $((${#MD_CONFIGS[@]} - 1))); do
        local config="${MD_CONFIGS[$md_i]#$NA}"
        if [ "$config" = "$ADD" ]; then
            oci_vcn_info "adding IP config for VNIC MAC ${MD_MACS[$md_i]} with id ${MD_VNICS[$md_i]}"
            oci_vcn_ip_addr_add $md_i
            found='t'
        fi
    done
    local del_vmac=''
    local -i ip_i
    for ip_i in $(seq 0 $((${#IP_CONFIGS[@]} - 1))); do
        local config="${IP_CONFIGS[$ip_i]#$NA}"
        if [ "$config" = "$DELETE" ]; then
            # del all pri addrs and sec addrs (unless its vlan is being deleted)
            local mac="${IP_MACS[$ip_i]}"
            local secad="${IP_SECADS[$ip_i]#$NA}"
            if [ "$secad" != "$YES" ] || [ "$del_vmac" != "$mac" ]; then
                local addr="${IP_ADDRS[$ip_i]}"
                oci_vcn_info "removing IP config of address $addr from MAC $mac"
                oci_vcn_ip_addr_del $ip_i
                found='t'
                # keep track of last deleted vlan
                [ "${IP_VLTAGS[$ip_i]}" -eq 0 ] || del_vmac=$mac
            fi
        fi
    done

    # config secondary addrs, if any
    local sec_addrs_found=''
    if [ ${#SEC_ADDRS[@]} -gt 0 ]; then
        # reread config if there were changes so that secondaries are put in the correct place
        if [ -n "$found" ]; then
            sleep 2 # wait for newly created ifaces to settle
            oci_vcn_read
        fi
        sec_addrs_found=$(oci_vcn_config_or_deconfig_sec_addrs 't') || exit $?
    fi

    [ -n "$found" ] || [ -n "$sec_addrs_found" ] || oci_vcn_info "no changes, IP configuration is up-to-date"
}

oci_vcn_deconfig_all() {
    local -i ip_i=0
    local found=''
    local mac
    for mac in "${IP_MACS[@]}"; do
        local addr="${IP_ADDRS[$ip_i]#$NA}"
        if [ -n "$addr" ]; then # ip is configured
            # note that primaries are encountered first
            if [ "${IP_SECADS[$ip_i]}" != "$YES" ]; then # primary addr
                if [ $ip_i -gt 0 ]; then # skip pri vnic, pri addr
                    local -i md_i=${MD_I_BY_MAC[$mac]:--1}
                    local missing=" missing"
                    local vnicmsg=''
                    if [ $md_i -ge 0 ]; then vnicmsg=" with id ${MD_VNICS[$md_i]}"; missing=""; fi
                    oci_vcn_info "removing IP config of address $addr for$missing VNIC MAC $mac$vnicmsg"
                    oci_vcn_ip_addr_del $ip_i
                    found='t'
                fi
            else # secondary addr
                oci_vcn_ip_sec_addr_del $ip_i 't'
                found='t'
            fi
        fi
        ip_i+=1
    done
    if [ -z "$found" ]; then
        oci_vcn_info "no changes, no IP configuration to delete"
    fi
}

oci_vcn_show() {
    local -r fmt="%-6s %-15s %-15s %-5s %-15s %-10s %-3s %-10s %-5s %-11s %-5s %-17s %s\n"
    printf "$fmt" CONFIG ADDR SPREFIX SBITS VIRTRT NS IND IFACE VLTAG VLAN STATE MAC VNIC
    local mac
    for mac in "${MACS[@]}"; do # all known macs
        local config="$NA"
        local addr="$NA"
        local nic_i="$NA"
        local vltag="$NA"
        local sprefix="$NA"
        local sbits="$NA"
        local virtrt="$NA"
        local ns="$NA"
        local iface="$NA"
        local vlan="$NA"
        local state="$NA"
        local vnic="$NA"
        local -i md_i=${MD_I_BY_MAC[$mac]:--1}
        if [ $md_i -ge 0 ]; then # in md: ADD, or no change depending on ip info
            config="${MD_CONFIGS[$md_i]}"
            nic_i="${MD_NIC_IS[$md_i]:-$NA}"
            addr="${MD_ADDRS[$md_i]}"
            [ -n "$IS_VM" ] || vltag="${MD_VLTAGS[$md_i]}" # not used in vms
            sprefix="${MD_SPREFIXS[$md_i]}"
            sbits="${MD_SBITSS[$md_i]}"
            virtrt="${MD_VIRTRTS[$md_i]}"
            vnic="${MD_VNICS[$md_i]}"
        fi
        # find the ip info on this mac, note that there could be none, one,
        # or multiple addrs if secondaries addrs exist (they will come after primary)
        local -i ip_i=${IP_I_BY_MAC[$mac]:--1} # index of primary addr, if any
        if [ $ip_i -ge 0 ]; then
            local -i pri_ip_i=$ip_i
            local secad=''
            while true; do
                secad="${IP_SECADS[$ip_i]#$NA}"
                [ $pri_ip_i -eq $ip_i ] || [ -n "$secad" ] || break
                vlan="${IP_VLANS[$ip_i]:-$NA}"
                iface="${IP_IFACES[$ip_i]}"
                ns="${IP_NSS[$ip_i]}"
                state="${IP_STATES[$ip_i]}"
                local cfg="${IP_CONFIGS[$ip_i]#$NA}"
                [ -z "$cfg" ] || config="$cfg"
                if [ $md_i -lt 0 ]; then # not in md, fill with ip info
                    addr="${IP_ADDRS[$ip_i]}"
                    sbits="${IP_SBITSS[$ip_i]}"
                    virtrt="${IP_VIRTRTS[$ip_i]}"
                    [ -n "$IS_VM" ] || vltag="${IP_VLTAGS[$ip_i]}"
                elif [ -n "$secad" ]; then
                    addr="${IP_ADDRS[$ip_i]}"
                fi
                local -i nic_phys=${NIC_I_BY_PHYS_IP_I[$ip_i]}
                [ -n "$secad" ] || [ $nic_phys -lt 0 ] || nic_i=$nic_phys # don't show if sec addr
                if [ -z "$secad" ]; then
                    printf "$fmt" "$config" "$addr" "$sprefix" "$sbits" "$virtrt" "$ns" "$nic_i" "$iface" "$vltag" "$vlan" "$state" "$mac" "$vnic"
                else
                    printf "$fmt" "$config" "$addr" "$NA" "$NA" "$NA" "$NA" "$NA" "$NA" "$NA" "$NA" "$NA" "$NA" "$NA"
                fi
                ip_i+=1
            done
        else
            printf "$fmt" "$config" "$addr" "$sprefix" "$sbits" "$virtrt" "$ns" "$nic_i" "$iface" "$vltag" "$vlan" "$state" "$mac" "$vnic"
        fi
    done
}

oci_vcn_help() {
    cat <<EOF
NAME
    $THIS -- display and configure Oracle OCI Virtual Cloud Networks on instance

SYNOPSIS
    $THIS [-s] [-e <IP address> <VNIC OCID>]
    $THIS -c [-q] [-s] [-n [<format>] [-r]] [-e <IP address> <VNIC OCID> [-e ...]]
    $THIS -d [-q] [-s] [-e <IP address> <VNIC OCID>]

DESCRIPTION
    This shows the current OCI Virtual interface Cards provisioned in the cloud
    and configured on this instance. When a secondary VNIC is provisioned in OCI it must
    be explicitly configured on the instance using this script or similar commands.

    The first version of this command displays the currently provisioned VNICs and the
    current IP configuration for this instance. VNICs that are not yet configured are
    marked with '$ADD' and IP configurations that no longer have an associated VNIC
    are marked with '$DELETE'.

    The second version, with -c, configures VNICs that do not have an IP configuration
    and deletes the IP configurations of VNICs that are not currently provisioned.
    This puts the instance IP configuration in sync with current OCI provisioning.
    If one or more optional -e options are present the secondary IP addresses are
    configured on the same interfaces as the corresponding VNIC.

    The configuring interfaces can optionally be placed inside separate network
    namespaces. This is necessary when VNICs are in subnets (different VCNs) with
    overlapping address blocks and the network applications are not bound directly
    to interfaces. Network namespaces require applications to be launched in them
    explicitly (via 'ip netns exec <ns>') in order to establish association with
    the interface. When namespaces are not used, policy-based routing is configured
    to provide a default route to the secondary VNIC\'s virtual router (default
    gateway) when the VNIC\'s address is the source address.

    Bare Metal secondary VNICs are configured using VLANs (where there is no
    corresponding physical interface). These will look like 2 addition interfaces
    when showing IP links, with names like '$MACVLAN_FORMAT' for the MAC VLAN
    and '$VLAN_FORMAT' for the IP VLAN.

    The third version, -d, deletes all IP configuration for provisioned secondary VNICs
    as long as there is no -e option. If one or more optional -e options are present
    only the given secondary IP addresses are deconfigured and the remaining configuration
    is left as is.

    This script is made to be run periodically to pick up changes in VNIC provisioning
    (whether adding or deleting). Note that these IP configuration changes are not
    persistent, the script must, at a minimum, be run on each startup.

    -c          Add IP configuration for VNICs that are not configured and delete
                for VNICs that are no longer provisioned.
    -d          Deconfigure all VNICs (except the primary). If a -e option is also
                present only the secondary IP address(es) are deconfigured.
    -e <IP address> <VNIC OCID>
                Secondary private IP address to configure or deconfigure.
    -h          Print help.
    -n [<format>]
                When configuring, place interfaces in namespace identified by the given
                format. Format can include \$nic and \$vltag variables. The name
                defaults to '$DEF_NS_FORMAT_BM' for BMs and '$DEF_NS_FORMAT_VM' for VMs.
                When configuring multiple VNICs ensure the namespaces are unique.
    -q          Suppress information messages.
    -r          Start sshd in namespace (if -n is present)
    -s          Show information on all provisioning and interface configuration.
                This is the default action if no options are given.
                Columns:
                    CONFIG  '$ADD' indicates missing IP config, '$DELETE' missing VNIC
                    ADDR    IP address
                    SPREFIX subnet CIDR prefix
                    SBITS   subnet mask bits
                    VIRTRT  virutal router IP address
                    NS      namespace (if any)
                    IND     interface index (if BM)
                    IFACE   interface (underlying physical if VLAN is also set)
                    VLTAG   VLAN tag (if BM)
                    VLAN    IP virtual LAN (if any)
                    STATE   state of interface
                    MAC     MAC address
                    VNIC    VNIC object identifier
    -v          Verbose information messages.

EXAMPLES
    $THIS
        Show all provisioned VNICs and configured IP addresses.
    $THIS -c
        Set configuration without a namespace.
    $THIS -c -n ''
        Set configuration using a namespace with the default format.
    $THIS -c -n 'myns\$vltag'
        Set configuration using a namespace with format 'myns\$vltag'.

SEE ALSO:
    OCI networking overview including route tables and security lists:
        https://docs.us-phoenix-1.oraclecloud.com/Content/Network/Concepts/overview.htm
    Note: secondary VNIC in different VCN not handled, requires manually adding default route:
        ip route add <VCN2 CIDR> via <VCN2 sec VNIC subnet virt router ip> dev <VCN2 sec VNIC ifname>
EOF
}

# TODO secondary private IPs in metadata

declare show=''
declare config=''
declare deconfig=''
declare os_ver="$OS_ID-$OS_VERSION"
declare os_maj_ver="$OS_ID-$OS_MAJ_VERSION"
while [ $# -ge 1 ]; do
    declare opt="$1"
    shift
    case $opt in
        -c) config='t';;
        -d) deconfig='t';;
        -e) if [ $# -lt 2 ]; then oci_vcn_err "secondary private IP address option requires <IP address> <VNIC OCID>"; fi
            SEC_ADDRS+=($1); shift
            SEC_VNICS+=($1); shift
            ;;
        -n) if [ "$os_maj_ver" = "ol-6" ] || [ "$os_maj_ver" = "centos-6" ]; then
                oci_vcn_err "namespaces not supported on this os version ($os_ver)"
            fi
            if [ $# -ge 1 ] && ! [[ "$1" =~ ^\- ]]; then
                [ -z "$1" ] || NS_FORMAT="$1"
                shift
            fi
            USE_NS='t';;
        -r) START_SSHD='t'
            [ -n "$SSHD" ] || oci_vcn_err "missing sshd command";;
        -s) show='t';;
        -h) oci_vcn_help; exit 0;;
        -q) if [ -n "$DEBUG" ]; then oci_vcn_err "cannot specify quiet with verbose"; fi
            QUIET='t';;
        -v) if [ -n "$QUIET" ]; then oci_vcn_err "cannot specify verbose with quiet"; fi
            DEBUG='t';;
        -*) oci_vcn_err "unknown option $opt";;
    esac
done

[ -z "$START_SSHD" ] || [ -n "$USE_NS" ] || oci_vcn_err "cannot start sshd if namespace is not created"

[ $EUID -eq 0 ] || oci_vcn_err "must be run as root"

# read all metadata and ip config
oci_vcn_md_read
oci_vcn_read

# process options
if [ -n "$config" ]; then
    [ -z "$deconfig" ] || oci_vcn_err "conflicting options"
    oci_vcn_config
    [ -z "$show" ] || oci_vcn_read # reread if show
elif [ -n "$deconfig" ]; then
    if [ ${#SEC_ADDRS[@]} -gt 0 ]; then # just deconfig addrs
        oci_vcn_config_or_deconfig_sec_addrs
    else # deconfig all
        oci_vcn_deconfig_all
    fi
    [ -z "$show" ] || oci_vcn_read # reread if show
else
    show='t'
fi
[ -z "$show" ] || oci_vcn_show
]]> Oracle DBMS_SCHEDULER vs DBMS_JOB: pacote único para gerenciar, pausar e monitorar jobs https://furushima.com.br/blog/oracle-dbms_scheduler-vs-dbms_job-pacote-unico-para-gerenciar-pausar-e-monitorar-jobs/ Wed, 10 Sep 2025 22:11:24 +0000 https://furushima.com.br/?p=2855 Introdução

Em muitos ambientes Oracle, convivem dois mecanismos de agendamento: o DBMS_SCHEDULER (moderno) e o DBMS_JOB (legado). Cada um possui comandos, dicionários e semânticas próprios — “enabled" de um lado, “broken” do outro; DBA_SCHEDULER_* aqui, DBA_JOBS* ali; STOP_JOB vs. “matar sessão” etc.
O resultado, no dia a dia, é fricção operacional: consultas diferentes para a mesma pergunta, scripts paralelos para operações equivalentes, e uma curva de aprendizado desnecessária para tarefas simples como ver quem está rodando, habilitar/desabilitar e pausar um lote de jobs para uma janela de manutenção.

Esta solução nasce exatamente desse cenário. O objetivo é oferecer um ponto único e transparente para inventariar, monitorar e operar ambos os mecanismos sem complexidade.
Você passa a consultar uma visão consolidada (inventário e execução), e a executar um pacote único para ações comuns — seja um job Scheduler com nome, seja um DBMS_JOB numérico.


2) O que são DBMS_SCHEDULER e DBMS_JOB

DBMS_SCHEDULER (o mecanismo moderno)

Introduzido para substituir o DBMS_JOB, o DBMS_SCHEDULER oferece uma arquitetura rica e modular:

  • Jobs, Programs e Schedules separados, possibilitando reuso e governança.
  • Chains (fluxos com dependências), Windows e Job Classes.
  • Calendário expressivo por repeat_interval (calendar expressions).
  • Parada controlada (STOP_JOB), logging detalhado, priorização e integração com Resource Manager.
  • Dicionário amplo (DBA_SCHEDULER_JOBS, DBA_SCHEDULER_RUNNING_JOBS, etc.).

Em suma: mais recursos, rastreabilidade e controle fino. É o padrão recomendado para novas rotinas.


DBMS_JOB (o mecanismo legado)

O DBMS_JOB é mais simples e direto:

  • Cada job tem um número (ex.: 128), um comando WHAT (PL/SQL a executar), um NEXT_DATE e um INTERVAL (string).
  • A disponibilidade é representada por BROKEN = 'Y'|'N' em vez de ENABLED.
  • Não possui um comando nativo para parar execução em curso; na prática, usa-se o encerramento da sessão que executa o job.
  • Dicionário compacto (DBA_JOBS, DBA_JOBS_RUNNING).

Embora menos flexível, é comum que ambientes antigos ainda mantenham rotinas estáveis sob DBMS_JOB.


Vantagens de utilizar esta solução

1. Interface única e coerente

  • Views consolidadas para inventário (JOB_ADMIN_ALL_JOBS[_V]) e execução (JOB_ADMIN_RUNNING[_V]) que mesclam Scheduler e DBMS_JOB.
  • Colunas homogêneas: enabled sempre como TRUE/FALSE, datas e intervalos formatados nas versões “_V”.

2. Produtividade imediata

  • Uma consulta responde “o que tenho?”, “quando roda?”, “quem está rodando e há quanto tempo?”.
  • O operador não precisa lembrar se o job é Scheduler ou DBMS_JOB para consultar status ou executar ações.

3. Operação simples e segura

  • Habilitar/Desabilitar por um único procedimento (enable_job/disable_job), passando nome (Scheduler) ou número (DBMS_JOB).
  • Parada elegante: para Scheduler usa STOP_JOB(force => TRUE); para DBMS_JOB, encerra a sessão de execução antes de mudar o estado (RAC-aware).
  • Lote inteligente (set_jobs_by_pattern): aplique uma ação a um conjunto por LIKE, escolhendo tipo (Scheduler/DBMS_JOB/ANY) e se deve parar os ativos.

4. Observabilidade e padronização

  • Saídas de list_jobs e list_running_jobs são limpas e didáticas, integrando as duas tecnologias com o mesmo layout.
  • Facilita auditorias, health-checks e relatórios operacionais com menos scripts.

5. Governança simplificada

  • Role única (JOBDBMSSCHEDULERALL) e sinônimos públicos: padroniza o consumo entre times e ferramentas.
  • AUTHID DEFINER: quem usa não precisa de privilégio de DBA — basta receber a role.

6. Idempotência e baixa fricção de implantação

  • CREATE OR REPLACE em todos os objetos e checagens defensivas: reexecutar reinstala.
  • Compatível com RAC e com execução em PDB (quando aplicável).

7. Menor risco operacional

  • Mensagens claras e validações garantem que “job não encontrado” ou “nome ambíguo entre owners” sejam tratados com erros explicativos.
  • Em manutenção, p_stop_running => TRUE reduz inconsistências ao pausar um lote inteiro de forma controlada.

8. Porta de entrada para modernização

  • Ao dar visibilidade e controle unificado, a solução facilita migrações graduais de DBMS_JOB para DBMS_SCHEDULER, sem interrupção do dia a dia.


Faça o download do instalador pkg_job_admin no link abaixo e habilite a gestão unificada de jobs Oracle.


Download – script pkg_job_admin – ORACLEBaixar




Administração de jobs Oracle em um só lugar: Instalação e uso do pkg_job_admin

[ORCL.oracle@furushimait_labs ~]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Wed Sep 10 14:52:51 2025
Version 19.20.0.0.0

Copyright (c) 1982, 2022, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production
Version 19.20.0.0.0

SQL> @job_admin_setup_completo.sql

═════════════════════════════════════════════════════════════════════════════════════════════
Iniciando job_admin_setup_completo.sql
═════════════════════════════════════════════════════════════════════════════════════════════
Owner atual: SYS

PL/SQL procedure successfully completed.


── 1) Criando/Atualizando Views Consolidadas …

View created.


View created.


View created.


View created.

✓ Views criadas/atualizadas com sucesso.

── 2) Criando/Atualizando Pacote (SPEC) …

Package created.

No errors.

── 3) Criando/Atualizando Pacote (BODY) …

Package body created.

No errors.
✓ Pacote criado/atualizado com sucesso.

── 4) Segurança: ROLE, Grants e Sinônimos Públicos …
Role JOBDBMSSCHEDULERALL já existente.

PL/SQL procedure successfully completed.


Grant succeeded.


Grant succeeded.


Grant succeeded.


Grant succeeded.


Grant succeeded.

Sinônimos públicos criados/atualizados.

PL/SQL procedure successfully completed.

✓ Segurança configurada (ROLE + grants + sinônimos públicos).

── 5) Auto-Validação (não intrusiva) …
Pacote PKG_JOB_ADMIN sem erros de compilação.

PL/SQL procedure successfully completed.

Views acessíveis: JOB_ADMIN_ALL_JOBS e JOB_ADMIN_RUNNING OK.

PL/SQL procedure successfully completed.


── 6) Exemplos de Uso para referência  …

-- Inventário:
BEGIN
pkg_job_admin.list_jobs;                          -- todos os jobs
pkg_job_admin.list_jobs('DEMOAPP');               -- por owner
pkg_job_admin.list_jobs(p_like => 'JOB_%');       -- por padrão (LIKE)
END
/
-- Em execução agora:
BEGIN
pkg_job_admin.list_running_jobs;                       -- tudo
pkg_job_admin.list_running_jobs('DEMOAPP');            -- por owner
pkg_job_admin.list_running_jobs(p_like => 'SYNC_%');   -- por padrão (LIKE)
END
/
-- Operações pontuais:
-- SCHEDULER (por nome; owner opcional se único no banco)
-- BEGIN
--   pkg_job_admin.disable_job('DEMOAPP.JOB_ATUALIZA_INDICES', p_stop_running => TRUE)
--   pkg_job_admin.enable_job ('DEMOAPP.JOB_ATUALIZA_INDICES')
-- END
-- /
-- DBMS_JOB (por número; owner apenas para validar pertinência quando desejar)
-- BEGIN
--   pkg_job_admin.disable_job('128', p_owner => 'SYS', p_stop_running => TRUE)
--   pkg_job_admin.enable_job ('128', p_owner => 'SYS')
-- END
-- /
-- Lote por padrão (por tipo):
-- BEGIN
--   pkg_job_admin.set_jobs_by_pattern(
--     p_name_like    => 'JOB_SYNC_%',
--     p_enable       => FALSE,
--     p_owner        => 'DEMOAPP',
--     p_type         => pkg_job_admin.c_type_scheduler, -- SCHEDULER | DBMS_JOB | ANY
--     p_stop_running => TRUE
--   )
-- END
-- /
-- Visões consolidadas:
-- SELECT * FROM job_admin_all_jobs_v ORDER BY owner, job_type, job_name
-- SELECT * FROM job_admin_running_v  ORDER BY running_instance, job_type, job_name

═════════════════════════════════════════════════════════════════════════════════════════════
Conclusão: job_admin_setup_completo.sql executado.
Para conceder a ROLE a um usuário final, utilize:
GRANT JOBDBMSSCHEDULERALL TO nome_do_usuario
═════════════════════════════════════════════════════════════════════════════════════════════




O que o script cria

Objetos de dados (Views)

  • JOB_ADMIN_ALL_JOBS — Inventário unificado (SCHEDULER + DBMS_JOB).
  • JOB_ADMIN_RUNNING — Execução unificada no momento (SCHEDULER + DBMS_JOB).
  • JOB_ADMIN_ALL_JOBS_V — Versão “amigável” do inventário (datas e intervalos formatados).
  • JOB_ADMIN_RUNNING_V — Versão “amigável” da execução (intervalos formatados).

API (Package)

  • PKG_JOB_ADMIN — Procedimentos para listar, habilitar/desabilitar e controlar lotes.
    • list_jobs(p_owner, p_like)
    • list_running_jobs(p_owner, p_like)
    • set_job_enabled(p_job_identifier, p_enable, p_owner, p_stop_running)
    • enable_job(...) / disable_job(...)
    • set_jobs_by_pattern(p_name_like, p_enable, p_owner, p_type, p_stop_running)
    • Constantes: c_type_scheduler, c_type_dbms_job, c_type_any




Inventário consolidado, pronto para relatório

SELECT 
  owner, 
  job_type, 
  job_name, 
  enabled, 
  state, 
  next_run_date 
FROM 
  job_admin_all_jobs_v 
ORDER BY 
  owner, 
  job_type, 
  job_name;

Execução no momento (quem está rodando agora)

SELECT 
  owner, 
  job_type, 
  job_name, 
  running_instance, 
  elapsed_time 
FROM 
  job_admin_running_v 
ORDER BY 
  running_instance, 
  job_type, 
  job_name;





Habilitar/Desabilitar individualmente

-- DBMS_SCHEDULER por nome (com owner)
BEGIN
  pkg_job_admin.disable_job('DEMOAPP.JOB_XPTO_ETL_DIARIO', p_stop_running => TRUE);
  pkg_job_admin.enable_job ('DEMOAPP.JOB_XPTO_ETL_DIARIO');
END;
/


-- DBMS_JOB por número (com validação de owner opcional)
BEGIN
  pkg_job_admin.disable_job('128', p_owner => 'SYS', p_stop_running => TRUE);
  pkg_job_admin.enable_job ('128', p_owner => 'SYS');
END;
/





Habilitar/Desabilitar JOBS em lote 

BEGIN
  pkg_job_admin.set_jobs_by_pattern(
    p_name_like    => 'JOB_XPTO_%',
    p_enable       => FALSE,                            -- desativar todos que casem com o padrão
    p_owner        => 'DEMOAPP',                        -- opcional
    p_type         => pkg_job_admin.c_type_scheduler,   -- QUALQUER TIPO : SCHEDULER | DBMS_JOB | ANY
    p_stop_running => TRUE
  );
END;
/





Quais jobs existem e quando rodarão?

SELECT owner, job_type, job_name, enabled, state, next_run_date 
FROM   job_admin_all_jobs_v
ORDER  BY owner, job_type, job_name;


--  O que observar
--    • job_type: distingue SCHEDULER vs DBMS_JOB.
--    • enabled: “TRUE/FALSE” consolidado para ambos.
--    • state: útil para SCHEDULER (ex.: SCHEDULED, DISABLED).





Quais jobs contêm a palavra ‘XPTO’ no nome ou no comando?

SELECT owner, job_type, job_name, enabled, job_action
FROM   job_admin_all_jobs
WHERE  UPPER(job_name)   LIKE '%XPTO%'
   OR  UPPER(job_action) LIKE '%XPTO%'
ORDER  BY owner, job_name;








Qual o próximo agendamento dos jobs do meu schema de aplicação?

SELECT job_name, enabled, state, next_run_date
FROM   job_admin_all_jobs_v
WHERE  owner = 'DEMOAPP'
ORDER  BY job_name;






Quem está rodando agora e há quanto tempo?

SELECT owner, job_type, job_name, running_instance, elapsed_time
FROM   job_admin_running_v
ORDER  BY running_instance, job_type, job_name;





Agora vamos ver se o job JOB_XPTO_ETL_DIARIO está rodando e há quanto tempo

SELECT owner, job_type, job_name, elapsed_time
FROM   job_admin_running_v
WHERE  job_name = 'JOB_XPTO_ETL_DIARIO';

-- • Se vier linha, o job está ativo; elapsed_time mostra a duração no formato DD HH:MI:SS.





Quais jobs estão desabilitados, para uma revisão rápida?

SELECT owner, job_type, job_name, enabled
FROM   job_admin_all_jobs_v
WHERE  enabled = 'FALSE'
ORDER  BY owner, job_type, job_name;





Como usar o Pacote (exemplos passo a passo)

Todos os exemplos assumem que você possui a role JOBDBMSSCHEDULERALL.
Use os sinônimos públicos (pkg_job_admin) — não há necessidade de prefixar com schema.

-- Inventário

BEGIN
  pkg_job_admin.list_jobs;                    -- Listar TUDO!
  pkg_job_admin.list_jobs('DEMOAPP');         -- Procurar pelo OWNER
  pkg_job_admin.list_jobs(p_like => 'JOB_%'); -- Busca por jobs cujo nome contenha o padrão informado (equivalente ao LIKE).
END;
/



--- OUTPUT : 

=== JOBS (SCHEDULER) ===
DEMOAPP.JOB_XPTO_ETL_DIARIO | enabled=TRUE | state=SCHEDULED | next=2025-09-27 01:00:00 | action=BEGIN pkg_etl.run_daily; END;
DEMOAPP.JOB_SYNC_CLIENTES   | enabled=FALSE | state=DISABLED | next=- | action=BEGIN sync_clientes(); END;

=== JOBS (DBMS_JOB) ===
DEMOAPP.128 | enabled=TRUE | next=2025-09-11 03:00:00 | what=BEGIN antiga_rotina(); END;






Execução (quem está rodando) com leitura guiada

-- Agora vamos ver se o job XPTO está rodando e há quanto tempo

BEGIN
  pkg_job_admin.list_running_jobs(p_like => 'JOB_XPTO_%');
END;
/



--- OUTPUT : 

=== RUNNING (SCHEDULER) ===
DEMOAPP.JOB_XPTO_ETL_DIARIO | sid=123 | inst=1 | elapsed=00 00:07:32 | cpu=00 00:02:10

=== RUNNING (DBMS_JOB) ===
-- (vazio, se nada estiver executando)






Operações pontuais: habilitar/desabilitar

-- DBMS_SCHEDULER por nome (owner informado — mais explícito):

BEGIN
  -- desativar e forçar parada se estiver rodando
  pkg_job_admin.disable_job('DEMOAPP.JOB_XPTO_ETL_DIARIO', p_stop_running => TRUE);
  -- reativar
  pkg_job_admin.enable_job ('DEMOAPP.JOB_XPTO_ETL_DIARIO');
END;
/



--- DBMS_JOB por número (owner opcional, útil para validar pertinência):

BEGIN
  -- desativar e forçar parada se estiver rodando
  pkg_job_admin.disable_job('128', p_owner => 'DEMOAPP', p_stop_running => TRUE);
  -- reativar
  pkg_job_admin.enable_job ('128', p_owner => 'DEMOAPP');
END;
/



-- O que acontece por trás:
--   • SCHEDULER: STOP_JOB(..., force => TRUE) (se p_stop_running=>TRUE), seguido de DISABLE/ENABLE.
--   • DBMS_JOB: encerra sessão (se ativa) e marca BROKEN (NOT p_enable).






Operações em lote: desabilitar todos os “JOB_XPTO_%” do SCHEDULER

-- Cenário: janela de manutenção requer pausar rotinas XPTO do schema de aplicação.

--- Desativar
BEGIN
  pkg_job_admin.set_jobs_by_pattern(
    p_name_like    => 'JOB_XPTO_%',
    p_enable       => FALSE,                              -- desativar
    p_owner        => 'DEMOAPP',
    p_type         => pkg_job_admin.c_type_scheduler,     
    p_stop_running => TRUE                                -- encerrar active session job
  );
END;
/



--- Reativar
BEGIN
  pkg_job_admin.set_jobs_by_pattern(
    p_name_like    => 'JOB_XPTO_%',
    p_enable       => TRUE,                               -- reativar
    p_owner        => 'DEMOAPP',
    p_type         => pkg_job_admin.c_type_scheduler
  );
END;
/






Analisar o job ‘JOB_XPTO_ETL_DIARIO’ especificamente

-- 1. Está presente? Quando roda?

SELECT *
FROM   job_admin_all_jobs_v
WHERE  owner = 'DEMOAPP' AND job_name = 'JOB_XPTO_ETL_DIARIO';


-- 2. Está executando agora? Há quanto tempo?
SELECT running_instance, elapsed_time
FROM   job_admin_running_v
WHERE  owner = 'DEMOAPP' AND job_name = 'JOB_XPTO_ETL_DIARIO';

-- 3. Pausar com segurança (parar se ativo, depois desabilitar)
BEGIN
  pkg_job_admin.disable_job('DEMOAPP.JOB_XPTO_ETL_DIARIO', p_stop_running => TRUE);
END;
/

-- 4. Reativar
BEGIN
  pkg_job_admin.enable_job('DEMOAPP.JOB_XPTO_ETL_DIARIO');
END;
/





Qual a serventia dessa solução ?

Ambientes Oracle costumam conviver com dois mecanismos de agendamento: DBMS_SCHEDULER (moderno) e DBMS_JOB (legado). Quando precisamos inventariar, monitorar, habilitar/desabilitar ou gerenciar em lote ambos os tipos, a experiência comum é assimétrica e dispersa.
Este projeto entrega uma interface única e consistente para manipular os dois mundos:

  • Visões consolidadas para inventário e execução.
  • Um pacote PL/SQL com comandos simples e legíveis para operações pontuais e em lote.
  • Role e sinônimos públicos para padronizar o consumo de forma segura.






Abaixo consta o codigo inteiro do pacote pkg_job_admin

Download – script pkg_job_admin – ORACLEBaixar
-- =================================================================================================
--  job_admin_setup_completo.sql
--  Administração unificada de jobs no Oracle Database (DBMS_SCHEDULER e DBMS_JOB)
--  Autor: Carlos Furushima — Furushima IT
--  Direitos Autorais: Este script é propriedade intelectual de Furushima IT. Todos os direitos reservados.
--
--  OBJETIVO
--  --------
--  Fornecer uma interface única, consistente e profissional para:
--    • Inventariar jobs do SCHEDULER e do DBMS_JOB em visões consolidadas;
--    • Consultar jobs em execução (tempo decorrido e sessão, quando aplicável);
--    • Habilitar/Desabilitar jobs individualmente (por nome ou número);
--    • Habilitar/Desabilitar em lote por padrão de nome;
--    • Padronizar o consumo por meio de uma ROLE e sinônimos públicos.
--
--  O QUE É CRIADO
--  --------------
--    Views:
--      - JOB_ADMIN_ALL_JOBS      : inventário unificado (SCHEDULER + DBMS_JOB)
--      - JOB_ADMIN_RUNNING       : execução unificada (SCHEDULER + DBMS_JOB)
--      - JOB_ADMIN_ALL_JOBS_V    : inventário formatado para leitura humana
--      - JOB_ADMIN_RUNNING_V     : execução formatada para leitura humana
--
--    Pacote:
--      - PKG_JOB_ADMIN           : utilitários de listagem e (des)ativação unificada
--
--    Segurança e Acesso:
--      - ROLE JOBDBMSSCHEDULERALL com grants de SELECT/EXECUTE
--      - Sinônimos públicos para facilitar o uso por quem tiver a ROLE
--
--  PRÉ-REQUISITOS
--  --------------
--  • Executar com um usuário com privilégios para consultar dicionários DBA_* e GV$* e criar objetos.
--  • O pacote é AUTHID DEFINER (permissões do dono do pacote). Usuários finais só precisam da ROLE.
--
--  USO TÍPICO
--  ----------
--  -- Inventário:
--  BEGIN
--    pkg_job_admin.list_jobs;                       -- tudo
--    pkg_job_admin.list_jobs('DEMOAPP');            -- por owner
--    pkg_job_admin.list_jobs(p_like => 'JOB_%');    -- por padrão (LIKE)
--  END;
--  /
--
--  -- Executando agora:
--  BEGIN
--    pkg_job_admin.list_running_jobs;                       -- tudo
--    pkg_job_admin.list_running_jobs('DEMOAPP');            -- por owner
--    pkg_job_admin.list_running_jobs(p_like => 'SYNC_%');   -- por padrão (LIKE)
--  END;
--  /
--
--  -- Operações pontuais:
--  -- SCHEDULER (identificador por nome, owner opcional se único no banco)
--  -- BEGIN
--  --   pkg_job_admin.disable_job('DEMOAPP.JOB_ATUALIZA_INDICES', p_stop_running => TRUE);
--  --   pkg_job_admin.enable_job ('DEMOAPP.JOB_ATUALIZA_INDICES');
--  -- END;
--  -- /
--  --
--  -- DBMS_JOB (identificador numérico; owner opcional apenas para validar pertinência)
--  -- BEGIN
--  --   pkg_job_admin.disable_job('128', p_owner => 'SYS', p_stop_running => TRUE);
--  --   pkg_job_admin.enable_job ('128', p_owner => 'SYS');
--  -- END;
--  -- /
--
--  -- Lote por padrão (por tipo):
--  -- BEGIN
--  --   pkg_job_admin.set_jobs_by_pattern(
--  --     p_name_like    => 'JOB_SYNC_%',
--  --     p_enable       => FALSE,                               -- desativar
--  --     p_owner        => 'DEMOAPP',                           -- opcional
--  --     p_type         => pkg_job_admin.c_type_scheduler,      -- SCHEDULER | DBMS_JOB | ANY
--  --     p_stop_running => TRUE
--  --   );
--  -- END;
--  -- /
--
--  DICAS
--  -----
--  • O script é idempotente (CREATE OR REPLACE; checagens seguras). Pode ser executado mais de uma vez.
--  • Saída “limpa”: mensagens organizadas por PROMPT/DBMS_OUTPUT para auditoria e documentação.
-- =================================================================================================

SET FEEDBACK ON
SET SERVEROUTPUT ON SIZE UNLIMITED
SET VERIFY OFF

PROMPT
PROMPT ═════════════════════════════════════════════════════════════════════════════════════════════
PROMPT   Iniciando job_admin_setup_completo.sql
PROMPT ═════════════════════════════════════════════════════════════════════════════════════════════

-- -----------------------------------------------------------------------------------------------
-- 0) CONTEXTO — Mostra o usuário (owner) sob o qual os objetos serão criados
-- -----------------------------------------------------------------------------------------------
DECLARE
  l_user VARCHAR2(128) := USER;
BEGIN
  DBMS_OUTPUT.PUT_LINE('Owner atual: '||l_user);
END;
/

PROMPT
PROMPT ── 1) Criando/Atualizando Views Consolidadas …

-- ===============================================================================================
-- 1.1) JOB_ADMIN_ALL_JOBS
--      Consolida em uma única visão os jobs do DBMS_SCHEDULER e do DBMS_JOB.
--      Observações de tipos:
--        • next_run_date / last_start_date: TIMESTAMP WITH TIME ZONE (SCHEDULER) x DATE (DBMS_JOB)
--          -> o Oracle promove DATE para TIMESTAMP durante o UNION ALL (sem perda de funcionalidade).
--        • last_run_duration: INTERVAL no SCHEDULER; CAST de NULL para INTERVAL no DBMS_JOB.
--        • job_action / repeat_interval: normalizados para VARCHAR2 (até 4000) no DBMS_JOB.
-- ===============================================================================================
CREATE OR REPLACE VIEW job_admin_all_jobs AS
    SELECT owner,
           job_name,
           'SCHEDULER'               AS job_type,
           CASE WHEN enabled = 'TRUE' THEN 'TRUE' ELSE 'FALSE' END AS enabled,
           state,
           next_run_date,                                -- TIMESTAMP WITH TIME ZONE
           last_start_date,                              -- TIMESTAMP WITH TIME ZONE
           last_run_duration,                            -- INTERVAL DAY TO SECOND
           job_action,                                   -- VARCHAR2/CLOB (na maioria dos casos, até 4000)
           repeat_interval                               -- VARCHAR2
      FROM dba_scheduler_jobs
  UNION ALL
    SELECT schema_user                                   AS owner,
           TO_CHAR(job)                                  AS job_name,
           'DBMS_JOB'                                    AS job_type,
           CASE broken WHEN 'Y' THEN 'FALSE' ELSE 'TRUE' END AS enabled,
           CAST(NULL AS VARCHAR2(30))                    AS state,
           next_date,                                    -- DATE (promovido a TIMESTAMP no UNION)
           last_date                                     AS last_start_date, -- DATE
           CAST(NULL AS INTERVAL DAY TO SECOND)          AS last_run_duration,
           SUBSTR(what,     4000)                        AS job_action,      -- LONG -> VARCHAR2
           SUBSTR(interval, 4000)                        AS repeat_interval  -- LONG -> VARCHAR2
      FROM dba_jobs
;

-- ===============================================================================================
-- 1.2) JOB_ADMIN_RUNNING
--      Consolida os jobs em execução. Para DBMS_JOB, calcula elapsed pelo logon_time da sessão.
--      Observações:
--        • cpu_used não se aplica ao DBMS_JOB; representa-se com NULL (cast para INTERVAL).
-- ===============================================================================================
CREATE OR REPLACE VIEW job_admin_running AS
    SELECT owner,
           job_name,
           'SCHEDULER'               AS job_type,
           session_id,
           running_instance,
           elapsed_time,                                 -- INTERVAL
           cpu_used                                      -- INTERVAL
      FROM dba_scheduler_running_jobs
  UNION ALL
    SELECT j.schema_user           AS owner,
           TO_CHAR(r.job)          AS job_name,
           'DBMS_JOB'              AS job_type,
           r.sid                   AS session_id,
           s.inst_id               AS running_instance,
           NUMTODSINTERVAL(TRUNC((SYSDATE - s.logon_time)*86400),'SECOND') AS elapsed_time,
           CAST(NULL AS INTERVAL DAY TO SECOND)          AS cpu_used
      FROM dba_jobs_running r
      JOIN gv$session s ON s.sid = r.sid
      JOIN dba_jobs j   ON j.job = r.job
;

-- ===============================================================================================
-- 1.3) JOB_ADMIN_ALL_JOBS_V — Versão “amigável” (formatos para leitura humana)
-- ===============================================================================================
CREATE OR REPLACE VIEW job_admin_all_jobs_v AS
SELECT owner, job_name, job_type, enabled, state,
       TO_CHAR(next_run_date,'YYYY-MM-DD HH24:MI:SS')      AS next_run_date,
       TO_CHAR(last_start_date,'YYYY-MM-DD HH24:MI:SS')    AS last_start_date,
       CASE WHEN last_run_duration IS NULL THEN '-' ELSE
         EXTRACT(DAY FROM last_run_duration)||' '||
         LPAD(EXTRACT(HOUR FROM last_run_duration),2,'0')||':'||
         LPAD(EXTRACT(MINUTE FROM last_run_duration),2,'0')||':'||
         LPAD(TRUNC(EXTRACT(SECOND FROM last_run_duration)),2,'0')
       END AS last_run_duration,
       job_action, repeat_interval
  FROM job_admin_all_jobs
;

-- ===============================================================================================
-- 1.4) JOB_ADMIN_RUNNING_V — Versão “amigável” (formatos para leitura humana)
-- ===============================================================================================
CREATE OR REPLACE VIEW job_admin_running_v AS
SELECT owner, job_name, job_type, session_id, running_instance,
       CASE WHEN elapsed_time IS NULL THEN '-' ELSE
         EXTRACT(DAY FROM elapsed_time)||' '||
         LPAD(EXTRACT(HOUR FROM elapsed_time),2,'0')||':'||
         LPAD(EXTRACT(MINUTE FROM elapsed_time),2,'0')||':'||
         LPAD(TRUNC(EXTRACT(SECOND FROM elapsed_time)),2,'0')
       END AS elapsed_time,
       CASE WHEN cpu_used IS NULL THEN '-' ELSE
         EXTRACT(DAY FROM cpu_used)||' '||
         LPAD(EXTRACT(HOUR FROM cpu_used),2,'0')||':'||
         LPAD(EXTRACT(MINUTE FROM cpu_used),2,'0')||':'||
         LPAD(TRUNC(EXTRACT(SECOND FROM cpu_used)),2,'0')
       END AS cpu_used
  FROM job_admin_running
;

PROMPT ✓ Views criadas/atualizadas com sucesso.

PROMPT
PROMPT ── 2) Criando/Atualizando Pacote (SPEC) …

-- =================================================================================================
-- 2) ESPECIFICAÇÃO DO PACOTE — PKG_JOB_ADMIN
--    Contém constantes de tipo e procedimentos públicos de listagem e (des)ativação unificada.
-- =================================================================================================
CREATE OR REPLACE PACKAGE pkg_job_admin AUTHID DEFINER AS
  -- Constantes para filtro por tipo
  c_type_scheduler CONSTANT VARCHAR2(11) := 'SCHEDULER';
  c_type_dbms_job  CONSTANT VARCHAR2(8)  := 'DBMS_JOB';
  c_type_any       CONSTANT VARCHAR2(3)  := 'ANY';

  -- Listagem de jobs (inventário)
  PROCEDURE list_jobs(
    p_owner IN VARCHAR2 DEFAULT NULL,   -- filtra por owner
    p_like  IN VARCHAR2 DEFAULT NULL    -- filtra por padrão (LIKE)
  );

  -- Listagem de jobs em execução
  PROCEDURE list_running_jobs(
    p_owner IN VARCHAR2 DEFAULT NULL,   -- filtra por owner
    p_like  IN VARCHAR2 DEFAULT NULL    -- filtra por padrão (LIKE)
  );

  -- Habilita/Desabilita um job (identificador por nome SCHEDULER ou número DBMS_JOB)
  PROCEDURE set_job_enabled(
    p_job_identifier IN VARCHAR2,       -- 'OWNER.JOB_NAME' | 'JOB_NAME' | '123' (DBMS_JOB)
    p_enable         IN BOOLEAN,        -- TRUE = ENABLE; FALSE = DISABLE
    p_owner          IN VARCHAR2 DEFAULT NULL,  -- para SCHEDULER sem owner único ou DBMS_JOB para validar owner
    p_stop_running   IN BOOLEAN DEFAULT FALSE   -- encerra execução corrente (se houver)
  );

  -- Açúcares sintáticos (conveniências)
  PROCEDURE enable_job(
    p_job_identifier IN VARCHAR2,
    p_owner          IN VARCHAR2 DEFAULT NULL,
    p_stop_running   IN BOOLEAN DEFAULT FALSE
  );

  PROCEDURE disable_job(
    p_job_identifier IN VARCHAR2,
    p_owner          IN VARCHAR2 DEFAULT NULL,
    p_stop_running   IN BOOLEAN DEFAULT TRUE
  );

  -- Habilita/Desabilita em lote por padrão de nome e tipo
  PROCEDURE set_jobs_by_pattern(
    p_name_like     IN VARCHAR2,                      -- ex: 'JOB_SYNC_%'
    p_enable        IN BOOLEAN,                       -- TRUE/FALSE
    p_owner         IN VARCHAR2 DEFAULT NULL,         -- opcional
    p_type          IN VARCHAR2 DEFAULT c_type_any,   -- SCHEDULER | DBMS_JOB | ANY
    p_stop_running  IN BOOLEAN DEFAULT FALSE
  );
END pkg_job_admin;
/
SHOW ERRORS

PROMPT
PROMPT ── 3) Criando/Atualizando Pacote (BODY) …

-- =================================================================================================
-- 3) CORPO DO PACOTE — PKG_JOB_ADMIN
--    Implementa utilitários de formatação, detecção de owner/instância, e operações de controle.
-- =================================================================================================
CREATE OR REPLACE PACKAGE BODY pkg_job_admin AS

  -- ---------------------------------------------------------------------------------------------
  -- Função auxiliar: formata INTERVAL DAY TO SECOND em 'DD HH24:MI:SS'
  -- ---------------------------------------------------------------------------------------------
  FUNCTION fmt_ds(p INTERVAL DAY TO SECOND) RETURN VARCHAR2 IS
    l_day  PLS_INTEGER; l_hour PLS_INTEGER; l_min PLS_INTEGER; l_sec PLS_INTEGER;
  BEGIN
    IF p IS NULL THEN RETURN '-'; END IF;
    l_day  := EXTRACT(DAY    FROM p);
    l_hour := EXTRACT(HOUR   FROM p);
    l_min  := EXTRACT(MINUTE FROM p);
    l_sec  := TRUNC(EXTRACT(SECOND FROM p));
    RETURN LPAD(l_day,2,'0')||' '||LPAD(l_hour,2,'0')||':'||LPAD(l_min,2,'0')||':'||LPAD(l_sec,2,'0');
  END fmt_ds;

  -- ---------------------------------------------------------------------------------------------
  -- Função auxiliar: TO_CHAR seguro para datas que podem ser NULL (retorna '-' no NULL)
  -- ---------------------------------------------------------------------------------------------
  FUNCTION to_char_nvl(p_date DATE) RETURN VARCHAR2 IS
  BEGIN
    RETURN CASE WHEN p_date IS NULL THEN '-' ELSE TO_CHAR(p_date,'YYYY-MM-DD HH24:MI:SS') END;
  END;

  -- ---------------------------------------------------------------------------------------------
  -- Monta o nome totalmente qualificado do job de SCHEDULER
  -- ---------------------------------------------------------------------------------------------
  FUNCTION sched_job_fqname(p_owner IN VARCHAR2, p_job_name IN VARCHAR2) RETURN VARCHAR2 IS
  BEGIN
    RETURN CASE WHEN p_owner IS NOT NULL THEN UPPER(p_owner)||'.'||UPPER(p_job_name) ELSE UPPER(p_job_name) END;
  END;

  -- ---------------------------------------------------------------------------------------------
  -- Solicita parada de job SCHEDULER, se estiver em execução (silencioso em falhas)
  -- ---------------------------------------------------------------------------------------------
  PROCEDURE stop_scheduler_if_running(p_owner IN VARCHAR2, p_job_name IN VARCHAR2) IS
    l_fq VARCHAR2(261) := sched_job_fqname(p_owner, p_job_name);
  BEGIN
    DBMS_SCHEDULER.STOP_JOB(job_name => l_fq, force => TRUE);
  EXCEPTION
    WHEN OTHERS THEN NULL;
  END;

  -- ---------------------------------------------------------------------------------------------
  -- Encerra sessão de DBMS_JOB, se houver (suporte RAC com @inst_id)
  -- ---------------------------------------------------------------------------------------------
  PROCEDURE kill_dbms_job_session(p_job_id IN NUMBER) IS
    l_sid     NUMBER;
    l_serial  NUMBER;
    l_inst    NUMBER;
    l_stmt    VARCHAR2(200);
  BEGIN
    SELECT s.sid, s.serial#, s.inst_id
      INTO l_sid, l_serial, l_inst
      FROM dba_jobs_running r
      JOIN gv$session s ON s.sid = r.sid
     WHERE r.job = p_job_id
       AND ROWNUM = 1;

    l_stmt := 'ALTER SYSTEM KILL SESSION '''||l_sid||','||l_serial||
              CASE WHEN l_inst IS NOT NULL THEN ',@'||l_inst ELSE NULL END||''' IMMEDIATE';
    EXECUTE IMMEDIATE l_stmt;
  EXCEPTION
    WHEN NO_DATA_FOUND THEN NULL;
    WHEN OTHERS THEN NULL;
  END;

  -- ---------------------------------------------------------------------------------------------
  -- Resolve owner de job SCHEDULER quando usuário não informou p_owner
  -- Lança erro se não encontrado ou se existir em múltiplos owners.
  -- ---------------------------------------------------------------------------------------------
  PROCEDURE resolve_scheduler(p_owner IN VARCHAR2, p_job_name IN VARCHAR2,
                              o_owner OUT VARCHAR2, o_job_name OUT VARCHAR2) IS
    l_cnt INTEGER;
  BEGIN
    o_job_name := UPPER(p_job_name);
    IF p_owner IS NOT NULL THEN o_owner := UPPER(p_owner); RETURN; END IF;

    SELECT COUNT(DISTINCT owner) INTO l_cnt
      FROM dba_scheduler_jobs
     WHERE job_name = o_job_name;

    IF l_cnt = 0 THEN
      RAISE NO_DATA_FOUND;
    ELSIF l_cnt > 1 THEN
      RAISE_APPLICATION_ERROR(-20002,
        'JOB_NAME existe em múltiplos owners. Informe p_owner. JOB_NAME='||o_job_name);
    ELSE
      SELECT owner INTO o_owner
        FROM dba_scheduler_jobs
       WHERE job_name = o_job_name
         AND ROWNUM = 1;
    END IF;
  END resolve_scheduler;

  -- ---------------------------------------------------------------------------------------------
  -- Listagem: inventário unificado
  -- ---------------------------------------------------------------------------------------------
  PROCEDURE list_jobs(p_owner IN VARCHAR2 DEFAULT NULL, p_like IN VARCHAR2 DEFAULT NULL) IS
  BEGIN
    DBMS_OUTPUT.PUT_LINE('=== JOBS (SCHEDULER) ===');
    FOR r IN (
      SELECT owner, job_name, enabled, state, next_run_date, job_action
        FROM dba_scheduler_jobs
       WHERE (p_owner IS NULL OR owner = UPPER(p_owner))
         AND (p_like  IS NULL OR job_name LIKE UPPER(p_like))
       ORDER BY owner, job_name
    ) LOOP
      DBMS_OUTPUT.PUT_LINE(r.owner||'.'||r.job_name||
                           ' | enabled='||r.enabled||
                           ' | state='||NVL(r.state,'-')||
                           ' | next='||to_char_nvl(CAST(r.next_run_date AS DATE))||
                           ' | action='||SUBSTR(r.job_action,1,60));
    END LOOP;

    DBMS_OUTPUT.PUT_LINE(CHR(10)||'=== JOBS (DBMS_JOB) ===');
    FOR r IN (
      SELECT schema_user AS owner, job AS job_id, DECODE(broken,'Y','FALSE','TRUE') AS enabled,
             next_date, what
        FROM dba_jobs
       WHERE (p_owner IS NULL OR schema_user = UPPER(p_owner))
         AND (p_like  IS NULL OR TO_CHAR(job) LIKE p_like OR UPPER(what) LIKE UPPER(p_like))
       ORDER BY schema_user, job
    ) LOOP
      DBMS_OUTPUT.PUT_LINE(r.owner||'.'||r.job_id||
                           ' | enabled='||r.enabled||
                           ' | next='||to_char_nvl(r.next_date)||
                           ' | what='||SUBSTR(r.what,1,60));
    END LOOP;
  END list_jobs;

  -- ---------------------------------------------------------------------------------------------
  -- Listagem: execução unificada
  -- ---------------------------------------------------------------------------------------------
  PROCEDURE list_running_jobs(p_owner IN VARCHAR2 DEFAULT NULL, p_like IN VARCHAR2 DEFAULT NULL) IS
  BEGIN
    DBMS_OUTPUT.PUT_LINE('=== RUNNING (SCHEDULER) ===');
    FOR r IN (
      SELECT owner, job_name, session_id, running_instance, elapsed_time, cpu_used
        FROM dba_scheduler_running_jobs
       WHERE (p_owner IS NULL OR owner = UPPER(p_owner))
         AND (p_like  IS NULL OR job_name LIKE UPPER(p_like))
       ORDER BY running_instance, job_name
    ) LOOP
      DBMS_OUTPUT.PUT_LINE(r.owner||'.'||r.job_name||
                           ' | sid='||r.session_id||
                           ' | inst='||r.running_instance||
                           ' | elapsed='||fmt_ds(r.elapsed_time)||
                           ' | cpu='||fmt_ds(r.cpu_used));
    END LOOP;

    DBMS_OUTPUT.PUT_LINE(CHR(10)||'=== RUNNING (DBMS_JOB) ===');
    FOR r IN (
      SELECT j.schema_user AS owner, r.job AS job_id, s.sid, s.serial#,
             s.inst_id AS running_instance,
             NUMTODSINTERVAL(TRUNC((SYSDATE - s.logon_time)*86400),'SECOND') AS elapsed_time,
             j.what
        FROM dba_jobs_running r
        JOIN gv$session s ON s.sid = r.sid
        JOIN dba_jobs j   ON j.job = r.job
       WHERE (p_owner IS NULL OR j.schema_user = UPPER(p_owner))
         AND (p_like  IS NULL OR TO_CHAR(r.job) LIKE p_like OR UPPER(j.what) LIKE UPPER(p_like))
       ORDER BY running_instance, job_id
    ) LOOP
      DBMS_OUTPUT.PUT_LINE(r.owner||'.'||r.job_id||
                           ' | sid='||r.sid||','||r.serial#||
                           ' | inst='||r.running_instance||
                           ' | elapsed='||fmt_ds(r.elapsed_time));
    END LOOP;
  END list_running_jobs;

  -- ---------------------------------------------------------------------------------------------
  -- Núcleo: habilita/desabilita por identificador (nome SCHEDULER ou número DBMS_JOB)
  -- ---------------------------------------------------------------------------------------------
  PROCEDURE set_job_enabled(
    p_job_identifier IN VARCHAR2,
    p_enable         IN BOOLEAN,
    p_owner          IN VARCHAR2 DEFAULT NULL,
    p_stop_running   IN BOOLEAN DEFAULT FALSE
  ) IS
    l_owner    VARCHAR2(128);
    l_job_name VARCHAR2(128);
    l_job_id   NUMBER;
  BEGIN
    -- 1) Tentar SCHEDULER (nome)
    BEGIN
      IF REGEXP_LIKE(p_job_identifier,'^\d+$') THEN RAISE NO_DATA_FOUND; END IF;

      IF INSTR(p_job_identifier,'.') > 0 THEN
        l_owner    := UPPER(REGEXP_SUBSTR(p_job_identifier,'^([^\.]+)'));
        l_job_name := UPPER(REGEXP_SUBSTR(p_job_identifier,'\.([^\.]+)$',1,1,NULL,1));
      ELSE
        l_job_name := UPPER(p_job_identifier);
        resolve_scheduler(p_owner, l_job_name, l_owner, l_job_name);
      END IF;

      -- valida existência
      DECLARE l_dummy PLS_INTEGER;
      BEGIN
        SELECT 1 INTO l_dummy
          FROM dba_scheduler_jobs
         WHERE owner = l_owner AND job_name = l_job_name AND ROWNUM = 1;
      END;

      IF p_stop_running THEN
        stop_scheduler_if_running(l_owner, l_job_name);
      END IF;

      IF p_enable THEN
        DBMS_SCHEDULER.ENABLE( sched_job_fqname(l_owner, l_job_name) );
      ELSE
        DBMS_SCHEDULER.DISABLE( sched_job_fqname(l_owner, l_job_name) );
      END IF;

      DBMS_OUTPUT.PUT_LINE('OK (SCHEDULER) '||
        sched_job_fqname(l_owner,l_job_name)||' => '||
        CASE WHEN p_enable THEN 'ENABLED' ELSE 'DISABLED' END);

      RETURN;
    EXCEPTION
      WHEN NO_DATA_FOUND THEN NULL; -- não era scheduler; tentar DBMS_JOB
    END;

    -- 2) Tentar DBMS_JOB (número)
    BEGIN
      l_job_id := TO_NUMBER(TRIM(p_job_identifier));

      -- valida existência (restringe owner se informado)
      DECLARE l_dummy2 PLS_INTEGER;
      BEGIN
        SELECT 1 INTO l_dummy2
          FROM dba_jobs
         WHERE job = l_job_id
           AND (p_owner IS NULL OR schema_user = UPPER(p_owner))
           AND ROWNUM = 1;
      END;

      IF p_stop_running THEN
        kill_dbms_job_session(l_job_id);
      END IF;

      DBMS_JOB.BROKEN(l_job_id, NOT p_enable);

      DBMS_OUTPUT.PUT_LINE('OK (DBMS_JOB) '||l_job_id||' => '||
        CASE WHEN p_enable THEN 'ENABLED' ELSE 'DISABLED' END);

      RETURN;
    EXCEPTION
      WHEN VALUE_ERROR    THEN NULL;
      WHEN INVALID_NUMBER THEN NULL;
      WHEN NO_DATA_FOUND  THEN NULL;
    END;

    -- 3) Não encontrado em nenhuma modalidade
    RAISE_APPLICATION_ERROR(-20001,
      'Job não encontrado como SCHEDULER (por nome) nem DBMS_JOB (por número): '||p_job_identifier);
  END set_job_enabled;

  -- Açúcares sintáticos
  PROCEDURE enable_job(
    p_job_identifier IN VARCHAR2,
    p_owner          IN VARCHAR2 DEFAULT NULL,
    p_stop_running   IN BOOLEAN  DEFAULT FALSE
  ) IS
  BEGIN
    set_job_enabled(p_job_identifier => p_job_identifier,
                    p_enable         => TRUE,
                    p_owner          => p_owner,
                    p_stop_running   => p_stop_running);
  END;

  PROCEDURE disable_job(
    p_job_identifier IN VARCHAR2,
    p_owner          IN VARCHAR2 DEFAULT NULL,
    p_stop_running   IN BOOLEAN  DEFAULT TRUE
  ) IS
  BEGIN
    set_job_enabled(p_job_identifier => p_job_identifier,
                    p_enable         => FALSE,
                    p_owner          => p_owner,
                    p_stop_running   => p_stop_running);
  END;

  -- ---------------------------------------------------------------------------------------------
  -- Habilita/Desabilita em lote por padrão (LIKE) e, opcionalmente, por tipo
  -- ---------------------------------------------------------------------------------------------
  PROCEDURE set_jobs_by_pattern(
    p_name_like     IN VARCHAR2,
    p_enable        IN BOOLEAN,
    p_owner         IN VARCHAR2 DEFAULT NULL,
    p_type          IN VARCHAR2 DEFAULT c_type_any,
    p_stop_running  IN BOOLEAN  DEFAULT FALSE
  ) IS
  BEGIN
    -- SCHEDULER
    IF UPPER(p_type) IN (c_type_any, c_type_scheduler) THEN
      FOR r IN (
        SELECT owner, job_name
          FROM dba_scheduler_jobs
         WHERE (p_owner IS NULL OR owner = UPPER(p_owner))
           AND job_name LIKE UPPER(p_name_like)
      ) LOOP
        set_job_enabled(r.owner||'.'||r.job_name, p_enable, NULL, p_stop_running);
      END LOOP;
    END IF;

    -- DBMS_JOB
    IF UPPER(p_type) IN (c_type_any, c_type_dbms_job) THEN
      FOR r IN (
        SELECT schema_user AS owner, job
          FROM dba_jobs
         WHERE (p_owner IS NULL OR schema_user = UPPER(p_owner))
           AND (TO_CHAR(job) LIKE p_name_like OR UPPER(what) LIKE UPPER(p_name_like))
      ) LOOP
        set_job_enabled(TO_CHAR(r.job), p_enable, r.owner, p_stop_running);
      END LOOP;
    END IF;
  END set_jobs_by_pattern;

END pkg_job_admin;
/
SHOW ERRORS

PROMPT ✓ Pacote criado/atualizado com sucesso.

PROMPT
PROMPT ── 4) Segurança: ROLE, Grants e Sinônimos Públicos …

-- =================================================================================================
-- 4.1) ROLE — criada apenas se não existir
-- =================================================================================================
DECLARE
  l_cnt INTEGER;
BEGIN
  SELECT COUNT(*) INTO l_cnt FROM dba_roles WHERE role = 'JOBDBMSSCHEDULERALL';
  IF l_cnt = 0 THEN
    EXECUTE IMMEDIATE 'CREATE ROLE JOBDBMSSCHEDULERALL';
    DBMS_OUTPUT.PUT_LINE('Role JOBDBMSSCHEDULERALL criada.');
  ELSE
    DBMS_OUTPUT.PUT_LINE('Role JOBDBMSSCHEDULERALL já existente.');
  END IF;
END;
/

-- =================================================================================================
-- 4.2) GRANTS — executar o pacote e consultar as views por meio da ROLE
-- =================================================================================================
GRANT EXECUTE ON pkg_job_admin        TO JOBDBMSSCHEDULERALL;
GRANT SELECT  ON job_admin_all_jobs   TO JOBDBMSSCHEDULERALL;
GRANT SELECT  ON job_admin_running    TO JOBDBMSSCHEDULERALL;
GRANT SELECT  ON job_admin_all_jobs_v TO JOBDBMSSCHEDULERALL;
GRANT SELECT  ON job_admin_running_v  TO JOBDBMSSCHEDULERALL;

-- =================================================================================================
-- 4.3) SINÔNIMOS PÚBLICOS — apontam para os objetos do OWNER atual
--     Observação: garantem uso uniforme via “public synonyms” para quem tiver a ROLE.
-- =================================================================================================
DECLARE
  l_owner VARCHAR2(128) := USER;
BEGIN
  EXECUTE IMMEDIATE 'CREATE OR REPLACE PUBLIC SYNONYM job_admin_all_jobs   FOR '||l_owner||'.job_admin_all_jobs';
  EXECUTE IMMEDIATE 'CREATE OR REPLACE PUBLIC SYNONYM job_admin_running    FOR '||l_owner||'.job_admin_running';
  EXECUTE IMMEDIATE 'CREATE OR REPLACE PUBLIC SYNONYM job_admin_all_jobs_v FOR '||l_owner||'.job_admin_all_jobs_v';
  EXECUTE IMMEDIATE 'CREATE OR REPLACE PUBLIC SYNONYM job_admin_running_v  FOR '||l_owner||'.job_admin_running_v';
  EXECUTE IMMEDIATE 'CREATE OR REPLACE PUBLIC SYNONYM pkg_job_admin        FOR '||l_owner||'.pkg_job_admin';
  DBMS_OUTPUT.PUT_LINE('Sinônimos públicos criados/atualizados.');
END;
/

PROMPT ✓ Segurança configurada (ROLE + grants + sinônimos públicos).

PROMPT
PROMPT ── 5) Auto-Validação (não intrusiva) …

-- =================================================================================================
-- 5.1) Verifica erros de compilação do pacote
-- =================================================================================================
DECLARE
  l_errs INTEGER;
BEGIN
  SELECT COUNT(*) INTO l_errs
    FROM user_errors
   WHERE name = 'PKG_JOB_ADMIN';

  IF l_errs = 0 THEN
    DBMS_OUTPUT.PUT_LINE('Pacote PKG_JOB_ADMIN sem erros de compilação.');
  ELSE
    DBMS_OUTPUT.PUT_LINE('ATENÇÃO: Encontrado(s) '||l_errs||' erro(s) em PKG_JOB_ADMIN:');
    FOR r IN (
      SELECT type, name, line, position, SUBSTR(text,1,200) AS text
        FROM user_errors
       WHERE name = 'PKG_JOB_ADMIN'
       ORDER BY sequence
    ) LOOP
      DBMS_OUTPUT.PUT_LINE(r.type||' '||r.name||' @'||r.line||':'||r.position||' - '||r.text);
    END LOOP;
  END IF;
END;
/

-- =================================================================================================
-- 5.2) Validação simples de acesso às views (sanidade)
-- =================================================================================================
DECLARE
  l_all NUMBER; l_run NUMBER;
BEGIN
  SELECT COUNT(*) INTO l_all FROM job_admin_all_jobs WHERE ROWNUM <= 1;
  SELECT COUNT(*) INTO l_run FROM job_admin_running  WHERE ROWNUM <= 1;
  DBMS_OUTPUT.PUT_LINE('Views acessíveis: JOB_ADMIN_ALL_JOBS e JOB_ADMIN_RUNNING OK.');
END;
/

PROMPT
PROMPT ── 6) Exemplos de Uso (para referência; copiar/colar quando necessário) …

PROMPT
PROMPT -- Inventário:
PROMPT BEGIN
PROMPT   pkg_job_admin.list_jobs;                          -- todos os jobs
PROMPT   pkg_job_admin.list_jobs('DEMOAPP');               -- por owner
PROMPT   pkg_job_admin.list_jobs(p_like => 'JOB_%');       -- por padrão (LIKE)
PROMPT END;
PROMPT /

PROMPT -- Em execução agora:
PROMPT BEGIN
PROMPT   pkg_job_admin.list_running_jobs;                       -- tudo
PROMPT   pkg_job_admin.list_running_jobs('DEMOAPP');            -- por owner
PROMPT   pkg_job_admin.list_running_jobs(p_like => 'SYNC_%');   -- por padrão (LIKE)
PROMPT END;
PROMPT /

PROMPT -- Operações pontuais:
PROMPT -- SCHEDULER (por nome; owner opcional se único no banco)
PROMPT -- BEGIN
PROMPT --   pkg_job_admin.disable_job('DEMOAPP.JOB_ATUALIZA_INDICES', p_stop_running => TRUE);
PROMPT --   pkg_job_admin.enable_job ('DEMOAPP.JOB_ATUALIZA_INDICES');
PROMPT -- END;
PROMPT -- /
PROMPT -- DBMS_JOB (por número; owner apenas para validar pertinência quando desejar)
PROMPT -- BEGIN
PROMPT --   pkg_job_admin.disable_job('128', p_owner => 'SYS', p_stop_running => TRUE);
PROMPT --   pkg_job_admin.enable_job ('128', p_owner => 'SYS');
PROMPT -- END;
PROMPT -- /

PROMPT -- Lote por padrão (por tipo):
PROMPT -- BEGIN
PROMPT --   pkg_job_admin.set_jobs_by_pattern(
PROMPT --     p_name_like    => 'JOB_SYNC_%',
PROMPT --     p_enable       => FALSE,
PROMPT --     p_owner        => 'DEMOAPP',
PROMPT --     p_type         => pkg_job_admin.c_type_scheduler, -- SCHEDULER | DBMS_JOB | ANY
PROMPT --     p_stop_running => TRUE
PROMPT --   );
PROMPT -- END;
PROMPT -- /

PROMPT -- Visões consolidadas:
PROMPT -- SELECT * FROM job_admin_all_jobs_v ORDER BY owner, job_type, job_name;
PROMPT -- SELECT * FROM job_admin_running_v  ORDER BY running_instance, job_type, job_name;

PROMPT
PROMPT ═════════════════════════════════════════════════════════════════════════════════════════════
PROMPT   Conclusão: job_admin_setup_completo.sql executado.
PROMPT   Para conceder a ROLE a um usuário final, utilize:
PROMPT     GRANT JOBDBMSSCHEDULERALL TO nome_do_usuario;
PROMPT ═════════════════════════════════════════════════════════════════════════════════════════════
]]> Oracle Cloud DBCS: Falha no Backup com ORA-28361 em Novo PDB sem Master Key (OPEN_NO_MASTER_KEY) https://furushima.com.br/blog/oracle-cloud-dbcs-falha-no-backup-com-ora-28361-em-novo-pdb-sem-master-key-open_no_master_key/ Sun, 13 Apr 2025 18:55:46 +0000 https://furushima.com.br/?p=2772 Ao realizar uma migração de um Pluggable Database (PDB), cujo ambiente de origem era on-premise e o destino foi a Oracle Cloud DBCS, identificamos uma falha durante a execução do backup nativo do DBCS. O erro apresentado foi o seguinte:

ORA-28361: master key not yet set

Esse erro ocorre, principalmente, quando o PDB de origem não possui criptografia TDE (Transparent Data Encryption) habilitada. Ao ser migrado para o ambiente DBCS, o PDB permanece com o status OPEN_NO_MASTER_KEY, o que impede a correta realização de operações como backup, entre outras funcionalidades que dependem da chave mestra (master key).

Neste artigo, abordaremos brevemente os conceitos fundamentais da criptografia TDE no Oracle, explicaremos por que esse problema ocorre e apresentaremos, na prática, o passo a passo necessário para solucionar o erro ORA-28361 e restabelecer o funcionamento completo do novo PDB no ambiente da Oracle Cloud.

Para um melhor entendimento deste tema, recomenda-se a leitura das seguintes notas técnicas oficiais disponíveis no My Oracle Support. Elas complementam este artigo com orientações detalhadas sobre o erro OPEN_NO_MASTER_KEY e os procedimentos corretos para ativação da chave de criptografia (master key) em PDBs na Oracle Cloud:

  • [OCI-C]: Newly Created PDB Inside The Container Database Shows Wallet Error “OPEN_NO_MASTER_KEY” (Doc ID 2443398.1)
  • Creating and Activating a Master Encryption Key for a PDB (in OCI and OCI-Classic) (Doc ID 2469398.1)
  • WALLET_STATUS is OPEN_NO_MASTER_KEY in new pdb (Doc ID 3028669.1)

Essas documentações oficiais fornecem instruções práticas e são altamente recomendadas, especialmente para ambientes DBCS em OCI que envolvem a criação de novos PDBs sem chave de criptografia ativa.

Para usar o Oracle Transparent Data Encryption (TDE) em um pluggable database (PDB), você deve criar e ativar uma master encryption key (chave mestra de criptografia) para o PDB.


O que é Transparent Data Encryption (TDE)?

O Transparent Data Encryption (TDE) é um recurso do Oracle Database que permite a criptografia de dados sensíveis armazenados em tabelas e tablespaces, com o objetivo de proteger essas informações contra acessos não autorizados.

Após criptografados, os dados são descriptografados de forma transparente no momento do acesso por usuários ou aplicações autorizadas. Isso significa que, para quem tem permissão, a leitura dos dados ocorre normalmente, sem necessidade de ações manuais para descriptografá-los.

O TDE é especialmente eficaz para proteger os dados armazenados em mídia física — também chamados de dados em repouso (data at rest) — em situações como perda, roubo ou acesso indevido ao meio de armazenamento (por exemplo, datafiles no sistema operacional).

Embora o Oracle Database utilize mecanismos robustos de autenticação, autorização e auditoria para proteger os dados internamente, esses mecanismos não se aplicam diretamente aos arquivos físicos de dados no sistema operacional. Para isso, o TDE atua como uma camada adicional de segurança, criptografando os dados diretamente nesses arquivos.

A fim de evitar a descriptografia não autorizada, o TDE armazena as chaves de criptografia em um módulo de segurança externo ao banco de dados, denominado keystore (repositório de chaves).

Como parte da implementação do TDE, é possível configurar o Oracle Key Vault, uma solução que permite o gerenciamento centralizado dos keystores (também chamados de virtual wallets no contexto do Oracle Key Vault) em toda a infraestrutura da organização.

Por exemplo, é possível carregar um software keystore no Oracle Key Vault, migrar o banco de dados para utilizá-lo como keystore padrão, e então compartilhar seu conteúdo com outros nós do Oracle Real Application Clusters (Oracle RAC) — primários e de contingência (standby) —, otimizando assim as operações administrativas diárias em ambientes com dados criptografados.

________

________

O armazenamento da chave mestra (master key) pode ser realizado de duas formas: localmente (dentro do servidor de banco de dados), por meio do Oracle Wallet, ou de maneira centralizada e segura (externa ao servidor de banco de dados), utilizando o Oracle Key Vault. Ambos os mecanismos têm como finalidade armazenar e proteger a chave mestra do banco de dados.

A chave mestra é a chave principal dentro da arquitetura de criptografia TDE (Transparent Data Encryption). Ela é utilizada para criptografar as chaves de dados, também chamadas de data encryption keys, que são as responsáveis diretas por criptografar os dados sensíveis armazenados no banco de dados — como tabelas, tablespaces, backups e outros objetos persistentes.

Essa abordagem de segurança baseada em múltiplos níveis de chaves garante que, mesmo que os arquivos físicos do banco de dados sejam acessados indevidamente, os dados permanecerão protegidos, desde que a chave mestra não esteja acessível.

________

A seguir, apresentaremos o passo a passo para criar e ativar a master key no novo PDB, além de realizar a recriação do wallet em modo AUTOLOGIN.

Listagem de jobs com status “Failure” no DBCS utilizando o comando dbcli

[root@database ~]# dbcli list-jobs | grep -i Failure
a047a9ac-5fab-4495-8c0a-3d897404c5ee     Create Longterm Backup with TAG-DBTLongterm17443774703478Op for Db:BRAVEO in OSS:b4u6hISKttDARmxAARwI Friday, April 11, 2025, 10:38:39 BRT Failure

________

Após identificar o job com status “Failure”, é necessário consultar os logs correspondentes utilizando o comando dbcli. Para isso, use o parâmetro describe-job juntamente com o ID do job, que pode ser obtido na listagem anterior. Esse comando fornece detalhes completos sobre a execução do job, incluindo mensagens de erro e etapas realizadas.

[root@database ~]# dbcli describe-job -i  a047a9ac-5fab-4495-8c0a-3d897404c5ee  -j
{
  "jobId" : "a047a9ac-5fab-4495-8c0a-3d897404c5ee",
  "status" : "Failure",
  "message" : "DCS-10430:Request failed with ORA-* Errors:ORA-28361: master key not yet set \nError Stack :[RMAN-00601: fatal error in recovery manager,\n RMAN-03004: fatal error during execution of command,\n ORA-01480: trailing null missing from STR bind value,\n ORA-199",
  "errorCode" : "DCS-10430",
  "reports" : [ {
    "taskId" : "TaskSequential_29809",
    "taskName" : "task:TaskSequential_29809",
    "taskResult" : "",
    "startTime" : "April 11, 2025 10:38:40 AM BRT",
    "endTime" : "April 11, 2025 10:39:14 AM BRT",
    "status" : "Failure",
    "taskDescription" : null,
    "parentTaskId" : "TaskZLockWrapper_29808",
    "jobId" : "a047a9ac-5fab-4495-8c0a-3d897404c5ee",
    "tags" : [ ],
    "reportLevel" : "Error",
    "updatedTime" : "April 11, 2025 10:39:14 AM BRT",
    "message" : null
  }, {
    "taskId" : "TaskServiceRequest_29810",
    "taskName" : "Validate Database backup Configuration",
    "taskResult" : "",
    "startTime" : "April 11, 2025 10:38:40 AM BRT",
    "endTime" : "April 11, 2025 10:39:04 AM BRT",
    "status" : "Success",
    "taskDescription" : null,
    "parentTaskId" : "TaskSequential_29809",
    "jobId" : "a047a9ac-5fab-4495-8c0a-3d897404c5ee",
    "tags" : [ ],
    "reportLevel" : "CInfo",
    "updatedTime" : "April 11, 2025 10:39:04 AM BRT",
    "message" : null
  }, {
    "taskId" : "TaskParallel_29826",
    "taskName" : "Install object store swift module",
    "taskResult" : "",
    "startTime" : "April 11, 2025 10:38:42 AM BRT",
    "endTime" : "April 11, 2025 10:38:52 AM BRT",
    "status" : "Success",
    "taskDescription" : null,
    "parentTaskId" : "TaskSequential_29825",
    "jobId" : "a047a9ac-5fab-4495-8c0a-3d897404c5ee",
    "tags" : [ ],
    "reportLevel" : "CInfo",
    "updatedTime" : "April 11, 2025 10:38:52 AM BRT",
    "message" : null
  }, {
    "taskId" : "TaskServiceRequest_29811",
    "taskName" : "Backup Database",
    "taskResult" : "",
    "startTime" : "April 11, 2025 10:39:04 AM BRT",
    "endTime" : "April 11, 2025 10:39:14 AM BRT",
    "status" : "Failure",
    "taskDescription" : null,
    "parentTaskId" : "TaskSequential_29809",
    "jobId" : "a047a9ac-5fab-4495-8c0a-3d897404c5ee",
    "tags" : [ ],
    "reportLevel" : "Error",
    "updatedTime" : "April 11, 2025 10:39:14 AM BRT",
    "message" : null
  }, {
    "taskId" : "TaskSequential_29812",
    "taskName" : "task:TaskSequential_29812",
    "taskResult" : "DCS-10430:Request failed with ORA-* Errors:ORA-28361: master key not yet set \nError Stack :[RMAN-00601: fatal error in recovery manager,\n RMAN-03004: fatal error during execution of command,\n ORA-01480: trailing null missing from STR bind value,\n ORA-199",
    "startTime" : "April 11, 2025 10:39:04 AM BRT",
    "endTime" : "April 11, 2025 10:39:14 AM BRT",
    "status" : "Failure",
    "taskDescription" : null,
    "parentTaskId" : "TaskServiceRequest_29811",
    "jobId" : "a047a9ac-5fab-4495-8c0a-3d897404c5ee",
    "tags" : [ ],
    "reportLevel" : "Error",
    "updatedTime" : "April 11, 2025 10:39:14 AM BRT",
    "message" : null
  }, {
    "taskId" : "TaskZJsonRpcExt_29846",
    "taskName" : "Database backup",
    "taskResult" : "DCS-10430:Request failed with ORA-* Errors:ORA-28361: master key not yet set \nError Stack :[RMAN-00601: fatal error in recovery manager,\n RMAN-03004: fatal error during execution of command,\n ORA-01480: trailing null missing from STR bind value,\n ORA-199",
    "startTime" : "April 11, 2025 10:39:04 AM BRT",
    "endTime" : "April 11, 2025 10:39:14 AM BRT",
    "status" : "Failure",
    "taskDescription" : null,
    "parentTaskId" : "TaskSequential_29812",
    "jobId" : "a047a9ac-5fab-4495-8c0a-3d897404c5ee",
    "tags" : [ ],
    "reportLevel" : "Error",
    "updatedTime" : "April 11, 2025 10:39:14 AM BRT",
    "message" : null
  } ],
  "createTimestamp" : "April 11, 2025 10:38:39 AM BRT",
  "resourceList" : [ ],
  "description" : "Create Longterm Backup with TAG-DBTLongterm17443774703478Op for Db:BRAVEO in OSS:b4u6hISKttDARmxAARwI",
  "updatedTime" : "April 11, 2025 10:39:14 AM BRT",
  "percentageProgress" : "33%",
  "cause" : "Request has failed with ORA-* errors during the operation(s).",
  "action" : "Refer to RMAN logs for more information."
}

________

É importante ressaltar que ambos os passos apresentados anteriormente devem ser executados com o usuário root.

Agora, utilizando o usuário oracle, vamos consultar a visão dinâmica v$encryption_wallet para verificar o status da master key e entender melhor a situação atual do keystore.

$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Sun Apr 13 16:39:35 2025
Version 19.24.0.0.0

Copyright (c) 1982, 2024, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.24.0.0.0

SQL> col WRL_PARAMETER for a60
SQL> SELECT wrl_parameter, status, wallet_type FROM v$encryption_wallet;

WRL_PARAMETER                                               |STATUS                        |WALLET_TYPE
------------------------------------------------------------|------------------------------|--------------------
/opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde/           |OPEN                          |AUTOLOGIN
                                                            |OPEN_NO_MASTER_KEY            |AUTOLOGIN

                                                            
SQL> show pdbs ;

    CON_ID|CON_NAME                      |OPEN MODE |RESTRICTED
----------|------------------------------|----------|----------
         2|PDB$SEED                      |READ ONLY |NO
         3|PDB                           |READ WRITE|NO

________

Vamos destacar alguns pontos importantes com base no resultado obtido a partir da consulta à view v$encryption_wallet:

A consulta retornou duas linhas. A primeira linha representa o CDB (Container Database), enquanto as demais linhas representam os PDBs (Pluggable Databases).

Neste caso específico, há apenas um PDB criado, portanto foi retornada uma única linha adicional, cujo status é OPEN_NO_MASTER_KEY. Isso indica que a master key ainda não foi criada ou ativada para esse PDB.

Ao executar o comando SHOW PDBS, é possível visualizar tanto o PDB que precisa da ativação da chave quanto o PDB$SEED. Este último, no entanto, não é considerado no processo, pois trata-se de um template padrão utilizado apenas como base para a criação de novos PDBs, não sendo utilizado diretamente para armazenamento de dados ou operações administrativas.

O que significa o status OPEN_NO_MASTER_KEY no Oracle Database?

No Oracle Database, o status OPEN_NO_MASTER_KEY indica que o keystore (repositório de chaves) está aberto, porém nenhuma chave mestra de criptografia (master encryption key) foi criada ou ativada para o banco de dados atual.​

Esse status é comum em ambientes multitenant, onde um Pluggable Database (PDB) foi recentemente criado ou clonado, mas ainda não possui sua própria chave mestra de criptografia. Mesmo que o keystore esteja acessível, a ausência de uma chave mestra impede operações que dependem de criptografia, como backups, exportações de dados e acesso a dados criptografados.​

Por que cada PDB requer sua própria chave mestra?

Em um ambiente multitenant, cada PDB é isolado e pode ter requisitos de segurança distintos. Portanto, o Oracle Database permite que cada PDB tenha sua própria chave mestra de criptografia, mesmo quando todos compartilham um único keystore. Isso proporciona uma gestão mais granular da segurança e facilita operações como rotação de chaves e exportação/importação de PDBs.​

Neste exemplo, estamos utilizando o Oracle Wallet como forma de armazenamento da master key, o que significa que a chave é armazenada localmente, no próprio servidor de banco de dados. Para localizar o caminho do wallet, é possível verificar o arquivo sqlnet.ora ou consultar o parâmetro da instância de banco de dados wallet_root.

$ cat $ORACLE_HOME/network/admin/sqlnet.ora | grep -i WALLET
ENCRYPTION_WALLET_LOCATION=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=/opt/oracle/dcs/commonstore/wallets/BRAVEO_DB2/tde)))


$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Sun Apr 13 16:39:35 2025
Version 19.24.0.0.0

Copyright (c) 1982, 2024, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.24.0.0.0

SQL> show parameter wallet_root

NAME                                 TYPE        VALUE
------------------------------------ ----------- --------------------------------------------------
wallet_root                          string      /opt/oracle/dcs/commonstore/wallets/ORCL_LAB

Com o banco de dados em operação, vamos renomear o arquivo cwallet.sso para cwallet.sso.old. Essa ação desativa o modo de acesso automático (AUTOLOGIN) ao wallet, exigindo que a abertura do keystore seja feita manualmente por meio de senha.

$ ls -la /opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde/cwallet.sso
-rw------- 1 oracle oinstall 9958 Apr 11 15:13 /opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde/cwallet.sso

$ mv /opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde/cwallet.sso /opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde/cwallet.sso.old

$ ls -la /opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde/cwallet.sso*
-rw------- 1 oracle oinstall 9958 Apr 11 15:13 /opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde/cwallet.sso.old

Após a desativação do AUTOLOGIN da wallet, acessaremos o PDB em questão para criar sua própria master key. Nesse passo, será necessário informar a senha do keystore. Para fins de padronização e facilidade de gestão, utilizaremos a mesma senha já definida para a master key do CDB.

SQL> alter session set container=PDB;

Session altered.

SQL> ADMINISTER KEY MANAGEMENT SET KEYSTORE open IDENTIFIED BY "Wallet_Password_Here";

keystore altered.

SQL> administer key management set key identified by  "Wallet_Password_Here" with backup;

keystore altered.

SQL> col WRL_PARAMETER for a60
SQL> SELECT wrl_parameter, status, wallet_type FROM v$encryption_wallet;

WRL_PARAMETER                                               |STATUS                        |WALLET_TYPE
------------------------------------------------------------|------------------------------|--------------------
                                                            |OPEN                          |PASSWORD

Após a criação da master key do PDB, o próximo passo é recriar o AUTOLOGIN da wallet. Para isso, será necessário informar a senha do keystore. A fim de manter a padronização e facilitar a administração, utilizaremos a mesma senha previamente definida para a master key do CDB.

O último passo consiste em realizar um shutdown immediate seguido de um startup da instância do banco de dados. Em seguida, é recomendada uma nova consulta à view v$encryption_wallet para verificar se o status da wallet e da master key foi atualizado corretamente.

SQL> alter session set container=CDB$ROOT;

Session altered.

SQL>  administer key management create AUTO_LOGIN keystore from keystore '/opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde' identified by  "Wallet_Password_Here" ;

keystore altered.

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL>
SQL> startup;
ORACLE instance started.

Total System Global Area 1.4361E+10 bytes
Fixed Size                  9151448 bytes
Variable Size            6710886400 bytes
Database Buffers         7616856064 bytes
Redo Buffers               24399872 bytes
Database mounted.
Database opened.
SQL>
SQL> col WRL_PARAMETER for a60
SQL> SELECT wrl_parameter, status, wallet_type FROM v$encryption_wallet;

WRL_PARAMETER                                                STATUS                         WALLET_TYPE
------------------------------------------------------------ ------------------------------ --------------------
/opt/oracle/dcs/commonstore/wallets/ORCL_LAB/tde             OPEN                           AUTOLOGIN
                                                             OPEN                           AUTOLOGIN

Entendendo os Arquivos do Oracle Wallet
Para facilitar a compreensão, vamos explicar o papel de cada arquivo presente no diretório onde o Oracle Wallet está armazenado. De forma geral, os dois principais arquivos são:

🔐 ewallet.p12

  • É o arquivo que representa a keystore, ou seja, o repositório seguro onde são armazenadas:
    • Chaves criptográficas (como a master key),
    • Senhas,
    • Certificados digitais e outros dados sensíveis.

🔓 cwallet.sso

  • É o arquivo responsável pelo Single Sign-On (SSO) do wallet.
  • Permite que o banco de dados abra automaticamente o keystore durante o processo de startup, sem necessidade de informar a senha manualmente.

Esses dois arquivos trabalham juntos para garantir segurança e praticidade no gerenciamento das chaves criptográficas dentro do Oracle Database.

$ ls -la | egrep -i '(cwallet\.sso|ewallet\.p12)$'
-rw------- 1 oracle oinstall 9958 Apr 11 15:13 cwallet.sso
-rw------- 1 oracle oinstall 9913 Apr 11 15:12 ewallet.p12

Com todos os passos anteriores concluídos, agora podemos reexecutar o processo de backup para validar a solução implementada.

]]> MySQL Migration: How to Migrate from AWS Amazon Aurora MySQL to OCI HeatWave MySQL with Minimal Downtime https://furushima.com.br/blog/mysql-migration-how-to-migrate-from-aws-amazon-aurora-mysql-to-oci-heatwave-mysql-with-minimal-downtime/ Wed, 26 Mar 2025 21:08:39 +0000 https://furushima.com.br/?p=2736 In this article, we will demonstrate—clearly and practically—how to perform a MySQL database migration with minimal downtime. For this example, our source environment will be Amazon Aurora MySQL 8.0.39, and the target environment will be OCI HeatWave MySQL 8.4.4.

Before initiating the migration procedure, it is essential to ensure that a few infrastructure prerequisites are properly configured and fully operational:

  • AWS and OCI infrastructures must be installed, configured, and up and running.
  • An existing Amazon Aurora MySQL cluster must be currently operational and serving as the production database (source environment).
  • An OCI HeatWave MySQL cluster must already be provisioned and configured, ready to receive the migrated data from Amazon Aurora. This will become the new production database (target environment).
  • Network connectivity between the Amazon Aurora MySQL and the OCI HeatWave MySQL instances must be properly established, specifically allowing traffic on the default MySQL port (3306).

The configuration of these prerequisites will not be covered in detail in this article. If you encounter difficulties during this stage or would like to understand each step more thoroughly, we recommend referring to the official documentation available at the link below:

Oracle – Migration Guide from Amazon Aurora to OCI HeatWave MySQL

This document provides a comprehensive guide, covering everything from setting up the AWS and OCI infrastructures to the detailed procedures that will be briefly summarized in this article. There, you will find in-depth explanations of the concepts that will be simplified here in order to keep this article concise and focused.

Below, we present a high-level flowchart outlining the migration process from a MySQL database currently hosted on AWS Amazon Aurora MySQL to the OCI HeatWave MySQL infrastructure.

The primary goal of this approach is to carry out the migration with the least amount of downtime possible. To achieve this, we will employ a technique that consists of two main stages:

1. Initial Data Migration (Baseline)

In this initial phase, the entire database (i.e., the full dataset) is migrated from the source (AWS Amazon Aurora MySQL) to the target (OCI HeatWave MySQL).
This process is performed using MySQL Shell, a powerful and reliable tool that ensures data consistency and integrity throughout the transfer.

2. Continuous Replication of Differential Data (Delta)

Following the baseline migration, a continuous replication process is established to capture and apply any changes that occur on the source database while the final cutover has not yet been completed.
This delta replication is achieved through the use of binary logs (binlogs)—files that record all transactions executed on the source MySQL database.

To enable this real-time replication between AWS Aurora and OCI HeatWave environments, we will utilize a feature known as the OCI HeatWave MySQL Channel. This feature establishes a direct and reliable connection between the two environments, allowing for ongoing synchronization of transactional data.

In practice, during the migration process, the OCI HeatWave MySQL environment will temporarily operate as a replica (slave) database, faithfully tracking all changes made in the primary (master) environment—Amazon Aurora.

Once all differential (delta) changes have been successfully replicated and both environments are fully synchronized, the only remaining step is to redirect the application servers (e.g., web servers, application servers, middleware, etc.) to the new production environment hosted on OCI HeatWave MySQL.
As a result, the only downtime experienced will be the brief period required to reconfigure these connection endpoints, ensuring a fast, safe, and low-impact transition for end users.

The final outcome will be a fully migrated and operational environment hosted on OCI HeatWave, with complete fidelity to the data and structure of the original Amazon Aurora environment, while also benefiting from the enhanced performance and scalability offered by HeatWave technology.

To enhance clarity and streamline the migration process, this article is divided into two main parts, outlining the key steps required to execute a successful migration from AWS Amazon Aurora MySQL to OCI MySQL HeatWave with minimal downtime.

Part 1: Export (AWS Aurora MySQL) and Import (OCI MySQL HeatWave)

In the first part of this article, we will provide a detailed explanation of how to export the database from the source environment (AWS Amazon Aurora MySQL) using MySQL Shell, a powerful and user-friendly tool that enables fast, secure, and consistent data exports.

Following the export, we will guide you step-by-step through the import process to transfer the extracted data into the target environment (OCI MySQL HeatWave).
This section will also include best practices and recommendations to ensure a successful and reliable import, along with important precautions to preserve data integrity throughout the process.

Part 2: Implementing the OCI HeatWave MySQL Channel (Real-Time MASTER-SLAVE Replication)

In the second part, we will explain in detail how to implement the OCI HeatWave MySQL Channel, which enables the establishment of real-time MASTER-SLAVE replication between the AWS Aurora MySQL (MASTER) and OCI MySQL HeatWave (SLAVE) environments.

This approach ensures that all transactions performed on the AWS Aurora MySQL instance are automatically and continuously replicated in real time to the OCI HeatWave MySQL database using binary logs (binlogs).
In doing so, the OCI HeatWave instance will remain synchronized with the source, allowing the final migration cutover to take place with minimal downtime.

Additionally, we will provide detailed instructions for configuring the replication channel, monitoring its status, and troubleshooting potential synchronization issues during the replication phase.

By the end of this article, you will be equipped with all the necessary information to perform a secure, consistent, and low-impact migration from AWS Amazon Aurora MySQL to OCI MySQL HeatWave.

To facilitate understanding, the following flowchart clearly illustrates the steps that will be demonstrated in practice throughout this article.

Before we begin the practical export and import procedures using MySQL Shell, it is essential to ensure that the following parameters are properly configured and enabled in the source environment (AWS Amazon Aurora MySQL):

gtid_mode = ON
enforce-gtid-consistency = ON
log_bin = ON
binlog_format = ROW
log_slave_updates = ON

These parameters are mandatory to ensure that GTID-based replication (Global Transaction Identifiers) and binary logging are correctly enabled, thereby supporting a reliable, consistent, and compliant migration to the OCI HeatWave MySQL environment.

For more detailed information, refer to the official documentation below:

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_LogAccess.MySQL.BinaryFormat.html

EXPORT – util.dumpschemas

Export

In this step, we will perform the export (dump) of the npx database.
The resulting dump file will be stored in the directory /DUMP/NPX/.

Additionally, specific parameters will be used to ensure full compatibility of the dump with the target environment, OCI MySQL HeatWave.

util.dumpSchemas(
  ["npx"],
  "/DUMP/NPX/",
  {
    threads: 60,
    ocimds: true,
    compatibility: [
      "skip_invalid_accounts",
      "strip_restricted_grants",
      "ignore_wildcard_grants",
      "strip_definers",
      "strip_invalid_grants",
      "create_invisible_pks"    ],
    consistent: true
  }
);

Explanation of the Parameters Used in the util.dumpSchemas Command

util.dumpSchemas

A MySQL Shell command used to generate a database dump (data export).

["npx"]

Specifies the name of the database to be exported.

"/DUMP/NPX/"

The directory path where the generated dump files will be stored.

threads: 60

Defines the number of parallel threads used during the export. In this case, 60 concurrent processes will be executed to speed up the dump operation.

ocimds: true

Automatically optimizes the export for full compatibility with OCI MySQL Database Service (MDS) or OCI MySQL HeatWave.

Parameters in the compatibility Field:

  • skip_invalid_accounts
    Skips invalid or unsupported user accounts during the export to avoid compatibility issues with the target.
  • strip_restricted_grants
    Removes restricted privileges that are not supported by the target MySQL environment.
  • ignore_wildcard_grants
    Ignores user grants created using wildcards (e.g., %), enhancing security and preventing potential permission issues on the target system.
  • strip_definers
    Removes specific DEFINER clauses from objects such as views, stored procedures, and triggers, preventing errors if the definer user does not exist on the target environment.
  • strip_invalid_grants
    Strips out any invalid or incompatible privilege definitions that may cause conflicts in the destination system.
  • create_invisible_pks
    Automatically creates invisible primary keys on tables that lack one, ensuring compatibility with platforms like OCI HeatWave, which may require primary keys for certain operations.

consistent: true

Ensures that the dump is transactionally consistent, meaning it reflects the exact state of the database at a single point in time, thus avoiding inconsistencies during the export process.

IMPORT – util.loadDump

Import

In this step, we will perform the import of the previously generated dump into the npx database.
The dump files to be imported are located in the directory /DUMP/NPX/.

To speed up the process, we will use 60 parallel threads and the ignoreVersion parameter, which allows the import to proceed even when there are version differences between the source and target MySQL instances.

The target database will be explicitly defined using the schema parameter, which in this case is also named npx.

It is important to note that in MySQL, the term schema is synonymous with database name.

util.loadDump(
  "/DUMP/NPX",
  {
    threads: 60,
    ignoreVersion: true,
	  schema: 'npx'
  }
);

Explanation of the Parameters Used in the util.loadDump Command

util.loadDump

A MySQL Shell command used to load (import) a previously exported dump into the target database.

"/DUMP/NPX"

Specifies the directory path where the dump files to be imported are located.

threads: 60

Indicates the number of parallel threads used during the import process. In this example, 60 concurrent threads will be used to speed up data loading.

ignoreVersion: true

Ignores version differences between the source database (where the dump was generated) and the target database. This allows the import to proceed even if there are minor version mismatches.

schema: 'npx'

Explicitly defines the name of the target database (schema) where the data will be imported. In this case, the target schema is npx.

Now that we have a clear understanding of how to perform the export and import procedures, let’s walk through the practical execution of these steps in a real-world lab environment.

Execution export – util.dumpschemas

  MySQL  XXXXXXXXX-producao-clone.c4xlg1kbktwa.us-west-2.rds.amazonaws.com:3306 ssl  JS > util.dumpSchemas(
                                             ->   ["npx"],
                                             ->   "/DUMP/NPX/",
                                             ->   {
                                             ->     threads: 60,
                                             ->     ocimds: true,
                                             ->     compatibility: [
                                             ->       "skip_invalid_accounts",
                                             ->       "strip_restricted_grants",
                                             ->       "ignore_wildcard_grants","strip_definers",
                                             ->       "strip_invalid_grants","create_invisible_pks"    ],
                                             ->     consistent: true
                                             ->   }
                                             -> );
                                             ->
NOTE: The 'targetVersion' option is set to 9.1.0. This version supports the SET_ANY_DEFINER privilege, using the 'strip_definers' compatibility option is unnecessary.
NOTE: Backup lock is not available to the account 'tksmaster'@'%' and DDL changes will not be blocked. The dump may fail with an error if schema changes are made while dumping.
Acquiring global read lock
WARNING: The current user lacks privileges to acquire a global read lock using 'FLUSH TABLES WITH READ LOCK'. Falling back to LOCK TABLES...
Table locks acquired
Initializing - done
1 schemas will be dumped and within them 276 tables, 0 views, 5 routines.
Gathering information - done
All transactions have been started
Global read lock has been released
NOTE: When migrating to MySQL HeatWave Service, please always use the latest available version of MySQL Shell.
Checking for compatibility with MySQL HeatWave Service 9.1.0
Checking for potential upgrade issues.
The MySQL server at
beecare-producao-clone.c4xlg1kbktwa.us-west-2.rds.amazonaws.com:3306, version
8.0.39 - 2f855dc7, will now be checked for compatibility issues for upgrade to
MySQL 9.1.0.

WARNING: Upgrading MySQL Server from version 8.0.39 to 9.1.0 is not supported.
Please consider running the check using the following option: targetVersion=8.4

1) Checks for foreign keys not referencing a full unique index
(foreignKeyReferences)
   No issues found

2) Checks for errors in column definitions (columnDefinition)
   No issues found

3) Checks for partitions by key using columns with prefix key indexes
(partitionsWithPrefixKeys)
   No issues found
Errors:   0
Warnings: 0
Notices:  0

No known compatibility errors or issues were found.
NOTE: Database `npx` had unsupported ENCRYPTION option commented out
NOTE: Function `npx`.`available_date` had definer clause removed
NOTE: Function `npx`.`available_date` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`GetEligibilityRecords` had definer clause removed
NOTE: Procedure `npx`.`GetEligibilityRecords` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`available_date_procedure` had definer clause removed
NOTE: Procedure `npx`.`available_date_procedure` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`SP_INSERT_PAYMENT_ADVICES` had definer clause removed
NOTE: Procedure `npx`.`SP_INSERT_PAYMENT_ADVICES` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`cadastar_payment_advice_partners` had definer clause removed
NOTE: Procedure `npx`.`cadastar_payment_advice_partners` had SQL SECURITY characteristic set to INVOKER
NOTE: Table `npx`.`migrations` does not have a Primary Key, this will be fixed when the dump is loaded
NOTE: Table `npx`.`password_resets` does not have a Primary Key, this will be fixed when the dump is loaded
NOTE: Table `npx`.`message_organization` does not have a Primary Key, this will be fixed when the dump is loaded
NOTE: Table `npx`.`message_menu` does not have a Primary Key, this will be fixed when the dump is loaded
Validating MySQL HeatWave Service compatibility - done

NOTE: One or more tables without Primary Keys were found.

      Missing Primary Keys will be created automatically when this dump is loaded.
      This will make it possible to enable High Availability in MySQL HeatWave Service DB System instance without application impact and without changes to the source database.
      Inbound Replication into a DB System HA instance will also be possible, as long as the instance has version 8.0.32 or newer. For more information, see https://docs.oracle.com/en-us/iaas/mysql-database/doc/creating-replication-channel.html.

Compatibility issues with MySQL HeatWave Service 9.1.0 were found and repaired. Please review the changes made before loading them.
Writing global DDL files
Writing schema metadata - done
Running data dump using 60 threads.
NOTE: Progress information uses estimated values and may not be accurate.
NOTE: Table statistics not available for `npx`.`password_securities`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`password_securities`;' first.
Writing DDL - done
Writing table metadata - done
Starting data dump
NOTE: Table statistics not available for `npx`.`incident_types`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`incident_types`;' first.
NOTE: Backup lock is not available to the account 'tksmaster'@'%' and DDL changes were not blocked. The DDL is consistent, the world may resume now.
NOTE: Table statistics not available for `npx`.`comercial_contracts`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`comercial_contracts`;' first.
NOTE: Table statistics not available for `npx`.`comercial_negotiations`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`comercial_negotiations`;' first.
NOTE: Table statistics not available for `npx`.`procedure_info_files`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`procedure_info_files`;' first.
NOTE: Table statistics not available for `npx`.`refute_approval_levels`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`refute_approval_levels`;' first.
NOTE: Table statistics not available for `npx`.`modules`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`modules`;' first.
NOTE: Table statistics not available for `npx`.`organization_payment_types`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`organization_payment_types`;' first.
110% (3.60G rows / ~3.26G rows), 33.50K rows/s, 25.84 MB/s uncompressed, 1.17 MB/s compressed
Dump duration: 03:17:25s
Total duration: 03:24:46s
Schemas dumped: 1
Tables dumped: 276
Uncompressed data size: 1.45 TB
Compressed data size: 413.88 GB
Compression ratio: 3.5
Rows written: 3597220261
Bytes written: 413.88 GB
Average uncompressed throughput: 122.12 MB/s
Average compressed throughput: 34.94 MB/s

Execution import – util.loadDump

MySQL  10.27.2.35:3306 ssl  JS > util.loadDump(
                               ->   "/DUMP/NPX",
                               ->   {
                               ->     threads: 60,
                               ->     ignoreVersion: true,
                               -> schema: 'npx'
                               ->   }
                               -> );
                               ->
Loading DDL and Data from '/DUMP/NPX' using 60 threads.
Opening dump - done
Target is MySQL 8.4.4-u3-cloud (MySQL HeatWave Service). Dump was produced from MySQL 8.0.39
WARNING: Destination MySQL version is different than the value of the 'targetVersion' option set when the dump was created: 9.1.0
Scanning metadata - done
Checking for pre-existing objects - done
NOTE: The dump contains tables without Primary Keys and it is loaded with the 'createInvisiblePKs' option set to true, Inbound Replication into an MySQL HeatWave Service DB System instance with High Availability can be used with this dump.
Executing common preamble SQL - done
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_tables`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker050]: Error processing table `npx`.`comercial_procedures`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker023]: Error processing table `npx`.`comercial_volumes`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_tables`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker046]: Error processing table `npx`.`payment_advice_partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker049]: Error processing table `npx`.`payment_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker043]: Error processing table `npx`.`payment_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker038]: Error processing table `npx`.`partner_configurations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker023]: Error processing table `npx`.`comercial_volumes`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_procedure_reference_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker021]: Error processing table `npx`.`partner_integration_windows`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker009]: Error processing table `npx`.`procedure_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker053]: Error processing table `npx`.`glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker037]: Error processing table `npx`.`protocol_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker025]: Error processing table `npx`.`document_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker059]: Error processing table `npx`.`rpa_tasks`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker003]: Error processing table `npx`.`authorizations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker015]: Error processing table `npx`.`comercial_contracts`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker035]: Error processing table `npx`.`reconcile_statement_index_data_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker021]: Error processing table `npx`.`partner_integration_windows`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker038]: Error processing table `npx`.`partner_connections`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker023]: Error processing table `npx`.`comercial_volumes`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker011]: Error processing table `npx`.`partner_integration_window_audits`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker013]: Error processing table `npx`.`procedure_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_procedure_reference_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker044]: Error processing table `npx`.`related_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker058]: Error processing table `npx`.`procedure_info_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker002]: Error processing table `npx`.`integration_window_logs`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker049]: Error processing table `npx`.`payment_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker025]: Error processing table `npx`.`document_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker040]: Error processing table `npx`.`partner_status_relations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker007]: Error processing table `npx`.`guide_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker004]: Error processing table `npx`.`document_paperless`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker031]: Error processing table `npx`.`organization_from_to_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker059]: Error processing table `npx`.`rpa_tasks`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker043]: Error processing table `npx`.`payment_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker037]: Error processing table `npx`.`protocol_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker003]: Error processing table `npx`.`authorizations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker009]: Error processing table `npx`.`procedure_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker053]: Error processing table `npx`.`glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker035]: Error processing table `npx`.`reconcile_statement_index_data_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker007]: Error processing table `npx`.`guide_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker013]: Error processing table `npx`.`procedure_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker037]: Error processing table `npx`.`protocol_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker011]: Error processing table `npx`.`erp_reconcile_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker025]: Error processing table `npx`.`document_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker031]: Error processing table `npx`.`organization_from_to_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker053]: Error processing table `npx`.`glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker007]: Error processing table `npx`.`guide_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker002]: Error processing table `npx`.`organizations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
Executing DDL - done
Executing view DDL - done
Starting data load
2 thds indexing - 100% (1.45 TB / 1.45 TB), 0.00 B/s (15.64K rows/s), 276 / 276 tables done
Building indexes - done
Executing common postamble SQL - done
43064 chunks (3.60G rows, 1.45 TB) for 276 tables in 1 schemas were loaded in 7 hours 44 min 26 sec (avg throughput 51.91 MB/s, 129.09K rows/s)
277 DDL files were executed in 16 sec.
Data load duration: 7 hours 44 min 26 sec
2 indexes were built in 1 min 21 sec.
Total duration: 7 hours 45 min 54 sec
0 warnings were reported during the load.

At this point in the article, we have the following consolidated scenario:
We have already performed a database export using the util.dumpSchemas command in the source environment (AWS Amazon Aurora MySQL), and a data import into the target environment (OCI HeatWave MySQL) using the util.loadDump command.

With this, we now move on to the second part of our article, where we will walk through the step-by-step configuration of the OCI HeatWave MySQL Channel.

This configuration will enable the creation of a MASTER/SLAVE replication setup between the two environments mentioned earlier—designating AWS Amazon Aurora MySQL as the MASTER and OCI HeatWave MySQL as its SLAVE replica.

As a result, all transactions executed on the Aurora MySQL database will be automatically replicated in real time to the OCI HeatWave MySQL instance.

At this stage, it is important to ensure that the replication-specific user has already been created in the source environment, that is, in the AWS Amazon Aurora MySQL database.
If this step has not yet been completed, use the commands below to create the user and grant the necessary replication privileges:

CREATE USER 'repuser'@'%' IDENTIFIED BY 'my_password';
GRANT REPLICATION SLAVE ON *.* TO 'repuser'@'%';

Verifying GTID Consistency Before Replication

When performing a database export using the util.dumpSchemas command, a special metadata file named @.json is automatically generated in the directory specified for storing the dump files.

This @.json file contains a comprehensive set of metadata, including critical information about the export process. Among the most important elements within this file is the GTID set (Global Transaction Identifiers), which plays a fundamental role in ensuring data consistency and the accurate tracking of replicated transactions.

It is strongly recommended to review and validate the contents of the @.json file prior to initiating the import process, as the GTID set recorded in this file will later be used during the replication configuration, particularly for the execution of the SET GTID_PURGED statement.

Failure to review or correctly apply the GTID information from this metadata file can result in common errors and may cause serious data consistency issues during the database migration and replication process.

[root@gateway-furushima-linux ~]# cd /DUMP/NPX/
[root@gateway-furushima-linux NPX]# pwd
/DUMP/NPX
[root@gateway-furushima-linux NPX]# cat @.json | grep -i '"gtidExecuted"'
    "gtidExecuted": "415d143e-3653-30b3-980b-657ad05d72bd:1-44171859",



[root@gateway-furushima-linux NPX]# mysql -u sys -p'#SENHA_DO_MYSQL#' -h 192.168.1.35  -P 3306
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 886
Server version: 8.4.4-u4-cloud MySQL Enterprise - Cloud

Copyright (c) 2000, 2024, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>  call sys.SET_GTID_PURGED("+415d143e-3653-30b3-980b-657ad05d72bd:1-44171859");
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW GLOBAL VARIABLES LIKE 'gtid_executed';
+---------------+-----------------------------------------------------------------------------------------------+
| Variable_name | Value                                                                                         |
+---------------+-----------------------------------------------------------------------------------------------+
| gtid_executed | 415d143e-3653-30b3-980b-657ad05d72bd:1-49842480,
df21fd43-067a-11f0-b189-020017028ccd:1-44462 |
+---------------+-----------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)

Using the SET_GTID_PURGED Command Correctly

When executing the SET_GTID_PURGED command, it is essential to strictly follow the format shown below to prevent replication errors:


CALL sys.SET_GTID_PURGED("+<gtidSet>");

Practical Example:

CALL sys.SET_GTID_PURGED("+415d143e-3653-30b3-980b-657ad05d72bd:1-44171859");

Special Attention to the “+” Symbol

It is mandatory to include the plus sign (“+”) before the GTID set (<gtidSet>).
This symbol instructs MySQL to append the provided GTID set to the existing one, rather than completely replacing the current GTID values.

This subtle yet critical detail is often overlooked or forgotten, and is one of the most common causes of errors during GTID-based database migration and replication.
Always double-check the presence of the “+” symbol when executing this command to ensure the process completes successfully.

How to Identify Replication Issues in MySQL

The most effective way to identify replication-related issues in MySQL is to connect directly to the replica instance of the MySQL DB System and run specific diagnostic commands.
For this purpose, we recommend using MySQL Shell, which provides a practical and robust interface for administering MySQL environments.

Replication issues are typically reported in four main locations:

1. SHOW REPLICA STATUS\G Command

This is the most commonly used method, though not the most comprehensive.
It provides a quick overview of the replication status, particularly useful for identifying problems with the replication threads—namely, SQL_thread and IO_thread.

2. performance_schema.replication_connection_status Table

This table should be consulted when the IO_thread (responsible for communication between the master and the replica) is not functioning properly.
It provides detailed information about connection failures with the master server.

3. performance_schema.replication_applier_status_by_coordinator and replication_applier_status_by_worker Tables

These two tables offer detailed diagnostics for issues related to the SQL_thread, which is responsible for applying replication events received from the master.
They are especially useful for identifying failures or stalls in the event applier process.

4. MySQL Error Log

The most critical and detailed errors are logged directly in the MySQL error log, which can also be accessed via the performance_schema.error_log table.
This method is particularly helpful in cloud environments, such as MySQL HeatWave Database Service, allowing for detailed tracking and analysis of replication issues.

By leveraging these methods together, you can quickly and accurately diagnose any replication problem occurring in your MySQL environment, speeding up resolution and restoring proper replication as efficiently as possible.


SELECT logged,
       prio,
       error_code,
       data
FROM   performance_schema.error_log
WHERE  subsystem = 'Repl'
       AND prio = 'Error'
ORDER  BY 1 DESC; 


mysql> select LOGGED , PRIO, ERROR_CODE, DATA  from performance_schema.error_log where SUBSYSTEM = 'Repl' and PRIO = 'Error' order by 1 desc ;
+----------------------------+-------+------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| LOGGED                     | PRIO  | ERROR_CODE | DATA                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+----------------------------+-------+------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2025-03-24 20:48:35.415561 | Error | MY-010586  | Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log 'mysql-bin-changelog.001714' position 79540834                                                                                                                                                                                                                                                           |
| 2025-03-24 20:48:35.414871 | Error | MY-010584  | Replica SQL for channel 'replication_channel': Worker 1 failed executing transaction '415d143e-3653-30b3-980b-657ad05d72bd:49842481' at source log mysql-bin-changelog.001714, end_log_pos 81453887; Error 'Plugin 'mysql_native_password' is not loaded' on query. Default database: 'npx'. Query: 'ALTER USER 'replication_user'@'%' IDENTIFIED WITH 'mysql_native_password' AS '*102732A660139466B3EC305AF2DB488933474F4A'', Error_code: MY-001524 |
| 2025-03-24 16:14:25.868055 | Error | MY-010569  | Replica I/O thread aborted while waiting for relay log space                                                                                                                                                                                                                                                                                                                                                                                          |
| 2025-03-24 08:50:37.531874 | Error | MY-010586  | Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log 'INVALID' position 0                                                                                                                                                                                                                                                                                     |
| 2025-03-24 08:50:37.531007 | Error | MY-013146  | Replica SQL for channel 'replication_channel': Worker 1 failed executing transaction '415d143e-3653-30b3-980b-657ad05d72bd:1' at source log mysql-bin-changelog.000002, end_log_pos 3163; Column 32 of table 'npx.authorizations' cannot be converted from type 'blob' to type 'mediumblob', Error_code: MY-013146                                                                                                                                    |
| 2025-03-24 08:31:17.961232 | Error | MY-010569  | Replica I/O thread aborted while waiting for relay log space                                                                                                                                                                                                                                                                                                                                                                                          |
+----------------------------+-------+------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
6 rows in set (0.00 sec)


-- Check Replication Channel
SELECT 
  concat(
    conn_status.channel_name, ' (', worker_id, 
    ')'
  ) AS channel, 
  conn_status.service_state AS io_state, 
  applier_status.service_state AS sql_state, 
  format_pico_time(
    if(
      GTID_SUBTRACT(
        LAST_QUEUED_TRANSACTION, LAST_APPLIED_TRANSACTION
      ) = "", 
      "0", 
      abs(
        time_to_sec(
          if(
            time_to_sec(
              APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP
            )= 0, 
            0, 
            timediff(
              APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP, 
              now()
            )
          )
        )
      )
    ) * 1000000000000
  ) latency, 
  format_pico_time(
    (
      LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP - LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP
    ) * 100000000000
  ) transport_time, 
  format_pico_time(
    (
      LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP - LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP
    ) * 1000000000000
  ) time_to_relay_log, 
  format_pico_time(
    (
      LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP - LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP
    ) * 1000000000000
  ) apply_time, 
  conn_status.LAST_QUEUED_TRANSACTION AS last_queued_transaction, 
  applier_status.LAST_APPLIED_TRANSACTION AS last_applied_transaction 
FROM 
  performance_schema.replication_connection_status AS conn_status 
  JOIN performance_schema.replication_applier_status_by_worker AS applier_status ON applier_status.channel_name = conn_status.channel_name;
  
  

+---------------------------+----------+-----------+---------+----------------+-------------------+------------+-----------------------------------------------+-----------------------------------------------+
| channel                   | io_state | sql_state | latency | transport_time | time_to_relay_log | apply_time | last_queued_transaction                       | last_applied_transaction                      |
+---------------------------+----------+-----------+---------+----------------+-------------------+------------+-----------------------------------------------+-----------------------------------------------+
| replication_channel (1)   | ON       | ON        | 2.56 d  | 2.36 d         | 20.00 us          | 1.86 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50002732 |
| replication_channel (2)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 2.54 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50002601 |
| replication_channel (3)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.85 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50001734 |
| replication_channel (4)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.63 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50001736 |
| replication_channel (5)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.45 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50001727 |
| replication_channel (6)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 9.59 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49998021 |
| replication_channel (7)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.18 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49992586 |
| replication_channel (8)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.18 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959713 |
| replication_channel (9)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.19 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959714 |
| replication_channel (10)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.19 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959715 |
| replication_channel (11)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.34 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959717 |
| replication_channel (12)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.52 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49907064 |
| replication_channel (13)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.48 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49907065 |
| replication_channel (14)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.25 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866179 |
| replication_channel (15)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.21 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866180 |
| replication_channel (16)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.18 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866181 |
| replication_channel (17)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.17 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866182 |
| replication_channel (18)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.15 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866183 |
| replication_channel (19)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.13 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866184 |
| replication_channel (20)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.10 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866185 |
| replication_channel (21)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.09 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866186 |
| replication_channel (22)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.06 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866187 |
| replication_channel (23)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.04 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866188 |
| replication_channel (24)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.02 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866189 |
| replication_channel (25)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.98 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866190 |
| replication_channel (26)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 6.01 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49850471 |
| replication_channel (27)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 6.01 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49850472 |
| replication_channel (28)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (29)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (30)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (31)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (32)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (33)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (34)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (35)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (36)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (37)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (38)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (39)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (40)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (41)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (42)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (43)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (44)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (45)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (46)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (47)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (48)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (49)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (50)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (51)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (52)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (53)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (54)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (55)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (56)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (57)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (58)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (59)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (60)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (61)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (62)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (63)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (64)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (65)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (66)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (67)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (68)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (69)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (70)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (71)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (72)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (73)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (74)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (75)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (76)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (77)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (78)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (79)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (80)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (81)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (82)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (83)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (84)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (85)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (86)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (87)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (88)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (89)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (90)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (91)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (92)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (93)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (94)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (95)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (96)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (97)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (98)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (99)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (100) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (101) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (102) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (103) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (104) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (105) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (106) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (107) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (108) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (109) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (110) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (111) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (112) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (113) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (114) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (115) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (116) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (117) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (118) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (119) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (120) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (121) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (122) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (123) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (124) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (125) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (126) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (127) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (128) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (129) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (130) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (131) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (132) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (133) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (134) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (135) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (136) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (137) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (138) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (139) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (140) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (141) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (142) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (143) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (144) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (145) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (146) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (147) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (148) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (149) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (150) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (151) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (152) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (153) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (154) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (155) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (156) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (157) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (158) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (159) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (160) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (161) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (162) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (163) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (164) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (165) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (166) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (167) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (168) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (169) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (170) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (171) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (172) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (173) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (174) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (175) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (176) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (177) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (178) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (179) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (180) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (181) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (182) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (183) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (184) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (185) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (186) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (187) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (188) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (189) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (190) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (191) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (192) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (193) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (194) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (195) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (196) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (197) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (198) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (199) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (200) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (201) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (202) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (203) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (204) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (205) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (206) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (207) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (208) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (209) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (210) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (211) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (212) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (213) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (214) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (215) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (216) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (217) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (218) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (219) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (220) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (221) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (222) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (223) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (224) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (225) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (226) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (227) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (228) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (229) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (230) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (231) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (232) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (233) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (234) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (235) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (236) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (237) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (238) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (239) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (240) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (241) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (242) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (243) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (244) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (245) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (246) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (247) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (248) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (249) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (250) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (251) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (252) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (253) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (254) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (255) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (256) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
+---------------------------+----------+-----------+---------+----------------+-------------------+------------+-----------------------------------------------+-----------------------------------------------+
256 rows in set (0.01 sec)

🔸 channel

Identifies the name of the replication channel, along with the specific thread or worker number.

Example: replication_channel (1)

🔸 io_state

Indicates the state of the channel related to binlog connection and transfer (I/O Thread).

Possible values:

  • ON → The connection is active and functioning normally.
  • OFF → The connection is inactive or disconnected.

🔸 sql_state

Reflects the state of transaction application (SQL Thread).

Possible values:

  • ON → Transactions are being applied correctly.
  • OFF → Transaction application is halted or experiencing issues.

🔸 latency

Represents the overall replication lag, indicating the delay between the last GTID received by the replica and the last GTID actually applied.

Example: 2.56 d means that channel (1) is 2.56 days behind in applying transactions.

🔸 time_to_relay_log

The time it takes for the replica to write the received data to the relay log.

This value is typically very small.
Example: 20.00 µs (microseconds), which is an acceptable and fast response time.

🔸 apply_time

The time taken by the replica to apply the last transaction to its local database.

Example: 1.86 ms, 5.18 ms — these are considered good and acceptable values.

🔸 last_queued_transaction

Indicates the last GTID received (queued) from the master.

🔸 last_applied_transaction

Indicates the last GTID successfully applied by the replica.

The difference between this GTID and the last_queued_transaction represents the current replication lag.

mysql> show replica status \G ;
*************************** 1. row ***************************
             Replica_IO_State: Waiting for source to send event
                  Source_Host: 100.22.20.186
                  Source_User: replication_user
                  Source_Port: 3306
                Connect_Retry: 60
              Source_Log_File: mysql-bin-changelog.001778
          Read_Source_Log_Pos: 66207953
               Relay_Log_File: relay-log-replication_channel.000006
                Relay_Log_Pos: 70856500
        Relay_Source_Log_File: mysql-bin-changelog.001716
           Replica_IO_Running: Yes
          Replica_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Source_Log_Pos: 70856263
              Relay_Log_Space: 8521164737
              Until_Condition: None
               Until_Log_File:
                Until_Log_Pos: 0
           Source_SSL_Allowed: Yes
           Source_SSL_CA_File:
           Source_SSL_CA_Path:
              Source_SSL_Cert:
            Source_SSL_Cipher:
               Source_SSL_Key:
        Seconds_Behind_Source: 232722
Source_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Source_Server_Id: 925869836
                  Source_UUID: 415d143e-3653-30b3-980b-657ad05d72bd
             Source_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
    Replica_SQL_Running_State: Waiting for dependent transaction to commit
           Source_Retry_Count: 0
                  Source_Bind: 10.27.2.35
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp:
               Source_SSL_Crl:
           Source_SSL_Crlpath:
           Retrieved_Gtid_Set: 415d143e-3653-30b3-980b-657ad05d72bd:49842481-50356353
            Executed_Gtid_Set: 415d143e-3653-30b3-980b-657ad05d72bd:1-49854029,
df21fd43-067a-11f0-b189-020017028ccd:1-44464
                Auto_Position: 1
         Replicate_Rewrite_DB:
                 Channel_Name: replication_channel
           Source_TLS_Version: TLSv1.2,TLSv1.3
       Source_public_key_path:
        Get_Source_public_key: 1
            Network_Namespace: mysql
1 row in set (0.01 sec)

Monitoring MySQL Replication

Replication Status

  • Replica_IO_Running and Replica_SQL_Running:
    Indicate whether the I/O and SQL threads are active—critical for verifying the replication’s operational status.
  • Replica_IO_State:
    Displays the current state of the I/O thread, such as "Waiting for source to send event", indicating that the replica is ready to receive new events.

Source Server Connection

  • Source_Host, Source_User, and Source_Port:
    Show the host address, user, and port of the source (master) server—key for validating the replication connection.
  • Connect_Retry:
    Defines the retry interval before attempting to reconnect to the source, reflecting the connection’s resilience in case of failure.

Log Position Tracking

  • Source_Log_File and Read_Source_Log_Pos:
    Indicate the current binary log file and read position on the source server—useful for tracking replication progress.
  • Relay_Log_File and Relay_Log_Pos:
    Refer to the relay log file and position on the replica—important for monitoring the processing of incoming events.
  • Exec_Source_Log_Pos:
    The position up to which SQL statements have been executed on the replica—critical for understanding how much of the transaction stream has been applied.

Performance and Lag

  • Seconds_Behind_Source:
    Shows the replication lag in seconds between the replica and the source—a vital metric for performance and stability monitoring.

Security

  • Source_SSL_Allowed and Source_SSL_Verify_Server_Cert:
    Indicate whether SSL encryption is enabled for the connection and whether the source server’s certificate is verified, helping ensure data security and integrity.

Global Transaction Identifiers (GTIDs)

  • Auto_Position:
    Enables GTID-based auto-positioning, which simplifies the configuration and management of replication.
  • Retrieved_Gtid_Set and Executed_Gtid_Set:
    Represent the sets of GTIDs that have been retrieved and executed, respectively—essential for verifying consistency and integrity in GTID-based replication.

Error Diagnostics

  • Last_IO_Errno, Last_IO_Error, Last_SQL_Errno, and Last_SQL_Error:
    Provide information about the most recent I/O and SQL thread errors, essential for diagnosing and resolving replication issues.

mysql> select * from performance_schema.replication_connection_status\G
*************************** 1. row ***************************
                                      CHANNEL_NAME: replication_channel
                                        GROUP_NAME:
                                       SOURCE_UUID: 415d143e-3653-30b3-980b-657ad05d72bd
                                         THREAD_ID: 1651
                                     SERVICE_STATE: ON
                         COUNT_RECEIVED_HEARTBEATS: 3
                          LAST_HEARTBEAT_TIMESTAMP: 2025-03-25 15:16:16.930055
                          RECEIVED_TRANSACTION_SET: 415d143e-3653-30b3-980b-657ad05d72bd:49842481-50396683
                                 LAST_ERROR_NUMBER: 0
                                LAST_ERROR_MESSAGE:
                              LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
                           LAST_QUEUED_TRANSACTION: 415d143e-3653-30b3-980b-657ad05d72bd:50396683
 LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.013504
LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.013504
     LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: 2025-03-25 15:18:35.587187
       LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: 2025-03-25 15:18:35.587199
                              QUEUEING_TRANSACTION: 415d143e-3653-30b3-980b-657ad05d72bd:50396684
    QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.201468
   QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.201468
        QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: 2025-03-25 15:18:35.587203
1 row in set (0.00 sec)

Monitoring Replication via performance_schema.replication_connection_status

MySQL provides the performance_schema.replication_connection_status table to monitor the current state of the I/O thread that manages the replica’s connection to the source server.
This table offers detailed insights into the replication connection, including service status, received transactions, and potential errors.

Below are the key metrics for effectively monitoring replication:

Replication Connection State

  • SERVICE_STATE:
    Indicates the current state of the replica’s I/O thread. Possible values include:
    • ON: The connection is active.
    • OFF: The connection is inactive.
    • CONNECTING: The replica is attempting to connect to the source.

Connection Identification

  • CHANNEL_NAME:
    Name of the replication channel associated with this connection.
  • SOURCE_UUID:
    The unique universal identifier (UUID) of the source server — useful for tracking the origin of the replication.

Transaction Information

  • RECEIVED_TRANSACTION_SET:
    The set of GTIDs (Global Transaction Identifiers) representing all transactions received by the replica.
  • LAST_QUEUED_TRANSACTION:
    The GTID of the last transaction queued in the relay log.
  • LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP:
    Timestamp when the last queued transaction was originally committed on the source server.
  • LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP:
    Timestamp when the last queued transaction was committed on the immediate upstream source (e.g., an intermediate master).
  • LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP:
    Timestamp indicating when the I/O thread started queuing the last transaction.
  • LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP:
    Timestamp indicating when the transaction was fully queued into the relay log.

Replication Heartbeats

  • LAST_HEARTBEAT_TIMESTAMP:
    Timestamp of the last heartbeat signal received from the source server, confirming the connection is alive even in the absence of recent events.
  • COUNT_RECEIVED_HEARTBEATS:
    Total number of heartbeat signals received since the replica was last restarted or reset.

Error Information

  • LAST_ERROR_NUMBER:
    The error code of the most recent I/O thread failure. A value of 0 indicates no errors.
  • LAST_ERROR_MESSAGE:
    The error message associated with the most recent failure. An empty string indicates no recent errors.
  • LAST_ERROR_TIMESTAMP:
    Timestamp of the last I/O thread error occurrence.

Timestamps for Current Transactions

  • QUEUEING_TRANSACTION:
    The GTID of the transaction currently being queued.
  • QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP:
    Timestamp when the currently queued transaction was committed on the original source server.
  • QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP:
    Timestamp when the transaction was committed on the immediate upstream source.
  • QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP:
    Timestamp when the first event of the currently queued transaction was written to the relay log.

✅ Final Checklist – Migration from AWS Aurora MySQL to OCI HeatWave MySQL

To conclude this article, we present a practical and detailed checklist of the main steps required to successfully perform a migration from AWS Amazon Aurora MySQL to OCI HeatWave MySQL, with minimal downtime.

This high-level summary offers a clear and structured view of the entire process, serving as a quick reference for readers with varying levels of technical background and time availability.

1. Validation of Prerequisites

  • Ensure that the MySQL infrastructures on AWS and OCI are fully provisioned.
  • Confirm network connectivity between AWS (Aurora MySQL) and OCI (HeatWave MySQL), with port 3306 open.
  • Use a bridge server with MySQL Shell installed, ensuring full bidirectional connectivity between the environments.
  • Refer to the Official Oracle Documentation for in-depth prerequisite validation.

2. Mandatory Configuration in AWS Aurora MySQL (Source)

Enable and verify the following parameters:

gtid_mode = ON
enforce-gtid-consistency = ON
log_bin = ON
binlog_format = ROW
log_slave_updates = ON

These configurations are essential to ensure technical feasibility and data integrity during replication.

For details, consult the Official AWS Documentation.

3. Export and Import Using MySQL Shell

  • Use MySQL Shell as the primary tool for the export/import process.
  • Ensure proper execution, including the correct handling of JSON metadata files for GTID consistency.
  • Follow best practices provided throughout the article for a smooth transfer.

4. Replication User Configuration

  • Confirm that the replication user is properly created on AWS Aurora MySQL (source) and has the required privileges.
  • A full example for creating the user repuser is provided earlier in this article to avoid permission-related issues.

5. OCI HeatWave MySQL Channel Configuration

  • Ensure GTID consistency between source and target using the .json file generated during export.
  • If needed, adjust GTIDs with the SET GTID_PURGED command.
  • Pay special attention to the step-by-step instructions previously outlined for the correct implementation of the replication channel in OCI.

6. Troubleshooting and Monitoring

  • Use the monitoring techniques and scripts provided in this article to detect issues proactively.
  • Leverage MySQL Shell, performance_schema tables, and error logs for effective diagnosis and resolution.

]]> Migração MySQL: Como migrar do AWS Amazon Aurora MYSQL para OCI HeatWave MYSQL com mínimo downtime. https://furushima.com.br/blog/migracao-mysql-como-migrar-do-aws-amazon-aurora-mysql-para-oci-heatwave-mysql-com-minimo-downtime/ Tue, 25 Mar 2025 12:03:30 +0000 https://furushima.com.br/?p=2676 Neste artigo vamos demonstrar, de maneira clara e prática, como realizar uma migração entre bancos de dados MySQL com o mínimo possível de downtime (indisponibilidade). Para este exemplo, nosso ambiente de origem (source) será o Amazon Aurora MySQL 8.0.39, e o ambiente de destino (target) será o OCI HeatWave MySQL 8.4.4.


Antes de iniciarmos o procedimento de migração, é necessário garantir que alguns pré-requisitos de infraestrutura estejam devidamente configurados e operacionais:

  1. Infraestrutura AWS e OCI já instaladas, configuradas e operacionais.

  2. Cluster Amazon Aurora MySQL já existente e atualmente em operação como banco de produção (ambiente de origem ou source).

  3. Cluster OCI HeatWave MySQL já criado e configurado, pronto para receber os dados migrados do Amazon Aurora. Este será o novo ambiente de produção (ambiente de destino ou target).

  4. Conectividade devidamente configurada entre o Amazon Aurora MySQL e o OCI HeatWave MySQL, especificamente na porta padrão do MySQL (3306).


Os detalhes sobre a configuração dos pré-requisitos não serão abordados neste artigo. Caso você tenha dificuldades durante essa etapa, ou deseje compreender melhor cada passo mencionado, recomenda-se consultar a documentação oficial, cujo link está disponível abaixo:

https://www.oracle.com/a/ocom/docs/mysql/amazon-aurora-to-mysql-heatwave-on-aws-migration.pdf


Este documento é um guia completo que aborda desde a criação das infraestruturas AWS e OCI até os procedimentos que serão resumidamente demonstrados neste artigo. Lá você encontrará explicações detalhadas sobre conceitos que aqui serão simplificados, a fim de manter este artigo objetivo e direto.


A seguir apresentamos um fluxograma macro detalhando como será realizado o processo de migração de um banco de dados MySQL que atualmente está hospedado na infraestrutura AWS Amazon Aurora MySQL para a infraestrutura OCI HeatWave MySQL.


O objetivo principal dessa abordagem é realizar a migração com o menor downtime possível. Para alcançar esse objetivo, utilizaremos uma técnica que consiste basicamente em duas etapas principais:

  1. Migração inicial dos dados (Baseline)
    Nesta fase inicial, o banco de dados completo (ou seja, a base integral) é migrado da origem (AWS Amazon Aurora MySQL) para o destino (OCI HeatWave MySQL). Este procedimento será realizado com o auxílio do MySQL Shell, uma ferramenta robusta que garante consistência e integridade na transferência dos dados.

  2. Replicação contínua dos dados diferenciais (Delta)
    Após a migração inicial, haverá uma replicação contínua das alterações que ocorrerem na origem enquanto a migração final não é concluída. Essa replicação diferencial é realizada por meio dos binlogs (binary logs), arquivos que registram todas as transações realizadas no banco de dados de origem.


Para viabilizar essa replicação em tempo real entre os ambientes AWS Aurora e OCI HeatWave, será utilizado o recurso conhecido como OCI HeatWave MySQL Channel, que estabelece uma conexão direta e confiável entre os ambientes, tornando o OCI HeatWave MySQL uma réplica ativa (também conhecida como réplica read/write) do Amazon Aurora MySQL.

Na prática, durante o processo, o ambiente OCI HeatWave MySQL funcionará temporariamente como um banco de dados replicado (Slave) que acompanhará fielmente as alterações feitas no ambiente Master (Amazon Aurora). Quando todas as replicações diferenciais estiverem em sincronia, restará apenas apontar os servidores de aplicação (servidores web, appservers, middlewares etc.) para o novo ambiente de produção OCI HeatWave MySQL. Dessa forma, o único tempo de indisponibilidade (downtime) será o necessário para realizar os ajustes desses apontamentos nos servidores de aplicação, garantindo uma transição rápida, segura e com mínimo impacto para os usuários finais.

O resultado final será um ambiente totalmente migrado e operacional na infraestrutura OCI HeatWave, mantendo-se fiel às características e dados originais do Amazon Aurora, com ganhos adicionais em desempenho e escalabilidade proporcionados pela tecnologia HeatWave.

Neste artigo, dividiremos o conteúdo em duas partes principais, com o objetivo de tornar mais clara a compreensão das etapas necessárias para realizar uma migração eficiente entre os ambientes AWS Amazon Aurora MySQL e OCI MySQL HeatWave, mantendo o mínimo de indisponibilidade possível.

Parte 1: Exportação (AWS Aurora MySQL) e Importação (OCI MySQL HeatWave)
Na primeira parte deste artigo, explicaremos detalhadamente como realizar o processo de exportação dos dados do banco de dados AWS Amazon Aurora MySQL (ambiente de origem) utilizando o MySQL Shell, uma ferramenta poderosa e prática que permite exportações rápidas, seguras e consistentes dos dados.

Após a exportação, demonstraremos passo a passo como realizar o processo inverso, ou seja, a importação dos dados extraídos para o ambiente destino (OCI MySQL HeatWave). Nesta etapa, abordaremos também as melhores práticas e recomendações para garantir uma importação bem-sucedida, além dos cuidados necessários para garantir a integridade dos dados importados.

Parte 2: Implementação do OCI HeatWave MySQL Channel (Replicação MASTER-SLAVE em tempo real)
Na segunda parte do artigo, abordaremos de forma detalhada como implementar o OCI HeatWave MySQL Channel, que permitirá estabelecer uma replicação em tempo real no modelo MASTER-SLAVE entre os bancos de dados AWS Aurora MySQL (MASTER) e OCI MySQL HeatWave (SLAVE).

Esse método garante que todas as transações realizadas no ambiente AWS Aurora MySQL sejam replicadas automaticamente e em tempo real para o ambiente OCI MySQL HeatWave, utilizando para isso os binlogs (binary logs). Dessa forma, o OCI MySQL HeatWave se manterá sempre atualizado com o ambiente de origem, permitindo que a migração final ocorra com o mínimo de downtime possível.

Além disso, vamos apresentar orientações sobre a configuração do canal de replicação, monitoramento do status e solução de possíveis problemas de sincronização durante a replicação.

Dessa maneira, ao final deste artigo, você terá todas as informações necessárias para realizar a migração segura, consistente e com mínimo impacto operacional entre AWS Amazon Aurora MySQL e OCI MySQL HeatWave.

Para facilitar o entendimento, apresentamos abaixo um fluxograma que ilustra claramente as etapas que serão demonstradas na prática ao longo deste artigo.

Antes de iniciarmos o procedimento prático de exportação e importação utilizando o MySQL Shell, é fundamental garantir que os seguintes parâmetros estejam devidamente configurados e ativados no ambiente de origem (SOURCE), ou seja, no AWS Amazon Aurora MySQL:


gtid_mode = ON
enforce-gtid-consistency = ON
log_bin = ON
binlog_format = ROW
log_slave_updates = ON

Esses parâmetros são obrigatórios para assegurar que a replicação baseada em GTID (Global Transaction Identifiers) e os logs binários estejam corretamente habilitados, garantindo uma migração confiável, consistente e adequada ao ambiente OCI HeatWave MySQL.

Para mais detalhes consulte a documentação abaixo :

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_LogAccess.MySQL.BinaryFormat.html



EXPORTAÇÃO – EXPORT – util.dumpschemas

Exportação: Nesta etapa realizaremos a exportação (dump) do banco de dados npx. O arquivo gerado será armazenado no diretório /DUMP/NPX/. Além disso, serão utilizados parâmetros específicos que garantem total compatibilidade do dump com o ambiente de destino, o OCI MySQL HeatWave.

util.dumpSchemas(
  ["npx"],
  "/DUMP/NPX/",
  {
    threads: 60,
    ocimds: true,
    compatibility: [
      "skip_invalid_accounts",
      "strip_restricted_grants",
      "ignore_wildcard_grants",
      "strip_definers",
      "strip_invalid_grants",
      "create_invisible_pks"    ],
    consistent: true
  }
);


Explicação dos parâmetros utilizados no comando util.dumpSchemas:

  • util.dumpSchemas
    Comando do MySQL Shell usado para gerar um dump (exportação dos dados).
  • ["npx"]
    Indica o nome do banco de dados que será exportado.
  • "/DUMP/NPX/"
    Diretório (pasta) onde serão armazenados os arquivos do dump gerado.
  • threads: 60
    Número de threads simultâneas usadas na exportação. Neste caso, serão usados 60 processos paralelos para acelerar a geração do dump.
  • ocimds: true
    Otimiza automaticamente a exportação para garantir total compatibilidade com o ambiente OCI MySQL Database Service (MDS) ou OCI MySQL HeatWave.
  • Parâmetros do campo compatibility:
    • skip_invalid_accounts
      Ignora contas de usuários inválidas ou não compatíveis com o destino.
    • strip_restricted_grants
      Remove permissões restritas que não são suportadas pelo banco de dados de destino.
    • ignore_wildcard_grants
      Ignora permissões de usuários criadas com curingas (%), aumentando a segurança e evitando problemas no destino.
    • strip_definers
      Remove definições específicas de usuários (DEFINER) em objetos como views, stored procedures e triggers, evitando erros caso esses usuários não existam no destino.
    • strip_invalid_grants
      Remove permissões inválidas ou incompatíveis com o destino.
    • create_invisible_pks
      Cria automaticamente chaves primárias invisíveis nas tabelas que não possuem chave primária, garantindo compatibilidade com ambientes como OCI HeatWave.
  • consistent: true
    Garante que o dump seja consistente, refletindo exatamente o estado do banco de dados em um único momento específico, evitando inconsistências durante a exportação.



IMPORTAÇÃO – IMPORT – util.loadDump

Importação: Nesta etapa será realizada a importação do dump previamente gerado para o banco de dados npx. Os arquivos a serem importados estão localizados no diretório /DUMP/NPX/. Para acelerar esse processo, utilizaremos 60 threads em paralelo e o parâmetro ignoreVersion, permitindo a importação mesmo em versões diferentes do MySQL. O banco de dados de destino será explicitamente definido pelo parâmetro schema, que neste caso também se chama npx. Vale lembrar que no MySQL, o termo schema representa o nome do banco de dados.

util.loadDump(
  "/DUMP/NPX",
  {
    threads: 60,
    ignoreVersion: true,
	  schema: 'npx'
  }
);

Explicação dos parâmetros utilizados no comando util.loadDump:

  • util.loadDump
    Comando do MySQL Shell utilizado para carregar (importar) um dump previamente exportado para o banco de dados.
  • "/DUMP/NPX"
    Diretório (pasta) onde estão armazenados os arquivos do dump que será importado.
  • threads: 60
    Número de processos paralelos utilizados durante a importação. Neste exemplo, 60 threads serão usadas para acelerar o carregamento dos dados.
  • ignoreVersion: true
    Ignora diferenças de versão entre o banco de dados original (onde o dump foi gerado) e o banco de dados de destino. Isso permite importar o dump mesmo se houver pequenas diferenças de versão.
  • schema: 'npx'
    Define explicitamente o nome do banco de dados (schema) onde os dados serão importados. Nesse caso, o schema destino será npx.

Agora que já entendemos como realizar o processo de exportação e importação do banco de dados, vamos acompanhar, na prática, a execução desses procedimentos em um ambiente real de laboratório.




Execução do export – util.dumpschemas

  MySQL  XXXXXXXXX-producao-clone.c4xlg1kbktwa.us-west-2.rds.amazonaws.com:3306 ssl  JS > util.dumpSchemas(
                                             ->   ["npx"],
                                             ->   "/DUMP/NPX/",
                                             ->   {
                                             ->     threads: 60,
                                             ->     ocimds: true,
                                             ->     compatibility: [
                                             ->       "skip_invalid_accounts",
                                             ->       "strip_restricted_grants",
                                             ->       "ignore_wildcard_grants","strip_definers",
                                             ->       "strip_invalid_grants","create_invisible_pks"    ],
                                             ->     consistent: true
                                             ->   }
                                             -> );
                                             ->
NOTE: The 'targetVersion' option is set to 9.1.0. This version supports the SET_ANY_DEFINER privilege, using the 'strip_definers' compatibility option is unnecessary.
NOTE: Backup lock is not available to the account 'tksmaster'@'%' and DDL changes will not be blocked. The dump may fail with an error if schema changes are made while dumping.
Acquiring global read lock
WARNING: The current user lacks privileges to acquire a global read lock using 'FLUSH TABLES WITH READ LOCK'. Falling back to LOCK TABLES...
Table locks acquired
Initializing - done
1 schemas will be dumped and within them 276 tables, 0 views, 5 routines.
Gathering information - done
All transactions have been started
Global read lock has been released
NOTE: When migrating to MySQL HeatWave Service, please always use the latest available version of MySQL Shell.
Checking for compatibility with MySQL HeatWave Service 9.1.0
Checking for potential upgrade issues.
The MySQL server at
beecare-producao-clone.c4xlg1kbktwa.us-west-2.rds.amazonaws.com:3306, version
8.0.39 - 2f855dc7, will now be checked for compatibility issues for upgrade to
MySQL 9.1.0.

WARNING: Upgrading MySQL Server from version 8.0.39 to 9.1.0 is not supported.
Please consider running the check using the following option: targetVersion=8.4

1) Checks for foreign keys not referencing a full unique index
(foreignKeyReferences)
   No issues found

2) Checks for errors in column definitions (columnDefinition)
   No issues found

3) Checks for partitions by key using columns with prefix key indexes
(partitionsWithPrefixKeys)
   No issues found
Errors:   0
Warnings: 0
Notices:  0

No known compatibility errors or issues were found.
NOTE: Database `npx` had unsupported ENCRYPTION option commented out
NOTE: Function `npx`.`available_date` had definer clause removed
NOTE: Function `npx`.`available_date` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`GetEligibilityRecords` had definer clause removed
NOTE: Procedure `npx`.`GetEligibilityRecords` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`available_date_procedure` had definer clause removed
NOTE: Procedure `npx`.`available_date_procedure` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`SP_INSERT_PAYMENT_ADVICES` had definer clause removed
NOTE: Procedure `npx`.`SP_INSERT_PAYMENT_ADVICES` had SQL SECURITY characteristic set to INVOKER
NOTE: Procedure `npx`.`cadastar_payment_advice_partners` had definer clause removed
NOTE: Procedure `npx`.`cadastar_payment_advice_partners` had SQL SECURITY characteristic set to INVOKER
NOTE: Table `npx`.`migrations` does not have a Primary Key, this will be fixed when the dump is loaded
NOTE: Table `npx`.`password_resets` does not have a Primary Key, this will be fixed when the dump is loaded
NOTE: Table `npx`.`message_organization` does not have a Primary Key, this will be fixed when the dump is loaded
NOTE: Table `npx`.`message_menu` does not have a Primary Key, this will be fixed when the dump is loaded
Validating MySQL HeatWave Service compatibility - done

NOTE: One or more tables without Primary Keys were found.

      Missing Primary Keys will be created automatically when this dump is loaded.
      This will make it possible to enable High Availability in MySQL HeatWave Service DB System instance without application impact and without changes to the source database.
      Inbound Replication into a DB System HA instance will also be possible, as long as the instance has version 8.0.32 or newer. For more information, see https://docs.oracle.com/en-us/iaas/mysql-database/doc/creating-replication-channel.html.

Compatibility issues with MySQL HeatWave Service 9.1.0 were found and repaired. Please review the changes made before loading them.
Writing global DDL files
Writing schema metadata - done
Running data dump using 60 threads.
NOTE: Progress information uses estimated values and may not be accurate.
NOTE: Table statistics not available for `npx`.`password_securities`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`password_securities`;' first.
Writing DDL - done
Writing table metadata - done
Starting data dump
NOTE: Table statistics not available for `npx`.`incident_types`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`incident_types`;' first.
NOTE: Backup lock is not available to the account 'tksmaster'@'%' and DDL changes were not blocked. The DDL is consistent, the world may resume now.
NOTE: Table statistics not available for `npx`.`comercial_contracts`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`comercial_contracts`;' first.
NOTE: Table statistics not available for `npx`.`comercial_negotiations`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`comercial_negotiations`;' first.
NOTE: Table statistics not available for `npx`.`procedure_info_files`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`procedure_info_files`;' first.
NOTE: Table statistics not available for `npx`.`refute_approval_levels`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`refute_approval_levels`;' first.
NOTE: Table statistics not available for `npx`.`modules`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`modules`;' first.
NOTE: Table statistics not available for `npx`.`organization_payment_types`, chunking operation may be not optimal. Please consider running 'ANALYZE TABLE `npx`.`organization_payment_types`;' first.
110% (3.60G rows / ~3.26G rows), 33.50K rows/s, 25.84 MB/s uncompressed, 1.17 MB/s compressed
Dump duration: 03:17:25s
Total duration: 03:24:46s
Schemas dumped: 1
Tables dumped: 276
Uncompressed data size: 1.45 TB
Compressed data size: 413.88 GB
Compression ratio: 3.5
Rows written: 3597220261
Bytes written: 413.88 GB
Average uncompressed throughput: 122.12 MB/s
Average compressed throughput: 34.94 MB/s



Execução do import – util.loadDump

MySQL  10.27.2.35:3306 ssl  JS > util.loadDump(
                               ->   "/DUMP/NPX",
                               ->   {
                               ->     threads: 60,
                               ->     ignoreVersion: true,
                               -> schema: 'npx'
                               ->   }
                               -> );
                               ->
Loading DDL and Data from '/DUMP/NPX' using 60 threads.
Opening dump - done
Target is MySQL 8.4.4-u3-cloud (MySQL HeatWave Service). Dump was produced from MySQL 8.0.39
WARNING: Destination MySQL version is different than the value of the 'targetVersion' option set when the dump was created: 9.1.0
Scanning metadata - done
Checking for pre-existing objects - done
NOTE: The dump contains tables without Primary Keys and it is loaded with the 'createInvisiblePKs' option set to true, Inbound Replication into an MySQL HeatWave Service DB System instance with High Availability can be used with this dump.
Executing common preamble SQL - done
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_tables`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker050]: Error processing table `npx`.`comercial_procedures`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker023]: Error processing table `npx`.`comercial_volumes`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_tables`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker046]: Error processing table `npx`.`payment_advice_partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker049]: Error processing table `npx`.`payment_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker043]: Error processing table `npx`.`payment_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker038]: Error processing table `npx`.`partner_configurations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker023]: Error processing table `npx`.`comercial_volumes`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_procedure_reference_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker021]: Error processing table `npx`.`partner_integration_windows`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker009]: Error processing table `npx`.`procedure_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker053]: Error processing table `npx`.`glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker037]: Error processing table `npx`.`protocol_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker025]: Error processing table `npx`.`document_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker059]: Error processing table `npx`.`rpa_tasks`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker003]: Error processing table `npx`.`authorizations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker015]: Error processing table `npx`.`comercial_contracts`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker035]: Error processing table `npx`.`reconcile_statement_index_data_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker021]: Error processing table `npx`.`partner_integration_windows`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker038]: Error processing table `npx`.`partner_connections`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker039]: Error processing table `npx`.`billing_headers`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker006]: Error processing table `npx`.`statements`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker023]: Error processing table `npx`.`comercial_volumes`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker011]: Error processing table `npx`.`partner_integration_window_audits`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker013]: Error processing table `npx`.`procedure_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker017]: Error processing table `npx`.`comercial_auditor_procedure_reference_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker044]: Error processing table `npx`.`related_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker051]: Error processing table `npx`.`statement_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker058]: Error processing table `npx`.`procedure_info_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker002]: Error processing table `npx`.`integration_window_logs`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker014]: Error processing table `npx`.`partner_password_addresses`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker049]: Error processing table `npx`.`payment_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker025]: Error processing table `npx`.`document_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker040]: Error processing table `npx`.`partner_status_relations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker007]: Error processing table `npx`.`guide_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker004]: Error processing table `npx`.`document_paperless`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker031]: Error processing table `npx`.`organization_from_to_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker059]: Error processing table `npx`.`rpa_tasks`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker043]: Error processing table `npx`.`payment_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker037]: Error processing table `npx`.`protocol_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker003]: Error processing table `npx`.`authorizations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker009]: Error processing table `npx`.`procedure_glosa_insights`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker053]: Error processing table `npx`.`glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker035]: Error processing table `npx`.`reconcile_statement_index_data_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker007]: Error processing table `npx`.`guide_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker013]: Error processing table `npx`.`procedure_glosa_insight_tmps`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker037]: Error processing table `npx`.`protocol_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker057]: Error processing table `npx`.`tax_records`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker011]: Error processing table `npx`.`erp_reconcile_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker025]: Error processing table `npx`.`document_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker031]: Error processing table `npx`.`organization_from_to_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker053]: Error processing table `npx`.`glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker019]: Error processing table `npx`.`resubmission_details`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker007]: Error processing table `npx`.`guide_payments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker022]: Error processing table `npx`.`users`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker002]: Error processing table `npx`.`organizations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker048]: Error processing table `npx`.`refute_glosa_replies`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker036]: Error processing table `npx`.`refute_glosas`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker030]: Error processing table `npx`.`partners`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker045]: Error processing table `npx`.`refute_glosa_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker001]: Error processing table `npx`.`authorization_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker054]: Error processing table `npx`.`mass_import_files`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker056]: Error processing table `npx`.`authorization_attachments`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker029]: Error processing table `npx`.`document_paperless_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker012]: Error processing table `npx`.`protocol_payment_histories`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker032]: Error processing table `npx`.`erp_refute_glosa_integrations`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
NOTE: [Worker027]: Error processing table `npx`.`partner_passwords`, will retry after delay: MySQL Error 1213 (40001): Deadlock found when trying to get lock; try restarting transaction
Executing DDL - done
Executing view DDL - done
Starting data load
2 thds indexing - 100% (1.45 TB / 1.45 TB), 0.00 B/s (15.64K rows/s), 276 / 276 tables done
Building indexes - done
Executing common postamble SQL - done
43064 chunks (3.60G rows, 1.45 TB) for 276 tables in 1 schemas were loaded in 7 hours 44 min 26 sec (avg throughput 51.91 MB/s, 129.09K rows/s)
277 DDL files were executed in 16 sec.
Data load duration: 7 hours 44 min 26 sec
2 indexes were built in 1 min 21 sec.
Total duration: 7 hours 45 min 54 sec
0 warnings were reported during the load.


Neste ponto do artigo, temos o seguinte cenário consolidado: já realizamos uma exportação do banco de dados utilizando o comando util.dumpSchemas no ambiente de origem (AWS Amazon Aurora MySQL) e uma importação desses dados no ambiente de destino (OCI HeatWave MySQL) utilizando o comando util.loadDump.


Com isso, partiremos agora para a segunda parte do nosso artigo, onde faremos passo a passo a configuração do OCI HeatWave MySQL Channel. Essa configuração permitirá criar uma replicação no modelo MASTER/SLAVE entre os dois ambientes mencionados, transformando o AWS Amazon Aurora MySQL no banco de dados MASTER e o OCI HeatWave MySQL em sua réplica (SLAVE). Assim, todas as transações realizadas no Aurora MySQL serão automaticamente replicadas em tempo real para o OCI HeatWave MySQL.




Nesta etapa, é importante garantir que o usuário específico para replicação já tenha sido criado no ambiente SOURCE (origem), ou seja, no banco de dados AWS Amazon Aurora MySQL. Caso ainda não tenha sido feito, utilize os comandos abaixo para criar o usuário e conceder as permissões necessárias para replicação:

CREATE USER 'repuser'@'%' IDENTIFIED BY 'minha_senha_forte';
GRANT REPLICATION SLAVE ON *.* TO 'repuser'@'%';








































Certificando que GTID esta no ponto correto





Ao realizar um dump (exportação) utilizando o comando util.dumpSchemas, será gerado automaticamente um arquivo especial chamado @.json no diretório escolhido para armazenar o dump.





Este arquivo @.json é um arquivo de metadados contendo diversas informações essenciais sobre o dump realizado. Entre as informações mais relevantes presentes neste arquivo está o conjunto GTID (Global Transaction ID), que é crucial para garantir consistência e rastreamento correto das transações replicadas.





Recomenda-se sempre verificar e consultar esse arquivo antes da importação (load), pois o GTID ali informado será utilizado posteriormente para configuração correta da replicação e execução do comando SET_GTID_PURGED.





Ignorar ou não utilizar corretamente o arquivo @.json pode levar a erros comuns e sérios problemas de consistência na migração e replicação do banco de dados.





[root@gateway-furushima-linux ~]# cd /DUMP/NPX/
[root@gateway-furushima-linux NPX]# pwd
/DUMP/NPX
[root@gateway-furushima-linux NPX]# cat @.json | grep -i '"gtidExecuted"'
    "gtidExecuted": "415d143e-3653-30b3-980b-657ad05d72bd:1-44171859",












[root@gateway-furushima-linux NPX]# mysql -u sys -p'#SENHA_DO_MYSQL#' -h 192.168.1.35  -P 3306
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 886
Server version: 8.4.4-u4-cloud MySQL Enterprise - Cloud

Copyright (c) 2000, 2024, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>  call sys.SET_GTID_PURGED("+415d143e-3653-30b3-980b-657ad05d72bd:1-44171859");
Query OK, 0 rows affected (0.00 sec)










mysql> SHOW GLOBAL VARIABLES LIKE 'gtid_executed';
+---------------+-----------------------------------------------------------------------------------------------+
| Variable_name | Value                                                                                         |
+---------------+-----------------------------------------------------------------------------------------------+
| gtid_executed | 415d143e-3653-30b3-980b-657ad05d72bd:1-49842480,
df21fd43-067a-11f0-b189-020017028ccd:1-44462 |
+---------------+-----------------------------------------------------------------------------------------------+
1 row in set (0.00 sec)
















Ao utilizar o comando SET_GTID_PURGED, siga rigorosamente o modelo abaixo para garantir que não ocorram erros na replicação dos dados:





CALL sys.SET_GTID_PURGED("+<gtidSet>");





Veja um exemplo prático:





CALL sys.SET_GTID_PURGED("+415d143e-3653-30b3-980b-657ad05d72bd:1-44171859");





Atenção especial ao sinal “+”:
Note que é obrigatório utilizar o sinal “+” antes do conjunto GTID (<gtidSet>). Esse sinal indica ao MySQL que o GTID fornecido deve ser adicionado (“append”) ao conjunto já existente, em vez de substituir completamente os valores atuais.





Essa pequena particularidade é extremamente importante e frequentemente ignorada ou esquecida, sendo um dos principais motivos de erros durante a migração e replicação dos dados utilizando GTIDs. Sempre verifique cuidadosamente a presença do sinal “+” ao executar este comando.










Como identificar problemas de replicação no MySQL?


A forma mais eficaz de identificar problemas relacionados à replicação no MySQL é conectar diretamente na instância réplica do MySQL DB System e executar comandos específicos de diagnóstico. Para realizar esses comandos, recomendamos o uso da ferramenta MySQL Shell, que oferece uma interface prática e robusta para administração do MySQL.





Normalmente, os problemas relacionados à replicação são reportados em quatro locais diferentes:





    

  1. Comando SHOW REPLICA STATUS\G
    Este é o método mais utilizado, porém não é o mais completo. Ele oferece uma visão geral do status da replicação, apresentando rapidamente se há algum problema com os threads (SQL_thread ou IO_thread).

    2. 




  2. Tabela performance_schema.replication_connection_status
    Esta tabela deve ser consultada quando o IO_thread (responsável pela comunicação entre Master e Replica) não estiver funcionando corretamente. Nela estarão disponíveis detalhes sobre possíveis falhas de conexão com o servidor mestre (Master).

    3. 




  3. Tabelas performance_schema.replication_applier_status_by_coordinator e performance_schema.replication_applier_status_by_worker
    Estas duas tabelas fornecem informações detalhadas sobre problemas relacionados ao SQL_thread, responsável pela aplicação dos eventos recebidos do servidor mestre (Master). São extremamente úteis quando há falha ou travamento do processo que aplica os comandos SQL.

    4. 




  4. Arquivo de log de erros do MySQL (error log)
    Os erros mais críticos ou detalhados são registrados diretamente no arquivo de log de erros do MySQL, acessível também através da tabela performance_schema.error_log.
    Esse método é especialmente útil em ambientes na nuvem, como no serviço MySQL HeatWave Database Service, permitindo uma fácil análise e acompanhamento detalhado dos problemas de replicação.


    5. 






Utilizando esses métodos em conjunto, é possível identificar rapidamente e com precisão qualquer problema de replicação que esteja ocorrendo no seu ambiente MySQL, agilizando assim a correção e restabelecendo rapidamente o funcionamento correto da replicação.







SELECT logged,
       prio,
       error_code,
       data
FROM   performance_schema.error_log
WHERE  subsystem = 'Repl'
       AND prio = 'Error'
ORDER  BY 1 DESC; 

















mysql> select LOGGED , PRIO, ERROR_CODE, DATA  from performance_schema.error_log where SUBSYSTEM = 'Repl' and PRIO = 'Error' order by 1 desc ;
+----------------------------+-------+------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| LOGGED                     | PRIO  | ERROR_CODE | DATA                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+----------------------------+-------+------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 2025-03-24 20:48:35.415561 | Error | MY-010586  | Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log 'mysql-bin-changelog.001714' position 79540834                                                                                                                                                                                                                                                           |
| 2025-03-24 20:48:35.414871 | Error | MY-010584  | Replica SQL for channel 'replication_channel': Worker 1 failed executing transaction '415d143e-3653-30b3-980b-657ad05d72bd:49842481' at source log mysql-bin-changelog.001714, end_log_pos 81453887; Error 'Plugin 'mysql_native_password' is not loaded' on query. Default database: 'npx'. Query: 'ALTER USER 'replication_user'@'%' IDENTIFIED WITH 'mysql_native_password' AS '*102732A660139466B3EC305AF2DB488933474F4A'', Error_code: MY-001524 |
| 2025-03-24 16:14:25.868055 | Error | MY-010569  | Replica I/O thread aborted while waiting for relay log space                                                                                                                                                                                                                                                                                                                                                                                          |
| 2025-03-24 08:50:37.531874 | Error | MY-010586  | Error running query, replica SQL thread aborted. Fix the problem, and restart the replica SQL thread with "START REPLICA". We stopped at log 'INVALID' position 0                                                                                                                                                                                                                                                                                     |
| 2025-03-24 08:50:37.531007 | Error | MY-013146  | Replica SQL for channel 'replication_channel': Worker 1 failed executing transaction '415d143e-3653-30b3-980b-657ad05d72bd:1' at source log mysql-bin-changelog.000002, end_log_pos 3163; Column 32 of table 'npx.authorizations' cannot be converted from type 'blob' to type 'mediumblob', Error_code: MY-013146                                                                                                                                    |
| 2025-03-24 08:31:17.961232 | Error | MY-010569  | Replica I/O thread aborted while waiting for relay log space                                                                                                                                                                                                                                                                                                                                                                                          |
+----------------------------+-------+------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
6 rows in set (0.00 sec)
















-- Check Replication Channel
SELECT 
  concat(
    conn_status.channel_name, ' (', worker_id, 
    ')'
  ) AS channel, 
  conn_status.service_state AS io_state, 
  applier_status.service_state AS sql_state, 
  format_pico_time(
    if(
      GTID_SUBTRACT(
        LAST_QUEUED_TRANSACTION, LAST_APPLIED_TRANSACTION
      ) = "", 
      "0", 
      abs(
        time_to_sec(
          if(
            time_to_sec(
              APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP
            )= 0, 
            0, 
            timediff(
              APPLYING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP, 
              now()
            )
          )
        )
      )
    ) * 1000000000000
  ) latency, 
  format_pico_time(
    (
      LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP - LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP
    ) * 100000000000
  ) transport_time, 
  format_pico_time(
    (
      LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP - LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP
    ) * 1000000000000
  ) time_to_relay_log, 
  format_pico_time(
    (
      LAST_APPLIED_TRANSACTION_END_APPLY_TIMESTAMP - LAST_APPLIED_TRANSACTION_START_APPLY_TIMESTAMP
    ) * 1000000000000
  ) apply_time, 
  conn_status.LAST_QUEUED_TRANSACTION AS last_queued_transaction, 
  applier_status.LAST_APPLIED_TRANSACTION AS last_applied_transaction 
FROM 
  performance_schema.replication_connection_status AS conn_status 
  JOIN performance_schema.replication_applier_status_by_worker AS applier_status ON applier_status.channel_name = conn_status.channel_name;
  
  





+---------------------------+----------+-----------+---------+----------------+-------------------+------------+-----------------------------------------------+-----------------------------------------------+
| channel                   | io_state | sql_state | latency | transport_time | time_to_relay_log | apply_time | last_queued_transaction                       | last_applied_transaction                      |
+---------------------------+----------+-----------+---------+----------------+-------------------+------------+-----------------------------------------------+-----------------------------------------------+
| replication_channel (1)   | ON       | ON        | 2.56 d  | 2.36 d         | 20.00 us          | 1.86 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50002732 |
| replication_channel (2)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 2.54 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50002601 |
| replication_channel (3)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.85 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50001734 |
| replication_channel (4)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.63 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50001736 |
| replication_channel (5)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.45 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:50001727 |
| replication_channel (6)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 9.59 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49998021 |
| replication_channel (7)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 3.18 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49992586 |
| replication_channel (8)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.18 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959713 |
| replication_channel (9)   | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.19 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959714 |
| replication_channel (10)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.19 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959715 |
| replication_channel (11)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.34 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49959717 |
| replication_channel (12)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.52 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49907064 |
| replication_channel (13)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.48 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49907065 |
| replication_channel (14)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.25 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866179 |
| replication_channel (15)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.21 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866180 |
| replication_channel (16)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.18 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866181 |
| replication_channel (17)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.17 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866182 |
| replication_channel (18)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.15 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866183 |
| replication_channel (19)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.13 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866184 |
| replication_channel (20)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.10 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866185 |
| replication_channel (21)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.09 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866186 |
| replication_channel (22)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.06 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866187 |
| replication_channel (23)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.04 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866188 |
| replication_channel (24)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 5.02 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866189 |
| replication_channel (25)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 4.98 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49866190 |
| replication_channel (26)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 6.01 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49850471 |
| replication_channel (27)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          | 6.01 ms    | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 | 415d143e-3653-30b3-980b-657ad05d72bd:49850472 |
| replication_channel (28)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (29)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (30)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (31)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (32)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (33)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (34)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (35)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (36)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (37)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (38)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (39)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (40)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (41)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (42)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (43)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (44)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (45)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (46)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (47)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (48)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (49)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (50)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (51)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (52)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (53)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (54)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (55)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (56)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (57)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (58)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (59)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (60)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (61)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (62)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (63)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (64)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (65)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (66)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (67)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (68)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (69)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (70)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (71)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (72)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (73)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (74)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (75)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (76)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (77)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (78)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (79)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (80)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (81)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (82)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (83)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (84)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (85)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (86)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (87)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (88)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (89)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (90)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (91)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (92)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (93)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (94)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (95)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (96)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (97)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (98)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (99)  | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (100) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (101) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (102) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (103) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (104) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (105) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (106) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (107) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (108) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (109) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (110) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (111) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (112) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (113) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (114) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (115) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (116) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (117) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (118) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (119) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (120) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (121) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (122) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (123) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (124) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (125) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (126) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (127) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (128) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (129) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (130) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (131) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (132) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (133) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (134) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (135) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (136) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (137) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (138) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (139) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (140) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (141) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (142) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (143) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (144) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (145) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (146) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (147) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (148) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (149) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (150) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (151) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (152) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (153) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (154) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (155) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (156) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (157) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (158) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (159) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (160) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (161) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (162) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (163) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (164) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (165) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (166) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (167) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (168) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (169) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (170) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (171) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (172) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (173) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (174) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (175) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (176) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (177) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (178) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (179) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (180) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (181) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (182) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (183) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (184) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (185) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (186) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (187) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (188) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (189) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (190) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (191) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (192) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (193) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (194) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (195) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (196) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (197) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (198) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (199) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (200) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (201) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (202) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (203) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (204) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (205) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (206) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (207) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (208) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (209) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (210) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (211) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (212) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (213) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (214) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (215) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (216) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (217) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (218) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (219) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (220) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (221) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (222) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (223) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (224) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (225) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (226) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (227) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (228) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (229) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (230) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (231) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (232) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (233) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (234) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (235) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (236) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (237) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (238) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (239) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (240) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (241) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (242) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (243) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (244) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (245) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (246) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (247) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (248) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (249) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (250) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (251) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (252) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (253) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (254) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (255) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
| replication_channel (256) | ON       | ON        |   0 ps  | 2.36 d         | 20.00 us          |   0 ps     | 415d143e-3653-30b3-980b-657ad05d72bd:50467766 |                                               |
+---------------------------+----------+-----------+---------+----------------+-------------------+------------+-----------------------------------------------+-----------------------------------------------+
256 rows in set (0.01 sec)















🔸 channel:





    

  • Identifica o nome do canal de replicação junto com o número específico da thread ou worker.
    • 




  • Ex.: replication_channel (1)

    • 











🔸 io_state:





    

  • Estado do canal relacionado à conexão e transferência de binlogs (I/O Thread).
    • 




  • Valores possíveis:

      

    • ON → A conexão está ativa e funcionando normalmente.
      • 




    • OFF → A conexão não está funcionando ou desconectada.
      • 

    

    • 











🔸 sql_state:





    

  • Estado do canal relacionado à aplicação das transações recebidas (SQL Thread).
    • 




  • Valores possíveis:

      

    • ON → Transações estão sendo aplicadas normalmente.
      • 




    • OFF → Aplicação de transações está parada ou com problemas.
      • 

    

    • 











🔸 latency:





    

  • Latência total da replicação.
    • 




  • Representa o atraso entre o último registro (GTID) recebido no Slave e o último registro efetivamente aplicado.
    • 




  • No exemplo acima: 2.56 d significa que o canal (1) está com 2,56 dias de atraso.
    • 











🔸 time_to_relay_log:





    

  • Tempo gasto pelo Slave para colocar os dados recebidos no relay log.
    • 




  • Normalmente é muito pequeno (no caso é cerca de 20.00 us, ou seja, 20 microssegundos, tempo aceitável e rápido).
    • 






🔸 apply_time:





    

  • Tempo que o Slave gastou para aplicar a última transação recebida no seu banco.
    • 




  • No exemplo: 1.86 ms, 5.18 ms são valores bons e aceitáveis.
    • 











🔸 last_queued_transaction:





    

  • Indica o último GTID recebido (enfileirado) do Master.
    • 






🔸 last_applied_transaction:





    

  • Indica o último GTID aplicado pelo Slave.
    • 




  • Diferença entre este GTID e o “last_queued_transaction” representa o tamanho do atraso na aplicação.
    • 













mysql> show replica status \G ;
*************************** 1. row ***************************
             Replica_IO_State: Waiting for source to send event
                  Source_Host: 100.22.20.186
                  Source_User: replication_user
                  Source_Port: 3306
                Connect_Retry: 60
              Source_Log_File: mysql-bin-changelog.001778
          Read_Source_Log_Pos: 66207953
               Relay_Log_File: relay-log-replication_channel.000006
                Relay_Log_Pos: 70856500
        Relay_Source_Log_File: mysql-bin-changelog.001716
           Replica_IO_Running: Yes
          Replica_SQL_Running: Yes
              Replicate_Do_DB:
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Source_Log_Pos: 70856263
              Relay_Log_Space: 8521164737
              Until_Condition: None
               Until_Log_File:
                Until_Log_Pos: 0
           Source_SSL_Allowed: Yes
           Source_SSL_CA_File:
           Source_SSL_CA_Path:
              Source_SSL_Cert:
            Source_SSL_Cipher:
               Source_SSL_Key:
        Seconds_Behind_Source: 232722
Source_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
  Replicate_Ignore_Server_Ids:
             Source_Server_Id: 925869836
                  Source_UUID: 415d143e-3653-30b3-980b-657ad05d72bd
             Source_Info_File: mysql.slave_master_info
                    SQL_Delay: 0
          SQL_Remaining_Delay: NULL
    Replica_SQL_Running_State: Waiting for dependent transaction to commit
           Source_Retry_Count: 0
                  Source_Bind: 10.27.2.35
      Last_IO_Error_Timestamp:
     Last_SQL_Error_Timestamp:
               Source_SSL_Crl:
           Source_SSL_Crlpath:
           Retrieved_Gtid_Set: 415d143e-3653-30b3-980b-657ad05d72bd:49842481-50356353
            Executed_Gtid_Set: 415d143e-3653-30b3-980b-657ad05d72bd:1-49854029,
df21fd43-067a-11f0-b189-020017028ccd:1-44464
                Auto_Position: 1
         Replicate_Rewrite_DB:
                 Channel_Name: replication_channel
           Source_TLS_Version: TLSv1.2,TLSv1.3
       Source_public_key_path:
        Get_Source_public_key: 1
            Network_Namespace: mysql
1 row in set (0.01 sec)












Monitoramento da Replicação em MySQL





Estado da Replicação





    

  • Replica_IO_Running e Replica_SQL_Running: Indicam se os threads de I/O e SQL estão ativos, essencial para verificar a operacionalidade da replicação.
    • 




  • Replica_IO_State: Exibe o estado do thread de I/O, como “Waiting for source to send event”, mostrando que a réplica está pronta para receber eventos.
    • 






Conexão com o Servidor Fonte





    

  • Source_Host, Source_User, e Source_Port: Informações do host, usuário e porta do servidor fonte, cruciais para confirmar a conexão da réplica.
    • 




  • Connect_Retry: Define o tempo de espera antes de tentar reconectar ao servidor fonte, refletindo a resiliência da conexão.
    • 






Posicionamento nos Logs





    

  • Source_Log_File e Read_Source_Log_Pos: Indicam o arquivo de log atual no servidor fonte e a posição lida, úteis para acompanhar o progresso da replicação.
    • 




  • Relay_Log_File e Relay_Log_Pos: Apontam para o arquivo de log de retransmissão e a posição correspondente na réplica, importantes para o processamento de eventos.
    • 




  • Exec_Source_Log_Pos: Posição até onde o SQL foi executado, crucial para entender até onde as transações foram aplicadas.
    • 






Performance e Atraso





    

  • Seconds_Behind_Source: Mostra o atraso da réplica em relação ao servidor fonte, um indicador vital de performance e estabilidade.
    • 






Segurança





    

  • Source_SSL_Allowed e Source_SSL_Verify_Server_Cert: Confirmam se a conexão utiliza criptografia SSL e se a verificação do certificado do servidor está ativa, assegurando a segurança dos dados.
    • 






Global Transaction Identifiers (GTIDs)





    

  • Auto_Position: Usa posições automáticas baseadas em GTIDs, facilitando o gerenciamento da replicação.
    • 




  • Retrieved_Gtid_Set e Executed_Gtid_Set: Conjuntos de GTIDs que foram recuperados e executados, respectivamente, essenciais para monitorar a integridade e a consistência.
    • 






Erros





    

  • Last_IO_Errno, Last_IO_Error, Last_SQL_Errno, Last_SQL_Error: Informam sobre os erros recentes dos threads de I/O e SQL, fundamentais para diagnóstico e resolução de problemas.
    • 
















mysql> select * from performance_schema.replication_connection_status\G
*************************** 1. row ***************************
                                      CHANNEL_NAME: replication_channel
                                        GROUP_NAME:
                                       SOURCE_UUID: 415d143e-3653-30b3-980b-657ad05d72bd
                                         THREAD_ID: 1651
                                     SERVICE_STATE: ON
                         COUNT_RECEIVED_HEARTBEATS: 3
                          LAST_HEARTBEAT_TIMESTAMP: 2025-03-25 15:16:16.930055
                          RECEIVED_TRANSACTION_SET: 415d143e-3653-30b3-980b-657ad05d72bd:49842481-50396683
                                 LAST_ERROR_NUMBER: 0
                                LAST_ERROR_MESSAGE:
                              LAST_ERROR_TIMESTAMP: 0000-00-00 00:00:00.000000
                           LAST_QUEUED_TRANSACTION: 415d143e-3653-30b3-980b-657ad05d72bd:50396683
 LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.013504
LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.013504
     LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: 2025-03-25 15:18:35.587187
       LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: 2025-03-25 15:18:35.587199
                              QUEUEING_TRANSACTION: 415d143e-3653-30b3-980b-657ad05d72bd:50396684
    QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.201468
   QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: 2025-03-23 09:16:47.201468
        QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: 2025-03-25 15:18:35.587203
1 row in set (0.00 sec)















​O MySQL oferece a tabela performance_schema.replication_connection_status para monitorar o status atual da thread de I/O que gerencia a conexão da réplica com o servidor de origem. Essa tabela fornece informações detalhadas sobre a conexão de replicação, incluindo o estado do serviço, transações recebidas e possíveis erros. A seguir, destacam-se os principais pontos para monitoramento eficaz da replicação:​





Estado da Conexão de Replicação





    

  • SERVICE_STATE: Indica o estado atual da thread de I/O da réplica. Os valores possíveis são:​

      

    • ON:
      • 




    • OFF: 
      • 




    • CONNECTING:
      • 

    

    • 






Identificação da Conexão





    

  • CHANNEL_NAME: Nome do canal de replicação associado a esta conexão.​
    • 




  • SOURCE_UUID: Identificador único universal (UUID) do servidor de origem, útil para identificar a fonte da replicação.​
    • 






Informações sobre Transações





    

  • RECEIVED_TRANSACTION_SET: Conjunto de IDs de transações globais (GTIDs) correspondentes a todas as transações recebidas pela réplica.​
    • 




  • LAST_QUEUED_TRANSACTION: GTID da última transação enfileirada no log de retransmissão.​
    • 




  • LAST_QUEUED_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: Timestamp que indica quando a última transação enfileirada foi confirmada no servidor de origem original.​
    • 




  • LAST_QUEUED_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: Timestamp que indica quando a última transação enfileirada foi confirmada no servidor de origem imediato.​
    • 




  • LAST_QUEUED_TRANSACTION_START_QUEUE_TIMESTAMP: Timestamp que indica quando a última transação foi colocada na fila pelo thread de I/O.​
    • 




  • LAST_QUEUED_TRANSACTION_END_QUEUE_TIMESTAMP: Timestamp que indica quando a última transação foi enfileirada nos arquivos de log de retransmissão.​
    • 






Heartbeats da Replicação





    

  • LAST_HEARTBEAT_TIMESTAMP: Timestamp do último sinal de heartbeat recebido do servidor de origem, indicando que a conexão está ativa mesmo na ausência de eventos recentes.​
    • 




  • COUNT_RECEIVED_HEARTBEATS: Número total de sinais de heartbeat recebidos desde a última reinicialização ou redefinição da réplica.​
    • 






Informações sobre Erros





    

  • LAST_ERROR_NUMBER: Número do erro mais recente que causou a interrupção da thread de I/O. Um valor de 0 indica ausência de erros.​
    • 




  • LAST_ERROR_MESSAGE: Mensagem descritiva do erro mais recente. Se vazia, indica que não houve erros recentes.​
    • 




  • LAST_ERROR_TIMESTAMP: Timestamp indicando quando ocorreu o erro mais recente na thread de I/O.​
    • 






Timestamps das Transações Atuais





    

  • QUEUEING_TRANSACTION: GTID da transação atualmente sendo enfileirada no log de retransmissão.​
    • 




  • QUEUEING_TRANSACTION_ORIGINAL_COMMIT_TIMESTAMP: Timestamp que indica quando a transação atualmente enfileirada foi confirmada no servidor de origem original.​
    • 




  • QUEUEING_TRANSACTION_IMMEDIATE_COMMIT_TIMESTAMP: Timestamp que indica quando a transação atualmente enfileirada foi confirmada no servidor de origem imediato.​
    • 




  • QUEUEING_TRANSACTION_START_QUEUE_TIMESTAMP: Timestamp que indica quando o primeiro evento da transação atualmente enfileirada foi escrito no log de retransmissão pelo thread de I/O.​
    • 
















Para concluir este artigo, apresentamos um checklist detalhado e prático com os principais passos para realizar com sucesso uma migração do AWS Amazon Aurora MySQL para OCI HeatWave MySQL, com o mínimo downtime possível. Abaixo você encontra uma visão macro de todo o processo, de maneira clara e explicativa, permitindo rápida consulta ou revisão para leitores com diferentes níveis de interesse ou pressa.





Checklist Final – Migração AWS Aurora MySQL para OCI HeatWave MySQL





Foram abordadas diversas maneiras práticas e objetivas de monitoramento para garantir uma interpretação clara e precisa das situações críticas durante o processo.










1. Validação dos Pré-requisitos:





Certifique-se que as infraestruturas de banco de dados em AWS e OCI estejam devidamente provisionadas.





Garanta conectividade entre AWS (Aurora MySQL) e OCI (HeatWave MySQL), especialmente liberando a porta padrão MySQL 3306.





Utilize um servidor intermediário (servidor ponte) com MySQL Shell instalado, garantindo conectividade bidirecional total entre AWS e OCI.





Consulte a documentação completa para validação detalhada dos pré-requisitos: Documentação Oficial Oracle.





2. Configurações Obrigatórias no AWS Aurora MySQL (Source):





Habilite e verifique rigorosamente os seguintes parâmetros:





gtid_mode = ON
enforce-gtid-consistency = ON
log_bin = ON
binlog_format = ROW
log_slave_updates = ON





Esses parâmetros garantem a viabilidade técnica e a integridade dos dados durante a replicação.





Mais detalhes sobre essas configurações estão disponíveis na Documentação Oficial AWS.





3. Exportação e Importação com MySQL Shell:





Utilize o MySQL Shell como ferramenta principal para exportação/importação.





Garanta que o processo seja executado seguindo boas práticas indicadas no decorrer do artigo, incluindo geração e manipulação correta dos arquivos JSON para GTID.





4. Configuração do Usuário de Replicação:





Confirme que o usuário de replicação está criado corretamente no AWS Aurora MySQL (origem) e possui as permissões adequadas.





Um exemplo prático para criação do usuário repuser foi detalhado ao longo deste artigo, fornecendo um guia completo para evitar problemas de permissão.





5. Implementação do Canal de Replicação OCI HeatWave MySQL:





Neste passo crucial, verifique a congruência dos GTIDs entre origem e destino utilizando o arquivo .json gerado durante o export.





Caso necessário, ajuste o GTID utilizando o comando SET_GTID_PURGED, garantindo que a replicação delta inicie no ponto correto.





Atenção especial ao detalhado passo a passo fornecido anteriormente para implementação eficaz e segura do canal de replicação HeatWave na OCI.





6. Troubleshooting e Monitoramento:





O artigo forneceu insights valiosos para solucionar problemas comuns durante a migração.





Utilize os scripts e exemplos fornecidos para identificar rapidamente qualquer desvio ou problema.







Referências :










]]>
					
		
		
			
		
		Entendendo o Plano de Execução no POSTGRESQL: Como Melhorar a Performance das Suas Consultas SQL – PARTE 2
		https://furushima.com.br/blog/entendendo-o-plano-de-execucao-no-postgresql-como-melhorar-a-performance-das-suas-consultas-sql-parte-2/
		
		
		Mon, 24 Feb 2025 16:33:17 +0000
				
		
		
		https://furushima.com.br/?p=2566

					
										





Seguindo a parte 2 do artigo sobre Execution Plan (planos de execução), veremos como é o funcionamento da analise e interpretação de um plano de execução no banco de dados POSTGRESQL.





Seguindo o que comumente faço para essa analise, 2 modos podemos estabelecer para essa analise :





    

  1. Plano de execução em modo texto/tabular, onde é visto de forma indentada os steps.
    2. 




  2. Plano de execução em modo tree (arvore), onde é visto de forma grafica os steps.
    3. 






Similar ao oracle database, o POSTGRESQL utilize a seguinte metodologia para interpretação de planos de execução, O plano de execução é lido de baixo para cima e da direita para a esquerda, refletindo a sequência em que o PostgreSQL executa as operações.





No PostgreSQL, os planos de execução são lidos de baixo para cima e da direita para a esquerda. Isso significa que:





    

  • A operação mais profunda (mais aninhada) no plano é a primeira a ser executada.
    • 




  • As operações externas ou superiores são executadas posteriormente, processando os dados obtidos das operações inferiores.
    • 






Essa abordagem permite entender melhor o fluxo da execução da consulta e identificar possíveis gargalos de desempenho.










Para tornar a explicação mais objetiva, vamos analisar um exemplo de query, interpretar seu plano de execução e, posteriormente, verificar possíveis otimizações para tornar a execução do SQL mais eficiente.





 SELECT * FROM (
    (SELECT
        poi.supplier_product ->> 'supplier_product_name' AS name,
        poi.price AS price,
        poi.created_at AS expires_at,
        poi.supplier_product ->> 'supplier_product_manufacturer' AS manufacturer,
        poi.supplier_product ->> 'supplier_product_packing' AS packing,
        poi.supplier_product ->> 'supplier_product_pack_quantity' AS pack_quantity,
        poi.supplier_product ->> 'supplier_product_unit_purchase' AS unit_purchase,
        poi.confirmed_quantity AS quantity_price,
        sp.name AS name_supply,
        sp.identifier AS identifier_supply,
        1 AS order_by
    FROM purchase_order_items poi
    INNER JOIN purchase_orders po ON po.id = poi.purchase_order_id
    INNER JOIN buyer_products bp ON bp.buyer_id = po.buyer_id AND
        bp.code = poi.buyer_product ->> 'buyer_product_code'
    INNER JOIN products p ON p.id = bp.base_product_id
    INNER JOIN suppliers sp ON sp.id = po.supplier_id
    WHERE bp.id = 12081956
        AND poi.created_at < '2025-02-21 16:57:59.225571'
    ORDER BY poi.created_at DESC
    LIMIT 3
    )
    UNION ALL
    (SELECT
        bp.name,
        bp.source_price AS price,
        bp.created_at AS expires_at,
        '' AS manufacturer,
        '' AS packing,
        '' AS pack_quantity,
        '' AS unit_purchase,
        0 AS quantity_price,
        '' AS name_supply, 
        '' AS identifier_supply,
        2 AS order_by
    FROM public.buyer_products bp
    INNER JOIN public.products p ON p.id = bp.base_product_id
    WHERE bp.id = 12081956
        AND bp.source_price IS NOT NULL
    )
) b
ORDER BY order_by
LIMIT 3;










Para analisar os planos de execução, utilizaremos duas ferramentas que auxiliam na visualização e interpretação dos dados. Cada ferramenta apresenta o plano de uma forma diferente, permitindo uma análise mais completa:





    

  1. Modo Tabular: Explain Depesz – Exibe o plano de execução em formato tabular, facilitando a leitura estruturada dos passos. 
    https://explain.depesz.com/

    2. 




  2. Modo Árvore (Tree): Explain Dalibo – Representa o plano de execução graficamente, tornando mais intuitiva a hierarquia das operações.
    https://explain.dalibo.com/
    3. 






📌 Instrução: Clique nos links acima para acessar as ferramentas e seguir o procedimento de visualização dos dois métodos.





Para visualizar o plano de execução em ambos os modos, primeiro precisamos extraí-lo em formato de texto. Para isso, basta adicionar a seguinte declaração no início da query:





EXPLAIN (ANALYZE, COSTS, VERBOSE, BUFFERS)
(...) SQL CODE (...)





Essa instrução fornece informações detalhadas sobre a execução da consulta, incluindo:





    

  • ANALYZE: Executa a query de fato e retorna estatísticas reais de tempo e quantidade de linhas processadas.
    • 




  • COSTS: Exibe os custos estimados de cada operação no plano de execução.
    • 




  • VERBOSE: Apresenta detalhes adicionais, como a estrutura da consulta e a relação das colunas envolvidas.
    • 




  • BUFFERS: Mostra informações sobre o uso do cache de memória (buffers) durante a execução.
    • 






Abaixo, veja como o código SQL completo ficará com a inclusão do EXPLAIN na consulta.





 EXPLAIN (ANALYZE, COSTS, VERBOSE, BUFFERS )
 SELECT * FROM (
    (SELECT
        poi.supplier_product ->> 'supplier_product_name' AS name,
        poi.price AS price,
        poi.created_at AS expires_at,
        poi.supplier_product ->> 'supplier_product_manufacturer' AS manufacturer,
        poi.supplier_product ->> 'supplier_product_packing' AS packing,
        poi.supplier_product ->> 'supplier_product_pack_quantity' AS pack_quantity,
        poi.supplier_product ->> 'supplier_product_unit_purchase' AS unit_purchase,
        poi.confirmed_quantity AS quantity_price,
        sp.name AS name_supply,
        sp.identifier AS identifier_supply,
        1 AS order_by
    FROM purchase_order_items poi
    INNER JOIN purchase_orders po ON po.id = poi.purchase_order_id
    INNER JOIN buyer_products bp ON bp.buyer_id = po.buyer_id AND
        bp.code = poi.buyer_product ->> 'buyer_product_code'
    INNER JOIN products p ON p.id = bp.base_product_id
    INNER JOIN suppliers sp ON sp.id = po.supplier_id
    WHERE bp.id = 12081956
        AND poi.created_at < '2025-02-21 16:57:59.225571'
    ORDER BY poi.created_at DESC
    LIMIT 3
    )
    UNION ALL
    (SELECT
        bp.name,
        bp.source_price AS price,
        bp.created_at AS expires_at,
        '' AS manufacturer,
        '' AS packing,
        '' AS pack_quantity,
        '' AS unit_purchase,
        0 AS quantity_price,
        '' AS name_supply, 
        '' AS identifier_supply,
        2 AS order_by
    FROM public.buyer_products bp
    INNER JOIN public.products p ON p.id = bp.base_product_id
    WHERE bp.id = 12081956
        AND bp.source_price IS NOT NULL
    )
) b
ORDER BY order_by
LIMIT 3;










Após executar o comando EXPLAIN, o PostgreSQL gera um plano de execução em formato de texto. A seguir, veja um exemplo do plano gerado para esta query:








 Limit  (cost=120200.56..120200.57 rows=2 width=252) (actual time=207.212..207.217 rows=3 loops=1)
   Output: ((poi.supplier_product ->> 'supplier_product_name'::text)), poi.price, poi.created_at, ((poi.supplier_product ->> 'supplier_product_manufacturer'::text)), ((poi.supplier_product ->> 'supplier_product_packing'::t
ext)), ((poi.supplier_product ->> 'supplier_product_pack_quantity'::text)), ((poi.supplier_product ->> 'supplier_product_unit_purchase'::text)), poi.confirmed_quantity, sp.name, sp.identifier, (1)
   Buffers: shared hit=64032
   ->  Sort  (cost=120200.56..120200.57 rows=2 width=252) (actual time=186.714..186.718 rows=3 loops=1)
         Output: ((poi.supplier_product ->> 'supplier_product_name'::text)), poi.price, poi.created_at, ((poi.supplier_product ->> 'supplier_product_manufacturer'::text)), ((poi.supplier_product ->> 'supplier_product_packi
ng'::text)), ((poi.supplier_product ->> 'supplier_product_pack_quantity'::text)), ((poi.supplier_product ->> 'supplier_product_unit_purchase'::text)), poi.confirmed_quantity, sp.name, sp.identifier, (1)
         Sort Key: (1)
         Sort Method: quicksort  Memory: 25kB
         Buffers: shared hit=64032
         ->  Append  (cost=120195.05..120200.49 rows=2 width=252) (actual time=186.639..186.704 rows=4 loops=1)
               Buffers: shared hit=64032
               ->  Limit  (cost=120195.05..120195.06 rows=1 width=242) (actual time=186.637..186.640 rows=3 loops=1)
                     Output: ((poi.supplier_product ->> 'supplier_product_name'::text)), poi.price, poi.created_at, ((poi.supplier_product ->> 'supplier_product_manufacturer'::text)), ((poi.supplier_product ->> 'supplier_p
roduct_packing'::text)), ((poi.supplier_product ->> 'supplier_product_pack_quantity'::text)), ((poi.supplier_product ->> 'supplier_product_unit_purchase'::text)), poi.confirmed_quantity, sp.name, sp.identifier, 1
                     Buffers: shared hit=64024
                     ->  Sort  (cost=120195.05..120195.06 rows=1 width=242) (actual time=186.619..186.621 rows=3 loops=1)
                           Output: ((poi.supplier_product ->> 'supplier_product_name'::text)), poi.price, poi.created_at, ((poi.supplier_product ->> 'supplier_product_manufacturer'::text)), ((poi.supplier_product ->> 'supp
lier_product_packing'::text)), ((poi.supplier_product ->> 'supplier_product_pack_quantity'::text)), ((poi.supplier_product ->> 'supplier_product_unit_purchase'::text)), poi.confirmed_quantity, sp.name, sp.identifier, 1
                           Sort Key: poi.created_at DESC
                           Sort Method: top-N heapsort  Memory: 26kB
                           Buffers: shared hit=64024
                           ->  Nested Loop  (cost=2.04..120195.04 rows=1 width=242) (actual time=0.193..186.435 rows=273 loops=1)
                                 Output: (poi.supplier_product ->> 'supplier_product_name'::text), poi.price, poi.created_at, (poi.supplier_product ->> 'supplier_product_manufacturer'::text), (poi.supplier_product ->> 'sup
plier_product_packing'::text), (poi.supplier_product ->> 'supplier_product_pack_quantity'::text), (poi.supplier_product ->> 'supplier_product_unit_purchase'::text), poi.confirmed_quantity, sp.name, sp.identifier, 1
                                 Inner Unique: true
                                 Buffers: shared hit=64024
                                 ->  Nested Loop  (cost=1.75..120194.70 rows=1 width=423) (actual time=0.169..181.896 rows=273 loops=1)
                                       Output: poi.supplier_product, poi.price, poi.created_at, poi.confirmed_quantity, po.supplier_id
                                       Inner Unique: true
                                       Buffers: shared hit=63194
                                       ->  Nested Loop  (cost=1.31..120192.03 rows=1 width=427) (actual time=0.154..181.249 rows=273 loops=1)
                                             Output: poi.supplier_product, poi.price, poi.created_at, poi.confirmed_quantity, po.supplier_id, bp.base_product_id
                                             Join Filter: ((bp.code)::text = (poi.buyer_product ->> 'buyer_product_code'::text))
                                             Rows Removed by Join Filter: 48357
                                             Buffers: shared hit=62374
                                             ->  Nested Loop  (cost=0.87..7304.32 rows=6352 width=19) (actual time=0.037..8.088 rows=9209 loops=1)
                                                   Output: po.id, po.supplier_id, bp.code, bp.base_product_id
                                                   Buffers: shared hit=4649
                                                   ->  Index Scan using buyer_products_pkey on public.buyer_products bp  (cost=0.44..2.68 rows=1 width=15) (actual time=0.016..0.018 rows=1 loops=1)
                                                         Output: bp.id, bp.base_product_id, bp.buyer_id, bp.created_at, bp.updated_at, bp.external_id, bp.name, bp.code, bp.status, bp.source_price, bp.identifier, bp.accept_
alternative_brands, bp.id_scub, bp.internal_scub_id, bp.detailed_description, bp.buyer_product_children
                                                         Index Cond: (bp.id = 12081956)
                                                         Buffers: shared hit=4
                                                   ->  Index Scan using index_purchase_orders_on_buyer_id on public.purchase_orders po  (cost=0.43..7100.53 rows=6704 width=12) (actual time=0.012..6.880 rows=9209 loops=1)
                                                         Output: po.id, po.supplier_id, po.total_price, po.items_count, po.created_at, po.updated_at, po.confirmation_id, po.synchronized_at, po.buyer_id, po.observation, po.
sequence, po.origin_id, po.origin_type, po.external_id, po.redirect_to_legacy, po.name, po.origin_observation, po.opened_at, po.contact, po.terms_and_conditions, po.freight_type, po.minimum_purchase, po.valid_until, po.pay
ment_method_id, po.billing_address, po.uuid, po.created_by, po.created_by_info, po.pending_download, po.text_search_vector, po.request_id, po.upload_id, po.upload_id_gr
                                                         Index Cond: (po.buyer_id = bp.buyer_id)
                                                         Buffers: shared hit=4645
                                             ->  Index Scan using index_purchase_order_items_on_purchase_order_id on public.purchase_order_items poi  (cost=0.44..9.90 rows=225 width=751) (actual time=0.002..0.006 rows=5 lo
ops=9209)
                                                   Output: poi.id, poi.purchase_order_id, poi.created_at, poi.updated_at, poi.status, poi.confirmed_quantity, poi.cancellation, poi.supplier_observation, poi.opening_quantity
, poi.supplier_product, poi.buyer_product, poi.sequence_number, poi.price, poi.comments, poi.origin, poi.uuid, poi.sequence_seller_item_number
                                                   Index Cond: (poi.purchase_order_id = po.id)
                                                   Filter: (poi.created_at < '2025-02-21 16:57:59.225571'::timestamp without time zone)
                                                   Rows Removed by Filter: 0
                                                   Buffers: shared hit=57725
                                       ->  Index Only Scan using products_pkey on public.products p  (cost=0.44..2.68 rows=1 width=4) (actual time=0.002..0.002 rows=1 loops=273)
                                             Output: p.id
                                             Index Cond: (p.id = bp.base_product_id)
                                             Heap Fetches: 0
                                             Buffers: shared hit=820
                                 ->  Index Scan using idx_sp_on_id on public.suppliers sp  (cost=0.29..0.33 rows=1 width=58) (actual time=0.002..0.002 rows=1 loops=273)
                                       Output: sp.id, sp.name, sp.created_at, sp.updated_at, sp.external_id, sp.identifier, sp.identifier_kind, sp.bio_id, sp.synchronized_at, sp.bioid_synchronized_at, sp.phone, sp.plan_nam
e, sp.metadata, sp.is_external
                                       Index Cond: (sp.id = po.supplier_id)
                                       Buffers: shared hit=828
               ->  Subquery Scan on "*SELECT* 2"  (cost=0.87..5.38 rows=1 width=252) (actual time=0.058..0.060 rows=1 loops=1)
                     Output: "*SELECT* 2".name, "*SELECT* 2".price, "*SELECT* 2".expires_at, ''::text, ''::text, ''::text, ''::text, 0, ''::character varying, ''::character varying, 2
                     Buffers: shared hit=8
                     ->  Nested Loop  (cost=0.87..5.34 rows=1 width=262) (actual time=0.054..0.055 rows=1 loops=1)
                           Output: bp_1.name, bp_1.source_price, bp_1.created_at, ''::text, ''::text, ''::text, ''::text, 0, ''::character varying, ''::character varying, 2
                           Inner Unique: true
                           Buffers: shared hit=8
                           ->  Index Scan using idx_bp_on_id_source_price on public.buyer_products bp_1  (cost=0.43..2.67 rows=1 width=66) (actual time=0.013..0.013 rows=1 loops=1)
                                 Output: bp_1.id, bp_1.base_product_id, bp_1.buyer_id, bp_1.created_at, bp_1.updated_at, bp_1.external_id, bp_1.name, bp_1.code, bp_1.status, bp_1.source_price, bp_1.identifier, bp_1.accept_
alternative_brands, bp_1.id_scub, bp_1.internal_scub_id, bp_1.detailed_description, bp_1.buyer_product_children
                                 Index Cond: (bp_1.id = 12081956)
                                 Buffers: shared hit=4
                           ->  Index Only Scan using products_pkey on public.products p_1  (cost=0.44..2.68 rows=1 width=4) (actual time=0.005..0.005 rows=1 loops=1)
                                 Output: p_1.id
                                 Index Cond: (p_1.id = bp_1.base_product_id)
                                 Heap Fetches: 0
                                 Buffers: shared hit=4
 Query Identifier: 273579094919034765
 Planning:
   Buffers: shared hit=129
 Planning Time: 3.160 ms
 JIT:
   Functions: 34
   Options: Inlining false, Optimization false, Expressions true, Deforming true
   Timing: Generation 1.963 ms, Inlining 0.000 ms, Optimization 0.883 ms, Emission 19.683 ms, Total 22.528 ms
 Execution Time: 209.321 ms
(82 rows)
















Assim como no Oracle Database, o PostgreSQL utiliza a indentação, representada pelo símbolo ->, para indicar a ordem de execução das operações, sem atribuir um identificador sequencial a cada passo. Dessa forma, quanto maior a indentação antes do ->, mais interno (ou profundo) é o passo no plano de execução. Isso significa que os passos mais indentados são executados primeiro.










Com o plano de execução em formato de texto, podemos utilizar as duas ferramentas apresentadas para realizar a análise e identificar possíveis gargalos na execução da query. A seguir, exploraremos ambas as abordagens e demonstraremos como detectar os principais pontos de otimização no SQL.


Utilizaremos o plano de execução em formato de texto gerado anteriormente e o submeteremos à ferramenta Explain Depesz, que apresenta a análise no formato tabular. Você pode acessá-la através do seguinte link: Explain Depesz.
https://explain.depesz.com/

























Passos para visualizar o plano de execução no Explain Depesz:





    

  • 🔴 Seta Vermelha: Insira um título para o plano de execução (opcional, mas facilita a organização).
    • 




  • 🟢 Seta Verde: Cole o plano de execução gerado em formato de texto.
    • 




  • 🔵 Seta Azul: Cole a query utilizada para gerar o plano de execução.
    • 




  • ⚫ Seta Preta: Após preencher os campos acima, clique em Submit para processar e visualizar o plano de execução.
    • 





















Após submeter o plano de execução, observe na demonstração abaixo os principais gargalos identificados. Eles são destacados em laranja e vermelho, indicando as operações mais custosas. Além disso, os trechos grifados representam cláusulas da query que podem ser otimizadas para melhorar o desempenho.
















Nested Loop (cost=1.31..120,192.03 rows=1 width=427) (actual time=0.154..181.249 rows=273 loops=1)
Output: poi.supplier_product, poi.price, poi.created_at, poi.confirmed_quantity, po.supplier_id, bp.base_product_id
Join Filter: ((bp.code)::text = (poi.buyer_product ->> ‘buyer_product_code’::text))
Rows Removed by Join Filter: 48,357
Buffers: shared hit=62,374




















📌 O que significa?





    

  • O PostgreSQL está executando um Nested Loop Join para combinar os dados das tabelas buyer_products (bp) e purchase_order_items (poi).
    • 




  • Custo estimado: 120.192 → Indica que esta é uma das etapas mais pesadas do plano.
    • 




  • Tempo real gasto: 181.249 ms → Isso confirma que essa operação está realmente demorando muito.
    • 











🚨 Problema identificado:





    

  • O Nested Loop Join pode ser ineficiente, especialmente quando muitas linhas precisam ser comparadas.
    • 






🔹 Detalhes do Join e o Problema do Filtro










Join Filter: ((bp.code)::text = (poi.buyer_product ->> ‘buyer_product_code’::text))
Rows Removed by Join Filter: 48,357





📌 O que isso significa?





    

  • O PostgreSQL está tentando juntar bp.code com o campo JSON poi.buyer_product ->> 'buyer_product_code'.
    • 




  • Porém, 48.357 linhas foram lidas e removidas porque não atendiam ao filtro.
    Isso significa que muitos dados desnecessários foram carregados antes da filtragem.
    • 











🚨 Problema identificado:





    

  • O filtro de comparação JSON é extremamente ineficiente.
    • 




  • O PostgreSQL precisa percorrer todas as linhas antes de saber quais realmente fazem parte da junção.
    • 











Buffers: shared hit=62,374

📌 O que isso significa?





    

  • 62.374 blocos de memória foram acessados no cache do PostgreSQL.
    • 




  • Isso indica que nenhuma leitura de disco foi necessária, o que é positivo.
    • 




  • Porém, mesmo sem leituras de disco, a query ainda está lenta, o que mostra que o problema está na lógica da consulta, não apenas no hardware.
    • 






🔹 Como otimizar essa parte do plano?





Agora que sabemos que o Nested Loop Join e o filtro JSON são os principais problemas, podemos sugerir melhorias:





1⃣ Criar um índice para melhorar a comparação JSON





A comparação (bp.code)::text = (poi.buyer_product ->> 'buyer_product_code'::text) é muito custosa, pois o PostgreSQL precisa processar os dados JSON antes de compará-los.










🚀 Solução: Criar um índice funcional no JSON





CREATE INDEX idx_poi_buyer_product_code ON purchase_order_items ((buyer_product ->> 'buyer_product_code'));

CREATE INDEX idx_poi_purchase_order_id_created_at ON purchase_order_items (purchase_order_id, created_at DESC);











📌 Impacto esperado:





    

  • O PostgreSQL poderá usar o índice diretamente para encontrar as correspondências.
    • 




  • Reduz drasticamente o número de linhas removidas pelo Join Filter.
    • 




  • Diminui a necessidade de percorrer todas as linhas da tabela.
    • 




  • Reduz tempo da busca no purchase_order_items.
    • 




  • Melhora a performance do Nested Loop.
    • 











📌 Problemas identificados:





    

  1. Join Filter está descartando muitas linhas (48.357 removidas).
    2. 




  2. Nested Loop Join não é eficiente para grandes volumes de dados.
    3. 




  3. Falta de um índice eficiente para buscas no JSON.
    4. 




  4. Falta de um índice composto no purchase_order_items para junções rápidas.
    5. 











🚀 Melhorias sugeridas: 





✅ Criar um índice para otimizar a busca JSON.
✅ Usar um Hash Join em vez de Nested Loop.
✅ Criar um índice composto para melhorar as junções.










Melhoria da Análise e Utilização da Ferramenta EXPLAIN DALIBO





Agora que identificamos os gargalos e propomos soluções, vamos abordar esse problema sob uma nova perspectiva, utilizando a ferramenta EXPLAIN Dalibo.





https://explain.dalibo.com



































































Observe que a caixa do Nested Loop representa o principal gargalo da query, e o “Join Filter” está relacionado à condição ((bp.code)::text = (poi.buyer_product ->> 'buyer_product_code'::text)), o que indica uma junção ineficiente que impacta diretamente o desempenho da consulta.







Conclusão





Neste trabalho, exploramos duas abordagens para analisar e otimizar uma query SQL no PostgreSQL:





    

  1. EXPLAIN ANALYZE → Fornece um relatório detalhado sobre a execução da query, ajudando a identificar custos, tempo de execução e estatísticas importantes.
    2. 




  2. EXPLAIN Dalibo → Apresenta um formato visual e intuitivo, facilitando a identificação dos pontos críticos da consulta, como Nested Loops, filtros ineficientes e ordenações desnecessárias.
    3. 






Além disso, aprendemos a identificar gargalos na execução da query, como o Join Filter ineficiente e a ordenção manual sem suporte de índices. Com isso, aplicamos índices estratégicos e sugerimos a troca de algoritmos de junção para melhorar a performance.





O principal aprendizado aqui é que, antes de otimizar uma query, é essencial entender como o PostgreSQL a executa, localizar os gargalos e aplicar ajustes cirúrgicos, como a criação de índices e a escolha do tipo de junção mais eficiente. 🚀

]]>
					
		
		
			
		
		Entendendo o Plano de Execução no Oracle: Como Melhorar a Performance das Suas Consultas SQL – PARTE 1
		https://furushima.com.br/blog/entendendo-o-plano-de-execucao-no-oracle-como-melhorar-a-performance-das-suas-consultas-sql-parte-1/
		
		
		Fri, 21 Feb 2025 19:08:00 +0000
				
		
		
		https://furushima.com.br/?p=2536

					
										





O Poder do SQL e o Desafio da Performance





Uma das grandes vantagens do SQL é sua natureza declarativa. Isso significa que você não precisa dizer ao banco de dados como obter os dados; basta especificar o que deseja. O otimizador do Oracle (CBO) cuida de encontrar a melhor forma de executar sua consulta.





No entanto, nem sempre o caminho escolhido pelo banco de dados é o mais eficiente. Em consultas complexas ou com grandes volumes de dados, a performance pode ser impactada. Mas como identificar e corrigir esses problemas?





A resposta está no plano de execução.










O Que é um Plano de Execução?





O Execution Plan (Plano de Execução) é um roteiro detalhado que descreve o caminho que o Oracle seguirá para recuperar os dados solicitados em uma consulta SQL. Esse plano é gerado durante a fase de análise (parser) da instrução SQL.
Para construir esse caminho de execução, o Oracle considera diversas informações, entre elas:





    

  • Estatísticas do banco de dados: Incluem system statistics (estatísticas do sistema) e data statistics (estatísticas dos dados), que ajudam a prever a melhor forma de acessar as tabelas e índices.
    • 






    

  • Parâmetros da instância do banco de dados: Configurações específicas da instância que influenciam as decisões do otimizador.
    • 











Esses fatores fornecem insumos para o CBO (Cost-Based Optimizer), o otimizador do Oracle, que calcula a estratégia mais eficiente para executar a consulta SQL. Dessa forma, o plano de execução representa a melhor estimativa do banco de dados sobre como recuperar as informações da maneira mais rápida e eficiente possível.





Diferença entre Execution Plan e Explain Plan





EXPLAIN PLAN (Planos de Explicação) e EXECUTION PLAN (Plano de execução): Qual a Diferença?





Ao trabalhar com consultas SQL no Oracle, é essencial entender a diferença entre dois tipos de planos: EXPLAIN PLAN e EXECUTION PLAN.





Explain Plan (Planos de Explicação)





O EXPLAIN PLAN é uma previsão do que o Oracle planeja fazer para executar a consulta. Quando você roda um EXPLAIN PLAN, o banco de dados gera um plano estimado de execução, com base nas estatísticas atuais das tabelas e nos algoritmos do otimizador. Isso pode ser útil para entender a estratégia escolhida pelo otimizador antes de realmente executar a consulta.





No entanto, o EXPLAIN PLAN pode estar errado ou ser diferente do plano real de execução, porque:





Ele não executa a consulta de fato, apenas faz uma previsão.





Se as estatísticas do banco de dados estiverem desatualizadas, a previsão pode ser imprecisa.











EXPLAIN PLAN FOR 
SELECT * FROM TABELA_XPTO WHERE coluna = 'valor';

SELECT * FROM TABLE(DBMS_XPLAN.DISPLAY);











Execution Plan (Plano de execução)





O EXECUTION PLAN, por outro lado, mostra o que realmente aconteceu quando a consulta foi executada. Ele exibe:





A sequência exata de operações realizadas pelo banco de dados.
O tempo gasto em cada operação.
O número real de linhas processadas.
O impacto da E/S (leitura e escrita em disco ou memória).
Se a consulta utilizou índices, joins, ordenações ou full table scans.





SELECT * FROM TABLE(dbms_xplan.display_cursor('<SQL_ID>','<CHILD_NUMBER>','ALLSTATS LAST  +PEEKED_BINDS +PREDICATE +COST +BYTES ADVANCED'));











Ao analisar a rota seguida pelo banco de dados, você pode identificar se ele escolheu o caminho mais eficiente ou se há uma alternativa ainda mais rápida, como a criação de um atalho.





Abaixo está o plano de execução para a junção de duas tabelas:





--------------------------------------
| Id  | Operation          | Name    |
--------------------------------------
|   0 | SELECT STATEMENT   |         |
|   1 |  HASH JOIN         |         |
|   2 |   TABLE ACCESS FULL| TAB_A   |
|   3 |   TABLE ACCESS FULL| TAB_B   |
--------------------------------------


Cada linha no Execution Plan (Plano de Execução) representa uma operação distinta. Essas operações estão organizadas em uma estrutura hierárquica, formando um relacionamento de pai/filho.

O plano pode ser visualizado como uma árvore. A instrução SELECT, localizada no topo, é a raiz; as tabelas, situadas na parte inferior, são as folhas; e, entre elas, há uma série de operações intermediárias.

Essas operações se dividem em três categorias principais:

- Single-child operations (Operações de filho único)
- Multichild operations (Operações de múltiplos filhos)
- Joins (Junções)










Single-child operations (Operações de filho único)





Como o nome sugere, esse tipo de operação sempre possui exatamente uma operação abaixo dela na árvore do plano de execução. Exemplos comuns incluem:





    

  • Grouping (Agrupamento)
    • 




  • Sorting (Ordenação)
    • 











Multichild operations (Operações de múltiplos filhos)





Essas operações podem ter uma ou mais operações abaixo delas e são mais raras. A mais comum que pode aparecer no plano de execução é a operação UNION (ALL), que combina os resultados de múltiplas consultas.










Joins (Junções)





As junções sempre possuem exatamente dois filhos. Esses filhos podem ser:





    

  • Outras junções
    • 




  • Tabelas
    • 




  • Qualquer outra operação do plano de execução
    • 






Cada um desses componentes desempenha um papel essencial na forma como o banco de dados processa a consulta, influenciando diretamente a eficiência e o desempenho da execução.





Como Ler ou Interpretar um Execution Plan (Plano de Execução)





Em um Execution Plan (Plano de Execução) baseado em texto, a estrutura hierárquica das operações é representada pelo nível de recuo (indentação). Esse recuo indica o relacionamento pai/filho entre as operações.





    

  • Operação pai: É sempre a primeira linha acima de uma operação, com um recuo menor.
    • 




  • Operações filhas: São as linhas logo abaixo da operação pai, recuadas mais para a direita. Elas pertencem à operação pai até que outra linha com o mesmo nível de recuo apareça.
    • 











Essa estrutura ajuda a visualizar como as operações se relacionam e a entender a ordem em que o banco de dados executa cada etapa da consulta.










Para ilustrar a estrutura hierárquica de um Execution Plan (Plano de Execução) no Oracle, vamos analisar um exemplo prático. Suponha que temos duas tabelas: clientes e pedidos. Desejamos selecionar todos os clientes e seus respectivos pedidos. A consulta SQL seria:






SELECT c.nome, p.numero_pedido
FROM clientes c
JOIN pedidos p ON c.cliente_id = p.cliente_id;






Ao gerar o plano de execução para essa consulta, obteríamos uma saída semelhante a:





--------------------------------------------------------------------------------
| Id  | Operation           | Name    | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------
|   0 | SELECT STATEMENT    |         |   100 |  5200 |    10   (0)| 00:00:01 |
|*  1 |  HASH JOIN          |         |   100 |  5200 |    10   (0)| 00:00:01 |
|   2 |   TABLE ACCESS FULL | CLIENTES|   100 |  2600 |     5   (0)| 00:00:01 |
|   3 |   TABLE ACCESS FULL | PEDIDOS |   200 |  5200 |     5   (0)| 00:00:01 |
--------------------------------------------------------------------------------

Vamos interpretar esse plano de execução, destacando as relações pai/filho:

Operação Raiz (Pai Principal):

Id 0: SELECT STATEMENT é a operação raiz. Todas as outras operações são suas filhas diretas ou indiretas.

Operação Filha da Raiz:

Id 1: HASH JOIN é filha direta do SELECT STATEMENT. Esta operação combina as tabelas CLIENTES e PEDIDOS usando um algoritmo de junção hash.
Operações Filhas do HASH JOIN:

Id 2: TABLE ACCESS FULL na tabela CLIENTES. Esta operação lê toda a tabela CLIENTES e fornece os dados para o HASH JOIN.

Id 3: TABLE ACCESS FULL na tabela PEDIDOS. Similarmente, lê toda a tabela PEDIDOS e passa os dados para o HASH JOIN.

Observações Importantes:
Recuo (Indentação): No plano de execução baseado em texto, o nível de recuo indica a hierarquia das operações. Operações com maior recuo são filhas da operação imediatamente acima com menor recuo.

Relação Pai/Filho:

SELECT STATEMENT é o pai do HASH JOIN.
HASH JOIN é pai das operações TABLE ACCESS FULL das tabelas CLIENTES e PEDIDOS.

Entender essa estrutura hierárquica é crucial para analisar como o Oracle executa a consulta e identificar possíveis otimizações, como a criação de índices ou a reescrita da consulta para melhorar o desempenho.











Passo a Passo do Execution Plan





1 – Primeira operação (Seta Vermelha) – Busca inicial das tabelas COLOURS e TOYS





    

  • A execução começa buscando os dados da tabela COLOURS (TABLE ACCESS FULL, linha 4).
    • 




  • Em seguida, os dados da tabela TOYS são buscados (TABLE ACCESS FULL, linha 5).
    • 




  • Esses dados são passados para o primeiro HASH JOIN (linha 3), que combina os resultados dessas tabelas.
    • 






    




    




    2 – Segunda operação (Seta Roxa) – Adicionando a tabela PENS
    




      

    • Após a junção das tabelas COLOURS e TOYS, o banco acessa a tabela PENS (TABLE ACCESS FULL, linha 6).
      • 




    • O resultado do primeiro HASH JOIN é combinado com os dados da tabela PENS através de outro HASH JOIN (linha 2).
      • 




    • Neste ponto, temos um novo dataset contendo os dados já filtrados e processados.
      • 

    




      




      




      3 – Terceira operação (Seta Laranja) – Busca na tabela BRICKS
      




        

      • O próximo passo é buscar os dados da tabela BRICKS (TABLE ACCESS FULL, linha 7).
        • 




      • O resultado da junção anterior (dataset da etapa 2) é agora unido à tabela BRICKS por meio de um HASH JOIN (linha 1).
        • 

      




        




        




        4 – Última operação (Seta Verde) – Retorno do resultado
        




          

        • O HASH JOIN final combina todos os resultados e retorna os dados ao cliente através do SELECT STATEMENT (linha 0).
          • 




        • Como não há mais filhos na estrutura, essa etapa finaliza a execução.

          • 

        




          




          




          Resumo da Ordem de Execução
          




          A ordem correta de execução pode ser descrita assim:
          




            

          1. TABLE ACCESS FULL COLOURS (linha 4) → primeiro conjunto de dados.
            2. 




          2. TABLE ACCESS FULL TOYS (linha 5) → segundo conjunto de dados.
            3. 




          3. HASH JOIN (linha 3) → combinação de COLOURS e TOYS.
            4. 




          4. TABLE ACCESS FULL PENS (linha 6) → terceiro conjunto de dados.
            5. 




          5. HASH JOIN (linha 2) → combinação do resultado do primeiro HASH JOIN com PENS.
            6. 




          6. TABLE ACCESS FULL BRICKS (linha 7) → quarto conjunto de dados.
            7. 




          7. HASH JOIN (linha 1) → combinação do resultado da segunda junção com BRICKS.
            8. 




          8. SELECT STATEMENT (linha 0) → retorna o resultado final ao cliente.
            9. 

          




          




          




          




          




          




          Compreender a estrutura e a ordem de execução de um plano de execução é essencial para diagnosticar e otimizar o desempenho de consultas no Oracle Database. Ao analisar detalhadamente cada operação e suas interações, é possível identificar gargalos e aplicar melhorias específicas, resultando em consultas mais eficientes e sistemas mais responsivos.
          




          




          Referencias : 
          https://blogs.oracle.com/connect/post/how-to-read-an-execution-plan
          




          




          




          
]]>          
					
		
		
			          
		
		EXECUTANDO DATAPUMP EXPORT (EXPDP) NO ORACLE RDS
		https://furushima.com.br/blog/executando-datapump-export-expdp-no-oracle-rds/
		
		
		Tue, 02 Apr 2024 18:50:37 +0000
				
		
		
		
		https://dev.furushima.com.br/?p=2174

					
										
          




          Neste tutorial, vamos explorar como realizar uma exportação de dados utilizando o Datapump Export via a API DBMS_DATAPUMP no Oracle Database. Este método é altamente flexível e permite exportar dados de forma eficiente e controlada.
          




          Etapa 1: Configurando a Exportação
          




          Antes de iniciar a exportação, certifique-se de executar este código no banco de dados de origem, onde deseja realizar o export:
          




          DECLARE
    Bkp NUMBER;
    s VARCHAR2(30000);
BEGIN
    -- Abrindo um job de exportação no Data Pump
    Bkp := DBMS_DATAPUMP.OPEN(
        operation => 'EXPORT',
        job_mode => 'SCHEMA',
        job_name => NULL
    );

    -- Adicionando arquivo de exportação
    DBMS_DATAPUMP.ADD_FILE(
        handle    => Bkp,
        filename  => 'datapump_source_DATA_F.dmp',
        directory => 'DATA_PUMP_DIR',
        filetype  => dbms_datapump.ku$_file_type_dump_file,
        reusefile => 1
    );

    -- Adicionando arquivo de log
    DBMS_DATAPUMP.ADD_FILE(
        handle    => Bkp,
        filename  => 'datapump_source_DATA_F.log',
        directory => 'DATA_PUMP_DIR',
        filetype  => dbms_datapump.ku$_file_type_log_file
    );

    -- Selecionando owners para exportação
    SELECT LISTAGG('''' || owner || '''', ', ') WITHIN GROUP (ORDER BY owner) 
    INTO s
    FROM (
        SELECT username AS owner
        FROM dba_users
        WHERE username NOT IN (
            'ANONYMOUS', 'SYS', 'SYSTEM', 'SYSAUX',
            'APPQOSSYS', 'AUDSYS', 'CTXSYS', 'DBSNMP',
            'DIP', 'GSMADMIN_INTERNAL', 'GSMCATUSER', 'GSMUSER',
            'ORACLE_OCM', 'SYSBACKUP', 'SYSDG', 'SYSKM',
            'XDB', 'XS$NULL', 'RDSADMIN', 'SYSRAC',
            'SYS$UMF', 'REMOTE_SCHEDULER_AGENT', 'GGSYS',
            'DBSFWUSER'
        )
    );

    -- Aplicando filtro para exportação dos schemas selecionados
    DBMS_DATAPUMP.METADATA_FILTER(Bkp, 'SCHEMA_LIST', s);

    -- Iniciando o job de exportação
    DBMS_DATAPUMP.START_JOB(Bkp);
END;
/

          




          




          Etapa 2: Acompanhando o Progresso da Exportação
          




          Para verificar o progresso da exportação, execute o seguinte comando no banco de dados de origem:
          




          SELECT text
          FROM TABLE(rdsadmin.rds_file_util.Read_text_file (
          p_directory => 'DATA_PUMP_DIR',
          p_filename => 'datapump_source_DATA_F.log'
          ));
          




          




          Etapa 3: Verificando o Arquivo Gerado
          




          Para verificar o arquivo gerado no diretório, utilize o seguinte comando no banco de dados de origem:
          




          SET LINES 200 PAGES 200
          COL filename FORMAT A100
          SELECT filename,
          ROUND(filesize / 1024 / 1024 / 1024) AS SIZE_GB
          FROM TABLE(rdsadmin.rds_file_util.Listdir('DATA_PUMP_DIR'))
          WHERE filename LIKE 'datapump_source_DATA_F%'
          ORDER BY mtime;
          




          




          Para as próximas etapas sobre transferência para o ambiente de destino e criação de DBLINK e DIRECTORY, sugiro verificá-las diretamente na documentação oficial da Oracle , pois podem variar dependendo da configuração e políticas de segurança do ambiente.
          




          




          Criado por : Carlos Furushima
          




          




          




          




          
]]>