Skip to content

Commit b92661b

Browse files
author
Antoun Moubarak
committed
Update to add image title
1 parent 4462165 commit b92661b

File tree

1 file changed

+12
-3
lines changed

1 file changed

+12
-3
lines changed

cloud-architecture/custom-apps-and-consolidation/db-migration/db-migration-examples/files/oracle-database-migration-to-base-database-service-an-example-migration.md

Lines changed: 12 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -481,11 +481,17 @@ Customer is responsible for setting the access rules to services and environment
481481

482482
### Physical Architecture
483483

484-
![Future State Production Deployment Diagram – Base Database Workload Multi-AD, DR Design Diagram](images/oracle-database-migration-to-base-database-service-an-example-migration-2NODEDB_DRwithinRegion.png)
484+
<figure>
485+
<img src="images/oracle-database-migration-to-base-database-service-an-example-migration-2NODEDB_DRwithinRegion.png" title="Production Deployment Diagram – Multi-AD with near DR Design Diagram"/>
486+
<figcaption>Production Deployment Diagram – Multi-AD with near DR Design Diagram</figcaption>
487+
</figure>
485488

486489
For the production environment Oracle RAC database will be deployed to ensure High Availability in Single AD with a Disaster Recovery across Availability Domain using Dataguard.
487490

488-
![Future State Non-Production Deployment Diagram – Base Database Workload](images/oracle-database-migration-to-base-database-service-an-example-migration-1NodeDB_NoDRwithinRegion.png)
491+
<figure>
492+
<img src="images/oracle-database-migration-to-base-database-service-an-example-migration-1NodeDB_NoDRwithinRegion.png" title="Non-Production Deployment Diagram"/>
493+
<figcaption>Non-Production Deployment Diagram</figcaption>
494+
</figure>
489495

490496
For the non-production environment, a single Oracle database node will be deployed. Automatic Backup stored in the Oracle Cloud Infrastructure Object Storage will be enabled to ensure database recovery in case of failure.
491497

@@ -553,7 +559,10 @@ A Data Guard configuration consists of one production database and one or more s
553559
A Data Guard configuration contains one production database, also referred to as the primary database, that functions in the primary role. This is the database that is accessed by most of your applications. On the other hand, a standby database is a transactionally consistent copy of the primary database. Once created, Data Guard automatically maintains the standby database by transmitting redo data from the primary database and then applying the redo to the standby database.
554560
Like a primary database, a standby database can be either a single-instance Oracle database or an Oracle Real Application Clusters database.
555561

556-
![DataGuard Configuration](images/oracle-database-migration-to-base-database-service-an-example-migration-dataguard_config.jpg)
562+
<figure>
563+
<img src="images/oracle-database-migration-to-base-database-service-an-example-migration-dataguard_config.jpg" title="DataGuard Configuration"/>
564+
<figcaption>DataGuard Configuration</figcaption>
565+
</figure>
557566

558567
Below is a guideline for how the DataGuard works:
559568

0 commit comments

Comments
 (0)