Fix 30 KB errors: ExaCS storage 3-10x wrong, ECPU transition, IOPS limits, missing shapes

Cross-referenced all 70+ KB files against official Oracle docs. Critical fixes:
- ExaCS: storage was flash cache not usable disk (76.8→190.8 TB QR), added X11M, removed X10M
- ADB-S: OCPU→ECPU migration, 26ai as default, cross-region RTO 15→10 min
- Compute: E5 max 94→126, A2 80→78, added E6/A4/BM shapes, 11 GPU shapes
- Storage: Higher Perf IOPS 35K→50K, UHP 450K→300K, File Storage 25K→50K
- DBCS: E5.Flex max 94→64, storage 80→150 TB, added 26ai
- Networking: FastConnect +400 Gbps, NSG max 120 rules

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

kb/sizing/adb-scaling-behavior.yaml

@@ -4,9 +4,10 @@ description: ADB-S auto-scaling behavior, timing, and sizing implications.
 ---
 
 auto_scaling:
+  notes: "OCPU is legacy billing. ECPU is now default. 1 OCPU ≈ 4 ECPUs."
   ocpu_scaling:
     trigger: "CPU demand exceeds current allocation"
-    max_scale: "3x base OCPUs (up to 128 OCPU maximum)"
+    max_scale: "3x base OCPUs/ECPUs (up to 128 OCPU / 512 ECPU maximum)"
     ramp_up_time: "2-3 minutes to begin scaling"
     ramp_down_time: "After sustained low utilization (5-10 minutes)"
     billing: "Only billed during active scaling period, per OCPU per second"

kb/sizing/cpu-conversion-ratios.yaml

@@ -65,8 +65,8 @@ adb_s_sizing:
 memory_sizing:
   oci_shapes:
     standard_e4: "16 GB per OCPU (VM.Standard.E4.Flex)"
-    standard_e5: "16 GB per OCPU (VM.Standard.E5.Flex)"
+    standard_e5: "up to 64 GB per OCPU (VM.Standard.E5.Flex, default 16)"
     standard_a1: "6 GB per OCPU (VM.Standard.A1.Flex / Ampere)"
-    standard_a2: "8 GB per OCPU (VM.Standard.A2.Flex / Ampere)"
+    standard_a2: "up to 64 GB per OCPU (VM.Standard.A2.Flex / Ampere)"
     optimized3: "14 GB per OCPU (VM.Optimized3.Flex)"
     dense_io_e4: "32 GB per OCPU + local NVMe (VM.DenseIO.E4.Flex)"

kb/sizing/storage-iops.yaml

@@ -21,18 +21,19 @@ block_volume:
 
     - name: "Higher Performance"
       iops_per_gb: 75
-      max_iops: 35000
+      max_iops: 50000
       throughput_mbps_per_gb: 0.6
-      max_throughput_mbps: 480
+      max_throughput_mbps: 680
       use_when: "Database data files, high-throughput applications"
 
     - name: "Ultra High Performance"
       iops_per_gb: 90
-      max_iops: 120000
+      max_iops: 300000
+      iops_range: "75,000 - 300,000 (at 30-120 VPU)"
       throughput_mbps_per_gb: 0.72
       max_throughput_mbps: 2680
       use_when: "Extreme IOPS requirements, OLTP databases"
-      notes: "Only available with certain compute shapes"
+      notes: "Only available with certain compute shapes. IOPS scales with VPU (30-120)."
 
   sizing_guidance: |
     1. Determine required IOPS (from AWR, CloudWatch, or application benchmarks)

kb/sizing/storage-performance.yaml

@@ -33,14 +33,14 @@ storage_tiers:
   block_volume_higher_performance:
     type: "Block Volume (Higher Performance)"
     iops_per_gb: 75
-    max_iops: 35000
+    max_iops: 50000
     throughput_kbps_per_gb: 600
-    max_throughput_mbps: 600
+    max_throughput_mbps: 680
     latency_us: "Sub-millisecond"
 
   block_volume_uhp:
     type: "Block Volume (Ultra High Performance)"
-    max_iops: 450000
+    max_iops: 300000
     max_throughput_mbps: 2680
     notes: "Requires UHP-enabled shapes"
 
@@ -53,7 +53,7 @@ storage_tiers:
 
   file_storage:
     type: "File Storage (NFS)"
-    max_iops: 25000
+    max_iops: 50000
     max_throughput_mbps: 1200
     latency: "Sub-millisecond"
     use_for: "Shared file access, NFS workloads"