From 15316600bddc83686473f3a89b2c2f3878cc36ba Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 15 Sep 2022 15:47:24 -0400 Subject: [PATCH 01/50] added customcolmap content --- .../36_creating_subscription_cli.mdx | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index a04039ced50..27d58d62438 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -15,6 +15,7 @@ title: "Creating a subscription (createsub)" -pubsvrfile pubsvrfile -pubname pubname [ -filterrule filterid_1[,filterid_2 ] ...] +[-customcolmap | -customcolmapfile ] ``` The `createsub` command adds a subscription subordinate to the subscription database definition with the subscription database ID given by parameter `subdbid.` @@ -46,6 +47,37 @@ The file containing the publication server login information of the publication Comma-separated list of filter IDs identifying the filter rules from the set of available table filters to enable on the corresponding tables in the new subscription. Use the `printpubfilterslist` command to obtain the filter IDs for the available filter rules in the publication (see [Printing a list of filters in a Publication](17_print_publications_filters_list/#print_publications_filters_list)). Don't use white space between the comma and filter IDs. +`customcolmap` + +Directly provides the column mappings between different but compatible columns in the source and target database. Table and schema qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. + +To provide multiple mappings, use a semicolon to separate the column mappings. + +Provide mappings in the following format, where `dataType` represents the data type of the column in the target database. + + ```shell + SchemaName\.tableName\.columName=dataType + ``` + +The following is an example of custom column mapping: + + ```shell + company\.emp\.emp_id=integer + ``` + + The `\` characters act as an escape string, while `.` is a reserved character in regular expressions. Use `\.` to represent the `.` character. + +The following is example of regular expression for a column mapping entery: + + ```shell + .*id=integer + ``` + + Where you map any column whose name ends in `id` to type `integer`. + + + + ## Examples This example creates a subscription named `dept_emp_sub` in the EDB Postgres Advanced Server subscription database identified by subscription database ID 2. The subscription is associated with a publication named `dept_emp`. From 4e27ff1b6d43450d33b7c4491099bbc7aa97f2f4 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Mon, 19 Sep 2022 09:41:28 -0400 Subject: [PATCH 02/50] added customcolmapfile content --- .../36_creating_subscription_cli.mdx | 25 +++++++++++++++---- 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index 27d58d62438..7fd92cc3472 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -49,11 +49,11 @@ Comma-separated list of filter IDs identifying the filter rules from the set of `customcolmap` -Directly provides the column mappings between different but compatible columns in the source and target database. Table and schema qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. +Enter the column mappings between different but compatible columns in the source and target database. Table and schema qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. -To provide multiple mappings, use a semicolon to separate the column mappings. +To enter multiple mappings, use a semicolon to separate the column mappings. -Provide mappings in the following format, where `dataType` represents the data type of the column in the target database. +Enter mappings in the following format, where `dataType` represents the data type of the column in the target database. ```shell SchemaName\.tableName\.columName=dataType @@ -67,7 +67,7 @@ The following is an example of custom column mapping: The `\` characters act as an escape string, while `.` is a reserved character in regular expressions. Use `\.` to represent the `.` character. -The following is example of regular expression for a column mapping entery: +The following is an example of regular expression for a column mapping entery: ```shell .*id=integer @@ -75,8 +75,23 @@ The following is example of regular expression for a column mapping entery: Where you map any column whose name ends in `id` to type `integer`. - +`customcolmapfile` +Enter the path of the file containing the column mappings. Multiple custom type mappings can also be provided in the file. You can use either the fully qualify column name or regression expression. Enter each mapping on a new line. + +For example, create the file `/usr/edb/xdb/replicator/bin/columnMapping.txt` with the following contents: + +```shell +uuidasprimarykey\.id=char +mapjson1\..*=clob +.*no=numeric +``` + +And enter the complete path for the file in the `customcolmapfile` option: + +```shell +-customcolmapfile /usr/edb/xdb/replicator/bin/columnMapping.txt +``` ## Examples From 2b7ac7100a003b74a3f8c8cab3eee6b40b36740f Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 20 Sep 2022 14:11:47 -0400 Subject: [PATCH 03/50] added column mapping note to addtablesintopub --- .../03_xdb_cli_commands/18_adding_tables_to_publication.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx index 8a0890eb2e0..354ed8387ce 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx @@ -6,6 +6,10 @@ title: "Adding tables to a publication (addtablesintopub)" The `addtablesintopub` command adds tables or views into an existing publication. +!!! Note +Column mappings are applied when you create subscriptions. If you add a table which qualifies for column mapping with regular expression to the related publication, then Replication Server applies the column mapping for the newly added table. For more information on column mappings, see [Creating a subscription](/36_creating_subscription_cli). +!!! + ## Synopsis ```shell From f99ba96a65391640718e9eddb709731f57f5ec42 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 20 Sep 2022 14:19:57 -0400 Subject: [PATCH 04/50] changed note location --- .../18_adding_tables_to_publication.mdx | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx index 354ed8387ce..f2f3c9c0708 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx @@ -6,10 +6,6 @@ title: "Adding tables to a publication (addtablesintopub)" The `addtablesintopub` command adds tables or views into an existing publication. -!!! Note -Column mappings are applied when you create subscriptions. If you add a table which qualifies for column mapping with regular expression to the related publication, then Replication Server applies the column mapping for the newly added table. For more information on column mappings, see [Creating a subscription](/36_creating_subscription_cli). -!!! - ## Synopsis ```shell @@ -49,6 +45,11 @@ The `views` parameter applies only for a snapshot-only publication. It's ignored !!! Note The schema names, table names, and view names that you supply as values for the tables and views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. + +!!! Note + Column mappings are applied when you create subscriptions. If you add a table which qualifies for column mapping with regular expression to the related publication, then Replication Server applies the column mapping for the newly added table. For more information on column mappings, see [Creating a subscription](/36_creating_subscription_cli). +!!! + ## Parameters `pubname` From f4f0fe16a072e94a117869e8a2d48593f5f60efd Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 21 Sep 2022 16:13:53 -0400 Subject: [PATCH 05/50] added printuserolmapping topic --- .../10_printing_pdn_node_db_id.mdx | 2 +- .../print_column_mappings_publication.mdx | 72 +++++++++++++++++++ 2 files changed, 73 insertions(+), 1 deletion(-) create mode 100644 product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/print_column_mappings_publication.mdx diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx index f48d6d77bc6..a3d53bacc22 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/10_printing_pdn_node_db_id.mdx @@ -6,7 +6,7 @@ title: "Printing the primary definition node database ID (printpdndbid)" **For MMR only:** The `printmdndbid` command prints the publication database ID of the primary definition node. -##Synopsis +## Synopsis `-printmdnbid -repsvrfile pubsvrfile` diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/print_column_mappings_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/print_column_mappings_publication.mdx new file mode 100644 index 00000000000..ffd4bca9661 --- /dev/null +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/print_column_mappings_publication.mdx @@ -0,0 +1,72 @@ +--- +title: Printing the column mappings added to a publication (printusercolmapping) +--- + +**For SMR only:** The `printusercolmapping` command prints column data type mapping between the publication and subsciprtion database. + +## Synopsis + +```shell +-printusercolmapping -repsvrfile [-subname ] [-details] +``` + +## Parameters + +`pubname` + +The name of the publication whose column mappings are displaying. + +`pubsvrfile` + +The file containing the publication server login information. + +`subname` + +The name of the subscription whose column mappings are displaying. Providing the name allows for the column mappings to be filtered according to the subscription name. + +`details` + +Provides additional details about implicit column mappings and internal mapping representation of the column mapping. Implicit column mappings are'nt provided by the user. They are added by default depending on source and target database and their versions. For example, JSON is'nt supported on Oracle database versions 21 and earlier. Memory mapping is referred to as internal mapping in Replication Server. + +## Examples + +The following is an example where `-details` isn't included: + +```shell +$ java -jar edb-repcli.jar -printusercolmapping emp_pub -repsvrfile ~/pubsvrfile.prop + +Printing user column mapping details... + +Publication name:Subscription name:User expressions +emp_pub:emp_sub:uuidasprimarykey.id=char;public.mapjson.details=varchar2(4000);.*no=numeric;mapjson1..*=clob +``` + +The following is an example where `-details` is included: + +```shell +java -jar edb-repcli.jar -printusercolmapping emp_pub -repsvrfile ~/pubsvrfile.prop -details + +Printing user column mapping details... + +Publication name:Subscription name:User expressions +emp_pub:emp_sub:uuidasprimarykey.id=char;public.mapjson.details=varchar2(4000);.*no=numeric;mapjson1..*=clob + +Printing implicit column mapping details (Not provided by user)... + +Publication name:Subscription name:Database incompatible datatype-->Database compatible datatype +emp_pub:emp_sub1:json-->varchar +Note: Please provide custom column mapping with -customcolmap argument to override implicit mapping. + +Printing internal column mapping representation... + +Publication name:Subscription name:Table name:Column name:Source datatype-->Target datatype +emp_pub:emp_sub:public.test123:deptbuildno:integer-->number +emp_pub:emp_sub:public.test123:deptno:numeric-->number +emp_pub:emp_sub1:public.mapjson1:details:json-->varchar +emp_pub:emp_sub1:public.mapjson:details:json-->varchar + +``` + +!!! Note +User provided column data type mappings override implicit column data type mappings when they are present in the same column. +!!! From 1a121eacbc0c98bf5192c29d45047aa4835bb10b Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 22 Sep 2022 11:49:20 -0400 Subject: [PATCH 06/50] added column mappings note --- .../03_xdb_cli_commands/36_creating_subscription_cli.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index 7fd92cc3472..2dd4af91985 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -51,6 +51,14 @@ Comma-separated list of filter IDs identifying the filter rules from the set of Enter the column mappings between different but compatible columns in the source and target database. Table and schema qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. +!!! Note + Column mapping can be added only with the Replication Server CLI; this feature isn't supported by Replication Console. Column mappings are supported only for single-master replication clusters. + + Column data type mapping supports synchronization between two databases having different but compatible column data types. For example, the data types of a column may be different but data can be populated without any loss. Ensure that there is no possibility of data loss while providing the column data type mapping. This is very important when adding column mapping for columns that act as primary or unique keys as data or precision loss may create inconsistent data across the source and target database. + + Column mapping is currently not supported for large object type columns. +!!! + To enter multiple mappings, use a semicolon to separate the column mappings. Enter mappings in the following format, where `dataType` represents the data type of the column in the target database. From 1335e1f442225c5ff9d6ef2c366ef5b816b45a42 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 22 Sep 2022 12:19:03 -0400 Subject: [PATCH 07/50] ordered printusercolmapping topic in nav --- ..._publication.mdx => 37a_print_column_mappings_publication.mdx} | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/{print_column_mappings_publication.mdx => 37a_print_column_mappings_publication.mdx} (100%) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/print_column_mappings_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/37a_print_column_mappings_publication.mdx similarity index 100% rename from product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/print_column_mappings_publication.mdx rename to product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/37a_print_column_mappings_publication.mdx From feed48a6130007846c5a87775ac3e4f75929aab7 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 22 Sep 2022 15:22:41 -0400 Subject: [PATCH 08/50] removed SQL server 2012 --- .../7/01_introduction/03_certified_supported_versions.mdx | 1 - .../01_prerequisites/04_preparing_pub_database.mdx | 2 +- .../03_resolving_problems/04_troubleshooting_areas.mdx | 4 ++-- 3 files changed, 3 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx b/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx index 4fbda9145e7..2f9708ebbf2 100644 --- a/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx +++ b/product_docs/docs/eprs/7/01_introduction/03_certified_supported_versions.mdx @@ -11,7 +11,6 @@ You can use the following database product versions with Replication Server: - Oracle 12c version 12.1.0.2.0 is explicitly certified. Newer minor versions in the 12.1 line are supported as well. - Oracle 18c version 18.1.0.2.0 is explicitly certified. Newer minor versions in the 18.1 line are supported as well. - Oracle 19c version 19.1.0.2.0 is explicitly certified. Newer minor versions in the 19.1 line are supported as well. -- SQL Server 2012 version 11.0.6020.0 is explicitly certified. Newer minor versions in the 11.0 line are supported as well. - SQL Server 2014 version 12.0.5000.0 is explicitly certified. Newer minor versions in the 12.0 line are supported as well. As of Replication Server 7.1.0: diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx index 222bb3b5d26..72c497b6529 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx @@ -316,7 +316,7 @@ GRANT INSERT ON _edb_replicator_pub.rrep_tx_seq TO newuser; GO ``` -**For SQL Server 2012, 2014:** +**For SQL Server 2014:** ```sql GRANT UPDATE ON _edb_replicator_pub.rrep_tx_seq TO newuser; diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx index c92bb22d577..94b8d50a5a3 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx @@ -188,7 +188,7 @@ Changed database context to 'edb'. 7> GO ``` -**For SQL Server 2012, 2014 only:** Drop the following control schema objects when the publication database is SQL Server 2012 or 2014: +**For SQL Server 2014 only:** Drop the following control schema objects when the publication database is SQL Server 2014: ```sql 1> USE edb; @@ -211,7 +211,7 @@ Drop the `_edb_replicator_pub` control schema: The control schema objects under the`_edb_replicator_sub` schema as well as the schema itself are dropped as shown by the following. !!! Note - **(For SQL Server 2012, 2014):** When the publication database is SQL Server 2012 or 2014, the first table in the following list, `rrep_common_seq`, does not exist. Therefore don't issue the first `DROP TABLE` + **(For SQL Server 2014):** When the publication database is SQL Server 2014, the first table in the following list, `rrep_common_seq`, does not exist. Therefore don't issue the first `DROP TABLE` `_edb_replicator_sub.rrep_common_seq` command. From 7f345922583e877ef200a70d8cf542e04a081865 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Fri, 23 Sep 2022 10:32:31 -0400 Subject: [PATCH 09/50] added debian 11 install topic --- .../eprs/7/03_installation/03_installing_rpm_package/index.mdx | 1 + .../03_installing_rpm_package/x86_amd64/index.mdx | 1 + 2 files changed, 2 insertions(+) diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx index 8f54131c74e..b200c508019 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx @@ -23,6 +23,7 @@ For platform-specific install instructions, see: - [SLES 12](x86_amd64/eprs_sles12_x86) - [Ubuntu 20.04](x86_amd64/eprs_ubuntu20_x86) - [Ubuntu 18.04](x86_amd64/eprs_ubuntu18_x86) + - [Debian 11](x86_amd64/eprs_deb11_x86) - [Debian 10](x86_amd64/eprs_deb10_x86) - Linux on IBM Power (ppc64le): diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx index 9554c4b3ec4..bf2b86985c9 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/index.mdx @@ -26,4 +26,5 @@ For operating system-specific install instructions, see: - [SLES 12](eprs_sles12_x86) - [Ubuntu 20.04](eprs_ubuntu20_x86) - [Ubuntu 18.04](eprs_ubuntu18_x86) + - [Debian 11](eprs_deb11_x86) - [Debian 10](eprs_deb10_x86) From 2339913e573cbf6842f934d9a8eb01c2595e0a89 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 19 Oct 2022 06:17:57 -0400 Subject: [PATCH 10/50] EPRS: JDBC driver --- .../01_installing_with_stackbuilder.mdx | 42 ++++++++++--------- .../03_installing_rpm_package/index.mdx | 1 + .../docs/eprs/7/03_installation/index.mdx | 6 +++ .../installing_jdbc_driver.mdx | 21 ++++++++++ 4 files changed, 50 insertions(+), 20 deletions(-) create mode 100644 product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx diff --git a/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx b/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx index 068f446fe80..dca03433f96 100644 --- a/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx +++ b/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx @@ -22,19 +22,21 @@ Follow the directions for your host operating system to install Java runtime. !!! Note After installation of Replication Server has completed, the path to your Java runtime program is stored in the Replication Server Startup Configuration file used by Replication Server. Verify that the path to your Java runtime program set in the Replication Server Startup Configuration file is correct. See [Installation details](03_installing_rpm_package/installation_details/) for the location of this file. -**Step 2:** From the host’s application menu, open the Postgres menu and choose `Stack Builder` or `StackBuilder Plus`. +**Step 2:** Install a JDBC driver. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for more information. + +**Step 3:** From the host’s application menu, open the Postgres menu and choose `Stack Builder` or `StackBuilder Plus`. ![Postgres application menu](../images/image26.png) **Figure 3-1: Postgres application menu** -**Step 3 (For Linux only):** Depending upon your Linux host, a dialog box or a prompt appears requesting the root account’s password. Enter the root password and click the `OK` button. +**Step 4 (For Linux only):** Depending upon your Linux host, a dialog box or a prompt appears requesting the root account’s password. Enter the root password and click the `OK` button. ![Enter root account password](../images/image27.png) **Figure 3-2: Enter root account password** -**Step 4:** The StackBuilder Plus welcome screen appears. Select your `Postgres` installation from the drop-down list and click the `Next` button. +**Step 5:** The StackBuilder Plus welcome screen appears. Select your `Postgres` installation from the drop-down list and click the `Next` button. ![StackBuilder Plus welcome screen](../images/image28.png) @@ -49,7 +51,7 @@ Follow the directions for your host operating system to install Java runtime. **Figure 3-4: StackBuilder Plus applications** -**Step 5 (For PostgreSQL):** Expand the Registration-Required and Trial Products node, and then expand the EnterpriseDB Tools node. Check the box for `Replication Server` under the `EnterpriseDB Tools` list and click the `Next` button. +**Step 6 (For PostgreSQL):** Expand the Registration-Required and Trial Products node, and then expand the EnterpriseDB Tools node. Check the box for `Replication Server` under the `EnterpriseDB Tools` list and click the `Next` button. ![Stack Builder applications](../images/image30.png) @@ -59,7 +61,7 @@ Follow the directions for your host operating system to install Java runtime. **Figure 3-6: EnterpriseDB Tools for PostgreSQL** -**Step 6 (For Advanced Server only):** In the `Account Registration` screen, either enter your email address and password for your EnterpriseDB user account if you have one, or click the link in which case you will be directed to the registration page of the EnterpriseDB website where you can create an account. Click the `Next` button. +**Step 7 (For Advanced Server only):** In the `Account Registration` screen, either enter your email address and password for your EnterpriseDB user account if you have one, or click the link in which case you will be directed to the registration page of the EnterpriseDB website where you can create an account. Click the `Next` button. !!! Note (For PostgreSQL only): Proceed to Step 7. If you are using PostgreSQL, account registration occurs later in the process. @@ -68,7 +70,7 @@ Follow the directions for your host operating system to install Java runtime. **Figure 3-7: EnterpriseDB account registration** -**Step 7:** Verify that Replication Server appears in the list of selected packages. Click the `Next` button. +**Step 8:** Verify that Replication Server appears in the list of selected packages. Click the `Next` button. ![Selected packages](../images/image33.png) @@ -80,7 +82,7 @@ An information box appears showing the download progress of the Replication Serv **Figure 3-9: Downloading progress** -**Step 8:** When downloading of the Replication Server package completes, the following screen appears that starts the installation of Replication Server. Click the `Next` button. +**Step 9:** When downloading of the Replication Server package completes, the following screen appears that starts the installation of Replication Server. Click the `Next` button. !!! Note You can check the Skip Installation box if you wish to install Replication Server some other time. @@ -89,38 +91,38 @@ An information box appears showing the download progress of the Replication Serv **Figure 3-10: Start installation** -**Step 9:** Select the installation language and click the `OK` button. +**Step 10:** Select the installation language and click the `OK` button. ![Installation language](../images/image36.png) **Figure 3-11: Installation language** -**Step 10:** In the Setup Replication Server screen, click the `Next` button. +**Step 11:** In the Setup Replication Server screen, click the `Next` button. ![Installation language](../images/image37.png) **Figure 3-12: Setup Replication Server** -**Step 11:** Read the license agreement. If you accept the agreement, select the accept radio button and click the `Next` button. +**Step 12:** Read the license agreement. If you accept the agreement, select the accept radio button and click the `Next` button. ![Installation language](../images/image38.png) **Figure 3-13: License agreement** -**Step 12:** Browse to a directory where you want the Replication Server components installed, or allow it to install the components in the default location shown. Click the `Next` button. +**Step 13:** Browse to a directory where you want the Replication Server components installed, or allow it to install the components in the default location shown. Click the `Next` button. ![Installation directory](../images/image39.png) **Figure 3-14: Installation directory** -**Step 13:** If you do not want a particular Replication Server component installed on this particular host, uncheck the box `Next` to the component name. Click the `Next` button. +**Step 14:** If you do not want a particular Replication Server component installed on this particular host, uncheck the box `Next` to the component name. Click the `Next` button. ![Select components](../images/image40.png) **Figure 3-15: Select components** -**Step 14:** In the Account Registration screen select the radio button that applies to you. Click the `Next` button. +**Step 15:** In the Account Registration screen select the radio button that applies to you. Click the `Next` button. ![Account registration](../images/image41.png) @@ -134,7 +136,7 @@ If you already have an EnterpriseDB user account, enter the email address and pa **Figure 3-17: My EnterpriseDB account** -**Step 15:** Enter information for the Replication Server administrator. +**Step 16:** Enter information for the Replication Server administrator. !!! Note From this point on, it is suggested that you record the values you enter on these screens as they will be needed during the publication and subscription server registration process. @@ -150,25 +152,25 @@ Enter values for the following fields: The admin user and the admin password (in encrypted form) are saved to the EPRS Replication Configuration file named `/etc/edb-repl.conf (XDB_HOME\etc\edb-repl.conf` on Windows hosts). Click the `Next` button. -**Step 16 (Only if publication server is a selected component):** Enter an available port on which the publication server will run. Default port number is 9051. Click the `Next` button. +**Step 17 (Only if publication server is a selected component):** Enter an available port on which the publication server will run. Default port number is 9051. Click the `Next` button. ![Replication Server admin user information](../images/image44.png) **Figure 3-19: Publication server details** -**Step 17 (Only if subscription server is a selected component):** Enter an available port on which the subscription server will run. Default port number is 9052. Click the `Next` button. +**Step 18 (Only if subscription server is a selected component):** Enter an available port on which the subscription server will run. Default port number is 9052. Click the `Next` button. ![Subscription server details](../images/image45.png) **Figure 3-20: Subscription server details** -**Step 18:** For the operating system account under which the publication server or subscription server is to run, enter `postgres` (`enterprisedb` if you are using Advanced Server installed in Oracle compatible configuration mode). +**Step 19:** For the operating system account under which the publication server or subscription server is to run, enter `postgres` (`enterprisedb` if you are using Advanced Server installed in Oracle compatible configuration mode). ![Publication/subscription server operating system account](../images/image46.png) **Figure 3-21: Publication/subscription server operating system account** -**Step 19:** On the Ready to Install screen, click the `Next` button. +**Step 20:** On the Ready to Install screen, click the `Next` button. ![Ready to install](../images/image47.png) @@ -180,13 +182,13 @@ An information box appears showing the installation progress of the Replication **Figure 3-23: Installation progress** -**Step 20:** When installation has completed the following screen appears. Click the Finish button. +**Step 21:** When installation has completed the following screen appears. Click the Finish button. ![Replication Server installation completion](../images/image49.png) **Figure 3-24: Replication Server installation completion** -**Step 21:** On the `StackBuilder Plus Installation Complete` screen, click the `Finish` button. +**Step 22:** On the `StackBuilder Plus Installation Complete` screen, click the `Finish` button. ![StackBuilder Plus installation complete](../images/image50.png) diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx index 8f54131c74e..94d8922d1c3 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/index.mdx @@ -6,6 +6,7 @@ redirects: navigation: - x86_amd64 - ibm_power_ppc64le +- installation_details --- diff --git a/product_docs/docs/eprs/7/03_installation/index.mdx b/product_docs/docs/eprs/7/03_installation/index.mdx index 5cb915e66f6..04ede782df3 100644 --- a/product_docs/docs/eprs/7/03_installation/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/index.mdx @@ -1,5 +1,11 @@ --- title: "Installing" +navigation: +- 01_installing_with_stackbuilder +- 03_installing_rpm_package +- installing_jdbc_driver +- 03a_updating_linux_installation +- 06_uninstalling_xdb_replication_server --- diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx new file mode 100644 index 00000000000..74af5b1587b --- /dev/null +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -0,0 +1,21 @@ +--- +title: "Installing a JDBC driver" +--- + +Which JDBC driver you use depends on the what database you are using: +using migrating to or from EDB Postgres Advanced Server, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). + +- If you're using PostgreSQL, use the PostgreSQL JDBC driver. To download the latest supported driver, see the [JDBC drivers section](https://jdbc.postgresql.org/download/) on the PostgreSQL Downloads page. + +- If you're using Oracle, MySQL, Microsoft SQL Server or Sybase, use the freely available source-specific JDBC driver. + - [Oracle JDBC](https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html) + - [MySQL JDBC](https://dev.mysql.com/downloads/connector/j/) + - [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) + - [Sybase ASE (jTDS) JDBC](https://sourceforge.net/projects/jtds/files/) + + !!! Note + The open source jTDS driver also supports older versions of Microsoft SQL Server (version 2012 and earlier) and may be used with Replication Server. The Microsoft provided JDBC driver for SQL Server is recommended for the newer versions of SQL Server supported by Migration Toolkit. + + + + From 45331ae9d2b8b1afa6440a48601628abf624d014 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 19 Oct 2022 06:23:38 -0400 Subject: [PATCH 11/50] added jdbc info to initial config section of install topics --- .../templates/products/replication-server/base.njk | 6 +++++- .../ibm_power_ppc64le/eprs_rhel8_ppcle.mdx | 4 ++++ .../ibm_power_ppc64le/eprs_sles12_ppcle.mdx | 4 ++++ .../ibm_power_ppc64le/eprs_sles15_ppcle.mdx | 4 ++++ .../x86_amd64/eprs_centos7_x86.mdx | 6 +++++- .../03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx | 4 ++++ .../03_installing_rpm_package/x86_amd64/eprs_deb11_x86.mdx | 4 ++++ .../x86_amd64/eprs_other_linux8_x86.mdx | 4 ++++ .../03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx | 4 ++++ .../03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx | 4 ++++ .../03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx | 4 ++++ .../03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx | 4 ++++ .../x86_amd64/eprs_ubuntu18_x86.mdx | 4 ++++ .../x86_amd64/eprs_ubuntu20_x86.mdx | 4 ++++ 14 files changed, 58 insertions(+), 2 deletions(-) diff --git a/install_template/templates/products/replication-server/base.njk b/install_template/templates/products/replication-server/base.njk index 9dbb964d036..836ef9e93cc 100644 --- a/install_template/templates/products/replication-server/base.njk +++ b/install_template/templates/products/replication-server/base.njk @@ -31,4 +31,8 @@ Where `` is: | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | -{% endblock installCommand %} \ No newline at end of file +{% endblock installCommand %} +{% block postinstall %} +## Initial configuration +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. +{% endblock postinstall %} \ No newline at end of file diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx index 38b6c4dabcb..50b73abb14f 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_rhel8_ppcle.mdx @@ -66,3 +66,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx index 4fdffaa8210..e7889b68db9 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles12_ppcle.mdx @@ -62,3 +62,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx index 312244cbc96..982720d8f9d 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/ibm_power_ppc64le/eprs_sles15_ppcle.mdx @@ -61,3 +61,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx index f53f41891cc..a57b728df83 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_centos7_x86.mdx @@ -17,7 +17,7 @@ Before you begin the installation process: ``` !!!note - When Replication Server is installed on a machine where Java is not present, the JDK is installed as part of the installation process. Since, in this case, the JDK was installed via Replication Server as its dependency, if you subsequently remove the JDK, Replication Server is also removed. + When Replication Server is installed on a machine where Java is not present, the JDK is installed as part of the installation process. Since in this case the JDK was installed via Replication Server as its dependency, if you subsequently remove the JDK, Replication Server is also removed. If Java 1.8 or greater exists before installing Replication Server, the installed Replication Server is not removed on removal of the JDK. !!! @@ -59,3 +59,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx index 4b9cb383a93..958f452bced 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb10_x86.mdx @@ -51,3 +51,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb11_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb11_x86.mdx index 2336e455060..f520d282cb1 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb11_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_deb11_x86.mdx @@ -51,3 +51,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx index cac0f0f688f..425b7ff176e 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_other_linux8_x86.mdx @@ -61,3 +61,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx index 82340b0b564..444bb234610 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel7_x86.mdx @@ -59,3 +59,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx index cff2aed90dc..ba33fa6c86e 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_rhel8_x86.mdx @@ -64,3 +64,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx index 3cec985e1c1..d8a49112261 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles12_x86.mdx @@ -62,3 +62,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx index 71bcda99f7b..fe97f44ae63 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_sles15_x86.mdx @@ -61,3 +61,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu18_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu18_x86.mdx index 546da8b601c..411f2b9200f 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu18_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu18_x86.mdx @@ -51,3 +51,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu20_x86.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu20_x86.mdx index 1fbf1f34b86..ee313c1f641 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu20_x86.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package/x86_amd64/eprs_ubuntu20_x86.mdx @@ -51,3 +51,7 @@ Where `` is: | `edb-xdb-console` | Replication console and the Replication Server command line interface | | `edb-xdb-publisher` | Publication server | | `edb-xdb-subscriber` | Subscription server | + +## Initial configuration + +Before using Replication Server, you must download and install JDBC drivers. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for details. From 09933e794329dec7dab1eb6290c195cf10b9d80c Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 19 Oct 2022 06:53:12 -0400 Subject: [PATCH 12/50] fixed list ordering in Stackbuilder topic --- .../01_installing_with_stackbuilder.mdx | 193 +++++++++--------- 1 file changed, 97 insertions(+), 96 deletions(-) diff --git a/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx b/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx index dca03433f96..6f2158ca1e6 100644 --- a/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx +++ b/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx @@ -10,188 +10,189 @@ Stack Builder and StackBuilder Plus are very similar in functionality and look-a This section demonstrates the installation of Replication Server using StackBuilder Plus for Advanced Server. Steps are noted where the installation process differs for installation on PostgreSQL using Stack Builder. -**Step 1:** You must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (EPRS Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. +1. You must have Java Runtime Environment (JRE) version 1.8 or later installed on the hosts where you intend to install any Replication Server component (EPRS Replication Console, publication server, or subscription server). Any Java product such as Oracle Java or OpenJDK may be used. -Follow the directions for your host operating system to install Java runtime. + Follow the directions for your host operating system to install Java runtime. -**For Windows only:** Be sure the system environment variable, `JAVA_HOME`, is set to the JRE installation directory of the JRE version and bitness (32-bit or 64-bit) you wish to use with the Replication Server. The Replication Server installer for a Windows platform contains both the 32-bit and 64-bit versions. The `JAVA_HOME` setting determines whether the 32-bit or the 64-bit version of Replication Server is installed. (If `JAVA_HOME` is not set, then the first JRE version encountered in the Path system environment variable determines the Replication Server version to be installed.) + **For Windows only:** Be sure the system environment variable, `JAVA_HOME`, is set to the JRE installation directory of the JRE version and bitness (32-bit or 64-bit) you wish to use with the Replication Server. The Replication Server installer for a Windows platform contains both the 32-bit and 64-bit versions. The `JAVA_HOME` setting determines whether the 32-bit or the 64-bit version of Replication Server is installed. (If `JAVA_HOME` is not set, then the first JRE version encountered in the Path system environment variable determines the Replication Server version to be installed.) -!!! Note - For Advanced Server versions prior to 9.3, a Java runtime is supplied and installed as part of the Advanced Server installation process, however, you must still have pre-installed a separate Java runtime system on your host. The Replication Server installation process does not utilize the Java runtime supplied with Advanced Server. + !!! Note + For Advanced Server versions prior to 9.3, a Java runtime is supplied and installed as part of the Advanced Server installation process, however, you must still have pre-installed a separate Java runtime system on your host. The Replication Server installation process does not utilize the Java runtime supplied with Advanced Server. -!!! Note - After installation of Replication Server has completed, the path to your Java runtime program is stored in the Replication Server Startup Configuration file used by Replication Server. Verify that the path to your Java runtime program set in the Replication Server Startup Configuration file is correct. See [Installation details](03_installing_rpm_package/installation_details/) for the location of this file. + !!! Note + After installation of Replication Server has completed, the path to your Java runtime program is stored in the Replication Server Startup Configuration file used by Replication Server. Verify that the path to your Java runtime program set in the Replication Server Startup Configuration file is correct. See [Installation details](03_installing_rpm_package/installation_details/) for the location of this file. -**Step 2:** Install a JDBC driver. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for more information. +1. From the host’s application menu, open the Postgres menu and choose `Stack Builder` or `StackBuilder Plus`. -**Step 3:** From the host’s application menu, open the Postgres menu and choose `Stack Builder` or `StackBuilder Plus`. + ![Postgres application menu](../images/image26.png) -![Postgres application menu](../images/image26.png) + **Figure 3-1: Postgres application menu** -**Figure 3-1: Postgres application menu** +1. **(For Linux only):** Depending upon your Linux host, a dialog box or a prompt appears requesting the root account’s password. Enter the root password and click the `OK` button. -**Step 4 (For Linux only):** Depending upon your Linux host, a dialog box or a prompt appears requesting the root account’s password. Enter the root password and click the `OK` button. + ![Enter root account password](../images/image27.png) -![Enter root account password](../images/image27.png) + **Figure 3-2: Enter root account password** -**Figure 3-2: Enter root account password** +1. The StackBuilder Plus welcome screen appears. Select your `Postgres` installation from the drop-down list and click the `Next` button. -**Step 5:** The StackBuilder Plus welcome screen appears. Select your `Postgres` installation from the drop-down list and click the `Next` button. + ![StackBuilder Plus welcome screen](../images/image28.png) -![StackBuilder Plus welcome screen](../images/image28.png) + **Figure 3-3: StackBuilder Plus welcome screen** -**Figure 3-3: StackBuilder Plus welcome screen** + 1. (For Advanced Server):** Expand the EnterpriseDB Tools node and check the box for Replication Server. Click the Next button. -**Step 5 (For Advanced Server):** Expand the EnterpriseDB Tools node and check the box for Replication Server. Click the Next button. + !!! Note + Though the following ../images show Replication Server v6.0, use the same process for Replication Server v6.2. -!!! Note - Though the following ../images show Replication Server v6.0, use the same process for Replication Server v6.2. + ![StackBuilder Plus applications](../images/image29.png) -![StackBuilder Plus applications](../images/image29.png) + **Figure 3-4: StackBuilder Plus applications** -**Figure 3-4: StackBuilder Plus applications** +1. (For PostgreSQL):** Expand the Registration-Required and Trial Products node, and then expand the EnterpriseDB Tools node. Check the box for `Replication Server` under the `EnterpriseDB Tools` list and click the `Next` button. -**Step 6 (For PostgreSQL):** Expand the Registration-Required and Trial Products node, and then expand the EnterpriseDB Tools node. Check the box for `Replication Server` under the `EnterpriseDB Tools` list and click the `Next` button. + ![Stack Builder applications](../images/image30.png) -![Stack Builder applications](../images/image30.png) + **Figure 3-5: Stack Builder applications** -**Figure 3-5: Stack Builder applications** + ![EnterpriseDB Tools for PostgreSQL](../images/image31.png) -![EnterpriseDB Tools for PostgreSQL](../images/image31.png) + **Figure 3-6: EnterpriseDB Tools for PostgreSQL** -**Figure 3-6: EnterpriseDB Tools for PostgreSQL** + 1. (For Advanced Server only):** In the `Account Registration` screen, either enter your email address and password for your EnterpriseDB user account if you have one, or click the link in which case you will be directed to the registration page of the EnterpriseDB website where you can create an account. Click the `Next` button. -**Step 7 (For Advanced Server only):** In the `Account Registration` screen, either enter your email address and password for your EnterpriseDB user account if you have one, or click the link in which case you will be directed to the registration page of the EnterpriseDB website where you can create an account. Click the `Next` button. + !!! Note + (For PostgreSQL only): Proceed to Step 7. If you are using PostgreSQL, account registration occurs later in the process. -!!! Note - (For PostgreSQL only): Proceed to Step 7. If you are using PostgreSQL, account registration occurs later in the process. + ![EnterpriseDB account registration](../images/image32.png) -![EnterpriseDB account registration](../images/image32.png) + **Figure 3-7: EnterpriseDB account registration** -**Figure 3-7: EnterpriseDB account registration** +1. Verify that Replication Server appears in the list of selected packages. Click the `Next` button. -**Step 8:** Verify that Replication Server appears in the list of selected packages. Click the `Next` button. + ![Selected packages](../images/image33.png) -![Selected packages](../images/image33.png) + **Figure 3-8: Selected packages** -**Figure 3-8: Selected packages** + An information box appears showing the download progress of the Replication Server package. This may take a few minutes. -An information box appears showing the download progress of the Replication Server package. This may take a few minutes. + ![Downloading progress](../images/image34.png) -![Downloading progress](../images/image34.png) + **Figure 3-9: Downloading progress** -**Figure 3-9: Downloading progress** +1. When downloading of the Replication Server package completes, the following screen appears that starts the installation of Replication Server. Click the `Next` button. -**Step 9:** When downloading of the Replication Server package completes, the following screen appears that starts the installation of Replication Server. Click the `Next` button. + !!! Note + You can check the Skip Installation box if you wish to install Replication Server some other time. -!!! Note - You can check the Skip Installation box if you wish to install Replication Server some other time. + ![Start installation](../images/image35.png) -![Start installation](../images/image35.png) + **Figure 3-10: Start installation** -**Figure 3-10: Start installation** +1. Select the installation language and click the `OK` button. -**Step 10:** Select the installation language and click the `OK` button. + ![Installation language](../images/image36.png) -![Installation language](../images/image36.png) + **Figure 3-11: Installation language** -**Figure 3-11: Installation language** + 1. In the Setup Replication Server screen, click the `Next` button. -**Step 11:** In the Setup Replication Server screen, click the `Next` button. + ![Installation language](../images/image37.png) -![Installation language](../images/image37.png) + **Figure 3-12: Setup Replication Server** -**Figure 3-12: Setup Replication Server** +1. Read the license agreement. If you accept the agreement, select the accept radio button and click the `Next` button. -**Step 12:** Read the license agreement. If you accept the agreement, select the accept radio button and click the `Next` button. + ![Installation language](../images/image38.png) -![Installation language](../images/image38.png) + **Figure 3-13: License agreement** -**Figure 3-13: License agreement** +1. Browse to a directory where you want the Replication Server components installed, or allow it to install the components in the default location shown. Click the `Next` button. -**Step 13:** Browse to a directory where you want the Replication Server components installed, or allow it to install the components in the default location shown. Click the `Next` button. + ![Installation directory](../images/image39.png) -![Installation directory](../images/image39.png) + **Figure 3-14: Installation directory** -**Figure 3-14: Installation directory** +1. If you do not want a particular Replication Server component installed on this particular host, uncheck the box `Next` to the component name. Click the `Next` button. -**Step 14:** If you do not want a particular Replication Server component installed on this particular host, uncheck the box `Next` to the component name. Click the `Next` button. + ![Select components](../images/image40.png) -![Select components](../images/image40.png) + **Figure 3-15: Select components** -**Figure 3-15: Select components** +1. In the Account Registration screen select the radio button that applies to you. Click the `Next` button. + ![Account registration](../images/image41.png) -**Step 15:** In the Account Registration screen select the radio button that applies to you. Click the `Next` button. + **Figure 3-16: Account registration** -![Account registration](../images/image41.png) + If you do not have an EnterpriseDB user account, you will be directed to the registration page of the EnterpriseDB website. -**Figure 3-16: Account registration** + If you already have an EnterpriseDB user account, enter the email address and password for your EnterpriseDB user account as shown in the following screen. Click the `Next` button. -If you do not have an EnterpriseDB user account, you will be directed to the registration page of the EnterpriseDB website. + ![My EnterpriseDB account](../images/image42.png) -If you already have an EnterpriseDB user account, enter the email address and password for your EnterpriseDB user account as shown in the following screen. Click the `Next` button. + **Figure 3-17: My EnterpriseDB account** -![My EnterpriseDB account](../images/image42.png) +1. Enter information for the Replication Server administrator. -**Figure 3-17: My EnterpriseDB account** + !!! Note + From this point on, it is suggested that you record the values you enter on these screens as they will be needed during the publication and subscription server registration process. -**Step 16:** Enter information for the Replication Server administrator. + Enter values for the following fields: -!!! Note - From this point on, it is suggested that you record the values you enter on these screens as they will be needed during the publication and subscription server registration process. + - `Admin User.` The Replication Server administrator user name to authenticate certain usage of the Replication Server such as registering a publication server or a subscription server running on this host. Any alphanumeric string may be entered for the admin user name. The default admin user name is admin. + - `Admin Password.` Password of your choice for the Replication Server administrator given in the Admin User field. -Enter values for the following fields: + ![Replication Server admin user information](../images/image43.png) -- `Admin User.` The Replication Server administrator user name to authenticate certain usage of the Replication Server such as registering a publication server or a subscription server running on this host. Any alphanumeric string may be entered for the admin user name. The default admin user name is admin. -- `Admin Password.` Password of your choice for the Replication Server administrator given in the Admin User field. + **Figure 3-18: Replication Server admin user information** -![Replication Server admin user information](../images/image43.png) + The admin user and the admin password (in encrypted form) are saved to the EPRS Replication Configuration file named `/etc/edb-repl.conf (XDB_HOME\etc\edb-repl.conf` on Windows hosts). Click the `Next` button. -**Figure 3-18: Replication Server admin user information** +1. **(Only if publication server is a selected component):** Enter an available port on which the publication server will run. Default port number is 9051. Click the `Next` button. -The admin user and the admin password (in encrypted form) are saved to the EPRS Replication Configuration file named `/etc/edb-repl.conf (XDB_HOME\etc\edb-repl.conf` on Windows hosts). Click the `Next` button. + ![Replication Server admin user information](../images/image44.png) -**Step 17 (Only if publication server is a selected component):** Enter an available port on which the publication server will run. Default port number is 9051. Click the `Next` button. + **Figure 3-19: Publication server details** -![Replication Server admin user information](../images/image44.png) +1. **(Only if subscription server is a selected component):** Enter an available port on which the subscription server will run. Default port number is 9052. Click the `Next` button. -**Figure 3-19: Publication server details** + ![Subscription server details](../images/image45.png) -**Step 18 (Only if subscription server is a selected component):** Enter an available port on which the subscription server will run. Default port number is 9052. Click the `Next` button. + **Figure 3-20: Subscription server details** -![Subscription server details](../images/image45.png) +1. For the operating system account under which the publication server or subscription server is to run, enter `postgres` (`enterprisedb` if you are using Advanced Server installed in Oracle compatible configuration mode). -**Figure 3-20: Subscription server details** + ![Publication/subscription server operating system account](../images/image46.png) -**Step 19:** For the operating system account under which the publication server or subscription server is to run, enter `postgres` (`enterprisedb` if you are using Advanced Server installed in Oracle compatible configuration mode). + **Figure 3-21: Publication/subscription server operating system account** -![Publication/subscription server operating system account](../images/image46.png) +1. On the Ready to Install screen, click the `Next` button. -**Figure 3-21: Publication/subscription server operating system account** + ![Ready to install](../images/image47.png) -**Step 20:** On the Ready to Install screen, click the `Next` button. + **Figure 3-22: Ready to install** -![Ready to install](../images/image47.png) + An information box appears showing the installation progress of the Replication Server selected components. This may take a few minutes. -**Figure 3-22: Ready to install** + ![Installation progress](../images/image48.png) -An information box appears showing the installation progress of the Replication Server selected components. This may take a few minutes. + **Figure 3-23: Installation progress** -![Installation progress](../images/image48.png) +1. When installation has completed the following screen appears. Click the Finish button. -**Figure 3-23: Installation progress** + ![Replication Server installation completion](../images/image49.png) -**Step 21:** When installation has completed the following screen appears. Click the Finish button. + **Figure 3-24: Replication Server installation completion** -![Replication Server installation completion](../images/image49.png) +1. On the `StackBuilder Plus Installation Complete` screen, click the `Finish` button. -**Figure 3-24: Replication Server installation completion** + ![StackBuilder Plus installation complete](../images/image50.png) -**Step 22:** On the `StackBuilder Plus Installation Complete` screen, click the `Finish` button. + **Figure 3-25: StackBuilder Plus installation complete** -![StackBuilder Plus installation complete](../images/image50.png) + Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in Section [Installation details](03_installing_rpm_package/installation_details/). + +1. Install a JDBC driver. See [Installing a JDBC driver](/eprs/7/03_installation/installing_jdbc_driver) for more information. -**Figure 3-25: StackBuilder Plus installation complete** -Successful installation of Replication Server results in the creation of directory structures and files in your host environment as described in Section [Installation details](03_installing_rpm_package/installation_details/). From ee01761ae8d5abca680e1b23420c0b0bba26dab0 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 19 Oct 2022 06:59:15 -0400 Subject: [PATCH 13/50] Formatting tweaks to Stackbuilder topic --- .../7/03_installation/01_installing_with_stackbuilder.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx b/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx index 6f2158ca1e6..b552cbb647b 100644 --- a/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx +++ b/product_docs/docs/eprs/7/03_installation/01_installing_with_stackbuilder.mdx @@ -43,13 +43,13 @@ This section demonstrates the installation of Replication Server using StackBuil 1. (For Advanced Server):** Expand the EnterpriseDB Tools node and check the box for Replication Server. Click the Next button. !!! Note - Though the following ../images show Replication Server v6.0, use the same process for Replication Server v6.2. + Though the following images show Replication Server v6.0, use the same process for later versions of Replication Server. ![StackBuilder Plus applications](../images/image29.png) **Figure 3-4: StackBuilder Plus applications** -1. (For PostgreSQL):** Expand the Registration-Required and Trial Products node, and then expand the EnterpriseDB Tools node. Check the box for `Replication Server` under the `EnterpriseDB Tools` list and click the `Next` button. +1. **(For PostgreSQL):** Expand the Registration-Required and Trial Products node, and then expand the EnterpriseDB Tools node. Check the box for `Replication Server` under the `EnterpriseDB Tools` list and click the `Next` button. ![Stack Builder applications](../images/image30.png) @@ -59,10 +59,10 @@ This section demonstrates the installation of Replication Server using StackBuil **Figure 3-6: EnterpriseDB Tools for PostgreSQL** - 1. (For Advanced Server only):** In the `Account Registration` screen, either enter your email address and password for your EnterpriseDB user account if you have one, or click the link in which case you will be directed to the registration page of the EnterpriseDB website where you can create an account. Click the `Next` button. + 1. **(For Advanced Server only):** In the `Account Registration` screen, either enter your email address and password for your EnterpriseDB user account if you have one, or click the link in which case you will be directed to the registration page of the EnterpriseDB website where you can create an account. Click the `Next` button. !!! Note - (For PostgreSQL only): Proceed to Step 7. If you are using PostgreSQL, account registration occurs later in the process. + (For PostgreSQL only): Proceed to Step 6. If you are using PostgreSQL, account registration occurs later in the process. ![EnterpriseDB account registration](../images/image32.png) From 1af0773a7d264c2e8b50e17ba9e1c10901af5960 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Thu, 20 Oct 2022 06:46:27 -0400 Subject: [PATCH 14/50] fixed typo --- .../37a_print_column_mappings_publication.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/37a_print_column_mappings_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/37a_print_column_mappings_publication.mdx index ffd4bca9661..bd98e2b1bba 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/37a_print_column_mappings_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/37a_print_column_mappings_publication.mdx @@ -2,7 +2,7 @@ title: Printing the column mappings added to a publication (printusercolmapping) --- -**For SMR only:** The `printusercolmapping` command prints column data type mapping between the publication and subsciprtion database. +**For SMR only:** The `printusercolmapping` command prints column data type mapping between the publication and subscription database. ## Synopsis From 96db2dca2d9ee513bebf938060746bb054b8507f Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Mon, 24 Oct 2022 15:49:33 -0400 Subject: [PATCH 15/50] XDB-1660 update --- .../03_xdb_cli_commands/36_creating_subscription_cli.mdx | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index 2dd4af91985..162d3a8b852 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -90,11 +90,15 @@ Enter the path of the file containing the column mappings. Multiple custom type For example, create the file `/usr/edb/xdb/replicator/bin/columnMapping.txt` with the following contents: ```shell -uuidasprimarykey\.id=char -mapjson1\..*=clob +uuidasprimarykey\\.id=char +mapjson1\\..*=clob .*no=numeric ``` +!!! Note +Often, a single `\` acts as an escape character for the `.` operator. However, this file requires a `\\` for the `.` operator in order to read and write its contents. The `\.` acts as a separator and the single `.` operator acts as regular expression in this case. +!!! + And enter the complete path for the file in the `customcolmapfile` option: ```shell From 7fd6cb9f9e325d3bad465653f2020ab09a0585d5 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Mon, 31 Oct 2022 14:12:22 -0400 Subject: [PATCH 16/50] feedback changes --- .../04_preparing_pub_database.mdx | 9 --------- .../36_creating_subscription_cli.mdx | 4 ++-- .../04_troubleshooting_areas.mdx | 15 --------------- 3 files changed, 2 insertions(+), 26 deletions(-) diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx index 72c497b6529..ed8297d82be 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx @@ -307,15 +307,6 @@ GO In addition, depending on the version of SQL Server, grant the following privileges. Using this approach, however, requires you to issue additional privileges for each application table that is later added to the publication. -**For SQL Server 2008:** - -```sql -GRANT EXECUTE ON _edb_replicator_pub.nextval TO newuser; -GRANT SELECT ON _edb_replicator_pub.rrep_tx_seq TO newuser; -GRANT INSERT ON _edb_replicator_pub.rrep_tx_seq TO newuser; -GO -``` - **For SQL Server 2014:** ```sql diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index 162d3a8b852..5f79bbf98b4 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -49,7 +49,7 @@ Comma-separated list of filter IDs identifying the filter rules from the set of `customcolmap` -Enter the column mappings between different but compatible columns in the source and target database. Table and schema qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. +The column mappings between different but compatible columns in the source and target database. Table and schema qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. !!! Note Column mapping can be added only with the Replication Server CLI; this feature isn't supported by Replication Console. Column mappings are supported only for single-master replication clusters. @@ -85,7 +85,7 @@ The following is an example of regular expression for a column mapping entery: `customcolmapfile` -Enter the path of the file containing the column mappings. Multiple custom type mappings can also be provided in the file. You can use either the fully qualify column name or regression expression. Enter each mapping on a new line. + The file containing the column mappings. Multiple custom type mappings can also be provided in the file. You can use either the fully qualify column name or regression expression. Enter each mapping on a new line. For example, create the file `/usr/edb/xdb/replicator/bin/columnMapping.txt` with the following contents: diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx index 94b8d50a5a3..dc19d4758c9 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx @@ -173,21 +173,6 @@ Changed database context to 'edb'. 27> GO ``` -**For SQL Server 2008 only:** Drop the following control schema objects when the publication database is SQL Server 2008: - -```sql -1> USE edb; -2> GO -Changed database context to 'edb'. -1> DROP PROCEDURE _edb_replicator_pub.nextval; -2> DROP PROCEDURE _edb_replicator_pub.sp_createsequence; -3> DROP PROCEDURE _edb_replicator_pub.sp_dropsequence; -4> DROP TABLE _edb_replicator_pub.rrep_common_seq; -5> DROP TABLE _edb_replicator_pub.rrep_tx_seq; -6> DROP TABLE _edb_replicator_pub.rrep_txset_seq; -7> GO -``` - **For SQL Server 2014 only:** Drop the following control schema objects when the publication database is SQL Server 2014: ```sql From e57548778d507b9013ba1caa8e46aecf5c025dc1 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Mon, 31 Oct 2022 14:26:45 -0400 Subject: [PATCH 17/50] moved Permitted configurations and combinations page --- .../04_permitted_conf_and_permutations.mdx} | 2 ++ ...orted_jdk_versions.mdx => 05_supported_jdk_versions.mdx} | 2 ++ .../02_design_considerations.mdx | 2 +- .../10_replicating_postgres_partitioned_tables.mdx | 2 +- .../02_upgrading_with_gui_installer.mdx | 0 .../03_upgrading_with_xdb_rpm_package.mdx | 0 .../04_updating_sub_and_pub_ports.mdx | 0 .../index.mdx | 2 ++ .../01_error_messages.mdx | 6 +++--- .../02_where_to_look_for_errors.mdx | 0 .../03_common_problems_checklist.mdx | 0 .../04_troubleshooting_areas.mdx | 0 .../index.mdx | 2 ++ .../01_controlling_logging_level.mdx | 0 .../02_replacing_null_characters.mdx | 0 .../03_schema_migration_options.mdx | 0 .../04_replicate_oracle_partitioned_tables.mdx | 0 .../05_specify_custom_url_for_oracle_jdbc.mdx | 0 .../06_snapshot_replication_options.mdx | 0 .../07_assign_ip_adress_for_rmi.mdx | 0 .../08_using_pgagent_job_scheduling.mdx | 0 .../09_forcing_shadow_table_cleanup.mdx | 0 .../10_setting_event_history_cleanup.mdx | 0 .../11_ddl_change_replication_table_locking.mdx | 0 .../12_persisting_zero_txn_replication_hist.mdx | 0 ...kipping_grants_of_table_level_user_privileges_on_mmr.mdx | 0 ...pplying_grants_of_table_level_user_privileges_on_smr.mdx | 0 .../15_log_based_sync_options.mdx | 0 .../16_setting_apache_dbcp_connection_validation_query.mdx | 0 .../index.mdx | 0 .../02_encrypt_password_inconf_file.mdx | 0 .../03_writing_cron_exp.mdx | 0 ...ble_foreign_key_constraints_for_snapshot_replication.mdx | 0 .../05_quoted_identifiers.mdx | 0 .../06_replicating_sql_server_sql_variant_data_type.mdx | 0 .../index.mdx | 2 ++ ...pack_maintenance.mdx => 04_service_pack_maintenance.mdx} | 2 ++ 37 files changed, 17 insertions(+), 5 deletions(-) rename product_docs/docs/eprs/7/{10_appendix/01_permitted_conf_and_permutations.mdx => 01_introduction/04_permitted_conf_and_permutations.mdx} (98%) rename product_docs/docs/eprs/7/01_introduction/{04_supported_jdk_versions.mdx => 05_supported_jdk_versions.mdx} (95%) rename product_docs/docs/eprs/7/10_appendix/{02_upgrading_to_xdb6_2 => 01_upgrading_to_xdb6_2}/02_upgrading_with_gui_installer.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{02_upgrading_to_xdb6_2 => 01_upgrading_to_xdb6_2}/03_upgrading_with_xdb_rpm_package.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{02_upgrading_to_xdb6_2 => 01_upgrading_to_xdb6_2}/04_updating_sub_and_pub_ports.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{02_upgrading_to_xdb6_2 => 01_upgrading_to_xdb6_2}/index.mdx (93%) rename product_docs/docs/eprs/7/10_appendix/{03_resolving_problems => 02_resolving_problems}/01_error_messages.mdx (98%) rename product_docs/docs/eprs/7/10_appendix/{03_resolving_problems => 02_resolving_problems}/02_where_to_look_for_errors.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{03_resolving_problems => 02_resolving_problems}/03_common_problems_checklist.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{03_resolving_problems => 02_resolving_problems}/04_troubleshooting_areas.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{03_resolving_problems => 02_resolving_problems}/index.mdx (82%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/01_publications_and_subscriptions_server_conf_options/index.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/02_encrypt_password_inconf_file.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/03_writing_cron_exp.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/04_disable_foreign_key_constraints_for_snapshot_replication.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/05_quoted_identifiers.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/06_replicating_sql_server_sql_variant_data_type.mdx (100%) rename product_docs/docs/eprs/7/10_appendix/{04_miscellaneous_xdb_processing_topics => 03_miscellaneous_xdb_processing_topics}/index.mdx (88%) rename product_docs/docs/eprs/7/10_appendix/{05_service_pack_maintenance.mdx => 04_service_pack_maintenance.mdx} (94%) diff --git a/product_docs/docs/eprs/7/10_appendix/01_permitted_conf_and_permutations.mdx b/product_docs/docs/eprs/7/01_introduction/04_permitted_conf_and_permutations.mdx similarity index 98% rename from product_docs/docs/eprs/7/10_appendix/01_permitted_conf_and_permutations.mdx rename to product_docs/docs/eprs/7/01_introduction/04_permitted_conf_and_permutations.mdx index 14c5549b953..49f182de08b 100644 --- a/product_docs/docs/eprs/7/10_appendix/01_permitted_conf_and_permutations.mdx +++ b/product_docs/docs/eprs/7/01_introduction/04_permitted_conf_and_permutations.mdx @@ -1,5 +1,7 @@ --- title: "Permitted configurations and combinations" +redirects: +- /docs/eprs/latest/10_appendix/01_permitted_conf_and_permutations/ --- diff --git a/product_docs/docs/eprs/7/01_introduction/04_supported_jdk_versions.mdx b/product_docs/docs/eprs/7/01_introduction/05_supported_jdk_versions.mdx similarity index 95% rename from product_docs/docs/eprs/7/01_introduction/04_supported_jdk_versions.mdx rename to product_docs/docs/eprs/7/01_introduction/05_supported_jdk_versions.mdx index edbb6ad3b74..cb3ca7d6f48 100644 --- a/product_docs/docs/eprs/7/01_introduction/04_supported_jdk_versions.mdx +++ b/product_docs/docs/eprs/7/01_introduction/05_supported_jdk_versions.mdx @@ -1,5 +1,7 @@ --- title: "Supported platforms" +redirects: +- /docs/eprs/latest/01_introduction/04_supported_jdk_versions/ --- Replication Server is certified to work with the following Java platforms: diff --git a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx index efdb020157f..38233036b6d 100644 --- a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx +++ b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx @@ -38,7 +38,7 @@ CREATE TABLE dept_uk2 ( - A database can contain both publications and subscriptions. - A given publication server can support only one multi-master replication system. All primary nodes created subordinate to a given publication server are assumed to be part of the same multi-master replication system. - You can use a table that is created as a result of a subscription in another publication. Thus, a publication can replicate data to a subscription which, in turn, you can use in a publication to replicate to another subscription. This scenario creates a cascaded replication architecture. -- For restrictions on the combinations and configurations of database servers that you can use for a publication and its subscription, see [EDB Postgres Advanced Server compatibility configuration modes](../../10_appendix/01_permitted_conf_and_permutations/#edb-postgres-advanced-server-compatibility-configuration-modes). +- For restrictions on the combinations and configurations of database servers that you can use for a publication and its subscription, see [EDB Postgres Advanced Server compatibility configuration modes](/eprs/latest/01_introduction/04_permitted_conf_and_permutations/#edb-postgres-advanced-server-compatibility-configuration-modes). - All replication system components must be running for replication to occur or before you configure, operate, or modify the replication system. Use the Replication Server console to configure and modify a replication system. The console doesn't need to be running for replication to occur. - In general, the order of creating a replication system is as follows: 1. Create the required physical databases, database user names, tables, and views to use in the replication system. diff --git a/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx b/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx index 729122d6994..cd8bd40a4d4 100644 --- a/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/10_replicating_postgres_partitioned_tables.mdx @@ -281,7 +281,7 @@ The following restrictions apply when the publication contains a table with part - You must select the log-based method of synchronization replication for the publication database. You can't use the trigger-based method. - In a single-master replication system, the subscription databases must be Postgres version 10 or later. You can't use Oracle and SQL Server as a subscription database. -- In a multi-master replication system, all primary nodes must be Postgres version 10 or later with the same compatibility mode as the primary definition node (that is, either compatible with native PostgreSQL or compatible with Oracle databases). For more information on the multi-master replication system compatibility modes, see [Permitted MMR database server configurations](../10_appendix/01_permitted_conf_and_permutations/#permitted-mmr-database-server-configurations). +- In a multi-master replication system, all primary nodes must be Postgres version 10 or later with the same compatibility mode as the primary definition node (that is, either compatible with native PostgreSQL or compatible with Oracle databases). For more information on the multi-master replication system compatibility modes, see [Permitted MMR database server configurations](/eprs/latest/01_introduction/04_permitted_conf_and_permutations/#permitted-mmr-database-server-configurations). Follow the steps in [Creating a publication](../06_mmr_operation/02_creating_publication_mmr/#creating_publication_mmr) to create a primary definition node along with a publication containing the partitioned table. (For a single-master replication system, create the publication database along with the publication following the steps in [Creating a publication](../05_smr_operation/02_creating_publication/#creating_publication).) diff --git a/product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx rename to product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx rename to product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx rename to product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/index.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/index.mdx similarity index 93% rename from product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/index.mdx rename to product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/index.mdx index e10458ebcaf..ff8666e0c36 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_upgrading_to_xdb6_2/index.mdx +++ b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/index.mdx @@ -1,5 +1,7 @@ --- title: "Upgrading to Replication Server 7.0" +redirects: +- /docs/eprs/latest/10_appendix/02_upgrading_to_xdb6_2/ --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/01_error_messages.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx similarity index 98% rename from product_docs/docs/eprs/7/10_appendix/03_resolving_problems/01_error_messages.mdx rename to product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx index fbbc25ce855..57a658666dc 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/01_error_messages.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx @@ -128,7 +128,7 @@ Occurs when attempting to add a subscription database. Verify that the Replicati **Resolution** -All database servers in a multi-master replication system must be of the same type—either all PostgreSQL (or EDB Postgres Advanced Server installed in PostgreSQL-compatible configuration mode) or all EDB Postgres Advanced Server installed in Oracle-compatible configuration mode. This error message appears when attempting to add a primary node and the database server type differs from the database server type of the primary definition node. See [Permitted MMR database server configurations](../01_permitted_conf_and_permutations/#permitted_mmr_db_server_conf). +All database servers in a multi-master replication system must be of the same type—either all PostgreSQL (or EDB Postgres Advanced Server installed in PostgreSQL-compatible configuration mode) or all EDB Postgres Advanced Server installed in Oracle-compatible configuration mode. This error message appears when attempting to add a primary node and the database server type differs from the database server type of the primary definition node. See [Permitted MMR database server configurations](/eprs/latest/01_introduction/04_permitted_conf_and_permutations/#permitted_mmr_db_server_conf). **Problem** @@ -432,7 +432,7 @@ Might be caused by characters in the publication data that are illegal for the c **Resolution** -See [Permitted configurations and combinations](../01_permitted_conf_and_permutations/#permitted_conf_and_permutations) for supported database server configurations. Use Oracle products for Oracle-to-Oracle replication. +See [Permitted configurations and combinations](/eprs/latest/01_introduction/04_permitted_conf_and_permutations/#permitted_conf_and_permutations) for supported database server configurations. Use Oracle products for Oracle-to-Oracle replication. **Problem** @@ -596,7 +596,7 @@ Occurs when creating a subscription. The subscription server running on host `xx **Resolution** -The subscription database type isn't supported for the intended publication database type. See [Permitted SMR source and target configurations](../01_permitted_conf_and_permutations/#permitted_smr_source_and_target_conf). +The subscription database type isn't supported for the intended publication database type. See [Permitted SMR source and target configurations](/eprs/latest/01_introduction/04_permitted_conf_and_permutations/#permitted_smr_source_and_target_conf). **Problem** diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/02_where_to_look_for_errors.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/03_resolving_problems/02_where_to_look_for_errors.mdx rename to product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/03_common_problems_checklist.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/03_resolving_problems/03_common_problems_checklist.mdx rename to product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/03_resolving_problems/04_troubleshooting_areas.mdx rename to product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/index.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/index.mdx similarity index 82% rename from product_docs/docs/eprs/7/10_appendix/03_resolving_problems/index.mdx rename to product_docs/docs/eprs/7/10_appendix/02_resolving_problems/index.mdx index 3fe874d6dab..ae6fcc6e9f2 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_resolving_problems/index.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/index.mdx @@ -1,5 +1,7 @@ --- title: "Resolving problems" +redirects: +- /docs/eprs/latest/10_appendix/03_resolving_problems/ --- diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx similarity index 100% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx diff --git a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/index.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/index.mdx similarity index 88% rename from product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/index.mdx rename to product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/index.mdx index 7e09cbd1635..ccac31360c7 100644 --- a/product_docs/docs/eprs/7/10_appendix/04_miscellaneous_xdb_processing_topics/index.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/index.mdx @@ -1,5 +1,7 @@ --- title: "Miscellaneous Replication Server processing topics" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/ --- diff --git a/product_docs/docs/eprs/7/10_appendix/05_service_pack_maintenance.mdx b/product_docs/docs/eprs/7/10_appendix/04_service_pack_maintenance.mdx similarity index 94% rename from product_docs/docs/eprs/7/10_appendix/05_service_pack_maintenance.mdx rename to product_docs/docs/eprs/7/10_appendix/04_service_pack_maintenance.mdx index a5a13229edf..9557210860c 100644 --- a/product_docs/docs/eprs/7/10_appendix/05_service_pack_maintenance.mdx +++ b/product_docs/docs/eprs/7/10_appendix/04_service_pack_maintenance.mdx @@ -1,5 +1,7 @@ --- title: "Service pack maintenance" +redirects: +- /docs/eprs/latest/10_appendix/05_service_pack_maintenance/ --- From c86b7b101262dd69a3c6280202c34facb059e552 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Mon, 31 Oct 2022 15:32:09 -0400 Subject: [PATCH 18/50] added redirects --- .../01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx | 2 ++ .../03_upgrading_with_xdb_rpm_package.mdx | 2 ++ .../01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx | 2 ++ .../7/10_appendix/02_resolving_problems/01_error_messages.mdx | 2 ++ .../02_resolving_problems/02_where_to_look_for_errors.mdx | 2 ++ .../02_resolving_problems/03_common_problems_checklist.mdx | 2 ++ .../02_resolving_problems/04_troubleshooting_areas.mdx | 2 ++ .../01_controlling_logging_level.mdx | 2 ++ .../02_replacing_null_characters.mdx | 2 ++ .../03_schema_migration_options.mdx | 2 ++ .../04_replicate_oracle_partitioned_tables.mdx | 2 ++ .../05_specify_custom_url_for_oracle_jdbc.mdx | 2 ++ .../06_snapshot_replication_options.mdx | 2 ++ .../07_assign_ip_adress_for_rmi.mdx | 2 ++ .../08_using_pgagent_job_scheduling.mdx | 2 ++ .../09_forcing_shadow_table_cleanup.mdx | 2 ++ .../10_setting_event_history_cleanup.mdx | 2 ++ .../11_ddl_change_replication_table_locking.mdx | 2 ++ .../12_persisting_zero_txn_replication_hist.mdx | 2 ++ ...13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx | 2 ++ ...14_applying_grants_of_table_level_user_privileges_on_smr.mdx | 2 ++ .../15_log_based_sync_options.mdx | 2 ++ .../16_setting_apache_dbcp_connection_validation_query.mdx | 2 ++ .../index.mdx | 2 ++ .../02_encrypt_password_inconf_file.mdx | 2 ++ .../03_writing_cron_exp.mdx | 2 ++ ...disable_foreign_key_constraints_for_snapshot_replication.mdx | 2 ++ .../05_quoted_identifiers.mdx | 2 ++ .../06_replicating_sql_server_sql_variant_data_type.mdx | 2 ++ 29 files changed, 58 insertions(+) diff --git a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx index 55ee4cfcee3..acec13906ac 100644 --- a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx @@ -1,5 +1,7 @@ --- title: "Upgrading with the graphical user interface installer" +redirects: +- /docs/eprs/latest/10_appendix/02_upgrading_to_xdb6_2/02_upgrading_with_gui_installer --- diff --git a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx index caa44eb09ae..3db3fb32f6a 100644 --- a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx +++ b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package.mdx @@ -1,5 +1,7 @@ --- title: "Upgrading from a Replication Server RPM package installation" +redirects: +- /docs/eprs/latest/10_appendix/02_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package --- diff --git a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx index 188d811f4c0..29222bb2b3f 100644 --- a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx +++ b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports.mdx @@ -1,5 +1,7 @@ --- title: "Updating the publication and subscription server ports" +redirects: +- /docs/eprs/latest/10_appendix/02_upgrading_to_xdb6_2/04_updating_sub_and_pub_ports --- diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx index 57a658666dc..0fce5c9da49 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx @@ -1,5 +1,7 @@ --- title: "Error messages" +redirects: +- /docs/eprs/latest/10_appendix/03_resolving_problems/01_error_messages --- diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx index 43c405a5d26..b0b614584c4 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx @@ -1,5 +1,7 @@ --- title: "Where to look for errors" +redirects: +- /docs/eprs/latest/10_appendix/03_resolving_problems/02_where_to_look_for_errors --- diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx index 173dd069809..970c1b2d59a 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx @@ -1,5 +1,7 @@ --- title: "Common problems checklist" +redirects: +- /docs/eprs/latest/10_appendix/03_resolving_problems/03_common_problems_checklist --- diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx index dc19d4758c9..8022568374a 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/04_troubleshooting_areas.mdx @@ -1,5 +1,7 @@ --- title: "Troubleshooting areas" +redirects: +- /docs/eprs/latest/10_appendix/03_resolving_problems/04_troubleshooting_areas --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx index 8e48df8fb73..f162830e152 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx @@ -1,5 +1,7 @@ --- title: "Controlling logging level, log file sizes, and rotation count" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx index 692fb45fc3d..68a9e63d1fb 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters.mdx @@ -1,5 +1,7 @@ --- title: "Replacing null characters" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx index 7552b5178b4..a707590ccbc 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options.mdx @@ -1,5 +1,7 @@ --- title: "Schema migration options" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/03_schema_migration_options --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx index 684c3b1f8b9..ad0560474c5 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables.mdx @@ -1,5 +1,7 @@ --- title: "Replicating Oracle partitioned tables" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx index ccaffb16213..1a54f42b13b 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc.mdx @@ -1,5 +1,7 @@ --- title: "Specifying a custom URL for an Oracle JDBC connection" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx index 1298c559e41..d155343c507 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options.mdx @@ -1,5 +1,7 @@ --- title: "Snapshot replication options" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/06_snapshot_replication_options --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx index 56ceedb0613..bd7c39cb9c2 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi.mdx @@ -1,5 +1,7 @@ --- title: "Assigning an IP address for remote method invocation" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx index dfb304070fa..8191be5c466 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling.mdx @@ -1,5 +1,7 @@ --- title: "Using pgAgent job scheduling" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx index f67e52f469d..672ea1ee9d6 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup.mdx @@ -1,5 +1,7 @@ --- title: "Forcing immediate shadow table cleanup" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx index e613897d39a..762905bddc0 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup.mdx @@ -1,5 +1,7 @@ --- title: "Setting event history cleanup threshold" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx index a3604fb2586..dbf7e198b36 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking.mdx @@ -1,5 +1,7 @@ --- title: "DDL change replication table locking" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx index 32b7e108ea0..b63b602b85f 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist.mdx @@ -1,5 +1,7 @@ --- title: "Persisting zero transaction count replication history" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/12_persisting_zero_txn_replication_hist --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx index 51a66137603..3bb4d136e60 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr.mdx @@ -1,5 +1,7 @@ --- title: "Skipping grants of table-level user privileges on MMR target tables" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx index 428b0eef3cc..15c03dd0647 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr.mdx @@ -1,5 +1,7 @@ --- title: "Applying grants of table-level user privileges on SMR target tables" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/14_applying_grants_of_table_level_user_privileges_on_smr --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx index b27f04acf5f..528da59f343 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options.mdx @@ -1,5 +1,7 @@ --- title: "Log-based method of synchronization options" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx index 3da953d8370..7a36d86539a 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query.mdx @@ -1,5 +1,7 @@ --- title: "Setting the Apache DBCP connection validation query timeout" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/16_setting_apache_dbcp_connection_validation_query --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx index f92d61b0057..77a05995c26 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/index.mdx @@ -1,5 +1,7 @@ --- title: "Publication and subscription server configuration options" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx index 114e07d33be..29c367476b7 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file.mdx @@ -1,5 +1,7 @@ --- title: "Encrypting the password in the Replication Server configuration file" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx index 9f6ea611f72..9668766736e 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp.mdx @@ -1,5 +1,7 @@ --- title: "Writing a cron expression" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx index 912108c0589..6805884f79e 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication.mdx @@ -1,5 +1,7 @@ --- title: "Disabling foreign key constraints for snapshot replications" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx index a07a841f6f1..ee02d0bffc3 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers.mdx @@ -1,5 +1,7 @@ --- title: "Quoted identifiers and default case translation" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers --- diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx index 2eb19b40c69..b54899ad7b3 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type.mdx @@ -1,5 +1,7 @@ --- title: "Replicating the SQL server SQL_VARIANT data type" +redirects: +- /docs/eprs/latest/10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type --- From 61d28d9f6aa9de6e16b793cadecc610722b3700a Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 1 Nov 2022 09:21:14 -0400 Subject: [PATCH 19/50] fixed broken links --- .../08_snapshot_replication.mdx | 2 +- .../01_requirements_and_restrictions.mdx | 2 +- .../04_replication_origin.mdx | 2 +- .../01_physical_components.mdx | 2 +- .../02_design_considerations.mdx | 2 +- .../03_restrictions_on_replicated_database_objects.mdx | 4 ++-- .../7/03_installation/03_installing_rpm_package.mdx | 4 ++-- .../03a_updating_linux_installation.mdx | 2 +- product_docs/docs/eprs/7/03_installation/index.mdx | 2 +- .../01_prerequisites/04_preparing_pub_database.mdx | 2 +- .../01_prerequisites/05_preparing_sub_database.mdx | 2 +- .../06_verifying_host_accessibility.mdx | 2 +- .../01_registering_publication_server.mdx | 2 +- .../01_registering_subscription_server.mdx | 2 +- .../7/05_smr_operation/06_performing_switchover.mdx | 2 +- .../02_optimize_sync_replication/index.mdx | 2 +- .../08_optimizing_performance/index.mdx | 2 +- .../docs/eprs/7/06_mmr_operation/01_pre_steps.mdx | 6 +++--- .../06_mmr_operation/12_optimizing_performance_mmr.mdx | 4 ++-- .../7/07_common_operations/02_creating_schedule.mdx | 2 +- .../04_view_replication_history.mdx | 2 +- .../7/07_common_operations/05_managing_history.mdx | 10 +++++----- .../01_ddl_change_replication.mdx | 2 +- .../07_common_operations/11_using_ssl_connections.mdx | 2 +- .../14_creating_publication_cli.mdx | 2 +- .../18_adding_tables_to_publication.mdx | 2 +- .../19_removing_tables_from_publication.mdx | 2 +- .../20_adding_tablefilters_to_publication.mdx | 2 +- .../23_print_conflict_resolution_strategy.mdx | 2 +- .../24_updating_conflict_resolution_strategy.mdx | 2 +- .../03_xdb_cli_commands/43_configure_smr_schedule.mdx | 2 +- .../03_xdb_cli_commands/44_configure_mmr_schedule.mdx | 2 +- .../48_schedule_shadow_table_history_clean.mdx | 2 +- .../02_upgrading_with_gui_installer.mdx | 2 +- .../02_resolving_problems/01_error_messages.mdx | 10 +++++----- .../02_where_to_look_for_errors.mdx | 6 +++--- .../03_common_problems_checklist.mdx | 2 +- .../01_controlling_logging_level.mdx | 2 +- 38 files changed, 53 insertions(+), 53 deletions(-) diff --git a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx index a88b3969352..006c4473cc6 100644 --- a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx +++ b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/08_snapshot_replication.mdx @@ -15,6 +15,6 @@ If the target table (regardless of database type) contains a large object data t !!! Note EDB Postgres Advanced Server supports a number of aliases for data types. Such aliases that translate to `BYTEA` are treated as large object data types. See the [Database Compatibility for Oracle Developers Reference Guide](/epas/latest/epas_compat_reference/) for a listing of EDB Postgres Advanced Server data types. (See the [Database Compatibility for Oracle Developer’s Guide](/epas/latest/epas_compat_ora_dev_guide/) for EDB Postgres Advanced Server version 9.5 or earlier versions.) -Under certain circumstances, the corresponding Postgres target table created for certain types of Oracle partitioned tables is a set of inherited tables. In these cases, the `SQL DELETE` statement is used on the inherited child tables instead of truncation. See [Replicating Oracle partitioned tables](../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables/#replicate_oracle_partitioned_tables). +Under certain circumstances, the corresponding Postgres target table created for certain types of Oracle partitioned tables is a set of inherited tables. In these cases, the `SQL DELETE` statement is used on the inherited child tables instead of truncation. See [Replicating Oracle partitioned tables](../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables/#replicate_oracle_partitioned_tables). A server configuration option is available that forces the snapshot replication process to use the Oracle database link utility instead of `JDBC COPY` to populate the Postgres target tables from an Oracle publication. Oracle database link provides a performance improvement over `JDBC COPY`. See [Optimizing snapshot replication](../../05_smr_operation/08_optimizing_performance/01_optimizing_snapshot_replication/#optimizing_snapshot_replication) for information on using the Oracle database link option as well as various configuration options to optimize snapshot replication. diff --git a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/01_requirements_and_restrictions.mdx b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/01_requirements_and_restrictions.mdx index 1232543915f..df4713e2cb3 100644 --- a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/01_requirements_and_restrictions.mdx +++ b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/01_requirements_and_restrictions.mdx @@ -33,4 +33,4 @@ In addition, the `pg_hba.conf` configuration file of the Postgres database serve See [Postgres server authentication](../../../05_smr_operation/01_prerequisites/06_verifying_host_accessibility/#postgres_server_auth) for setting `REPLICATION` access for a single-master replication system. See [Verifying host accessibility](../../../05_smr_operation/01_prerequisites/06_verifying_host_accessibility/#verifying_host_accessibility) for a multi-master replication system. -For configuration options in the publication server configuration file that specifically apply to the log-based method see [Log-based method of synchronization options](../../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options/#log_based_sync_options). +For configuration options in the publication server configuration file that specifically apply to the log-based method see [Log-based method of synchronization options](../../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options/#log_based_sync_options). diff --git a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx index 52b8cdaeae6..95db9126cd5 100644 --- a/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx +++ b/product_docs/docs/eprs/7/02_overview/02_replication_concepts_and_definitions/10_sync_replication_log_based/04_replication_origin.mdx @@ -104,4 +104,4 @@ The replication slots are in the active state when the publication server is run The replication slots and replication origin sessions are deleted from the database cluster when their corresponding primary nodes are removed from the multi-master replication system using the Replication Server Console or the Replication Server CLI. -If the replication slots aren't properly deleted when required, see [Dropping replication slots for log-based synchronization replication](../../../10_appendix/03_resolving_problems/04_troubleshooting_areas/#drop_replication_slots_for_log_based) to learn how to delete them manually. +If the replication slots aren't properly deleted when required, see [Dropping replication slots for log-based synchronization replication](../../../10_appendix/02_resolving_problems/04_troubleshooting_areas/#drop_replication_slots_for_log_based) to learn how to delete them manually. diff --git a/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx b/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx index 9e0fe7ce035..feeae917de9 100644 --- a/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx +++ b/product_docs/docs/eprs/7/02_overview/03_replication_server_components_and_architecture/01_physical_components.mdx @@ -119,7 +119,7 @@ host=192.168.2.23 ``` !!! Note - The passwords for the admin user name and the controller database user name are encrypted. If you change either of these passwords, you must modify the corresponding password parameters in the replication configuration file to contain the encrypted form of the new password. See [Encrypting the password in the replication configuration file](../../10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file) for directions on how to generate the encrypted form of a password. + The passwords for the admin user name and the controller database user name are encrypted. If you change either of these passwords, you must modify the corresponding password parameters in the replication configuration file to contain the encrypted form of the new password. See [Encrypting the password in the replication configuration file](../../10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file) for directions on how to generate the encrypted form of a password. See [Installation details](/eprs/latest/03_installation/03_installing_rpm_package/installation_details) for the file system location of the EPRS Replication Configuration file. diff --git a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx index 38233036b6d..237db02d495 100644 --- a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx +++ b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/02_design_considerations.mdx @@ -48,7 +48,7 @@ CREATE TABLE dept_uk2 ( 1. Remove the replication system logical components using the Replication Server console or CLI, starting with the subscriptions (Subscription nodes) and then their parent components (Subscription Database nodes). 1. Unregister the subscription server if you no longer need it. 1. Repeat the same process for the publications. - 1. After all replication system logical components are removed (except for possibly the publication server and subscription server) you can drop any of the physical database objects in Oracle, SQL Server, or Postgres. Don't drop the control schema objects manually, for example by using an SQL command line utility. Doing so can cause the Replication Server console and CLI to stop working. See [Deleting the control schema and control schema objects](../../10_appendix/03_resolving_problems/04_troubleshooting_areas/#deleting-the-control-schema-and-control-schema-objects) if this problem occurs. Deleting the replication system logical components using the Replication Server console or CLI drops the control schema objects from the physical database. + 1. After all replication system logical components are removed (except for possibly the publication server and subscription server) you can drop any of the physical database objects in Oracle, SQL Server, or Postgres. Don't drop the control schema objects manually, for example by using an SQL command line utility. Doing so can cause the Replication Server console and CLI to stop working. See [Deleting the control schema and control schema objects](../../10_appendix/02_resolving_problems/04_troubleshooting_areas/#deleting-the-control-schema-and-control-schema-objects) if this problem occurs. Deleting the replication system logical components using the Replication Server console or CLI drops the control schema objects from the physical database. - The order of removing a multi-master replication system is as follows: 1. Remove the replication system logical components using the Replication Server console or CLI starting with the publication database definitions of the non-MDN nodes. 1. Remove the publication from under the primary definition node. diff --git a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx index 86cb8a88534..16c4e3e7537 100644 --- a/product_docs/docs/eprs/7/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx +++ b/product_docs/docs/eprs/7/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx @@ -30,7 +30,7 @@ Replication Server does have some restrictions on the types of tables it can rep The following are the restrictions on Oracle database objects: -- You can replicate certain types of Oracle partitioned tables. See [Replicating Oracle partitioned tables](../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables/#replicate_oracle_partitioned_tables) for details. +- You can replicate certain types of Oracle partitioned tables. See [Replicating Oracle partitioned tables](../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/04_replicate_oracle_partitioned_tables/#replicate_oracle_partitioned_tables) for details. - You can't replicate Oracle global temporary tables. @@ -68,7 +68,7 @@ You can't replicate SQL Server tables that include the following data types: - `SQL_VARIANT` !!! Note - See [Replicating the SQL Server SQL_VARIANT data type](../../10_appendix/04_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type/#replicating_sql_server_sql_variant_data_type) for a method to replicate tables containing the `SQL_VARIANT` data type under certain conditions. + See [Replicating the SQL Server SQL_VARIANT data type](../../10_appendix/03_miscellaneous_xdb_processing_topics/06_replicating_sql_server_sql_variant_data_type/#replicating_sql_server_sql_variant_data_type) for a method to replicate tables containing the `SQL_VARIANT` data type under certain conditions. You can use SQL Server tables with the following data types in snapshot-only publications but not in synchronization replications: diff --git a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package.mdx index 8f768f0a421..698183aa3ee 100644 --- a/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/7/03_installation/03_installing_rpm_package.mdx @@ -246,7 +246,7 @@ Successful installation of Replication Server results in the creation of directo !!! Note Neither the publication server nor the subscription server are running immediately following installation. If after reviewing the remaining steps, you wish to start the publication server, see [Registering a Publication Server](../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server). For starting the subscription server see [Registering a Subscription Server](../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). -**Step 5 (For Replication Server 7.0 and 6.2):** In the EPRS Replication Configuration file `/etc/edb-repl.conf`, you can either use the default password (`edb`) as the admin user password, or you can substitute a password of your choice. If you want to use your own password, see [Encrypting the Password in the EPRS Replication Configuration File](../10_appendix/04_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file) on how to generate the encrypted form of the password. Place the encrypted password in the admin_password parameter of the EPRS Replication Configuration file. The default admin user name is set to admin and can be changed as well. See [EPRS Replication Configuration File](../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for information on the EPRS Replication Configuration file. +**Step 5 (For Replication Server 7.0 and 6.2):** In the EPRS Replication Configuration file `/etc/edb-repl.conf`, you can either use the default password (`edb`) as the admin user password, or you can substitute a password of your choice. If you want to use your own password, see [Encrypting the Password in the EPRS Replication Configuration File](../10_appendix/03_miscellaneous_xdb_processing_topics/02_encrypt_password_inconf_file) on how to generate the encrypted form of the password. Place the encrypted password in the admin_password parameter of the EPRS Replication Configuration file. The default admin user name is set to admin and can be changed as well. See [EPRS Replication Configuration File](../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_replication_conf_file) for information on the EPRS Replication Configuration file. **Step 6:** The `JAVA_EXECUTABLE_PATH` parameter in the Replication Server Startup Configuration file should be set so that the Java runtime program can be accessed upon startup of the publication server and subscription server. If the publication server or subscription server startup fails due to inaccessibility to the Java program, be sure to set the path to your Java runtime program in the Replication Server Startup Configuration file. See [Replication Server Startup Configuration File](../02_overview/03_replication_server_components_and_architecture/01_physical_components/#xdb_startup_conf_file) for information on the Replication Server Startup Configuration file. See [Installation details](03_installing_rpm_package/installation_details/) for the location of this file. @@ -321,7 +321,7 @@ If you have an existing Replication Server RPM installation, you can use yum to `yum upgrade ppas-xdb*` -See [Upgrading from a Replication Server RPM Package Installation](../10_appendix/02_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/) for details. +See [Upgrading from a Replication Server RPM Package Installation](../10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/) for details. ## Updating a Bitrock installer installation diff --git a/product_docs/docs/eprs/7/03_installation/03a_updating_linux_installation.mdx b/product_docs/docs/eprs/7/03_installation/03a_updating_linux_installation.mdx index 1995f52d471..cbd75e96f97 100644 --- a/product_docs/docs/eprs/7/03_installation/03a_updating_linux_installation.mdx +++ b/product_docs/docs/eprs/7/03_installation/03a_updating_linux_installation.mdx @@ -10,4 +10,4 @@ If you have an existing Replication Server installed on Linux, you can use yum t `yum upgrade ppas-xdb*` -See [Upgrading from a Replication Server RPM Package Installation](../10_appendix/02_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/) for details. +See [Upgrading from a Replication Server RPM Package Installation](../10_appendix/01_upgrading_to_xdb6_2/03_upgrading_with_xdb_rpm_package/) for details. diff --git a/product_docs/docs/eprs/7/03_installation/index.mdx b/product_docs/docs/eprs/7/03_installation/index.mdx index 5cb915e66f6..1a7b6798468 100644 --- a/product_docs/docs/eprs/7/03_installation/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/index.mdx @@ -13,7 +13,7 @@ The Replication Server product is also available as a native package in which ca An interactive installer for Windows is available from the [Downloads](https://www.enterprisedb.com/software-downloads-postgres#replication-server) page. !!! Note - If you have an older version of Replication Server and existing replication systems, review Section [Upgrading to Replication Server 7.0](../10_appendix/02_upgrading_to_xdb6_2/#upgrading_to_xdb6_2) before installing Replication Server. + If you have an older version of Replication Server and existing replication systems, review Section [Upgrading to Replication Server 7.0](../10_appendix/01_upgrading_to_xdb6_2/#upgrading_to_xdb6_2) before installing Replication Server. If you later decide you wish to remove Replication Server from your system see [Uninstalling Replication Server](06_uninstalling_xdb_replication_server). diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx index ed8297d82be..152428fe14c 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/04_preparing_pub_database.mdx @@ -325,7 +325,7 @@ When creating the publication database definition, you must specify a database u - The database user can connect to the publication database. - The database user has superuser privileges. Superuser privileges are required because the database configuration parameter `session_replication_role` is altered by the database user to replica for snapshot operations involving replication of the control schema from one publication database to another. -- The database user must have the ability to modify the system catalog tables to disable foreign key constraints on the control schema tables for snapshot operations involving replication of the control schema from one publication database to another. See [Disabling foreign key constraints for snapshot replications](../../10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement. +- The database user must have the ability to modify the system catalog tables to disable foreign key constraints on the control schema tables for snapshot operations involving replication of the control schema from one publication database to another. See [Disabling foreign key constraints for snapshot replications](../../10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement. **Step 1:** Create a database superuser for the publication database user. The publication database user name must have a password, and it must have the ability to create a database session. The publication database user becomes the owner of the control schema objects created in the publication database to track, control, and record the replication process and history. diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx index 69ecbd0ff43..423b55d7f90 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/05_preparing_sub_database.mdx @@ -23,7 +23,7 @@ When creating the subscription database definition, enter the subscription datab The subscription database user must also be able to run the `TRUNCATE` command on the subscription tables. This requires the following: - Superuser privileges. -- The ability to modify the system catalog tables to disable foreign key constraints on subscription tables. See [Disabling foreign key constraints for snapshot replications](../../10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement. +- The ability to modify the system catalog tables to disable foreign key constraints on subscription tables. See [Disabling foreign key constraints for snapshot replications](../../10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement. When choosing the subscription database user name, you can either: diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx index 08784415280..4d9db10fd4c 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/06_verifying_host_accessibility.mdx @@ -58,7 +58,7 @@ The loopback address works as long as the communicating components are on the sa **For Linux only:** You might need to modify the `/etc/hosts` file so that a host’s network IP address is associated with the host’s name. -(For an alternative to modifying the `/etc/hosts` file, see [Assigning an IP Address for remote method invocation](../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi/#assign_ip_adress_for_rmi).) +(For an alternative to modifying the `/etc/hosts` file, see [Assigning an IP Address for remote method invocation](../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi/#assign_ip_adress_for_rmi).) The default configuration on Linux systems associates the host name with the loopback address in the `/etc/hosts` file as shown by the following example: diff --git a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx index 881385ccca9..cd54653cb71 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/02_creating_publication/01_registering_publication_server.mdx @@ -59,7 +59,7 @@ Similarly, use the `stop` option to stop the publication server. **For Windows only:** Open **Control Panel > System and Security > Administrative Tools > Services**. The publication server runs as a service named Publication Service for Replication Server. Use the **Start** or **Restart** link for the service. -If the publication server doesn't start, see [Publication and subscription server startup failures](../../10_appendix/03_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures). +If the publication server doesn't start, see [Publication and subscription server startup failures](../../10_appendix/02_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures). **Step 2:** Register the publication server. Open the Replication Server console from the system’s application menu. For Replication Server installed from an Replication Server RPM package, invoke the script `XDB_HOME/bin/runRepConsole.sh` to start the Replication Server console. diff --git a/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx b/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx index 70b47c82116..410e54efd0f 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/03_creating_subscription/01_registering_subscription_server.mdx @@ -17,7 +17,7 @@ It's important that you record the login information for the subscription server **For Windows only:** Open **Control Panel > System and Security > Administrative Tools > Services**. Use the **Start** or **Restart** link for the service named Subscription Service for Replication Server. -If the subscription server doesn't start, see [Publication and subscription server startup failures](../../10_appendix/03_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures). +If the subscription server doesn't start, see [Publication and subscription server startup failures](../../10_appendix/02_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures). **Step 2:** Register the subscription server. Open the Replication Server console from the system’s application menu. For Replication Server installed from a Replication Server RPM package, start the Replication Server console by invoking the script `XDB_HOME/bin/runRepConsole.sh`. diff --git a/product_docs/docs/eprs/7/05_smr_operation/06_performing_switchover.mdx b/product_docs/docs/eprs/7/05_smr_operation/06_performing_switchover.mdx index aa31780b72a..2701d64f279 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/06_performing_switchover.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/06_performing_switchover.mdx @@ -160,7 +160,7 @@ Alternatively, you can delete the replication slot from the database server that SELECT pg_drop_replication_slot('xdb_47919_5'); ``` -See [Dropping replication slots for log-based synchronization replication](../10_appendix/03_resolving_problems/04_troubleshooting_areas/#drop_replication_slots_for_log_based) for more information on deleting the replication slot if the `pg_drop_replication_slot` function isn't successful. If you switch the databases back to their original roles, you have to recreate the replication slot on the publication database server as described in this step. +See [Dropping replication slots for log-based synchronization replication](../10_appendix/02_resolving_problems/04_troubleshooting_areas/#drop_replication_slots_for_log_based) for more information on deleting the replication slot if the `pg_drop_replication_slot` function isn't successful. If you switch the databases back to their original roles, you have to recreate the replication slot on the publication database server as described in this step. 1. The controlled switchover is now complete. Start the publication server and the subscription server. diff --git a/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/02_optimize_sync_replication/index.mdx b/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/02_optimize_sync_replication/index.mdx index d4e3e5b2db8..6f603c72d69 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/02_optimize_sync_replication/index.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/02_optimize_sync_replication/index.mdx @@ -8,7 +8,7 @@ You can set various configuration options for improving synchronization replicat These options apply only to the publication server. You set them in the publication server configuration file. -For configuration options that apply to publication databases configured with the log-based method of synchronization replication, see [Specifying a custom URL for an Oracle JDBC connection](../../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc/#specify_custom_url_for_oracle_jdbc). +For configuration options that apply to publication databases configured with the log-based method of synchronization replication, see [Specifying a custom URL for an Oracle JDBC connection](../../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/05_specify_custom_url_for_oracle_jdbc/#specify_custom_url_for_oracle_jdbc).
diff --git a/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/index.mdx b/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/index.mdx index ccadfcacfa3..2e1d1cd2378 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/index.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/08_optimizing_performance/index.mdx @@ -6,7 +6,7 @@ title: "Optimizing performance" Once you're familiar with setting up and managing your replication system, you mmight look for ways to optimize the performance of replications. Various publication server and subscription server configuration options are available for improving the performance of snapshot and synchronization replications. -Set the publication server and subscription server configuration options in the publication server and subscription server configuration files. See [Publication and subscription server configuration options](../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/#publications_and_subscriptions_server_conf_options) for a detailed explanation of how to set the configuration options in these files. +Set the publication server and subscription server configuration options in the publication server and subscription server configuration files. See [Publication and subscription server configuration options](../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/#publications_and_subscriptions_server_conf_options) for a detailed explanation of how to set the configuration options in these files. !!! Note Most of these configuration options also apply to multi-master replication systems. Options that apply to multi-master replication systems are those that apply to the publication server. They aren't specific to a database product other than Postgres (such as an Oracle feature). diff --git a/product_docs/docs/eprs/7/06_mmr_operation/01_pre_steps.mdx b/product_docs/docs/eprs/7/06_mmr_operation/01_pre_steps.mdx index a20aed3860d..ea49acd8600 100644 --- a/product_docs/docs/eprs/7/06_mmr_operation/01_pre_steps.mdx +++ b/product_docs/docs/eprs/7/06_mmr_operation/01_pre_steps.mdx @@ -37,7 +37,7 @@ When creating the publication database definition for the primary definition nod - The database user can connect to the primary definition node. - The database user has superuser privileges. Superuser privileges are required because the database configuration parameter `session_replication_role` is modified by the database user when the primary definition node receives updates from other primary nodes during a synchronization replication. The database user temporarily changes `session_replication_role` to `replica` to prevent the triggers on the publication tables from activating. This session change also occurs for snapshot operations involving replication of the control schema from one publication database to another. -- The database user must be able to modify the system catalog tables. This ability is needed to disable foreign key constraints on the publication tables for snapshots targeted to the publication. It is also needed for the control schema tables for snapshot operations involving the replication of the control schema from one publication database to another. (See [Disabling foreign key constraints for snapshot replications](../10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement.) +- The database user must be able to modify the system catalog tables. This ability is needed to disable foreign key constraints on the publication tables for snapshots targeted to the publication. It is also needed for the control schema tables for snapshot operations involving the replication of the control schema from one publication database to another. (See [Disabling foreign key constraints for snapshot replications](../10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement.) The examples we use are based on the following primary definition node: @@ -72,8 +72,8 @@ When creating the publication database definition for an additional primary node - The database user can connect to the primary node. - The database user has superuser privileges. Superuser privileges are required because the database user modfies the database configuration parameter `session_replication_role` when the primary node receives updates from other primary nodes during a synchronization replication. The database user temporarily changes `session_replication_role` to `replica` to prevent the triggers on the publication tables from activating. This session change also occurs for snapshot operations involving replication of the control schema from one publication database to another. -- The database user must be able to modify the system catalog tables. This abiity is needed to disable foreign key constraints on the publication tables for snapshots targeted to the publication. It is also needed for the control schema tables for snapshot operations involving the replication of the control schema from one publication database to another. See [Disabling foreign key constraints for snapshot replications](../10_appendix/04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement. -- If the added primary node resides on a different database server instance (that is, on a different host or port number) from the primary definition node, then use the same database user name for this additional primary node as used for the primary definition node. This isn't necessary if the publication server configuration option `skipTablePrivileges` is changed from its default value of false to true. See [Skipping grants of table-level user privileges on MMR target tables](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr/#skipping_grants_of_table_level_user_privileges_on_mmr) for information on `skipTablePrivileges`. +- The database user must be able to modify the system catalog tables. This abiity is needed to disable foreign key constraints on the publication tables for snapshots targeted to the publication. It is also needed for the control schema tables for snapshot operations involving the replication of the control schema from one publication database to another. See [Disabling foreign key constraints for snapshot replications](../10_appendix/03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication) for more information on this requirement. +- If the added primary node resides on a different database server instance (that is, on a different host or port number) from the primary definition node, then use the same database user name for this additional primary node as used for the primary definition node. This isn't necessary if the publication server configuration option `skipTablePrivileges` is changed from its default value of false to true. See [Skipping grants of table-level user privileges on MMR target tables](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/13_skipping_grants_of_table_level_user_privileges_on_mmr/#skipping_grants_of_table_level_user_privileges_on_mmr) for information on `skipTablePrivileges`. Two possible options are available with respect to how to create the publication tables in the primary node: diff --git a/product_docs/docs/eprs/7/06_mmr_operation/12_optimizing_performance_mmr.mdx b/product_docs/docs/eprs/7/06_mmr_operation/12_optimizing_performance_mmr.mdx index d125b4226f4..f309317410a 100644 --- a/product_docs/docs/eprs/7/06_mmr_operation/12_optimizing_performance_mmr.mdx +++ b/product_docs/docs/eprs/7/06_mmr_operation/12_optimizing_performance_mmr.mdx @@ -8,9 +8,9 @@ Publication server configuration options are available to optimize the performan Almost all publication server performance-related configuration options for single-master replication systems apply to multi-master replication systems (except when they are database-product specific, such as for Oracle). -Set the publication server configuration options in the publication server configuration file. See [Publication and subscription server configuration options](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/#publications_and_subscriptions_server_conf_options) for a detailed explanation of how to set the configuration options in this file. +Set the publication server configuration options in the publication server configuration file. See [Publication and subscription server configuration options](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/#publications_and_subscriptions_server_conf_options) for a detailed explanation of how to set the configuration options in this file. -In addition, for configuration options that apply specifically to publication databases configured with the log-based method of synchronization replication, see [Log-based method of synchronization options](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options/#log_based_sync_options). +In addition, for configuration options that apply specifically to publication databases configured with the log-based method of synchronization replication, see [Log-based method of synchronization options](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/15_log_based_sync_options/#log_based_sync_options). The following are some other configuration options that apply only to multi-master replication systems. diff --git a/product_docs/docs/eprs/7/07_common_operations/02_creating_schedule.mdx b/product_docs/docs/eprs/7/07_common_operations/02_creating_schedule.mdx index dcb668290bc..455593195af 100644 --- a/product_docs/docs/eprs/7/07_common_operations/02_creating_schedule.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/02_creating_schedule.mdx @@ -49,7 +49,7 @@ For snapshot replications, skipped scheduled replications present no problem sin - **Daily**. Schedules replication to run once a day at the time you choose. Select this option if the target tables need to be refreshed daily. - **Weekly**. Schedules replication to run once a day at the time you choose, but only on the specific days of the week you choose. Select this option if you need more flexibility than a daily schedule, and the target tables don't have to be refreshed every day. - **Monthly**. Schedules replication to run one day per month on the day of the month and time you choose, but only in the months you choose. Select this option if updates to the source tables aren't very frequent, and the target tables can be out of date by a month or more. The **Monthly** option allows you to schedule replication for as often as once a month or as infrequently as once a year. - - **Cron Expression**. Provides additional flexibility for specifying a schedule. See [Writing a cron expression](../10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. + - **Cron Expression**. Provides additional flexibility for specifying a schedule. See [Writing a cron expression](../10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. 1. Select **Next**. diff --git a/product_docs/docs/eprs/7/07_common_operations/04_view_replication_history.mdx b/product_docs/docs/eprs/7/07_common_operations/04_view_replication_history.mdx index fe67101af65..4485f8a8790 100644 --- a/product_docs/docs/eprs/7/07_common_operations/04_view_replication_history.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/04_view_replication_history.mdx @@ -44,7 +44,7 @@ The next time the **Replication History** tab refreshes, only the replications w When the publication server starts running again, zero transaction count replication records appear on the **Replication History** tab as zero transaction count replications occur. -To permanently store zero transaction count replication records to disk, set the publication server configuration option `persistZeroTxRepEvent` to `true`. See [Replacing null characters](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters/#replacing_null_characters) for more information. +To permanently store zero transaction count replication records to disk, set the publication server configuration option `persistZeroTxRepEvent` to `true`. See [Replacing null characters](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters/#replacing_null_characters) for more information. diff --git a/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx b/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx index 30138d57980..0779d7a435b 100644 --- a/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/05_managing_history.mdx @@ -25,7 +25,7 @@ You can set a preference for each publication database definition to specify the Replication history isn't deleted by scheduling shadow table history cleanup. New publication database definitions include a scheduled default setting of every Sunday at 12:00 a.m. for shadow table history cleanup. !!! Note - A configuration option is available to force shadow table history cleanup after every synchronization replication. See [Forcing immediate shadow table cleanup](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup/#forcing_shadow_table_cleanup) for information on this option. + A configuration option is available to force shadow table history cleanup after every synchronization replication. See [Forcing immediate shadow table cleanup](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup/#forcing_shadow_table_cleanup) for information on this option. !!! Note The cleanup of certain processed rows in the shadow tables might be delayed beyond the next scheduled cleanup. These roles are eventually removed in later cleanup events. @@ -47,7 +47,7 @@ By contrast, assume the publication server is running on a host in New York alon **For Postgres only:** The publication server must be running for the cleanup job to run on a Postgres publication database. !!! Note - An alternative to using the Quartz scheduler when Postgres is the publication database is to use pgAgent job scheduling instead. See [Using pgAgent job scheduling](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling/#using_pgagent_job_scheduling) for information on how to use pgAgent job scheduling and its advantages. + An alternative to using the Quartz scheduler when Postgres is the publication database is to use pgAgent job scheduling instead. See [Using pgAgent job scheduling](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/08_using_pgagent_job_scheduling/#using_pgagent_job_scheduling) for information on how to use pgAgent job scheduling and its advantages. To change the default setting: @@ -64,10 +64,10 @@ To change the default setting: - **Every number of minutes/hours.** Schedules shadow table history cleanup to run continuously at an interval in either minutes or hours that you specify. Select this option for huge volumes of updates to the publication tables during the course of the day, every day. - **Every Day at hour of day.** Schedules shadow table history cleanup to run once a day at the hour you choose. Select this option if updates to the publication tables are frequent enough to require more than once-a-week cleanup but aren't needed more than once a day. - **Every selected day of week at hour of day.** Schedules shadow table history cleanup to run once a week on the day and at the hour you choose. Select this option if updates to the publication tables are infrequent and you don't want to run cleanup manually. - - **Cron Expression.** Provides more flexibility for specifying a schedule. See [Writing a cron expression](../10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp). + - **Cron Expression.** Provides more flexibility for specifying a schedule. See [Writing a cron expression](../10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp). !!! Note - A configuration option is available to force shadow table history cleanup after every synchronization replication. See [Forcing immediate shadow table cleanup](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup/#forcing_shadow_table_cleanup) for information on this option. + A configuration option is available to force shadow table history cleanup after every synchronization replication. See [Forcing immediate shadow table cleanup](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/09_forcing_shadow_table_cleanup/#forcing_shadow_table_cleanup) for information on this option. 1. To accept the schedule, select **OK**. @@ -156,4 +156,4 @@ Publication server configuration option `historyCleanupDaysThreshold` enables yo To clean up all completed event and replication history, set `historyCleanupDaysThreshold` to a value of `0`, and then restart the publication server. The cleanup occurs during the next scheduled 12 a.m. cleanup. -See [Setting event history cleanup threshold](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup/#setting_event_history_cleanup) for the `historyCleanupDaysThreshold` option. +See [Setting event history cleanup threshold](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/10_setting_event_history_cleanup/#setting_event_history_cleanup) for the `historyCleanupDaysThreshold` option. diff --git a/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx b/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx index b2f25d346bc..70d5b46b2fa 100644 --- a/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/08_replicating_ddl_changes/01_ddl_change_replication.mdx @@ -11,7 +11,7 @@ If there's a backlog of pending transactions, we recommend that you perform an e Perform DDL change replication when the OLTP rate is very low (near zero). !!! Note - You can turn off exclusive acquisition of each target table during the DDL change replication process by setting `ddlChangeTableLock` to `false`. However, make this change only when there are no write transactions taking place against the target table. Otherwise, transactions might not be recorded by the replication system. See [DDL change replication table locking](../../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking/#ddl_change_replication_table_locking) for more information on the `ddlChangeTableLock` configuration option. + You can turn off exclusive acquisition of each target table during the DDL change replication process by setting `ddlChangeTableLock` to `false`. However, make this change only when there are no write transactions taking place against the target table. Otherwise, transactions might not be recorded by the replication system. See [DDL change replication table locking](../../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/11_ddl_change_replication_table_locking/#ddl_change_replication_table_locking) for more information on the `ddlChangeTableLock` configuration option. The following is the series of steps that occur during the DDL change replication process. diff --git a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx index 01100eccd6a..1ba4c57d66b 100644 --- a/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx +++ b/product_docs/docs/eprs/7/07_common_operations/11_using_ssl_connections.mdx @@ -341,7 +341,7 @@ total 20 **Step 5:** Generate the encrypted form of the new password specified in the preceding step. -You must specify the encrypted password with the `sslTrustStorePassword` configuration option of the publication server configuration file for publication server SSL connections and the subscription server configuration file for subscription server SSL connections. (See [Publication and subscription server configuration options](../10_appendix/04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/#publications_and_subscriptions_server_conf_options) for information on the publication server and subscription server configuration files.) +You must specify the encrypted password with the `sslTrustStorePassword` configuration option of the publication server configuration file for publication server SSL connections and the subscription server configuration file for subscription server SSL connections. (See [Publication and subscription server configuration options](../10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/#publications_and_subscriptions_server_conf_options) for information on the publication server and subscription server configuration files.) Encrypt the password using the Replication Server CLI `encrypt` command. The following example shows this process encrypting the password contained in file `infile`. diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/14_creating_publication_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/14_creating_publication_cli.mdx index 08c47d37e06..e1e9dbeedf4 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/14_creating_publication_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/14_creating_publication_cli.mdx @@ -38,7 +38,7 @@ The `createpub` command adds a publication subordinate to the publication databa See [Adding a publication](../../05_smr_operation/02_creating_publication/03_adding_publication/#adding_publication) for more information on creating a publication for a single-master replication system. See [Adding a publication](../../06_mmr_operation/02_creating_publication_mmr/#add_pub_mmr) for a multi-master replication system. !!! Note - The schema names, table names, and view names that you supply as values for the tables and views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. + The schema names, table names, and view names that you supply as values for the tables and views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. ## Parameters diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx index f2f3c9c0708..57a1a58bea2 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx @@ -43,7 +43,7 @@ The `addtablesintopub` command updates an existing publication identified by `pu The `views` parameter applies only for a snapshot-only publication. It's ignored if the publication isn't defined as snapshot-only. See [Adding tables to a publication](../../07_common_operations/06_managing_publication/03_updating_pub/#add_tables_to_pub) for more information. !!! Note - The schema names, table names, and view names that you supply as values for the tables and views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. + The schema names, table names, and view names that you supply as values for the tables and views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. !!! Note diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/19_removing_tables_from_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/19_removing_tables_from_publication.mdx index c5f81069573..b784bc24d73 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/19_removing_tables_from_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/19_removing_tables_from_publication.mdx @@ -18,7 +18,7 @@ The `removetablesfrompub` command removes tables from a publication. See [Removing tables from a publication](../../07_common_operations/06_managing_publication/03_updating_pub/#remove_tables_from_pub) for more information. !!! Note - The schema names, table names, and view names that you supply as values for the tables and views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must use uppercase letters for Oracle names (for example, `EDB.DEPT`) and lowercase letters for EDB Postgres Advanced Server names(for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. + The schema names, table names, and view names that you supply as values for the tables and views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must use uppercase letters for Oracle names (for example, `EDB.DEPT`) and lowercase letters for EDB Postgres Advanced Server names(for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. ## Parameters diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx index ec8820d71a6..742027dd218 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/20_adding_tablefilters_to_publication.mdx @@ -28,7 +28,7 @@ If the filter rule isn't enabled on a target subscription or non-MDN node, then See [Table filters](../../02_overview/02_replication_concepts_and_definitions/13_table_filters/#table_filters) for more information. !!! Note - The schema names and table or view names that you supply as values for the tables or views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted edentifiers and default case translation](../../10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. + The schema names and table or view names that you supply as values for the tables or views parameters are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted edentifiers and default case translation](../../10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. ## Parameters diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/23_print_conflict_resolution_strategy.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/23_print_conflict_resolution_strategy.mdx index 068135930dd..8b775a1b6fb 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/23_print_conflict_resolution_strategy.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/23_print_conflict_resolution_strategy.mdx @@ -17,7 +17,7 @@ title: "Printing the conflict resolution strategy (printconfresolutionstrategy)" See [Conflict resolution](../../06_mmr_operation/06_conflict_resolution/#conflict_resolution) for more information. !!! Note - The schema name and table or view name that you supply as values for the table parameter are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. + The schema name and table or view name that you supply as values for the table parameter are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. ## Parameters diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/24_updating_conflict_resolution_strategy.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/24_updating_conflict_resolution_strategy.mdx index afa43cc59c3..2b5efe0da9a 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/24_updating_conflict_resolution_strategy.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/24_updating_conflict_resolution_strategy.mdx @@ -20,7 +20,7 @@ title: "Updating the conflict resolution strategy (updateconfresolutionstrategy) See [Updating the conflict resolution options](../../06_mmr_operation/08_update_conflict_resolution_options/#update_conflict_resolution_options) for more information. !!! Note - The schema name and table or view name that you supply as values for the table parameter are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/04_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. + The schema name and table or view name that you supply as values for the table parameter are case sensitive. Unless quoted identifiers were used to build the database objects, you must enter Oracle names using uppercase letters (for example, `EDB.DEPT`) and EDB Postgres Advanced Server names in lowercase letters (for example `edb.dept`). See [Quoted identifiers and default case translation](../../10_appendix/03_miscellaneous_xdb_processing_topics/05_quoted_identifiers/#quoted_identifiers) for more information. ## Parameters diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/43_configure_smr_schedule.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/43_configure_smr_schedule.mdx index 3bebe190695..54ee9cc11b3 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/43_configure_smr_schedule.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/43_configure_smr_schedule.mdx @@ -68,7 +68,7 @@ The day of the month. Specify an integer 1 or greater up to and including the nu `cron_expression` -A cron expression. See [Writing a cron expression](../../10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. +A cron expression. See [Writing a cron expression](../../10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. ## Examples diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/44_configure_mmr_schedule.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/44_configure_mmr_schedule.mdx index 9e49e46ee3f..d95295fd34c 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/44_configure_mmr_schedule.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/44_configure_mmr_schedule.mdx @@ -74,7 +74,7 @@ The day of the month. Specify an integer 1 or greater up to and including the nu `cron_expression` -A cron expression. See [Writing a cron expression](../../10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. +A cron expression. See [Writing a cron expression](../../10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. ## Examples diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/48_schedule_shadow_table_history_clean.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/48_schedule_shadow_table_history_clean.mdx index 808fd62ef36..e34c6eb6647 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/48_schedule_shadow_table_history_clean.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/48_schedule_shadow_table_history_clean.mdx @@ -60,7 +60,7 @@ The day of the week. Specify any of the following values: `SUNDAY`, `MONDAY`, `T `cron_expression` -A cron expression. See [Writing a cron expression](../../10_appendix/04_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. +A cron expression. See [Writing a cron expression](../../10_appendix/03_miscellaneous_xdb_processing_topics/03_writing_cron_exp/#writing_cron_exp) for details. ## Examples diff --git a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx index acec13906ac..fca3d6a9a86 100644 --- a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx @@ -36,7 +36,7 @@ You can upgrade to Replication Server 7.0 using the graphical user interface ins 1. Restart the publication server and the subscription server. See [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server)). -1. Check the publication server and subscription server log files to verify that no errors occurred (see [Publication and subscription server startup failures](../03_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures)). +1. Check the publication server and subscription server log files to verify that no errors occurred (see [Publication and subscription server startup failures](../02_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures)). 1. Adjust the publication server and subscription server port numbers if necessary. diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx index 0fce5c9da49..b129ef6b57e 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/01_error_messages.mdx @@ -34,7 +34,7 @@ You can create only one publication database definition for any given database. **Resolution** -Occurs whenever a Java RMI connection can't be made to the publication server, the subscription server, or a database server. Can occur when registering a publication or subscription server, adding a publication database or a subscription database, or identifying the publication server for a new subscription. Verify you that have entered the correct host IP address and port number of the server. Verify the server is running (see [Starting the publication server or subscription server](04_troubleshooting_areas/#start_pub_or_sub_server)). If the server is running on Linux, verify that in the `/etc/hosts` file the host name is mapped to the correct network IP address, which matches the IP address returned by the Linux `/sbin/ifconfig` command and also matches the IP address you entered in the **Host** field of the dialog box. Alternatively, instead of modifying the `/etc/hosts` file, set configuration option `java.rmi.server.hostname` to the IP address of the publication or subscription server (see [Assigning an IP address for remote method invocation](../04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi/#assign_ip_adress_for_rmi) Don't use the loopback address `127.\ *x*.\ *x*.\ *x*` for this entry. +Occurs whenever a Java RMI connection can't be made to the publication server, the subscription server, or a database server. Can occur when registering a publication or subscription server, adding a publication database or a subscription database, or identifying the publication server for a new subscription. Verify you that have entered the correct host IP address and port number of the server. Verify the server is running (see [Starting the publication server or subscription server](04_troubleshooting_areas/#start_pub_or_sub_server)). If the server is running on Linux, verify that in the `/etc/hosts` file the host name is mapped to the correct network IP address, which matches the IP address returned by the Linux `/sbin/ifconfig` command and also matches the IP address you entered in the **Host** field of the dialog box. Alternatively, instead of modifying the `/etc/hosts` file, set configuration option `java.rmi.server.hostname` to the IP address of the publication or subscription server (see [Assigning an IP address for remote method invocation](../03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi/#assign_ip_adress_for_rmi) Don't use the loopback address `127.\ *x*.\ *x*.\ *x*` for this entry. **Problem** @@ -426,7 +426,7 @@ Verify that the publication server is running. See [Starting the publication ser **Resolution** -Might be caused by characters in the publication data that are illegal for the character set of the subscription database. Check the snapshot replication failure log file or the database server log file. See [Replacing null characters](../04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters/#replacing_null_characters). +Might be caused by characters in the publication data that are illegal for the character set of the subscription database. Check the snapshot replication failure log file or the database server log file. See [Replacing null characters](../03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/02_replacing_null_characters/#replacing_null_characters). **Problem** @@ -574,7 +574,7 @@ Occurs when attempting an operation such as performing synchronization replicati `DB-42501: com.edb.util.PSQLException: ERROR: permission denied for relation pg_class.` -**Resolution** Occurs when attempting to create an MMR publication database definition and the publication server can't create the control schema objects in the new publication database. This typically results when creating a second publication database definition and the publication server can't copy by snapshot the control schema objects from the controller database to the new publication database. The publication database user of the new publication database must be a superuser. In addition, in system catalog table `pg_catalog.pg_authid`, column `rolcatupdate` must be set to true for this superuser. See [Disabling foreign key constraints for snapshot replications](../04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication). +**Resolution** Occurs when attempting to create an MMR publication database definition and the publication server can't create the control schema objects in the new publication database. This typically results when creating a second publication database definition and the publication server can't copy by snapshot the control schema objects from the controller database to the new publication database. The publication database user of the new publication database must be a superuser. In addition, in system catalog table `pg_catalog.pg_authid`, column `rolcatupdate` must be set to true for this superuser. See [Disabling foreign key constraints for snapshot replications](../03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication). **Problem** @@ -618,7 +618,7 @@ The subscription server can't create a subscription table definition in the inte **Resolution** -Occurs when attempting to create an SMR publication database definition and the publication server can't create the control schema objects in the new publication database. This typically results when creating a second publication database definition and the publication server can't copy by snapshot the control schema objects from the controller database to the new publication database. The publication database user of the new publication database must be a superuser. In addition, in system catalog table `pg_catalog.pg_authid`, column `rolcatupdate` must be set to `true` for this superuser. See [Disabling foreign key constraints for snapshot replications](../04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication). +Occurs when attempting to create an SMR publication database definition and the publication server can't create the control schema objects in the new publication database. This typically results when creating a second publication database definition and the publication server can't copy by snapshot the control schema objects from the controller database to the new publication database. The publication database user of the new publication database must be a superuser. In addition, in system catalog table `pg_catalog.pg_authid`, column `rolcatupdate` must be set to `true` for this superuser. See [Disabling foreign key constraints for snapshot replications](../03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication). **Problem** @@ -626,7 +626,7 @@ Occurs when attempting to create an SMR publication database definition and the **Resolution** -Occurs when attempting a snapshot replication. The database user of the database receiving the snapshot must be a superuser. In addition, in system catalog table `pg_catalog.pg_authid`, column `rolcatupdate` must be set to `true` for this superuser. See [Disabling foreign key constraints for snapshot replications](../04_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication). +Occurs when attempting a snapshot replication. The database user of the database receiving the snapshot must be a superuser. In addition, in system catalog table `pg_catalog.pg_authid`, column `rolcatupdate` must be set to `true` for this superuser. See [Disabling foreign key constraints for snapshot replications](../03_miscellaneous_xdb_processing_topics/04_disable_foreign_key_constraints_for_snapshot_replication/#disable_foreign_key_constraints_for_snapshot_replication). **Problem** diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx index b0b614584c4..773c1360389 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/02_where_to_look_for_errors.mdx @@ -28,7 +28,7 @@ View the log file found in the following path: `POSTGRES_HOME` is the home directory of the Windows postgres account (enterprisedb account for EDB Postgres Advanced Server installed in Oracle-compatible configuration mode). The specific location of `POSTGRES_HOME` depends on your version of Windows. The Replication Server version number is represented by x.x. -See [Controlling logging level, log file sizes, and rotation count](../04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level/#controlling_logging_level) for more information on setting log file options. +See [Controlling logging level, log file sizes, and rotation count](../03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level/#controlling_logging_level) for more information on setting log file options. ## Synchronization replication failures @@ -52,12 +52,12 @@ View the publication server and subscription server log files `pubserver.log[.n] `POSTGRES_HOME\.enterprisedb\xdb\x.x` -`[.n]` is an optional integer suffix whose presence depends on the `logging.file.count` configuration option described in [Controlling logging level, log file sizes, and rotation count](../04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level/#controlling_logging_level). +`[.n]` is an optional integer suffix whose presence depends on the `logging.file.count` configuration option described in [Controlling logging level, log file sizes, and rotation count](../03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level/#controlling_logging_level). `POSTGRES_HOME` is the home directory of the Windows postgres account (enterprisedb account for EDB Postgres Advanced Server installed in Oracle-compatible configuration mode). The specific location of `POSTGRES_HOME` depends on your version of Windows. The Replication Server version number is represented by `x.x`. !!! Note - You can control the severity level of messages logged in these files using a configuration option. See [Controlling logging level, log file sizes, and rotation count](../04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level/#controlling_logging_level). + You can control the severity level of messages logged in these files using a configuration option. See [Controlling logging level, log file sizes, and rotation count](../03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level/#controlling_logging_level). **For Linux only:** View the publication service and subscription service startup log files `edb-xdbpubserver.log` and `edb-xdbsubserver.log` as well as the service script log files `edb-xdbpubserver_script.log` and `edb-xdbsubserver_script.log` in directories `/var/log/edb/xdbpubserver` and `/var/log/edb/xdbsubserver`. These log files contain the output from the scripts used to start the publication server and subscription server and can typically be used to confirm the port number on which the publication and subscription servers were started. diff --git a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx index 970c1b2d59a..4ed418c82f3 100644 --- a/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx +++ b/product_docs/docs/eprs/7/10_appendix/02_resolving_problems/03_common_problems_checklist.mdx @@ -47,4 +47,4 @@ Use the following checklist to verify that the proper configuration steps were f For a Postgres subscription database, verify that the subscription database user is a superuser and has the privilege to modify `pg_catalog` tables. See [Preparing the Subscription Database](../../05_smr_operation/01_prerequisites/05_preparing_sub_database/#preparing_sub_database). -1. **For Linux only:** Verify that the network IP address returned by the `/sbin/ifconfig` command either matches the IP address associated with the host name in the `/etc/hosts` file (see [Network IP addresses](../../05_smr_operation/01_prerequisites/06_verifying_host_accessibility/#network_ip)) or matches the IP address specified with the `java.rmi.server.hostname` configuration option in the publication and subscription server configuration files (see [Assigning an IP address for remote method invocation](../04_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi/#assign_ip_adress_for_rmi)). +1. **For Linux only:** Verify that the network IP address returned by the `/sbin/ifconfig` command either matches the IP address associated with the host name in the `/etc/hosts` file (see [Network IP addresses](../../05_smr_operation/01_prerequisites/06_verifying_host_accessibility/#network_ip)) or matches the IP address specified with the `java.rmi.server.hostname` configuration option in the publication and subscription server configuration files (see [Assigning an IP address for remote method invocation](../03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/07_assign_ip_adress_for_rmi/#assign_ip_adress_for_rmi)). diff --git a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx index f162830e152..6bcdf7e06b6 100644 --- a/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx +++ b/product_docs/docs/eprs/7/10_appendix/03_miscellaneous_xdb_processing_topics/01_publications_and_subscriptions_server_conf_options/01_controlling_logging_level.mdx @@ -11,7 +11,7 @@ redirects: The following options control various aspects of message logging in the publication server log file, the subscription server log file, and the Migration Toolkit log file. -See [Publication and subscription server startup failures](../../03_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures) and [Snapshot replication failures](../../03_resolving_problems/02_where_to_look_for_errors/#snapshot_replication_failures) for more information. +See [Publication and subscription server startup failures](../../02_resolving_problems/02_where_to_look_for_errors/#pub_and_sub_startup_failures) and [Snapshot replication failures](../../02_resolving_problems/02_where_to_look_for_errors/#snapshot_replication_failures) for more information. `logging.level` From a96003e7925381c0a4d01e959cb7a9b4411a98d7 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 1 Nov 2022 09:36:19 -0400 Subject: [PATCH 20/50] release notes shell --- .../eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx | 9 +++++++++ product_docs/docs/eprs/7/eprs_rel_notes/index.mdx | 1 + 2 files changed, 10 insertions(+) create mode 100644 product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx new file mode 100644 index 00000000000..4224863dee5 --- /dev/null +++ b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx @@ -0,0 +1,9 @@ +--- +title: "Version 7.3.0" +--- + + +New features, enhancements, bug fixes, and other changes in Replication Server 7.3.0 include the following: + +| Type | Description | +| ------- |------------ | \ No newline at end of file diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index 902965287b9..a7534726003 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -9,6 +9,7 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | | -------------------------------- | ------------ | +| [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 04 | | [7.2.1](16_eprs_rel_notes_7.2.1) | 2022 Jul 25 | | [7.2.0](17_eprs_rel_notes_7.2.0) | 2022 Jun 24 | | [7.1.0](18_eprs_rel_notes_7.1.0) | 2022 Mar 21 | From e30f89bac3cf30d030c487444c4e9370addd4542 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 1 Nov 2022 11:37:03 -0400 Subject: [PATCH 21/50] deleted "with regular expression" --- .../03_xdb_cli_commands/18_adding_tables_to_publication.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx index 57a1a58bea2..55084edb365 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/18_adding_tables_to_publication.mdx @@ -47,7 +47,7 @@ The `views` parameter applies only for a snapshot-only publication. It's ignored !!! Note - Column mappings are applied when you create subscriptions. If you add a table which qualifies for column mapping with regular expression to the related publication, then Replication Server applies the column mapping for the newly added table. For more information on column mappings, see [Creating a subscription](/36_creating_subscription_cli). + Column mappings are applied when you create subscriptions. If you add a table which qualifies for column mapping to the related publication, then Replication Server applies the column mapping for the newly added table. For more information on column mappings, see [Creating a subscription](/36_creating_subscription_cli). !!! ## Parameters From 99c46976c1994ddcb2082778ffb08c9550dc2dad Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 1 Nov 2022 17:50:49 -0400 Subject: [PATCH 22/50] Removing references to MySQL and Sybase per Matt's comments --- .../eprs/7/03_installation/installing_jdbc_driver.mdx | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index 74af5b1587b..b9a765a91e3 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -7,15 +7,10 @@ using migrating to or from EDB Postgres Advanced Server, use the EDB JDBC driver - If you're using PostgreSQL, use the PostgreSQL JDBC driver. To download the latest supported driver, see the [JDBC drivers section](https://jdbc.postgresql.org/download/) on the PostgreSQL Downloads page. -- If you're using Oracle, MySQL, Microsoft SQL Server or Sybase, use the freely available source-specific JDBC driver. +- If you're using Oracle or Microsoft SQL Server, use the freely available source-specific JDBC driver. - [Oracle JDBC](https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html) - - [MySQL JDBC](https://dev.mysql.com/downloads/connector/j/) - [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) - - [Sybase ASE (jTDS) JDBC](https://sourceforge.net/projects/jtds/files/) - - !!! Note - The open source jTDS driver also supports older versions of Microsoft SQL Server (version 2012 and earlier) and may be used with Replication Server. The Microsoft provided JDBC driver for SQL Server is recommended for the newer versions of SQL Server supported by Migration Toolkit. - + From 426159bc6a2798722ae690f196212e2695a9c84d Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 2 Nov 2022 10:51:10 -0400 Subject: [PATCH 23/50] XDB-1683 update --- .../03_xdb_cli_commands/36_creating_subscription_cli.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index 5f79bbf98b4..26d6bc75447 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -49,7 +49,7 @@ Comma-separated list of filter IDs identifying the filter rules from the set of `customcolmap` -The column mappings between different but compatible columns in the source and target database. Table and schema qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. +The column mappings between different but compatible columns in the source and target database. Table qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. !!! Note Column mapping can be added only with the Replication Server CLI; this feature isn't supported by Replication Console. Column mappings are supported only for single-master replication clusters. @@ -64,13 +64,13 @@ To enter multiple mappings, use a semicolon to separate the column mappings. Enter mappings in the following format, where `dataType` represents the data type of the column in the target database. ```shell - SchemaName\.tableName\.columName=dataType + tableName\.columName=dataType ``` The following is an example of custom column mapping: ```shell - company\.emp\.emp_id=integer + emp\.emp_id=integer ``` The `\` characters act as an escape string, while `.` is a reserved character in regular expressions. Use `\.` to represent the `.` character. From be5b5df57ee86f636e089ab1a7f301e4d4ea7fbc Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 2 Nov 2022 11:01:29 -0400 Subject: [PATCH 24/50] added XDB-1683 note --- .../03_xdb_cli_commands/36_creating_subscription_cli.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index 26d6bc75447..0601ebf55ab 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -49,7 +49,7 @@ Comma-separated list of filter IDs identifying the filter rules from the set of `customcolmap` -The column mappings between different but compatible columns in the source and target database. Table qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. +The column mappings between different but compatible columns in the source and target database. Table-qualified column names can be used in mappings, or a regular expression can be used to implement a mapping rule on multiple columns. !!! Note Column mapping can be added only with the Replication Server CLI; this feature isn't supported by Replication Console. Column mappings are supported only for single-master replication clusters. @@ -67,6 +67,10 @@ Enter mappings in the following format, where `dataType` represents the data typ tableName\.columName=dataType ``` +!!! Note +If the table-qualified `columnName` on which the mapping is applied is also present in another schema, then the provided column mapping is applied on both the table-qualified columns. +!!! + The following is an example of custom column mapping: ```shell From 6f1d80d2d231acc13f05d73792e89dba0581dbea Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 2 Nov 2022 13:18:12 -0400 Subject: [PATCH 25/50] Fixed messy formatting --- .../7/03_installation/installing_jdbc_driver.mdx | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index b9a765a91e3..d7d73c84968 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -2,15 +2,15 @@ title: "Installing a JDBC driver" --- -Which JDBC driver you use depends on the what database you are using: -using migrating to or from EDB Postgres Advanced Server, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). +Which JDBC driver you use depends on the what database you're using. If you're using: -- If you're using PostgreSQL, use the PostgreSQL JDBC driver. To download the latest supported driver, see the [JDBC drivers section](https://jdbc.postgresql.org/download/) on the PostgreSQL Downloads page. +- **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). -- If you're using Oracle or Microsoft SQL Server, use the freely available source-specific JDBC driver. - - [Oracle JDBC](https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html) - - [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) - +- **PostgreSQL**, use the PostgreSQL JDBC driver. To download the latest supported driver, see the [JDBC drivers section](https://jdbc.postgresql.org/download/) on the PostgreSQL Downloads page. + +- **Oracle**, use the freely available [Oracle JDBC](https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html) driver. +- **Microsoft SQL Server**, use the freely available [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) driver. + From 4531280b1d941ebbcd7b636df2419546bb06027a Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Wed, 2 Nov 2022 14:16:17 -0400 Subject: [PATCH 26/50] fixed embarrassing typo --- .../docs/eprs/7/03_installation/installing_jdbc_driver.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index d7d73c84968..19821f38994 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -2,7 +2,7 @@ title: "Installing a JDBC driver" --- -Which JDBC driver you use depends on the what database you're using. If you're using: +Which JDBC driver you use depends on what database you're using. If you're using: - **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). From 5884581f25c31aae1269e79b14b1d7a6bbc83587 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Wed, 2 Nov 2022 17:35:29 -0400 Subject: [PATCH 27/50] Rearranged text + other updates to de-emphasize SB / SBP Mostly rearranged text and made some other tweaks to de-emphasize Stackbuilder (SB) and Stackbuilder Plus (SBP) as being the most common method for installing Replication Server. I'm leaving the other and more comprehensive changes related to SB and SBP for a follow-on PR. --- product_docs/docs/eprs/7/03_installation/index.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/eprs/7/03_installation/index.mdx b/product_docs/docs/eprs/7/03_installation/index.mdx index 04ede782df3..d630f86a7ba 100644 --- a/product_docs/docs/eprs/7/03_installation/index.mdx +++ b/product_docs/docs/eprs/7/03_installation/index.mdx @@ -12,11 +12,11 @@ navigation: This section describes how to install and uninstall Replication Server. -The most common installation of Replication Server is done with the graphical user interface invoked by Stack Builder or StackBuilder Plus depending upon whether you are using PostgreSQL or Advanced Server. See [Installing With Stack Builder or StackBuilder Plus](01_installing_with_stackbuilder) for more information. +Replication Server is available for installion on Linux and Windows hosts. -The Replication Server product is also available as a native package in which case the applicable package manager is used for installation. See [Installing on Linux](03_installing_rpm_package) for platform specific installation instructions. Each Replication Server component is available as an individual RPM package. You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. +For Linux systems, the Replication Server product is available as a native package in which case the applicable package manager is used for installation. See [Installing on Linux](03_installing_rpm_package) for platform specific installation instructions. Each Replication Server component is available as an individual RPM package. You can install all Replication Server components with a single install command, or you may choose to install selected, individual components by installing only those particular packages. -An interactive installer for Windows is available from the [Downloads](https://www.enterprisedb.com/software-downloads-postgres#replication-server) page. +An interactive installer for Windows is available from the [Downloads](https://www.enterprisedb.com/software-downloads-postgres#replication-server) page. Replication Server may also be installed using Stack Builder or StackBuilder Plus depending upon whether you are using PostgreSQL or Advanced Server. See [Installing With Stack Builder or StackBuilder Plus](01_installing_with_stackbuilder) for more information. !!! Note If you have an older version of Replication Server and existing replication systems, review Section [Upgrading to Replication Server 7.0](../10_appendix/02_upgrading_to_xdb6_2/#upgrading_to_xdb6_2) before installing Replication Server. From cd85ed0be2b30d314d0ee0c3f935cb1df196d0d5 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 3 Nov 2022 07:54:34 -0400 Subject: [PATCH 28/50] added XDB-1677 note --- .../eprs/7/09_data_validator/02_perform_datavalidation.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx b/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx index aca0ec7a6ec..f23d58f842a 100644 --- a/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx +++ b/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx @@ -94,6 +94,10 @@ OPTIONS: !!! Tip "New enhancement" The --use-ora-case option is available in Replication Server 7.1 and later. +!!! Note + Data Validator doesn't support column mapping. For custom column mapping, the source and target databases can have different data types so Data Validator can't validate the data when column mapping is applied. +!!! + The general syntax for all options except for `--version` and `--help` is shown by the following: ```shell From 36ec881e8c2d5f2473c5be8c4bec52d0e4ddde1f Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 3 Nov 2022 07:58:21 -0400 Subject: [PATCH 29/50] added "snapshots" --- .../03_xdb_cli_commands/36_creating_subscription_cli.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx index 0601ebf55ab..d746bc3d538 100644 --- a/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx +++ b/product_docs/docs/eprs/7/08_xdb_cli/03_xdb_cli_commands/36_creating_subscription_cli.mdx @@ -54,7 +54,7 @@ The column mappings between different but compatible columns in the source and t !!! Note Column mapping can be added only with the Replication Server CLI; this feature isn't supported by Replication Console. Column mappings are supported only for single-master replication clusters. - Column data type mapping supports synchronization between two databases having different but compatible column data types. For example, the data types of a column may be different but data can be populated without any loss. Ensure that there is no possibility of data loss while providing the column data type mapping. This is very important when adding column mapping for columns that act as primary or unique keys as data or precision loss may create inconsistent data across the source and target database. + Column data type mapping supports snapshots and synchronization between two databases having different but compatible column data types. For example, the data types of a column may be different but data can be populated without any loss. Ensure that there is no possibility of data loss while providing the column data type mapping. This is very important when adding column mapping for columns that act as primary or unique keys as data or precision loss may create inconsistent data across the source and target database. Column mapping is currently not supported for large object type columns. !!! From 3a494478262b7dd3c6304e39cd364db3e0624fe9 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Thu, 3 Nov 2022 11:40:32 -0400 Subject: [PATCH 30/50] Updated Data Validator Custom Column Mapping Note Made some minor tweaks to the wording in the note about the Data Validator not being supported for custom column mappings --- .../docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx b/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx index f23d58f842a..ce8e2f2021a 100644 --- a/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx +++ b/product_docs/docs/eprs/7/09_data_validator/02_perform_datavalidation.mdx @@ -95,7 +95,7 @@ OPTIONS: The --use-ora-case option is available in Replication Server 7.1 and later. !!! Note - Data Validator doesn't support column mapping. For custom column mapping, the source and target databases can have different data types so Data Validator can't validate the data when column mapping is applied. + Data Validator does not support column mapping. With custom column mapping, table columns in the source and target databases can have different data types. As a result, the Data Validator is not able to validate the data when column mapping is applied. !!! The general syntax for all options except for `--version` and `--help` is shown by the following: From 92adddc9d23c45637f813b231ba11c88d7fc15b7 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 8 Nov 2022 15:25:04 -0500 Subject: [PATCH 31/50] XDB-1629 update --- .../03_enable_access_to_database.mdx | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx index 71b76d6da41..f54daeeaf05 100644 --- a/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx +++ b/product_docs/docs/eprs/7/05_smr_operation/01_prerequisites/03_enable_access_to_database.mdx @@ -53,9 +53,20 @@ total 4032 !!! Note These instructions apply only if you're using SQL Server as the publication or subscription database. -The jTDS JDBC driver `jar` file `jtds-1.3.1.jar` must be accessible to the Java virtual machine (JVM) on the host running the publication server and the subscription server. If the publication server and subscription server are running on separate hosts, the `jTDS JDBC` driver must be accessible to the JVM on each host. +Replication Server now supports both Microsoft JDBC and jTDS JDBC drivers. A new parameter option `useJtdsDriver` is added with the default value of `true` in both `xdb_pubserver.conf` and `xdb_subserver.conf` configuration files. This option when true uses jTDS driver for SQL Server connection. To use a Microsoft specific JDBC driver, uncomment this option and specify the value `false` in both the configuration files. -When you install Replication Server, the `jtds-1.3.1.jar` file is placed in the directory `XDB_HOME/lib/jdbc` so there is no manual configuration needed for this requirement. +The MS SQL JDBC driver jar file `mssql-jdbc-10.2.1.jre8.jar` or the jTDS JDBC driver jar file `jtds-1.3.1.jar` must be accessible to the Java virtual machine (JVM) on the host running the publication server and the subscription server depending on which driver is being used. If the publication server and subscription server are running on separate hosts, the Microsoft JDBC or jTDS JDBC driver must be accessible to the JVM on each host. + +When you install Replication Server, there is no `jtds-1.3.1.jar` or `mssql-jdbc-10.2.1.jre8.jar` placed in the directory `XDB_HOME/lib/jdbc` by the Replication Server installation. The user has to copy the required JDBC driver and rename them as `mssql-jdbc.jar` and `jtds.jar` . Alternatively, the user can create a symlink in `XDB_HOME/lib/jdbc` for the required JDBC driver. The symlink names should be as below: + +``` +mssql-jdbc.jar +jtds.jar +``` + +!!!Note +For windows, we recommended that the user copy the required JDBC jars to the `XDB_HOME/lib/jdbc` folder and rename them. +!!! **Step 1:** Be sure SQL Server Authentication mode is enabled on your SQL Server database engine. SQL Server Authentication mode allows the use of SQL Server logins such as the built-in system administrator login, sa. From c615d29ed85002c74a289235ed12796a2da67c4b Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 9 Nov 2022 16:14:29 -0500 Subject: [PATCH 32/50] added release notes --- .../7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx index 4224863dee5..3ee384d3b94 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx @@ -6,4 +6,15 @@ title: "Version 7.3.0" New features, enhancements, bug fixes, and other changes in Replication Server 7.3.0 include the following: | Type | Description | -| ------- |------------ | \ No newline at end of file +| ------- |------------ | +| Enhancement | Replication Server now provides the ability to define custom column data type mappings for the replication of tables between Oracle and EDB Postgres Advanced Server or PostgreSQL. The data types in the source and target databases must be of compatible types. | +| Enhancement | Replication Server is now certified to work with the Microsoft provided SQL Server JDBC driver version 10.2. Although the open source jTDS driver can still be used for connections to Microsoft SQL Server, it is recommended that the Microsoft provided SQL Server JDBC driver be used instead, as it provides support for the more recent versions of SQL Server. | +| Enhancement | The synchronize process has been enhanced to optimize the `replicateDDL` operation so that it is able to complete within a reasonable time window during peak activity. [Support ticket #84057] | +| Enhancement | Removed the limitation of being able to add only 1000 tables to a single Oracle publication. | +| Security fix | Updated the version of the zlib library provided with the Replication Server Windows installer to version 1.2.13 to address a security vulnerability identified in CVE-2022-37434. This vulnerability is not present in the Linux distributions of Replication Server. | +| Bug fix | Fixed an issue where the `reloadconf` Replication Server CLI command reports success even when the configuration file is not found. | +| Bug fix | Fixed an issue that causes the synchronize operation to fail when an Oracle Publication table primary key is based on the NCHAR/NVARCHAR type and the table contains a LOB column. | +| Bug fix | Fixed an issue that results in a publication creation failure for trigger-based replication mode if two or more tables have a common name pattern. [Support ticket #83414] | +| Bug fix | Fixed an issue encountered in an MMR cluster where the update-update conflict resolution might not discard some of the modified column values on the database node whose values are marked to be discarded. [Support ticket #83594] | +| Bug fix | Fixed an issue encountered in a trigger-based MMR cluster where the history cleanup job is not configured to fire automatically for non-MDN nodes. | +| Bug fix | Fixed an issue where the synchronize operation fails if the `standard_conforming_strings` is off and the source Oracle column contains a `\’` character combination. | \ No newline at end of file From 5908f58fff28beb5a808c6545b66c14f959de866 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Wed, 9 Nov 2022 16:23:33 -0500 Subject: [PATCH 33/50] updated release date --- product_docs/docs/eprs/7/eprs_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index a7534726003..3c059765fee 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -9,7 +9,7 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | | -------------------------------- | ------------ | -| [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 04 | +| [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 14 | | [7.2.1](16_eprs_rel_notes_7.2.1) | 2022 Jul 25 | | [7.2.0](17_eprs_rel_notes_7.2.0) | 2022 Jun 24 | | [7.1.0](18_eprs_rel_notes_7.1.0) | 2022 Mar 21 | From c1009bd238cd02d5cadeb197040bcf082a712b4e Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 10 Nov 2022 06:06:43 -0500 Subject: [PATCH 34/50] Adding Java 8 requirement to driver topic --- .../docs/eprs/7/03_installation/installing_jdbc_driver.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index 19821f38994..98307585a2c 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -6,7 +6,7 @@ Which JDBC driver you use depends on what database you're using. If you're using - **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). -- **PostgreSQL**, use the PostgreSQL JDBC driver. To download the latest supported driver, see the [JDBC drivers section](https://jdbc.postgresql.org/download/) on the PostgreSQL Downloads page. +- **PostgreSQL**, use the PostgreSQL JDBC driver. To download the latest supported driver (Java 8), see the [JDBC drivers section](https://jdbc.postgresql.org/download/) on the PostgreSQL Downloads page. - **Oracle**, use the freely available [Oracle JDBC](https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html) driver. From 29b1494341230387dd8aba384d79d4752ca789f8 Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Thu, 10 Nov 2022 07:58:58 -0500 Subject: [PATCH 35/50] updated release notes --- .../eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx index 3ee384d3b94..6230d525d6a 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx @@ -11,10 +11,10 @@ New features, enhancements, bug fixes, and other changes in Replication Server 7 | Enhancement | Replication Server is now certified to work with the Microsoft provided SQL Server JDBC driver version 10.2. Although the open source jTDS driver can still be used for connections to Microsoft SQL Server, it is recommended that the Microsoft provided SQL Server JDBC driver be used instead, as it provides support for the more recent versions of SQL Server. | | Enhancement | The synchronize process has been enhanced to optimize the `replicateDDL` operation so that it is able to complete within a reasonable time window during peak activity. [Support ticket #84057] | | Enhancement | Removed the limitation of being able to add only 1000 tables to a single Oracle publication. | -| Security fix | Updated the version of the zlib library provided with the Replication Server Windows installer to version 1.2.13 to address a security vulnerability identified in CVE-2022-37434. This vulnerability is not present in the Linux distributions of Replication Server. | -| Bug fix | Fixed an issue where the `reloadconf` Replication Server CLI command reports success even when the configuration file is not found. | -| Bug fix | Fixed an issue that causes the synchronize operation to fail when an Oracle Publication table primary key is based on the NCHAR/NVARCHAR type and the table contains a LOB column. | +| Security fix | Updated the version of the zlib library provided with the Replication Server Windows installer to version 1.2.13 to address a security vulnerability identified in [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434). This vulnerability is not present in the Linux distributions of Replication Server. | | Bug fix | Fixed an issue that results in a publication creation failure for trigger-based replication mode if two or more tables have a common name pattern. [Support ticket #83414] | | Bug fix | Fixed an issue encountered in an MMR cluster where the update-update conflict resolution might not discard some of the modified column values on the database node whose values are marked to be discarded. [Support ticket #83594] | +| Bug fix | Fixed an issue that causes the synchronize operation to fail when an Oracle Publication table primary key is based on the NCHAR/NVARCHAR type and the table contains a LOB column. | | Bug fix | Fixed an issue encountered in a trigger-based MMR cluster where the history cleanup job is not configured to fire automatically for non-MDN nodes. | -| Bug fix | Fixed an issue where the synchronize operation fails if the `standard_conforming_strings` is off and the source Oracle column contains a `\’` character combination. | \ No newline at end of file +| Bug fix | Fixed an issue where the synchronize operation fails if the `standard_conforming_strings` is off and the source Oracle column contains a `\’` character combination. | +| Bug fix | Fixed an issue where the `reloadconf` Replication Server CLI command reports success even when the configuration file is not found. | \ No newline at end of file From 33b32f0049af4fe2a3eba68acc0d3878a05a1288 Mon Sep 17 00:00:00 2001 From: Jagdish Kewat Date: Thu, 10 Nov 2022 18:45:43 +0530 Subject: [PATCH 36/50] HNG-636-Create release notes for harp 2.2.1 --- .../3.7/harp/01_release_notes/harp2.2.1_rel_notes.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 product_docs/docs/pgd/3.7/harp/01_release_notes/harp2.2.1_rel_notes.mdx diff --git a/product_docs/docs/pgd/3.7/harp/01_release_notes/harp2.2.1_rel_notes.mdx b/product_docs/docs/pgd/3.7/harp/01_release_notes/harp2.2.1_rel_notes.mdx new file mode 100644 index 00000000000..c0c2f4cbe75 --- /dev/null +++ b/product_docs/docs/pgd/3.7/harp/01_release_notes/harp2.2.1_rel_notes.mdx @@ -0,0 +1,10 @@ +--- +title: "Version 2.2.1" +--- + +This is a patch release of HARP 2 that includes fixes for issues identified +in previous versions. + +| Type | Description | +| ---- |------------ | +| Bug Fix | Fix connection leak issue (BDR-2530). | From a5172dc95fd0a37a5de9718c7b97a51cb7949747 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Thu, 10 Nov 2022 11:59:51 -0500 Subject: [PATCH 37/50] Creating symlinks for the jdbc driver updated symlink section to reflect how Matt thinks it should work --- .../7/03_installation/installing_jdbc_driver.mdx | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index 98307585a2c..6aa823ec4cc 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -2,6 +2,8 @@ title: "Installing a JDBC driver" --- +## Choosing and installing a JDBC driver + Which JDBC driver you use depends on what database you're using. If you're using: - **EDB Postgres Advanced Server**, use the EDB JDBC driver. To download the latest driver, see [EDB Connectors](https://enterprisedb.com/software-downloads-postgres#edb-connectors) on the EDB Downloads page. For installation instructions, see [Installing and configuring EDB JDBC Connector](/jdbc_connector/latest/04_installing_and_configuring_the_jdbc_connector/). @@ -12,5 +14,19 @@ Which JDBC driver you use depends on what database you're using. If you're using - **Microsoft SQL Server**, use the freely available [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) driver. +## Configuring the driver + +After downloading the driver, create a symlink in the `XDB-install-folder/lib/jdbc` directory that points to the location where you installed the driver. + +For Linux, create a symlink for the driver using these naming conventions: + | Driver | symlink name | + | -------------------- | -------------- | + | EDB | edb-jdbc18.jar | + | PostgreSQL | postgresql.jar | + | Oracle | ojdbc.jar | + | Microsoft SQL Server | mssql-jdbc.jar | + | jTDS | jtds.jar | + + For Windows simply rename the driver file using the same naming conventions. From d4fd1f002266ba12892a0432e224707e9b111f22 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Thu, 10 Nov 2022 14:17:09 -0500 Subject: [PATCH 38/50] Updated instructions for Windows Correct the instructions for installing and configuring the drivers on Windows based on the steps identified in https://docs.google.com/document/d/16yf8qng_NMyC903p8CfGymija-s2-31QmWPVxHcgO0o/edit --- .../docs/eprs/7/03_installation/installing_jdbc_driver.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index 6aa823ec4cc..a3b77304bee 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -28,5 +28,5 @@ For Linux, create a symlink for the driver using these naming conventions: | Microsoft SQL Server | mssql-jdbc.jar | | jTDS | jtds.jar | - For Windows simply rename the driver file using the same naming conventions. + For Windows, the drivers need to be copied to the `XDB-install-folder/lib/jdbc` directory and renamed using the same naming conventions. From f43b9fe17209a7038374dd74fd6e4adfd952bcea Mon Sep 17 00:00:00 2001 From: Jagdish Kewat Date: Mon, 14 Nov 2022 12:37:53 +0530 Subject: [PATCH 39/50] HNG-636 - Fix review comment --- product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx index ee20d5f79f3..9ef8fd75722 100644 --- a/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx +++ b/product_docs/docs/pgd/3.7/harp/01_release_notes/index.mdx @@ -1,6 +1,7 @@ --- title: Release Notes navigation: +- harp2.2.1_rel_notes - harp2.2.0_rel_notes - harp2.1.1_rel_notes - harp2.1.0_rel_notes @@ -20,6 +21,7 @@ The release notes in this section provide information on what was new in each re | Version | Release Date | | ----------------------- | ------------ | +| [2.2.1](harp2.2.1_rel_notes) | 2022 Nov 16 | | [2.2.0](harp2.2.0_rel_notes) | 2022 Aug 22 | | [2.1.1](harp2.1.1_rel_notes) | 2022 Jun 21 | | [2.1.0](harp2.1.0_rel_notes) | 2022 May 17 | From a257856ed6329c75df9425ec8c21333e0ac74095 Mon Sep 17 00:00:00 2001 From: jingjingliu20 <86595232+jingjingliu20@users.noreply.github.com> Date: Mon, 14 Nov 2022 16:18:19 +0800 Subject: [PATCH 40/50] Update index.mdx --- .../01_connecting_from_azure/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx index c532eae714c..5689cdc5b12 100644 --- a/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx +++ b/product_docs/docs/biganimal/release/using_cluster/02_connecting_your_cluster/01_connecting_from_azure/index.mdx @@ -13,7 +13,7 @@ While other methods for connecting your cluster from your application's virtual Azure Private Endpoint is a network interface that securely connects a private IP address from your Azure Virtual Network (VNet) to an external service. You grant access only to a single cluster instead of the entire BigAnimal resource virtual network, thus ensuring maximum network isolation. Other advantages include: -- You need to configure the Private Link only once. Then you can use multiple Private Links to connect applications from many different VNets. +- You need to configure the Private Link only once. Then you can use multiple Private Endpoints to connect applications from many different VNets. - There's no risk of IP address conflicts. Private Endpoints are the same mechanism used by first-party Azure services such as CosmosDB for private VNet connectivity. For more information, see [What is an Azure Private Endpoint?](https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-overview). Private Links (required by Private Endpoints) are not free, however. See [Azure Private Link pricing](https://azure.microsoft.com/en-us/pricing/details/private-link/#pricing) for information on the costs associated with Private Links (required by Private Endpoints). From 4a6b7d8d2ac771695aba11d131d980a6cab71e80 Mon Sep 17 00:00:00 2001 From: kshitijakarpe <92665409+kshitijakarpe@users.noreply.github.com> Date: Mon, 14 Nov 2022 16:59:21 +0530 Subject: [PATCH 41/50] Update index.mdx --- .../release/getting_started/creating_a_cluster/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx index cfca3f2ad11..abee0fc284d 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx @@ -43,7 +43,7 @@ Prior to creating your cluster, make sure you have enough resources. Without eno !!! Note You can't switch from a single node or high-availability cluster to an extreme high-availability cluster or vice versa. -1. Select the number of standby replicas for your cluster. +1. Select the number of standby replicas for your High availability cluster. 1. Select the cloud provider for your cluster. If you're using your own account and haven't connected it to BigAnimal yet, see [Connecting to your cloud](/biganimal/latest/getting_started/02_connecting_to_your_cloud). From 1bec34d2c609bd5cdcd588887867178111a78248 Mon Sep 17 00:00:00 2001 From: Dee Dee Rothery <83650384+drothery-edb@users.noreply.github.com> Date: Mon, 14 Nov 2022 08:27:15 -0500 Subject: [PATCH 42/50] updated case --- .../release/getting_started/creating_a_cluster/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx index abee0fc284d..93180fcec8b 100644 --- a/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx +++ b/product_docs/docs/biganimal/release/getting_started/creating_a_cluster/index.mdx @@ -43,7 +43,7 @@ Prior to creating your cluster, make sure you have enough resources. Without eno !!! Note You can't switch from a single node or high-availability cluster to an extreme high-availability cluster or vice versa. -1. Select the number of standby replicas for your High availability cluster. +1. Select the number of standby replicas for your high availability cluster. 1. Select the cloud provider for your cluster. If you're using your own account and haven't connected it to BigAnimal yet, see [Connecting to your cloud](/biganimal/latest/getting_started/02_connecting_to_your_cloud). From c83df999e068a6e9d50ce368dbc9039260e81102 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 14 Nov 2022 19:14:02 +0530 Subject: [PATCH 43/50] EPAS - Release notes 14.6.0, 13.9.13, 12.13.17, 11.18.29 and 10.23.33 --- .../epas_rel_notes/epas10_23_33_rel_notes.mdx | 12 ++++++++++++ .../docs/epas/10/epas_rel_notes/index.mdx | 2 ++ .../epas_rel_notes/epas11_18_29_rel_notes.mdx | 11 +++++++++++ .../docs/epas/11/epas_rel_notes/index.mdx | 2 ++ .../epas_rel_notes/epas12_13_17_rel_notes.mdx | 12 ++++++++++++ .../docs/epas/12/epas_rel_notes/index.mdx | 2 ++ .../epas_rel_notes/epas13_9_13_rel_notes.mdx | 11 +++++++++++ .../docs/epas/13/epas_rel_notes/index.mdx | 2 ++ .../14/epas_rel_notes/epas14_6_0_rel_notes.mdx | 18 ++++++++++++++++++ .../docs/epas/14/epas_rel_notes/index.mdx | 2 ++ 10 files changed, 74 insertions(+) create mode 100644 product_docs/docs/epas/10/epas_rel_notes/epas10_23_33_rel_notes.mdx create mode 100644 product_docs/docs/epas/11/epas_rel_notes/epas11_18_29_rel_notes.mdx create mode 100644 product_docs/docs/epas/12/epas_rel_notes/epas12_13_17_rel_notes.mdx create mode 100644 product_docs/docs/epas/13/epas_rel_notes/epas13_9_13_rel_notes.mdx create mode 100644 product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx diff --git a/product_docs/docs/epas/10/epas_rel_notes/epas10_23_33_rel_notes.mdx b/product_docs/docs/epas/10/epas_rel_notes/epas10_23_33_rel_notes.mdx new file mode 100644 index 00000000000..3931c3c7b22 --- /dev/null +++ b/product_docs/docs/epas/10/epas_rel_notes/epas10_23_33_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: "Version 10.23.33" +--- + +EDB Postgres Advanced Server 10.23.33 includes the following enhancements: + +| Type | Description | ID | Category | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------| ------- | ---------------- | +| Upstream merge | Merged with community PostgreSQL 10.23. See the community [Release Notes](https://www.postgresql.org/docs/release/10.23/) for details. | | | +| Enhancement | Enhance edb_filter_log.redact_password_commands so that passwords used in the CREATE/ALTER ROLE, CREATE/ALTER USER, and CREATE/ALTER GROUP syntax will get redacted when using optional parameters. [Support Ticket: #86366]| DB-1984 | | +| Enhancement | Improve an error when you alter the table column dependent on the package variable. [Support Ticket: #85027] | DB-1950 | | + diff --git a/product_docs/docs/epas/10/epas_rel_notes/index.mdx b/product_docs/docs/epas/10/epas_rel_notes/index.mdx index d2921241228..eb5d0584e4e 100644 --- a/product_docs/docs/epas/10/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/10/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas10_23_33_rel_notes - epas10_22_32_rel_notes - epas10_21_31_rel_notes legacyRedirectsGenerated: @@ -20,6 +21,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merge | | ------- | ------------ | -------------- | +| [10.23.33](epas10_23_33_rel_notes.mdx) | 2022 Nov 10 | [10.23](https://www.postgresql.org/docs/10/release-10-23.html) | | [10.22.32](epas10_22_32_rel_notes.mdx) | 2022 Aug 11 | [10.22](https://www.postgresql.org/docs/10/release-10-22.html) | | [10.21.31](epas10_21_31_rel_notes.mdx) | 2022 May 12 | [10.21](https://www.postgresql.org/docs/10/release-10-21.html) | | [10.20.30](09_epas10.20.30_rel_notes.mdx) | 2022 Feb 10 | [10.20](https://www.postgresql.org/docs/10/release-10-20.html) | diff --git a/product_docs/docs/epas/11/epas_rel_notes/epas11_18_29_rel_notes.mdx b/product_docs/docs/epas/11/epas_rel_notes/epas11_18_29_rel_notes.mdx new file mode 100644 index 00000000000..01d12e8ff2f --- /dev/null +++ b/product_docs/docs/epas/11/epas_rel_notes/epas11_18_29_rel_notes.mdx @@ -0,0 +1,11 @@ +--- +title: "Version 11.18.29" +--- + +EDB Postgres Advanced Server 11.18.29 includes the following enhancements: + +| Type | Description | ID | Category | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------| ------- | ---------------- | +| Upstream merge | Merged with community PostgreSQL 11.18.29. See the community [Release Notes](https://www.postgresql.org/docs/release/11.18/) for details. | | | +| Enhancement | Enhance edb_filter_log.redact_password_commands so that passwords used in the CREATE/ALTER ROLE, CREATE/ALTER USER, and CREATE/ALTER GROUP syntax will get redacted when using optional parameters. [Support Ticket: #86366]| DB-1984 | | +| Enhancement | Improve an error when you alter the table column dependent on the package variable. [Support Ticket: #85027] | DB-1950 | | diff --git a/product_docs/docs/epas/11/epas_rel_notes/index.mdx b/product_docs/docs/epas/11/epas_rel_notes/index.mdx index 8a34801bca1..0c2f609091f 100644 --- a/product_docs/docs/epas/11/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/11/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas11_18_29_rel_notes - epas11_17_28_rel_notes - epas11_16_26_rel_notes legacyRedirectsGenerated: @@ -20,6 +21,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merge | | ------- | ------------ | -------------- | +| [11.18.29](epas11_18_29_rel_notes.mdx) | 2022 Nov 10 | [11.18](https://www.postgresql.org/docs/11/release-11-18.html) | | [11.17.28](epas11_17_28_rel_notes.mdx) | 2022 Aug 11 | [11.17](https://www.postgresql.org/docs/11/release-11-17.html) | | [11.16.26](epas11_16_26_rel_notes.mdx) | 2022 May 12 | [11.16](https://www.postgresql.org/docs/11/release-11-16.html) | | [11.15.25](09_epas11.15.25_rel_notes.mdx) | 2022 Feb 10 | [11.15](https://www.postgresql.org/docs/11/release-11-15.html) | diff --git a/product_docs/docs/epas/12/epas_rel_notes/epas12_13_17_rel_notes.mdx b/product_docs/docs/epas/12/epas_rel_notes/epas12_13_17_rel_notes.mdx new file mode 100644 index 00000000000..39b7f2c389f --- /dev/null +++ b/product_docs/docs/epas/12/epas_rel_notes/epas12_13_17_rel_notes.mdx @@ -0,0 +1,12 @@ +--- +title: "Version 12.13.17" +--- + +EDB Postgres Advanced Server 12.13.17 includes the following enhancements: + +| Type | Description | ID | Category | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------| ------- | ---------------- | +| Upstream merge | Merged with community PostgreSQL 12.13.17. See the community [Release Notes](https://www.postgresql.org/docs/release/12.13/) for details. | | | +| Enhancement | Enhance edb_filter_log.redact_password_commands so that passwords used in the CREATE/ALTER ROLE, CREATE/ALTER USER, and CREATE/ALTER GROUP syntax will get redacted when using optional parameters. [Support Ticket: #86366]| DB-1984 | | +| Enhancement | Improve an error when you alter the table column dependent on the package variable. [Support Ticket: #85027] | DB-1950 | | + diff --git a/product_docs/docs/epas/12/epas_rel_notes/index.mdx b/product_docs/docs/epas/12/epas_rel_notes/index.mdx index 6461d623cea..6fcf08c331b 100644 --- a/product_docs/docs/epas/12/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/12/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas12_13_17_rel_notes - epas12_12_16_rel_notes - epas12_11_15_rel_notes legacyRedirectsGenerated: @@ -23,6 +24,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ------- | ------------ | --------------- | +| [12.13.17](epas12_13_17_rel_notes.mdx) | 2022 Nov 10 | [12.13](https://www.postgresql.org/docs/12/release-12-13.html) | | [12.12.16](epas12_12_16_rel_notes.mdx) | 2022 Aug 11 | [12.12](https://www.postgresql.org/docs/12/release-12-12.html) | | [12.11.15](epas12_11_15_rel_notes.mdx) | 2022 May 12 | [12.11](https://www.postgresql.org/docs/12/release-12-11.html) | | [12.10.14](05_epas12.10.14_rel_notes.mdx) | 2022 Feb 10 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | | [12.10.14](05_epas12.10.14_rel_notes.mdx) | 2022 Feb 10 | [12.10](https://www.postgresql.org/docs/12/release-12-10.html) | diff --git a/product_docs/docs/epas/13/epas_rel_notes/epas13_9_13_rel_notes.mdx b/product_docs/docs/epas/13/epas_rel_notes/epas13_9_13_rel_notes.mdx new file mode 100644 index 00000000000..3b9d8839605 --- /dev/null +++ b/product_docs/docs/epas/13/epas_rel_notes/epas13_9_13_rel_notes.mdx @@ -0,0 +1,11 @@ +--- +title: "Version 13.9.13" +--- + +EDB Postgres Advanced Server 13.9.13 includes the following enhancements: + +| Type | Description | ID | Category | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------| ------- | ---------------- | +| Upstream merge | Merged with community PostgreSQL 13.9.13. See the community [Release Notes](https://www.postgresql.org/docs/release/13.9/) for details. | | | +| Enhancement | Enhance edb_filter_log.redact_password_commands so that passwords used in the CREATE/ALTER ROLE, CREATE/ALTER USER, and CREATE/ALTER GROUP syntax will get redacted when using optional parameters. [Support Ticket: #86366]| DB-1984 | | +| Enhancement | Improve an error when you alter the table column dependent on the package variable. [Support Ticket: #85027] | DB-1950 | | \ No newline at end of file diff --git a/product_docs/docs/epas/13/epas_rel_notes/index.mdx b/product_docs/docs/epas/13/epas_rel_notes/index.mdx index 014c2c38abe..313e34b5819 100644 --- a/product_docs/docs/epas/13/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/13/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release Notes title: "EDB Postgres Advanced Server Release Notes" navigation: +- epas13_9_13_rel_notes - epas13_8_12_rel_notes - epas13_7_11_rel_notes @@ -16,6 +17,7 @@ The EDB Postgres Advanced Server (Advanced Server) documentation describes the l | Version | Release Date | Upstream Merges | | ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | +| [13.9.13](epas13_9_13_rel_notes) | 2022 Nov 10 | [13.9](https://www.postgresql.org/docs/release/13.9/) | [13.8.12](epas13_8_12_rel_notes) | 2022 Aug 11 | [13.8](https://www.postgresql.org/docs/release/13.8/) | [13.7.11](epas13_7_11_rel_notes) | 2022 May 23 | [13.7](https://www.postgresql.org/docs/release/13.7/) | [13.6.10](13_epas13.6.10_rel_notes) | 2022 Feb 10 | [13.6](https://www.postgresql.org/docs/13/release-13-6.html) | diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx new file mode 100644 index 00000000000..339bd211110 --- /dev/null +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx @@ -0,0 +1,18 @@ +--- +title: "Version 14.6.0" +--- + +EDB Postgres Advanced Server 14.6.0 includes the following enhancements and bug fixes: + +| Type | Description | ID | Category | +| -------------- | -------------------------------------------------------------------------------------------------------------------------------------| ------- | --------------------- | +| Upstream merge | Merged with community PostgreSQL 14.6. See the community [Release Notes](https://www.postgresql.org/docs/release/14.6/) for details. | | | +| Enhancement | Enhance edb_filter_log.redact_password_commands so that passwords used in the CREATE/ALTER ROLE, CREATE/ALTER USER, and CREATE/ALTER GROUP syntax will get redacted when using optional parameters. [Support Ticket: #86366]| DB-1984 | | +| Enhancement | Improve an error when you alter the table column dependent on the package variable. [Support Ticket: #85027] | DB-1950 | | +| Bug fix | Fix edbwrap to work under the FIPS-enabled system. This fix allows initdb to work with a FIPS-enabled system. [Support Ticket: #81283, #81673, #77660, #81457, #85713, #86663, #87246] | DB-1746 | edbwrap | +| Bug fix | Fix abnormal behavior of edb-audit by enabling shared memory access to an edb-audit background worker. [Support Ticket: #86002] | DB-1978 | | +| Bug fix | Fix IMPORT FOREIGN SCHEMA failure when the remote database is community PostgreSQL. [Support Ticket: #86156] | EXT-29 | postgres_fdw | +| Bug fix | Advanced server now provides edb_fix_pg_proc.sql script to fix system function behavior on the existing v14 clusters created between 14.1.0 and 14.5.0. The script is inside /share/postgresql/ directory and must run manually. The edb_redwood_date setting is disabled in the system_functions.sql file to avoid the same issue in the future. | DB-2023 | | +| Bug fix | Fix crash in type conversion function due to null input. | DB-1547 | edbldr | + + diff --git a/product_docs/docs/epas/14/epas_rel_notes/index.mdx b/product_docs/docs/epas/14/epas_rel_notes/index.mdx index a2ca91f2754..3dbbff5e058 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/index.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/index.mdx @@ -2,6 +2,7 @@ navTitle: Release notes title: "EDB Postgres Advanced Server release notes" navigation: +- epas14_6_0_rel_notes - epas14_5_0_rel_notes - epas14_4_0_rel_notes - epas14_3_0_rel_notes @@ -15,6 +16,7 @@ The EDB Postgres Advanced Server (EDB Postgres Advanced Server) documentation de | Version | Release date | Upstream merges | | ------------------------------------- | ------------ | ---------------------------------------------------------------------------------------------------------------- | +| [14.6.0](epas14_6_0_rel_notes) | 2022 Nov 10 | [14.6](https://www.postgresql.org/docs/14/release-14-6.html) | | [14.5.0](epas14_5_0_rel_notes) | 2022 Aug 11 | [14.5](https://www.postgresql.org/docs/14/release-14-5.html) | | [14.4.0](epas14_4_0_rel_notes) | 2022 Jun 16 | [14.4](https://www.postgresql.org/docs/14/release-14-4.html) | | [14.3.0](epas14_3_0_rel_notes) | 2022 May 12 | [14.3](https://www.postgresql.org/docs/14/release-14-3.html) | From 35eb03d4564950d664d39f7b440ee3ff8763283f Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Mon, 14 Nov 2022 10:13:51 -0500 Subject: [PATCH 44/50] added limitation for MSSQL server --- .../docs/eprs/7/03_installation/installing_jdbc_driver.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index a3b77304bee..b3ea9804be4 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -27,6 +27,10 @@ For Linux, create a symlink for the driver using these naming conventions: | Oracle | ojdbc.jar | | Microsoft SQL Server | mssql-jdbc.jar | | jTDS | jtds.jar | + +!!! Note +For Microsoft SQL Server, if your system uses JDK/JAVA then it is recommended that you use an equal or earlier mssql-jdbc jre version than the JDK/JAVA version on your system. For example, a system with JDK/JAVA version 18 can use `mssql-jdbc-11.2.0.jre18.jar`, `mssql-jdbc-11.2.0.jre17.jar`, and so on. +!!! For Windows, the drivers need to be copied to the `XDB-install-folder/lib/jdbc` directory and renamed using the same naming conventions. From 207fff9cf1dc098125b2efd989a05f6d684a05e7 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Mon, 14 Nov 2022 13:44:21 -0500 Subject: [PATCH 45/50] Moved MS JDBC driver related note Moved the note about the Microsoft JDBC driver for SQL Server to before the Configuring the driver section to be closer to the text it relates to. --- .../eprs/7/03_installation/installing_jdbc_driver.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx index b3ea9804be4..edf20254360 100644 --- a/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx +++ b/product_docs/docs/eprs/7/03_installation/installing_jdbc_driver.mdx @@ -13,7 +13,11 @@ Which JDBC driver you use depends on what database you're using. If you're using - **Oracle**, use the freely available [Oracle JDBC](https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html) driver. - **Microsoft SQL Server**, use the freely available [Microsoft SQL Server JDBC](https://learn.microsoft.com/en-us/sql/connect/jdbc/release-notes-for-the-jdbc-driver?view=sql-server-ver16#102) driver. - + +!!! Note +For Microsoft SQL Server, if your system uses JDK/JAVA then it is recommended that you use an equal or earlier mssql-jdbc jre version than the JDK/JAVA version on your system. For example, a system with JDK/JAVA version 18 can use `mssql-jdbc-11.2.0.jre18.jar`, `mssql-jdbc-11.2.0.jre17.jar`, and so on. +!!! + ## Configuring the driver After downloading the driver, create a symlink in the `XDB-install-folder/lib/jdbc` directory that points to the location where you installed the driver. @@ -27,10 +31,6 @@ For Linux, create a symlink for the driver using these naming conventions: | Oracle | ojdbc.jar | | Microsoft SQL Server | mssql-jdbc.jar | | jTDS | jtds.jar | - -!!! Note -For Microsoft SQL Server, if your system uses JDK/JAVA then it is recommended that you use an equal or earlier mssql-jdbc jre version than the JDK/JAVA version on your system. For example, a system with JDK/JAVA version 18 can use `mssql-jdbc-11.2.0.jre18.jar`, `mssql-jdbc-11.2.0.jre17.jar`, and so on. -!!! For Windows, the drivers need to be copied to the `XDB-install-folder/lib/jdbc` directory and renamed using the same naming conventions. From 7216192951eda9f31d0ddf9b17d68e2bed55c6b5 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Tue, 15 Nov 2022 07:54:55 -0500 Subject: [PATCH 46/50] Updated MS driver versions and added Debian 11 Support Updated the Microsoft JDBC driver for SQL Server text to list both versions 10.2 and 11.2 as being certified as supported. Added a new Enhancement row indicating that Debian 11 is now a supported platform. --- .../docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx index 6230d525d6a..c2704f54049 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/15_eprs_rel_notes_7.3.0.mdx @@ -8,7 +8,8 @@ New features, enhancements, bug fixes, and other changes in Replication Server 7 | Type | Description | | ------- |------------ | | Enhancement | Replication Server now provides the ability to define custom column data type mappings for the replication of tables between Oracle and EDB Postgres Advanced Server or PostgreSQL. The data types in the source and target databases must be of compatible types. | -| Enhancement | Replication Server is now certified to work with the Microsoft provided SQL Server JDBC driver version 10.2. Although the open source jTDS driver can still be used for connections to Microsoft SQL Server, it is recommended that the Microsoft provided SQL Server JDBC driver be used instead, as it provides support for the more recent versions of SQL Server. | +| Enhancement | Replication Server is now certified to work with the Microsoft provided SQL Server JDBC driver versions 10.2 and 11.2. Although the open source jTDS driver can still be used for connections to Microsoft SQL Server, it is recommended that the Microsoft provided SQL Server JDBC driver be used instead, as it provides support for the more recent versions of SQL Server. | +| Enhancement | Replication Server is now certified to work on the Debian 11 platform. | | Enhancement | The synchronize process has been enhanced to optimize the `replicateDDL` operation so that it is able to complete within a reasonable time window during peak activity. [Support ticket #84057] | | Enhancement | Removed the limitation of being able to add only 1000 tables to a single Oracle publication. | | Security fix | Updated the version of the zlib library provided with the Replication Server Windows installer to version 1.2.13 to address a security vulnerability identified in [CVE-2022-37434](https://nvd.nist.gov/vuln/detail/CVE-2022-37434). This vulnerability is not present in the Linux distributions of Replication Server. | @@ -17,4 +18,4 @@ New features, enhancements, bug fixes, and other changes in Replication Server 7 | Bug fix | Fixed an issue that causes the synchronize operation to fail when an Oracle Publication table primary key is based on the NCHAR/NVARCHAR type and the table contains a LOB column. | | Bug fix | Fixed an issue encountered in a trigger-based MMR cluster where the history cleanup job is not configured to fire automatically for non-MDN nodes. | | Bug fix | Fixed an issue where the synchronize operation fails if the `standard_conforming_strings` is off and the source Oracle column contains a `\’` character combination. | -| Bug fix | Fixed an issue where the `reloadconf` Replication Server CLI command reports success even when the configuration file is not found. | \ No newline at end of file +| Bug fix | Fixed an issue where the `reloadconf` Replication Server CLI command reports success even when the configuration file is not found. | From bcaba4629af00007e7076bb14196e030c675f967 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Tue, 15 Nov 2022 07:55:53 -0500 Subject: [PATCH 47/50] Updated 7.3 Release Date Changed 7.3 release date from 14 Nov to 15 Nov --- product_docs/docs/eprs/7/eprs_rel_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx index 3c059765fee..65d1dfb89ac 100644 --- a/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/7/eprs_rel_notes/index.mdx @@ -9,7 +9,7 @@ The Replication Server documentation describes the latest version including mino | Version | Release Date | | -------------------------------- | ------------ | -| [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 14 | +| [7.3.0](15_eprs_rel_notes_7.3.0) | 2022 Nov 15 | | [7.2.1](16_eprs_rel_notes_7.2.1) | 2022 Jul 25 | | [7.2.0](17_eprs_rel_notes_7.2.0) | 2022 Jun 24 | | [7.1.0](18_eprs_rel_notes_7.1.0) | 2022 Mar 21 | From 43afdd3ba67eee9dbed214d43920c49b5ffa8096 Mon Sep 17 00:00:00 2001 From: drothery-edb Date: Tue, 15 Nov 2022 05:54:50 -0500 Subject: [PATCH 48/50] Used full product name, added article, and used font treatment for path added noun --- .../docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx b/product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx index 339bd211110..db0ed026838 100644 --- a/product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx +++ b/product_docs/docs/epas/14/epas_rel_notes/epas14_6_0_rel_notes.mdx @@ -12,7 +12,7 @@ EDB Postgres Advanced Server 14.6.0 includes the following enhancements and bug | Bug fix | Fix edbwrap to work under the FIPS-enabled system. This fix allows initdb to work with a FIPS-enabled system. [Support Ticket: #81283, #81673, #77660, #81457, #85713, #86663, #87246] | DB-1746 | edbwrap | | Bug fix | Fix abnormal behavior of edb-audit by enabling shared memory access to an edb-audit background worker. [Support Ticket: #86002] | DB-1978 | | | Bug fix | Fix IMPORT FOREIGN SCHEMA failure when the remote database is community PostgreSQL. [Support Ticket: #86156] | EXT-29 | postgres_fdw | -| Bug fix | Advanced server now provides edb_fix_pg_proc.sql script to fix system function behavior on the existing v14 clusters created between 14.1.0 and 14.5.0. The script is inside /share/postgresql/ directory and must run manually. The edb_redwood_date setting is disabled in the system_functions.sql file to avoid the same issue in the future. | DB-2023 | | +| Bug fix | EDB Postgres Advanced Server now provides the edb_fix_pg_proc.sql script to fix system function behavior on the existing v14 clusters created between 14.1.0 and 14.5.0. The script is inside `/share/postgresql/` directory and you must run it manually. The edb_redwood_date setting is disabled in the system_functions.sql file to avoid the same issue in the future. | DB-2023 | | | Bug fix | Fix crash in type conversion function due to null input. | DB-1547 | edbldr | From 6c3ee888664bbe405542ea0ed133fe5b7aff76ba Mon Sep 17 00:00:00 2001 From: Chris Estes <106166814+ccestes@users.noreply.github.com> Date: Tue, 15 Nov 2022 08:20:48 -0500 Subject: [PATCH 49/50] XDB-1702 update --- .../01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx index fca3d6a9a86..62970c55db1 100644 --- a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx @@ -12,6 +12,8 @@ You can upgrade to Replication Server 7.0 using the graphical user interface ins 1. After all pending transactions are replicated to their target databases, stop the Replication Server 6.2.x publication server and subscription server. See [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). +1. Ensure the installation user has administrative permissions on the `XDB_HOME/xdata` folder. This can be done by opening the Replication Server installation directory in Windows Explorer and selecting the xdata folder. When prompted, select **Continue** to enable the required permission. + 1. Install Replication Server 7.0. See [Installation and uninstallation](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for instructions on installing Replication Server, but note the differences described in the following steps. 1. Following the acceptance of the license agreement in [Installing with Stack Builder or StackBuilder Plus](../../03_installation/01_installing_with_stackbuilder/#installing_with_stackbuilder), the Select Components screen appears but with the entries grayed out. The old Replication Server components are replaced with the new ones in the old Replication Server’s directory location. Select **Next**. From c1886eb96f0be4a9095ac9b979c2b6b73e3ebef4 Mon Sep 17 00:00:00 2001 From: mlewandowski-edb <63003848+mlewandowski-edb@users.noreply.github.com> Date: Tue, 15 Nov 2022 10:52:46 -0500 Subject: [PATCH 50/50] Minor update to xdata permission step Updated instructions to indicate the method for ensuring the installation user has administrative permissions on xdata directory is for Windows. --- .../02_upgrading_with_gui_installer.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx index 62970c55db1..bb713376e38 100644 --- a/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx +++ b/product_docs/docs/eprs/7/10_appendix/01_upgrading_to_xdb6_2/02_upgrading_with_gui_installer.mdx @@ -12,7 +12,7 @@ You can upgrade to Replication Server 7.0 using the graphical user interface ins 1. After all pending transactions are replicated to their target databases, stop the Replication Server 6.2.x publication server and subscription server. See [Registering a publication server](../../05_smr_operation/02_creating_publication/01_registering_publication_server/#registering_publication_server) and [Registering a subscription server](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server). -1. Ensure the installation user has administrative permissions on the `XDB_HOME/xdata` folder. This can be done by opening the Replication Server installation directory in Windows Explorer and selecting the xdata folder. When prompted, select **Continue** to enable the required permission. +1. Ensure the installation user has administrative permissions on the `XDB_HOME/xdata` folder. On Windows, this can be done by opening the Replication Server installation directory in Windows Explorer and selecting the xdata folder. When prompted, select **Continue** to enable the required permission. 1. Install Replication Server 7.0. See [Installation and uninstallation](../../05_smr_operation/03_creating_subscription/01_registering_subscription_server/#registering_subscription_server) for instructions on installing Replication Server, but note the differences described in the following steps. @@ -49,4 +49,4 @@ You can upgrade to Replication Server 7.0 using the graphical user interface ins You are now ready to use Replication Server 7.0 to create new replication systems and manage existing ones. !!! Note - **For Windows:** If you give a new admin password during an upgrade, it is ignored. After the upgrade, Replication Server picks the old admin user name and password (which is saved in `edb-replconf`). \ No newline at end of file + **For Windows:** If you give a new admin password during an upgrade, it is ignored. After the upgrade, Replication Server picks the old admin user name and password (which is saved in `edb-replconf`).