Oracle Cloud Infrastructure Documentation

Exadata Database Service on Exascale Infrastructure

Use the information in this section to resolve common errors and provisioning issues for Exadata Database Service on Exascale Infrastructure in your Oracle Database@Google Cloud environments.

Troubleshooting

No currently known troubleshooting topics.

Known Issues
Known Issue Resolution
Database move operations and Grid Infrastructure update operations fail due to the inability to establish connectivity after multiple attempts. There are two steps to resolve this issue.
  1. Add the following ingress rule to the default security list attached to the VCN. Ingress Rule: Allows Patching Traffic from Within the Client Subnet
    • Stateless: No (all rules must be stateful)
    • Source Type: CIDR
    • Source CIDR: Client subnet's CIDR
    • IP Protocol: TCP
    • Source Port Range: All
    • Destination Port Range: 7085
    • Description: Add a optional description of the rule to assist in future management task. For example, "Allow access to Exadata Fleet Update private endpoint within the subnet."
  2. Add the following egress rule to the default security list attached to the VCN. Egress rule: Allows all TCP traffic inside the client subnet
    • Stateless: No (all rules must be stateful)
    • Destination Type: CIDR
    • Destination CIDR: 0.0.0.0/0
    • IP Protocol: TCP
    • Source Port Range: All
    • Destination Port Range: 22
    • Description: Add a optional description of the rule to assist in future management task. For example, "This security rule can be removed after the operation completes."