ODB Network provides a secure and private connectivity to your Oracle Database resources which enables you to control how these resources can connect and communicate with each other. With an ODB Network, you can map the Virtual Private Cloud (VPC) that resides in your Google Cloud console to the Virtual Cloud Network (VCN) in the OCI console.

With an ODB Network, support for Shared VPC is provided. Shared VPC allows organizations to link resources from multiple projects to a single Virtual Private Cloud (VPC) network which enables secure and efficient communication through internal IP addresses across projects within the same organization.

These are steps to create an ODB network from Google Cloud console.

1. From the Google Cloud console, select the application.
2. From the left navigation menu, select ODB networks and then select Create to start the creation flow.
3. From the dropdown list, select your Associated network. The Associated network field populates the list of available Shared VPC(s) and VPC(s).
4. Select the Region from the drop-down list of available regions. The Region field contains the list of availability zone (AZ) where your ODB network will exist.
   Note
   
   The Region list is limited by your subscription. Your Region selection cant be changed after the creation of an ODB network.
5. Enter an unique Name for your ODB network name.
   Note
   
   ODB network name can be up to 63 characters. It can include the following characters: a-z, 0-9, and hyphen (-). It must start with a lowercase letter and must end with a lowercase letter or number.
6. Review the information that you entered, and then select Create button.
7. Once you created your ODB network successfully, you must create a subnet.

1. Navigate to ODB network and select your ODB network from the list.
2. From the Subnets section, select the Create button to start the creation process.
3. Enter an unique Name for your Subnet name.
   Note
   
   Subnet name can be up to 63 characters. It can include the following characters: a-z, 0-9, and hyphen (-). It must start with a lowercase letter and must end with a lowercase letter or number.
4. Enter your subnet range into the Subnet range.
   Note
   
   You must use CIDR notation while providing your subnet range. For more information, see CIDR notation.
5. Based on your system requirement, select your Subnet type. The Subnet type provides the Client and Backup options.
   Note
   
   The Client subnets are the default. For Exadata VM Cluster(s), both Client and Backup subnets are required. For Autonomous Database, you must select the Client subnet.
6. Review your information, and then select the Create button.

The following policies allow you to have stricter compartment access controls in OCI. With these policies, the database administrators will not be able to create databases or make changes within the networking compartment. Similarly, these policies restrict networking administrators from accessing and modifying resources within the database compartment. These policies enhance the security and reduce the risk of unauthorized changes across compartments.

Policies for the odbg-network-administrators role include:

allow group 'Default'/'odbg-network-administrators' to manage virtual-network-family in compartment MulticloudLink_ODBG_Compartment:ProjectNumberCompartment
allow group 'Default'/'odbg-network-administrators' to inspect compartments in tenancy