diff --git a/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx b/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx index 87ad47228b6..83738f2f7f1 100644 --- a/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx +++ b/product_docs/docs/migration_toolkit/55/06_building_toolkit.properties_file.mdx @@ -1,6 +1,6 @@ --- title: "Specifying connection properities" - +DeepToC: true --- @@ -30,11 +30,11 @@ Before executing Migration Toolkit commands, modify the `toolkit.properties` fil Unless specified in the command line, Migration Toolkit expects the source database to be Oracle and the target database to be EDB Postgres Advanced Server. For any other source or target database, specify the `-sourcedbtype` or `-targetdbtype` options as described in [Migrating from a non-Oracle source database](/migration_toolkit/latest/07_invoking_mtk/#migrating-schemas-from-a-non-oracle-source-database). -For specifying a target database on BigAnimal, see [Defining a BigAnimal URL](#defining-a-biganimal-url). +For specifying a target database on Cloud Service, see [Defining the URL and configuring the required parameters for Cloud Service](#url-and-parameters-for-cloud-service). -## Defining an Advanced Server URL +## URL and parameters for an Advanced Server Migration Toolkit helps with migration from the following platforms to Advanced Server: @@ -70,13 +70,15 @@ An Advanced Server URL contains the following information: - `` — The name of the source or target database. +Ensure these values are set in the `toolkit.properties` file: + - `{TARGET_DB_USER|SRC_DB_USER}` — Specifies a user with privileges to create each type of object migrated. If migrating data into a table, the specified user might also require insert, truncate, and references privileges for each target table. -- `{TARGET_DB_PASSWORD|SRC_DB_PASSWORD}` — Set to the password of the privileged Advanced Server user. Do not wrap the password in quotes. +- `{TARGET_DB_PASSWORD|SRC_DB_PASSWORD}` — Set to the password of the privileged Advanced Server user. Provide the password without any surrounding quotes. -## Defining a PostgreSQL URL +## URL and parameters for PostgreSQL Migration Toolkit helps with migration from the following platforms to PostgreSQL: @@ -111,15 +113,17 @@ The URL contains the following information: - `` — The name of the source or target database. +Ensure these values are set in the `toolkit.properties` file: + - `{SRC_DB_USER|TARGET_DB_USER}` — Specify a user with privileges to create each type of object migrated. If migrating data into a table, the specified user might also need insert, truncate, and references privileges for each target table. -- `{SRC_DB_PASSWORD|TARGET_DB_PASSWORD}` — Set to the password of the privileged PostgreSQL user. Do not wrap the password in quotes. +- `{SRC_DB_PASSWORD|TARGET_DB_PASSWORD}` — Set to the password of the privileged PostgreSQL user. Provide the password without any surrounding quotes. -## Defining a BigAnimal URL +## URL and parameters for Cloud Service -Migration Toolkit helps with migration from the following platforms to BigAnimal: +Migration Toolkit helps with migration from the following platforms to Cloud Service: - Oracle - Advanced Server @@ -133,7 +137,7 @@ Migration Toolkit reads connection specifications for the source and the target - The name of a privileged user - The password associated with the specified user -When migrating to BigAnimal, `TARGET_DB_URL` takes the form of a JDBC URL. For example: +When migrating to Cloud Service, `TARGET_DB_URL` takes the form of a JDBC URL. For example: ```text jdbc:://[:]/?sslmode= @@ -141,7 +145,7 @@ jdbc:://[:]/?sslmode= !!!Note -Many of the values you need for the target database URL are available from the BigAnimal portal. In BigAnimal, select your cluster and go to the **Connect** tab to find the values. +Many of the values you need for the target database URL are available from the Cloud Service portal. In Cloud Service, select your cluster and go to the **Connect** tab to find the values. !!! The URL contains the following information: @@ -150,19 +154,23 @@ The URL contains the following information: - `postgres_type` — The subprotocol is the Postgres type. Specify `edb` if you're using Advanced Server or `postgresql` if you're using PostgreSQL. -- `` — The host name of your cluster. You can copy it from the **Host** field on the **Connect** tab in the BigAnimal portal. +- `` — The host name of your cluster. You can copy it from the **Host** field on the **Connect** tab in the Cloud Service portal. + +- `` — The port number that the database listener is monitoring. You can copy it from the **Port** field on the **Connect** tab in the Cloud Service portal. + +- `` — The name of the target database. Set this to the name of the database in your cluster that you want to use as your migration target database. The name of the default database for your cluster is shown in the **Dbname** field on the **Connect** tab in the Cloud Service portal. Often a separate database is created for use as the migration target. -- `` — The port number that the database listener is monitoring. You can copy it from the **Port** field on the **Connect** tab in the BigAnimal portal. +Ensure these values are set in the `toolkit.properties` file: -- `` — The name of the target database. Set this to the name of the database in your cluster that you want to use as your migration target database. The name of the default database for your cluster is shown in the **Dbname** field on the **Connect** tab in the BigAnimal portal. Often a separate database is created for use as the migration target. +- `TARGET_DB_USER` — Specifies the name of a privileged database user. You can copy it from the **User** field on the **Connect** tab in the Cloud Service portal. -- `TARGET_DB_USER` — Specifies the name of a privileged database user. You can copy it from the **User** field on the **Connect** tab in the BigAnimal portal. +- `TARGET_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. -- `TARGET_DB_PASSWORD` — Contains the password of the specified user. Do not wrap the password in quotes. +Ensure this value is set in Cloud Service: -- `sslmode` — Either "require" or "verify-full". See [Recommended settings for SSL mode](/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/#recommended-settings-for-ssl-mode). Listed at the end of the **Service URI** value on the **Connect** tab in the BigAnimal portal. +- `sslmode` — Either "require" or "verify-full". See [Recommended settings for SSL mode](/edb-postgres-ai/cloud-service/using_cluster/connect_from_a_client/#recommended-settings-for-ssl-mode). Listed at the end of the **Service URI** value on the **Connect** tab in the Cloud Service portal. -## Defining an Oracle URL +## URL and parameters for Oracle Migration Toolkit helps with migration from an Oracle database to a PostgreSQL or Advanced Server database. When migrating from Oracle, you must specify connection specifications for the Oracle source database in the `toolkit.properties` file. The connection information must include: @@ -198,6 +206,8 @@ An Oracle URL contains the following information: - `` — The name of the Oracle service. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged Oracle user. The Oracle user needs read access to the source database objects you want to migrate. If you want to migrate users/roles and related profiles/privileges, grant the Oracle user SELECT privileges on the following Oracle catalog objects: - `DBA_ROLES` @@ -209,11 +219,11 @@ An Oracle URL contains the following information: - `DBA_SYS_PRIVS` -- `SRC_DB_PASSWORD` — Contains the password of the specified user. Do not wrap the password in quotes. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. -## Defining a SQL Server URL +## URL and parameters for an SQL Server Migration Toolkit helps with migration from an SQL Server database to a PostgreSQL or Advanced Server database. Migration Toolkit supports migration of the following object definitions: @@ -251,9 +261,11 @@ A SQL server URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged SQL Server user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. Do not wrap the password in quotes. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. ### JTDS URL @@ -279,11 +291,13 @@ A SQL server URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged SQL Server user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. Do not wrap the password in quotes. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. -## Defining a MySQL URL +## URL and parameters for MySQL Migration Toolkit helps with migration from a MySQL database to an Advanced Server or PostgreSQL database. When migrating from MySQL, you must specify connection specifications for the MySQL source database in the `toolkit.properties` file. The connection information must include: @@ -309,9 +323,11 @@ The URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged MySQL user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. Do not wrap the password in quotes. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. !!! Note @@ -333,7 +349,7 @@ In this case, the JDBC driver reports `TINYINT(1)` as `TINYINT` and is mapped to -## Defining a Sybase URL +## URL and parameters for Sybase Migration Toolkit helps with migration from a Sybase database to an Advanced Server database. When migrating from Sybase, you must specify connection specifications for the Sybase source database in the `toolkit.properties` file. The connection information must include: @@ -365,6 +381,8 @@ A Sybase URL contains the following information: - `` — The name of the source database. +Ensure these values are set in the `toolkit.properties` file: + - `SRC_DB_USER` — Specifies the name of a privileged Sybase user. -- `SRC_DB_PASSWORD` — Contains the password of the specified user. Do not wrap the password in quotes. +- `SRC_DB_PASSWORD` — Contains the password of the specified user. Provide the password without any surrounding quotes. \ No newline at end of file diff --git a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx index 29cd9cb5629..8a93686a46b 100644 --- a/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx +++ b/product_docs/docs/migration_toolkit/55/09_mtk_errors.mdx @@ -117,7 +117,7 @@ Check the connectivity credentials. The JDBC URL for the target database (EDB Postgres Advanced Server) specified in the `toolkit.properties` file contains invalid connection properties. -To resolve this error, edit the `toolkit.properties` file, specifying valid connection information for the target database in the `TARGET_DB_URL` property. For information about forming a JDBC URL for EDB Postgres Advanced Server, see [Defining an EDB Postgres Advanced Server URL](06_building_toolkit.properties_file/#defining-an-advanced-server-url). +To resolve this error, edit the `toolkit.properties` file, specifying valid connection information for the target database in the `TARGET_DB_URL` property. For information about forming a JDBC URL for EDB Postgres Advanced Server, see [Defining an EDB Postgres Advanced Server URL](06_building_toolkit.properties_file/#url-and-parameters-for-an-advanced-server).