Merge pull request #5603 from EnterpriseDB/docs/mtk-55.8.0

EnterpriseDB · May 16, 2024 · 33c09eb · 33c09eb · github-actions · May 16, 2024
2 parents 1183fef + 3ede832
commit 33c09eb
Show file tree

Hide file tree

Showing 6 changed files with 235 additions and 28 deletions.
diff --git a/product_docs/docs/migration_toolkit/55/04_functionality_overview.mdx b/product_docs/docs/migration_toolkit/55/04_functionality_overview.mdx
@@ -29,6 +29,11 @@ Migration Toolkit also allows you to migrate database objects and data to an EDB
 -   Use the `-dropSchema` option to drop the existing schema and create a new schema prior to migration.
 -   On EDB Postgres Advanced Server, use the `-allDBLinks` option to migrate all Oracle database links.
 -   On EDB Postgres Advanced Server, use the `-copyViaDBLinkOra` option to enable the `dblink_ora` module.
+-   Use the `-connRetryCount <connection_attempts>` option to specify the number of retry attempts to perform if the target database connection is lost during data migration. 
+-   Use the `-connRetryInterval <seconds>` option to specify the seconds to wait before each target database reconnection attempt during a data migration.
+-   Use the `-abortConnOnFailure <true/false>` option to specify if to abort the migration when all target database reconnection attempts during a data migration fail.
+    The default is `true`, which aborts the session if the connection fails after the the specified `-connRetryCount` threshold.
+-   Use the `-pgIdleTxSessionTimeOut <seconds>` to override the value of the PostgreSQL or EDB Postgres Advanced Server `idle_in_transaction_session_timeout` configuration option in the MTK connection session.
 
 ## Object migration support