From ae77d228e2258c46e4875ddfaef81f56c5fb8ff5 Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Wed, 13 Nov 2024 16:47:14 +0000 Subject: [PATCH 01/65] Add pem-port to options table --- product_docs/docs/pem/9/registering_database_server.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/product_docs/docs/pem/9/registering_database_server.mdx b/product_docs/docs/pem/9/registering_database_server.mdx index 62d742913a5..b871b5d1474 100644 --- a/product_docs/docs/pem/9/registering_database_server.mdx +++ b/product_docs/docs/pem/9/registering_database_server.mdx @@ -56,6 +56,7 @@ Append command line options to the command string when invoking the pemworker ut | Option                           | Description | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `--pem-user` | Specifies the name of the PEM administrative user (must have the pem_admin role) on the PEM server to use to write the server details to the PEM database. Required. | +| `--pem-port` | Specifies the port on which to connect to the PEM server when writing the server details to the PEM database. Optional, defaults to the value of `--pem-port` set during agent registration (PEM 9.8 or newer, only). Otherwise defaults to 5432. | | **Server parameters** | These parameters are used to populate the connection properties in the PEM web application. They're used when a user connects from the PEM web application to the monitored server. They're also used for connections from the agent to the monitored server unless overridden by Agent Server Binding parameters (see the **Agent-server binding parameters** in this table). | | `--server-addr` | Specifies the IP address or fully qualified domain name of the monitored server. On Linux systems, you can leave the address field blank to use the default PostgreSQL Unix Domain Socket on the local machine. Or you can set it to an alternative path containing a PostgreSQL socket. If you enter a path, the path must begin with a forward slash (/). Required. | | `--server-port` | Specifies the port number of the monitored server. Required. | From a83fe6b91863497dcfbc74d54285171fbc97bb98 Mon Sep 17 00:00:00 2001 From: Simon Notley <43099400+sonotley@users.noreply.github.com> Date: Wed, 13 Nov 2024 16:50:00 +0000 Subject: [PATCH 02/65] Update product_docs/docs/pem/9/registering_database_server.mdx --- product_docs/docs/pem/9/registering_database_server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/registering_database_server.mdx b/product_docs/docs/pem/9/registering_database_server.mdx index b871b5d1474..4c0cf858432 100644 --- a/product_docs/docs/pem/9/registering_database_server.mdx +++ b/product_docs/docs/pem/9/registering_database_server.mdx @@ -56,7 +56,7 @@ Append command line options to the command string when invoking the pemworker ut | Option                           | Description | | ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `--pem-user` | Specifies the name of the PEM administrative user (must have the pem_admin role) on the PEM server to use to write the server details to the PEM database. Required. | -| `--pem-port` | Specifies the port on which to connect to the PEM server when writing the server details to the PEM database. Optional, defaults to the value of `--pem-port` set during agent registration (PEM 9.8 or newer, only). Otherwise defaults to 5432. | +| `--pem-port` | Specifies the port on which to connect to the PEM server when writing the server details to the PEM database. Optional, defaults to the value of `--pem-port` set during agent registration (PEM 9.8 or newer only). Otherwise defaults to 5432. | | **Server parameters** | These parameters are used to populate the connection properties in the PEM web application. They're used when a user connects from the PEM web application to the monitored server. They're also used for connections from the agent to the monitored server unless overridden by Agent Server Binding parameters (see the **Agent-server binding parameters** in this table). | | `--server-addr` | Specifies the IP address or fully qualified domain name of the monitored server. On Linux systems, you can leave the address field blank to use the default PostgreSQL Unix Domain Socket on the local machine. Or you can set it to an alternative path containing a PostgreSQL socket. If you enter a path, the path must begin with a forward slash (/). Required. | | `--server-port` | Specifies the port number of the monitored server. Required. | From afa76089d2ef5a9be26ccb9dfe732ee4dab39a42 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 14 Nov 2024 12:34:55 +0530 Subject: [PATCH 03/65] PEM 9.8 - release branch --- .../pem/9/pem_rel_notes/980_rel_notes.mdx | 18 ++++++++++ .../docs/pem/9/pem_rel_notes/index.mdx | 34 ++++++++++--------- 2 files changed, 36 insertions(+), 16 deletions(-) create mode 100644 product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx diff --git a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx new file mode 100644 index 00000000000..1d036bd0425 --- /dev/null +++ b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx @@ -0,0 +1,18 @@ +--- +title: "Postgres Enterprise Manager 9.8.0 release notes" +navTitle: Version 9.8.0 +--- + +Released: 19th Nov 2024 + +New features, enhancements, bug fixes, and other changes in PEM 9.8.0 include: + +| Type | Description | +|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------| +| Enhancement | Added support for EDB Advanced Server, EDB Postgres Distributed, and PostgreSQL 17. | +| Enhancement | Added support for RHEL9 ARM64 platform. | +| Enhancement | Added support to allow sslmode connections from PEM agent to PEM server. | +| Bug fix | Fixed an issue for PEM port while registering the server. Now `pemworker` picks up the PEM port from the agent config file while registering the server. | +| Bug fix | Fixed an issue where PEM agent installation on Windows was failing if a `%` character was used to set the service for the agent. | +| Bug fix | Fixed an issue where data was not purged as job id 2 was missing. | +| Bug fix | Fixed an issue for displaying errors on EINTR signal. Now spoolers `select()` error will be displayed on EINTR signal only when log level is set to INFO. | diff --git a/product_docs/docs/pem/9/pem_rel_notes/index.mdx b/product_docs/docs/pem/9/pem_rel_notes/index.mdx index 652a9654806..69890c99b51 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/index.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/index.mdx @@ -1,6 +1,7 @@ --- title: "Release notes" navigation: + - 980_rel_notes - 970_rel_notes - 960_rel_notes - 951_rel_notes @@ -19,22 +20,23 @@ navigation: The Postgres Enterprise Manager (PEM) documentation describes the latest version of PEM 9 including minor releases and patches. The release notes in this section provide information on what was new in each release. For new functionality introduced after 8.0.0 in a minor or patch release, there are also indicators within the content about what release introduced the feature. -| Version | Release Date | Upstream Merges | Accessibility Conformance | -| ------------------------- | ------------ | --------------------------------------------------------------------------| --------------------------------------------------------------------------------------------------- | -| [9.7.0](970_rel_notes) | 13 Aug 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.6.0](960_rel_notes) | 15 May 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.5.1](951_rel_notes) | 04 Mar 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.5.0](950_rel_notes) | 15 Feb 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.4.1](941_rel_notes) | 28 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.4.0](940_rel_notes) | 16 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.3.1](931_rel_notes) | 12 Oct 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.3.0](930_rel_notes) | 31 Aug 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.2.2](922_rel_notes) | 14 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.2.1](921_rel_notes) | 03 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.2.0](920_rel_notes) | 24 May 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.1.1](911_rel_notes) | 31 Mar 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.1.0](910_rel_notes) | 14 Feb 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | -| [9.0.0](900_rel_notes) | 9 Dec 2022 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| Version | Release Date | Upstream Merges | Accessibility Conformance | +|------------------------|--------------|-----------------|------------------------------------------------------------------| +| [9.8.0](980_rel_notes) | 19 Nov 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.7.0](970_rel_notes) | 13 Aug 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.6.0](960_rel_notes) | 15 May 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.5.1](951_rel_notes) | 04 Mar 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.5.0](950_rel_notes) | 15 Feb 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.4.1](941_rel_notes) | 28 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.4.0](940_rel_notes) | 16 Nov 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.3.1](931_rel_notes) | 12 Oct 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.3.0](930_rel_notes) | 31 Aug 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.2.2](922_rel_notes) | 14 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.2.1](921_rel_notes) | 03 Jul 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.2.0](920_rel_notes) | 24 May 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.1.1](911_rel_notes) | 31 Mar 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.1.0](910_rel_notes) | 14 Feb 2023 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.0.0](900_rel_notes) | 9 Dec 2022 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | Often only select issues are included in the upstream merges. The specific issues included in the merges are listed in the release note topics. From ad99eac69f904fd6508d28eb382764ab2d945811 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 19 Nov 2024 10:57:40 +0530 Subject: [PATCH 04/65] Update product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx Co-authored-by: Simon Notley <43099400+sonotley@users.noreply.github.com> --- product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx index 1d036bd0425..06b69288f5b 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx @@ -14,5 +14,5 @@ New features, enhancements, bug fixes, and other changes in PEM 9.8.0 include: | Enhancement | Added support to allow sslmode connections from PEM agent to PEM server. | | Bug fix | Fixed an issue for PEM port while registering the server. Now `pemworker` picks up the PEM port from the agent config file while registering the server. | | Bug fix | Fixed an issue where PEM agent installation on Windows was failing if a `%` character was used to set the service for the agent. | -| Bug fix | Fixed an issue where data was not purged as job id 2 was missing. | +| Bug fix | Fixed an issue where some historical probe data was not purged because the system job that tracks data for purging would be erroneously deleted by another system job. | | Bug fix | Fixed an issue for displaying errors on EINTR signal. Now spoolers `select()` error will be displayed on EINTR signal only when log level is set to INFO. | From f06da5bb168e8df0caf2a6bb72dcc2bb5d05ab1d Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 19 Nov 2024 10:58:24 +0530 Subject: [PATCH 05/65] Update product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx Co-authored-by: Simon Notley <43099400+sonotley@users.noreply.github.com> --- product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx index 06b69288f5b..289fb16e752 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx @@ -4,6 +4,12 @@ navTitle: Version 9.8.0 --- Released: 19th Nov 2024 +!!! Note +This release contains a fix for a bug that prevented some historical data from being correctly purged when its configured retention time expired. +Therefore, it is likely that the first purge job to run after this update will delete more data than usual and may take longer to complete. +The purge job should start within 3 hours of the upgrade. +You may also notice that the total size of your PEM database shrinks significantly once this job and subsequent vacuuming is complete. +!!! New features, enhancements, bug fixes, and other changes in PEM 9.8.0 include: From a2421ac7c46261c253c1aa74c77629955dd8ca59 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 19 Nov 2024 12:02:53 +0530 Subject: [PATCH 06/65] Reworded the note on release notes page and added --pem-ssl-mode parameter to the docs --- .../pem/9/pem_rel_notes/980_rel_notes.mdx | 7 ++-- product_docs/docs/pem/9/registering_agent.mdx | 41 ++++++++++--------- 2 files changed, 24 insertions(+), 24 deletions(-) diff --git a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx index 289fb16e752..260a735f006 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx @@ -5,10 +5,9 @@ navTitle: Version 9.8.0 Released: 19th Nov 2024 !!! Note -This release contains a fix for a bug that prevented some historical data from being correctly purged when its configured retention time expired. -Therefore, it is likely that the first purge job to run after this update will delete more data than usual and may take longer to complete. -The purge job should start within 3 hours of the upgrade. -You may also notice that the total size of your PEM database shrinks significantly once this job and subsequent vacuuming is complete. +This release includes a fix for a bug that previously prevented the correct purging of historical data when the configured retention time expired. As a result, the first purge job to run after this update is expected to delete more data than usual and may take longer to complete. + +The purge job should begin within three hours of the upgrade. Additionally, after this job and the subsequent vacuuming process are finished, you may notice a significant reduction in the total size of your PEM database. !!! New features, enhancements, bug fixes, and other changes in PEM 9.8.0 include: diff --git a/product_docs/docs/pem/9/registering_agent.mdx b/product_docs/docs/pem/9/registering_agent.mdx index 73d558b884a..3c617e4f678 100644 --- a/product_docs/docs/pem/9/registering_agent.mdx +++ b/product_docs/docs/pem/9/registering_agent.mdx @@ -44,26 +44,27 @@ set PEM_SERVER_PASSWORD=edb ./pemworker.exe REGISTER ``` -| Option | Description | -|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| `--pem-server` | The IP address of the PEM backend database server. This parameter is required. | -| `--pem-port` | The port of the PEM backend database server. The default value is `5432`. | -| `--pem-user` | The name of the database user having superuser privileges of the PEM backend database server. This parameter is required. | -| `--pem-agent-user` | The agent user to connect the PEM server backend database server. | -| `--cert-path` | The complete path to the directory where certificates are created. If you don't provide a path, certificates are created in `~/.pem` on Linux and `%APPDATA%/pem` on Windows. | -| `--config-dir` | The directory path for the configuration file. The default is `/../etc`. | -| `--display-name` | A user-friendly name for the agent to display in the PEM browser tree. In PEM 9.6 and later, the default is the host's fully qualified domain name (FQDN), falling back to the hostname if this option isn't set. For releases earlier than PEM 9.6, the default is the hostname. | -| `--force-registration` | Include the `force_registration` clause to register the agent with the arguments provided. This clause is useful if you're overriding an existing agent configuration. The default value is `Yes`. | -| `--group` | The name of the group in which the agent is displayed. | -| `--team` | The name of the database role on the PEM backend database server with access to the monitored database server. | -| `--owner` | The name of the database user on the PEM backend database server who owns the agent. | -| `--allow_server_restart` | Enable the `allow_server_restart` parameter to allow PEM to restart the monitored server. The default value is `True`. | -| `--allow-batch-probes` | Enable the `allow-batch-probes` parameter to allow PEM to run batch probes on this agent. The default value is `False`. | -| `--batch-script-user` | The operating system user to use for executing the batch/shell scripts. The default value is none. The scripts don't execute if you leave this parameter blank or the specified user doesn't exist. | -| `--enable-heartbeat-connection` | Enable the `enable-heartbeat-connection` parameter to create a dedicated heartbeat connection between the PEM agent and server to update the active status. The default value is `False`. | -| `--enable-smtp` | Enable the `enable-smtp parameter` to allow the PEM agent to send the email on behalf of the PEM server. The default value is `False`. | -| `--enable-snmp` | Enable the `enable-snmp parameter` to allow the PEM agent to send the SNMP traps on behalf of the PEM server. The default value is `False`. | -| `-o` | Specifies whether you want to override the configuration file options. | +| Option | Description | +|---------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| `--pem-server` | The IP address of the PEM backend database server. This parameter is required. | +| `--pem-port` | The port of the PEM backend database server. The default value is `5432`. | +| `--pem-user` | The name of the database user having superuser privileges of the PEM backend database server. This parameter is required. | +| `--pem-agent-user` | The agent user to connect the PEM server backend database server. | +| `--pem-ssl-mode` | Type of SSL authentication used for connecting PEM agent to the PEM server. The possible values are `prefer`, `require`,`disable`,`verify-CA`, and `verify-full`. | +| `--cert-path` | The complete path to the directory where certificates are created. If you don't provide a path, certificates are created in `~/.pem` on Linux and `%APPDATA%/pem` on Windows. | +| `--config-dir` | The directory path for the configuration file. The default is `/../etc`. | +| `--display-name` | A user-friendly name for the agent to display in the PEM browser tree. In PEM 9.6 and later, the default is the host's fully qualified domain name (FQDN), falling back to the hostname if this option isn't set. For releases earlier than PEM 9.6, the default is the hostname. | +| `--force-registration` | Include the `force_registration` clause to register the agent with the arguments provided. This clause is useful if you're overriding an existing agent configuration. The default value is `Yes`. | +| `--group` | The name of the group in which the agent is displayed. | +| `--team` | The name of the database role on the PEM backend database server with access to the monitored database server. | +| `--owner` | The name of the database user on the PEM backend database server who owns the agent. | +| `--allow_server_restart` | Enable the `allow_server_restart` parameter to allow PEM to restart the monitored server. The default value is `True`. | +| `--allow-batch-probes` | Enable the `allow-batch-probes` parameter to allow PEM to run batch probes on this agent. The default value is `False`. | +| `--batch-script-user` | The operating system user to use for executing the batch/shell scripts. The default value is none. The scripts don't execute if you leave this parameter blank or the specified user doesn't exist. | +| `--enable-heartbeat-connection` | Enable the `enable-heartbeat-connection` parameter to create a dedicated heartbeat connection between the PEM agent and server to update the active status. The default value is `False`. | +| `--enable-smtp` | Enable the `enable-smtp parameter` to allow the PEM agent to send the email on behalf of the PEM server. The default value is `False`. | +| `--enable-snmp` | Enable the `enable-snmp parameter` to allow the PEM agent to send the SNMP traps on behalf of the PEM server. The default value is `False`. | +| `-o` | Specifies whether you want to override the configuration file options. | !!! Note Allowing the agent to restart the database server If you use any feature of PEM that requires a database server restart by the PEM agent (such as Audit Manager, Log Manager, or the Tuning Wizard), then you must set the value of `allow_server_restart` to `true` in the `agent.cfg` file or restart the server manually for changes to take effect. From 251b9cac8a3ed0a3863998bc65bb62d8032b19d0 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 25 Nov 2024 11:51:25 +0530 Subject: [PATCH 07/65] Added RHEL 9 ARM64 to dependencies page --- product_docs/docs/pem/9/installing/dependencies.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/product_docs/docs/pem/9/installing/dependencies.mdx b/product_docs/docs/pem/9/installing/dependencies.mdx index ff9555f20b5..c6ef5d43864 100644 --- a/product_docs/docs/pem/9/installing/dependencies.mdx +++ b/product_docs/docs/pem/9/installing/dependencies.mdx @@ -37,6 +37,7 @@ Python 3 and mod_wsgi (a Python module for Apache HTTPD) are required for PEM Se | RHEL 9 | x86_64 | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | | | ppc64le | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | | | s390x | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | +| | arm64 | `python39/python39-mod_wsgi` | 3.9 | `/usr/bin/python3` | | SLES 15 | x86_64 | `edb-python310/edb-python310-mod-wsgi` | 3.10 | `/usr/libexec/edb-python310/bin/python3` | | | ppc64le | `edb-python310/edb-python310-mod-wsgi` | 3.10 | `/usr/libexec/edb-python310/bin/python3` | | | s390x | `edb-python310/edb-python310-mod-wsgi` | 3.10 | `/usr/libexec/edb-python310/bin/python3` | @@ -60,6 +61,7 @@ The PEM Server and Agent require OpenSSL. | RHEL 9 | x86_64 | `openssl-3.0.7` | | | ppc64le | `openssl-3.0.7` | | | s390x | `openssl-3.0.7` | +| | arm64 | `openssl-3.0.7` | | SLES 12 | x86_64 | `openssl-1.0.2p` | | | ppc64le | `openssl-1.0.2p` | | | s390x | `openssl-1.0.2p` | From 8600f57a2af852409bf3f23b0a243969bbe9ddb0 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 25 Nov 2024 16:42:45 +0530 Subject: [PATCH 08/65] Added version 17 to Postgres compatibility page --- product_docs/docs/pem/9/index.mdx | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/pem/9/index.mdx b/product_docs/docs/pem/9/index.mdx index 7624ced8cfa..19db59efe42 100644 --- a/product_docs/docs/pem/9/index.mdx +++ b/product_docs/docs/pem/9/index.mdx @@ -78,10 +78,10 @@ PEM is a comprehensive database design and management system. PEM is designed to Supported versions of Postgres for PEM 9.x: -| |**Monitored Instance** |**Backend Instance** | -|:-----------------------------------------|:---------------------------|:---------------------| -|**EDB Postgres Advanced Server (EPAS)** |12, 13, 14, 15, 16 |12, 13, 14, 15, 16 | -|**PostgreSQL (PG)** |12, 13, 14, 15, 16 |12, 13, 14, 15, 16 | -|**EDB Postgres Extended Server (PGE)** |12, 13, 14, 15, 16 |13, 14, 15, 16[^1] | +| | **Monitored Instance** | **Backend Instance** | +|:----------------------------------------|:-----------------------|:-----------------------| +| **EDB Postgres Advanced Server (EPAS)** | 12, 13, 14, 15, 16, 17 | 12, 13, 14, 15, 16, 17 | +| **PostgreSQL (PG)** | 12, 13, 14, 15, 16, 17 | 12, 13, 14, 15, 16, 17 | +| **EDB Postgres Extended Server (PGE)** | 12, 13, 14, 15, 16, 17 | 13, 14, 15, 16, 17[^1] | [^1]: sslutils isn't available for RHEL 7 on IBM Power, so this distribution can't use PGE as a backend. From d6ef2e6b00a8b2c5099058df19aca3f3bee512d2 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 4 Nov 2024 10:56:52 -0500 Subject: [PATCH 09/65] Template changes to add RHEL9 to ARM64 architecture for EPAS 13-16 --- install_template/config.yaml | 5 ++++- install_template/templates/platformBase/index.njk | 2 +- .../products/edb-postgres-advanced-server/rhel-9_arm64.njk | 2 ++ 3 files changed, 7 insertions(+), 2 deletions(-) create mode 100644 install_template/templates/products/edb-postgres-advanced-server/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index 4fb2dcc60c2..9c2378ae590 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -325,7 +325,10 @@ products: supported versions: [11, 12, 13, 14, 15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [11, 12, 13, 14, 15, 16, 17] + supported versions: [11, 12, 13, 14, 15, 16] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [13, 14, 15, 16] - name: RHEL 9 arch: ppc64le supported versions: [11, 12, 13, 14, 15, 16, 17] diff --git a/install_template/templates/platformBase/index.njk b/install_template/templates/platformBase/index.njk index d2adae158ae..c0029a8f9b2 100644 --- a/install_template/templates/platformBase/index.njk +++ b/install_template/templates/platformBase/index.njk @@ -79,7 +79,7 @@ Select a link to access the applicable installation instructions: {{archInstall("IBM Power (ppc64le)", "ppc64le", ["RHEL", "SLES"])}} -{{archInstall("AArch64 (ARM64)", "arm64", ["Debian"])}} +{{archInstall("AArch64 (ARM64)", "arm64", ["RHEL", "Debian"])}} {% endblock linuxinstall %} {% block otherosinstall %} diff --git a/install_template/templates/products/edb-postgres-advanced-server/rhel-9_arm64.njk b/install_template/templates/products/edb-postgres-advanced-server/rhel-9_arm64.njk new file mode 100644 index 00000000000..0c0b0deb008 --- /dev/null +++ b/install_template/templates/products/edb-postgres-advanced-server/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-postgres-advanced-server/rhel-9-or-ol-9.njk" %} + From b2524726b47ef7f083881123150ddfbe7ac2cd77 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 4 Nov 2024 11:13:57 -0500 Subject: [PATCH 10/65] Template changes to add RHEL9 to ARM architecture for PGE 15 and 16 --- install_template/config.yaml | 5 ++++- install_template/templates/platformBase/index.njk | 2 +- .../products/edb-postgres-extended-server/rhel-9_arm64.njk | 2 ++ 3 files changed, 7 insertions(+), 2 deletions(-) create mode 100644 install_template/templates/products/edb-postgres-extended-server/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index 9c2378ae590..f9ae6b36833 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -369,7 +369,10 @@ products: supported versions: [15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [15, 16, 17] + supported versions: [15, 16] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [15, 16] - name: Debian 12 arch: x86_64 supported versions: [16, 17] diff --git a/install_template/templates/platformBase/index.njk b/install_template/templates/platformBase/index.njk index c0029a8f9b2..6aba8f97103 100644 --- a/install_template/templates/platformBase/index.njk +++ b/install_template/templates/platformBase/index.njk @@ -79,7 +79,7 @@ Select a link to access the applicable installation instructions: {{archInstall("IBM Power (ppc64le)", "ppc64le", ["RHEL", "SLES"])}} -{{archInstall("AArch64 (ARM64)", "arm64", ["RHEL", "Debian"])}} +{{archInstall("AArch64 (ARM64)", "arm64", ["RHEL", "OL", "Debian"])}} {% endblock linuxinstall %} {% block otherosinstall %} diff --git a/install_template/templates/products/edb-postgres-extended-server/rhel-9_arm64.njk b/install_template/templates/products/edb-postgres-extended-server/rhel-9_arm64.njk new file mode 100644 index 00000000000..668e6b32a40 --- /dev/null +++ b/install_template/templates/products/edb-postgres-extended-server/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-postgres-extended-server/rhel-9-or-ol-9.njk" %} + From 5de55590c709edba03edb5c2377542e6ab59c034 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 4 Nov 2024 11:49:29 -0500 Subject: [PATCH 11/65] Template changes to add RHEL9 for ARM64 to PostgreSQL --- install_template/config.yaml | 3 +++ .../templates/products/postgresql/rhel-9_arm64.njk | 1 + 2 files changed, 4 insertions(+) create mode 100644 install_template/templates/products/postgresql/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index f9ae6b36833..2f78b4444f2 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -736,6 +736,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [15, 16] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [15, 16] - name: Debian 12 arch: x86_64 supported versions: [15, 16] diff --git a/install_template/templates/products/postgresql/rhel-9_arm64.njk b/install_template/templates/products/postgresql/rhel-9_arm64.njk new file mode 100644 index 00000000000..70b8b9d5529 --- /dev/null +++ b/install_template/templates/products/postgresql/rhel-9_arm64.njk @@ -0,0 +1 @@ +{% extends "products/postgresql/rhel-9-or-ol-9.njk" %} \ No newline at end of file From 5bc29039ac76421a252aeaea6b3ee29fd97af643 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Mon, 4 Nov 2024 11:51:12 -0500 Subject: [PATCH 12/65] Generated files to add RHEL 9 for ARM64 to EPAS, PGE, PG --- .../postgresql/installing/index.mdx | 6 + .../installing/linux_arm64/index.mdx | 7 + .../linux_arm64/postgresql_rhel_9.mdx | 55 ++++++ .../docs/epas/13/installing/index.mdx | 9 + .../13/installing/linux_arm64/epas_rhel_9.mdx | 157 ++++++++++++++++++ .../epas/13/installing/linux_arm64/index.mdx | 15 ++ .../docs/epas/14/installing/index.mdx | 9 + .../14/installing/linux_arm64/epas_rhel_9.mdx | 157 ++++++++++++++++++ .../epas/14/installing/linux_arm64/index.mdx | 15 ++ .../docs/epas/15/installing/index.mdx | 9 + .../15/installing/linux_arm64/epas_rhel_9.mdx | 157 ++++++++++++++++++ .../epas/15/installing/linux_arm64/index.mdx | 15 ++ .../docs/epas/16/installing/index.mdx | 8 +- .../16/installing/linux_arm64/epas_rhel_9.mdx | 157 ++++++++++++++++++ .../epas/16/installing/linux_arm64/index.mdx | 7 + product_docs/docs/pge/15/installing/index.mdx | 9 + .../pge/15/installing/linux_arm64/index.mdx | 15 ++ .../15/installing/linux_arm64/pge_rhel_9.mdx | 129 ++++++++++++++ product_docs/docs/pge/16/installing/index.mdx | 6 + .../pge/16/installing/linux_arm64/index.mdx | 7 + .../16/installing/linux_arm64/pge_rhel_9.mdx | 129 ++++++++++++++ 21 files changed, 1077 insertions(+), 1 deletion(-) create mode 100644 advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx create mode 100644 product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx create mode 100644 product_docs/docs/epas/13/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx create mode 100644 product_docs/docs/epas/14/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx create mode 100644 product_docs/docs/epas/15/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx create mode 100644 product_docs/docs/pge/15/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/pge/15/installing/linux_arm64/pge_rhel_9.mdx create mode 100644 product_docs/docs/pge/16/installing/linux_arm64/pge_rhel_9.mdx diff --git a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx index f9c41467155..fe3359d13bb 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/postgresql_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/postgresql_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/postgresql_debian_12) diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/index.mdx index a5b44702762..0b8f1e9e273 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/index.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/index.mdx @@ -4,11 +4,18 @@ navTitle: "On Linux ARM64" indexCards: none navigation: + - postgresql_rhel_9 - postgresql_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](postgresql_rhel_9) + +- [Oracle Linux (OL) 9](postgresql_rhel_9) + ### Debian and derivatives - [Debian 12](postgresql_debian_12) diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx new file mode 100644 index 00000000000..99d7acb4f60 --- /dev/null +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx @@ -0,0 +1,55 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing PostgreSQL on RHEL 9 or OL 9 arm64 +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + !!! Note + Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). + !!! + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- Enable additional repositories to resolve dependencies: + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` +- Disable the built-in PostgreSQL module: + ```shell + dnf -qy module disable postgresql + ``` + +## Install the package + +```shell +sudo dnf -y install postgresql-server postgresql-contrib +``` + +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. diff --git a/product_docs/docs/epas/13/installing/index.mdx b/product_docs/docs/epas/13/installing/index.mdx index ad0299efdaa..61ab80fcbd0 100644 --- a/product_docs/docs/epas/13/installing/index.mdx +++ b/product_docs/docs/epas/13/installing/index.mdx @@ -14,6 +14,7 @@ redirects: navigation: - linux_x86_64 + - linux_arm64 - linux_ppc64le - windows - linux_install_details @@ -54,6 +55,14 @@ Select a link to access the applicable installation instructions: - [SLES 15](linux_ppc64le/epas_sles_15) +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/epas_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/epas_rhel_9) + ## Windows - [Windows Server 2022](windows) diff --git a/product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx new file mode 100644 index 00000000000..337c7a30287 --- /dev/null +++ b/product_docs/docs/epas/13/installing/linux_arm64/epas_rhel_9.mdx @@ -0,0 +1,157 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Advanced Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_rhel9_arm + - /epas/13/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- If you are also installing PostGIS, enable additional repositories to resolve dependencies: + + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` + + !!!note + + If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-9-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + + !!! + +## Install the package + +```shell +sudo dnf -y install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 13, the package name is `edb-as13-server`. + +To install an individual component: + +```shell +sudo dnf -y install +``` + +Where `package_name` can be any of the available packages from the [available package list](/epas/13/installing/linux_install_details/rpm_packages/). + +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as13`. + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-as-13-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as13/bin/edb-as-13-setup initdb + +sudo systemctl start edb-as-13 +``` + +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo su - enterprisedb + +psql edb +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE enterprisedb IDENTIFIED BY password; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +psql (13.0.0, server 13.0.0) +You are now connected to database "hr" as user "enterprisedb". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/13/installing/linux_arm64/index.mdx b/product_docs/docs/epas/13/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..52ed78c6861 --- /dev/null +++ b/product_docs/docs/epas/13/installing/linux_arm64/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Installing EDB Postgres Advanced Server on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - epas_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](epas_rhel_9) + +- [Oracle Linux (OL) 9](epas_rhel_9) diff --git a/product_docs/docs/epas/14/installing/index.mdx b/product_docs/docs/epas/14/installing/index.mdx index 8b8efef1348..159288cf4fc 100644 --- a/product_docs/docs/epas/14/installing/index.mdx +++ b/product_docs/docs/epas/14/installing/index.mdx @@ -14,6 +14,7 @@ redirects: navigation: - linux_x86_64 + - linux_arm64 - linux_ppc64le - windows - linux_install_details @@ -54,6 +55,14 @@ Select a link to access the applicable installation instructions: - [SLES 15](linux_ppc64le/epas_sles_15) +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/epas_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/epas_rhel_9) + ## Windows - [Windows Server 2022](windows) diff --git a/product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx new file mode 100644 index 00000000000..44c3edccb28 --- /dev/null +++ b/product_docs/docs/epas/14/installing/linux_arm64/epas_rhel_9.mdx @@ -0,0 +1,157 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Advanced Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_rhel9_arm + - /epas/14/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- If you are also installing PostGIS, enable additional repositories to resolve dependencies: + + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` + + !!!note + + If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-9-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + + !!! + +## Install the package + +```shell +sudo dnf -y install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 14, the package name is `edb-as14-server`. + +To install an individual component: + +```shell +sudo dnf -y install +``` + +Where `package_name` can be any of the available packages from the [available package list](/epas/14/installing/linux_install_details/rpm_packages/). + +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as14`. + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-as-14-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/#initializing-the-cluster-in-postgres-mode). + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as14/bin/edb-as-14-setup initdb + +sudo systemctl start edb-as-14 +``` + +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo su - enterprisedb + +psql edb +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE enterprisedb IDENTIFIED BY password; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +psql (14.0.0, server 14.0.0) +You are now connected to database "hr" as user "enterprisedb". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/14/installing/linux_arm64/index.mdx b/product_docs/docs/epas/14/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..52ed78c6861 --- /dev/null +++ b/product_docs/docs/epas/14/installing/linux_arm64/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Installing EDB Postgres Advanced Server on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - epas_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](epas_rhel_9) + +- [Oracle Linux (OL) 9](epas_rhel_9) diff --git a/product_docs/docs/epas/15/installing/index.mdx b/product_docs/docs/epas/15/installing/index.mdx index ed51b1932c8..31ecf8ee083 100644 --- a/product_docs/docs/epas/15/installing/index.mdx +++ b/product_docs/docs/epas/15/installing/index.mdx @@ -18,6 +18,7 @@ redirects: navigation: - linux_x86_64 + - linux_arm64 - linux_ppc64le - windows - linux_install_details @@ -58,6 +59,14 @@ Select a link to access the applicable installation instructions: - [SLES 15](linux_ppc64le/epas_sles_15) +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/epas_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/epas_rhel_9) + ## Windows - [Windows Server 2022](windows) diff --git a/product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx new file mode 100644 index 00000000000..abf73aba6cc --- /dev/null +++ b/product_docs/docs/epas/15/installing/linux_arm64/epas_rhel_9.mdx @@ -0,0 +1,157 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Advanced Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_rhel9_arm + - /epas/15/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- If you are also installing PostGIS, enable additional repositories to resolve dependencies: + + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` + + !!!note + + If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-9-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + + !!! + +## Install the package + +```shell +sudo dnf -y install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 15, the package name is `edb-as15-server`. + +To install an individual component: + +```shell +sudo dnf -y install +``` + +Where `package_name` can be any of the available packages from the [available package list](/epas/15/installing/linux_install_details/rpm_packages/). + +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as15`. + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-as-15-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as15/bin/edb-as-15-setup initdb + +sudo systemctl start edb-as-15 +``` + +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo su - enterprisedb + +psql edb +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE enterprisedb IDENTIFIED BY password; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +psql (15.0.0, server 15.0.0) +You are now connected to database "hr" as user "enterprisedb". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/15/installing/linux_arm64/index.mdx b/product_docs/docs/epas/15/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..52ed78c6861 --- /dev/null +++ b/product_docs/docs/epas/15/installing/linux_arm64/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Installing EDB Postgres Advanced Server on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - epas_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](epas_rhel_9) + +- [Oracle Linux (OL) 9](epas_rhel_9) diff --git a/product_docs/docs/epas/16/installing/index.mdx b/product_docs/docs/epas/16/installing/index.mdx index 3ed032d9fa7..bc4f033a0f6 100644 --- a/product_docs/docs/epas/16/installing/index.mdx +++ b/product_docs/docs/epas/16/installing/index.mdx @@ -14,8 +14,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le - windows - linux_install_details - windows_install_details @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/epas_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/epas_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/epas_debian_12) diff --git a/product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx new file mode 100644 index 00000000000..6a5bba9ad44 --- /dev/null +++ b/product_docs/docs/epas/16/installing/linux_arm64/epas_rhel_9.mdx @@ -0,0 +1,157 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Advanced Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_rhel9_arm + - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- If you are also installing PostGIS, enable additional repositories to resolve dependencies: + + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` + + !!!note + + If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-9-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + + !!! + +## Install the package + +```shell +sudo dnf -y install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 16, the package name is `edb-as16-server`. + +To install an individual component: + +```shell +sudo dnf -y install +``` + +Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/). + +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as16`. + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-as-16-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as16/bin/edb-as-16-setup initdb + +sudo systemctl start edb-as-16 +``` + +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo su - enterprisedb + +psql edb +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE enterprisedb IDENTIFIED BY password; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +psql (16.0.0, server 16.0.0) +You are now connected to database "hr" as user "enterprisedb". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/16/installing/linux_arm64/index.mdx b/product_docs/docs/epas/16/installing/linux_arm64/index.mdx index c1e50ddb610..10c64a6a576 100644 --- a/product_docs/docs/epas/16/installing/linux_arm64/index.mdx +++ b/product_docs/docs/epas/16/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB Postgres Advanced Server on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - epas_rhel_9 - epas_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](epas_rhel_9) + +- [Oracle Linux (OL) 9](epas_rhel_9) + ### Debian and derivatives - [Debian 12](epas_debian_12) diff --git a/product_docs/docs/pge/15/installing/index.mdx b/product_docs/docs/pge/15/installing/index.mdx index db0991e6253..3d95d0b0b15 100644 --- a/product_docs/docs/pge/15/installing/index.mdx +++ b/product_docs/docs/pge/15/installing/index.mdx @@ -6,6 +6,7 @@ description: Installation instructions for EDB Postgres Extended Server on Linux navigation: - linux_x86_64 + - linux_arm64 --- Select a link to access the applicable installation instructions: @@ -27,3 +28,11 @@ Select a link to access the applicable installation instructions: - [Ubuntu 22.04](linux_x86_64/pge_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pge_ubuntu_20) - [Debian 11](linux_x86_64/pge_debian_11) + +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pge_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pge_rhel_9) diff --git a/product_docs/docs/pge/15/installing/linux_arm64/index.mdx b/product_docs/docs/pge/15/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..5827df314c9 --- /dev/null +++ b/product_docs/docs/pge/15/installing/linux_arm64/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Installing EDB Postgres Extended Server on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - pge_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pge_rhel_9) + +- [Oracle Linux (OL) 9](pge_rhel_9) diff --git a/product_docs/docs/pge/15/installing/linux_arm64/pge_rhel_9.mdx b/product_docs/docs/pge/15/installing/linux_arm64/pge_rhel_9.mdx new file mode 100644 index 00000000000..3b793cc0af9 --- /dev/null +++ b/product_docs/docs/pge/15/installing/linux_arm64/pge_rhel_9.mdx @@ -0,0 +1,129 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Extended Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-postgresextended15-server edb-postgresextended15-contrib +``` + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-15-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge15/bin/edb-pge-15-setup initdb + +sudo systemctl start edb-pge-15 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/pge/16/installing/index.mdx b/product_docs/docs/pge/16/installing/index.mdx index 0cc88e55d5e..4883cc3bb07 100644 --- a/product_docs/docs/pge/16/installing/index.mdx +++ b/product_docs/docs/pge/16/installing/index.mdx @@ -31,6 +31,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pge_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pge_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/pge_debian_12) diff --git a/product_docs/docs/pge/16/installing/linux_arm64/index.mdx b/product_docs/docs/pge/16/installing/linux_arm64/index.mdx index 230f6000758..04d27036fdd 100644 --- a/product_docs/docs/pge/16/installing/linux_arm64/index.mdx +++ b/product_docs/docs/pge/16/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB Postgres Extended Server on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - pge_rhel_9 - pge_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pge_rhel_9) + +- [Oracle Linux (OL) 9](pge_rhel_9) + ### Debian and derivatives - [Debian 12](pge_debian_12) diff --git a/product_docs/docs/pge/16/installing/linux_arm64/pge_rhel_9.mdx b/product_docs/docs/pge/16/installing/linux_arm64/pge_rhel_9.mdx new file mode 100644 index 00000000000..3b9f60bc7ec --- /dev/null +++ b/product_docs/docs/pge/16/installing/linux_arm64/pge_rhel_9.mdx @@ -0,0 +1,129 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Extended Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-postgresextended16-server edb-postgresextended16-contrib +``` + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-16-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge16/bin/edb-pge-16-setup initdb + +sudo systemctl start edb-pge-16 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` From 27ede0027ba598d00f85ee98b1f1d29a450644d4 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 09:06:58 -0500 Subject: [PATCH 13/65] Template changes to implement RHEL 9 on ARM 65 for JDBC, OCL, ODBC, and DMS Reader --- install_template/config.yaml | 16 ++++++++++++++-- .../arm64_index.njk | 7 +++++++ .../rhel-9_arm64.njk | 2 ++ .../products/edb-jdbc-connector/arm64_index.njk | 1 + .../products/edb-jdbc-connector/rhel-9_arm64.njk | 2 ++ .../products/edb-ocl-connector/rhel-9_arm64.njk | 2 ++ .../products/edb-odbc-connector/rhel-9_arm64.njk | 2 ++ 7 files changed, 30 insertions(+), 2 deletions(-) create mode 100644 install_template/templates/products/edb-data-migration-service-reader/arm64_index.njk create mode 100644 install_template/templates/products/edb-data-migration-service-reader/rhel-9_arm64.njk create mode 100644 install_template/templates/products/edb-jdbc-connector/rhel-9_arm64.njk create mode 100644 install_template/templates/products/edb-ocl-connector/rhel-9_arm64.njk create mode 100644 install_template/templates/products/edb-odbc-connector/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index 2f78b4444f2..126023f3f46 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -10,6 +10,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [2] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [2] - name: Debian 11 arch: x86_64 supported versions: [2] @@ -38,7 +41,10 @@ products: supported versions: [42.7.3.2] - name: RHEL 9 arch: ppc64le - supported versions: [42.7.3.2] + supported versions: [42.7.3.1] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [42.7.3.1] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 supported versions: [42.7.3.2] @@ -126,7 +132,10 @@ products: supported versions: [14, 15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [14, 15, 16, 17] + supported versions: [14, 15, 16] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [14, 15, 16] - name: Debian 11 arch: x86_64 supported versions: [14, 15, 16, 17] @@ -168,6 +177,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [13, 16] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [13, 16] - name: Debian 11 arch: x86_64 supported versions: [13, 16] diff --git a/install_template/templates/products/edb-data-migration-service-reader/arm64_index.njk b/install_template/templates/products/edb-data-migration-service-reader/arm64_index.njk new file mode 100644 index 00000000000..c538681325a --- /dev/null +++ b/install_template/templates/products/edb-data-migration-service-reader/arm64_index.njk @@ -0,0 +1,7 @@ +{% extends "platformBase/arm64_index.njk" %} +{% set productShortname="edb-dms-reader" %} + +{% block frontmatter %} +deployPath: advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/index.mdx +indexCards: none +{% endblock frontmatter %} \ No newline at end of file diff --git a/install_template/templates/products/edb-data-migration-service-reader/rhel-9_arm64.njk b/install_template/templates/products/edb-data-migration-service-reader/rhel-9_arm64.njk new file mode 100644 index 00000000000..0599dba7d89 --- /dev/null +++ b/install_template/templates/products/edb-data-migration-service-reader/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-data-migration-service-reader/rhel-9-or-ol-9.njk" %} + diff --git a/install_template/templates/products/edb-jdbc-connector/arm64_index.njk b/install_template/templates/products/edb-jdbc-connector/arm64_index.njk index 0a8c6d32c3d..587a9816227 100644 --- a/install_template/templates/products/edb-jdbc-connector/arm64_index.njk +++ b/install_template/templates/products/edb-jdbc-connector/arm64_index.njk @@ -4,3 +4,4 @@ {% block frontmatter %} deployPath: jdbc_connector/{{ product.version }}/installing/linux_arm64/index.mdx {% endblock frontmatter %} + diff --git a/install_template/templates/products/edb-jdbc-connector/rhel-9_arm64.njk b/install_template/templates/products/edb-jdbc-connector/rhel-9_arm64.njk new file mode 100644 index 00000000000..223963c714d --- /dev/null +++ b/install_template/templates/products/edb-jdbc-connector/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-jdbc-connector/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-ocl-connector/rhel-9_arm64.njk b/install_template/templates/products/edb-ocl-connector/rhel-9_arm64.njk new file mode 100644 index 00000000000..9f0b856e325 --- /dev/null +++ b/install_template/templates/products/edb-ocl-connector/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-ocl-connector/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-odbc-connector/rhel-9_arm64.njk b/install_template/templates/products/edb-odbc-connector/rhel-9_arm64.njk new file mode 100644 index 00000000000..11f119351c1 --- /dev/null +++ b/install_template/templates/products/edb-odbc-connector/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-odbc-connector/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file From 69b5820767c6e4a1d1c0564a7145e9ee257b970b Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 09:08:04 -0500 Subject: [PATCH 14/65] Generated files changes for adding RHEL 9 for ARM 64 for JDBC, OCL, ODBC and DMS Reader --- .../getting_started/installing/index.mdx | 8 +++ .../linux_arm64/edb-dms-reader_rhel_9.mdx | 36 ++++++++++++ .../installing/linux_arm64/index.mdx | 16 ++++++ .../42.7.3.2/installing/index.mdx | 6 ++ .../42.7.3.2/installing/linux_arm64/index.mdx | 7 +++ .../installing/linux_arm64/jdbc_rhel_9.mdx | 55 +++++++++++++++++++ .../ocl_connector/14/installing/index.mdx | 9 +++ .../14/installing/linux_arm64/index.mdx | 15 +++++ .../14/installing/linux_arm64/ocl_rhel_9.mdx | 52 ++++++++++++++++++ .../ocl_connector/15/installing/index.mdx | 9 +++ .../15/installing/linux_arm64/index.mdx | 15 +++++ .../15/installing/linux_arm64/ocl_rhel_9.mdx | 52 ++++++++++++++++++ .../ocl_connector/16/installing/index.mdx | 6 ++ .../16/installing/linux_arm64/index.mdx | 7 +++ .../16/installing/linux_arm64/ocl_rhel_9.mdx | 52 ++++++++++++++++++ .../odbc_connector/13/installing/index.mdx | 9 +++ .../13/installing/linux_arm64/index.mdx | 15 +++++ .../13/installing/linux_arm64/odbc_rhel_9.mdx | 52 ++++++++++++++++++ .../odbc_connector/16/installing/index.mdx | 6 ++ .../16/installing/linux_arm64/index.mdx | 7 +++ .../16/installing/linux_arm64/odbc_rhel_9.mdx | 52 ++++++++++++++++++ 21 files changed, 486 insertions(+) create mode 100644 advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/edb-dms-reader_rhel_9.mdx create mode 100644 advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/jdbc_rhel_9.mdx create mode 100644 product_docs/docs/ocl_connector/14/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/ocl_connector/14/installing/linux_arm64/ocl_rhel_9.mdx create mode 100644 product_docs/docs/ocl_connector/15/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/ocl_connector/15/installing/linux_arm64/ocl_rhel_9.mdx create mode 100644 product_docs/docs/ocl_connector/16/installing/linux_arm64/ocl_rhel_9.mdx create mode 100644 product_docs/docs/odbc_connector/13/installing/linux_arm64/index.mdx create mode 100644 product_docs/docs/odbc_connector/13/installing/linux_arm64/odbc_rhel_9.mdx create mode 100644 product_docs/docs/odbc_connector/16/installing/linux_arm64/odbc_rhel_9.mdx diff --git a/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/index.mdx b/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/index.mdx index 26a099eaa35..717a84e2bfa 100644 --- a/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/index.mdx +++ b/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/index.mdx @@ -30,3 +30,11 @@ Select a link to access the applicable installation instructions: - [Ubuntu 22.04](linux_x86_64/edb-dms-reader_ubuntu_22), [Ubuntu 20.04](linux_x86_64/edb-dms-reader_ubuntu_20) - [Debian 12](linux_x86_64/edb-dms-reader_debian_12), [Debian 11](linux_x86_64/edb-dms-reader_debian_11) + +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/edb-dms-reader_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/edb-dms-reader_rhel_9) diff --git a/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/edb-dms-reader_rhel_9.mdx b/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/edb-dms-reader_rhel_9.mdx new file mode 100644 index 00000000000..a576829d9e1 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/edb-dms-reader_rhel_9.mdx @@ -0,0 +1,36 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Data Migration Service Reader on RHEL 9 or OL 9 arm64 +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +Install the EDB DMS Reader (packaged as `cdcreader`): + +```shell +sudo dnf install cdcreader +``` diff --git a/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/index.mdx b/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..2c54c64a4e5 --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/migration-etl/data-migration-service/getting_started/installing/linux_arm64/index.mdx @@ -0,0 +1,16 @@ +--- +title: "Installing EDB Data Migration Service Reader on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" +indexCards: none + +navigation: + - edb-dms-reader_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](edb-dms-reader_rhel_9) + +- [Oracle Linux (OL) 9](edb-dms-reader_rhel_9) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/installing/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/index.mdx index 04c05105109..e644670856a 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/installing/index.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/installing/index.mdx @@ -68,6 +68,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/jdbc_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/jdbc_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/jdbc_debian_12) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/index.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/index.mdx index d96899f574a..9a7ad427d61 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/index.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB JDBC Connector on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - jdbc_rhel_9 - jdbc_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](jdbc_rhel_9) + +- [Oracle Linux (OL) 9](jdbc_rhel_9) + ### Debian and derivatives - [Debian 12](jdbc_debian_12) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/jdbc_rhel_9.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/jdbc_rhel_9.mdx new file mode 100644 index 00000000000..aefa66992f7 --- /dev/null +++ b/product_docs/docs/jdbc_connector/42.7.3.2/installing/linux_arm64/jdbc_rhel_9.mdx @@ -0,0 +1,55 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB JDBC Connector on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /jdbc_connector/42.5.4.1/04_installing_and_configuring_the_jdbc_connector/01_installing_the_connector_with_an_rpm_package/arm64/jdbc42_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Ensure that Java is installed on your system. You can download a Java installer that matches your environment from the Oracle Java Downloads [website](http://www.oracle.com/technetwork/java/javase/downloads/index.html). Documentation that contains detailed installation instructions is available through the associated `Installation Instruction` links on the same page. + +- Review [Supported JDBC distributions](/jdbc_connector/latest/02_requirements_overview/#supported-jdk-distribution). + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-jdbc +``` diff --git a/product_docs/docs/ocl_connector/14/installing/index.mdx b/product_docs/docs/ocl_connector/14/installing/index.mdx index 38ad5284927..ea9cf7354f1 100644 --- a/product_docs/docs/ocl_connector/14/installing/index.mdx +++ b/product_docs/docs/ocl_connector/14/installing/index.mdx @@ -16,6 +16,7 @@ redirects: navigation: - linux_ppc64le - linux_x86_64 + - linux_arm64 - windows - upgrading --- @@ -54,6 +55,14 @@ Select a link to access the applicable installation instructions: - [SLES 15](linux_ppc64le/ocl_sles_15) +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/ocl_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/ocl_rhel_9) + ## Windows - [Windows Server 2019](windows) diff --git a/product_docs/docs/ocl_connector/14/installing/linux_arm64/index.mdx b/product_docs/docs/ocl_connector/14/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..a7de35aebcd --- /dev/null +++ b/product_docs/docs/ocl_connector/14/installing/linux_arm64/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Installing EDB OCL Connector on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - ocl_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](ocl_rhel_9) + +- [Oracle Linux (OL) 9](ocl_rhel_9) diff --git a/product_docs/docs/ocl_connector/14/installing/linux_arm64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/14/installing/linux_arm64/ocl_rhel_9.mdx new file mode 100644 index 00000000000..8702eb5c124 --- /dev/null +++ b/product_docs/docs/ocl_connector/14/installing/linux_arm64/ocl_rhel_9.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB OCL Connector on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/14/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/15/installing/index.mdx b/product_docs/docs/ocl_connector/15/installing/index.mdx index 718f25597e2..3f77a558408 100644 --- a/product_docs/docs/ocl_connector/15/installing/index.mdx +++ b/product_docs/docs/ocl_connector/15/installing/index.mdx @@ -16,6 +16,7 @@ redirects: navigation: - linux_ppc64le - linux_x86_64 + - linux_arm64 - windows - upgrading --- @@ -54,6 +55,14 @@ Select a link to access the applicable installation instructions: - [SLES 15](linux_ppc64le/ocl_sles_15) +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/ocl_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/ocl_rhel_9) + ## Windows - [Windows Server 2019](windows) diff --git a/product_docs/docs/ocl_connector/15/installing/linux_arm64/index.mdx b/product_docs/docs/ocl_connector/15/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..a7de35aebcd --- /dev/null +++ b/product_docs/docs/ocl_connector/15/installing/linux_arm64/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Installing EDB OCL Connector on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - ocl_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](ocl_rhel_9) + +- [Oracle Linux (OL) 9](ocl_rhel_9) diff --git a/product_docs/docs/ocl_connector/15/installing/linux_arm64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/15/installing/linux_arm64/ocl_rhel_9.mdx new file mode 100644 index 00000000000..045b51f7b87 --- /dev/null +++ b/product_docs/docs/ocl_connector/15/installing/linux_arm64/ocl_rhel_9.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB OCL Connector on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/15/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/ocl_connector/16/installing/index.mdx b/product_docs/docs/ocl_connector/16/installing/index.mdx index 4b1f1965ad5..8016d75f50f 100644 --- a/product_docs/docs/ocl_connector/16/installing/index.mdx +++ b/product_docs/docs/ocl_connector/16/installing/index.mdx @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/ocl_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/ocl_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/ocl_debian_12) diff --git a/product_docs/docs/ocl_connector/16/installing/linux_arm64/index.mdx b/product_docs/docs/ocl_connector/16/installing/linux_arm64/index.mdx index 15061e86556..23b7a315d78 100644 --- a/product_docs/docs/ocl_connector/16/installing/linux_arm64/index.mdx +++ b/product_docs/docs/ocl_connector/16/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB OCL Connector on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - ocl_rhel_9 - ocl_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](ocl_rhel_9) + +- [Oracle Linux (OL) 9](ocl_rhel_9) + ### Debian and derivatives - [Debian 12](ocl_debian_12) diff --git a/product_docs/docs/ocl_connector/16/installing/linux_arm64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/16/installing/linux_arm64/ocl_rhel_9.mdx new file mode 100644 index 00000000000..b16c1a1d363 --- /dev/null +++ b/product_docs/docs/ocl_connector/16/installing/linux_arm64/ocl_rhel_9.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB OCL Connector on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/16/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/odbc_connector/13/installing/index.mdx b/product_docs/docs/odbc_connector/13/installing/index.mdx index 734cb20cc69..b3255e4d4f2 100644 --- a/product_docs/docs/odbc_connector/13/installing/index.mdx +++ b/product_docs/docs/odbc_connector/13/installing/index.mdx @@ -16,6 +16,7 @@ redirects: navigation: - linux_ppc64le - linux_x86_64 + - linux_arm64 - windows - upgrading --- @@ -54,6 +55,14 @@ Select a link to access the applicable installation instructions: - [SLES 15](linux_ppc64le/odbc_sles_15) +## Linux [AArch64 (ARM64)](linux_arm64) + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/odbc_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/odbc_rhel_9) + ## Windows - [Windows Server 2019](windows) diff --git a/product_docs/docs/odbc_connector/13/installing/linux_arm64/index.mdx b/product_docs/docs/odbc_connector/13/installing/linux_arm64/index.mdx new file mode 100644 index 00000000000..02b84b1bd33 --- /dev/null +++ b/product_docs/docs/odbc_connector/13/installing/linux_arm64/index.mdx @@ -0,0 +1,15 @@ +--- +title: "Installing EDB ODBC Connector on Linux AArch64 (ARM64)" +navTitle: "On Linux ARM64" + +navigation: + - odbc_rhel_9 +--- + +Operating system-specific install instructions are described in the corresponding documentation: + +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](odbc_rhel_9) + +- [Oracle Linux (OL) 9](odbc_rhel_9) diff --git a/product_docs/docs/odbc_connector/13/installing/linux_arm64/odbc_rhel_9.mdx b/product_docs/docs/odbc_connector/13/installing/linux_arm64/odbc_rhel_9.mdx new file mode 100644 index 00000000000..1909c35d14a --- /dev/null +++ b/product_docs/docs/odbc_connector/13/installing/linux_arm64/odbc_rhel_9.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB ODBC Connector on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/13/03_installing_edb_odbc/01_installing_linux/arm64/odbc13_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-odbc +sudo dnf -y install edb-odbc-devel +``` diff --git a/product_docs/docs/odbc_connector/16/installing/index.mdx b/product_docs/docs/odbc_connector/16/installing/index.mdx index adfc7806b5f..b65e5abd687 100644 --- a/product_docs/docs/odbc_connector/16/installing/index.mdx +++ b/product_docs/docs/odbc_connector/16/installing/index.mdx @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/odbc_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/odbc_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/odbc_debian_12) diff --git a/product_docs/docs/odbc_connector/16/installing/linux_arm64/index.mdx b/product_docs/docs/odbc_connector/16/installing/linux_arm64/index.mdx index 2514e5a8b44..91bec2cc213 100644 --- a/product_docs/docs/odbc_connector/16/installing/linux_arm64/index.mdx +++ b/product_docs/docs/odbc_connector/16/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB ODBC Connector on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - odbc_rhel_9 - odbc_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](odbc_rhel_9) + +- [Oracle Linux (OL) 9](odbc_rhel_9) + ### Debian and derivatives - [Debian 12](odbc_debian_12) diff --git a/product_docs/docs/odbc_connector/16/installing/linux_arm64/odbc_rhel_9.mdx b/product_docs/docs/odbc_connector/16/installing/linux_arm64/odbc_rhel_9.mdx new file mode 100644 index 00000000000..8d4f1ea4eaa --- /dev/null +++ b/product_docs/docs/odbc_connector/16/installing/linux_arm64/odbc_rhel_9.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB ODBC Connector on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /odbc_connector/16/03_installing_edb_odbc/01_installing_linux/arm64/odbc13_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-odbc +sudo dnf -y install edb-odbc-devel +``` From 5139ceee4ac6a03ecd45535a15a9165669caff52 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 09:38:14 -0500 Subject: [PATCH 15/65] Template changes to add RHEL 9 on ARM 64 for MTK, PgBouncer, PgPool, and PgPool extensions --- install_template/config.yaml | 14 +++++++++++++- .../products/edb-pgbouncer/rhel-9_arm64.njk | 2 ++ .../edb-pgpool-ii-extensions/rhel-9_arm64.njk | 2 ++ .../products/edb-pgpool-ii/rhel-9_arm64.njk | 2 ++ .../products/migration-toolkit/rhel-9_arm64.njk | 3 +++ 5 files changed, 22 insertions(+), 1 deletion(-) create mode 100644 install_template/templates/products/edb-pgbouncer/rhel-9_arm64.njk create mode 100644 install_template/templates/products/edb-pgpool-ii-extensions/rhel-9_arm64.njk create mode 100644 install_template/templates/products/edb-pgpool-ii/rhel-9_arm64.njk create mode 100644 install_template/templates/products/migration-toolkit/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index 126023f3f46..694952c0807 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -83,6 +83,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [55] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [55] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 supported versions: [55] @@ -220,7 +223,10 @@ products: supported versions: [1] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [1] + supported versions: [1] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [1] - name: Debian 11 arch: x86_64 supported versions: [1] @@ -262,6 +268,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [4] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [4] - name: Debian 11 arch: x86_64 supported versions: [4] @@ -303,6 +312,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [4] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [4] - name: Debian 11 arch: x86_64 supported versions: [4] diff --git a/install_template/templates/products/edb-pgbouncer/rhel-9_arm64.njk b/install_template/templates/products/edb-pgbouncer/rhel-9_arm64.njk new file mode 100644 index 00000000000..38d001007d7 --- /dev/null +++ b/install_template/templates/products/edb-pgbouncer/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgbouncer/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii-extensions/rhel-9_arm64.njk b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-9_arm64.njk new file mode 100644 index 00000000000..1e82154321e --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii-extensions/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii-extensions/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file diff --git a/install_template/templates/products/edb-pgpool-ii/rhel-9_arm64.njk b/install_template/templates/products/edb-pgpool-ii/rhel-9_arm64.njk new file mode 100644 index 00000000000..83f9e29b663 --- /dev/null +++ b/install_template/templates/products/edb-pgpool-ii/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/edb-pgpool-ii/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file diff --git a/install_template/templates/products/migration-toolkit/rhel-9_arm64.njk b/install_template/templates/products/migration-toolkit/rhel-9_arm64.njk new file mode 100644 index 00000000000..8a0caab90f9 --- /dev/null +++ b/install_template/templates/products/migration-toolkit/rhel-9_arm64.njk @@ -0,0 +1,3 @@ +{% extends "products/migration-toolkit/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file From a789bf19a2936dde0964e9214ad42d112419bd53 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 09:39:03 -0500 Subject: [PATCH 16/65] Generated file changes to add RHEL 9 on ARM 64 for MTK, PgBouncer, PgPool, and PgPool extensions --- .../migration_toolkit/55/installing/index.mdx | 6 +++ .../55/installing/linux_arm64/index.mdx | 7 +++ .../55/installing/linux_arm64/mtk_rhel_9.mdx | 44 +++++++++++++++ .../docs/pgbouncer/1/installing/index.mdx | 6 +++ .../1/installing/linux_arm64/index.mdx | 7 +++ .../linux_arm64/pgbouncer_rhel_9.mdx | 53 +++++++++++++++++++ .../docs/pgpool/4/installing/index.mdx | 6 +++ .../pgpool/4/installing/linux_arm64/index.mdx | 7 +++ .../installing/linux_arm64/pgpool_rhel_9.mdx | 53 +++++++++++++++++++ .../pgpool/4/installing_extensions/index.mdx | 6 +++ .../linux_arm64/index.mdx | 7 +++ .../linux_arm64/pgpoolext_rhel_9.mdx | 53 +++++++++++++++++++ 12 files changed, 255 insertions(+) create mode 100644 product_docs/docs/migration_toolkit/55/installing/linux_arm64/mtk_rhel_9.mdx create mode 100644 product_docs/docs/pgbouncer/1/installing/linux_arm64/pgbouncer_rhel_9.mdx create mode 100644 product_docs/docs/pgpool/4/installing/linux_arm64/pgpool_rhel_9.mdx create mode 100644 product_docs/docs/pgpool/4/installing_extensions/linux_arm64/pgpoolext_rhel_9.mdx diff --git a/product_docs/docs/migration_toolkit/55/installing/index.mdx b/product_docs/docs/migration_toolkit/55/installing/index.mdx index 12f8a23c699..350db2b5bd6 100644 --- a/product_docs/docs/migration_toolkit/55/installing/index.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/index.mdx @@ -71,6 +71,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/mtk_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/mtk_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/mtk_debian_12) diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_arm64/index.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_arm64/index.mdx index d7fea6257e9..ca17a82f60b 100644 --- a/product_docs/docs/migration_toolkit/55/installing/linux_arm64/index.mdx +++ b/product_docs/docs/migration_toolkit/55/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing Migration Toolkit on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - mtk_rhel_9 - mtk_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](mtk_rhel_9) + +- [Oracle Linux (OL) 9](mtk_rhel_9) + ### Debian and derivatives - [Debian 12](mtk_debian_12) diff --git a/product_docs/docs/migration_toolkit/55/installing/linux_arm64/mtk_rhel_9.mdx b/product_docs/docs/migration_toolkit/55/installing/linux_arm64/mtk_rhel_9.mdx new file mode 100644 index 00000000000..42ddf8a3081 --- /dev/null +++ b/product_docs/docs/migration_toolkit/55/installing/linux_arm64/mtk_rhel_9.mdx @@ -0,0 +1,44 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing Migration Toolkit on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /migration_toolkit/55/05_installing_mtk/install_on_linux/arm64/mtk55_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo dnf -y install edb-migrationtoolkit +``` + +## Initial configuration + +Before invoking Migration Toolkit, you must download and install JDBC drivers for connecting to the source and target databases. See [Installing a JDBC driver](/migration_toolkit/latest/installing/installing_jdbc_driver/) for details. diff --git a/product_docs/docs/pgbouncer/1/installing/index.mdx b/product_docs/docs/pgbouncer/1/installing/index.mdx index 8d2a4fad1be..e1b8a0cf9a2 100644 --- a/product_docs/docs/pgbouncer/1/installing/index.mdx +++ b/product_docs/docs/pgbouncer/1/installing/index.mdx @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pgbouncer_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pgbouncer_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/pgbouncer_debian_12) diff --git a/product_docs/docs/pgbouncer/1/installing/linux_arm64/index.mdx b/product_docs/docs/pgbouncer/1/installing/linux_arm64/index.mdx index 5f856c7733b..e7d3bbc9906 100644 --- a/product_docs/docs/pgbouncer/1/installing/linux_arm64/index.mdx +++ b/product_docs/docs/pgbouncer/1/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB pgBouncer on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - pgbouncer_rhel_9 - pgbouncer_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pgbouncer_rhel_9) + +- [Oracle Linux (OL) 9](pgbouncer_rhel_9) + ### Debian and derivatives - [Debian 12](pgbouncer_debian_12) diff --git a/product_docs/docs/pgbouncer/1/installing/linux_arm64/pgbouncer_rhel_9.mdx b/product_docs/docs/pgbouncer/1/installing/linux_arm64/pgbouncer_rhel_9.mdx new file mode 100644 index 00000000000..3af437c7d1a --- /dev/null +++ b/product_docs/docs/pgbouncer/1/installing/linux_arm64/pgbouncer_rhel_9.mdx @@ -0,0 +1,53 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB pgBouncer on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /pgbouncer/1/01_installation/install_on_linux/arm64/pgbouncer_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-pgbouncer +``` + +Where `` is the version of EDB PgBouncer you are installing. For example, if you are installing version 1.22, the package name would be `edb-pgbouncer122`. diff --git a/product_docs/docs/pgpool/4/installing/index.mdx b/product_docs/docs/pgpool/4/installing/index.mdx index 527aa99a1a1..5a49b78e14d 100644 --- a/product_docs/docs/pgpool/4/installing/index.mdx +++ b/product_docs/docs/pgpool/4/installing/index.mdx @@ -61,6 +61,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pgpool_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pgpool_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/pgpool_debian_12) diff --git a/product_docs/docs/pgpool/4/installing/linux_arm64/index.mdx b/product_docs/docs/pgpool/4/installing/linux_arm64/index.mdx index 2078edd5ca2..685b1c5f36d 100644 --- a/product_docs/docs/pgpool/4/installing/linux_arm64/index.mdx +++ b/product_docs/docs/pgpool/4/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB Pgpool-II on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - pgpool_rhel_9 - pgpool_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pgpool_rhel_9) + +- [Oracle Linux (OL) 9](pgpool_rhel_9) + ### Debian and derivatives - [Debian 12](pgpool_debian_12) diff --git a/product_docs/docs/pgpool/4/installing/linux_arm64/pgpool_rhel_9.mdx b/product_docs/docs/pgpool/4/installing/linux_arm64/pgpool_rhel_9.mdx new file mode 100644 index 00000000000..e1909fa11c0 --- /dev/null +++ b/product_docs/docs/pgpool/4/installing/linux_arm64/pgpool_rhel_9.mdx @@ -0,0 +1,53 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Pgpool-II on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /pgpool/4/01_installing_and_configuring_the_pgpool-II/arm64/pgpool_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-pgpool +``` + +Where `` is the version of EDB PgPool-II you are installing. For example, if you are installing version 4.3, the package name would be `edb-pgpool43`. diff --git a/product_docs/docs/pgpool/4/installing_extensions/index.mdx b/product_docs/docs/pgpool/4/installing_extensions/index.mdx index 52a68de8565..9664747ebf5 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/index.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/index.mdx @@ -58,6 +58,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pgpoolext_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pgpoolext_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/pgpoolext_debian_12) diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_arm64/index.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_arm64/index.mdx index 884bc272cc1..ce42a7975aa 100644 --- a/product_docs/docs/pgpool/4/installing_extensions/linux_arm64/index.mdx +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB Pgpool-II Extensions on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - pgpoolext_rhel_9 - pgpoolext_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pgpoolext_rhel_9) + +- [Oracle Linux (OL) 9](pgpoolext_rhel_9) + ### Debian and derivatives - [Debian 12](pgpoolext_debian_12) diff --git a/product_docs/docs/pgpool/4/installing_extensions/linux_arm64/pgpoolext_rhel_9.mdx b/product_docs/docs/pgpool/4/installing_extensions/linux_arm64/pgpoolext_rhel_9.mdx new file mode 100644 index 00000000000..15e7590074e --- /dev/null +++ b/product_docs/docs/pgpool/4/installing_extensions/linux_arm64/pgpoolext_rhel_9.mdx @@ -0,0 +1,53 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Pgpool-II Extensions on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /pgpool/4/02_extensions/arm64/pgpoolext_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as-pgpool-extensions +``` + +Where `` is the EDB Postgres Advanced Server version and `` is the EDB Pgpool-II version you are installing. For example, if you are installing EDB Pgpool-II version 4.4 and EDB Postgres Advanced Server version 15, the package name would be `edb-as15-pgpool44-extensions`. From f06d580f551eaf3e5ce32de51fd01c98a9c335ca Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 10:10:53 -0500 Subject: [PATCH 17/65] Template changes to support RHEL9 on ARM64 for EFM and EDBPlus --- install_template/config.yaml | 6 ++++++ .../templates/products/edb*plus/rhel-9_arm64.njk | 3 +++ .../templates/products/failover-manager/rhel-9_arm64.njk | 2 ++ 3 files changed, 11 insertions(+) create mode 100644 install_template/templates/products/edb*plus/rhel-9_arm64.njk create mode 100644 install_template/templates/products/failover-manager/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index 694952c0807..6b2ba406b6a 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -426,6 +426,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [41] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [41] - name: RHEL 9 arch: ppc64le supported versions: [41] @@ -470,6 +473,9 @@ products: - name: RHEL 9 arch: ppc64le supported versions: [4] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [4] - name: RHEL 8 arch: ppc64le supported versions: [4] diff --git a/install_template/templates/products/edb*plus/rhel-9_arm64.njk b/install_template/templates/products/edb*plus/rhel-9_arm64.njk new file mode 100644 index 00000000000..99fac101b08 --- /dev/null +++ b/install_template/templates/products/edb*plus/rhel-9_arm64.njk @@ -0,0 +1,3 @@ +{% extends "products/edb*plus/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/failover-manager/rhel-9_arm64.njk b/install_template/templates/products/failover-manager/rhel-9_arm64.njk new file mode 100644 index 00000000000..ea56c076990 --- /dev/null +++ b/install_template/templates/products/failover-manager/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/failover-manager/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file From 6d2521358d6ac60483f044c91e5871e941b65ea7 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 10:11:46 -0500 Subject: [PATCH 18/65] Generated files changes to support RHEL9 on ARM64 for EFM and EDBPlus --- .../docs/edb_plus/41/installing/index.mdx | 8 ++- .../installing/linux_arm64/edbplus_rhel_9.mdx | 49 ++++++++++++++ .../41/installing/linux_arm64/index.mdx | 7 ++ product_docs/docs/efm/4/installing/index.mdx | 6 ++ .../4/installing/linux_arm64/efm_rhel_9.mdx | 66 +++++++++++++++++++ .../efm/4/installing/linux_arm64/index.mdx | 7 ++ 6 files changed, 142 insertions(+), 1 deletion(-) create mode 100644 product_docs/docs/edb_plus/41/installing/linux_arm64/edbplus_rhel_9.mdx create mode 100644 product_docs/docs/efm/4/installing/linux_arm64/efm_rhel_9.mdx diff --git a/product_docs/docs/edb_plus/41/installing/index.mdx b/product_docs/docs/edb_plus/41/installing/index.mdx index e39e4d016a8..8d3ba5149f9 100644 --- a/product_docs/docs/edb_plus/41/installing/index.mdx +++ b/product_docs/docs/edb_plus/41/installing/index.mdx @@ -12,8 +12,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le - windows - configuring_linux_installation --- @@ -54,6 +54,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/edbplus_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/edbplus_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/edbplus_debian_12) diff --git a/product_docs/docs/edb_plus/41/installing/linux_arm64/edbplus_rhel_9.mdx b/product_docs/docs/edb_plus/41/installing/linux_arm64/edbplus_rhel_9.mdx new file mode 100644 index 00000000000..ac035a6544a --- /dev/null +++ b/product_docs/docs/edb_plus/41/installing/linux_arm64/edbplus_rhel_9.mdx @@ -0,0 +1,49 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB*Plus on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /edb_plus/41/03_installing_edb_plus/install_on_linux/arm64/edbplus_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo dnf -y install edb-edbplus +``` + +## Initial configuration + +After performing a Linux installation of EDB\*Plus, you must set the values of environment variables that allow EDB\*Plus to locate your Java installation: + +```shell +export JAVA_HOME= +export PATH=/bin:$PATH +``` diff --git a/product_docs/docs/edb_plus/41/installing/linux_arm64/index.mdx b/product_docs/docs/edb_plus/41/installing/linux_arm64/index.mdx index b59092fa855..57ef6887bac 100644 --- a/product_docs/docs/edb_plus/41/installing/linux_arm64/index.mdx +++ b/product_docs/docs/edb_plus/41/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB*Plus on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - edbplus_rhel_9 - edbplus_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](edbplus_rhel_9) + +- [Oracle Linux (OL) 9](edbplus_rhel_9) + ### Debian and derivatives - [Debian 12](edbplus_debian_12) diff --git a/product_docs/docs/efm/4/installing/index.mdx b/product_docs/docs/efm/4/installing/index.mdx index 8cac86cdc53..2bb0829289d 100644 --- a/product_docs/docs/efm/4/installing/index.mdx +++ b/product_docs/docs/efm/4/installing/index.mdx @@ -72,6 +72,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/efm_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/efm_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/efm_debian_12) diff --git a/product_docs/docs/efm/4/installing/linux_arm64/efm_rhel_9.mdx b/product_docs/docs/efm/4/installing/linux_arm64/efm_rhel_9.mdx new file mode 100644 index 00000000000..dfd8881b0a2 --- /dev/null +++ b/product_docs/docs/efm/4/installing/linux_arm64/efm_rhel_9.mdx @@ -0,0 +1,66 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing Failover Manager on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /efm/4/03_installing_efm/arm64/efm_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host (not needed for witness nodes). + + - See [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - See [PostgreSQL Downloads](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-efm<4x> +``` + +Where `<4x>` is the version of Failover Manager that you're installing. For example, if you're installing version 4.10, the package name is `edb-efm410`. + +The installation process creates a user named efm that has privileges to invoke scripts that control the Failover Manager service for clusters owned by enterprisedb or postgres. + +## Initial configuration + +If you're using Failover Manager to monitor a cluster owned by a user other than enterprisedb or postgres, see [Extending Failover Manager permissions](../../04_configuring_efm/04_extending_efm_permissions/#extending_efm_permissions). + +After installing on each node of the cluster: + +1. Modify the [cluster properties file](../../04_configuring_efm/01_cluster_properties/#cluster_properties) on each node. +2. Modify the [cluster members file](../../04_configuring_efm/03_cluster_members/#cluster_members) on each node. +3. If applicable, configure and test virtual IP address settings and any scripts that are identified in the cluster properties file. +4. Start the agent on each node of the cluster. For more information, see [Controlling the Failover Manager service](../../08_controlling_efm_service/). diff --git a/product_docs/docs/efm/4/installing/linux_arm64/index.mdx b/product_docs/docs/efm/4/installing/linux_arm64/index.mdx index caa4e6ab3f9..ecb0c136441 100644 --- a/product_docs/docs/efm/4/installing/linux_arm64/index.mdx +++ b/product_docs/docs/efm/4/installing/linux_arm64/index.mdx @@ -10,11 +10,18 @@ navTitle: "On Linux ARM64" redirects: navigation: + - efm_rhel_9 - efm_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](efm_rhel_9) + +- [Oracle Linux (OL) 9](efm_rhel_9) + ### Debian and derivatives - [Debian 12](efm_debian_12) From acfc5ad562d1ab24b3613d4ceee61ed516983050 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 10:33:23 -0500 Subject: [PATCH 19/65] Template changes to support RHEL9 on ARM64 for Hadoop, Mongo, and MySQL --- install_template/config.yaml | 9 +++++++++ .../hadoop-foreign-data-wrapper/rhel-9_arm64.njk | 9 +++++++++ .../mongodb-foreign-data-wrapper/rhel-9_arm64.njk | 2 ++ .../products/mysql-foreign-data-wrapper/rhel-9_arm64.njk | 2 ++ 4 files changed, 22 insertions(+) create mode 100644 install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9_arm64.njk create mode 100644 install_template/templates/products/mongodb-foreign-data-wrapper/rhel-9_arm64.njk create mode 100644 install_template/templates/products/mysql-foreign-data-wrapper/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index 6b2ba406b6a..c600e1c7120 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -514,6 +514,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [2] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [2] - name: RHEL 9 arch: ppc64le supported versions: [2] @@ -555,6 +558,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [5] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [5] - name: RHEL 9 arch: ppc64le supported versions: [5] @@ -596,6 +602,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [2] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [2] - name: Ubuntu 22.04 arch: x86_64 supported versions: [2] diff --git a/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9_arm64.njk b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9_arm64.njk new file mode 100644 index 00000000000..11d9017285f --- /dev/null +++ b/install_template/templates/products/hadoop-foreign-data-wrapper/rhel-9_arm64.njk @@ -0,0 +1,9 @@ +{% extends "products/hadoop-foreign-data-wrapper/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% block prerequisites %} +{{ super() }} +- Enable additional repositories to resolve dependencies: + ```shell + sudo dnf config-manager --set-enabled PowerTools + ``` +{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-9_arm64.njk b/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-9_arm64.njk new file mode 100644 index 00000000000..5d9c95280c5 --- /dev/null +++ b/install_template/templates/products/mongodb-foreign-data-wrapper/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/mongodb-foreign-data-wrapper/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file diff --git a/install_template/templates/products/mysql-foreign-data-wrapper/rhel-9_arm64.njk b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-9_arm64.njk new file mode 100644 index 00000000000..f6086814d16 --- /dev/null +++ b/install_template/templates/products/mysql-foreign-data-wrapper/rhel-9_arm64.njk @@ -0,0 +1,2 @@ +{% extends "products/mysql-foreign-data-wrapper/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} \ No newline at end of file From 42c249d088772563b2d020c38b7e7dc50155d916 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 10:34:08 -0500 Subject: [PATCH 20/65] Generated file changes to support RHEL9 on ARM64 for Hadoop, Mongo, and MySQL --- .../2/installing/index.mdx | 8 ++- .../installing/linux_arm64/hadoop_rhel_9.mdx | 59 +++++++++++++++++++ .../2/installing/linux_arm64/index.mdx | 7 +++ .../mongo_data_adapter/5/installing/index.mdx | 8 ++- .../5/installing/linux_arm64/index.mdx | 7 +++ .../5/installing/linux_arm64/mongo_rhel_9.mdx | 53 +++++++++++++++++ .../mysql_data_adapter/2/installing/index.mdx | 8 ++- .../2/installing/linux_arm64/index.mdx | 7 +++ .../2/installing/linux_arm64/mysql_rhel_9.mdx | 53 +++++++++++++++++ 9 files changed, 207 insertions(+), 3 deletions(-) create mode 100644 product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/hadoop_rhel_9.mdx create mode 100644 product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/mongo_rhel_9.mdx create mode 100644 product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/mysql_rhel_9.mdx diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx index 08e22d13dfd..c3d6ffd8b6a 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/index.mdx @@ -15,8 +15,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le --- Select a link to access the applicable installation instructions: @@ -55,6 +55,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/hadoop_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/hadoop_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/hadoop_debian_12) diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/hadoop_rhel_9.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/hadoop_rhel_9.mdx new file mode 100644 index 00000000000..b33b585ecd3 --- /dev/null +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/hadoop_rhel_9.mdx @@ -0,0 +1,59 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing Hadoop Foreign Data Wrapper on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /hadoop_data_adapter/2/05_installing_the_hadoop_data_adapter/arm64/hadoop_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- Enable additional repositories to resolve dependencies: + ```shell + sudo dnf config-manager --set-enabled PowerTools + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as15-hdfs_fdw +``` + +Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/index.mdx b/product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/index.mdx index 5affcd4accf..9abb36c317a 100644 --- a/product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/index.mdx +++ b/product_docs/docs/hadoop_data_adapter/2/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing Hadoop Foreign Data Wrapper on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - hadoop_rhel_9 - hadoop_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](hadoop_rhel_9) + +- [Oracle Linux (OL) 9](hadoop_rhel_9) + ### Debian and derivatives - [Debian 12](hadoop_debian_12) diff --git a/product_docs/docs/mongo_data_adapter/5/installing/index.mdx b/product_docs/docs/mongo_data_adapter/5/installing/index.mdx index a30fd831ccc..7a4bea64607 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/index.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/index.mdx @@ -15,8 +15,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le --- Select a link to access the applicable installation instructions: @@ -55,6 +55,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/mongo_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/mongo_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/mongo_debian_12) diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/index.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/index.mdx index df33136f6c0..f5b2c21f281 100644 --- a/product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/index.mdx +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing MongoDB Foreign Data Wrapper on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - mongo_rhel_9 - mongo_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](mongo_rhel_9) + +- [Oracle Linux (OL) 9](mongo_rhel_9) + ### Debian and derivatives - [Debian 12](mongo_debian_12) diff --git a/product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/mongo_rhel_9.mdx b/product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/mongo_rhel_9.mdx new file mode 100644 index 00000000000..7310e6d1c7d --- /dev/null +++ b/product_docs/docs/mongo_data_adapter/5/installing/linux_arm64/mongo_rhel_9.mdx @@ -0,0 +1,53 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing MongoDB Foreign Data Wrapper on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /mongo_data_adapter/5/04_installing_the_mongo_data_adapter/arm64/mongo_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as15-mongo_fdw +``` + +Where `15` is the version of EDB Postgres Advanced Server. Replace `15` with the version of EDB Postgres Advanced Server you are using. diff --git a/product_docs/docs/mysql_data_adapter/2/installing/index.mdx b/product_docs/docs/mysql_data_adapter/2/installing/index.mdx index df826a484c5..76e8ff5b52b 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/index.mdx @@ -14,8 +14,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le --- Select a link to access the applicable installation instructions: @@ -54,6 +54,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/mysql_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/mysql_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/mysql_debian_12) diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/index.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/index.mdx index 47795097677..cc4c9fff8fd 100644 --- a/product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/index.mdx +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing MySQL Foreign Data Wrapper on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - mysql_rhel_9 - mysql_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](mysql_rhel_9) + +- [Oracle Linux (OL) 9](mysql_rhel_9) + ### Debian and derivatives - [Debian 12](mysql_debian_12) diff --git a/product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/mysql_rhel_9.mdx b/product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/mysql_rhel_9.mdx new file mode 100644 index 00000000000..d7011921dbb --- /dev/null +++ b/product_docs/docs/mysql_data_adapter/2/installing/linux_arm64/mysql_rhel_9.mdx @@ -0,0 +1,53 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing MySQL Foreign Data Wrapper on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /mysql_data_adapter/2/04_installing_the_mysql_data_adapter/arm64/mysql_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-as15-mysql8_fdw +``` + +Where `15` is the version of EDB Postgres Advanced server and `8` is the version of MySQL to be installed. From a0a0b20aceeefd8b2a9425a77bac32eaf845dda6 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 10:51:19 -0500 Subject: [PATCH 21/65] Template changes to support RHEL9 on ARM64 for PostGIS and Replication Server --- install_template/config.yaml | 6 ++++ .../products/postgis/rhel-9_arm64.njk | 29 +++++++++++++++++++ .../replication-server/rhel-9_arm64.njk | 3 ++ 3 files changed, 38 insertions(+) create mode 100644 install_template/templates/products/postgis/rhel-9_arm64.njk create mode 100644 install_template/templates/products/replication-server/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index c600e1c7120..5ccc367a8ce 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -646,6 +646,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [3.4.2] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [3.4.2] - name: Ubuntu 22.04 arch: x86_64 supported versions: [3.4.2] @@ -813,6 +816,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [7] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [7] - name: Debian 11 arch: x86_64 supported versions: [7] diff --git a/install_template/templates/products/postgis/rhel-9_arm64.njk b/install_template/templates/products/postgis/rhel-9_arm64.njk new file mode 100644 index 00000000000..781d890ee87 --- /dev/null +++ b/install_template/templates/products/postgis/rhel-9_arm64.njk @@ -0,0 +1,29 @@ +{% extends "products/postgis/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% block prerequisites %} +{{ super() }} +- Enable additional repositories to resolve dependencies: + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` + !!!note + + If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + + !!! +{% endblock prerequisites %} +{% block installCommand %} +```shell +# To install PostGIS 3.4: +sudo dnf -y install edb-as-postgis34 + +# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15: +sudo dnf -y install edb-as-postgis3 + +# To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: +sudo dnf -y install edb-as-postgis +``` +{% include "./_epasVersionInPostGISPackageName.njk" %} +{% endblock installCommand %} + + diff --git a/install_template/templates/products/replication-server/rhel-9_arm64.njk b/install_template/templates/products/replication-server/rhel-9_arm64.njk new file mode 100644 index 00000000000..62ec8c125f5 --- /dev/null +++ b/install_template/templates/products/replication-server/rhel-9_arm64.njk @@ -0,0 +1,3 @@ +{% extends "products/replication-server/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file From 18345f7d2dbbf1b0789f13464c515a386ab1b16a Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 10:52:08 -0500 Subject: [PATCH 22/65] Generated file changes to support RHEL9 on ARM64 for PostGIS and Replication Server --- product_docs/docs/eprs/7/installing/index.mdx | 6 ++ .../7/installing/linux_arm64/eprs_rhel_9.mdx | 62 ++++++++++++++++ .../eprs/7/installing/linux_arm64/index.mdx | 7 ++ .../docs/postgis/3/installing/index.mdx | 8 +- .../3/installing/linux_arm64/index.mdx | 7 ++ .../installing/linux_arm64/postgis_rhel_9.mdx | 73 +++++++++++++++++++ 6 files changed, 162 insertions(+), 1 deletion(-) create mode 100644 product_docs/docs/eprs/7/installing/linux_arm64/eprs_rhel_9.mdx create mode 100644 product_docs/docs/postgis/3/installing/linux_arm64/postgis_rhel_9.mdx diff --git a/product_docs/docs/eprs/7/installing/index.mdx b/product_docs/docs/eprs/7/installing/index.mdx index 4719e38ab4c..df9e6de11e6 100644 --- a/product_docs/docs/eprs/7/installing/index.mdx +++ b/product_docs/docs/eprs/7/installing/index.mdx @@ -59,6 +59,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/eprs_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/eprs_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/eprs_debian_12) diff --git a/product_docs/docs/eprs/7/installing/linux_arm64/eprs_rhel_9.mdx b/product_docs/docs/eprs/7/installing/linux_arm64/eprs_rhel_9.mdx new file mode 100644 index 00000000000..d651e4c6cf2 --- /dev/null +++ b/product_docs/docs/eprs/7/installing/linux_arm64/eprs_rhel_9.mdx @@ -0,0 +1,62 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing Replication Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /eprs/7/03_installation/03_installing_rpm_package/arm64/eprs_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the 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. + +To install all Replication Server components: + +```shell +sudo dnf -y install edb-xdb +``` + +To install an individual component: + +```shell +sudo dnf -y install +``` + +Where `` is: + +| Package name | Component | +| -------------------- | --------------------------------------------------------------------- | +| `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/installing/installing_jdbc_driver) for details. diff --git a/product_docs/docs/eprs/7/installing/linux_arm64/index.mdx b/product_docs/docs/eprs/7/installing/linux_arm64/index.mdx index c3bab4f2b74..f456da6a0aa 100644 --- a/product_docs/docs/eprs/7/installing/linux_arm64/index.mdx +++ b/product_docs/docs/eprs/7/installing/linux_arm64/index.mdx @@ -11,11 +11,18 @@ redirects: - /eprs/latest/03_installation/03_installing_rpm_package/arm64/ navigation: + - eprs_rhel_9 - eprs_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](eprs_rhel_9) + +- [Oracle Linux (OL) 9](eprs_rhel_9) + ### Debian and derivatives - [Debian 12](eprs_debian_12) diff --git a/product_docs/docs/postgis/3/installing/index.mdx b/product_docs/docs/postgis/3/installing/index.mdx index e1c63fe9183..eb8ea65c5bd 100644 --- a/product_docs/docs/postgis/3/installing/index.mdx +++ b/product_docs/docs/postgis/3/installing/index.mdx @@ -14,8 +14,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le - windows - upgrading - uninstalling @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/postgis_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/postgis_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/postgis_debian_12) diff --git a/product_docs/docs/postgis/3/installing/linux_arm64/index.mdx b/product_docs/docs/postgis/3/installing/linux_arm64/index.mdx index 776defb5b04..1ce65b69c07 100644 --- a/product_docs/docs/postgis/3/installing/linux_arm64/index.mdx +++ b/product_docs/docs/postgis/3/installing/linux_arm64/index.mdx @@ -9,11 +9,18 @@ navTitle: "On Linux ARM64" redirects: navigation: + - postgis_rhel_9 - postgis_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](postgis_rhel_9) + +- [Oracle Linux (OL) 9](postgis_rhel_9) + ### Debian and derivatives - [Debian 12](postgis_debian_12) diff --git a/product_docs/docs/postgis/3/installing/linux_arm64/postgis_rhel_9.mdx b/product_docs/docs/postgis/3/installing/linux_arm64/postgis_rhel_9.mdx new file mode 100644 index 00000000000..cf8ef005e3a --- /dev/null +++ b/product_docs/docs/postgis/3/installing/linux_arm64/postgis_rhel_9.mdx @@ -0,0 +1,73 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing PostGIS on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /postgis/latest/01a_installing_postgis/installing_on_linux/arm64/postgis_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- Enable additional repositories to resolve dependencies: + + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` + + !!!note + + If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-8-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + + !!! + +## Install the package + +```shell +# To install PostGIS 3.4: +sudo dnf -y install edb-as-postgis34 + +# To install PostGIS 3.1 using EDB Postgres Advanced Server 13-15: +sudo dnf -y install edb-as-postgis3 + +# To install PostGIS 3.1 using EDB Postgres Advanced Server 11-12: +sudo dnf -y install edb-as-postgis +``` + +Where `` is the version of EDB Postgres Advanced Server. Replace `` with the version of EDB Postgres Advanced Server you are using. For example, `edb-as15-postgis34`. From 1268b28b30ee463a43506859337fd91e261344e8 Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 11:15:24 -0500 Subject: [PATCH 23/65] Template changes to support RHEL9 on ARM64 for PEM (agent and server) --- install_template/config.yaml | 6 ++++++ .../rhel-9_arm64.njk | 3 +++ .../rhel-9_arm64.njk | 11 +++++++++++ 3 files changed, 20 insertions(+) create mode 100644 install_template/templates/products/postgres-enterprise-manager-agent/rhel-9_arm64.njk create mode 100644 install_template/templates/products/postgres-enterprise-manager-server/rhel-9_arm64.njk diff --git a/install_template/config.yaml b/install_template/config.yaml index 5ccc367a8ce..54630902297 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -690,6 +690,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [9] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [9] - name: RHEL 9 arch: ppc64le supported versions: [9] @@ -731,6 +734,9 @@ products: - name: RHEL 9 or OL 9 arch: x86_64 supported versions: [9] + - name: RHEL 9 or OL 9 + arch: arm64 + supported versions: [9] - name: RHEL 9 arch: ppc64le supported versions: [9] diff --git a/install_template/templates/products/postgres-enterprise-manager-agent/rhel-9_arm64.njk b/install_template/templates/products/postgres-enterprise-manager-agent/rhel-9_arm64.njk new file mode 100644 index 00000000000..86cb86a3880 --- /dev/null +++ b/install_template/templates/products/postgres-enterprise-manager-agent/rhel-9_arm64.njk @@ -0,0 +1,3 @@ +{% extends "products/postgres-enterprise-manager-agent/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% block prerequisites %}{% endblock prerequisites %} \ No newline at end of file diff --git a/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_arm64.njk b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_arm64.njk new file mode 100644 index 00000000000..61856ff934e --- /dev/null +++ b/install_template/templates/products/postgres-enterprise-manager-server/rhel-9_arm64.njk @@ -0,0 +1,11 @@ +{% extends "products/postgres-enterprise-manager-server/base.njk" %} +{% set platformBaseTemplate = "rhel-9-or-ol-9" %} +{% set ssutilsName %}sslutils_ postgresql-contrib{% endset %} +{% set ssutilsExtendedName %}edb-postgresextended-contrib{% endset %} +{% set ssutilsExtendedFirstName %}edb-postgresextended-sslutils{% endset %} +{% block prerequisites %}{% endblock prerequisites %} +{% block firewallCommand %}```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ```{% endblock firewallCommand %} From 4cb40fa4dc52a3b98a16e531685a4ee27d639dfa Mon Sep 17 00:00:00 2001 From: David Wicinas <93669463+dwicinas@users.noreply.github.com> Date: Wed, 6 Nov 2024 11:16:10 -0500 Subject: [PATCH 24/65] Generated file changes to support RHEL9 on ARM64 for PEM (agent and server) --- product_docs/docs/pem/9/installing/index.mdx | 8 +- .../pem/9/installing/linux_arm64/index.mdx | 7 ++ .../9/installing/linux_arm64/pem_rhel_9.mdx | 97 +++++++++++++++++++ .../docs/pem/9/installing_pem_agent/index.mdx | 8 +- .../linux_arm64/index.mdx | 7 ++ .../linux_arm64/pem_agent_rhel_9.mdx | 42 ++++++++ 6 files changed, 167 insertions(+), 2 deletions(-) create mode 100644 product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx create mode 100644 product_docs/docs/pem/9/installing_pem_agent/linux_arm64/pem_agent_rhel_9.mdx diff --git a/product_docs/docs/pem/9/installing/index.mdx b/product_docs/docs/pem/9/installing/index.mdx index 38af403dee0..61bb23e5dc4 100644 --- a/product_docs/docs/pem/9/installing/index.mdx +++ b/product_docs/docs/pem/9/installing/index.mdx @@ -18,8 +18,8 @@ navigation: - prerequisites - dependencies - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le - windows - creating_pem_repository_in_isolated_network - configuring_the_pem_server_on_linux @@ -61,6 +61,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pem_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pem_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/pem_debian_12) diff --git a/product_docs/docs/pem/9/installing/linux_arm64/index.mdx b/product_docs/docs/pem/9/installing/linux_arm64/index.mdx index 7fd8cff272d..0fb39a9821e 100644 --- a/product_docs/docs/pem/9/installing/linux_arm64/index.mdx +++ b/product_docs/docs/pem/9/installing/linux_arm64/index.mdx @@ -10,11 +10,18 @@ navTitle: "On Linux ARM64" redirects: navigation: + - pem_rhel_9 - pem_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pem_rhel_9) + +- [Oracle Linux (OL) 9](pem_rhel_9) + ### Debian and derivatives - [Debian 12](pem_debian_12) diff --git a/product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx b/product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx new file mode 100644 index 00000000000..9cbcb213627 --- /dev/null +++ b/product_docs/docs/pem/9/installing/linux_arm64/pem_rhel_9.mdx @@ -0,0 +1,97 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing Postgres Enterprise Manager server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /pem/9/installing_pem_server/pem_server_inst_linux/installing_pem_server_using_edb_repository/arm64/pem_server_rhel9_arm + - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ibm_power_ppc64le/pem_server_rhel9_arm/ + - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/ppc64le/pem_server_rhel9_arm/ + - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86_amd64/pem_server_rhel9_arm/ + - /pem/9/installing_pem_server/installing_on_linux/using_edb_repository/x86/pem_server_rhel9_arm/ +--- + +You can install PEM on a single server, or you can install the web application server and the backend database on two separate servers. You must prepare your servers for PEM installation. + +After fulfilling the prerequisites and completing the installation procedure described in the following steps, you must [configure](/pem/9/installing/configuring_the_pem_server_on_linux.mdx) PEM. If you're using two servers, install and configure PEM on both servers. + +## Prerequisites + +Before you begin the installation process: + +1. Install a [supported Postgres instance](/pem/latest/#postgres-compatibility) for PEM to use as a backend database. + + You can install this instance on the same server to be used for the PEM web application or on a separate server. You can also use an existing Postgres instance if it is configured as detailed in the next steps. + +2. Configure authentication on the Postgres backend database by updating the `pg_hba.conf` file. + + Make the following changes manually, prior to configuration. (Additional changes are necessary during [configuration](../configuring_the_pem_server_on_linux.mdx).) + + - To create the relations required for PEM, the PEM configuration script connects to the Postgres backend database as a superuser of your choice using password authentication. This requires you to permit your chosen superuser to authenticate using a password. This user must be able to connect from any location where you run the configuration script. In practice, this means the server where the backend database is located and the server where the PEM web application is to be installed, if they're different. + + - To allow the chosen superuser to connect using password authentication, add a line to `pg_hba.conf` that allows `host` connections using `md5` or `scram-sha-256` authentication, such as `host all superusername 127.0.0.1/32 scram-sha-256`. + + !!! Note + If you're using EDB Postgres Advanced Server, see [Modifying the pg_hba.conf file](/pem/latest/managing_database_server/#modifying-the-pg_hbaconf-file). + + If you're using PostgreSQL, see [Client Authentication](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). + !!! + +3. Verify that the `sslutils` extension is installed on your Postgres server. + + If you're using PostgreSQL or EDB Postgres Extended Server on RHEL/AlmaLinux/Rocky Linux or SLES, you also need to install the `hstore contrib` module. + + - If you're using EDB Postgres Advanced Server, you can install the `sslutils` extension as follows, where `` is the EDB Postgres Advanced server version. + + ```shell + sudo dnf install edb-as-server-sslutils + ``` + + - If you're using PostgreSQL, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the PostgreSQL version. + ```shell + sudo dnf install sslutils_ postgresql-contrib + ``` + - If you're using EDB Postgres Extended Server, you can install the `sslutils` and, if required, `hstore` modules as follows, where `` is the EDB Postgres Extended Server version. + ```shell + sudo dnf install edb-postgresextended-sslutils edb-postgresextended-contrib + ``` + +4. If you're using a firewall, allow access to port 8443 on the server where the PEM web application will be located: + + ```shell + firewall-cmd --permanent --zone=public --add-port=8443/tcp + + firewall-cmd --reload + ``` + +5. Make sure the components Postgres Enterprise Manager depends on are up to date on all servers. You can do this by updating the whole system using your package manager as shown below. + If you prefer to update individual packages, a full list of dependencies is provided in [Dependencies of the PEM Server and Agent on Linux](../dependencies.md). + + ```shell + sudo dnf upgrade + ``` + +## Install the package + +```shell +sudo dnf -y install edb-pem +``` + +## Initial configuration + +```shell +# You can configure the PEM server using the following command: +sudo /usr/edb/pem/bin/configure-pem-server.sh +``` + +For more details, see [Configuring the PEM server on Linux](../configuring_the_pem_server_on_linux/). + +!!! Note + + - The operating system user pem is created while installing the PEM server. The PEM server web application is a WSGI application, which runs under Apache HTTPD. The pem application data and the session is saved to this user's home directory. + +## Supported locales + +Currently, the Postgres Enterprise Manager server and web interface support a locale of `English(US) en_US` and use of a period (.) as a language separator character. Using an alternate locale or a separator character other than a period might cause errors. diff --git a/product_docs/docs/pem/9/installing_pem_agent/index.mdx b/product_docs/docs/pem/9/installing_pem_agent/index.mdx index 23f4bb5a93b..1237796ac8a 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/index.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/index.mdx @@ -15,8 +15,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le - windows_agent --- @@ -56,6 +56,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pem_agent_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pem_agent_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/pem_agent_debian_12) diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_arm64/index.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_arm64/index.mdx index 393d32d65aa..e8bb443eb7b 100644 --- a/product_docs/docs/pem/9/installing_pem_agent/linux_arm64/index.mdx +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_arm64/index.mdx @@ -10,11 +10,18 @@ redirects: - /pem/latest/installing_pem_agent/installing_on_linux/arm64/ navigation: + - pem_agent_rhel_9 - pem_agent_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pem_agent_rhel_9) + +- [Oracle Linux (OL) 9](pem_agent_rhel_9) + ### Debian and derivatives - [Debian 12](pem_agent_debian_12) diff --git a/product_docs/docs/pem/9/installing_pem_agent/linux_arm64/pem_agent_rhel_9.mdx b/product_docs/docs/pem/9/installing_pem_agent/linux_arm64/pem_agent_rhel_9.mdx new file mode 100644 index 00000000000..ba5078b9d38 --- /dev/null +++ b/product_docs/docs/pem/9/installing_pem_agent/linux_arm64/pem_agent_rhel_9.mdx @@ -0,0 +1,42 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing Postgres Enterprise Manager agent on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /pem/9/installing_pem_agent/installing_on_linux/arm64/pem_agent_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +## Install the package + +```shell +sudo dnf -y install edb-pem-agent +``` + +After installing PEM agent, you need to register the PEM agent. For detailed information see [Registering an agent](../../registering_agent/). From 2b413d7f9982f11af84dbcc5cff5a7b71be1626d Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 26 Nov 2024 11:43:30 +0530 Subject: [PATCH 25/65] Added latest product version to few products and its install topics --- install_template/config.yaml | 16 +- .../docs/epas/17/installing/index.mdx | 8 +- .../17/installing/linux_arm64/epas_rhel_9.mdx | 157 ++++++++++++++++++ .../epas/17/installing/linux_arm64/index.mdx | 7 + .../ocl_connector/17/installing/index.mdx | 6 + .../17/installing/linux_arm64/index.mdx | 7 + .../17/installing/linux_arm64/ocl_rhel_9.mdx | 52 ++++++ product_docs/docs/pge/17/installing/index.mdx | 6 + .../pge/17/installing/linux_arm64/index.mdx | 7 + .../17/installing/linux_arm64/pge_rhel_9.mdx | 129 ++++++++++++++ 10 files changed, 386 insertions(+), 9 deletions(-) create mode 100644 product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx create mode 100644 product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_rhel_9.mdx create mode 100644 product_docs/docs/pge/17/installing/linux_arm64/pge_rhel_9.mdx diff --git a/install_template/config.yaml b/install_template/config.yaml index 54630902297..0485e53a8a4 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -41,10 +41,10 @@ products: supported versions: [42.7.3.2] - name: RHEL 9 arch: ppc64le - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: RHEL 9 or OL 9 arch: arm64 - supported versions: [42.7.3.1] + supported versions: [42.7.3.2] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 supported versions: [42.7.3.2] @@ -135,10 +135,10 @@ products: supported versions: [14, 15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: RHEL 9 or OL 9 arch: arm64 - supported versions: [14, 15, 16] + supported versions: [14, 15, 16, 17] - name: Debian 11 arch: x86_64 supported versions: [14, 15, 16, 17] @@ -349,10 +349,10 @@ products: supported versions: [11, 12, 13, 14, 15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [11, 12, 13, 14, 15, 16] + supported versions: [11, 12, 13, 14, 15, 16, 17] - name: RHEL 9 or OL 9 arch: arm64 - supported versions: [13, 14, 15, 16] + supported versions: [13, 14, 15, 16, 17] - name: RHEL 9 arch: ppc64le supported versions: [11, 12, 13, 14, 15, 16, 17] @@ -393,10 +393,10 @@ products: supported versions: [15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: RHEL 9 or OL 9 arch: arm64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Debian 12 arch: x86_64 supported versions: [16, 17] diff --git a/product_docs/docs/epas/17/installing/index.mdx b/product_docs/docs/epas/17/installing/index.mdx index 8b47c5d7b99..f98853d0098 100644 --- a/product_docs/docs/epas/17/installing/index.mdx +++ b/product_docs/docs/epas/17/installing/index.mdx @@ -14,8 +14,8 @@ redirects: navigation: - linux_x86_64 - - linux_ppc64le - linux_arm64 + - linux_ppc64le - windows - linux_install_details - windows_install_details @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/epas_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/epas_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/epas_debian_12) diff --git a/product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx b/product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx new file mode 100644 index 00000000000..aa04ebba1fb --- /dev/null +++ b/product_docs/docs/epas/17/installing/linux_arm64/epas_rhel_9.mdx @@ -0,0 +1,157 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Advanced Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_rhel9_arm + - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +- If you are also installing PostGIS, enable additional repositories to resolve dependencies: + + ```shell + ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-9-${ARCH}-rpms" + ``` + + !!!note + + If you are using a public cloud RHEL image, `subscription manager` may not be enabled and enabling it may incur unnecessary charges. Equivalent packages may be available under a different name such as `codeready-builder-for-rhel-9-rhui-rpms`. Consult the documentation for the RHEL image you are using to determine how to install `codeready-builder`. + + !!! + +## Install the package + +```shell +sudo dnf -y install edb-as-server +``` + +Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 17, the package name is `edb-as17-server`. + +To install an individual component: + +```shell +sudo dnf -y install +``` + +Where `package_name` can be any of the available packages from the [available package list](/epas/17/installing/linux_install_details/rpm_packages/). + +Installing the server package creates an operating system user named enterprisedb. The user is assigned a user ID (UID) and a group ID (GID). The user has no default password. Use the `passwd` command to assign a password for the user. The default shell for the user is `bash`, and the user's home directory is `/var/lib/edb/as17`. + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-as-17-setup` script creates a cluster in Oracle-compatible mode with the `edb` sample database in the cluster. To create a cluster in Postgres mode, see [Initializing the cluster in Postgres mode](../linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options/#initializing-the-cluster-in-postgres-mode). + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb + +sudo systemctl start edb-as-17 +``` + +To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo su - enterprisedb + +psql edb +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE enterprisedb IDENTIFIED BY password; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +psql (17.0.0, server 17.0.0) +You are now connected to database "hr" as user "enterprisedb". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` diff --git a/product_docs/docs/epas/17/installing/linux_arm64/index.mdx b/product_docs/docs/epas/17/installing/linux_arm64/index.mdx index c1e50ddb610..10c64a6a576 100644 --- a/product_docs/docs/epas/17/installing/linux_arm64/index.mdx +++ b/product_docs/docs/epas/17/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB Postgres Advanced Server on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - epas_rhel_9 - epas_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](epas_rhel_9) + +- [Oracle Linux (OL) 9](epas_rhel_9) + ### Debian and derivatives - [Debian 12](epas_debian_12) diff --git a/product_docs/docs/ocl_connector/17/installing/index.mdx b/product_docs/docs/ocl_connector/17/installing/index.mdx index 78a2585180f..6428feff91d 100644 --- a/product_docs/docs/ocl_connector/17/installing/index.mdx +++ b/product_docs/docs/ocl_connector/17/installing/index.mdx @@ -57,6 +57,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/ocl_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/ocl_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/ocl_debian_12) diff --git a/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx b/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx index 15061e86556..23b7a315d78 100644 --- a/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx +++ b/product_docs/docs/ocl_connector/17/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB OCL Connector on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - ocl_rhel_9 - ocl_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](ocl_rhel_9) + +- [Oracle Linux (OL) 9](ocl_rhel_9) + ### Debian and derivatives - [Debian 12](ocl_debian_12) diff --git a/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_rhel_9.mdx b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_rhel_9.mdx new file mode 100644 index 00000000000..908f9e3faeb --- /dev/null +++ b/product_docs/docs/ocl_connector/17/installing/linux_arm64/ocl_rhel_9.mdx @@ -0,0 +1,52 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB OCL Connector on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: + - /ocl_connector/17/04_open_client_library/01_installing_and_configuring_the_ocl_connector/install_on_linux_using_edb_repo/arm64/ocl_rhel9_arm +--- + +## Prerequisites + +Before you begin the installation process: + +- Install Postgres on a host that the product can connect to using a connection string. It doesn't need to be on the same host. See: + + - [Installing EDB Postgres Advanced Server](/epas/latest/installing/) + + - [Installing PostgreSQL](https://www.postgresql.org/download/) + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-oci +sudo dnf -y install edb-oci-devel +``` diff --git a/product_docs/docs/pge/17/installing/index.mdx b/product_docs/docs/pge/17/installing/index.mdx index 0cc88e55d5e..4883cc3bb07 100644 --- a/product_docs/docs/pge/17/installing/index.mdx +++ b/product_docs/docs/pge/17/installing/index.mdx @@ -31,6 +31,12 @@ Select a link to access the applicable installation instructions: ## Linux [AArch64 (ARM64)](linux_arm64) +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](linux_arm64/pge_rhel_9) + +- [Oracle Linux (OL) 9](linux_arm64/pge_rhel_9) + ### Debian and derivatives - [Debian 12](linux_arm64/pge_debian_12) diff --git a/product_docs/docs/pge/17/installing/linux_arm64/index.mdx b/product_docs/docs/pge/17/installing/linux_arm64/index.mdx index 230f6000758..04d27036fdd 100644 --- a/product_docs/docs/pge/17/installing/linux_arm64/index.mdx +++ b/product_docs/docs/pge/17/installing/linux_arm64/index.mdx @@ -3,11 +3,18 @@ title: "Installing EDB Postgres Extended Server on Linux AArch64 (ARM64)" navTitle: "On Linux ARM64" navigation: + - pge_rhel_9 - pge_debian_12 --- Operating system-specific install instructions are described in the corresponding documentation: +### Red Hat Enterprise Linux (RHEL) and derivatives + +- [RHEL 9](pge_rhel_9) + +- [Oracle Linux (OL) 9](pge_rhel_9) + ### Debian and derivatives - [Debian 12](pge_debian_12) diff --git a/product_docs/docs/pge/17/installing/linux_arm64/pge_rhel_9.mdx b/product_docs/docs/pge/17/installing/linux_arm64/pge_rhel_9.mdx new file mode 100644 index 00000000000..37ed943c9e6 --- /dev/null +++ b/product_docs/docs/pge/17/installing/linux_arm64/pge_rhel_9.mdx @@ -0,0 +1,129 @@ +--- +navTitle: RHEL 9 or OL 9 +title: Installing EDB Postgres Extended Server on RHEL 9 or OL 9 arm64 +# This topic is generated from templates. If you have feedback on it, instead of +# editing the page and creating a pull request, please enter a GitHub issue and +# the documentation team will update the templates accordingly. + +redirects: +--- + +## Prerequisites + +Before you begin the installation process: + +- Set up the EDB repository. + + Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. + + To determine if your repository exists, enter this command: + + `dnf repolist | grep enterprisedb` + + If no output is generated, the repository isn't installed. + + To set up the EDB repository: + + 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). + + 1. Select the button that provides access to the EDB repository. + + 1. Select the platform and software that you want to download. + + 1. Follow the instructions for setting up the EDB repository. + +- Install the EPEL repository: + ```shell + sudo dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm + ``` + +## Install the package + +```shell +sudo dnf -y install edb-postgresextended17-server edb-postgresextended17-contrib +``` + +## Initial configuration + +Getting started with your cluster involves logging in, ensuring the installation and initial configuration was successful, connecting to your cluster, and creating the user password. + +First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. + +```shell +sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/pge17/bin/edb-pge-17-setup initdb + +sudo systemctl start edb-pge-17 +``` + +To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. + +```shell +sudo -iu postgres + +psql postgres +``` + +The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. + +Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). + +```sql +ALTER ROLE postgres with PASSWORD 'password'; +``` + +## Experiment + +Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. + +First, use psql to create a database named `hr` to hold human resource information. + +```sql +# running in psql +CREATE DATABASE hr; +__OUTPUT__ +CREATE DATABASE +``` + +Connect to the `hr` database inside psql: + +``` +\c hr +__OUTPUT__ +You are now connected to database "hr" as user "postgres". +``` + +Create columns to hold department numbers, unique department names, and locations: + +``` +CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk +PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc +varchar(13)); +__OUTPUT__ +CREATE TABLE +``` + +Insert values into the `dept` table: + +``` +INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); +__OUTPUT__ +INSERT 0 1 +``` + +``` +INSERT into dept VALUES (20,'RESEARCH','DALLAS'); +__OUTPUT__ +INSERT 0 1 +``` + +View the table data by selecting the values from the table: + +``` +SELECT * FROM dept; +__OUTPUT__ +deptno | dname | loc +--------+------------+---------- +10 | ACCOUNTING | NEW YORK +20 | RESEARCH | DALLAS +(2 rows) +``` From cf7bb601eb544336279d54cd8fe7309b72a71a23 Mon Sep 17 00:00:00 2001 From: sergioenterprisedb <86610980+sergioenterprisedb@users.noreply.github.com> Date: Thu, 21 Nov 2024 18:48:29 +0100 Subject: [PATCH 26/65] Update 04-ConfiguringHashicorpVault.mdx --- .../HashicorpVault/04-ConfiguringHashicorpVault.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx b/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx index 88222b36acf..48c0975957f 100644 --- a/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx +++ b/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx @@ -36,7 +36,7 @@ If you run a check and find that your system doesn't have Python installed, you ## Install Pykmip Once your EDB Repository is installed on your server, you can then install the PyKMIP utility. -- As root user, issue the `install python3-pykmip` command. This example uses a RHEL8 server, so the command is `dnf install python3-pymkip`. +- As root user, issue the `install python3-pykmip` command. This example uses a RHEL8 server, so the command is `dnf install python3-pykmip`. The output looks something like: @@ -230,4 +230,4 @@ IgIhAMb3y3xRXwddt2ejaow1GytysRz4LoxC3B5dLn1LoCpI -----END CERTIFICATE----- ``` -Once you have all of the required certificates, you're ready to use the Hashicorp Vault secrets engine with your EDB Postgres distribution with TDE. \ No newline at end of file +Once you have all of the required certificates, you're ready to use the Hashicorp Vault secrets engine with your EDB Postgres distribution with TDE. From 3fd8d9b462820e1f8f8c1b44a020e9345d4c2fd3 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 26 Nov 2024 10:41:21 +0100 Subject: [PATCH 27/65] minor rewording --- .../HashicorpVault/04-ConfiguringHashicorpVault.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx b/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx index 48c0975957f..fc1848ef4be 100644 --- a/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx +++ b/advocacy_docs/partner_docs/HashicorpVault/04-ConfiguringHashicorpVault.mdx @@ -230,4 +230,4 @@ IgIhAMb3y3xRXwddt2ejaow1GytysRz4LoxC3B5dLn1LoCpI -----END CERTIFICATE----- ``` -Once you have all of the required certificates, you're ready to use the Hashicorp Vault secrets engine with your EDB Postgres distribution with TDE. +Once you have all of the required certificates, you're ready to use the Hashicorp Vault secrets engine with your EDB Postgres distribution and TDE. From 01e09fd0a4e68b76cad040c5ae50d5edd1ecf8d9 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Tue, 26 Nov 2024 09:48:13 +0000 Subject: [PATCH 28/65] 3 part version number added Signed-off-by: Dj Walker-Morgan --- product_docs/docs/tpa/23/rel_notes/index.mdx | 4 ++-- .../{tpa_23.35_rel_notes.yml => tpa_23.35.0_rel_notes.yml} | 4 ++-- .../{tpa_23.35_rel_notes.mdx => tpa_23.35.0_rel_notes.mdx} | 6 +++--- 3 files changed, 7 insertions(+), 7 deletions(-) rename product_docs/docs/tpa/23/rel_notes/src/{tpa_23.35_rel_notes.yml => tpa_23.35.0_rel_notes.yml} (99%) rename product_docs/docs/tpa/23/rel_notes/{tpa_23.35_rel_notes.mdx => tpa_23.35.0_rel_notes.mdx} (98%) diff --git a/product_docs/docs/tpa/23/rel_notes/index.mdx b/product_docs/docs/tpa/23/rel_notes/index.mdx index 651be5a8139..2eddffa4239 100644 --- a/product_docs/docs/tpa/23/rel_notes/index.mdx +++ b/product_docs/docs/tpa/23/rel_notes/index.mdx @@ -3,7 +3,7 @@ title: Trusted Postgres Architect release notes navTitle: Release notes description: Release notes for Trusted Postgres Architect and later navigation: - - tpa_23.35_rel_notes + - tpa_23.35.0_rel_notes - tpa_23.34.1_rel_notes - tpa_23.34_rel_notes - tpa_23.33_rel_notes @@ -37,7 +37,7 @@ The Trusted Postgres Architect documentation describes the latest version of Tru | Trusted Postgres Architect version | Release Date | |---|---| -| [23.35](./tpa_23.35_rel_notes) | 25 Nov 2024 | +| [23.35.0](./tpa_23.35.0_rel_notes) | 25 Nov 2024 | | [23.34.1](./tpa_23.34.1_rel_notes) | 09 Sep 2024 | | [23.34](./tpa_23.34_rel_notes) | 22 Aug 2024 | | [23.33](./tpa_23.33_rel_notes) | 24 Jun 2024 | diff --git a/product_docs/docs/tpa/23/rel_notes/src/tpa_23.35_rel_notes.yml b/product_docs/docs/tpa/23/rel_notes/src/tpa_23.35.0_rel_notes.yml similarity index 99% rename from product_docs/docs/tpa/23/rel_notes/src/tpa_23.35_rel_notes.yml rename to product_docs/docs/tpa/23/rel_notes/src/tpa_23.35.0_rel_notes.yml index 2a3d85e7a6d..ceef28c7ea8 100644 --- a/product_docs/docs/tpa/23/rel_notes/src/tpa_23.35_rel_notes.yml +++ b/product_docs/docs/tpa/23/rel_notes/src/tpa_23.35.0_rel_notes.yml @@ -1,8 +1,8 @@ product: Trusted Postgres Architect -version: 23.35 +version: 23.35.0 date: 25 November 2024 intro: | - New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.35 include the following: + New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.35.0 include the following: highlights: | - Options for STIG/CIS compliance. - Support for PGD Lightweight architecture diff --git a/product_docs/docs/tpa/23/rel_notes/tpa_23.35_rel_notes.mdx b/product_docs/docs/tpa/23/rel_notes/tpa_23.35.0_rel_notes.mdx similarity index 98% rename from product_docs/docs/tpa/23/rel_notes/tpa_23.35_rel_notes.mdx rename to product_docs/docs/tpa/23/rel_notes/tpa_23.35.0_rel_notes.mdx index 6f8bbb20dd3..161be7b308e 100644 --- a/product_docs/docs/tpa/23/rel_notes/tpa_23.35_rel_notes.mdx +++ b/product_docs/docs/tpa/23/rel_notes/tpa_23.35.0_rel_notes.mdx @@ -1,11 +1,11 @@ --- -title: Trusted Postgres Architect 23.35 release notes -navTitle: Version 23.35 +title: Trusted Postgres Architect 23.35.0 release notes +navTitle: Version 23.35.0 --- Released: 25 November 2024 -New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.35 include the following: +New features, enhancements, bug fixes, and other changes in Trusted Postgres Architect 23.35.0 include the following: ## Highlights From 20165e6750f6249b7ef13f446698937049d2fa7a Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Mon, 25 Nov 2024 16:53:08 -0500 Subject: [PATCH 29/65] Edits to PGD: document compatibility with EPAS automatic partitioning #6289 --- product_docs/docs/pgd/5.6/scaling.mdx | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/product_docs/docs/pgd/5.6/scaling.mdx b/product_docs/docs/pgd/5.6/scaling.mdx index 612e43afda4..88864a7a006 100644 --- a/product_docs/docs/pgd/5.6/scaling.mdx +++ b/product_docs/docs/pgd/5.6/scaling.mdx @@ -1,6 +1,6 @@ --- title: PGD AutoPartition -description: How to use autopartioning in PGD to split tables into several partitions. +description: How to use autopartitioning in PGD to split tables into several partitions. redirects: - ../bdr/scaling --- @@ -185,19 +185,19 @@ enabled, then no action occurs. Similarly, use [`bdr.autopartition_disable()`](/pgd/latest/reference/autopartition#bdrautopartition_disable) to disable autopartitioning on the given table. -## Restrictions on EPAS-native automatic partitioning +## Restrictions on EDB Postgres Advanced Server-native automatic partitioning -EPAS-native automatic partitioning is not supported on PGD. +EDB Postgres Advanced Server-native automatic partitioning isn't supported in PGD. -If the PGD extension is active on an EPAS database, DDL commands to configure -EPAS automatic partitioning (`ALTER TABLE ... SET AUTOMATIC` and `ALTER TABLE ... SET INTERVAL`) -will be rejected. +If the PGD extension is active on an EDB Postgres Advanced Server database, DDL commands to configure +EDB Postgres Advanced Server automatic partitioning (`ALTER TABLE ... SET AUTOMATIC` and `ALTER TABLE ... SET INTERVAL`) +are rejected. -Note that while it is possible to enable the PGD extension on an EPAS database -containing tables configured to use EPAS-native automatic partitioning, it -will not be possible to join further nodes using this node as a source node. +While it's possible to enable the PGD extension on an EDB Postgres Advanced Server database +containing tables configured to use EDB Postgres Advanced Server-native automatic partitioning, it +isn't possible to join more nodes using this node as a source node. -EPAS-native automatic partitioning can be disabled with one of the following +You can disable EDB Postgres Advanced Server-native automatic partitioning with one of the following commands: - `ALTER TABLE ... SET MANUAL` (for list partitioned tables) From f0d55531364da82f4f5c4ab48f2ede7623d52b4a Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> Date: Tue, 26 Nov 2024 10:56:46 +0000 Subject: [PATCH 30/65] Update product_docs/docs/pgd/5.6/scaling.mdx --- product_docs/docs/pgd/5.6/scaling.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5.6/scaling.mdx b/product_docs/docs/pgd/5.6/scaling.mdx index 88864a7a006..49bb625b580 100644 --- a/product_docs/docs/pgd/5.6/scaling.mdx +++ b/product_docs/docs/pgd/5.6/scaling.mdx @@ -187,7 +187,7 @@ to disable autopartitioning on the given table. ## Restrictions on EDB Postgres Advanced Server-native automatic partitioning -EDB Postgres Advanced Server-native automatic partitioning isn't supported in PGD. +EDB Postgres Advanced Server-native automatic partitioning is not supported in PGD. If the PGD extension is active on an EDB Postgres Advanced Server database, DDL commands to configure EDB Postgres Advanced Server automatic partitioning (`ALTER TABLE ... SET AUTOMATIC` and `ALTER TABLE ... SET INTERVAL`) From 35203b2cc265193a51ff111372a5cc60e48eafea Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Tue, 26 Nov 2024 11:03:45 +0000 Subject: [PATCH 31/65] Added KI Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5.6/known_issues.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5.6/known_issues.mdx b/product_docs/docs/pgd/5.6/known_issues.mdx index 2d61b8aa3dc..0f881c854f8 100644 --- a/product_docs/docs/pgd/5.6/known_issues.mdx +++ b/product_docs/docs/pgd/5.6/known_issues.mdx @@ -51,6 +51,8 @@ To modify a commit scope safely, use [`bdr.alter_commit_scope`](/pgd/latest/refe - DDL run in serializable transactions can face the error: `ERROR: could not serialize access due to read/write dependencies among transactions`. A workaround is to run the DDL outside serializable transactions. -- The EPAS 17 data type [`BFILE`](/epas/latest/reference/sql_reference/02_data_types/03a_bfiles/) is not currently supported. This is due to `BFILE` being a file reference that is stored in the database, and the file itself is stored outside the database and not replicated. +- The EBD Postgres Advanced Server 17 data type [`BFILE`](/epas/latest/reference/sql_reference/02_data_types/03a_bfiles/) is not currently supported. This is due to `BFILE` being a file reference that is stored in the database, and the file itself is stored outside the database and not replicated. + +- EDB Postgres Advanced Server's native autopartioning is not supported in PGD. See [Restrictions on EDB Postgres Advanced Server-native automatic partitioning](scaling#restrictions-on-edb-postgres-advanced-server-native-automatic-partitioning) for more information. Details of other design or implementation [limitations](planning/limitations) are also available. From 5722525b67f7716cd43bc5b88d2efb4023add225 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Tue, 26 Nov 2024 17:27:59 +0530 Subject: [PATCH 32/65] PEM - 9.8 release date update --- product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx | 2 +- product_docs/docs/pem/9/pem_rel_notes/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx index 260a735f006..accc025012e 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/980_rel_notes.mdx @@ -3,7 +3,7 @@ title: "Postgres Enterprise Manager 9.8.0 release notes" navTitle: Version 9.8.0 --- -Released: 19th Nov 2024 +Released: 26th Nov 2024 !!! Note This release includes a fix for a bug that previously prevented the correct purging of historical data when the configured retention time expired. As a result, the first purge job to run after this update is expected to delete more data than usual and may take longer to complete. diff --git a/product_docs/docs/pem/9/pem_rel_notes/index.mdx b/product_docs/docs/pem/9/pem_rel_notes/index.mdx index 69890c99b51..7563cce1b6d 100644 --- a/product_docs/docs/pem/9/pem_rel_notes/index.mdx +++ b/product_docs/docs/pem/9/pem_rel_notes/index.mdx @@ -22,7 +22,7 @@ The Postgres Enterprise Manager (PEM) documentation describes the latest version | Version | Release Date | Upstream Merges | Accessibility Conformance | |------------------------|--------------|-----------------|------------------------------------------------------------------| -| [9.8.0](980_rel_notes) | 19 Nov 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | +| [9.8.0](980_rel_notes) | 26 Nov 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | | [9.7.0](970_rel_notes) | 13 Aug 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | | [9.6.0](960_rel_notes) | 15 May 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | | [9.5.1](951_rel_notes) | 04 Mar 2024 | NA | [Conformance Report](https://www.enterprisedb.com/accessibility) | From dfcb93cb68b7d0e9e8cfdb5c10df7558a978781c Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Tue, 26 Nov 2024 13:06:39 +0000 Subject: [PATCH 33/65] Fix compat listings Signed-off-by: Dj Walker-Morgan --- product_docs/docs/pgd/5.6/compatibility.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5.6/compatibility.mdx b/product_docs/docs/pgd/5.6/compatibility.mdx index d7812a703e9..14cd8df9c61 100644 --- a/product_docs/docs/pgd/5.6/compatibility.mdx +++ b/product_docs/docs/pgd/5.6/compatibility.mdx @@ -32,7 +32,7 @@ The following tables show the versions of EDB Postgres Distributed and their com | Oracle Linux 8/9 | Yes | Yes | | Rocky Linux/AlmaLinux | Yes | Yes | | SUSE Linux Enterprise Server 15SP5 | Yes | Yes | -| Ubuntu 20.04/22.04/24.04 | Yes | Yes | +| Ubuntu 20.04/22.04 | Yes | Yes | | Debian 11/12 | Yes | Yes | ### Linux ppc64le From bce67c641974280b6b0c8be06ad9bc53b86cc7fb Mon Sep 17 00:00:00 2001 From: Josh Earlenbaugh Date: Tue, 26 Nov 2024 09:58:05 -0500 Subject: [PATCH 34/65] DOCS-1131 Fixed typo and added missing release note item in JDBC release notes (#6299) * Fixed typo and added missing release note item. * Added 'Bug' to fixes according to style guide, formatted messages, and minor rewording --------- Co-authored-by: gvasquezvargas --- .../jdbc_42.7.3.2_rel_notes.mdx | 33 +++++++------------ 1 file changed, 11 insertions(+), 22 deletions(-) diff --git a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx index 5dfa55d500e..f040588d30f 100644 --- a/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx +++ b/product_docs/docs/jdbc_connector/42.7.3.2/01_jdbc_rel_notes/jdbc_42.7.3.2_rel_notes.mdx @@ -9,25 +9,14 @@ The EDB JDBC connector provides connectivity between a Java application and an E New features, enhancements, bug fixes, and other changes in the EDB JDBC Connector 42.7.3.2 include: -| Type | Description -|---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| Performance | Improved parsing performance with large SQL (MTK/SQL Plus). | -| Enhancement | Added support for EDB Postgres Advanced Server 17.2. | -| Bug fix | Fixes an incompatibility issue with JDK 8 that found in version 42.7.3.1 of the `edb-jdbc18` driver. | -| Fix | edb-jdbc installation should not install a lower JDK version when a higher version is installed. | -| Fix | Fixed issue where `Message.getJMSMessageID()` returns `null`. | -| Fix | Fixed issue with determining the queue table for a queue when there is more than one queue defined within a single schema. | -| Fix | Fixed issue where EDBJmsMessageConsumer.receiveNoWait() always returns null even when messages are available on the queue. -| Fix | Fixed issue where EDBJmsMessageConsuder() [without time parameter] is supposed to block until a message is available. | - - - - - - - - - - - - +| Type | Description | +|-------------|----------------------------------------------------------------------------------------------------------------------------| +| Performance | Improved parsing performance with large SQL (MTK/SQL Plus). | +| Enhancement | Added support for EDB Postgres Advanced Server 17.2. | +| Bug fix | Fixes an incompatibility issue with JDK 8 that was found in version 42.7.3.1 of the `edb-jdbc18` driver. | +| Bug Fix | `edb-jdbc` installation should not install a lower JDK version when a higher version is installed. | +| Bug Fix | Fixed issue where `Message.getJMSMessageID()` returns `null`. | +| Bug Fix | Fixed issue with determining the queue table for a queue when there is more than one queue defined within a single schema. | +| Bug Fix | Fixed issue where `EDBJmsMessageConsumer.receiveNoWait()` returns `null` even when messages are available on the queue. | +| Bug Fix | Fixed issue where `EDBJmsMessageConsumer.receive()` [without time parameter] fails to block until a message is available. | +| Bug Fix | Fixed issue where `EDBJmsMessageConsumer.receive(timeout)` doesn't honor the timeout specified. | \ No newline at end of file From 7c5d6b3fe889bd9e8276230db330196380c29f2e Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Wed, 20 Nov 2024 11:51:56 +0100 Subject: [PATCH 35/65] EDBPlus 41.3.0: release notes, version bumps, supported dbs --- .../02_release_notes/edbplus_41.3_rel_notes.mdx | 17 +++++++++++++++++ .../docs/edb_plus/41/02_release_notes/index.mdx | 6 ++++-- .../edb_plus/41/02a_supported_platforms.mdx | 4 ++-- .../docs/edb_plus/41/04_using_edb_plus.mdx | 14 +++++++------- .../edb_plus/41/05_using_edb_plus_with_ssl.mdx | 8 ++++---- .../docs/edb_plus/41/06_command_summary.mdx | 6 +++--- 6 files changed, 37 insertions(+), 18 deletions(-) create mode 100644 product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx new file mode 100644 index 00000000000..8e1d74fa9b0 --- /dev/null +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx @@ -0,0 +1,17 @@ +--- +title: "EDB*Plus 41.3.0 release notes" +navTitle: Version 41.3.0 +--- + +Released: 22 Nov 2024 + +New features, enhancements, bug fixes, and other changes in EDB\*Plus 41.3.0 include: + +| Type | Description | Addresses | +|--------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------| +| Enhancement | EDB\*Plus has been certified for use with EDB Postgres Advanced Server version 17. | | +| Enhancement | Enhanced the behavior where the `SET LINESIZE` command doesn't behave as expected when set to a value greater than 10. This enhancement mainly applies to the constants used in the select statement. | #103591
#35673 | +| Bug fix | Corrected the behavior where `SPOOL` was introducing redundant blank lines after each output. | #37846 | +| Bug fix | Fixed the issue where EDB\*Plus is unable to process the command when `--` is used in between `/* */`. | #100496 | +| Bug fix | Fixed the issue causing the execution of a trivial procedural script to perform quite slowly in EDB\*Plus. | #37747 | +| Bug fix | Fixed an issue related to the configuration of EDB\*Plus with SSL certificate authentication method when the password is not specified. | #37970 | diff --git a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx index 5269d7c8505..9a5771cac72 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx @@ -2,6 +2,7 @@ title: "Release notes" navigation: +- edbplus_41.3_rel_notes - edbplus_41.2_rel_notes - edbplus_41.1_rel_notes - edbplus_41.0_rel_notes @@ -11,8 +12,9 @@ EDB\*Plus is a utility program that provides a command line interface to EDB Pos The EDB\*Plus documentation describes the latest version of EDB\*Plus Version 41. The release notes provide information on what was new in each release. -| Version | Release Date | -| ------------------------------------- | ------------ | +| Version | Release Date | +|--------------------------------------|--------------| +| [41.3.0](edbplus_41.3_rel_notes.mdx) | 22 Nov 2024 | | [41.2.0](edbplus_41.2_rel_notes.mdx) | 23 Aug 2023 | | [41.1.0](edbplus_41.1_rel_notes.mdx) | 20 Apr 2023 | | [41.0.0](edbplus_41.0_rel_notes.mdx) | 14 Feb 2023 | diff --git a/product_docs/docs/edb_plus/41/02a_supported_platforms.mdx b/product_docs/docs/edb_plus/41/02a_supported_platforms.mdx index 40a4469527a..fe018b791a1 100644 --- a/product_docs/docs/edb_plus/41/02a_supported_platforms.mdx +++ b/product_docs/docs/edb_plus/41/02a_supported_platforms.mdx @@ -7,8 +7,8 @@ EDB\*Plus is supported on the same platforms as EDB Postgres Advanced Server. To ## Supported database versions The following list of EDB Postgres Advanced Server (EPAS) versions are currently supported for use with EDB\*Plus: +- EPAS 17 +- EPAS 16 - EPAS 15 - EPAS 14 - EPAS 13 -- EPAS 12 -- EPAS 11 diff --git a/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx b/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx index 561c258e9f3..a69ead27205 100644 --- a/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx +++ b/product_docs/docs/edb_plus/41/04_using_edb_plus.mdx @@ -78,9 +78,9 @@ The following example shows user `enterprisedb` with password `password` connect ```text C:\Program Files\edb\edbplus>edbplus enterprisedb/password -Connected to EnterpriseDB 14.1.0 (localhost:5444/edb) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (localhost:5444/edb) AS enterprisedb -EDB*Plus: Release 14 (Build 40.0.0) +EDB*Plus: (Build 41.3.0) Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved. SQL> @@ -90,9 +90,9 @@ The following example shows user `enterprisedb` with password `password` connect ```text C:\Program Files\edb\edbplus>edbplus enterprisedb/password@localhost:5445/edb -Connected to EnterpriseDB 14.1.0 (localhost:5445/edb) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (localhost:5445/edb) AS enterprisedb -EDB*Plus: Release 14 (Build 40.0.0) +EDB*Plus: (Build 41.3.0) Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved. SQL> @@ -102,9 +102,9 @@ Using variable `hr_5445` in the `login.sql` file, the following shows how it is ```text C:\Program Files\edb\edbplus>edbplus enterprisedb/password@hr_5445 -Connected to EnterpriseDB 14.0.0 (localhost:5445/hr) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (localhost:5445/hr) AS enterprisedb -EDB*Plus: Release 14 (Build 40.1.0) +EDB*Plus: (Build 41.3.0) Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved. SQL> @@ -127,7 +127,7 @@ The following example executes a script file, `dept_query.sql`, after connecting ```sql C:\Program Files\edb\edbplus>edbplus enterprisedb/password @dept_query -Connected to EnterpriseDB 14.1.0 (localhost:5444/edb) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (localhost:5444/edb) AS enterprisedb SQL> SELECT * FROM dept; diff --git a/product_docs/docs/edb_plus/41/05_using_edb_plus_with_ssl.mdx b/product_docs/docs/edb_plus/41/05_using_edb_plus_with_ssl.mdx index 337d345fef2..714c1de1d9c 100644 --- a/product_docs/docs/edb_plus/41/05_using_edb_plus_with_ssl.mdx +++ b/product_docs/docs/edb_plus/41/05_using_edb_plus_with_ssl.mdx @@ -284,9 +284,9 @@ $ export PGSSLCERTPASS=keypass $ export PGSSLKEYPASS=exppass $ cd /usr/edb/edbplus $ ./edbplus.sh enterprisedb/password@192.168.2.22:5444/edb?ssl=true -Connected to EnterpriseDB 14.0.0 (192.168.2.22:5444/edb) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (192.168.2.22:5444/edb) AS enterprisedb -EDB*Plus: Release 14 (Build 40.0.1) +EDB*Plus: (Build 41.3.0) Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved. SQL> @@ -301,9 +301,9 @@ $ export PGSSLCERTPASS=keypass $ export PGSSLKEYPASS=exppass $ cd /usr/edb/edbplus $ ./edbplus.sh enterprisedb/password@192.168.2.22:5444/edb?ssl=true -Connected to EnterpriseDB 14.0.0 (192.168.2.22:5444/edb) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (192.168.2.22:5444/edb) AS enterprisedb -EDB*Plus: Release 14 (Build 40.0.1) +EDB*Plus: (Build 41.3.0) Copyright (c) 2008-2021, EnterpriseDB Corporation. All rights reserved. SQL> diff --git a/product_docs/docs/edb_plus/41/06_command_summary.mdx b/product_docs/docs/edb_plus/41/06_command_summary.mdx index 10348cfde1c..e09121a27f8 100644 --- a/product_docs/docs/edb_plus/41/06_command_summary.mdx +++ b/product_docs/docs/edb_plus/41/06_command_summary.mdx @@ -320,7 +320,7 @@ In this example, the database connection is changed to database `edb` on the loc ```sql SQL> CONNECT smith/mypassword@localhost:5445/edb Disconnected from EnterpriseDB Database. -Connected to EnterpriseDB 14.0.0 (localhost:5445/edb) AS smith +Connected to EnterpriseDB 16.4.1 (localhost:5445/edb) AS smith ``` In this session, the connection is changed to the username `enterprisedb`. The host defaults to the localhost, the port defaults to `5444` (which isn't the same as the port previously used), and the database defaults to `edb`. @@ -328,7 +328,7 @@ In this session, the connection is changed to the username `enterprisedb`. The h ```sql SQL> CONNECT enterprisedb/password Disconnected from EnterpriseDB Database. -Connected to EnterpriseDB 14.0.0 (localhost:5444/edb) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (localhost:5444/edb) AS enterprisedb ``` This example shows connectivity for a multi-node cluster (one primary node and two secondary nodes) setup. The given multi-host `connectstring` syntax is used to establish a connection with the active primary database server. In this case, using `CONNECT` command, the connection is established with the primary database node on host `192.168.22.24` at port `5444`. @@ -336,7 +336,7 @@ This example shows connectivity for a multi-node cluster (one primary node and t ```sql SQL> CONNECT enterprisedb/edb@192.168.22.24:5444,192.168.22.25:5445,192.168.22.26:5446/edb?targetServerType=primary Disconnected from EnterpriseDB Database. -Connected to EnterpriseDB 15.3.0 (192.168.22.24:5444/edb) AS enterprisedb +Connected to EnterpriseDB 16.4.1 (192.168.22.24:5444/edb) AS enterprisedb ``` ## DEFINE From 623ca0b16ae7dab2bd26c26ee10aef2be7ad3ff9 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Wed, 27 Nov 2024 10:38:30 +0100 Subject: [PATCH 36/65] Corrected release date --- .../edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx | 2 +- product_docs/docs/edb_plus/41/02_release_notes/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx index 8e1d74fa9b0..39e42dccc34 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/edbplus_41.3_rel_notes.mdx @@ -3,7 +3,7 @@ title: "EDB*Plus 41.3.0 release notes" navTitle: Version 41.3.0 --- -Released: 22 Nov 2024 +Released: 27 Nov 2024 New features, enhancements, bug fixes, and other changes in EDB\*Plus 41.3.0 include: diff --git a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx index 9a5771cac72..9c0d7714452 100644 --- a/product_docs/docs/edb_plus/41/02_release_notes/index.mdx +++ b/product_docs/docs/edb_plus/41/02_release_notes/index.mdx @@ -14,7 +14,7 @@ The EDB\*Plus documentation describes the latest version of EDB\*Plus Version 41 | Version | Release Date | |--------------------------------------|--------------| -| [41.3.0](edbplus_41.3_rel_notes.mdx) | 22 Nov 2024 | +| [41.3.0](edbplus_41.3_rel_notes.mdx) | 27 Nov 2024 | | [41.2.0](edbplus_41.2_rel_notes.mdx) | 23 Aug 2023 | | [41.1.0](edbplus_41.1_rel_notes.mdx) | 20 Apr 2023 | | [41.0.0](edbplus_41.0_rel_notes.mdx) | 14 Feb 2023 | From 9fe95df3a0cefc8b0ad26ff4c5145cf19a0cc83f Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Wed, 27 Nov 2024 15:14:02 +0530 Subject: [PATCH 37/65] EPAS and PGE 17 - Remove Ubuntu 20 install topics --- install_template/config.yaml | 2 +- .../docs/epas/17/installing/index.mdx | 2 +- .../linux_x86_64/epas_ubuntu_20.mdx | 129 ------------------ .../epas/17/installing/linux_x86_64/index.mdx | 3 - 4 files changed, 2 insertions(+), 134 deletions(-) delete mode 100644 product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_20.mdx diff --git a/install_template/config.yaml b/install_template/config.yaml index 0485e53a8a4..46e22cc53d8 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -373,7 +373,7 @@ products: supported versions: [11, 12, 13, 14, 15, 16, 17] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [11, 12, 13, 14, 15, 16, 17] + supported versions: [11, 12, 13, 14, 15, 16] - name: SLES 15 arch: x86_64 supported versions: [11, 12, 13, 14, 15, 16, 17] diff --git a/product_docs/docs/epas/17/installing/index.mdx b/product_docs/docs/epas/17/installing/index.mdx index f98853d0098..2c7f3d5f4a4 100644 --- a/product_docs/docs/epas/17/installing/index.mdx +++ b/product_docs/docs/epas/17/installing/index.mdx @@ -41,7 +41,7 @@ Select a link to access the applicable installation instructions: ### Debian and derivatives -- [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20) +- [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22) - [Debian 12](linux_x86_64/epas_debian_12), [Debian 11](linux_x86_64/epas_debian_11) diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_20.mdx deleted file mode 100644 index 2b721211e32..00000000000 --- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_20.mdx +++ /dev/null @@ -1,129 +0,0 @@ ---- -navTitle: Ubuntu 20.04 -title: Installing EDB Postgres Advanced Server on Ubuntu 20.04 x86_64 -# This topic is generated from templates. If you have feedback on it, instead of -# editing the page and creating a pull request, please enter a GitHub issue and -# the documentation team will update the templates accordingly. - -redirects: - - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86 - - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu20_x86 ---- - -## Prerequisites - -Before you begin the installation process: - -- Set up the EDB repository. - - Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. - - To determine if your repository exists, enter this command: - - `apt-cache search enterprisedb` - - If no output is generated, the repository isn't installed. - - To set up the EDB repository: - - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). - - 1. Select the button that provides access to the EDB repository. - - 1. Select the platform and software that you want to download. - - 1. Follow the instructions for setting up the EDB repository. - -## Install the package - -```shell -sudo apt-get -y install edb-as-server -``` - -Where `` is the version of the EDB Postgres Advanced Server you're installing. For example, if you're installing version 17, the package name is `edb-as17-server`. - -To install an individual component: - -```shell -sudo apt-get -y install -``` - -Where `package_name` can be any of the available packages from the [available package list](/epas/17/installing/linux_install_details/rpm_packages/). - -## Initial configuration - -This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. - -To work in your cluster, log in as the enterprisedb user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. - -```shell -sudo su - enterprisedb - -psql edb -``` - -The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. - -Before changing the authentication method, assign a password to the database superuser, enterprisedb. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../database_administration/01_configuration_parameters/01_setting_new_parameters/#modifying-the-pg_hbaconf-file). - -```sql -ALTER ROLE enterprisedb IDENTIFIED BY password; -``` - -## Experiment - -Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. - -First, use psql to create a database named `hr` to hold human resource information. - -```sql -# running in psql -CREATE DATABASE hr; -__OUTPUT__ -CREATE DATABASE -``` - -Connect to the `hr` database inside psql: - -``` -\c hr -__OUTPUT__ -psql (17.0.0, server 17.0.0) -You are now connected to database "hr" as user "enterprisedb". -``` - -Create columns to hold department numbers, unique department names, and locations: - -``` -CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk -PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc -varchar(13)); -__OUTPUT__ -CREATE TABLE -``` - -Insert values into the `dept` table: - -``` -INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); -__OUTPUT__ -INSERT 0 1 -``` - -``` -INSERT into dept VALUES (20,'RESEARCH','DALLAS'); -__OUTPUT__ -INSERT 0 1 -``` - -View the table data by selecting the values from the table: - -``` -SELECT * FROM dept; -__OUTPUT__ -deptno | dname | loc ---------+------------+---------- -10 | ACCOUNTING | NEW YORK -20 | RESEARCH | DALLAS -(2 rows) -``` diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/index.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/index.mdx index f0b99b5fe2b..d56b8114664 100644 --- a/product_docs/docs/epas/17/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/epas/17/installing/linux_x86_64/index.mdx @@ -18,7 +18,6 @@ navigation: - epas_other_linux_8 - epas_sles_15 - epas_ubuntu_22 - - epas_ubuntu_20 - epas_debian_12 - epas_debian_11 --- @@ -51,8 +50,6 @@ Operating system-specific install instructions are described in the correspondin - [Ubuntu 22.04](epas_ubuntu_22) -- [Ubuntu 20.04](epas_ubuntu_20) - - [Debian 12](epas_debian_12) - [Debian 11](epas_debian_11) From 78da6d335e05f9679bd37f51109d6b28333384b9 Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Wed, 27 Nov 2024 09:47:06 +0000 Subject: [PATCH 38/65] Remove himesh references Signed-off-by: Dj Walker-Morgan --- .../docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx | 11 +++++------ .../docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml | 11 +++++------ 2 files changed, 10 insertions(+), 12 deletions(-) diff --git a/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx b/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx index 7d5b4b340b4..6f3d065a545 100644 --- a/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx +++ b/product_docs/docs/pgd/5.6/rel_notes/pgd_5.6.1_rel_notes.mdx @@ -35,7 +35,7 @@ If the nodename parameter is NULL, the function will wait for all n LSN. If the target LSN is NULL, it will wait for the current wal_flush_lsn.

