Senior DevOps Engineer (OCI-Azure)

Talent Groups is seeking a Senior DevOps Engineer specializing in Oracle Database on Azure. The role involves managing Exadata infrastructure, ensuring network connectivity, security, and overseeing migration strategies while employing automation and monitoring techniques.

Responsibilities:

• Understand that Exadata infrastructure runs in Azure datacenters but is managed via OCI control plane and provisioned through the Azure portal (linking an Azure subscription to an OCI tenancy)
• Know service scope (RAC support, Exadata performance, Azure billing/MACC) and onboarding steps
• Hands‑on with creating Exadata Infrastructure, VM Clusters, and Databases from the OracleDB@Azure blade; familiarity with supported models (X9M/X11M, and Exascale), quotas/limits, maintenance windows, and regions/AZs
• IP address reservation differences (e.g., 13 IPs on client subnet vs 3 in OCI), delegated subnet constraints, and how Azure/OCI APIs interplay
• Building delegated subnets (Oracle. Database/network Attachment), peering/hub‑and‑spoke, NSGs, route tables/NVAs (e.g., Azure Firewall), no default internet egress, and split‑DNS patterns
• Advanced networking features for Database Azure (regions, registration steps before creating the delegated subnet)
• ExpressRoute/S2S VPN planning, bandwidth/resiliency, and routing inspection through hub NVA
• Azure RBAC/Policies/Blueprints for Oracle resources in the subscription and resource groups; secure delegated subnets (private only, NSGs, routing through NVA)
• Key Vault/Secrets handling for DB credentials, wallet files, and automation pipelines; logging/monitoring via Azure Monitor and Defender for Cloud (often with Azure Arc)
• Storage cells, ASM, DB nodes, resource management, IORM, patching cycles, and AWR‑based performance tuning; experience administering CDB/PDB and RAC in production
• RMAN strategies, Data Guard topologies, and cutover playbooks aligned to RPO/RTO; understanding of service‑managed backup networks for OD@A
• Physical & logical migration paths: RMAN, Data Guard, Data Pump, Oracle GoldenGate, and especially Oracle Zero Downtime Migration (ZDM) for minimal‑downtime cutovers from on‑prem Exadata → OD@A
• Reference blueprints for OD@A migrations with ZDM: network setup, route tables, hub NVA routing to on‑prem, and stepwise execution
• Azure CLI/PowerShell, ARM/Bicep or Terraform/OpenTofu for consistent provisioning of VNets, delegated subnets, route tables, and OD@A resources (using the Oracle/OD@A examples)
• CI/CD (GitHub Actions/Azure DevOps) for promotion of infra changes, parameterized deployments, and post‑provision validation
• Azure Monitor metrics/logs for network and VM cluster connectivity; OD@A monitoring from Oracle side; alerting on latency/throughput; change windows and patch orchestration awareness
• Read/interpret AWR and workload characteristics to size OD@A shapes/VM clusters and storage; know inherited region/AZ constraints and VM‑cluster limits per Exadata infrastructure
• Dry‑runs for migration, back‑out plan, checkpoint criteria, and incident handling during DNS/app switchover
• Stakeholder alignment: App owners, network, security, DBA, and business sign‑off on RPO/RTO and the minimal‑downtime objective (e.g., ZDM with Data Guard)

Requirements:

• Understand that Exadata infrastructure runs in Azure datacenters but is managed via OCI control plane and provisioned through the Azure portal (linking an Azure subscription to an OCI tenancy)
• Know service scope (RAC support, Exadata performance, Azure billing/MACC) and onboarding steps
• Hands‑on with creating Exadata Infrastructure, VM Clusters, and Databases from the OracleDB@Azure blade
• Familiarity with supported models (X9M/X11M, and Exascale), quotas/limits, maintenance windows, and regions/AZs
• IP address reservation differences (e.g., 13 IPs on client subnet vs 3 in OCI), delegated subnet constraints, and how Azure/OCI APIs interplay
• Azure VNet design for OracleDB @ Azure: Building delegated subnets (Oracle. Database/network Attachment), peering/hub‑and‑spoke, NSGs, route tables/NVAs (e.g., Azure Firewall), no default internet egress, and split‑DNS patterns
• Advanced networking features for Database Azure (regions, registration steps before creating the delegated subnet)
• ExpressRoute/S2S VPN planning, bandwidth/resiliency, and routing inspection through hub NVA
• Azure RBAC/Policies/Blueprints for Oracle resources in the subscription and resource groups; secure delegated subnets (private only, NSGs, routing through NVA)
• Key Vault/Secrets handling for DB credentials, wallet files, and automation pipelines; logging/monitoring via Azure Monitor and Defender for Cloud (often with Azure Arc)
• Exadata fundamentals: Storage cells, ASM, DB nodes, resource management, IORM, patching cycles, and AWR‑based performance tuning
• Experience administering CDB/PDB and RAC in production
• RMAN strategies, Data Guard topologies, and cutover playbooks aligned to RPO/RTO
• Understanding of service‑managed backup networks for OD@A
• Physical & logical migration paths: RMAN, Data Guard, Data Pump, Oracle GoldenGate, and especially Oracle Zero Downtime Migration (ZDM) for minimal‑downtime cutovers from on‑prem Exadata → OD@A
• Reference blueprints for OD@A migrations with ZDM: network setup, route tables, hub NVA routing to on‑prem, and stepwise execution
• Scripting & IaC: Azure CLI/PowerShell, ARM/Bicep or Terraform/OpenTofu for consistent provisioning of VNets, delegated subnets, route tables, and OD@A resources (using the Oracle/OD@A examples)
• CI/CD (GitHub Actions/Azure DevOps) for promotion of infra changes, parameterized deployments, and post‑provision validation
• Azure Monitor metrics/logs for network and VM cluster connectivity; OD@A monitoring from Oracle side; alerting on latency/throughput; change windows and patch orchestration awareness
• Read/interpret AWR and workload characteristics to size OD@A shapes/VM clusters and storage; know inherited region/AZ constraints and VM‑cluster limits per Exadata infrastructure
• Runbook ownership: Dry‑runs for migration, back‑out plan, checkpoint criteria, and incident handling during DNS/app switchover
• Stakeholder alignment: App owners, network, security, DBA, and business sign‑off on RPO/RTO and the minimal‑downtime objective (e.g., ZDM with Data Guard)