Update oracle-database-network-plan.md

shigeooooooooooo · web-flow · commit 73b926577218 · 2024-12-18T11:42:03.000+09:00
network virtual alliance ---&gt; network virtual appliance

I suppose this is a typo.
If you really mean it as "alliance", then you can just abandon this PR..
diff --git a/articles/oracle/oracle-db/oracle-database-network-plan.md b/articles/oracle/oracle-db/oracle-database-network-plan.md
@@ -55,7 +55,7 @@ The following table describes required configurations of supported network featu
 |Dual stack (IPv4 and IPv6) virtual network|Only IPv4 is supported|
 
 >[!NOTE]
-> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual alliance or firewall destined to an Oracle Database@Azure instance from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Oracle Database@Azure instance. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective. 
+> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual appliance or firewall destined to an Oracle Database@Azure instance from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Oracle Database@Azure instance. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective. 
 >
 > For example, if your delegated subnet is `x.x.x.x/24`, you must configured your UDR to `x.x.x.x/24` (equal) or `x.x.x.x/32` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall. 
 

Original file line number	Diff line number	Diff line change
`@@ -55,7 +55,7 @@ The following table describes required configurations of supported network featu`
`55`	`55`	`\|Dual stack (IPv4 and IPv6) virtual network\|Only IPv4 is supported\|`
`56`	`56`
`57`	`57`	`>[!NOTE]`
`58`		`-> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual alliance or firewall destined to an Oracle Database@Azure instance from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Oracle Database@Azure instance. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective.`
	`58`	`+> If you want to configure a route table (UDR route) to control the routing of packets through a network virtual appliance or firewall destined to an Oracle Database@Azure instance from a source in the same VNet or a peered VNet, the UDR prefix must be more specific or equal to the delegated subnet size of the Oracle Database@Azure instance. If the UDR prefix is less specific than the delegated subnet size, it isn't be effective.`
`59`	`59`	`>`
`60`	`60`	> For example, if your delegated subnet is `x.x.x.x/24`, you must configured your UDR to `x.x.x.x/24` (equal) or `x.x.x.x/32` (more specific). If you configure the UDR route to be `x.x.x.x/16`, undefined behaviors such as asymmetric routing can cause a network drop at the firewall.
`61`	`61`