BDR5.6.1
Improvements made in SO Node Management and Progress Tracking.

An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in -progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh +progress updates. Improvements include enhanced watermark management for SO leaders in the Optimized Topology configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected, and the tap test for group slot movement has been revised. @@ -72,13 +72,12 @@ that are prone to failure won't consistently impact the success of other tasks.< BDR5.6.1

Fixed parting subscription with standbys.

The parting subscription used to hang, failing to wait for standbys when the bdr.standby_slot_names parameter was defined.

41821 -BDR5.6.1
Fixed parting SO node with multiple origins.

All relevant origins must be removed when parting SO node -With himesh, parting an SO node should result in removing all origins it +BDR5.6.1

Fixed parting SO node with multiple origins.

All relevant origins must be removed when parting SO node. +With Optimized Topology, parting an SO node should result in removing all origins it has, not just the one related to its SO group leader. When parting a data node, even though there is no subscription to it -from SO node, the origin should be removed -DO not make SO node target of a part catchup subscription when himesh -enabled

+from SO node, the origin should be removed. +DO not make SO node target of a part catchup subscription when Optimized Topology is enabled.

BDR5.6.1
Stopped creation of slots for subscriber only nodes on witness nodes.

Subscriber only nodes should not have slots on witness nodes.

diff --git a/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml b/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml index ddfd29bf032..9091df27928 100644 --- a/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml +++ b/product_docs/docs/pgd/5.6/rel_notes/src/relnote_5.6.1.yml @@ -104,7 +104,7 @@ relnotes: component_version: 5.6.1 details: | An update addresses the movement of group slots in SO nodes, ensuring they don't appear as peers in - progress updates. Improvements include enhanced watermark management for SO leaders in the Himesh + progress updates. Improvements include enhanced watermark management for SO leaders in the Optimized Topology configuration, where write leaders now include watermarks in their updates. Watermarks are broadcasted to simplify progress tracking on idle clusters. The peer progress mapping for SO nodes has been corrected, and the tap test for group slot movement has been revised. @@ -130,13 +130,12 @@ relnotes: component: BDR component_version: 5.6.1 details: | - All relevant origins must be removed when parting SO node - With himesh, parting an SO node should result in removing all origins it + All relevant origins must be removed when parting SO node. + With Optimized Topology, parting an SO node should result in removing all origins it has, not just the one related to its SO group leader. When parting a data node, even though there is no subscription to it - from SO node, the origin should be removed - DO not make SO node target of a part catchup subscription when himesh - enabled + from SO node, the origin should be removed. + DO not make SO node target of a part catchup subscription when Optimized Topology is enabled. jira: BDR-5552 addresses: "" type: Bug-fix From dc5eff64016fd059c20f6c930ae2090eed9c9e0f Mon Sep 17 00:00:00 2001 From: Benjamin Anderson <79652654+ba-edb@users.noreply.github.com> Date: Wed, 27 Nov 2024 14:09:13 -0800 Subject: [PATCH 39/65] Fix typo in choosing_server.mdx --- product_docs/docs/pgd/5.6/planning/choosing_server.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/pgd/5.6/planning/choosing_server.mdx b/product_docs/docs/pgd/5.6/planning/choosing_server.mdx index 807d5248506..77fd46b098f 100644 --- a/product_docs/docs/pgd/5.6/planning/choosing_server.mdx +++ b/product_docs/docs/pgd/5.6/planning/choosing_server.mdx @@ -16,7 +16,7 @@ The following table lists features of EDB Postgres Distributed that are dependen | [Granular DDL Locking](/pgd/latest/ddl/ddl-locking/) | Y | Y | Y | | [Streaming of large transactions](/pgd/latest/transaction-streaming/) | v14+ | v13+ | v14+ | | [Distributed sequences](/pgd/latest/sequences/#pgd-global-sequences) | Y | Y | Y | -| [Subscribe-only nodes](/pgd/latest/nodes/subscriber_only/) | Y | Y | Y | +| [Subscriber-only nodes](/pgd/latest/nodes/subscriber_only/) | Y | Y | Y | | [Monitoring](/pgd/latest/monitoring/) | Y | Y | Y | | [OpenTelemetry support](/pgd/latest/monitoring/otel/) | Y | Y | Y | | [Parallel apply](/pgd/latest/parallelapply) | Y | Y | Y | From c58b1b5202df83e8ac377c6f3c0d5652585ed911 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 28 Nov 2024 13:08:41 +0530 Subject: [PATCH 40/65] CLI 3.10 - Release --- .../using_cluster/cli/managing_clusters.mdx | 364 ++++++++++++++---- .../using_cluster/cli/using_features.mdx | 2 + 2 files changed, 288 insertions(+), 78 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx index 0fd59e5bf03..9f9076f5ed0 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx @@ -87,16 +87,21 @@ Here's a sample configuration file in YAML format with Azure specified as the pr --- clusterArchitecture: ha # haStandbyReplicas: 2 # -provider: azure # -cspSubscriptionIDs: # +provider: azure # +cspSubscriptionIDs: # - 123123123 # - 456456456 # -serviceAccountIds: # +serviceAccountIds: # - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# clusterName: biganimal_cluster # password: ************ # -# refer following link for steps to setup IAM: https://www.enterprisedb.com/docs/biganimal/latest/using_cluster/01_postgres_access/iam-authentication-for-postgres +tags: # + - name: tag1 # + color: "#c5eae7" # + - name: tag2 # + color: "#0b6ff4" # +# refer following link for steps to setup IAM: https://www.enterprisedb.com/docs/biganimal/latest/using_cluster/01_postgres_access/iam-authentication-for-postgres iamAuthentication: true # postgresType: epas # postgresVersion: 14 # @@ -104,7 +109,7 @@ region: eastus # volumeType: azurepremiumstorage # volumeProperties: P1 # -volumePropertySize: 4Gi # +volumePropertySize: 32Gi # volumePropertyIOPS: 1000 # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> networking: public # allowIpRangeMap: # @@ -117,9 +122,21 @@ pgConfigMap: # array_nulls: true # backupRetentionPeriod: 30d # -superuserAccess: true # -pgvector: true # -postgis: true # +customMaintenanceWindow: # + isEnabled: true # + maintenanceStartDay: Monday # + maintenanceStartTime: 02:00 # +superuserAccess: true # +pgvector: true # +postgis: true # +pgBouncer: true # +pgBouncerRWSettings: # + application_name_add_host: true # + max_client_conn: 100 # +pgBouncerROSettings: # + idle_transaction_timeout: 20 # + log_stats: true # + --- ``` !!! Note @@ -207,6 +224,7 @@ After the cluster is created, you can update attributes of the cluster, includin - IAM authentication - Cloud service provider subscription IDs - Service account IDs +- Tags For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: @@ -284,6 +302,7 @@ biganimal cluster restore\ --backup-retention-period "2w" \ --postgis=true --pgvector=true + --tags "tag1, tag2=blue" --read-only-workloads: "true" --csp-subscription-ids "123123123,456456456" --service-account-ids "service-account-1234567b@development-data-123456.iam.gserviceaccount.com, @@ -411,55 +430,70 @@ Where `` is a valid path to a YAML configuration file. #### Azure example ``` -clusterName: biganimal-azure-pgd-cluster -password: Meredith Palmer Memorial -postgresType: epas -postgresVersion: "14" -provider: azure -dataNodes: 2 -dataGroups: - - iamAuthentication: false - region: westus2 - instanceType: azure:Standard_E2s_v3 - volumeType: azurepremiumstorage - volumeProperties: P2 - customMaintenanceWindow: - maintenanceStartTime: 18:00 - maintenanceStartDay: wednesday - networking: public - allowIpRangeMap: - - cidr: 9.9.9.9/28 - description: Allow traffic from App A - - cidr: 10.10.10.10/27 - description: Allow traffic from App B - pgConfigMap: - application_name: test - array_nulls: true - backupRetentionPeriod: 30d - - iamAuthentication: false - region: canadacentral - instanceType: azure:Standard_E2s_v3 - volumeType: azurepremiumstorage - volumeProperties: P2 - customMaintenanceWindow: - maintenanceStartTime: 18:00 - maintenanceStartDay: tuesday - networking: public - allowIpRangeMap: - - cidr: 9.9.9.9/28 - description: Allow traffic from App A - - cidr: 10.10.10.10/27 - description: Allow traffic from App B - pgConfigMap: - application_name: test1 - array_nulls: true - backupRetentionPeriod: 30d -witnessGroups: - - provider: azure - region: uksouth - customMaintenanceWindow: - maintenanceStartTime: 18:00 - maintenanceStartDay: monday +clusterName: biganimal_cluster # +password: ************ # +postgresType: epas # (only epas is supported in pgd preview) +postgresVersion: 14 # +provider: azure # +dataNodes: 3 # +tags: # + - name: tag1 # + color: blue # + - name: tag2 # + color: "#FF0000" # +dataGroups: # + region: westus2 # + instanceType: azure:Standard_E2s_v3 # + volumeType: azurepremiumstorage # + volumeProperties: P1 # + volumePropertySize: 32Gi # + volumePropertyIOPS: 1000 # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> + customMaintenanceWindow: # + maintenanceStartTime: 15:00 # + maintenanceStartDay: monday # + networking: public # + allowIpRangeMap: # + - cidr: 9.9.9.9/28 # + description: Allow traffic from App A # + - cidr: 10.10.10.10/27 # + description: Allow traffic from App B # + pgConfigMap: # + application_name: test_app # + array_nulls: true # + backupRetentionPeriod: 30d # + - iamAuthentication: false # + region: canadacentral # + instanceType: azure:Standard_E2s_v3 # + volumeType: azurepremiumstorage # + volumeProperties: P1 # + volumePropertySize: 32Gi # + volumePropertyIOPS: 1000 # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> + customMaintenanceWindow: # + maintenanceStartTime: 17:00 # + maintenanceStartDay: tuesday # + networking: public # + allowIpRangeMap: # + - cidr: 9.9.9.9/28 # + description: Allow traffic from App A # + - cidr: 10.10.10.10/27 # + description: Allow traffic from App B # + pgConfigMap: # + application_name: test_app # + array_nulls: true # + backupRetentionPeriod: 30d # +# cspSubscriptionIds: # +# - 123123123 # +# - 456456456 # +# serviceAccountIds: # +# - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# +# - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# +witnessGroups: # + region: uksouth # + customMaintenanceWindow: # + maintenanceStartTime: 18:00 # + maintenanceStartDay: monday # ``` #### AWS example @@ -471,6 +505,11 @@ postgresType: pgextended # provider: aws # dataNodes: 2 # +tags: # + - name: tag1 # + color: blue # + - name: tag2 # + color: "#FF0000" # dataGroups: # region: ap-south-1 # @@ -537,6 +576,11 @@ postgresType: epas # provider: gcp # dataNodes: 3 # +tags: # + - name: tag1 # + color: blue # + - name: tag2 # + color: "#FF0000" # dataGroups: # region: europe-west1 # @@ -646,7 +690,51 @@ The syntax of the command is: pgd update [--config-file] ``` -Where `` is a valid path to a YAML configuration file with the same format as a configuration file for creating a distributed high-availability cluster. See [Create a distributed high-availability cluster](#create-a-distributed-high-availability-cluster). +Where `` is a valid path to a YAML configuration file. For updating a distributed high-availability cluster, clusterId and groupId are mandatory fields. All other fields are optional removing/unspecified optional fields means no change is intended for them. See the sample config file below to update a distributed high-availability cluster. + +``` +clusterId: p-***** # +clusterName: biganimal_cluster # +password: ************ # +tags: # + - name: tag1 # + color: blue # + - name: tag2 # + color: "#FF0000" # +dataNodes: 3 # +dataGroups: # + iamAuthentication: false # + instanceType: azure:Standard_E2s_v3 # + volumeType: azurepremiumstorage # + volumeProperties: P1 # + volumePropertySize: 32Gi # + volumePropertyIOPS: 1000 # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> + customMaintenanceWindow: # + maintenanceStartTime: 15:00 # + maintenanceStartDay: monday # + networking: public # + allowIpRangeMap: # + - cidr: 9.9.9.9/28 # + description: Allow traffic from App A # + - cidr: 10.10.10.10/27 # + description: Allow traffic from App B # + pgConfigMap: # + application_name: test_app # + array_nulls: true # + backupRetentionPeriod: 30d # +# cspSubscriptionIds: # +# - 123123123 # +# - 456456456 # +# serviceAccountIds: # +# - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# +# - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# +witnessGroups: # + customMaintenanceWindow: # + maintenanceStartTime: 18:00 # + maintenanceStartDay: monday # +``` ### Show distributed high-availability clusters @@ -670,27 +758,41 @@ pgd restore [--config-file] Where `` is a valid path to a YAML configuration file. For example: +You can either restore an active or a deleted distributed high-availability cluster within its retention period. You can restore only 1 data group from the available data groups in the source cluster. By default the new cluster will inherit all settings of source cluster, you can change the cluster setting and database configurations by specifying new values in the restore command. + +To restore a distributed high-availability cluster, clusterId, sourceGroupId and password are mandatory fields. All other fields are optional. Removing the optional fields will use the corresponding source group field instead. + ``` -clusterName: pgd-restore-name -password: Meredith Palmer Memorial -dataNodes: 2 -clusterId: p-9fdkl5ju29 -dataGroups: - - iamAuthentication: false - region: uksouth - instanceType: azure:Standard_E2s_v3 - volumeType: azurepremiumstorage - volumeProperties: P2 - allowIpRangeMap: - - cidr: 9.9.9.9/28 - description: Allow traffic from App A - - cidr: 10.10.10.10/27 - description: Allow traffic from App B - pgConfigMap: - application_name: test - array_nulls: true - backupRetentionPeriod: 30d - sourceGroupId: p-9fdkl5ju29-a +clusterName: biganimal_cluster # +password: ************ # +dataNodes: 3 # +clusterId: p-***** # +tags: # + - name: tag1 # + color: blue # + - name: tag2 # + color: "#FF0000" # +dataGroups: # + iamAuthentication: false # + region: westus2 # + instanceType: azure:Standard_E2s_v3 # + volumeType: azurepremiumstorage # + volumeProperties: P1 # + volumePropertySize: 32Gi # + volumePropertyIOPS: 1000 # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> + customMaintenanceWindow: # + maintenanceStartTime: 15:00 # + maintenanceStartDay: monday # + allowIpRangeMap: # + - cidr: 9.9.9.9/28 # + description: Allow traffic from App A # + - cidr: 10.10.10.10/27 # + description: Allow traffic from App B # + pgConfigMap: # + application_name: test_app # + array_nulls: true # + backupRetentionPeriod: 30d # ``` ### Get distributed high-availability cluster connection information @@ -749,4 +851,110 @@ For example: ``` biganimal pgd resume --id p-c5fh47nf +``` + +## Creating and Managing tags + +Tagging is a powerful way to organize, manage, and track your resources and clusters, especially in large-scale environments. Here's how you can effectively manage tags for grouping your clusters and other resources: + +Here are the available commands for creating and managing tags: + +``` +biganimal tag -h +Manage tags for grouping your clusters and other resources. + +Usage: + biganimal tag [flags] + biganimal tag [command] + +Available Commands: + create Create a tag + update Update a tag with specified ID. + delete Delete a tag + show Show all available tags + +Flags: + -h, --help help for tag +``` + +Here are the options with tag create command: + +``` +biganimal tag create -h +Create a tag with specified name and color. + +Usage: + biganimal tag create [flags] + +Examples: +biganimal tag create --name my-cyan-tag --color "#30f8ef" +tag create --name my-red-tag --color red + +Flags: + -n, --name string Tag Name + -r, --color string Tag color hex code or name (e.g. #FF0000 or red) + -y, --yes auto-confirm all confirmations + -c, --credential string The credential which you created via 'credential create' command, the default is fetched from 'context_credential' + -P, --project string The project that groups your clusters and other resources, the default is taken from 'context_project' (default "DummyProject") + -I, --interactive[=NoOpt] Execute command interactively + -h, --help help for create +``` + +Here are the options with the tag update command: + +``` +biganimal tag update -h +Update a tag color, name for specified tag ID. + +Usage: + biganimal tag update [flags] + +Examples: +biganimal tag update --id "" --name "" --color "" + +Flags: + -i, --id string Tag ID + -n, --name string Updated Tag Name + -r, --color string Updated Tag color hex code or name (e.g. #FF0000 or red) + -y, --yes auto-confirm all confirmations + -c, --credential string The credential which you created via 'credential create' command, the default is fetched from 'context_credential' + -P, --project string The project that groups your clusters and other resources, the default is taken from 'context_project' (default "DummyProject") + -I, --interactive[=NoOpt] Execute command interactively + -h, --help help for update +``` + +Here are the options with the tag show command: + +``` +Usage: + biganimal tag show [flags] + +Examples: +biganimal tags show + +Flags: + -c, --credential string The credential which you created via 'credential create' command, the default is fetched from 'context_credential' + -h, --help help for show + -i, --id string Tag ID + -o, --output string [table json yaml xml] (default "table") +``` + +Here are the options with the tag delete command: + +``` +Delete a tag with specified ID. + +Usage: + biganimal tag delete [flags] + +Examples: +biganimal tag delete --id "TagID_123" + +Flags: + -i, --id string Tag ID + -y, --yes auto-confirm all confirmations + -c, --credential string The credential which you created via 'credential create' command, the default is fetched from 'context_credential' + -P, --project string The project that groups your clusters and other resources, the default is taken from 'context_project' (default "DummyProject") + -I, --interactive[=NoOpt] Execute command interactively + -h, --help help for delete ``` \ No newline at end of file diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx index 63534e42efe..311554a680c 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx @@ -3,6 +3,8 @@ title: Using Cloud Service features with the CLI navTitle: Using Cloud Service features redirects: - /biganimal/latest/reference/cli/using_features/ #generated for BigAnimal URL path removal branch +indexDepth: 3 +deepToc: true --- ## Faraway replicas CLI commands From 66e6f37ba17a6ceb583e28a3f7bd39018636876b Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Thu, 28 Nov 2024 13:24:18 +0530 Subject: [PATCH 41/65] minor edit --- .../cloud-service/using_cluster/cli/using_features.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx index 311554a680c..0189dc40807 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/using_features.mdx @@ -3,8 +3,8 @@ title: Using Cloud Service features with the CLI navTitle: Using Cloud Service features redirects: - /biganimal/latest/reference/cli/using_features/ #generated for BigAnimal URL path removal branch -indexDepth: 3 -deepToc: true +indexdepth: 3 +deepToC: true --- ## Faraway replicas CLI commands From 76c22b7b01f63c0fddfdfd52c1d648b2b37515b6 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Thu, 28 Nov 2024 11:32:19 +0100 Subject: [PATCH 42/65] Corrected outdated link, BigAnimal mentions, and Monday with capital M --- .../using_cluster/cli/managing_clusters.mdx | 82 +++++++++---------- 1 file changed, 41 insertions(+), 41 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx index 9f9076f5ed0..dda5253484c 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/using_cluster/cli/managing_clusters.mdx @@ -33,7 +33,7 @@ Enable read-only workloads: No Provider: Azure Cloud Provider Subscription ID: "111,222" Service Account IDs, (leave empty to stop adding): "id1@iam.gcp" -Cluster Name: my-biganimal-cluster +Cluster Name: my-cloud-service-cluster Password: **************** PostgreSQL type: EDB Postgres Advanced Server PostgreSQL version: 14 @@ -71,7 +71,7 @@ __OUTPUT__ ├──────────────┬──────────────────────┬──────────┬──────────────┬──────────────────────────┬─────────────┬───────────────┬───────────────────────────────┬────────────────────┬────────────┤ │ ID │ Name │ Provider │ Architecture │ Status │ Region │ Instance Type │ Postgres Details │ Maintenance Window │ FAReplicas │ ├──────────────┼──────────────────────┼──────────┼──────────────┼──────────────────────────┼─────────────┼───────────────┼───────────────────────────────┼────────────────────┼────────────┤ -│ p-gxhkfww1fe │ my-biganimal-cluster │ Azure │ ha │ Cluster in healthy state │ East US │ E2s v3 │ EDB Postgres Advanced Server │ Disabled │ N/A │ +│ p-gxhkfww1fe │ my-cloud-service-cluster │ Azure │ ha │ Cluster in healthy state │ East US │ E2s v3 │ EDB Postgres Advanced Server │ Disabled │ N/A │ │ │ │ │ │ │ │ │ │ │ │ └──────────────┴──────────────────────┴──────────┴──────────────┴──────────────────────────┴─────────────┴───────────────┴───────────────────────────────┴────────────────────┴────────────┘ ``` @@ -87,21 +87,21 @@ Here's a sample configuration file in YAML format with Azure specified as the pr --- clusterArchitecture: ha # haStandbyReplicas: 2 # -provider: azure # -cspSubscriptionIDs: # +provider: azure # +cspSubscriptionIDs: # - 123123123 # - 456456456 # -serviceAccountIds: # +serviceAccountIds: # - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# -clusterName: biganimal_cluster # +clusterName: cloud_service_cluster # password: ************ # tags: # - name: tag1 # color: "#c5eae7" # - name: tag2 # color: "#0b6ff4" # -# refer following link for steps to setup IAM: https://www.enterprisedb.com/docs/biganimal/latest/using_cluster/01_postgres_access/iam-authentication-for-postgres +# refer following link for steps to setup IAM: https://www.enterprisedb.com/docs/edb-postgres-ai/cloud-service/using_cluster/postgres_access/database_authentication/#iam-authentication-for-postgres iamAuthentication: true # postgresType: epas # postgresVersion: 14 # @@ -124,9 +124,9 @@ pgConfigMap: # customMaintenanceWindow: # isEnabled: true # - maintenanceStartDay: Monday # + maintenanceStartDay: Monday # maintenanceStartTime: 02:00 # -superuserAccess: true # +superuserAccess: true # pgvector: true # postgis: true # pgBouncer: true # @@ -179,7 +179,7 @@ To use your Cloud Service cluster, you first need to get your cluster's connecti ```shell biganimal cluster show-connection \ - --name "my-biganimal-cluster" \ + --name "my-cloud-service-cluster" \ --provider "azure" \ --region "eastus" __OUTPUT__ @@ -198,7 +198,7 @@ You can query the complete connection information with other output formats, lik ```shell biganimal cluster show-connection \ - --name "my-biganimal-cluster" \ + --name "my-cloud-service-cluster" \ --provider "azure" \ --region "eastus" \ --output "json" @@ -229,7 +229,7 @@ After the cluster is created, you can update attributes of the cluster, includin For example, to set the public allowed IP range list, use the `--cidr-blocks` flag: ```shell -./biganimal cluster update --name "my-biganimal-cluster" --provider "azure" \ +./biganimal cluster update --name "my-cloud-service-cluster" --provider "azure" \ --region "eastus" \ --cidr-blocks "9.9.9.9/28=Traffic from App A" ``` @@ -237,7 +237,7 @@ For example, to set the public allowed IP range list, use the `--cidr-blocks` fl To check whether the setting took effect, use the `cluster show` command, and view the detailed cluster information output in JSON format. For example: ```shell -biganimal cluster show --name "my-biganimal-cluster" --provider "azure" \ +biganimal cluster show --name "my-cloud-service-cluster" --provider "azure" \ --region "eastus" \ --output "json" \ | jq '.[0].allowIpRangeMap' @@ -273,7 +273,7 @@ To delete a cluster you no longer need, use the `cluster delete` command. For ex ```shell biganimal cluster delete \ - --name "my-biganimal-cluster" \ + --name "my-cloud-service-cluster" \ --provider "azure" \ --region "eastus" ``` @@ -286,11 +286,11 @@ Cloud Service continuously backs up your PostgreSQL clusters. Using the CLI, you ```shell biganimal cluster restore\ - --name "my-biganimal-cluster" \ + --name "my-cloud-service-cluster" \ --provider "azure" \ --region "eastus" \ --password "mypassword@123" \ - --new-name "my-biganimal-cluster-restored" \ + --new-name "my-cloud-service-cluster-restored" \ --new-region="eastus2" \ --cluster-architecture "single" \ --instance-type "azure:Standard_E2s_v3" \ @@ -430,11 +430,11 @@ Where `` is a valid path to a YAML configuration file. #### Azure example ``` -clusterName: biganimal_cluster # +clusterName: cloud_service_cluster # password: ************ # postgresType: epas # (only epas is supported in pgd preview) postgresVersion: 14 # -provider: azure # +provider: azure # dataNodes: 3 # tags: # - name: tag1 # @@ -451,7 +451,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 15:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -471,7 +471,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 17:00 # - maintenanceStartDay: tuesday # + maintenanceStartDay: tuesday # networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -482,24 +482,24 @@ dataGroups: # array_nulls: true # backupRetentionPeriod: 30d # -# cspSubscriptionIds: # +# cspSubscriptionIds: # # - 123123123 # # - 456456456 # -# serviceAccountIds: # +# serviceAccountIds: # # - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# # - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# witnessGroups: # + - provider: azure # region: uksouth # customMaintenanceWindow: # maintenanceStartTime: 18:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # ``` #### AWS example ``` -clusterName: biganimal-aws-pgd-cluster # +clusterName: cloud-service-aws-pgd-cluster # password: Meredith Palmer Memorial # postgresType: pgextended # (only epas is supported in pgd preview) postgresVersion: 16 # @@ -520,7 +520,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 15:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -541,7 +541,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 17:00 # - maintenanceStartDay: tuesday # + maintenanceStartDay: tuesday # networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -564,13 +564,13 @@ witnessGroups: # customMaintenanceWindow: # maintenanceStartTime: 18:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # ``` #### Google Cloud example ``` -clusterName: biganimal-gcp-pgd-cluster # +clusterName: cloud-service-gcp-pgd-cluster # password: Meredith Palmer Memorial # postgresType: epas # (only epas is supported in pgd preview) postgresVersion: 16 # @@ -591,7 +591,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 15:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -612,7 +612,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 18:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -631,11 +631,11 @@ dataGroups: # witnessGroups: # + - provider: azure # region: australiaeast # customMaintenanceWindow: # maintenanceStartTime: 21:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # ``` ### Add a data group @@ -661,7 +661,7 @@ dataGroups: volumeProperties: P2 customMaintenanceWindow: maintenanceStartTime: 18:00 - maintenanceStartDay: monday + maintenanceStartDay: Monday networking: public allowIpRangeMap: - cidr: 9.9.9.9/28 @@ -694,7 +694,7 @@ Where `` is a valid path to a YAML configuration file. For updating ``` clusterId: p-***** # -clusterName: biganimal_cluster # +clusterName: cloud_service_cluster # password: ************ # tags: # - name: tag1 # @@ -712,7 +712,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 15:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # networking: public # allowIpRangeMap: # - cidr: 9.9.9.9/28 # @@ -723,17 +723,17 @@ dataGroups: # array_nulls: true # backupRetentionPeriod: 30d # -# cspSubscriptionIds: # +# cspSubscriptionIds: # # - 123123123 # # - 456456456 # -# serviceAccountIds: # +# serviceAccountIds: # # - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# # - service-account-1234567b@development-data-123456.iam.gserviceaccount.com# witnessGroups: # customMaintenanceWindow: # maintenanceStartTime: 18:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # ``` ### Show distributed high-availability clusters @@ -763,7 +763,7 @@ You can either restore an active or a deleted distributed high-availability clus To restore a distributed high-availability cluster, clusterId, sourceGroupId and password are mandatory fields. All other fields are optional. Removing the optional fields will use the corresponding source group field instead. ``` -clusterName: biganimal_cluster # +clusterName: cloud_service_cluster # password: ************ # dataNodes: 3 # clusterId: p-***** # @@ -783,7 +783,7 @@ dataGroups: # : Not Applicable to Azure Premium Storage and GCP:[pd-ssd], volume Input/Output Operations Per Second> customMaintenanceWindow: # maintenanceStartTime: 15:00 # - maintenanceStartDay: monday # + maintenanceStartDay: Monday # allowIpRangeMap: # - cidr: 9.9.9.9/28 # description: Allow traffic from App A # From 9aedb3d8c7e4b7983121c84f0d0ce71114e6f411 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Fri, 29 Nov 2024 10:57:55 +0530 Subject: [PATCH 43/65] Removed install topics of Ubuntu 20 from PGE and PG v17 --- .../postgresql/installing/index.mdx | 2 +- .../linux_arm64/postgresql_debian_12.mdx | 2 +- .../linux_arm64/postgresql_rhel_9.mdx | 2 +- .../linux_ppc64le/postgresql_rhel_8.mdx | 2 +- .../linux_ppc64le/postgresql_rhel_9.mdx | 2 +- .../linux_ppc64le/postgresql_sles_15.mdx | 2 +- .../installing/linux_x86_64/index.mdx | 3 - .../linux_x86_64/postgresql_debian_11.mdx | 2 +- .../linux_x86_64/postgresql_debian_12.mdx | 2 +- .../linux_x86_64/postgresql_other_linux_8.mdx | 2 +- .../linux_x86_64/postgresql_other_linux_9.mdx | 2 +- .../linux_x86_64/postgresql_rhel_8.mdx | 2 +- .../linux_x86_64/postgresql_rhel_9.mdx | 2 +- .../linux_x86_64/postgresql_sles_15.mdx | 2 +- .../linux_x86_64/postgresql_ubuntu_20.mdx | 40 ------ .../linux_x86_64/postgresql_ubuntu_22.mdx | 2 +- install_template/config.yaml | 28 ++-- product_docs/docs/pge/17/installing/index.mdx | 2 +- .../pge/17/installing/linux_x86_64/index.mdx | 3 - .../installing/linux_x86_64/pge_ubuntu_20.mdx | 124 ------------------ 20 files changed, 29 insertions(+), 199 deletions(-) delete mode 100644 advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx delete mode 100644 product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx diff --git a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx index fe3359d13bb..37d9eacbb08 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/index.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/index.mdx @@ -41,7 +41,7 @@ Select a link to access the applicable installation instructions: ### Debian and derivatives -- [Ubuntu 22.04](linux_x86_64/postgresql_ubuntu_22), [Ubuntu 20.04](linux_x86_64/postgresql_ubuntu_20) +- [Ubuntu 22.04](linux_x86_64/postgresql_ubuntu_22) - [Debian 12](linux_x86_64/postgresql_debian_12), [Debian 11](linux_x86_64/postgresql_debian_11) diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_debian_12.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_debian_12.mdx index 26187dbef09..dfb3a38b00c 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_debian_12.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_debian_12.mdx @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql-17`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx index 99d7acb4f60..55b89740a2a 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_arm64/postgresql_rhel_9.mdx @@ -52,4 +52,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server postgresql17-contrib`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx index 4103e5c54da..bbc29c34980 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_8.mdx @@ -54,4 +54,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server postgresql17-contrib`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx index 842d74bb296..c33af01fcd8 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_rhel_9.mdx @@ -54,4 +54,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server postgresql17-contrib`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx index a31953cafa4..aef206de738 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_ppc64le/postgresql_sles_15.mdx @@ -47,4 +47,4 @@ Before you begin the installation process: sudo zypper -n install postgresql-server ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx index ed79f869eb4..00942f6a71f 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/index.mdx @@ -10,7 +10,6 @@ navigation: - postgresql_other_linux_8 - postgresql_sles_15 - postgresql_ubuntu_22 - - postgresql_ubuntu_20 - postgresql_debian_12 - postgresql_debian_11 --- @@ -43,8 +42,6 @@ Operating system-specific install instructions are described in the correspondin - [Ubuntu 22.04](postgresql_ubuntu_22) -- [Ubuntu 20.04](postgresql_ubuntu_20) - - [Debian 12](postgresql_debian_12) - [Debian 11](postgresql_debian_11) diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx index a5b22f8e183..0a1eec48c7d 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_11.mdx @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql-17`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_12.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_12.mdx index 11ee583726e..0a8b97b683b 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_12.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_debian_12.mdx @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql-17`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx index 7c05941a38e..3b7e24ed004 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_8.mdx @@ -54,4 +54,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server postgresql17-contrib`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx index 92d4c6f4c52..ccdd36e0733 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_other_linux_9.mdx @@ -54,4 +54,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server postgresql17-contrib`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx index fe2c8b6c87b..0e8b62b9fc9 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_8.mdx @@ -52,4 +52,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server postgresql17-contrib`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx index 85f8c1cf8d8..9a76d8ed03d 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_rhel_9.mdx @@ -52,4 +52,4 @@ Before you begin the installation process: sudo dnf -y install postgresql-server postgresql-contrib ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server postgresql16-contrib`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server postgresql17-contrib`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx index 76fe2c2192d..413cf1cad96 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_sles_15.mdx @@ -47,4 +47,4 @@ Before you begin the installation process: sudo zypper -n install postgresql-server ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql16-server`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql17-server`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx deleted file mode 100644 index e742ba3fbcd..00000000000 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_20.mdx +++ /dev/null @@ -1,40 +0,0 @@ ---- -navTitle: Ubuntu 20.04 -title: Installing PostgreSQL on Ubuntu 20.04 x86_64 ---- - -## Prerequisites - -Before you begin the installation process: - -- Set up the EDB repository. - - !!! Note - Rather than use the EDB repository, you can obtain PostgreSQL installers and installation packages from the [PostgreSQL community downloads page](https://www.postgresql.org/download/). - !!! - - Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. - - To determine if your repository exists, enter this command: - - `apt-cache search enterprisedb` - - If no output is generated, the repository isn't installed. - - To set up the EDB repository: - - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). - - 1. Select the button that provides access to the EDB repository. - - 1. Select the platform and software that you want to download. - - 1. Follow the instructions for setting up the EDB repository. - -## Install the package - -```shell -sudo apt-get -y install postgresql- -``` - -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. diff --git a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx index 25129c010d1..d2fd1bc0bac 100644 --- a/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx +++ b/advocacy_docs/supported-open-source/postgresql/installing/linux_x86_64/postgresql_ubuntu_22.mdx @@ -37,4 +37,4 @@ Before you begin the installation process: sudo apt-get -y install postgresql- ``` -Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 16, the package name would be `postgresql-16`. +Where `` is the version of PostgreSQL you are installing. For example, if you are installing version 17, the package name would be `postgresql-17`. diff --git a/install_template/config.yaml b/install_template/config.yaml index 46e22cc53d8..229a781deec 100644 --- a/install_template/config.yaml +++ b/install_template/config.yaml @@ -411,7 +411,7 @@ products: supported versions: [15, 16, 17] - name: Ubuntu 20.04 arch: x86_64 - supported versions: [15, 16, 17] + supported versions: [15, 16] - name: EDB*Plus platforms: - name: AlmaLinux 8 or Rocky Linux 8 @@ -768,46 +768,46 @@ products: platforms: - name: RHEL 8 arch: ppc64le - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: RHEL 9 arch: ppc64le - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: AlmaLinux 8 or Rocky Linux 8 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: AlmaLinux 9 or Rocky Linux 9 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: RHEL 8 or OL 8 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: RHEL 9 or OL 9 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: RHEL 9 or OL 9 arch: arm64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Debian 12 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Debian 12 arch: arm64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Debian 11 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Ubuntu 20.04 arch: x86_64 supported versions: [15, 16] - name: Ubuntu 22.04 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: SLES 15 arch: x86_64 - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: SLES 15 arch: ppc64le - supported versions: [15, 16] + supported versions: [15, 16, 17] - name: Replication Server platforms: - name: AlmaLinux 8 or Rocky Linux 8 diff --git a/product_docs/docs/pge/17/installing/index.mdx b/product_docs/docs/pge/17/installing/index.mdx index 4883cc3bb07..61a8900ad8e 100644 --- a/product_docs/docs/pge/17/installing/index.mdx +++ b/product_docs/docs/pge/17/installing/index.mdx @@ -25,7 +25,7 @@ Select a link to access the applicable installation instructions: ### Debian and derivatives -- [Ubuntu 22.04](linux_x86_64/pge_ubuntu_22), [Ubuntu 20.04](linux_x86_64/pge_ubuntu_20) +- [Ubuntu 22.04](linux_x86_64/pge_ubuntu_22) - [Debian 12](linux_x86_64/pge_debian_12), [Debian 11](linux_x86_64/pge_debian_11) diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx index 0ec9f379e21..6e773b54920 100644 --- a/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx +++ b/product_docs/docs/pge/17/installing/linux_x86_64/index.mdx @@ -8,7 +8,6 @@ navigation: - pge_other_linux_9 - pge_other_linux_8 - pge_ubuntu_22 - - pge_ubuntu_20 - pge_debian_12 - pge_debian_11 --- @@ -37,8 +36,6 @@ Operating system-specific install instructions are described in the correspondin - [Ubuntu 22.04](pge_ubuntu_22) -- [Ubuntu 20.04](pge_ubuntu_20) - - [Debian 12](pge_debian_12) - [Debian 11](pge_debian_11) diff --git a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx b/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx deleted file mode 100644 index e396a6b58b7..00000000000 --- a/product_docs/docs/pge/17/installing/linux_x86_64/pge_ubuntu_20.mdx +++ /dev/null @@ -1,124 +0,0 @@ ---- -navTitle: Ubuntu 20.04 -title: Installing EDB Postgres Extended Server on Ubuntu 20.04 x86_64 -# This topic is generated from templates. If you have feedback on it, instead of -# editing the page and creating a pull request, please enter a GitHub issue and -# the documentation team will update the templates accordingly. - -redirects: ---- - -## Prerequisites - -Before you begin the installation process: - -- Set up the EDB repository. - - Setting up the repository is a one-time task. If you have already set up your repository, you don't need to perform this step. - - To determine if your repository exists, enter this command: - - `apt-cache search enterprisedb` - - If no output is generated, the repository isn't installed. - - To set up the EDB repository: - - 1. Go to [EDB repositories](https://www.enterprisedb.com/repos-downloads). - - 1. Select the button that provides access to the EDB repository. - - 1. Select the platform and software that you want to download. - - 1. Follow the instructions for setting up the EDB repository. - -## Install the package - -```shell -sudo apt-get -y install edb-postgresextended-17 -``` - -## Initial configuration - -This section steps you through getting started with your cluster including logging in, ensuring the installation was successful, connecting to your cluster, and creating the user password. - -First, you need to initialize and start the database cluster. The `edb-pge-17-setup` script creates a cluster. - -```shell -sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/lib/edb-pge/17/bin/edb-pge-17-setup initdb - -sudo systemctl start edb-pge-17 -``` - -To work in your cluster, log in as the postgres user. Connect to the database server using the psql command-line client. Alternatively, you can use a client of your choice with the appropriate connection string. - -```shell -sudo -iu postgres - -psql postgres -``` - -The server runs with the `peer` or `ident` permission by default. You can change the authentication method by modifying the `pg_hba.conf` file. - -Before changing the authentication method, assign a password to the database superuser, postgres. For more information on changing the authentication, see [Modifying the pg_hba.conf file](../../administration/01_setting_configuration_parameters/#modifying-the-pg_hbaconf-file). - -```sql -ALTER ROLE postgres with PASSWORD 'password'; -``` - -## Experiment - -Now you're ready to create and connect to a database, create a table, insert data in a table, and view the data from the table. - -First, use psql to create a database named `hr` to hold human resource information. - -```sql -# running in psql -CREATE DATABASE hr; -__OUTPUT__ -CREATE DATABASE -``` - -Connect to the `hr` database inside psql: - -``` -\c hr -__OUTPUT__ -You are now connected to database "hr" as user "postgres". -``` - -Create columns to hold department numbers, unique department names, and locations: - -``` -CREATE TABLE public.dept (deptno numeric(2) NOT NULL CONSTRAINT dept_pk -PRIMARY KEY, dname varchar(14) CONSTRAINT dept_dname_uq UNIQUE, loc -varchar(13)); -__OUTPUT__ -CREATE TABLE -``` - -Insert values into the `dept` table: - -``` -INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK'); -__OUTPUT__ -INSERT 0 1 -``` - -``` -INSERT into dept VALUES (20,'RESEARCH','DALLAS'); -__OUTPUT__ -INSERT 0 1 -``` - -View the table data by selecting the values from the table: - -``` -SELECT * FROM dept; -__OUTPUT__ -deptno | dname | loc ---------+------------+---------- -10 | ACCOUNTING | NEW YORK -20 | RESEARCH | DALLAS -(2 rows) -``` From 098acf98a0e3e799c9c22e71a47e0976e0f39ffc Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 2 Dec 2024 12:30:58 +0530 Subject: [PATCH 44/65] Cloud Service - EDB hosted deprecation note Added a deprecation note for EDB hosted cloud service --- advocacy_docs/edb-postgres-ai/cloud-service/index.mdx | 4 ++++ .../edb-postgres-ai/cloud-service/release_notes/index.mdx | 4 ++++ advocacy_docs/edb-postgres-ai/index.mdx | 3 +++ 3 files changed, 11 insertions(+) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx index 2bea31b38d2..22037980b9f 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx @@ -18,6 +18,10 @@ redirects: - /biganimal/latest/overview/ --- +!!!note "Deprecation" +Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. +!!! + The EDB Postgres® AI Cloud Service is a holistic platform which includes hybrid data estate management, observability, analytics, and AI capabilities. ## Overview diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx index d95154b39d7..c128684f6c4 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx @@ -18,6 +18,10 @@ redirects: indexCards: none --- +!!!note "Deprecation" +Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. +!!! + The Cloud Service documentation describes the latest version of Cloud Service, including minor releases and patches. These release notes provide information on what was new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature. | 2024 | diff --git a/advocacy_docs/edb-postgres-ai/index.mdx b/advocacy_docs/edb-postgres-ai/index.mdx index 4ee4c49ef4e..7b0590d93b3 100644 --- a/advocacy_docs/edb-postgres-ai/index.mdx +++ b/advocacy_docs/edb-postgres-ai/index.mdx @@ -22,3 +22,6 @@ navigation: The home of all EDB Postgres® AI documentation. +!!!note "Deprecation" +Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. +!!! \ No newline at end of file From c38ea18ab11d4385ea2b4324eece7df32a62382c Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 2 Dec 2024 12:31:12 +0530 Subject: [PATCH 45/65] Update index.mdx --- .../cloud-service/release_notes/index.mdx | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx index c128684f6c4..17f4d7417ba 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx @@ -39,19 +39,19 @@ The Cloud Service documentation describes the latest version of Cloud Service, i
2023 -|| -|--------------------------------------| -| [December 2023](2023/2023_12_dec_rel_notes) | -| [November 2023](2023/2023_11_nov_rel_notes) | -| [October 2023](2023/2023_10_oct_rel_notes) | -| [September 2023](2023/2023_09_sep_rel_notes)| -| [August 2023](2023/2023_08_aug_rel_notes) | -| [July 2023](2023/2023_07_jul_rel_notes) | -| [June 2023](2023/2023_06_jun_rel_notes) | -| [May 2023](2023/2023_05_may_rel_notes) | -| [April 2023](2023/2023_04_apr_rel_notes) | -| [March 2023](2023/2023_03_mar_rel_notes) | -| [February 2023](2023/2023_02_feb_rel_notes) | -| [January 2023](2023/2023_01_jan_rel_notes) | +| 2023 | +|----------------------------------------------| +| [December 2023](2023/2023_12_dec_rel_notes) | +| [November 2023](2023/2023_11_nov_rel_notes) | +| [October 2023](2023/2023_10_oct_rel_notes) | +| [September 2023](2023/2023_09_sep_rel_notes) | +| [August 2023](2023/2023_08_aug_rel_notes) | +| [July 2023](2023/2023_07_jul_rel_notes) | +| [June 2023](2023/2023_06_jun_rel_notes) | +| [May 2023](2023/2023_05_may_rel_notes) | +| [April 2023](2023/2023_04_apr_rel_notes) | +| [March 2023](2023/2023_03_mar_rel_notes) | +| [February 2023](2023/2023_02_feb_rel_notes) | +| [January 2023](2023/2023_01_jan_rel_notes) |
From cad91f291e2fc983ffe91b6a4873a1fb7bfc10bc Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 2 Dec 2024 13:05:57 +0530 Subject: [PATCH 46/65] Moved deprecation note as a dsiplay banner as suggested by Dj --- advocacy_docs/edb-postgres-ai/cloud-service/index.mdx | 5 +---- advocacy_docs/edb-postgres-ai/index.mdx | 7 ++----- 2 files changed, 3 insertions(+), 9 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx index 22037980b9f..82ed2e3e1ec 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx @@ -16,12 +16,9 @@ redirects: - /purl/upm/home/ - /biganimal/latest/ - /biganimal/latest/overview/ +displayBanner: "Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses." --- -!!!note "Deprecation" -Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. -!!! - The EDB Postgres® AI Cloud Service is a holistic platform which includes hybrid data estate management, observability, analytics, and AI capabilities. ## Overview diff --git a/advocacy_docs/edb-postgres-ai/index.mdx b/advocacy_docs/edb-postgres-ai/index.mdx index 7b0590d93b3..7fb885db2e9 100644 --- a/advocacy_docs/edb-postgres-ai/index.mdx +++ b/advocacy_docs/edb-postgres-ai/index.mdx @@ -18,10 +18,7 @@ navigation: - developer-guides - platforms-and-tools - extensions-and-tools +displayBanner: "Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses." --- -The home of all EDB Postgres® AI documentation. - -!!!note "Deprecation" -Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. -!!! \ No newline at end of file +The home of all EDB Postgres® AI documentation. \ No newline at end of file From 2ba4f62b04e78ea4356741d441a7dae4cfa11a5f Mon Sep 17 00:00:00 2001 From: Dj Walker-Morgan Date: Mon, 2 Dec 2024 09:30:47 +0000 Subject: [PATCH 47/65] Modifications for displayBanner and cascade Signed-off-by: Dj Walker-Morgan --- advocacy_docs/edb-postgres-ai/cloud-service/index.mdx | 5 ++++- advocacy_docs/edb-postgres-ai/index.mdx | 7 +++++-- src/templates/learn-doc.js | 6 ++++++ 3 files changed, 15 insertions(+), 3 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx index 82ed2e3e1ec..8e0e0e87484 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx @@ -2,6 +2,8 @@ title: EDB Postgres AI Cloud Service navTitle: Cloud Service description: An introduction to the EDB Postgres AI Cloud Service and its features. +directoryDefaults: + displayBanner: "Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses." navigation: - getting_started - using_cluster @@ -16,11 +18,12 @@ redirects: - /purl/upm/home/ - /biganimal/latest/ - /biganimal/latest/overview/ -displayBanner: "Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses." + --- The EDB Postgres® AI Cloud Service is a holistic platform which includes hybrid data estate management, observability, analytics, and AI capabilities. + ## Overview The EDB Postgres AI Cloud Service itself is a fully managed cloud service that provides a high-performance, scalable, and secure database platform for analytics and AI workloads. It also provides the platform for [EDB Postgres AI Analytics](../analytics/) and [EDB Postgres AIDB](../ai-ml/) services. diff --git a/advocacy_docs/edb-postgres-ai/index.mdx b/advocacy_docs/edb-postgres-ai/index.mdx index 7fb885db2e9..933498649ad 100644 --- a/advocacy_docs/edb-postgres-ai/index.mdx +++ b/advocacy_docs/edb-postgres-ai/index.mdx @@ -18,7 +18,10 @@ navigation: - developer-guides - platforms-and-tools - extensions-and-tools -displayBanner: "Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses." --- -The home of all EDB Postgres® AI documentation. \ No newline at end of file +The home of all EDB Postgres® AI documentation. + +!!!note "Deprecation" + Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. + diff --git a/src/templates/learn-doc.js b/src/templates/learn-doc.js index c5bcdcd0f0f..91132384f08 100644 --- a/src/templates/learn-doc.js +++ b/src/templates/learn-doc.js @@ -215,6 +215,12 @@ const LearnDocTemplate = ({ data, pageContext }) => {
{editOrFeedbackButton}
+ {frontmatter.displayBanner ? ( + + ) : null} + Date: Mon, 2 Dec 2024 10:09:45 +0000 Subject: [PATCH 48/65] Addeed release notes for November Signed-off-by: Dj Walker-Morgan --- .../release_notes/2024_11_nov_rel_notes.mdx | 14 ++++++++++++++ .../cloud-service/release_notes/index.mdx | 2 ++ 2 files changed, 16 insertions(+) create mode 100644 advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_11_nov_rel_notes.mdx diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_11_nov_rel_notes.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_11_nov_rel_notes.mdx new file mode 100644 index 00000000000..19249b36a3f --- /dev/null +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/2024_11_nov_rel_notes.mdx @@ -0,0 +1,14 @@ +--- +title: Cloud Service November 2024 release notes +navTitle: November 2024 +redirect: +- /edb-postgres-ai/cloud-service/release_notes/2024_11_nov_rel_notes/ +--- + +EDB Postgres® AI Cloud Service's November 2024 release includes the following enhancements and bug fixes: + +| Type | Description | +|------|-------------| +| Enhancement | Expansion of service notifications to customers via Slack, PagerDuty, Webhook | +| Enhancement | BigAnimal CLI v3.10.0 is now available. Learn more about what’s new [**here**](https://cli.biganimal.com/versions/v3.10.0/). | +| Enhancement | Terrraform provider for EDB Postgres AI Cloud Service 1.2.0 is now available. Learn more about what’s new [**here**](https://github.com/EnterpriseDB/terraform-provider-biganimal/releases/tag/v1.2.0). | diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx index 17f4d7417ba..b1635c07f2b 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx @@ -3,6 +3,7 @@ title: Cloud Service release notes navTitle: Release notes description: Provides monthly release notes for Cloud Service navigation: + - 2024_11_nov_rel_notes - 2024_10_oct_rel_notes - 2024_09_sep_rel_notes - 2024_08_aug_rel_notes @@ -26,6 +27,7 @@ The Cloud Service documentation describes the latest version of Cloud Service, i | 2024 | |----------------------------------------| +| [November 2024](2024_11_nov_rel_notes) | | [October 2024](2024_10_oct_rel_notes) | | [September 2024](2024_09_sep_rel_notes)| | [August 2024](2024_08_aug_rel_notes) | From 94144c44a5ffe6fdc6a3e02c94b2de7dfd43ce49 Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 2 Dec 2024 18:11:49 +0530 Subject: [PATCH 49/65] Update advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx Co-authored-by: gvasquezvargas --- .../edb-postgres-ai/cloud-service/release_notes/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx index b1635c07f2b..2f417028986 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx @@ -20,7 +20,7 @@ indexCards: none --- !!!note "Deprecation" -Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. +The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. We recommend that affected users transition to an alternative solution immediately. Further updates will be provided as the removal progresses. !!! The Cloud Service documentation describes the latest version of Cloud Service, including minor releases and patches. These release notes provide information on what was new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature. From 5e3a46da77f6074b546331f0ff3d9d559101e71d Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 2 Dec 2024 18:16:51 +0530 Subject: [PATCH 50/65] Updated note as per suggestion from Gaby --- advocacy_docs/edb-postgres-ai/cloud-service/index.mdx | 2 +- advocacy_docs/edb-postgres-ai/index.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx index 8e0e0e87484..b6019e8d78d 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx @@ -3,7 +3,7 @@ title: EDB Postgres AI Cloud Service navTitle: Cloud Service description: An introduction to the EDB Postgres AI Cloud Service and its features. directoryDefaults: - displayBanner: "Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses." + displayBanner: "The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. We recommend that affected users transition to an alternative solution immediately. Further updates will be provided as the removal progresses." navigation: - getting_started - using_cluster diff --git a/advocacy_docs/edb-postgres-ai/index.mdx b/advocacy_docs/edb-postgres-ai/index.mdx index 933498649ad..81a9f19dacf 100644 --- a/advocacy_docs/edb-postgres-ai/index.mdx +++ b/advocacy_docs/edb-postgres-ai/index.mdx @@ -23,5 +23,5 @@ navigation: The home of all EDB Postgres® AI documentation. !!!note "Deprecation" - Please be advised that the EDB Hosted Cloud Service has been deprecated. Support will still be available for current customers. However the related documentation topics removal work is in progress and will be removed shortly. We recommend affected users transition to alternative solutions as soon as possible. Further updates will be provided as the transition progresses. + The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. We recommend that affected users transition to an alternative solution immediately. Further updates will be provided as the removal progresses. From 9e22b32edb5f859a35b50fc22e6044add1814aed Mon Sep 17 00:00:00 2001 From: nidhibhammar <59045594+nidhibhammar@users.noreply.github.com> Date: Mon, 2 Dec 2024 20:06:41 +0530 Subject: [PATCH 51/65] made edits as suggested by David --- advocacy_docs/edb-postgres-ai/cloud-service/index.mdx | 2 +- .../edb-postgres-ai/cloud-service/release_notes/index.mdx | 2 +- advocacy_docs/edb-postgres-ai/index.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx index b6019e8d78d..a02602d3cba 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/index.mdx @@ -3,7 +3,7 @@ title: EDB Postgres AI Cloud Service navTitle: Cloud Service description: An introduction to the EDB Postgres AI Cloud Service and its features. directoryDefaults: - displayBanner: "The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. We recommend that affected users transition to an alternative solution immediately. Further updates will be provided as the removal progresses." + displayBanner: "The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. Further updates will be provided as the removal progresses." navigation: - getting_started - using_cluster diff --git a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx index 2f417028986..c72d98c6e6f 100644 --- a/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx +++ b/advocacy_docs/edb-postgres-ai/cloud-service/release_notes/index.mdx @@ -20,7 +20,7 @@ indexCards: none --- !!!note "Deprecation" -The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. We recommend that affected users transition to an alternative solution immediately. Further updates will be provided as the removal progresses. +The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. Further updates will be provided as the removal progresses. !!! The Cloud Service documentation describes the latest version of Cloud Service, including minor releases and patches. These release notes provide information on what was new in each release. For new functionality introduced in a minor or patch release, the content also indicates the release that introduced the feature. diff --git a/advocacy_docs/edb-postgres-ai/index.mdx b/advocacy_docs/edb-postgres-ai/index.mdx index 81a9f19dacf..5b4ab79fffe 100644 --- a/advocacy_docs/edb-postgres-ai/index.mdx +++ b/advocacy_docs/edb-postgres-ai/index.mdx @@ -23,5 +23,5 @@ navigation: The home of all EDB Postgres® AI documentation. !!!note "Deprecation" - The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. We recommend that affected users transition to an alternative solution immediately. Further updates will be provided as the removal progresses. + The EDB Hosted Cloud Service has been deprecated. Support is available for current customers. However, the related documentation topics will be removed shortly. Further updates will be provided as the removal progresses. From 99d4f4a29252c5b6d65e94b98523d425ddd9ba98 Mon Sep 17 00:00:00 2001 From: Bobby Bissett Date: Mon, 2 Dec 2024 10:47:30 -0500 Subject: [PATCH 52/65] Added a paragraph about the Promote Status section of cluster status output This leaves the existing info mostly alone, but adds an explanation of the Promote Status output and why it's there. Users sometimes think this is meant to check if replication is working, or want more information listed. The info that efm collects here is all related to whether or not a promotion would be safe (or a switchover allowed) and how a standby would be picked. It's not meant to be the place a user monitors replication. The existing text goes into detail a little about it, but this new text explains why this particular info is here. --- product_docs/docs/efm/4/06_monitoring_efm_cluster.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/product_docs/docs/efm/4/06_monitoring_efm_cluster.mdx b/product_docs/docs/efm/4/06_monitoring_efm_cluster.mdx index 94c111c78d9..07e4873073a 100644 --- a/product_docs/docs/efm/4/06_monitoring_efm_cluster.mdx +++ b/product_docs/docs/efm/4/06_monitoring_efm_cluster.mdx @@ -76,7 +76,9 @@ Standby priority host list: 172.19.12.163 172.19.10.2 ``` -The `Promote Status` section of the report is the result of a direct query from the node on which you are invoking the `cluster-status` command to each database in the cluster. The query also returns the transaction log location of each database. Because the queries to each database return at different times, the LSNs might not match even if streaming replication is working normally for the cluster. To get the latest view of replication, connect to the primary database, and execute SQL command `SELECT * FROM pg_stat_replication;`. +The `Promote Status` section of the report includes information related to promotion in the cluster. The LSN information is used, along with the `Standby priority host list`, when choosing a standby to promote. If there is a mismatch in replay LSNs, Failover Manager will not allow a switchover (though the promotion of a standby is always allowed). + +The LSN information is the result of a direct query from the node on which you are invoking the `cluster-status` command to each database in the cluster. The query also returns the transaction log location of each database. Because the queries to each database return at different times, the LSNs might not match even if streaming replication is working normally for the cluster. To get the latest view of replication, connect to the primary database, and execute SQL command `SELECT * FROM pg_stat_replication;`. ```text Promote Status: From f73198cfd898820e1a62f406d3f21f5f85072da1 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 3 Dec 2024 15:03:34 +0100 Subject: [PATCH 53/65] Typos in Install Beacon agent doc --- .../edb-postgres-ai/console/estate/agent/install-agent.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx index fa6d7c26ca0..c31dd14dbf8 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx @@ -82,7 +82,7 @@ export BEACON_AGENT_ACCESS_KEY= export BEACON_AGENT_PROJECT_ID= ``` -Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory. using those environment variables. +Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory using those environment variables. You also need to specify the Beacon configuration directory for storing the configuration file and the name of the configuration file to generate there. The `$HOME/.beacon/` file is one of the default locations which `beacon_agent` searches for `beacon_agent.yaml` when it starts. Using the `-file` flag tells the agent setup process to create its configuration file in a specific location. @@ -153,7 +153,7 @@ provider: poll_interval: 5m0s ``` -## Test Beacon Agent locally. +## Test Beacon Agent locally For an initial test of the agent, you can get it to send the data that it would normally send to the EDB Enterprise AI control plane to standard output, your terminal session, instead. This allows you to quickly confirm if the agent is successfully able to gather data and what that data looks like. From 633150cf87aa545ea5aa429a6d0e41a545b4a19b Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 3 Dec 2024 15:06:10 +0100 Subject: [PATCH 54/65] Removed heading 2 final stop --- .../edb-postgres-ai/console/estate/agent/install-agent.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx index c31dd14dbf8..7ca575059e7 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx @@ -210,7 +210,7 @@ agent: ``` -## Run Beacon Agent. +## Run Beacon Agent Run the agent using the following command: From b96aff7ba195c6283c84a1888ad7cda872761cd7 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Mon, 25 Nov 2024 15:06:41 -0500 Subject: [PATCH 55/65] Edits to MTK 55.10 release branch #6186 --- .../55/07_invoking_mtk/08_mtk_command_options.mdx | 8 ++++---- .../55/mtk_rel_notes/mtk_55100_rel_notes.mdx | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx index b1e1ae155be..b0041e0bccc 100644 --- a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx +++ b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx @@ -490,21 +490,21 @@ Specify each entry in the file on a separate line in a key=value pair. The left ### `-mapVirtualToRegular` -Include the `-mapVirtualToRegular` option to migrate virtual, computed or generated columns in the source database to regular columns in the target database. +Include the `-mapVirtualToRegular` option to migrate virtual, computed, or generated columns in the source database to regular columns in the target database. -Turning virtual columns to regular columns is helpful when the expression used to compute the values in the source database column is not supported in the target database or cannot be translated into an expression supported by the target database. With this option, you can still migrate the column's values to the target, but the values will no longer be computed dynamically, as they are stored in a regular column. +Turning virtual columns to regular columns is helpful when the expression used to compute the values in the source database column isn't supported in the target database or can't be translated into an expression supported by the target database. With this option, you can still migrate the column's values to the target, but the values will no longer be computed dynamically, as they're stored in a regular column. For schema migrations, including the option results in all virtual columns in the source database being migrated to regular columns in the target database. For data migrations, including the option extracts the computed values from all computed columns in the source database and inserts those values into regular columns in the target database. -For example, in: +In the following example, a column `FullName` is computed from other two columns called `FirstName` and `LastName` in the source database. This column is migrated as a regular column called `FullName` in the target database. ``` ./runMTK.sh -sourcedbtype sqlserver -targetdbtype enterprisedb -mapVirtualToRegular -allTables ``` -A column called `FullName` that is computed from other two columns called `FirstName` and `LastName` in the source database, is migrated as a regular column called `FullName` in the target database. In the target, this column is no longer dynamically generated, but displays the `FullName` value the source database had at the time the migration was performed. +In the target, this column is no longer dynamically generated, but displays the `FullName` value the source database had at the time the migration was performed. ## Connection retry options diff --git a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx index 8cd5a8bf42b..16e34f4e7d1 100644 --- a/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx +++ b/product_docs/docs/migration_toolkit/55/mtk_rel_notes/mtk_55100_rel_notes.mdx @@ -12,6 +12,6 @@ New features, enhancements, bug fixes, and other changes in Migration Toolkit 55 | Enhancement | Migration Toolkit now supports PostgreSQL version 17 and EDB Postgres Advanced Server version 17 both as a source and target database. | | | Enhancement | Improved the handling and consistency in migrating virtual columns across different source and target database combinations.
You can now choose whether to migrate virtual columns as virtual columns or map them to regular columns in the target. See [mapVirtualToRegular](../07_invoking_mtk/08_mtk_command_options/#-mapvirtualtoregular) for more information. | #38897 | | Bug fix | Fixed an issue that caused synonyms from all source schemas to be migrated even when only one schema was selected for migration. | #41178 | -| Bug fix | Fixed an issue where the MySQL column type `BIGINT AUTO_INCREMENT` is not mapped to the `BIGSERIAL` column type in the target PostgreSQL/EDB Postgres Advanced Server table. | | +| Bug fix | Fixed an issue where the MySQL column type `BIGINT AUTO_INCREMENT` isn't mapped to the `BIGSERIAL` column type in the target PostgreSQL/EDB Postgres Advanced Server table. | | | Bug fix | Fixed the issue where migration fails in parallel mode for a table with a primary key based on the float data type. | | | Bug fix | Fixed an issue where the indexes are skipped from migration when multiple tables are selected for a source MySQL database. | | From 384989b9b18fbd40af005845086a4249aa197541 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Mon, 25 Nov 2024 15:08:35 -0500 Subject: [PATCH 56/65] Update product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx --- .../55/07_invoking_mtk/08_mtk_command_options.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx index b0041e0bccc..f692dc668c7 100644 --- a/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx +++ b/product_docs/docs/migration_toolkit/55/07_invoking_mtk/08_mtk_command_options.mdx @@ -504,7 +504,7 @@ In the following example, a column `FullName` is computed from other two columns ./runMTK.sh -sourcedbtype sqlserver -targetdbtype enterprisedb -mapVirtualToRegular -allTables ``` -In the target, this column is no longer dynamically generated, but displays the `FullName` value the source database had at the time the migration was performed. +In the target, this column is no longer dynamically generated but displays the `FullName` value the source database had at the time the migration was performed. ## Connection retry options From 9dc50491adebef9f767b4288e4a8c13cd8fb92e2 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Mon, 25 Nov 2024 15:14:02 -0500 Subject: [PATCH 57/65] Edits to 3.0.2 release update #6225 --- product_docs/docs/livecompare/3/oracle_support.mdx | 2 +- product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/livecompare/3/oracle_support.mdx b/product_docs/docs/livecompare/3/oracle_support.mdx index 3d2873e13ea..b226a3270d5 100644 --- a/product_docs/docs/livecompare/3/oracle_support.mdx +++ b/product_docs/docs/livecompare/3/oracle_support.mdx @@ -17,7 +17,7 @@ For example, you can define `technology = oracle` in a data connection. You can All other data connections must be PostgreSQL. -The `user` you use to connect to Oracle must have the necessary privileges to read the data from the tables you want to compare. Specifically, `CONNECT`, `SELECT ANY TABLE` and `SELECT_CATALOG_ROLE`. These can be granted with the command: +The `user` you use to connect to Oracle must have the privileges needed to read the data from the tables you want to compare. Specifically, these privileges are `CONNECT`, `SELECT ANY TABLE`, and `SELECT_CATALOG_ROLE`. These can be granted with the command: ```sql GRANT CONNECT, SELECT ANY TABLE, SELECT_CATALOG_ROLE TO username; diff --git a/product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx b/product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx index 3d274b86c53..361b4790e77 100644 --- a/product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx +++ b/product_docs/docs/livecompare/3/rel_notes/3.0.2_rel_notes.mdx @@ -11,5 +11,5 @@ LiveCompare 3.0.2 includes the following new features, enhancements, bug fixes, | Type | Description | Addresses | |:--------|:---------------------------------------------------------------------------------|:----------| -| Bug Fix | Fixed an issue which caused the application to crash when using replication sets | | -| Enhancement | Revised documentation to clarify what roles are required for Oracle | | +| Bug Fix | Fixed an issue that caused the application to crash when using replication sets. | | +| Enhancement | Revised documentation to clarify the roles that are required for Oracle. | | From 3d180dffe631335471fce035ed795dac9d2b7e16 Mon Sep 17 00:00:00 2001 From: Betsy Gitelman Date: Mon, 25 Nov 2024 15:41:49 -0500 Subject: [PATCH 58/65] Edits to Mig Portal: DDL Extractor note and reorg of extraction section #6259 --- .../edb_ddl_extractor.mdx | 26 +++++++++---------- .../01_mp_schema_extraction/index.mdx | 2 +- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/edb_ddl_extractor.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/edb_ddl_extractor.mdx index 487738b8be4..af6468b035a 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/edb_ddl_extractor.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/edb_ddl_extractor.mdx @@ -7,7 +7,7 @@ navTitle: Using EDB DDL Extractor Download the latest EDB DDL Extractor script from the Migration Portal Projects page. !!! Note - Migration Portal might become unresponsive for very large SQL files, depending on your system and browser resource availability. To resolve this, try extracting fewer schemas at a time to reduce the SQL file size. + Migration Portal might become unresponsive for very large SQL files, depending on your system and browser resource availability. To resolve this issue, try extracting fewer schemas at a time to reduce the SQL file size. ## Prerequisites @@ -24,18 +24,20 @@ You can run the EDB DDL Extractor script in SQL Developer or SQL\*Plus. It uses @edb_ddl_extractor.sql ``` -1. When prompted, if the Oracle user that is running the script has the required privileges, press **Enter** to continue running the script. + The script prompts you to provide the details described in the steps that follow. -1. When prompted, provide the schema name. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter. +1. If the Oracle user that's running the script has the required privileges, press **Enter** to continue running the script. + +1. Provide the schema name. When extracting multiple schemas, use a comma (`‘,’`) as a delimiter. !!! Note If you want to extract all the user schemas from the current database, don't mention any schema names while extracting. However, we recommend mentioning the schema names that you want to extract. -1. When prompted, enter the path or directory for the extractor to store the extracted DDL. If you don't specify a path, the extracted DDL is output to the directory where you ran the SQL\*Plus command. +1. Enter the path or directory for the extractor to store the extracted DDL. If you don't specify a path, the extracted DDL is output to the directory where you ran the SQL\*Plus command. -1. When prompted, enter `yes`or `no` depending on whether you want to extract dependent objects from other schemas. +1. Enter `yes` to extract dependent objects from other schemas or `no` if you don't want to extract them. -1. When prompted, enter `yes`or `no` depending on whether you want to extract grant statements from other schemas. +1. Enter `yes` to extract grant statements from other schemas or `no` if you don't want to want to extract them. ## Example @@ -91,21 +93,19 @@ After loading the `edb_ddl_extractor.sql` script into SQL Developer and connecti 1. If the user for the database connection has the required privileges as listed in the **Script Output** tab, select **Yes** to continue running the script. -2. Enter a comma-separated list of schemas, and select **OK**. +2. Enter a comma-separated list of schemas, and select **OK**. 3. Enter the path for the output file, and select **OK**. The default is the location of the DDL Extractor script. -4. Enter `yes` or `no` to extract dependent objects, and select **OK**. The default is to not extract dependent objects. +4. Enter `yes` or `no` to extract dependent objects, and select **OK**. The default is not to extract dependent objects. -5. Enter `yes` or `no` to extract grant statements, and select **OK**. The default setting is not to extract grant statements. +5. Enter `yes` or `no` to extract grant statements, and select **OK**. The default is not to extract grant statements. Output of the DDL Extractor run appears in the Script Output tab. The name of the output file appears after the `Extraction Completed` message in the script output. !!! Note You can also enter single schema name in both SQL\*Plus and SQL Developer. -The script then iterates through the object types in the source database. Once the task is completed, the `.SQL` output is stored at the location you entered (e.g., `c:\Users\Example\Desktop\`). - -See [file encoding](/migration_portal/latest/known_issues_notes/#file-encoding) for information about the file encoding format expected by Migration Portal. - +The script then iterates through the object types in the source database. After the task is completed, the `.SQL` output is stored at the location you entered (for example, `c:\Users\Example\Desktop\`). +See [File encoding](/migration_portal/latest/known_issues_notes/#file-encoding) for information about the file encoding format Migration Portal expects. diff --git a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx index 30953d039ec..730a5465906 100644 --- a/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx +++ b/product_docs/docs/migration_portal/4/04_mp_migrating_database/01_mp_schema_extraction/index.mdx @@ -15,7 +15,7 @@ navigation: ## Schema extraction methods -You can perform a schema extraction using the EDB or Oracle extraction tools.Select one of the following for instructions and examples: +You can perform a schema extraction using the EDB or Oracle extraction tools. For instructions and examples, see: - [EDB DDL Extractor](edb_ddl_extractor) (recommended method) - [Oracle Data Pump utilities](01_data_pump_utility/) From 20c6766d2005b34a892b10842c2d1116eebc7a5d Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Wed, 4 Dec 2024 09:47:53 +0100 Subject: [PATCH 59/65] Committing DJs suggestion Co-authored-by: Dj Walker-Morgan <126472455+djw-m@users.noreply.github.com> --- .../edb-postgres-ai/console/estate/agent/install-agent.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx index 7ca575059e7..6b9c1ecd041 100644 --- a/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx +++ b/advocacy_docs/edb-postgres-ai/console/estate/agent/install-agent.mdx @@ -82,7 +82,7 @@ export BEACON_AGENT_ACCESS_KEY= export BEACON_AGENT_PROJECT_ID= ``` -Running the `beacon-agent setup` command creates a configuration file in the Beacon configuration directory using those environment variables. +These environment variables are used when you run the `beacon-agent setup` command to create a configuration file in the Beacon configuration directory. You also need to specify the Beacon configuration directory for storing the configuration file and the name of the configuration file to generate there. The `$HOME/.beacon/` file is one of the default locations which `beacon_agent` searches for `beacon_agent.yaml` when it starts. Using the `-file` flag tells the agent setup process to create its configuration file in a specific location. From 91ce4bae9b3e5d6b429ac22bb2101c41444b0d3b Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Mon, 25 Nov 2024 09:42:00 +0100 Subject: [PATCH 60/65] Changed location of DBMS_XMLDOM in left nav bar --- product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx | 2 +- .../{dbms_xmldom => 18_dbms_xmldom}/appendchild.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/createelement.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/createtextnode.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/freedocument.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/getattribute.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/getchildnodes.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/getfirstchild.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/getlength.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/getnodename.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/getnodevalue.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/getxmltype.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/index.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/item.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/makeelement.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/makenode.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/newdomdocument.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/setattribute.mdx | 0 .../{dbms_xmldom => 18_dbms_xmldom}/setversion.mdx | 0 19 files changed, 1 insertion(+), 1 deletion(-) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/appendchild.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/createelement.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/createtextnode.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/freedocument.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/getattribute.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/getchildnodes.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/getfirstchild.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/getlength.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/getnodename.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/getnodevalue.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/getxmltype.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/index.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/item.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/makeelement.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/makenode.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/newdomdocument.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/setattribute.mdx (100%) rename product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/{dbms_xmldom => 18_dbms_xmldom}/setversion.mdx (100%) diff --git a/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx b/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx index fa8e3ce50bf..dd23db89dcf 100644 --- a/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx +++ b/product_docs/docs/epas/17/epas_rel_notes/epas17_2_rel_notes.mdx @@ -19,7 +19,7 @@ The `pgAgent` and `adminpack` packages are end of life from EPAS 17 and later. |----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------| | Upstream merge | Merged with community PostgreSQL 17.2. See the [PostgreSQL 17 Release Notes](https://www.postgresql.org/docs/17/release-17-2.html) for more information. | | | Feature | Added support for the Oracle-compatible `BFILE` native datatype and the `DBMS_LOB` package APIs. See the [DBMS_LOB](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/) for more information. | | -| Feature | Added support for the Oracle-compatible `DBMS_XMLDOM` package to provide interface for HTML and XML documents. See the [DBMS_XMLDOM](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom) for more information. | | +| Feature | Added support for the Oracle-compatible `DBMS_XMLDOM` package to provide interface for HTML and XML documents. See the [DBMS_XMLDOM](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom) for more information. | | | Feature | Added support for the Oracle-compatible `DBMS_ASSERT` package to validate input properties and sanitize user input, thereby reducing the risk of SQL injections. See the [DBMS_ASSERT](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert) for more information. | | | Feature | Added support for the Oracle-equivalent `NLS_UPPER`,`NLS_LOWER`, and `NLS_INITCAP` functions. See the [NLS functions](../reference/sql_reference/03_functions_and_operators/nls_functions) for more information. | | | Feature | Implemented `alteruser` utility to modify roles in the clusters. See the [alteruser utility](/tools/alteruser_utility/) for more information. | | diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/appendchild.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/appendchild.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/createelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/createelement.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/createtextnode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/createtextnode.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/freedocument.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/freedocument.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/freedocument.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/freedocument.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getattribute.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getchildnodes.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getchildnodes.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getchildnodes.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getchildnodes.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getfirstchild.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getfirstchild.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getfirstchild.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getfirstchild.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getlength.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getlength.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getlength.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getlength.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getnodename.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodename.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getnodename.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodename.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getnodevalue.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodevalue.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getnodevalue.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodevalue.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getxmltype.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getxmltype.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/getxmltype.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getxmltype.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/index.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/index.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/item.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/item.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/item.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/item.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/makeelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/makeelement.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/makenode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/makenode.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/newdomdocument.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/newdomdocument.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/newdomdocument.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/newdomdocument.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/setattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/setattribute.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/setversion.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setversion.mdx similarity index 100% rename from product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/dbms_xmldom/setversion.mdx rename to product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setversion.mdx From 078535c3880baab6256893965773ee12c30421d6 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Mon, 25 Nov 2024 09:58:46 +0100 Subject: [PATCH 61/65] Changes to createElement, createTextNode and MakeNode --- .../03_built-in_packages/18_dbms_xmldom/createelement.mdx | 2 +- .../03_built-in_packages/18_dbms_xmldom/createtextnode.mdx | 2 +- .../03_built-in_packages/18_dbms_xmldom/makenode.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx index ddbe6da1296..4a5391bb3fa 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx @@ -20,7 +20,7 @@ Tag name to be given to the new DOMELEMENT. ## Examples -This example creates a new XML DOMDocument named `l_domdoc` and a new DOMElement named `l_department_element` with tag name `Departments`. It then converts `l_domdoc` and `l_department_element` into DOMNodes, so `l_department_element` can be appended as a child to `l_domdoc`. +This example creates a new XML DOMDocument named `l_domdoc` and a new DOMElement named `l_department_element` with tag name `Departments`. It then appends the DOMElement as a child of the DOMDocument. ```sql DECLARE diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx index 5fc7eef5de8..172c55044ad 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx @@ -20,7 +20,7 @@ Content provided for the DOMTEXT node. ## Examples -This example creates a new XML DOMDocument, and turns it into a node so it can be root. Then, it creates a DOMElement with tag name “Departments”, turns it into a node and appends it to the DOMDocument. It then creates a text node with tag name “Depts list” and appends it to the “Departments” node. +This example creates a new XML DOMDocument, a DOMElement with tag name “Departments” and a text node with “Depts list” as its value. The DOMElement is appended as a child to the DOMDocument, and the text node as a child to the DOMElement. ```sql DECLARE diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx index 31665be5532..a88374d02b1 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx @@ -30,7 +30,7 @@ The `DOMTEXT` to be casted You can turn a `DOMDocument`, `DOMElement` and `DOMText` to a `DOMNode`. -This example creates a new XML DOMDocument, and turns it into a node so it can be root. Then, it creates a DOMElement with tag name “Departments”, turns it into a node and appends it to the DOMDocument. It then creates a text node with tag name “Depts list” and appends it to the “Departments” node. +This example creates a new XML DOMDocument, and turns it into a DOMNode so it can be root. Then, it creates a DOMElement with tag name “Departments”, turns it into a node and appends it to the DOMDocument. It then creates a text node DOMNode with tag name “Depts list” and appends it as a child to the DOMElement node. ```sql DECLARE From d2eca17ae0cfcb8a0506ef0ac5dff7881049c44e Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Mon, 25 Nov 2024 17:52:54 +0100 Subject: [PATCH 62/65] streamline formatting: programs and subprograms capitalized in text and code, types lower-case --- .../06_dbms_lob/11_substr.mdx | 2 +- .../18_dbms_xmldom/appendchild.mdx | 14 +++--- .../18_dbms_xmldom/createelement.mdx | 20 ++++---- .../18_dbms_xmldom/createtextnode.mdx | 34 ++++++------- .../18_dbms_xmldom/freedocument.mdx | 14 +++--- .../18_dbms_xmldom/getattribute.mdx | 48 +++++++++---------- .../18_dbms_xmldom/getchildnodes.mdx | 40 ++++++++-------- .../18_dbms_xmldom/getfirstchild.mdx | 22 ++++----- .../18_dbms_xmldom/getlength.mdx | 42 ++++++++-------- .../18_dbms_xmldom/getnodename.mdx | 14 +++--- .../18_dbms_xmldom/getnodevalue.mdx | 16 +++---- .../18_dbms_xmldom/getxmltype.mdx | 28 +++++------ .../18_dbms_xmldom/index.mdx | 42 ++++++++-------- .../18_dbms_xmldom/item.mdx | 42 ++++++++-------- .../18_dbms_xmldom/makeelement.mdx | 28 +++++------ .../18_dbms_xmldom/makenode.mdx | 40 ++++++++-------- .../18_dbms_xmldom/newdomdocument.mdx | 30 ++++++------ .../18_dbms_xmldom/setattribute.mdx | 24 +++++----- .../18_dbms_xmldom/setversion.mdx | 18 +++---- 19 files changed, 259 insertions(+), 259 deletions(-) diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx index ae685a2ae99..ca1cd0744a7 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx @@ -1,4 +1,4 @@ -s--- +--- title: "SUBSTR" redirects: - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr/ #generated for docs/epas/reorg-role-use-case-mode diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx index 1c46fa3f3ae..1ee2892e1a9 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx @@ -12,7 +12,7 @@ APPENDCHILD(n DOMNode, newChild IN DOMNode) RETURN DOMNode `n` -The DOMNODE where the new node is to be added. +The `DOMNode` where the new node is to be added. `newchild` @@ -24,16 +24,16 @@ This example creates a new XML DOMDocument named `l_domdoc` and a new DOMElement ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_department_element dbms_xmldom.DOMElement; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_department_element DBMS_XMLDOM.DOMElement; l_xmltype XMLTYPE; BEGIN - l_domdoc := dbms_xmldom.NewDOMDocument(); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - PERFORM dbms_xmldom.appendChild(dbms_xmldom.makeNode(l_domdoc), dbms_xmldom.makeNode(l_department_element)); - l_xmltype := dbms_xmldom.getXmlType(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + PERFORM DBMS_XMLDOM.appendChild(DBMS_XMLDOM.MAKENODE(l_domdoc), DBMS_XMLDOM.MAKENODE(l_department_element)); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); DBMS_OUTPUT.PUT_LINE(l_xmltype.getStringVal()); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx index 4a5391bb3fa..b6867947919 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx @@ -2,21 +2,21 @@ title: "CREATEELEMENT" --- -The `CREATEELEMENT` function creates and returns a DOMELEMENT. +The `CREATEELEMENT` function creates and returns a DOMElement. ``` -CREATEELEMENT( doc DOMDOCUMENT, tagname IN VARCHAR2) RETURN DOMELEMENT +CREATEELEMENT( doc DOMDocument, tagname IN VARCHAR2) RETURN DOMElement ``` ## Parameters `doc` -Any DOMDOCUMENT +Any `DOMDocument`. `tagname` -Tag name to be given to the new DOMELEMENT. +Tag name to be given to the new `DOMDocument`. ## Examples @@ -24,16 +24,16 @@ This example creates a new XML DOMDocument named `l_domdoc` and a new DOMElement ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_department_element dbms_xmldom.DOMElement; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_department_element DBMS_XMLDOM.DOMElement; l_xmltype XMLTYPE; BEGIN - l_domdoc := dbms_xmldom.NewDOMDocument(); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - PERFORM dbms_xmldom.appendChild(dbms_xmldom.makeNode(l_domdoc), dbms_xmldom.makeNode(l_department_element)); - l_xmltype := dbms_xmldom.getXmlType(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + PERFORM DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(l_domdoc), DBMS_XMLDOM.MAKENODE(l_department_element)); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); DBMS_OUTPUT.PUT_LINE(l_xmltype.getStringVal()); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx index 172c55044ad..f22cad7a7a0 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createtextnode.mdx @@ -2,44 +2,44 @@ title: "CREATETEXTNODE" --- -The `CREATETEXTNODE` function creates and returns a DOMTEXT node. +The `CREATETEXTNODE` function creates and returns a DOMText node. ``` -CREATETEXTNODE( doc DOMDOCUMENT, data IN VARCHAR2) RETURN DOMTEXT +CREATETEXTNODE( doc DOMDocument, data IN VARCHAR2) RETURN DOMText ``` ## Parameters `doc` -Any DOMDOCUMENT +Any `DOMDocument`. `data` -Content provided for the DOMTEXT node. +Content provided for the `DOMText` node. ## Examples -This example creates a new XML DOMDocument, a DOMElement with tag name “Departments” and a text node with “Depts list” as its value. The DOMElement is appended as a child to the DOMDocument, and the text node as a child to the DOMElement. +This example creates a new XML `DOMDocument`, a `DOMElement` with tag name “Departments” and a text node with “Depts list” as its value. The `DOMElement` is appended as a child to the `DOMDocument`, and the text node as a child to the `DOMElement`. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_root_node dbms_xmldom.DOMNode; - l_department_element dbms_xmldom.DOMElement; - l_departments_node dbms_xmldom.DOMNode; - l_name_text dbms_xmldom.DOMText; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_root_node DBMS_XMLDOM.DOMNode; + l_department_element DBMS_XMLDOM.DOMElement; + l_departments_node DBMS_XMLDOM.DOMNode; + l_name_text DBMS_XMLDOM.DOMText; l_xmltype XMLTYPE; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - l_root_node := dbms_xmldom.makeNode(l_domdoc); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - l_departments_node := dbms_xmldom.appendChild(l_root_node,dbms_xmldom.makeNode(l_department_element)); - l_name_text := dbms_xmldom.createTextNode(l_domdoc, 'Depts list' ); - PERFORM dbms_xmldom.appendChild(l_departments_node,dbms_xmldom.makeNode(l_name_text)); - l_xmltype := dbms_xmldom.getXmlType(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + l_root_node := DBMS_XMLDOM.MAKENODE(l_domdoc); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + l_departments_node := DBMS_XMLDOM.APPENDCHILD(l_root_node,DBMS_XMLDOM.MAKENODE(l_department_element)); + l_name_text := DBMS_XMLDOM.CREATETEXTNODE(l_domdoc, 'Depts list' ); + PERFORM DBMS_XMLDOM.APPENDCHILD(l_departments_node,DBMS_XMLDOM.MAKENODE(l_name_text)); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); DBMS_OUTPUT.PUT_LINE(l_xmltype.getStringVal()); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/freedocument.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/freedocument.mdx index b8b9571de96..ee973653c9b 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/freedocument.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/freedocument.mdx @@ -2,7 +2,7 @@ title: "FREEDOCUMENT" --- -The `FREEDOCUMENT` procedure is used to free the DOMDOCUMENT object. +The `FREEDOCUMENT` procedure is used to free the `DOMDocument` object. ``` FREEDOCUMENT(doc IN DOMDocument) @@ -12,22 +12,22 @@ FREEDOCUMENT(doc IN DOMDocument) `doc` -The DOMDOCUMENT to be made free. +The `DOMDocument` to be made free. ## Examples -This example creates a new DOMDocument, which is not accessible after it has been freed. +This example creates a new `DOMDocument`, which is not accessible after it has been freed. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; + l_domdoc DBMS_XMLDOM.DOMDocument; BEGIN - l_domdoc := dbms_xmldom.newDOMDocument(); - dbms_xmldom.freeDocument(l_domdoc); - dbms_xmldom.setversion(l_domdoc, '1.0'); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(); + DBMS_XMLDOM.FREEDOCUMENT(l_domdoc); + DBMS_XMLDOM.SETVERSION(l_domdoc, '1.0'); END; / ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx index 415a5bda18c..f7b07d85085 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx @@ -2,7 +2,7 @@ title: "GETATTRIBUTE" --- -The `GETATTRIBUTE` function returns the value of an attribute of an DOMELEMENT by name. +The `GETATTRIBUTE` function returns the value of an attribute of an `DOMElement` by name. ``` GETATTRIBUTE(elem DOMElement, name IN VARCHAR2) RETURN VARCHAR2 @@ -14,7 +14,7 @@ GETATTRIBUTE(elem DOMElement, name IN VARCHAR2, ns IN VARCHAR2) RETURN VARCHAR2 `elem` -The DOMELEMENT whose attribute needs to be obtained. +The `DOMElement` whose attribute needs to be obtained. `name` @@ -22,49 +22,49 @@ The attribute name which needs to be obtained. `ns` -The namespace URI +The namespace URI. ## Examples -This example creates a new DOMDocument named `l_domdoc`, and a DOMElement named `elem` with tag name “Departments”. It then adds an attribute to the DOMElement named ‘value’. The example turns both `l_domdoc` and `elem` to DOMNodes to append `elem` as a child of `l_domdoc`. Finally, it converts `l_domdoc` to `XMLType`. +This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It then adds an attribute to the `DOMElement` named ‘value’. The example turns both `l_domdoc` and `elem` to `DOMNodes` to append `elem` as a child of `l_domdoc`. Finally, it converts `l_domdoc` to `XMLType`. The `get` subprogram returns the value of the attribute `attr` of the "Departments" element. ```sql DECLARE - l_xml xmltype; - l_domdoc dbms_xmldom.DOMDocument; - l_departments_node dbms_xmldom.DOMNode; - elem dbms_xmldom.DOMElement; + l_xml XMLType; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_departments_node DBMS_XMLDOM.DOMNode; + elem DBMS_XMLDOM.DOMElement; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - elem := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - dbms_xmldom.setAttribute(elem, 'attr', 'value'); - PERFORM dbms_xmldom.appendchild(dbms_xmldom.makeNode(l_domdoc), dbms_xmldom.makeNode(elem)); - l_xml := dbms_xmldom.getxmltype(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + elem := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + DBMS_XMLDOM.SETATTRIBUTE(elem, 'attr', 'value'); + PERFORM DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(l_domdoc), DBMS_XMLDOM.MAKENODE(elem)); + l_xml := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); dbms_output.put_line(l_xml.getStringVal()); - dbms_output.put_line(dbms_xmldom.getattribute(elem, 'attr')); + dbms_output.put_line(DBMS_XMLDOM.GETATTRIBUTE(elem, 'attr')); END; ``` -This example defines a namespace named “example” and uses an XMLtype string to create an XML structure. `GETFIRSTCHILD` then returns a `DOMNODE` that represents a `DOMELEMENT`. Since `GETATTRIBUTE` expects a `DOMELEMENT`, the `MAKEELEMENT` function converts a specified `DOMNODE` into a `DOMELEMENT` and returns it. +This example defines a namespace named “example” and uses an XMLtype string to create an XML structure. `GETFIRSTCHILD` then returns a `DOMNode` that represents a `DOMElement`. Since `GETATTRIBUTE` expects a `DOMElement`, the `MAKEELEMENT` function converts a specified `DOMNode` into a `DOMElement` and returns it. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_departments_node dbms_xmldom.DOMNode; - item_node dbms_xmldom.DOMNode; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_departments_node DBMS_XMLDOM.DOMNode; + item_node DBMS_XMLDOM.DOMNode; BEGIN - l_domdoc := dbms_xmldom.newDOMDocument(XMLTYPE('')); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(XMLTYPE('')); - l_departments_node := DBMS_XMLDOM.getfirstchild(dbms_xmldom.makeNode(l_domdoc)); - item_node := dbms_xmldom.getfirstchild(l_departments_node); - dbms_output.put_line('item node: ' || dbms_xmldom.getnodename(item_node)); - dbms_output.put_line('item attr: ' || dbms_xmldom.getattribute(dbms_xmldom.makeelement(item_node), 'id', 'example:namespace')); + l_departments_node := DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.MAKENODE(l_domdoc)); + item_node := DBMS_XMLDOM.GETFIRSTCHILD(l_departments_node); + dbms_output.put_line('item node: ' || DBMS_XMLDOM.GETNODENAME(item_node)); + dbms_output.put_line('item attr: ' || DBMS_XMLDOM.GETATTRIBUTE(DBMS_XMLDOM.MAKEELEMENT(item_node), 'id', 'example:namespace')); - dbms_xmldom.freeDocument(l_domdoc); + DBMS_XMLDOM.FREEDOCUMENT(l_domdoc); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getchildnodes.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getchildnodes.mdx index 9df6387b545..5d077558a0d 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getchildnodes.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getchildnodes.mdx @@ -2,7 +2,7 @@ title: "GETCHILDNODES" --- -The `GETCHILDNODES` function retrieves a DOMENODELIST that has all the children of the particular node. If no children are there, then the DOMENODELIST doesn't contain nodes. +The `GETCHILDNODES` function retrieves a `DOMNodeList` that has all the children of the particular node. If no children are there, then the `DOMNodeList` doesn't contain nodes. ``` GETCHILDNODES(n DOMNode) RETURN DOMNodeList @@ -12,40 +12,40 @@ GETCHILDNODES(n DOMNode) RETURN DOMNodeList `n` -The DOMNODE whose childnode list is to be retrieved. +The `DOMNode` whose childnode list is to be retrieved. ## Examples -This example executes a function named `func1` that creates the XML structure `Dept1` and returns the root node which is a DOMDocument. +This example executes a function named `func1` that creates the XML structure `Dept1` and returns the root node which is a `DOMDocument`. ```sql -CREATE OR REPLACE FUNCTION func1 RETURN dbms_xmldom.DOMNode IS - l_domdoc dbms_xmldom.DOMDocument; - l_root_node dbms_xmldom.DOMNode; - l_department_element dbms_xmldom.DOMElement; - l_departments_node dbms_xmldom.DOMNode; - l_name_text dbms_xmldom.DOMText; - l_name_textnode dbms_xmldom.DOMNode; +CREATE OR REPLACE FUNCTION func1 RETURN DBMS_XMLDOM.DOMNode IS + l_domdoc DBMS_XMLDOM.DOMDocument; + l_root_node DBMS_XMLDOM.DOMNode; + l_department_element DBMS_XMLDOM.DOMElement; + l_departments_node DBMS_XMLDOM.DOMNode; + l_name_text DBMS_XMLDOM.DOMText; + l_name_textnode DBMS_XMLDOM.DOMNode; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - l_root_node := dbms_xmldom.makeNode(l_domdoc); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - l_departments_node := dbms_xmldom.appendChild(l_root_node,dbms_xmldom.makeNode(l_department_element)); - l_name_text := dbms_xmldom.createTextNode(l_domdoc, 'Dept1' ); - PERFORM dbms_xmldom.appendChild(l_departments_node,dbms_xmldom.makeNode(l_name_text)); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + l_root_node := DBMS_XMLDOM.MAKENODE(l_domdoc); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + l_departments_node := DBMS_XMLDOM.APPENDCHILD(l_root_node,DBMS_XMLDOM.MAKENODE(l_department_element)); + l_name_text := DBMS_XMLDOM.CREATETEXTNODE(l_domdoc, 'Dept1' ); + PERFORM DBMS_XMLDOM.APPENDCHILD(l_departments_node,DBMS_XMLDOM.MAKENODE(l_name_text)); return l_root_node; END; ``` -You can retrieve all the child nodes of the root node by calling `getChildNodes`, and you can determine the number of child nodes using the `getLength` function: +You can retrieve all the child nodes of the root node by calling `GETCHILDNODES`, and you can determine the number of child nodes using the `GETLENGTH` function: ```sql DECLARE - clist dbms_xmldom.DOMNodeList; + clist DBMS_XMLDOM.DOMNodeList; len NUMBER; BEGIN - clist := dbms_xmldom.getChildNodes(func1()); - len := dbms_xmldom.getlength(clist); + clist := DBMS_XMLDOM.GETCHILDNODES(func1()); + len := DBMS_XMLDOM.GETLENGTH(clist); dbms_output.put_line('root node num children: ' || to_char(len)); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getfirstchild.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getfirstchild.mdx index 7e510b7ba1e..341c8ddf6c3 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getfirstchild.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getfirstchild.mdx @@ -5,31 +5,31 @@ title: "GETFIRSTCHILD" The `GETFIRSTCHILD` function retrieves the first child of the particular node. If there is no such node, then this function returns NULL. ``` -GETFIRSTCHILD(n DOMNODE) RETURN DOMNODE +GETFIRSTCHILD(n DOMNode) RETURN DOMNode ``` ## Parameters `n` -The DOMNODE whose first child needs to be retrieved. +The `DOMNode` whose first child needs to be retrieved. ## Examples -This example creates a new DOMDocument named `l_domdoc`, and turns it into a DOMNode. Then, it creates a DOMElement named `l_department_element` with the tag name “Departments” and appends this element as a child to the DOMNode. Finally, it outputs the tag name of the first (and in this example, the only) appended child. +This example creates a new `DOMDocument` named `l_domdoc`, and turns it into a `DOMNode`. Then, it creates a `DOMElement` named `l_department_element` with the tag name “Departments” and appends this element as a child to the `DOMNode`. Finally, it outputs the tag name of the first (and in this example, the only) appended child. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_root_node dbms_xmldom.DOMNode; - l_department_element dbms_xmldom.DOMElement; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_root_node DBMS_XMLDOM.DOMNode; + l_department_element DBMS_XMLDOM.DOMElement; BEGIN - l_domdoc := dbms_xmldom.NewDOMDocument(); - l_root_node := dbms_xmldom.makeNode(l_domdoc); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Deptartments' ); - PERFORM dbms_xmldom.appendChild(l_root_node,dbms_xmldom.makeNode(l_department_element)); - DBMS_OUTPUT.PUT_LINE(dbms_xmldom.getNodename(dbms_xmldom.getfirstChild(l_root_node))); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(); + l_root_node := DBMS_XMLDOM.MAKENODE(l_domdoc); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Deptartments' ); + PERFORM DBMS_XMLDOM.APPENDCHILD(l_root_node,DBMS_XMLDOM.MAKENODE(l_department_element)); + DBMS_OUTPUT.PUT_LINE(DBMS_XMLDOM.GETNODENAME(DBMS_XMLDOM.GETFIRSTCHILD(l_root_node))); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getlength.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getlength.mdx index 5728cdf95e6..1c4c16598d6 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getlength.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getlength.mdx @@ -2,50 +2,50 @@ title: "GETLENGTH" --- -The `GETLENGTH` function returns the number of nodes in a DOMNODELIST. +The `GETLENGTH` function returns the number of nodes in a `DOMNodeList`. ``` -GETLENGTH(nl DOMNODELIST) RETURN PLS_INTEGER +GETLENGTH(nl DOMNodeList) RETURN PLS_INTEGER ``` ## Parameters `nl` -The DOMENODELIST +The `DOMNodeList` ## Examples -This example executes a function named `func1` that creates the XML structure `Dept1` and returns the root node which is a DOMDocument. +This example executes a function named `func1` that creates the XML structure `Dept1` and returns the root node which is a `DOMDocument`. ```sql -CREATE OR REPLACE FUNCTION func1 RETURN dbms_xmldom.DOMNode IS - l_domdoc dbms_xmldom.DOMDocument; - l_root_node dbms_xmldom.DOMNode; - l_department_element dbms_xmldom.DOMElement; - l_departments_node dbms_xmldom.DOMNode; - l_name_text dbms_xmldom.DOMText; - l_name_textnode dbms_xmldom.DOMNode; +CREATE OR REPLACE FUNCTION func1 RETURN DBMS_XMLDOM.DOMNode IS + l_domdoc DBMS_XMLDOM.DOMDocument; + l_root_node DBMS_XMLDOM.DOMNode; + l_department_element DBMS_XMLDOM.DOMElement; + l_departments_node DBMS_XMLDOM.DOMNode; + l_name_text DBMS_XMLDOM.DOMText; + l_name_textnode DBMS_XMLDOM.DOMNode; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - l_root_node := dbms_xmldom.makeNode(l_domdoc); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Deptartments' ); - l_departments_node := dbms_xmldom.appendChild(l_root_node,dbms_xmldom.makeNode(l_department_element)); - l_name_text := dbms_xmldom.createTextNode(l_domdoc, 'Dept1' ); - PERFORM dbms_xmldom.appendChild(l_departments_node,dbms_xmldom.makeNode(l_name_text)); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + l_root_node := DBMS_XMLDOM.MAKENODE(l_domdoc); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Deptartments' ); + l_departments_node := DBMS_XMLDOM.APPENDCHILD(l_root_node,DBMS_XMLDOM.MAKENODE(l_department_element)); + l_name_text := DBMS_XMLDOM.CREATETEXTNODE(l_domdoc, 'Dept1' ); + PERFORM DBMS_XMLDOM.APPENDCHILD(l_departments_node,DBMS_XMLDOM.MAKENODE(l_name_text)); return l_root_node; END; ``` -You can retrieve all the child nodes of the root node by calling `getChildNodes`, and you can determine the number of child nodes using the `getLength` function: +You can retrieve all the child nodes of the root node by calling `GETCHILDNODES`, and you can determine the number of child nodes using the `GETLENGTH` function: ```sql DECLARE - clist dbms_xmldom.DOMNodeList; + clist DBMS_XMLDOM.DOMNodeList; len NUMBER; BEGIN - clist := dbms_xmldom.getChildNodes(func1()); - len := dbms_xmldom.getlength(clist); + clist := DBMS_XMLDOM.GETCHILDNODES(func1()); + len := DBMS_XMLDOM.GETLENGTH(clist); dbms_output.put_line('root node num children: ' || to_char(len)); END; ``` diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodename.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodename.mdx index b02326231f5..174f0ba38ae 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodename.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodename.mdx @@ -12,21 +12,21 @@ GETNODENAME(n DOMNODE) RETURN VARCHAR2 `n` -DOMNODE value to be provided +`DOMNode` value to be provided. ## Examples -This example creates a new DOMDocument named `l_domdoc`, and a DOMElement named `elem` with tag name “Departments”. Finally, it outputs the tag name. +This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. Finally, it outputs the tag name. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_department_element dbms_xmldom.DOMElement; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_department_element DBMS_XMLDOM.DOMElement; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - dbms_output.put_line(dbms_xmldom.getnodename(dbms_xmldom.makeNode(l_department_element))); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + dbms_output.put_line(DBMS_XMLDOM.GETNODENAME(DBMS_XMLDOM.MAKENODE(l_department_element))); END; ``` diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodevalue.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodevalue.mdx index 8129ac155d3..75827faedec 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodevalue.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getnodevalue.mdx @@ -5,29 +5,29 @@ title: "GETNODEVALUE" The `GETNODEVALUE` function provides the value of the node depending on its type. ``` -GETNODEVALUE(n DOMNODE) RETURN VARCHAR2 +GETNODEVALUE(n DOMNode) RETURN VARCHAR2 ``` ## Parameters `n` -DOMNODE to be provided +`DOMNode` to be provided. ## Examples -This example creates a new DOMDocument named `l_domdoc`, and a text node with tag name “Depts list”. Finally, it outputs the text node value in XML it set before. +This example creates a new `DOMDocument` named `l_domdoc`, and a text node with tag name “Depts list”. Finally, it outputs the text node value in XML it set before. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_name_text dbms_xmldom.DOMText; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_name_text DBMS_XMLDOM.DOMText; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - l_name_text := dbms_xmldom.createTextNode(l_domdoc, 'Depts list' ); - dbms_output.put_line(dbms_xmldom.getnodevalue(dbms_xmldom.makeNode(l_name_text))); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + l_name_text := DBMS_XMLDOM.CREATETEXTNODE(l_domdoc, 'Depts list' ); + dbms_output.put_line(DBMS_XMLDOM.GETNODEVALUE(DBMS_XMLDOM.MAKENODE(l_name_text))); END; ``` diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getxmltype.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getxmltype.mdx index c8b9f73a792..8c9b8557674 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getxmltype.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getxmltype.mdx @@ -2,7 +2,7 @@ title: "GETXMLTYPE" --- -The `GETXMLTYPE` function converts a DOMDOCUMENT to XMLTYPE and returns it. +The `GETXMLTYPE` function converts a `DOMDocument` to XMLTYPE and returns it. ``` GETXMLTYPE(doc IN DOMDOCUMENT) RETURN XMLTYPE @@ -12,39 +12,39 @@ GETXMLTYPE(doc IN DOMDOCUMENT) RETURN XMLTYPE `doc` -The DOMDOCUMENT +The `DOMDocument`. ## Examples -This example creates a new XML DOMDocument, sets the version to 1.0, and converts it into an XMLType object. +This example creates a new XML `DOMDocument`, sets the version to 1.0, and converts it into an XMLType object. ```sql DECLARE l_xmltype XMLTYPE; - l_domdoc dbms_xmldom.DOMDocument; + l_domdoc DBMS_XMLDOM.DOMDocument; BEGIN - l_domdoc := dbms_xmldom.NewDOMDocument(); - dbms_xmldom.setversion(l_domdoc, '1.0'); - l_xmltype := dbms_xmldom.getXmlType(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(); + DBMS_XMLDOM.SETVERSION(l_domdoc, '1.0'); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); DBMS_OUTPUT.PUT_LINE(l_xmltype.getStringVal()); END; ``` -This example takes an xml string as input, converts it into a DOMDocument, and adds a new element to the document. It then converts the DOMDocument back to XMLType. +This example takes an xml string as input, converts it into a `DOMDocument`, and adds a new element to the document. It then converts the `DOMDocument` back to `XMLType`. ```sql DECLARE - doc dbms_xmldom.domdocument; + doc DBMS_XMLDOM.domdocument; xmldata xmltype:=xmltype('1020'); l_xmltype XMLTYPE; - elem dbms_xmldom.DOMElement; + elem DBMS_XMLDOM.DOMElement; BEGIN - doc := dbms_xmldom.newdomdocument(xmldata); - elem := dbms_xmldom.createElement(doc, 'testTag'); - PERFORM dbms_xmldom.appendChild(dbms_xmldom.makeNode(doc), dbms_xmldom.makeNode(elem)); - l_xmltype := dbms_xmldom.getXmlType(doc); + doc := DBMS_XMLDOM.NEWDOMDOCUMENT(xmldata); + elem := DBMS_XMLDOM.CREATEELEMENT(doc, 'testTag'); + PERFORM DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(doc), DBMS_XMLDOM.MAKENODE(elem)); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(doc); DBMS_OUTPUT.PUT_LINE(l_xmltype::varchar2); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx index 5c13d59fc2e..8d97298b912 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx @@ -28,8 +28,8 @@ EDB Postgres Advanced Server's implementation of `DBMS_XMLDOM` is a partial impl These are some guidelines for the usage of the `DBMS_XMLDOM` subprogram: -- The `makeNode` function supports DOM element types only (`DOMDocument`, `DOMElement`, `DOMText`, etc.). -- A `DOMDocument` accepts assigned DOMElement types only, otherwise an error is thrown. +- The `MAKENODE` function supports DOM element types only (`DOMDocument`, `DOMElement`, `DOMText`, etc.). +- A `DOMDocument` accepts assigned `DOMElement` types only, otherwise an error is thrown. - `DBMS_XMLDOM` accepts only unicode characters in the HTML or XML file. - You can call methods on NULL objects. - You cannot assign documents that are freed. @@ -56,25 +56,25 @@ The `DBMS_XMLDOM` package implements the following types: This table lists the subprograms available with `DBMS_XMLDOM` package: -| Subprogram | Type | Return type | Description | -|------------------|-----------|-------------|-------------------------------------------------------------------------------| -| `appendChild` | Function | DOMNODE | Appends a new child to the node | -| `createElement` | Function | DOMELEMENT | Creates a new element | -| `createTextNode` | Function | DOMTEXT | Creates a text node | -| `freeDocument` | Procedure | N/A | Frees the resources associated with the DOMDocument | -| `getAttribute` | Function | DOMELEMENT | Retrieves the attribute value given to an attribute name and returns VARCHAR2 | -| `getChildNodes` | Function | DOMNODELIST | Retrieves the children of the node | -| `getFirstChild` | Function | DOMNODE | Retrieves the first child of the node | -| `getLength` | Function | PLS_INTEGER | Retrieves the number of items in the given DOMNODELIST | -| `getNodeName` | Function | VARCHAR2 | Retrieves the name of the node | -| `getNodeValue` | Function | VARCHAR2 | Retrieves the value of the node | -| `getxmltype` | Function | XMLTYPE | Converts DOMDocument to xmltype and returns it | -| `item` | Function | DOMNODE | Retrieves the item from the given the index in the NODELIST | -| `makeElement` | Function | DOMELEMENT | Casts the node to a DOMELEMENT | -| `makeNode` | Function | DOMNODE | Casts the attribute to a node | -| `newDOMDcoument` | Function | DOMDOCUMENT | Creates a new document | -| `setAttribute` | Procedure | N/A | Sets the attribute value of a DOMElement | -| `setVersion` | Procedure | N/A | Sets the version of the document | +| Subprogram | Type | Return type | Description | +|------------------|-----------|-------------|--------------------------------------------------------------------------------| +| `APPENDCHILD` | Function | DOMNode | Appends a new child to the node. | +| `CREATEELEMENT` | Function | DOMElement | Creates a new element. | +| `CREATETEXTNODE` | Function | DOMText | Creates a text node. | +| `FREEDOCUMENT` | Procedure | N/A | Frees the resources associated with the DOMDocument. | +| `GETATTRIBUTE` | Function | DOMElement | Retrieves the attribute value given to an attribute name and returns VARCHAR2. | +| `GETCHILDNODES` | Function | DOMNodeList | Retrieves the children of the node. | +| `GETFIRSTCHILD` | Function | DOMNode | Retrieves the first child of the node. | +| `GETLENGTH` | Function | PLS_INTEGER | Retrieves the number of items in the given DOMNodeList. | +| `GETNODENAME` | Function | VARCHAR2 | Retrieves the name of the node. | +| `GETNODEVALUE` | Function | VARCHAR2 | Retrieves the value of the node. | +| `GETXMLTYPE` | Function | XMLTYPE | Converts DOMDocument to xmltype and returns it. | +| `ITEM` | Function | DOMNode | Retrieves the item from the given the index in the NODELIST. | +| `MAKEELEMENT` | Function | DOMElement | Casts the node to a DOMElement. | +| `MAKENODE` | Function | DOMNode | Casts the attribute to a node. | +| `NEWDOMDOCUMENT` | Function | DOMDocument | Creates a new document. | +| `SETATTRIBUTE` | Procedure | N/A | Sets the attribute value of a DOMElement. | +| `SETVERSION` | Procedure | N/A | Sets the version of the document. | diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/item.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/item.mdx index e2becee172c..51ca627d4e8 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/item.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/item.mdx @@ -5,14 +5,14 @@ title: "ITEM" The `ITEM` function returns the item in the collection corresponding to the `idx` parameter. If the value of `idx` parameter is greater than or equal to the number of nodes in the list, then function returns a `NULL`. ``` -ITEM(nl DOMNODELIST, idx IN PLS_INTEGER) RETURN DOMNODE +ITEM(nl DOMNodeList, idx IN PLS_INTEGER) RETURN DOMNode ``` ## Parameters `nl` -The DOMNODELIST, the number of nodes in the list. +The DOMNodeList, the number of nodes in the list. `idx` @@ -23,33 +23,33 @@ The index in the NODELIST that is used to retrieve the item. This example uses a function named `func1` that creates an XML structure `Dept1` and returns the document node that is the root node. ```sql -CREATE OR REPLACE FUNCTION func1 RETURN dbms_xmldom.DOMNode IS - l_domdoc dbms_xmldom.DOMDocument; - l_root_node dbms_xmldom.DOMNode; - l_department_element dbms_xmldom.DOMElement; - l_departments_node dbms_xmldom.DOMNode; - l_name_text dbms_xmldom.DOMText; - l_name_textnode dbms_xmldom.DOMNode; +CREATE OR REPLACE FUNCTION func1 RETURN DBMS_XMLDOM.DOMNode IS + l_domdoc DBMS_XMLDOM.DOMDocument; + l_root_node DBMS_XMLDOM.DOMNode; + l_department_element DBMS_XMLDOM.DOMElement; + l_departments_node DBMS_XMLDOM.DOMNode; + l_name_text DBMS_XMLDOM.DOMText; + l_name_textnode DBMS_XMLDOM.DOMNode; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - l_root_node := dbms_xmldom.makeNode(l_domdoc); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Deptartments' ); - l_departments_node := dbms_xmldom.appendChild(l_root_node,dbms_xmldom.makeNode(l_department_element)); - l_name_text := dbms_xmldom.createTextNode(l_domdoc, 'Dept1' ); - PERFORM dbms_xmldom.appendChild(l_departments_node,dbms_xmldom.makeNode(l_name_text)); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + l_root_node := DBMS_XMLDOM.MAKENODE(l_domdoc); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Deptartments' ); + l_departments_node := DBMS_XMLDOM.APPENDCHILD(l_root_node,DBMS_XMLDOM.MAKENODE(l_department_element)); + l_name_text := DBMS_XMLDOM.CREATETEXTNODE(l_domdoc, 'Dept1' ); + PERFORM DBMS_XMLDOM.APPENDCHILD(l_departments_node,DBMS_XMLDOM.MAKENODE(l_name_text)); return l_root_node; END; ``` -The document node is passed to `getChildNodes` using the function `func1`, which returns the list of children of the document node. The list contains the `DOMElement` representing "Departments". The call to item returns this element as a `DOMNode`, which is then picked by `getnodename` to fetch the tag name of this `DOMElement`. +The document node is passed to `GETCHILDNODES` using the function `func1`, which returns the list of children of the document node. The list contains the `DOMElement` representing "Departments". The call to item returns this element as a `DOMNode`, which is then picked by `GETNODENAME` to fetch the tag name of this `DOMElement`. ```sql DECLARE - clist dbms_xmldom.DOMNodeList; - l_node dbms_xmldom.DOMNode; + clist DBMS_XMLDOM.DOMNodeList; + l_node DBMS_XMLDOM.DOMNode; BEGIN - clist := dbms_xmldom.getChildNodes(func1()); - l_node := dbms_xmldom.item(clist, 0); - dbms_output.put_line(dbms_xmldom.getnodename(l_node)); + clist := DBMS_XMLDOM.GETCHILDNODES(func1()); + l_node := DBMS_XMLDOM.ITEM(clist, 0); + dbms_output.put_line(DBMS_XMLDOM.GETNODENAME(l_node)); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx index 8e6f8263498..ca68c41da82 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx @@ -2,39 +2,39 @@ title: "MAKEELEMENT" --- -The `MAKEELEMENT` function converts a specified DOMNODE into a DOMELEMENT and returns it. +The `MAKEELEMENT` function converts a specified `DOMNode` into a `DOMElement` and returns it. -`MAKEELEMENT` can only convert a DOMNODE that originates from a DOMELEMENT. If the DOMNODE originates from a different type, like a DOMTEXT, running `MAKEELEMENT` results in failure. +`MAKEELEMENT` can only convert a `DOMNode` that originates from a `DOMElement`. If the `DOMNode` originates from a different type, like a `DOMText`, running `MAKEELEMENT` results in failure. ``` -MAKEELEMENT(n DOMNODE) RETURN DOMELEMENT +MAKEELEMENT(n DOMNode) RETURN DOMElement ``` ## Parameters `n` -Value of the DOMNODE to convert. +Value of the `DOMNode` to convert. ## Examples -This example defines a namespace named “example” and uses an XMLtype string to create an XML structure. `GETFIRSTCHILD` then returns a `DOMNODE` that represents a `DOMELEMENT`. Since `GETATTRIBUTE` expects a `DOMELEMENT`, the `MAKEELEMENT` function converts a specified `DOMNODE` into a `DOMELEMENT` and returns it. +This example defines a namespace named “example” and uses an XMLtype string to create an XML structure. `GETFIRSTCHILD` then returns a `DOMNode` that represents a `DOMElement`. Since `GETATTRIBUTE` expects a `DOMElement`, the `MAKEELEMENT` function converts a specified `DOMNode` into a `DOMElement` and returns it. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_departments_node dbms_xmldom.DOMNode; - item_node dbms_xmldom.DOMNode; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_departments_node DBMS_XMLDOM.DOMNode; + item_node DBMS_XMLDOM.DOMNode; BEGIN - l_domdoc := dbms_xmldom.newDOMDocument(XMLTYPE('')); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(XMLTYPE('')); - l_departments_node := DBMS_XMLDOM.getfirstchild(dbms_xmldom.makeNode(l_domdoc)); - item_node := dbms_xmldom.getfirstchild(l_departments_node); - dbms_output.put_line('item node: ' || dbms_xmldom.getnodename(item_node)); - dbms_output.put_line('item attr: ' || dbms_xmldom.getattribute(dbms_xmldom.makeelement(item_node), 'id', 'example:namespace')); + l_departments_node := DBMS_XMLDOM.GETFIRSTCHILD(DBMS_XMLDOM.MAKENODE(l_domdoc)); + item_node := DBMS_XMLDOM.GETFIRSTCHILD(l_departments_node); + dbms_output.put_line('item node: ' || DBMS_XMLDOM.GETNODENAME(item_node)); + dbms_output.put_line('item attr: ' || DBMS_XMLDOM.GETATTRIBUTE(DBMS_XMLDOM.MAKEELEMENT(item_node), 'id', 'example:namespace')); - dbms_xmldom.freeDocument(l_domdoc); + DBMS_XMLDOM.FREEDOCUMENT(l_domdoc); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx index a88374d02b1..b98f76a0f4a 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx @@ -2,54 +2,54 @@ title: "MAKENODE" --- -The `MAKENODE` function accepts different types of values and returns the DOMNODE. +The `MAKENODE` function accepts different types of values and returns the `DOMNode`. ``` -MAKENODE(doc DOMDOCUMENT) RETURN DOMNODE +MAKENODE(doc DOMDocument) RETURN DOMNode -MAKENODE(elem DOMELEMENT) RETURN DOMNODE +MAKENODE(elem DOMElement) RETURN DOMNode -MAKENODE(t DOMTEXT) RETURN DOMNODE +MAKENODE(t DOMText) RETURN DOMNode ``` ## Parameters `doc` -The DOMDOCUMENT to be casted +The `DOMDocument` to be casted. `elem` -The `DOMELEMENT` to be casted +The `DOMElement` to be casted. `t` -The `DOMTEXT` to be casted +The `DOMText` to be casted. ## Examples You can turn a `DOMDocument`, `DOMElement` and `DOMText` to a `DOMNode`. -This example creates a new XML DOMDocument, and turns it into a DOMNode so it can be root. Then, it creates a DOMElement with tag name “Departments”, turns it into a node and appends it to the DOMDocument. It then creates a text node DOMNode with tag name “Depts list” and appends it as a child to the DOMElement node. +This example creates a new XML DOMDocument, and turns it into a `DOMNode` so it can be root. Then, it creates a `DOMElement` with tag name “Departments”, turns it into a node and appends it to the `DOMElement`. It then creates a text node `DOMNode` with tag name “Depts list” and appends it as a child to the `DOMElement` node. ```sql DECLARE - l_domdoc dbms_xmldom.DOMDocument; - l_root_node dbms_xmldom.DOMNode; - l_department_element dbms_xmldom.DOMElement; - l_departments_node dbms_xmldom.DOMNode; - l_name_text dbms_xmldom.DOMText; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_root_node DBMS_XMLDOM.DOMNode; + l_department_element DBMS_XMLDOM.DOMElement; + l_departments_node DBMS_XMLDOM.DOMNode; + l_name_text DBMS_XMLDOM.DOMText; l_xmltype XMLTYPE; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - l_root_node := dbms_xmldom.makeNode(l_domdoc); - l_department_element := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - l_departments_node := dbms_xmldom.appendChild(l_root_node,dbms_xmldom.makeNode(l_department_element)); - l_name_text := dbms_xmldom.createTextNode(l_domdoc, 'Depts list' ); - PERFORM dbms_xmldom.appendChild(l_departments_node,dbms_xmldom.makeNode(l_name_text)); - l_xmltype := dbms_xmldom.getXmlType(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + l_root_node := DBMS_XMLDOM.MAKENODE(l_domdoc); + l_department_element := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + l_departments_node := DBMS_XMLDOM.APPENDCHILD(l_root_node,DBMS_XMLDOM.makeNode(l_department_element)); + l_name_text := DBMS_XMLDOM.CREATETEXTNODE(l_domdoc, 'Depts list' ); + PERFORM DBMS_XMLDOM.APPENDCHILD(l_departments_node,DBMS_XMLDOM.MAKENODE(l_name_text)); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); DBMS_OUTPUT.PUT_LINE(l_xmltype.getStringVal()); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/newdomdocument.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/newdomdocument.mdx index b334076a5b9..1c84ed519b3 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/newdomdocument.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/newdomdocument.mdx @@ -3,54 +3,54 @@ title: "NEWDOMDOCUMENT" --- -The `NEWDOMDOCUMENT` function accepts XMLTYPE or CLOB type as input and returns the DOMDOCUMENT type. You can also create an empty DOMDOCUMENT. +The `NEWDOMDOCUMENT` function accepts XMLTYPE or CLOB type as input and returns the `DOMDocument` type. You can also create an empty `DOMDocument`. ``` -NEWDOMDOCUMENT RETURN DOMDOCUMENT +NEWDOMDOCUMENT RETURN DOMDocument -NEWDOMDOCUMENT(xmldoc IN XMLTYPE) RETURN DOMDOCUMENT; +NEWDOMDOCUMENT(xmldoc IN XMLTYPE) RETURN DOMDocument; -NEWDOMDOCUMENT (cl IN CLOB) RETURN DOMDOCUMENT; +NEWDOMDOCUMENT (cl IN CLOB) RETURN DOMDocument; ``` ## Parameters `xmldoc` -It is the `XMLTYPE` of source for the DOMDOCUMENT. +It is the `XMLTYPE` of source for the `DOMDocument`. `cl` -It is the `CLOB` source for the DOMDOCUMENT. +It is the `CLOB` source for the `DOMDocument`. ## Example -This example creates a new XML DOMDocument, sets the version to 1.0, and converts it into an XMLType object. +This example creates a new XML `DOMDocument`, sets the version to 1.0, and converts it into an XMLType object. ```sql DECLARE l_xmltype XMLTYPE; - l_domdoc dbms_xmldom.DOMDocument; + l_domdoc DBMS_XMLDOM.DOMDocument; BEGIN - l_domdoc := dbms_xmldom.NewDOMDocument(); - dbms_xmldom.setversion(l_domdoc, '1.0'); - l_xmltype := dbms_xmldom.getXmlType(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(); + DBMS_XMLDOM.SETVERSION(l_domdoc, '1.0'); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); DBMS_OUTPUT.PUT_LINE(l_xmltype.getStringVal()); END; ``` -This example takes an XMLType object, converts it into a DOMDocument, and then back to a XMLType. +This example takes an XMLType object, converts it into a `DOMDocument`, and then back to a XMLType. ```sql DECLARE - doc dbms_xmldom.domdocument; + doc DBMS_XMLDOM.DOMDocument; xmldata xmltype:=xmltype('1020'); l_xmltype XMLTYPE; BEGIN - doc := dbms_xmldom.newdomdocument(xmldata); - l_xmltype := dbms_xmldom.getXmlType(doc); + doc := DBMS_XMLDOM.NEWDOMDOCUMENT(xmldata); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(doc); DBMS_OUTPUT.PUT_LINE(l_xmltype::varchar2); diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx index 2c56eda10ba..3c6df83a58d 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx @@ -2,17 +2,17 @@ title: "SETATTRIBUTE" --- -The `SETATTRIBUTE` procedure sets the value of a DOMELEMENT's attribute by name. +The `SETATTRIBUTE` procedure sets the value of a `DOMElement`'s attribute by name. ``` -SETATTRIBUTE(elem DOMELEMENT, name IN VARCHAR2, newvalue IN VARCHAR2) +SETATTRIBUTE(elem DOMElement, name IN VARCHAR2, newvalue IN VARCHAR2) ``` ## Parameters `elem` -The DOMELEMENT whose attribute is to be set. +The `DOMElement` whose attribute is to be set. `name` @@ -24,20 +24,20 @@ Attribute value to be set. ## Examples -This example creates a new DOMDocument named `l_domdoc`, and a DOMElement named `elem` with tag name “Departments”. It then adds an attribute to the DOMElement named ‘value’. The example turns both `l_domdoc` and `elem` to DOMNodes to append `elem` as a child of `l_domdoc`. Finally, it converts `l_domdoc` to `XMLType`. +This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It then adds an attribute to the `DOMElement` named ‘value’. The example turns both `l_domdoc` and `elem` to `DOMNodes` to append `elem` as a child of `l_domdoc`. Finally, it converts `l_domdoc` to `XMLType`. ```sql DECLARE l_xml xmltype; - l_domdoc dbms_xmldom.DOMDocument; - l_departments_node dbms_xmldom.DOMNode; - elem dbms_xmldom.DOMElement; + l_domdoc DBMS_XMLDOM.DOMDocument; + l_departments_node DBMS_XMLDOM.DOMNode; + elem DBMS_XMLDOM.DOMElement; BEGIN - l_domdoc := dbms_xmldom.newDomDocument; - elem := dbms_xmldom.createElement(l_domdoc, 'Departments' ); - dbms_xmldom.setAttribute(elem, 'attr', 'value'); - PERFORM dbms_xmldom.appendchild(dbms_xmldom.makeNode(l_domdoc), dbms_xmldom.makeNode(elem)); - l_xml := dbms_xmldom.getxmltype(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT; + elem := DBMS_XMLDOM.CREATEELEMENT(l_domdoc, 'Departments' ); + DBMS_XMLDOM.SETATTRIBUTE(elem, 'attr', 'value'); + PERFORM DBMS_XMLDOM.APPENDCHILD(DBMS_XMLDOM.MAKENODE(l_domdoc), DBMS_XMLDOM.MAKENODE(elem)); + l_xml := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); dbms_output.put_line(l_xml.getStringVal()); END; ``` \ No newline at end of file diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setversion.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setversion.mdx index 33ccac022d8..e2a37fb349f 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setversion.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setversion.mdx @@ -2,36 +2,36 @@ title: "SETVERSION" --- -The `SETVERSION` procedure is used to set the version of the DOMDOCUMENT. +The `SETVERSION` procedure is used to set the version of the `DOMDocument`. ``` -SETVERSION(doc DOMDOCUMENT, v VARCHAR2) +SETVERSION(doc DOMDocument, v VARCHAR2) ``` ## Parameters `doc` -Any DOMDOCUMENT +Any `DOMDocument`. `v` -The version of the document +The version of the document. ## Examples -This example creates a new XML DOMDocument, sets the version to 1.0, and converts it into an XMLType object. +This example creates a new XML `DOMDocument`, sets the version to 1.0, and converts it into an XMLType object. ```sql DECLARE l_xmltype XMLTYPE; - l_domdoc dbms_xmldom.DOMDocument; + l_domdoc DBMS_XMLDOM.DOMDocument; BEGIN - l_domdoc := dbms_xmldom.NewDOMDocument(); - dbms_xmldom.setversion(l_domdoc, '1.0'); - l_xmltype := dbms_xmldom.getXmlType(l_domdoc); + l_domdoc := DBMS_XMLDOM.NEWDOMDOCUMENT(); + DBMS_XMLDOM.setversion(l_domdoc, '1.0'); + l_xmltype := DBMS_XMLDOM.GETXMLTYPE(l_domdoc); DBMS_OUTPUT.PUT_LINE(l_xmltype.getStringVal()); END; ``` From 0ac128ad8e6efe567e00660df6c93bcb32a0a1de Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Thu, 28 Nov 2024 13:16:20 +0100 Subject: [PATCH 63/65] streamlining subprogram example descriptions --- .../18_dbms_xmldom/appendchild.mdx | 4 +++- .../18_dbms_xmldom/createelement.mdx | 2 +- .../18_dbms_xmldom/getattribute.mdx | 2 +- .../18_dbms_xmldom/index.mdx | 18 +----------------- .../18_dbms_xmldom/makeelement.mdx | 4 ++++ .../18_dbms_xmldom/makenode.mdx | 4 ++++ .../18_dbms_xmldom/setattribute.mdx | 2 +- 7 files changed, 15 insertions(+), 21 deletions(-) diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx index 1ee2892e1a9..0a702982c69 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx @@ -4,6 +4,8 @@ title: "APPENDCHILD" The `APPENDCHILD` function adds the node at the end of the list of children of a particular node. It returns the newly added node and if the node is already present, it removes the existing node before adding new node. +You can append more than one child to a document node. + ``` APPENDCHILD(n DOMNode, newChild IN DOMNode) RETURN DOMNode ``` @@ -20,7 +22,7 @@ The child node to be added to the existing list of children of node n. ## Examples -This example creates a new XML DOMDocument named `l_domdoc` and a new DOMElement named `l_department_element` with tag name `Departments`. It then converts `l_domdoc` and `l_department_element` into DOMNodes, so `l_department_element` can be appended as a child to `l_domdoc`. +This example creates a new XML `DOMDocument` named `l_domdoc` and a new `DOMElement` named `l_department_element` with tag name `Departments`. It then appends the `DOMElement` as a child of the `DOMDocument`. ```sql DECLARE diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx index b6867947919..c55cff033b4 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx @@ -20,7 +20,7 @@ Tag name to be given to the new `DOMDocument`. ## Examples -This example creates a new XML DOMDocument named `l_domdoc` and a new DOMElement named `l_department_element` with tag name `Departments`. It then appends the DOMElement as a child of the DOMDocument. +This example creates a new XML `DOMDocument` named `l_domdoc` and a new `DOMElement` named `l_department_element` with tag name `Departments`. It then appends the `DOMElement` as a child of the `DOMDocument`. ```sql DECLARE diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx index f7b07d85085..cdbf4b28a1c 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx @@ -26,7 +26,7 @@ The namespace URI. ## Examples -This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It then adds an attribute to the `DOMElement` named ‘value’. The example turns both `l_domdoc` and `elem` to `DOMNodes` to append `elem` as a child of `l_domdoc`. Finally, it converts `l_domdoc` to `XMLType`. +This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It adds an attribute to the `DOMElement` named "value" and appends the `DOMElement` as a child of the `DOMDocument`. Finally, it converts the `DOMDocument` to `XMLType`. The `get` subprogram returns the value of the attribute `attr` of the "Departments" element. diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx index 8d97298b912..033e5146a26 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx @@ -20,26 +20,10 @@ navigation: - setversion --- -The `DBMS_XMLDOM` package is mainly used to access the `XMLType` objects. It provides an application programming interface for HTML and XML documents as an Document Object Model (DOM). This package is specially designed to work like any other DOM interfaces. +The `DBMS_XMLDOM` package implements Document Object Model (DOM) and is used to create DOM documents from scratch or from an `XMLType` object. EDB Postgres Advanced Server's implementation of `DBMS_XMLDOM` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in this table are supported. -## Guidelines - -These are some guidelines for the usage of the `DBMS_XMLDOM` subprogram: - -- The `MAKENODE` function supports DOM element types only (`DOMDocument`, `DOMElement`, `DOMText`, etc.). -- A `DOMDocument` accepts assigned `DOMElement` types only, otherwise an error is thrown. -- `DBMS_XMLDOM` accepts only unicode characters in the HTML or XML file. -- You can call methods on NULL objects. -- You cannot assign documents that are freed. -- Nodes: - - You can append more than one child to a document node. - - A node cannot belong to several documents. -- Elements: - - When an element is added twice, only the latest is considered. - - You cannot add an element to itself. - ## Types The `DBMS_XMLDOM` package implements the following types: diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx index ca68c41da82..e64382f1651 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx @@ -6,6 +6,10 @@ The `MAKEELEMENT` function converts a specified `DOMNode` into a `DOMElement` an `MAKEELEMENT` can only convert a `DOMNode` that originates from a `DOMElement`. If the `DOMNode` originates from a different type, like a `DOMText`, running `MAKEELEMENT` results in failure. +When the same element is added twice, only the latest is considered. + +You cannot add an element to itself. + ``` MAKEELEMENT(n DOMNode) RETURN DOMElement ``` diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx index b98f76a0f4a..a839abf3d63 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx @@ -4,6 +4,10 @@ title: "MAKENODE" The `MAKENODE` function accepts different types of values and returns the `DOMNode`. +You can append more than one child to a document node. + +A node cannot belong to several documents. + ``` MAKENODE(doc DOMDocument) RETURN DOMNode diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx index 3c6df83a58d..e845690bcbf 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx @@ -24,7 +24,7 @@ Attribute value to be set. ## Examples -This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It then adds an attribute to the `DOMElement` named ‘value’. The example turns both `l_domdoc` and `elem` to `DOMNodes` to append `elem` as a child of `l_domdoc`. Finally, it converts `l_domdoc` to `XMLType`. +This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It adds an attribute to the `DOMElement` named "value" and appends the `DOMElement` as a child of the `DOMDocument`. Finally, it converts the `DOMDocument` to `XMLType`. ```sql DECLARE From c209a38a8c4fe40444a9dd4b1c30b73cc542aa77 Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Mon, 2 Dec 2024 10:32:51 +0100 Subject: [PATCH 64/65] Implemented feedback from Sravan 02.12 --- .../03_built-in_packages/18_dbms_xmldom/appendchild.mdx | 4 +++- .../03_built-in_packages/18_dbms_xmldom/getattribute.mdx | 2 +- .../03_built-in_packages/18_dbms_xmldom/index.mdx | 2 +- .../03_built-in_packages/18_dbms_xmldom/makeelement.mdx | 3 --- .../03_built-in_packages/18_dbms_xmldom/makenode.mdx | 4 ---- .../03_built-in_packages/18_dbms_xmldom/setattribute.mdx | 2 +- 6 files changed, 6 insertions(+), 11 deletions(-) diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx index 0a702982c69..0df6f7c10fa 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/appendchild.mdx @@ -4,7 +4,9 @@ title: "APPENDCHILD" The `APPENDCHILD` function adds the node at the end of the list of children of a particular node. It returns the newly added node and if the node is already present, it removes the existing node before adding new node. -You can append more than one child to a document node. +You can append more than one child to a document node. However, a node cannot belong to several documents. + +When appending elements, you cannot add an element to itself. Additionally, if the same element is added twice, only the latest is considered. ``` APPENDCHILD(n DOMNode, newChild IN DOMNode) RETURN DOMNode diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx index cdbf4b28a1c..36d11fada63 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx @@ -26,7 +26,7 @@ The namespace URI. ## Examples -This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It adds an attribute to the `DOMElement` named "value" and appends the `DOMElement` as a child of the `DOMDocument`. Finally, it converts the `DOMDocument` to `XMLType`. +This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It adds an attribute (`attr`) to the `DOMElement` with the value "value" and appends the `DOMElement` as a child of the `DOMDocument`. The `get` subprogram returns the value of the attribute `attr` of the "Departments" element. diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx index 033e5146a26..74423e0aa8c 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/index.mdx @@ -20,7 +20,7 @@ navigation: - setversion --- -The `DBMS_XMLDOM` package implements Document Object Model (DOM) and is used to create DOM documents from scratch or from an `XMLType` object. +The `DBMS_XMLDOM` package implements Document Object Model (DOM) and is used to create DOM documents from scratch or from an XML document. EDB Postgres Advanced Server's implementation of `DBMS_XMLDOM` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in this table are supported. diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx index e64382f1651..6b3d60430d0 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makeelement.mdx @@ -6,9 +6,6 @@ The `MAKEELEMENT` function converts a specified `DOMNode` into a `DOMElement` an `MAKEELEMENT` can only convert a `DOMNode` that originates from a `DOMElement`. If the `DOMNode` originates from a different type, like a `DOMText`, running `MAKEELEMENT` results in failure. -When the same element is added twice, only the latest is considered. - -You cannot add an element to itself. ``` MAKEELEMENT(n DOMNode) RETURN DOMElement diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx index a839abf3d63..b98f76a0f4a 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/makenode.mdx @@ -4,10 +4,6 @@ title: "MAKENODE" The `MAKENODE` function accepts different types of values and returns the `DOMNode`. -You can append more than one child to a document node. - -A node cannot belong to several documents. - ``` MAKENODE(doc DOMDocument) RETURN DOMNode diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx index e845690bcbf..e18419aac09 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/setattribute.mdx @@ -24,7 +24,7 @@ Attribute value to be set. ## Examples -This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It adds an attribute to the `DOMElement` named "value" and appends the `DOMElement` as a child of the `DOMDocument`. Finally, it converts the `DOMDocument` to `XMLType`. +This example creates a new `DOMDocument` named `l_domdoc`, and a `DOMElement` named `elem` with tag name “Departments”. It adds an attribute (`attr`) to the `DOMElement` with the value "value" and appends the `DOMElement` as a child of the `DOMDocument`. ```sql DECLARE From 1605e4f265ed2547183b2859c89494bf30212a8a Mon Sep 17 00:00:00 2001 From: gvasquezvargas Date: Tue, 3 Dec 2024 08:43:16 +0100 Subject: [PATCH 65/65] Wording improvements in getattribute and createelement --- .../03_built-in_packages/18_dbms_xmldom/createelement.mdx | 2 +- .../03_built-in_packages/18_dbms_xmldom/getattribute.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx index c55cff033b4..3afe26dcb57 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/createelement.mdx @@ -16,7 +16,7 @@ Any `DOMDocument`. `tagname` -Tag name to be given to the new `DOMDocument`. +Tag name to be given to the new `DOMElement`. ## Examples diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx index 36d11fada63..ba9e5bb0f8b 100644 --- a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx +++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_xmldom/getattribute.mdx @@ -14,11 +14,11 @@ GETATTRIBUTE(elem DOMElement, name IN VARCHAR2, ns IN VARCHAR2) RETURN VARCHAR2 `elem` -The `DOMElement` whose attribute needs to be obtained. +The `DOMElement` whose attribute value needs to be obtained. `name` -The attribute name which needs to be obtained. +The attribute name whose attribute value needs to be obtained. `ns`