Membuat konfigurasi konektivitas pribadi untuk database sumber
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Halaman ini menjelaskan cara membuat konfigurasi konektivitas pribadi.
Konfigurasi konektivitas pribadi adalah konstruksi Database Migration Service yang membantu
Anda membuat koneksi peering antara jaringan layanan Database Migration Service
dan jaringan Virtual Private Cloud (VPC) project Anda. Anda membuat konfigurasi konektivitas pribadi untuk membuat koneksi pribadi ke database Oracle sumber.
Ini adalah jaringan yang sama dengan tempat database sumber Anda dihubungkan.
Untuk mengetahui informasi selengkapnya, lihat bagian persyaratan di
Konektivitas pribadi dengan peering VPC.
Jaringan VPC memiliki rentang IP yang tersedia dengan blok CIDR minimum /29. Database Migration Service menggunakan rentang IP ini untuk membuat subnet agar dapat berkomunikasi dengan database sumber.
Aktifkan Database Migration Service dan Compute Engine API.
Untuk mendapatkan izin yang diperlukan guna membuat konfigurasi
konektivitas pribadi, minta administrator untuk memberi Anda
peran IAM yang diperlukan di project Anda:
Untuk mengetahui informasi selengkapnya tentang cara memberikan peran, lihat
Mengelola akses dalam dokumentasi Identity and Access Management.
Peran yang telah ditetapkan ini berisi izin yang diperlukan untuk membuat
konfigurasi konektivitas pribadi di Database Migration Service. Untuk melihat izin
yang benar-benar diperlukan, luaskan
bagian Izin yang diperlukan:
Izin yang diperlukan
Izin berikut diperlukan untuk melakukan migrasi Oracle heterogen dengan Database Migration Service:
Di bagian Configure private connectivity, masukkan nama tampilan untuk konfigurasi dan pilih region.
Pastikan Anda menggunakan region yang sama dengan tempat jaringan Virtual Private Cloud project Anda berada. Region ini harus sama dengan region tempat Anda ingin membuat
tugas migrasi dan profil koneksi. Database Migration Service adalah
produk yang sepenuhnya bersifat regional, yang berarti semua entitas
yang terkait dengan migrasi Anda (profil koneksi sumber dan tujuan,
tugas migrasi, database tujuan, ruang kerja konversi) harus disimpan di
satu region.
Dari menu drop-down Authorized VPC network, pilih VPC yang Anda inginkan agar Database Migration Service memiliki akses konektivitas pribadi.
VPC ini harus berupa jaringan tempat Oracle sumber Anda
memiliki IP pribadi yang ditetapkan.
Di kolom Allocate an IP range, masukkan rentang IP dengan blok CIDR minimum /29. Contoh:
10.72.149.40/29.
Database Migration Service membuat subnet berdasarkan rentang IP tersebut di VPC yang Anda pilih. Sebaiknya konsultasikan dengan administrator jaringan Anda untuk mendapatkan rentang IP yang sesuai.
Untuk tujuan pengujian, Anda juga dapat mencoba membuat rentang IP dengan antarmuka akses layanan pribadi Virtual Private Cloud. Perhatikan bahwa alokasi otomatis ini tidak ditujukan untuk konfigurasi konektivitas pribadi Database Migration Service. Anda harus melepaskan rentang yang dialokasikan secara otomatis sebelum menggunakannya di Database Migration Service. Luaskan bagian berikut untuk mengetahui informasi selengkapnya.
Contoh: membuat rentang IP dengan akses layanan pribadi
Anda dapat membuat rentang IP yang tidak terisi di jaringan VPC saat membuat penyiapan akses layanan pribadi. Anda nantinya dapat
melepaskan rentang ini dalam konfigurasi VPC dan menggunakannya untuk
konfigurasi konektivitas pribadi Database Migration Service.
Untuk membuat rentang IP yang tidak terisi, ikuti langkah-langkah berikut:
Di konsol Google Cloud , buka halaman
VPC networks.
Dari daftar jaringan dalam project Anda, pilih jaringan tempat database Oracle sumber Anda memiliki IP pribadi yang ditetapkan.
Buka tab Private services access, lalu klik
Allocate IP range.
Di jendela Alokasikan rentang IP internal, masukkan hal berikut:
Nama tampilan di kolom Name.
Pilih opsi Otomatis dan masukkan 29 untuk awalan
panjang.
Hasil: Jaringan VPC Anda mengalokasikan rentang IP kosong untuk akses layanan pribadi di project Anda.
Periksa nilai Rentang IP internal dari rentang yang dialokasikan baru.
Catat untuk digunakan nanti di Database Migration Service.
Pilih rentang IP baru Anda dari daftar, lalu klik Release.
Rentang IP yang dihasilkan kini bebas digunakan di subnet lain.
Masukkan rentang yang Anda catat di kolom Alokasikan rentang IP saat Anda membuat konfigurasi konektivitas pribadi di Database Migration Service.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-18 UTC."],[[["\u003cp\u003eThis page provides instructions on creating a private connectivity configuration in Database Migration Service to establish a peering connection between the service network and your Virtual Private Cloud (VPC).\u003c/p\u003e\n"],["\u003cp\u003eA VPC network is required, without peering restrictions, where your source database's private IP is available, and it must have an available IP range with a minimum CIDR block of \u003ccode\u003e/29\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eSpecific IAM roles are required for both the user account performing the migration and the Database Migration Service account, including \u003ccode\u003edatamigration.admin\u003c/code\u003e and \u003ccode\u003ecompute.networkViewer\u003c/code\u003e for the user, and \u003ccode\u003ecompute.networkAdmin\u003c/code\u003e for the service account.\u003c/p\u003e\n"],["\u003cp\u003eCreating the configuration involves selecting an authorized VPC network, entering an IP range (with a minimum \u003ccode\u003e/29\u003c/code\u003e CIDR block), and ensuring the chosen region is consistent across migration entities.\u003c/p\u003e\n"],["\u003cp\u003eAn unoccupied IP range can be generated in your VPC using the private services access interface and then released for use in the Database Migration Service private connectivity configuration, by utilizing the "Allocate an internal IP range" feature.\u003c/p\u003e\n"]]],[],null,["# Create a private connectivity configuration for the source database\n\nThis page describes how to create a private connectivity configuration.\nPrivate connectivity configuration is Database Migration Service construct that helps\nyou create a peering connection between Database Migration Service service network\nand your project's Virtual Private Cloud (VPC) network. You create private connectivity\nconfigurations to establish private connections to source Oracle\ndatabases.\n\nFor more information about network connectivity in Database Migration Service, see\n[Network connectivity for heterogeneous Oracle migrations](/database-migration/docs/oracle-to-postgresql/networking-overview)\nand\n[Source networking methods overview](/database-migration/docs/oracle-to-postgresql/networking-methods-source).\n\nBefore you begin\n----------------\n\n1. Ensure you have a Virtual Private Cloud network that meets the following requirements:\n - The VPC network doesn't have any [peering restrictions](/vpc/docs/vpc-peering#restrictions).\n - It's the same network where your source database is peered. For more information, see the requirements section in [Private connectivity with VPC peering](/database-migration/docs/oracle-to-postgresql/networking-methods-source#private-connectivity-for-source).\n - The VPC network has an available IP range with a minimum CIDR block of `/29`. Database Migration Service uses this IP range to create a subnet so that it can communicate with the source database.\n2. Enable the Database Migration Service and Compute Engine APIs. [Enable the APIs](https://console.cloud.google.com/flows/enableapi?apiid=compute.googleapis.com,datamigration.googleapis.com)\n\n### Required roles\n\nTo get the permissions that you need to create a private connectivity\nconfiguration, ask your administrator to grant you the\nrequired IAM roles on your project:\n\n- [Database Migration Admin](/iam/docs/roles-permissions/datamigration#datamigration.admin) (`roles/datamigration.admin`)\n- [Compute Network Viewer](/iam/docs/roles-permissions/compute#compute.networkViewer) (`roles/compute.networkViewer`)\n\nFor more information about granting roles, see\n[Manage access](/iam/docs/granting-changing-revoking-access) in the Identity and Access Management documentation.\n\nThese predefined roles contain the permissions required to create a\nprivate connectivity configuration in Database Migration Service. To see the exact\npermissions that are required, expand the\n**Required permissions** section: \n\n#### Required permissions\n\nThe following permissions are required to perform heterogeneous Oracle\nmigrations with Database Migration Service:\n\n- `datamigration.* `\n- `compute.networks.list`\n\nYou might also be able to get these permissions with\n[custom roles](/iam/docs/creating-custom-roles) or other\n[predefined roles](/iam/docs/roles-permissions).\n\nCreate the configuration\n------------------------\n\nTo create a private connectivity configuration, follow these steps:\n\n1. In the Google Cloud console, go to the **Private connectivity configurations** page.\n\n [Go to Private connectivity configurations](https://console.cloud.google.com/dbmigration/private-connections)\n2. Click **Create configuration**.\n3. In the **Configure private connectivity** section, enter the display\n name for the configuration and select the region.\n\n Make sure you use the same region where your project Virtual Private Cloud\n network resides. It must be the same region where you intend to create\n the migration job and connection profiles. Database Migration Service is a\n fully-regional product, meaning all entities\n related to your migration (source and destination connection profiles,\n migration jobs, destination databases, conversion workspaces) must be saved in a\n single region.\n4. From the **Authorized VPC network** drop-down menu, select the VPC that you want Database Migration Service to have private connectivity access. This VPC needs to be the network where your source Oracle has a private IP assigned.\n5. In the **Allocate an IP range** field, enter an IP range with a\n minimum CIDR block of `/29`. For example:\n `10.72.149.40/29`.\n\n Database Migration Service creates a subnet based on that IP range in your\n selected VPC. We recommend that you consult your network administrator\n to acquire a suitable IP range.\n\n For testing purposes, you can also try to generate an IP range with\n Virtual Private Cloud private services access interface. Note that this automatic\n allocation isn't intended for Database Migration Service private connectivity\n configurations. You need to release the automatically allocated range\n before you use it in Database Migration Service. Expand the following section\n for more information. \n\n #### Example: generate an IP range with private services access\n\n You can generate an unoccupied IP range in your VPC network\n when you create a private services access setup. You can later\n release this range in the VPC configuration and use it for the\n Database Migration Service private connectivity configuration.\n\n To generate an unoccupied IP range, follow these steps:\n 1. In the Google Cloud console, go to the **VPC networks** page.\n\n [Go to VPC networks](https://console.cloud.google.com/networking/networks/list)\n 2. From the list of networks in your project, select the one where your source Oracle database has a private IP assigned.\n 3. Go to the **Private services access** tab and click **Allocate IP range**.\n 4. In the **Allocate an internal IP range** window, enter the following:\n 1. A display name in the **Name** field.\n 2. Select the **Automatic** option and enter `29` for the prefix\n 3. length.\n\n **Result**: Your VPC network allocates an empty IP range for\n private services access in your project.\n 5. Check the **Internal IP range** value of the new allocated range. Note it down for later use in Database Migration Service.\n 6. Select your new IP range from the list, and click **Release**.\n 7. The generated IP range is now free for use in another subnet. Enter the range you noted down in the **Allocate an IP range** field when you create the private connectivity configuration in Database Migration Service.\n6. Click **Create**.\n\nThe private connectivity configuration is now ready for use with a\n[source connection profile](/database-migration/docs/oracle-to-postgresql/create-source-connection-profile).\n\nWhat's next\n-----------\n\n- Learn about destination database connectivity. See\n [Destination database connectivity overview](/database-migration/docs/oracle-to-postgresql/networking-methods-destination).\n\n- To get a complete, step-by-step migration walkthrough, see\n [Oracle to Cloud SQL for PostgreSQL migration guide](/database-migration/docs/oracle-to-postgresql/guide)."]]
