diff --git a/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx b/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx deleted file mode 100644 index 1de1a6c4abe..00000000000 --- a/product_docs/docs/eprs/6.2/01_introduction/01_whats_new.mdx +++ /dev/null @@ -1,14 +0,0 @@ ---- -title: "What’s New" ---- - - - -The following features have been added to xDB Replication Server version 6.1 to create xDB Replication Server version 6.2: - -> - Registering your xDB Replication Server product with an EnterpriseDB product license key is no longer required. Thus, all components related to registering the product have been removed. The following are the removed components: - - The Product Registration dialog box accessed from the xDB Replication Console Help menu - - The `license_key` parameter located in the xDB Replication Configuration file - - The xDB Replication Server CLI `registerkey` command. -> - Partitioned tables created using the declarative partitioning feature of PostgreSQL and Advanced Server version 10 and later can now be replicated in a log-based single-master or multi-master replication system. For more information, see [Replicating Postgres Partitioned Tables](../07_common_operations/10_replicating_postgres_partitioned_tables/#replicating_postgres_partitioned_tables). -> - In a single-master replication system, removal of a table from a publication that has one or more existing subscriptions is now permitted as long as the table to be removed is not the parent referenced in a foreign key constraint from a child table that is not being removed as well. Previously, no tables from a publication in a single-master replication system could be removed if there are existing subscriptions. For more information, see [Removing Tables from a Publication](../07_common_operations/06_managing_publication/03_updating_pub/#remove_tables_from_pub). diff --git a/product_docs/docs/eprs/6.2/01_introduction/03_certified_supported_versions.mdx b/product_docs/docs/eprs/6.2/01_introduction/03_certified_supported_versions.mdx index 46634adef38..8586fb1a24e 100644 --- a/product_docs/docs/eprs/6.2/01_introduction/03_certified_supported_versions.mdx +++ b/product_docs/docs/eprs/6.2/01_introduction/03_certified_supported_versions.mdx @@ -4,8 +4,8 @@ title: "Certified and Supported Product Versions" The following database product versions may be used with xDB Replication Server: -- PostgreSQL versions 9.6, 10, 11, 12, and 13 -- Advanced Server versions 9.6, 10, 11, 12, and 13 +- PostgreSQL versions 10, 11, 12, 13, and 14 +- Advanced Server versions 10, 11, 12, 13, and 14 - Oracle 10g Release 2 version 10.2.0.1.0 has been explicitly certified. Newer minor versions in the 10.2 line are supported as well. - Oracle 11g Release 2 version 11.2.0.2.0 has been explicitly certified. Newer minor versions in the 11.2 line are supported as well. - Oracle 12c version 12.1.0.2.0 has been explicitly certified. Newer minor versions in the 12.1 line are supported as well. diff --git a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx index 757cb0a2085..0194ce0636f 100644 --- a/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx +++ b/product_docs/docs/eprs/6.2/02_overview/04_design_replication_system/03_restrictions_on_replicated_database_objects.mdx @@ -48,6 +48,13 @@ Oracle tables with the following data types can be used in snapshot-only publica - `NCLOB` - `RAW` +Columns with following data types cannot be added to a filter for a PostgreSQL or EDB Postgres Advanced Server database: + +- `money` +- `bit` +- `bit varying` + + ## Restrictions on SQL Server Database Objects SQL Server tables that include the following data types cannot be replicated: @@ -82,27 +89,37 @@ PostgreSQL or EDB Postgres Advanced Server database tables that include the foll - `JSON` - `JSONB` +- Geometry data types +- `tsvector`, `tsquery`, `txid_snapshot`, `pg_lsn` +- `cidr`, `inet`, `mcaddress`, `mcaddress8`, `uuid`, `Date` +- `ENUM`, `ARRAY`, range data type (such as `int4range`, `tstzrange`, `numrange`, `daterange`) +- Any user-defined data type (that is, defined as `CREATE TYPE type_name`) -Postgres tables that include `OID` based large objects cannot be replicated. For information on `OID` based large objects see `pg_largeobject` in the PostgreSQL Core Documentation located at: - -> +Postgres tables that include `OID` based large objects cannot be replicated. For information on `OID` based large objects see [`pg_largeobject`]() in the PostgreSQL Core Documentation. -Postgres tables that include any geometric data types such as POINT, POLYGON, etc., cannot be replicated to an Oracle subscription database. + Postgres tables that include any geometric data types such as POINT, POLYGON, etc., cannot be replicated to an Oracle subscription database. Postgres tables that include the following data types cannot be replicated to a SQL Server subscription database: - `ABSTIME` - `ACLITEM` - `CHKPASS` +- Geometric data types (such as `LINE`, `PATH`, `POLYGON`) - `CIRCLE` - `CUBE` -- `JSON` +- `JSON` +- `JSONB` - `ROWID` +- `tsvector`, `tsquery`, `txid_snapshot`, `pg_lsn` - `SEG` - `Any ARRAY` data type (that is, defined as `data_type[]`) +- `ENUM`, composite type, range data type (such as `int4range`, `tstzrange`, `numrange`, `daterange`), `mcaddress8` - Any user-defined data type (that is, defined as `CREATE TYPE type_name`) +!!! note + Tables containing columns of datatype `mcaddress8` can be replicated from PostgreSQL to PostgreSQL. However, replication from PostgreSQL to EDB Postgres Advanced Server and between EDB Postgres Advanced Servers is not supported. + **Restrictions on Range Data Types** Postgres data types called range types were first supported in PostgreSQL version 9.2 and Advanced Server version 9.2. Built-in range types refer to the following built-in data types: `int4range, int8range, numrange, tsrange, tstzrange`, and `daterange`. diff --git a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx index ba8d2e452f9..40eaa45616e 100644 --- a/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx +++ b/product_docs/docs/eprs/6.2/03_installation/03_installing_rpm_package.mdx @@ -50,7 +50,7 @@ To install any of the packages, invoke the following command as the root account For example to install all xDB components, invoke the following: -`yum install ppas-xdb` +`yum install ppas-xdb --exclude edb-xdb` To install only the xDB Replication Console and xDB Replication Server Command Line Interface, invoke the following: @@ -126,12 +126,12 @@ gpgkey=file:///etc/pki/rpm-gpg/ENTERPRISEDB-GPG-KEY The following syntax installs the xDB RPM package: -`yum install ppas-xdb` +`yum install ppas-xdb --exclude edb-xdb` The following is an example: ```text -yum install ppas-xdb +yum install ppas-xdb --exclude edb-xdb Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile * base: centos.excellmedia.net @@ -271,8 +271,8 @@ Successful installation of xDB Replication Server results in the creation of dir If you have an existing xDB RPM installation, you can use yum to upgrade your repository configuration file and update to a more recent product version. To update the `edb.repo` file, assume superuser privileges and enter: -> `yum upgrade edb-repo` + `yum upgrade edb-repo` `yum` will update the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use yum to upgrade any installed packages: -> `yum upgrade ppas-xdb` + `yum upgrade ppas-xdb* --exclude edb-xdb*` diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/41_taking_mmr_snapshot.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/41_taking_mmr_snapshot.mdx index 01fcef8099a..c2c82cb3941 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/41_taking_mmr_snapshot.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/41_taking_mmr_snapshot.mdx @@ -1,13 +1,13 @@ --- -title: "Take a Multi-Master Snapshot (doMMRsnapshot)" +title: "Take a Multi-Master Snapshot (dommrsnapshot)" --- -**For MMR only:** The `doMMRsnapshot` command performs snapshot synchronization on the specified primary node in a multi-master replication system. +**For MMR only:** The `dommrsnapshot` command performs snapshot synchronization on the specified primary node in a multi-master replication system. ```text --doMMRsnapshot pubname +-dommrsnapshot pubname –repsvrfile pubsvrfile -pubhostdbid dbid [ -verboseSnapshotOutput { true | false } ] @@ -17,26 +17,26 @@ Parameters `pubname` -> The name of the publication for which the snapshot is to be taken. + The name of the publication for which the snapshot is to be taken. `pubsvrfile` -> The file containing the publication server login information. + The file containing the publication server login information. `dbid` -> The publication database ID of the target primary node for the snapshot replication. + The publication database ID of the target primary node for the snapshot replication. `-verboseSnapshotOutput` -> Set this option to true if you want the output from the snapshot to be displayed. Set this option to false if you do not want the snapshot output displayed. If omitted, the default is true. + Set this option to true if you want the output from the snapshot to be displayed. Set this option to false if you do not want the snapshot output displayed. If omitted, the default is true. Examples In the following example snapshot replication is performed on publication `emp_pub` to the target primary node identified by publication database `ID 9`. ```text -$ java -jar edb-repcli.jar -doMMRsnapshot emp_pub \ +$ java -jar edb-repcli.jar -dommrsnapshot emp_pub \ > -pubhostdbid 9 \ > -repsvrfile ~/pubsvrfile.prop Performing snapshot... diff --git a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/49_clean_shadow_table_history.mdx b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/49_clean_shadow_table_history.mdx index a112a7164a8..a269c852324 100644 --- a/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/49_clean_shadow_table_history.mdx +++ b/product_docs/docs/eprs/6.2/08_xdb_cli/03_xdb_cli_commands/49_clean_shadow_table_history.mdx @@ -11,7 +11,7 @@ Synopsis ```text -cleanshadowhistforpub pubname –repsvrfile pubsvrfile -[ -MMRdbid dbid_1[,dbid_2 ] ...] +[ -mmrdbid dbid_1[,dbid_2 ] ...] ``` See [Cleaning Up Shadow Table History](#clean_shadow_table_history) for additional information on cleaning up shadow table history. diff --git a/product_docs/docs/eprs/6.2/10_appendix/01_permitted_conf_and_permutations.mdx b/product_docs/docs/eprs/6.2/10_appendix/01_permitted_conf_and_permutations.mdx index 8a6ceca3fa1..b795d5fccbe 100644 --- a/product_docs/docs/eprs/6.2/10_appendix/01_permitted_conf_and_permutations.mdx +++ b/product_docs/docs/eprs/6.2/10_appendix/01_permitted_conf_and_permutations.mdx @@ -47,7 +47,7 @@ The following table shows the combinations of source and target database server | **Microsoft SQL Server** | No | No | Yes | Yes | Yes | | **PostgreSQL** | Yes | Yes | Yes | Yes | Yes | | **Advanced Server (Oracle compatible)** | Yes | Yes | No | Yes | No | -| **Advanced Server (PostgreSQL compatible)** | No | Yes | Yes | Yes | Yes | +| **Advanced Server (PostgreSQL compatible)** | Yes | Yes | Yes | Yes | Yes | In the preceding table, the left hand column lists the possible source database server products including the possible Advanced Server compatibility configuration modes. The top row lists the same set of possible target database server products and Advanced Server compatibility configuration modes. diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/13_eprs_rel_notes_6.2.16.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/13_eprs_rel_notes_6.2.16.mdx new file mode 100644 index 00000000000..9f2dde7da41 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/13_eprs_rel_notes_6.2.16.mdx @@ -0,0 +1,29 @@ +--- +title: "Version 6.2.16" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.16 include the following: + +| Type | Description | +| ----------- |------------ | +| Enhancement | Replication Server is certified to support PostgreSQL v14 and EDB Postgres Advanced Server v14. | +| Enhancement | Performance optimization for Synchronize operation when a MMR Publication has a SMR Subscription. [Support Ticket #74217] | +| Bug Fix | The `removepub` CLI command removes a Publication while it has one or more Subscriptions. This issue is fixed. [Support Ticket #72194] | +| Bug Fix | Fixed an issue where replication fails for the `UUID` data type in EDB Postgres Advanced Server to MS SQL Server permutation. [Support Ticket #73835] | +| Bug Fix | Fixed an issue where the Synchronize operation failed to replicate NULL for a BLOB type for EDB Postgres Advanced Server to Oracle. [Support Ticket #74057] | +| Bug Fix | Fixed case where wrong schema qualifier was picked up during history cleanup for EDB Postgres Advanced Server to Oracle and SQL Server permutations. [Support Ticket #72626] | +| Bug Fix | Fixed loading of Replication History on Replication Console after restart of Publication Services when SMR subscription is associated with a MMR Publication. [Support Ticket #74217] | +| Bug Fix | Fixed the upgrade issue related with the enhancement of shadow table triggers. [Support Ticket #74447] | +| Bug Fix | Fixed an issue where redundant INSERT conflicts were recorded when a new table was added in the MMR Publication. | +| Bug Fix | In a hybrid replication cluster, the cleanup shadow table routine is subject to remove unprocessed changes. This issue is fixed. | +| Bug Fix | The Synchronize replication fails while replicating changes for a multi-level List Partition table. This issue is fixed. | +| Bug Fix | Fixed the error where Snapshot fails for the third database in a MMR cluster. | +| Bug Fix | Fixed an error that prevented creation of a row-level Filter based on the `->` operator for JSONB data type. | +| Bug Fix | Fixed the issue related with the reporting of incorrect missing privileges while registering Oracle Publication database. | +| Bug Fix | In a hybrid cluster, batch is always applied using BUS (batch update using simple Statement) mode even when the user has opted for BUP mode (batch update using PreparedStatement). This issue is now fixed. | +| Bug Fix | Fixed an issue where an INSERT conflict in MMR Publication is subject to failure of Synchronize operation for a target SMR Subscription in a hybrid cluster. | +| Bug Fix | Fixed an issue so that a validation error is reported when the CLI command `createpub` is executed without registering a Publication database. | +| Bug Fix | Fixed the NoClassDefFoundError error (org/postgresql/replication/LogSequenceNumber) observed during data Snapshot operation for a RPM based installation on RHEL8/CENTOS8. | +| Bug Fix | Fixed the error `libpq JNI wrapper library is not available` that occured while adding a database for WAL based replication. + diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/14_eprs_rel_notes_6.2.15.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/14_eprs_rel_notes_6.2.15.mdx new file mode 100644 index 00000000000..8a74f70afb2 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/14_eprs_rel_notes_6.2.15.mdx @@ -0,0 +1,26 @@ +--- +title: "Version 6.2.15" +redirects: + - eprs_rel_notes +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.15 include the following: + +| Type | Description | +| ---- |------------ | +| Enhancement | Postgres Replication Server is now certified to support Oracle 18c and 19c as the Publication and Subscription database. | +| Bug Fix | Fixed an issue where adding the non-MDN node in the MMR cluster fails as the Constraint OID value exceeds the INTEGER range. [Support Ticket #911176]| +| Bug Fix | After upgrading to version 6.2.13, frequent wal_sender_timeouts were observed causing slowness in the replication, this issue is fixed. [Support Ticket #1273404] | +| Bug Fix | The Snapshot operation takes too long to complete as it unnecessarily reloads an already failed table, this issue is fixed [Support Ticket #1280541]| +| Bug Fix | Fixed an issue where Snapshot fails for a Publication table that is named after a reserved keyword [Support Ticket #1292121] | +| Bug Fix | In a corner case, the conflict detection gets stuck when the target database has multiple conflicts. This issue is fixed [Support Ticket #1318732]| +| Bug Fix | Fixed an issue where Publication creation fails for EPAS 9.6. [Support Ticket #72306]| +| Bug Fix | Fixed an issue that caused Synchronize replication failure due to a non-escaped quote character in the control event. [Support Ticket #72614]| +| Bug Fix | In a corner case, the CDC changes were skipped when the SMR Subscription database was also part of the MMR cluster. This issue is resolved. [Support Ticket #72353]| +| Bug Fix | Fixed an issue that caused “addtablesintopub” operation failure in a corner case when database OID value exceeded INTEGER range. [Support Ticket #72694]| +| Bug Fix | In a hybrid replication setup where EDB Postgres Advanced Server was registered with no-redwood-compat option (as a controller database in MMR and Oracle was registered as a Publication database in SMR), the Publication removal operation failed to complete. This issue is fixed. [Support Ticket #72469]| +| Bug Fix | SSL root file opening issue that is caused by JDBC driver after upgrading from version 6.2.5 to 6.2.6, is resolved. [Support Ticket #899996]| +| Bug Fix | Rep CLI `createpub` command failed when the Filter index was greater than 9. This issue is fixed.| +| Bug Fix | Fixed an issue where Synchronize replication fails when Filter contains a modulus operator.| +| Bug Fix | Fixed an issue that caused `addtablesintopub` command failure for a table name with multiple $ characters.| diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/15_eprs_rel_notes_6.2.14.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/15_eprs_rel_notes_6.2.14.mdx new file mode 100644 index 00000000000..ec1f6ff4254 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/15_eprs_rel_notes_6.2.14.mdx @@ -0,0 +1,24 @@ +--- +title: "Version 6.2.14" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.14 include the following: + +| Type | Description | +| ---- |------------ | +| Enhancement | Added support for replication of Oracle XMLType column. [Support Ticket #1129386] | +| Enhancement | Added support to allow an MMR (trigger-based) Publication to be Subscribed in a SMR cluster. | +| Enhancement | Improved replication processing to cater for a corner case when large transactions are rolled back in MMR trigger-based setup causing delay in replication speed. [Support Ticket #1247976] | +| Enhancement | Enhanced xDB to support Subscription for a table having name longer than 30 characters length from EDB Postgres Advanced Server to Oracle 12.2 or later versions. [Support Ticket #1280206] | +| Bug Fix | Fixed Java heap space error when performing sync for a single row containing data > 100MB. | +| Bug Fix | Fixed issue of replication failure when user modifies an Oracle table column that is part of a Filter and PK column is of DATE/TIMESTAMP type. [Support Ticket #1207460] | +| Bug Fix | Fixed replication failure caused by change in Oracle XMLType column value that is part of a Filter. | +| Bug Fix | Fixed a corner case that is subject to replication failure if PK column ordinal position is after a LOB column in an Oracle Publication table. | +| Bug Fix | Fixed NPE case when cleanup job is fired while no Publication is defined yet [Support Ticket #1007131]. | +| Bug Fix | Fixed an issue that causes Sync operation get stuck due to Thread Deadlock. | +| Bug Fix | [EPAS to Oracle] Fixed an issue related with Subscription failure when table contains boolean type column. [Support Ticket #1280206] | +| Bug Fix | [EPAS to Oracle] Fixed an issue related with Subscription failure when table contains XML/XMLType column. | +| Bug Fix | Fixed an issue when a non-reserved keyword as column name causes exception in WAL parsing. [Support Ticket #1281560] | +| Bug Fix | Corrected the behavior of useFastCopy flag that was always enabled even when user turned it off. | +| Bug Fix | Fixed the issue where in trigger-mode, the UPDATE operation is denied on an EPAS Publication table with XMLType column. diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/16_eprs_rel_notes_6.2.13.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/16_eprs_rel_notes_6.2.13.mdx new file mode 100644 index 00000000000..3141aac42ba --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/16_eprs_rel_notes_6.2.13.mdx @@ -0,0 +1,20 @@ +--- +title: "Version 6.2.13" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.13 include the following: + +| Type | Description | +| ----------- |------------ | +| Bug Fix | Fixed the issue where TRUNCATE operation is captured only for parent partition table. [Support Ticket #1140685] | +| Bug Fix | Fixed the issue where xDB process intermittently crashes on Windows due to invalid libpq connection. [Support Ticket #1165973] | +| Bug Fix | Fixed the issue where user is getting duplicate key violates unique constraint "xdb_mmr_pub_group_pkey" error in non-MDN database server log. [Support Ticket #1039627] | +| Bug Fix | Fixed a corner case where processed data might not be removed from shadow tables for Oracle to EPAS permutation. [Support Ticket #1038941] | +| Bug Fix | Fixed the issue where WAL based Publication table filter does not work with negative integer. | +| Bug Fix | Fixed the issue where xDB might skip CDC changes after Snapshot, when exported Snapshot id occurs around transaction wrap-around boundary value. | +| Bug Fix | Apache Commons Collections libraries are updated to cater for possible security risks. | + + + + diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/17_eprs_rel_notes_6.2.12.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/17_eprs_rel_notes_6.2.12.mdx new file mode 100644 index 00000000000..3c5087827d6 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/17_eprs_rel_notes_6.2.12.mdx @@ -0,0 +1,20 @@ +--- +title: "Version 6.2.12" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.12 include the following: + +| Type | Description | +| ----------- |------------ | +| Enhancement | Replication Server supports PostgreSQL or EDB Postgres Advanced Server v13 both as a Publication and Subscription for SMR and MMR replication configurations. | +| Bug Fix | Fixed the issue where the cleanup job is unable to remove processed data from the shadow tables. [Support Ticket #1067057] | +| Bug Fix | Fixed the error where properties file containing user password created for Snapshot operation is not removed. [Support Ticket #947894] | +| Bug Fix | Fixed the issue where WAL streaming sticks due to a deadlock introduced after a network failure. | +| Bug Fix | Fixed the corner case issue where Replication Server failed to send LSN Acknowledgement to the database server. [Support Ticket #1018300, #1019154] | +| Bug Fix | Corrected the row level filter criteria execution based on JSON attributes for WAL mode replication. [Support Ticket #1044051] | +| Bug Fix | Fixed the installation issue observed on Windows 2012 in Azure environment. [Support Ticket #1032966] | +| Bug Fix | Resolved the Snapshot failure case when the source database connection is invalidated in a long running Snapshot session. [Support Ticket #1049973] | + + + diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/18_eprs_rel_notes_6.2.11.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/18_eprs_rel_notes_6.2.11.mdx new file mode 100644 index 00000000000..0a68a6a9666 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/18_eprs_rel_notes_6.2.11.mdx @@ -0,0 +1,16 @@ +--- +title: "Version 6.2.11" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.11 include the following: + +| Type | Description | +| ----------- |------------ | +| Bug ix | Replication performance degrades significantly when there are a large number of conflicts, resulting in sync slowing down as more and more tx sets pile up for conflict resolution. [Support Ticket #927590] | +| Bug Fix | Synchronize operation fails due to UnsupportedCharsetException for WIN1252 encoding. [Support Ticket #1022536] | +| Bug Fix | The data is not replicated to the target node after performing the Synchronize operation when the table name contains multi-bytes Japanese characters. [Support Ticket #993951] | + + + + diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/19_eprs_rel_notes_6.2.10.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/19_eprs_rel_notes_6.2.10.mdx new file mode 100644 index 00000000000..7bb96739187 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/19_eprs_rel_notes_6.2.10.mdx @@ -0,0 +1,21 @@ +--- +title: "Version 6.2.10" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.10 include the following: + +| Type | Description | +| ----------- |------------ | +| Bug Fix | Fixed error that caused data Snapshot failure for a table name with Japanese characters. [Support Ticket #993951] | +| Bug Fix | Fixed duplicate key error for conflicts with unique constraint “xdb_conflicts_pkey” failure. [Support Ticket #998952] | +| Bug Fix | Updated PostgreSQL/Advanced Server JDBC driver to version 42.2.9.| +| Bug Fix | Fixed an issue where a Publication database cannot register with dbtype "enterprisedb". | +| Bug Fix | Fixed redundant logging related with custom EUC_JP encoding. | +| Bug Fix | Exposed an option to turn off logging of table level history stats. [Support Ticket #927590] | +| Bug Fix | Resolved periodic Synchronisation stuck error when a database connection failure occurs. [Support Ticket #1002089] | +| Bug Fix | Fixed an issue where a column name with multi-byte character(s) is incorrectly flagged as case sensitive. [Support Ticket #1002319] | + + + + diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/20_eprs_rel_notes_6.2.9.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/20_eprs_rel_notes_6.2.9.mdx new file mode 100644 index 00000000000..4a451294146 --- /dev/null +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/20_eprs_rel_notes_6.2.9.mdx @@ -0,0 +1,23 @@ +--- +title: "Version 6.2.9" +--- + + +New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server 6.2.9 include the following: + +| Type | Description | +| ---- |------------ | +| Bug Fix | The execution time of RepCLI dosyncronize command is improved. [Support Ticket #936411] | +| Bug Fix | Synchronize replication fails if table column name contains a space. [Support Ticket #929731] | +| Bug Fix | Synchronize replication fails for EUC-JP encoding. [Support Ticket #929731] | +| Bug Fix | Synchronize replication might fail for an UPDATE transaction after a drop column via alter table. | +| Bug Fix | Shadow table cleanup is subject to remove unprocessed changes. [Support Ticket #966253] | +| Bug Fix | In Ora 2 PG/EPAS permutation, delta changes might skip in a corner case. [Support Ticket #966253] | +| Bug Fix | Replication breaks for Oracle partition tables. [Support Ticket #966575] | +| Bug Fix | Clean up shadow table history not working. [Support Ticket #927162] | +| Bug Fix | For Ora to EPAS permutation, replication of TIMESTAMP (6) truncates leading 0 of decimal places. [Support Ticket #974690] | +| Bug Fix | Adding a new table in MMR Publication might skip certain CDC changes introduced on target non-MDN Master database. [Support Ticket #979202] | +| Bug Fix | Fixed a Snapshot failure for JSONB array type. [Support Ticket #964245] | +| Bug Fix | Synchronize operation incorrectly attempts to use a non-existent replication slot while Snapshot operation is in progress. [Support Ticket #959229] | +| Bug Fix | Upgrading from xDB 6.2.5 to xDB 6.2.8 causes services to fail with SSL error. [Support Ticket #982469] | + diff --git a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx index 9b8c7ac70bf..8afab0e70d1 100644 --- a/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx +++ b/product_docs/docs/eprs/6.2/eprs_rel_notes/index.mdx @@ -4,25 +4,19 @@ redirects: - ../01_whats_new/ --- -The EDB Postgres Replication Server (EPRS) documentation describes the latest version of EDB Postgres Replication Server (EPRS) 6.2.15 including minor releases and patches. The release notes in this section provide information on what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators within the content about what release introduced the feature. +The EDB Postgres Replication Server documentation describes the latest version of EDB Postgres Replication Server 6.2 including minor releases and patches. The release notes in this section provide information on what was new in each release. For new functionality introduced in a minor or patch release, there are also indicators within the content about what release introduced the feature. -New features, enhancements, bug fixes, and other changes in EDB Postgres Replication Server (EPRS) 6.2.15 include the following: -| Type | Description | -| ---- |------------ | -| Enhancement | The EDB Postgres Replication Server is now certified to support Oracle 18c and 19c as the Publication and Subscription database. | -| Bug Fix | Fixed an issue where adding the non-MDN node in the MMR cluster fails as the Constraint OID value exceeds the INTEGER range [911176].| -| Bug Fix | After upgrading to version 6.2.13, frequent wal_sender_timeouts were observed causing slowness in the replication, this issue is fixed [1273404]. | -| Bug Fix | The Snapshot operation takes too long to complete as it unnecessarily reloads an already failed table, this issue is fixed [1280541].| -| Bug Fix | Fixed an issue where Snapshot fails for a Publication table that is named after a reserved keyword [1292121]. | -| Bug Fix | In a corner case, the conflict detection gets stuck when the target database has multiple conflicts. This issue is fixed [1318732].| -| Bug Fix | Fixed an issue where Publication creation fails for EPAS 9.6 [72306].| -| Bug Fix | Fixed an issue that caused Synchronize replication failure due to a non-escaped quote character in the control event [72614].| -| Bug Fix | In a corner case, the CDC changes were skipped when the SMR Subscription database was also part of the MMR cluster. This issue is resolved [72353].| -| Bug Fix | Fixed an issue that caused “addtablesintopub” operation failure in a corner case when database OID value exceeded INTEGER range [72694].| -| Bug Fix | In a hybrid replication setup where EDB Postgres Advanced Server was registered with no-redwood-compat option (as a controller database in MMR and Oracle was registered as a Publication database in SMR), the Publication removal operation failed to complete. This issue is fixed [72469].| -| Bug Fix | SSL root file opening issue that is caused by JDBC driver after upgrading from version 6.2.5 to 6.2.6, is resolved [899996].| -| Bug Fix | Rep CLI `createpub` command failed when the Filter index was greater than 9. This issue is fixed.| -| Bug Fix | Fixed an issue where Synchronize replication fails when Filter contains a modulus operator.| -| Bug Fix | Fixed an issue that caused `addtablesintopub` command failure for a table name with multiple $ characters.| +| Version | Release Date | +| ------- | ------------ | +| [6.2.16](13_eprs_rel_notes_6.2.16) | 2021 Dec 09 | +| [6.2.15](14_eprs_rel_notes_6.2.15) | 2021 Aug 30 | +| [6.2.14](15_eprs_rel_notes_6.2.14) | 2021 May 27 | +| [6.2.13](16_eprs_rel_notes_6.2.13) | 2021 Feb 18 | +| [6.2.12](17_eprs_rel_notes_6.2.12) | 2020 Nov 16 | +| [6.2.11](18_eprs_rel_notes_6.2.11) | 2020 Aug 28 | +| [6.2.10](19_eprs_rel_notes_6.2.10) | 2020 Jun 11 | +| [6.2.9](20_eprs_rel_notes_6.2.9) | 2020 May 07 | + + diff --git a/product_docs/docs/eprs/7.0/10_appendix/01_permitted_conf_and_permutations.mdx b/product_docs/docs/eprs/7.0/10_appendix/01_permitted_conf_and_permutations.mdx index da64a4094a0..b6ea22bf087 100644 --- a/product_docs/docs/eprs/7.0/10_appendix/01_permitted_conf_and_permutations.mdx +++ b/product_docs/docs/eprs/7.0/10_appendix/01_permitted_conf_and_permutations.mdx @@ -47,7 +47,7 @@ The following table shows the combinations of source and target database server | **Microsoft SQL Server** | No | No | Yes | Yes | Yes | | **PostgreSQL** | Yes | Yes | Yes | Yes | Yes | | **Advanced Server (Oracle compatible)** | Yes | Yes | No | Yes | No | -| **Advanced Server (PostgreSQL compatible)** | No | Yes | Yes | Yes | Yes | +| **Advanced Server (PostgreSQL compatible)** | Yes | Yes | Yes | Yes | Yes | In the preceding table, the left hand column lists the possible source database server products including the possible Advanced Server compatibility configuration modes. The top row lists the same set of possible target database server products and Advanced Server compatibility configuration modes. diff --git a/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx index cc7e0185f7c..d0bd6beaf72 100644 --- a/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/54/05_installing_mtk.mdx @@ -556,6 +556,6 @@ A dialog confirms that the Migration Toolkit installation is complete; click `Fi Before invoking Migration Toolkit, you must download and install a freely available source-specific driver. To download a driver, or for a link to a vendor download site, visit the `Third Party JDBC Drivers` section of the `Advanced Downloads` page at the EnterpriseDB website: - + After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/migration_toolkit/54/index.mdx b/product_docs/docs/migration_toolkit/54/index.mdx index 90493ce70c9..48be27102ca 100644 --- a/product_docs/docs/migration_toolkit/54/index.mdx +++ b/product_docs/docs/migration_toolkit/54/index.mdx @@ -27,7 +27,7 @@ You can also use Migration Toolkit to migrate database objects and data from Syb You can install Migration Toolkit with the EDB Postgres Advanced Server installer, or via Stack Builder. Stack Builder is distributed with both the EDB Postgres Advanced Server and the PostgreSQL one-click installer available from the EnterpriseDB web site at: - + This guide provides a high-level description of the steps involved in the migration process, as well as installation and usage instructions for Migration Toolkit. It also includes solutions to common migration problems, and details unsupported features and their potential workarounds. diff --git a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx index e7d9bb77b17..f4d2a700d92 100644 --- a/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx +++ b/product_docs/docs/migration_toolkit/55/05_installing_mtk.mdx @@ -553,6 +553,6 @@ A dialog confirms that the Migration Toolkit installation is complete; click `Fi Before invoking Migration Toolkit, you must download and install a freely available source-specific driver. To download a driver, or for a link to a vendor download site, visit the `Third Party JDBC Drivers` section of the `Advanced Downloads` page at the EnterpriseDB website: - + After downloading the source-specific driver, move the driver file into the `/lib` directory. diff --git a/product_docs/docs/migration_toolkit/55/index.mdx b/product_docs/docs/migration_toolkit/55/index.mdx index 13a6cdaaec4..5e894faa638 100644 --- a/product_docs/docs/migration_toolkit/55/index.mdx +++ b/product_docs/docs/migration_toolkit/55/index.mdx @@ -18,7 +18,7 @@ You can also use Migration Toolkit to migrate database objects and data from Syb You can install Migration Toolkit with the EDB Postgres Advanced Server installer, or via Stack Builder. Stack Builder is distributed with both the EDB Postgres Advanced Server and the PostgreSQL one-click installer available from the EnterpriseDB web site at: - + This guide provides a high-level description of the steps involved in the migration process, as well as installation and usage instructions for Migration Toolkit. It also includes solutions to common migration problems, and details unsupported features and their potential workarounds. diff --git a/product_docs/docs/pem/8/images/pem_server_web_properties_member_of.png b/product_docs/docs/pem/8/images/pem_server_web_properties_member_of.png index 3a5c2931a32..4449bf03cc8 100644 --- a/product_docs/docs/pem/8/images/pem_server_web_properties_member_of.png +++ b/product_docs/docs/pem/8/images/pem_server_web_properties_member_of.png @@ -1,3 +1,3 @@ version https://git-lfs.github.com/spec/v1 -oid sha256:8a14b58dcac9c570be212ee20d7032c531abc0746e31f9322f564c9786a3ddb6 -size 212427 +oid sha256:cb48d5a010005454d9ee76f6b2a1aff7b7fe9108b98f75232649230ae0ee744c +size 184881 diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx index 6d99ebffc24..c047fc11a8a 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/06_configuring_the_pem_server_to_use_kerberos_authentication.mdx @@ -89,7 +89,26 @@ chown enterprisedb /.keytab - `DATA_DIRECTORY_OF_POSTGRES` is the path of the data directory of the installed postgres (PostgreSQL/EDB Postgres Advanced Server. -- Restart the database server to have the effect of changes +- Edit the krb5.conf file + + ```text + $ sudo vim /etc/krb5.conf + [libdefaults] + default_realm = EDBPEM.ORG + Forwardable = True + + [domain_realm] + .edbpem.org = EDBPEM.ORG + edbpem.org = EDBPEM.ORG + + [realms] + EDBPEM.ORG = { + kdc = krb5server.edbpem.org + admin_server = krb5server.edbpem.org + } + ``` + +- Restart the database server to reflect the changes ```text systemctl restart @@ -99,7 +118,26 @@ chown enterprisedb /.keytab - `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL platforms. -## 5. Configure the PEM Server +## 5. Obtain and view the initial ticket + +- The `kinit` utility obtains and caches Kerberos tickets. This utility is typically used to obtain the ticket-granting ticket, using a password entered by the user to decrypt the credential from the key distribution center (KDC). The ticket-granting ticket is then stored in the user's credential cache. + +- You can view the details of the ticket using `klist` utility. + +!!! Note + The `Kerberos Client` must be installed on the PEM Server and the Client machine to use `kinit` and `klist`. + +```text +$ kinit +$ klist +``` + +It will display the principal along with the Kerberos ticket. + +!!! Note + The `USERNAME@REALM` specified here must be a database user having the `pem_admin` role and `CONNECT` privilege on `pem` database. + +## 6. Configure the PEM Server - Run the PEM configure script on the PEM Server to use Kerberos Authentication @@ -150,24 +188,6 @@ chown enterprisedb /.keytab !!! Note If you are using PostgreSQL OR EDB Postgres Advanced Server 12 or later then you can specify connection type as `hostgssenc` to allow only gss encrypted connection. -## 6. Obtain and view the initial ticket - -- The `kinit` utility obtains and caches Kerberos tickets. This utility is typically used to obtain the ticket-granting ticket, using a password entered by the user to decrypt the credential from the key distribution center (KDC). The ticket-granting ticket is then stored in the user's credential cache. - -- You can view the details of the ticket using `klist` utility. - -!!! Note - The `Kerberos Client` must be installed on the PEM Server and the Client machine to use `kinit` and `klist`. - -```text -$ kinit -$ klist -``` - -It will display the principal along with the kerberos ticket. - -!!! Note - The `USERNAME@REALM` specified here must be the database user having the `pem_admin` role and `CONNECT` privilege on `pem` database. ## 7. Browser Settings @@ -195,3 +215,12 @@ Configure the Browser on the Client machine to access the PEM Web Client to use ```text https://:8443/pem ``` + +!!! Note + If you run into the following error while connecting to your Postgres cluster: + + `psql -h hostname template1` + `psql: GSSAPI continuation error: Unspecified GSS failure. Minor code may provide more information` + `GSSAPI continuation error: Key version is not available` + + The resolution is to add the additional encryption types to the keytab using `ktutil` or recreating the Postgres keytab with all crypto systems from AD. \ No newline at end of file diff --git a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx index f8c2fc1b202..416a2bc6aae 100644 --- a/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx +++ b/product_docs/docs/pem/8/pem_inst_guide_linux/04_installing_postgres_enterprise_manager/07_configuring_the_pem_server_to_use_windows_kerberos_server.mdx @@ -39,12 +39,7 @@ Follow the steps to configure the Kerberos Authentication for the PEM Server: ![Active Directory Users and Computers User Details](../../images/active_directory_users_and_computers_user_details.png) - e. On the `PEMServer Web Properties`, add the Users as member of the following groups: - - - Domain Admins - - Domain Users - - Enterprise Admins - - Schema Admins + e. On the `PEMServer Web Properties`, add the Users as member of the `Domain Users` group: ![PEM Server Web Properties](../../images/pem_server_web_properties_member_of.png) @@ -59,13 +54,13 @@ Follow the steps to configure the Kerberos Authentication for the PEM Server: a. Open `Windows PowerShell` as an `Administrator` user, create a Key Table for HTTP Service Principal mapping with user `pemserverweb` and a Key Table for Postgres Service Principal mappping with user `pemserverdb`. ```text -> ktpass /out pemserver.keytab /princ HTTP/pem.edbpem.internal@EDBPEM.INTERNAL /mapuser pemserverweb /crypto AES256-SHA1 +rndpass /target EDBPEM.INTERNAL -ptype KRB5_NT_PRINCIPAL -> ktpass /out pemdb.keytab /princ postgres/pem.edbpem.internal@EDBPEM.INTERNAL /mapuser pemserverdb /crypto AES256-SHA1 +rndpass /target EDBPEM.INTERNAL -ptype KRB5_NT_PRINCIPAL +ktpass /out pemserver.keytab /princ HTTP/pem.edbpem.internal@EDBPEM.INTERNAL /mapuser pemserverweb /crypto AES256-SHA1 +rndpass /target EDBPEM.INTERNAL -ptype KRB5_NT_PRINCIPAL +ktpass /out pemdb.keytab /princ postgres/pem.edbpem.internal@EDBPEM.INTERNAL /mapuser pemserverdb /crypto AES256-SHA1 +rndpass /target EDBPEM.INTERNAL -ptype KRB5_NT_PRINCIPAL ``` Where, -- `pemserver.keytab` is the name of the Key Table for the PEM Web Apllication +- `pemserver.keytab` is the name of the Key Table for the PEM Web Application - `pemdb.keytab` is the name of the key Table for the PEM Backend Database Server - `pem.edbpem.internal@EDBPEM.INTERNAL` is the hostname of the PEM Server (here @EDBPEM.INTERNAL means @REALM) - `pemserverweb` is the user for the PEM Web Application @@ -90,7 +85,7 @@ c. Select `Trust this user for delegation to any service (Kerberos only)` option d. Copy both the Key Tables to the PEM Server Host (or respectively to PEM Web Server and PEM Backend Database Server hosts if installed on different hosts.) -e. On the PEM Server, move the Key Tables to required location and change the ownership as following: +e. On the PEM Server, move the Key Tables to the required location and change the ownership as following: ```text mv /tmp/pemserver.keytab /share @@ -119,7 +114,26 @@ chown enterprisedb /pemdb.keytab - `DATA_DIRECTORY_OF_POSTGRES` is the path of the data directory of the installed postgres (PostgreSQL/EDB Postgres Advanced Server. -- Restart the database server to have the effect of changes +- Edit the `krb5.conf` file: + + ```text + $ sudo vim /etc/krb5.conf + [libdefaults] + default_realm = EDBPEM.INTERNAL + Forwardable = True + + [domain_realm] + .edbpem.org = EDBPEM.INTERNAL + edbpem.org = EDBPEM.INTERNAL + + [realms] + EDBPEM.INTERNAL = { + kdc = krb5server.edbpem.internal + admin_server = krb5server.edbpem.internal + } + ``` + +- Restart the database server to reflect the changes ```text systemctl restart @@ -129,7 +143,26 @@ chown enterprisedb /pemdb.keytab - `POSTGRES_SERVICE_NAME` is the service name of Postgres (PostgreSQL/EDB Postgres Advanced Server) database. For eg: postgresql-13 for PostgreSQL 13 database on CentOS or RHEL platforms. -## 5. Configure the PEM Server +## 5. Obtain and view the initial ticket + +- The `kinit` utility obtains and caches Kerberos tickets. This utility is typically used to obtain the ticket-granting ticket, using a password entered by the user to decrypt the credential from the key distribution center (KDC). The ticket-granting ticket is then stored in the user's credential cache. + +- You can view the details of the ticket using `klist` utility. + +!!! Note + The `Kerberos Client` must be installed on the PEM Server and the Client machine to use `kinit` and `klist`. + +```text +$ kinit +$ klist +``` + +It will display the principal along with the kerberos ticket. + +!!! Note + The `USERNAME@REALM` specified here must be a database user having the `pem_admin` role and `CONNECT` privilege on `pem` database. + +## 6. Configure the PEM Server - Run the PEM configure script on the PEM Server to use Kerberos Authentication @@ -180,7 +213,7 @@ chown enterprisedb /pemdb.keytab !!! Note You cannot specify connection type as `hostgssenc` as windows does not support gss encrypted connection. -## 6. Browser Settings +## 7. Browser Settings Configure the Browser on the Client machine to access the PEM Web Client to use the `Spnego/Kerberos`. @@ -206,3 +239,12 @@ Configure the Browser on the Client machine to access the PEM Web Client to use ```text https://:8443/pem ``` + +!!! Note + If you run into the following error while connecting to your Postgres cluster: + + `psql -h hostname template1` + `psql: GSSAPI continuation error: Unspecified GSS failure. Minor code may provide more information` + `GSSAPI continuation error: Key version is not available` + + The resolution is to add the additional encryption types to the keytab using `ktutil` or recreating the Postgres keytab with all crypto systems from AD.