Diagram generation: ref-arch-driven procedure + spec validator + KB enrichment
The diagram path now follows a documented standard procedure (lookup the closest Oracle Architecture Center reference → confirm components → author absolute_layout → spec validator → render → visually verify) and ships persistent guardrails so layout regressions can't recur. Persistent procedure changes (apply to all users, all sessions): - tools/diagram_spec_validator.py — geometry checks (CONTAINER_TOO_THIN, CONTAINER_PADDING_VIOLATION, LABEL_OVERFLOW_PARENT) run BEFORE either renderer (drawio + PPTX). Catches the subnet-collapse / label-overflow bugs that the post-render drawio validator missed. - tools/oci_diagram_gen.py + tools/oci_pptx_diagram_gen.py — call the spec validator before emitting any output. Adds mysql / mysql_heatwave type aliases. - tools/archcenter_pattern_lookup.py — scores against cached page descriptions (not just the 1-line summary), supports --queries for multi-fragment composition, and applies synonym expansion via kb/architecture-center/synonyms.yaml so "LB HA cross AD" matches "load balancer high availability availability domain". - kb/architecture-center/synonyms.yaml — canonical synonym table (load balancer, autonomous database, data guard, …) used by the lookup scorer. KB enrichment: - tools/archcenter_description_fetcher.py + 121 cached _description.md under kb/diagram/assets/archcenter-refs/<slug>/. Removes the runtime dependency on docs.oracle.com when authoring specs and feeds the pattern-lookup scorer. - 110+ cached .drawio / .svg / .png references for offline reuse, plus the OCI Toolkit v24.2 import (kb/diagram/assets/oci-toolkit-drawio). Documentation: - docs/skill/output-formats.md — new "Standard diagram-generation procedure (MANDATORY)" + geometry rules + the new validator entry. - SKILL.md option 2 — references the mandatory procedure. - README.md — describes the spec validator, archcenter_pattern_lookup and description fetcher, and updates the KB-health table. Tooling that backs the procedure (cumulative across recent sessions): tools/archcenter_case_runner.py, archcenter_batch_driver.py, archcenter_zip_downloader.py, drawio_visual_validator.py, drawio_fidelity_eval.py, harvest_drawio_icon.py, import_oci_library.py, oci_pptx_diagram_gen.py, oci_pptx_render.py, refresh_pptx_icon_index.py. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
root
@@ -0,0 +1,224 @@
|
||||
# Implement disaster recovery with cross-zonal Data Guard on Oracle Database@AWS
|
||||
|
||||
- Source: https://docs.oracle.com/en/solutions/cross-zone-dr-db-at-aws/index.html
|
||||
- Date: 2025-08
|
||||
- Type: reference-architecture
|
||||
- Services: exacs, adg, aws
|
||||
- Tags: database, multicloud, aws, ha-dr
|
||||
|
||||
## Summary (catalog)
|
||||
|
||||
Cross-AZ Data Guard on Database@AWS for HA. Synchronous redo transport between AZs for zero data loss. Fast-Start Failover for automatic database switchover on failure.
|
||||
|
||||
## Architecture (fetched from source)
|
||||
|
||||
About Implementing Disaster Recovery with Cross-Zone Data Guard on Oracle Database@AWS
|
||||
|
||||
|
||||
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
-
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
-
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
-
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Previous
|
||||
Next
|
||||
JavaScript must be enabled to correctly display this content
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
About Implementing Disaster Recovery with Cross-Zone Data Guard on Oracle Database@AWS
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
This solution playbook describes the Oracle Active Data Guard setup on Oracle Exadata Database Service on Dedicated
|
||||
Infrastructure on Oracle Database@AWS across two availability zones in the same region. Oracle Database@AWS is the Oracle Database service running on Oracle Cloud Infrastructure (OCI), colocated in Amazon AWS data centers. Oracle Database@AWS offers Oracle Exadata Database Service on Dedicated
|
||||
Infrastructure and Oracle Autonomous Database on Dedicated Exadata Infrastructure , natively integrated into the AWS platform. Oracle Data Guard enables you to synchronously transport the data from the primary to the standby database to ensure zero data loss.
|
||||
|
||||
|
||||
|
||||
Oracle Database@AWS offers built-in high availability and scalability with Oracle Real Application Clusters (Oracle
|
||||
RAC) while ensuring low latency for AWS applications. Extending the solution with an Active Data Guard standby database hosted on another Oracle Exadata Cloud Infrastructure in another availability zone within the same region enhances availability and data protection in case of an entire availability zone outage.
|
||||
|
||||
|
||||
|
||||
Active Data Guard adds comprehensive data corruption prevention with automatic block repair, online upgrades and migrations, offload workload to standby with read-mostly scale-out, and enable Application Continuity to mask database outages during planned and unplanned events from end-users and ensure uninterrupted applications.
|
||||
|
||||
|
||||
|
||||
Oracle Exadata Database
|
||||
Service on Oracle Database@AWS is certified at the Gold tier of Oracle Maximum Availability Architecture (MAA). This validation confirms that the service meets Oracle’s highest standards for high availability and disaster recovery, with support for failover across multiple AWS availability zones as well as across AWS regions. With Gold MAA certification, Oracle Exadata Database
|
||||
Service on Oracle Database@AWS blends cloud flexibility with proven resilience, ensuring your mission-critical workloads stay protected from server failures as well as data center outages.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Before You Begin
|
||||
|
||||
|
||||
|
||||
|
||||
Ensure your deployment meets the following requirement:
|
||||
|
||||
|
||||
The configuration and deployment instructions in this solution playbook require the Exadata infrastructure and the Exadata VM Cluster to be already deployed in the standby availability zone, and that the network IP CIDR ranges for the primary and standby Exadata VM Clusters do not overlap.
|
||||
|
||||
|
||||
Review the following resources:
|
||||
|
||||
|
||||
|
||||
- Oracle Exadata Database Service on Dedicated Infrastructure Overview
|
||||
|
||||
- Deploy Oracle
|
||||
Database@AWS
|
||||
|
||||
|
||||
Review these related solutions:
|
||||
|
||||
|
||||
|
||||
- Security best practices for your VPC in the Amazon Virtual Private Cloud User Guide
|
||||
|
||||
- Plan for AWS IP address space using ODB Network Design
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
About Required Services and
|
||||
Roles
|
||||
|
||||
|
||||
|
||||
|
||||
This solution requires the following services and roles:
|
||||
|
||||
|
||||
|
||||
- Oracle Cloud Infrastructure
|
||||
Networking
|
||||
|
||||
- Oracle Exadata Database
|
||||
Service
|
||||
|
||||
|
||||
These are the roles needed for each service.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Service Name: Role
|
||||
Required to...
|
||||
|
||||
|
||||
|
||||
|
||||
Oracle Exadata Database
|
||||
Service : manage database-family
|
||||
Manage the database, including adding and operating Active Data Guard deployments
|
||||
|
||||
|
||||
OCI Networking : manage vcn-family
|
||||
Manage the network components, including VCNs, subnets, security rules, and VCN
|
||||
peering
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Title and Copyright Information
|
||||
|
||||
|
||||
|
||||
|
||||
Implement Disaster Recovery with Cross-Zone Data Guard on Oracle Database@AWS
|
||||
|
||||
|
||||
G40862-01
|
||||
|
||||
|
||||
August 2025
|
||||
|
||||
|
||||
Copyright © 2025,
|
||||
|
||||
Oracle and/or its affiliates.
|
||||
Reference in New Issue
Block a user