[
  {
    "id": "FF-202603-002",
    "date": "2026-03-08",
    "contributor": {
      "name": "Diego Cabrera",
      "team": "Field Architecture",
      "client": "Strategic Migration Customer",
      "context": "Production migration",
      "confidence": "validated"
    },
    "product": "ADB-S Dedicated Elastic Pool (DEP)",
    "version": "23ai",
    "severity": "HIGH",
    "category": "limitation",
    "summary": "ADG must be disabled before joining Dedicated Elastic Pool",
    "detail": "When attempting to add an ADB-S instance with active Autonomous Data Guard\nto a Dedicated Elastic Pool, the operation fails. ADG must be explicitly\ndisabled before the instance can join the DEP. This is a known issue\nacknowledged by Oracle but not prominently documented.\n\nImpact: requires a brief HA gap during DEP onboarding. Must coordinate\nwith the customer's change window.\n",
    "workaround": "Disable ADG \u2192 join DEP \u2192 re-enable ADG. Plan for ~15 min HA gap.",
    "oracle_sr": "",
    "status": "acknowledged",
    "resolved_date": null,
    "resolution": null,
    "affects_matrix": "Elastic Pool Membership",
    "tags": [
      "dep",
      "adg",
      "elastic-pool",
      "ha",
      "limitation"
    ]
  },
  {
    "id": "FF-202603-003",
    "date": "2026-03-05",
    "contributor": {
      "name": "Diego Cabrera",
      "team": "Field Architecture",
      "client": "Strategic Migration Customer",
      "context": "Production migration",
      "confidence": "validated"
    },
    "product": "ADB-S Dedicated Elastic Pool (DEP)",
    "version": "23ai",
    "severity": "MEDIUM",
    "category": "undocumented",
    "summary": "DEP maintenance window immutable post-creation \u2014 change only via SR",
    "detail": "The maintenance window for a Dedicated Elastic Pool cannot be changed\nafter creation via Console, CLI, or API. The only way to change it is\nby filing a Service Request with Oracle Support.\n\nDefault window is Saturday/Sunday. Other days require specifying at\ncreation time (which itself has the CLI bug \u2014 see FF-202603-001) or\nrequesting via SR.\n",
    "workaround": "Set desired window at DEP creation time (via Console, not CLI). If missed, file SR.",
    "oracle_sr": "",
    "status": "acknowledged",
    "resolved_date": null,
    "resolution": null,
    "affects_matrix": "Auto Patching",
    "tags": [
      "dep",
      "maintenance-window",
      "immutable",
      "sr-required"
    ]
  },
  {
    "id": "FF-202603-004",
    "date": "2026-03-01",
    "contributor": {
      "name": "Diego Cabrera",
      "team": "Field Architecture",
      "client": "Strategic Migration Customer",
      "context": "Production migration",
      "confidence": "validated"
    },
    "product": "ADB-S",
    "version": "23ai",
    "severity": "MEDIUM",
    "category": "gotcha",
    "summary": "DEP provisioning takes days to weeks depending on capacity",
    "detail": "Dedicated Elastic Pool provisioning is NOT instant like ADB-S Serverless.\nIt requires physical Exadata infrastructure allocation. Lead time varies\nfrom 3 days (if capacity available in region) to 2-3 weeks (if capacity\nneeds to be provisioned).\n\nBilling starts only at AVAILABLE state, not at request time.\nCo-location of existing ADB-S instances happens at the next maintenance\nwindow after joining, not immediately.\n",
    "workaround": "Request DEP early in the project timeline. Don't make it a critical-path dependency in week 1.",
    "oracle_sr": "",
    "status": "acknowledged",
    "resolved_date": null,
    "resolution": null,
    "affects_matrix": "Elastic Pool Membership",
    "tags": [
      "dep",
      "provisioning",
      "lead-time",
      "capacity",
      "planning"
    ]
  },
  {
    "id": "FF-202603-005",
    "date": "2026-02-20",
    "contributor": {
      "name": "Diego Cabrera",
      "team": "Field Architecture",
      "client": "Strategic Migration Customer",
      "context": "Production migration",
      "confidence": "observed"
    },
    "product": "ADB-S",
    "version": "23ai",
    "severity": "LOW",
    "category": "gotcha",
    "summary": "Refreshable Clone failed refresh leaves clone in AVAILABLE state \u2014 detection delay",
    "detail": "When a Refreshable Clone's auto-refresh fails, the clone remains in\nAVAILABLE state (not DISCONNECTED). The Elastic Pool leader monitors\nlifecycle state changes, not refresh success/failure.\n\nThis means a failed refresh is NOT immediately detected by the\ninfrastructure. The stale data window equals the ADG RTO for\nunplanned scenarios.\n",
    "workaround": "Planned switchovers: DBMS_PROXY_SQL.DISABLE_READ_ONLY_OFFLOAD proactively.\nUnplanned: OCI Events + OCI Function that monitors refresh state and\ndisables read offload automatically. Reduces stale window to ~ADG RTO.\n",
    "oracle_sr": "",
    "status": "monitoring",
    "resolved_date": null,
    "resolution": null,
    "affects_matrix": "Refreshable Clone",
    "tags": [
      "refreshable-clone",
      "stale-reads",
      "elastic-pool",
      "detection-delay",
      "proxysql"
    ]
  }
]
