Skip to content

Commit e921dc8

Browse files
Merge pull request #272614 from b-ahibbard/oracle-418
Oracle 418
2 parents 7caa4a7 + 7ab07f4 commit e921dc8

File tree

3 files changed

+3
-5
lines changed

3 files changed

+3
-5
lines changed

articles/azure-netapp-files/application-volume-group-concept.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -107,13 +107,11 @@ Resulting volumes provide the same flexibility for resizing capacity and through
107107

108108
## Availability
109109

110-
Application volume group is currently available for [SAP HANA](application-volume-group-introduction.md).
111-
112-
<!-- and Oracle databases. -->
110+
Application volume group is currently available for [SAP HANA](application-volume-group-introduction.md) and [Oracle](application-volume-group-oracle-introduction.md) databases.
113111

114112
## Conclusion
115113

116-
In conclusion, the application volume group is a pivotal concept in modern data management, providing a structured approach to handling volumes within application environments. By leveraging application volume group, you can enhance performance, streamline administration, and ensure the resilience of your applications in dynamic and evolving scenarios.
114+
Application volume group is a pivotal concept in modern data management, providing a structured approach to handling volumes within application environments. By leveraging application volume group, you can enhance performance, streamline administration, and ensure the resilience of your applications in dynamic and evolving scenarios.
117115

118116
## Next steps
119117

articles/azure-netapp-files/application-volume-group-oracle-introduction.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,7 @@ A fully built deployment with eight data volumes and all optional volumes in a z
6666

6767
In resource-constrained zones, volumes might be deployed on shared storage endpoints due to the aforementioned anti-affinity and no-grouping algorithms. This diagram depicts an example volume layout in a resource-constrained zone:
6868

69-
:::image type="content" source="./media/application-volume-group-concept/resource-constrained-layout.png" alt-text="Diagram of constrained zone deployment." lightbox="./media/application-volume-group-concept/resource-constrained-layout.png":::
69+
:::image type="content" source="./media/application-volume-group-oracle-introduction/oracle-built-environment.png" alt-text="Diagram of Oracle deployment." lightbox="./media/application-volume-group-oracle-introduction/oracle-built-environment.png":::
7070

7171
In resource-constrained zones, the volumes are deployed on shared storage endpoints while maintaining the anti-affinity and no-grouping rules. The resulting layout shows the log and log-mirror volumes on private storage endpoints while the data volumes share storage-endpoints. The log and log-mirror volumes do not share storage-endpoints.
7272

182 KB
Loading

0 commit comments

Comments
 (0)