ODB Network
Use the information in this section to resolve common errors of ODB Network.
Restricted CIDR Blocks
ODB networks require specific CIDR blocks for client and backup subnets. You must confirm that the CIDR blocks you select, do not overlap with reserved or prohibited IP ranges. You must avoid using the following reserved ranges. For more information, see Restrictions for IP Addresses.
You must confirm that there is no overlap between your selected VPC subnets and the ranges used for connectivity to the ODB network. For more information, see IPv4 CIDR block association restrictions.
Overlapping VPC CIDRs
You must verify that the CIDR range assigned to the ODB network must not overlap with any CIDR ranges of your existing VPCs.
Common Connectivity Issues between VPC and ODB Network
If you can not connect from your VPC to the ODB network or VM cluster(s), check for the following common issues.
- VPC Configuration
From the AWS console, select VPC, and then expand the Virtual private cloud section. Select Your VPCs to see a list of VPC. You must confirm that your peered VPC ID matches with the one listed on the ODB network details page.
- Route Table
From the AWS console, navigate to Route tables, and then select the route table that is attached to the subnet and the application is running. You must confirm that there is a route which targets the client subnet CIDR of the ODB network. This route should direct traffic to the correct ODB network ARN. If it does not, you must create it manually.
- Peered CIDRs
From the Oracle Database@AWS dashboard, navigate to ODB networks, and then select the ODB network you are using. From ODB network details page, navigate to the Peered CIDRs section, and confirm that all related VPC CIDR blocks are included. You must add any missing CIDRs to maintain the connectivity.
- Missing Transit Gateway
If you add a CIDR to the ODB network’s peering list but have not attached a transit gateway to your VPC, the network creation or update will fail. You must verify that a transit gateway is configured, regardless of the CIDR range.
Resolve Hostnames and Scannames Issues for VM Clusters
If the hostnames or scannames of the VM clusters can’t be resolved from your VPC, you can set up DNS forwarding by following the steps:
- Outbound Endpoint:
You can create an outbound endpoint to forward DNS queries to the ODB network. For more information, see https://docs.aws.amazon.com/odb/latest/UserGuide/configuring.html#configuring.endpoint
- Resolver Rules:
You can configure a resolver rule to direct specific domain queries to the ODB network’s DNS services. For more information, see Configuring a resolver rule in Oracle Database@AWS.
Resolve VM Cluster Creation Failures
The domain name must not contain more than four labels. If it does, restrict the domain name to four labels or fewer.
ODB Network is Stuck in 'Updating' State After Adding Peered CIDR
The ODB Network is stuck in Updating status after adding a peered CIDR range to the ODB Network's Peered CIDRs field.
Solution
- Create a transit gateway attachment in the same AZ as the ODB network.
- Remove the CIDR range from ODB Network's Peered CIDRs field. Click Continue. Click the Modify button.
- Add the CIDR back to the ODB Network's Peered CIDRs field again. Click the Continue button and then select the Modify button.
Cause
The transit gateway attachment was in different Availability Zone (AZ) as the ODB network. Both must be in same AZ as explained in Configuring Amazon VPC Transit Gateways for Oracle Database@AWS.