diff --git a/install_template/config.yaml b/install_template/config.yaml
index d67cab3420b..3d51e7d3e55 100644
--- a/install_template/config.yaml
+++ b/install_template/config.yaml
@@ -361,49 +361,49 @@ products:
     platforms:
       - name: AlmaLinux 8 or Rocky Linux 8
         arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: AlmaLinux 9 or Rocky Linux 9
         arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: RHEL 8 or OL 8
         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: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: RHEL 9
         arch: ppc64le
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: RHEL 8
         arch: ppc64le
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: Debian 12
         arch: x86_64
-        supported versions: [16]
+        supported versions: [16, 17]
       - name: Debian 12
         arch: arm64
-        supported versions: [16]
+        supported versions: [16, 17]
       - name: Debian 11
         arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: Ubuntu 22.04
         arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: Ubuntu 20.04
         arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: SLES 15
         arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: SLES 15
         arch: ppc64le
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: SLES 12
         arch: x86_64
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
       - name: SLES 12
         arch: ppc64le
-        supported versions: [11, 12, 13, 14, 15, 16]
+        supported versions: [11, 12, 13, 14, 15, 16, 17]
   - name: EDB Postgres Extended Server
     platforms:
       - name: AlmaLinux 8 or Rocky Linux 8
diff --git a/product_docs/docs/epas/17/images/download_complete_confirmation.png b/product_docs/docs/epas/17/images/download_complete_confirmation.png
new file mode 100644
index 00000000000..311a2f19d49
--- /dev/null
+++ b/product_docs/docs/epas/17/images/download_complete_confirmation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:53af024b51dfd46c7d6f26d057f6e133bee7d020bf2ce480b2e23c7dd49d81fb
+size 69545
diff --git a/product_docs/docs/epas/17/images/selected_packages_summary_window.png b/product_docs/docs/epas/17/images/selected_packages_summary_window.png
new file mode 100644
index 00000000000..8325bc25697
--- /dev/null
+++ b/product_docs/docs/epas/17/images/selected_packages_summary_window.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:38a61b6f6e238697dab8da790f979ddf77409a495e637e2ee3d11403715311dc
+size 68659
diff --git a/product_docs/docs/epas/17/images/stackBuilder_plus_confirms_the_completed_installation.png b/product_docs/docs/epas/17/images/stackBuilder_plus_confirms_the_completed_installation.png
new file mode 100644
index 00000000000..f7eacf0d2ef
--- /dev/null
+++ b/product_docs/docs/epas/17/images/stackBuilder_plus_confirms_the_completed_installation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:68b4b6d4e811d511ba9406fb0374ea0c1bbcf76947545d75d0d4bfdd42167608
+size 74362
diff --git a/product_docs/docs/epas/17/images/summary_window_displaying_selected_packages.png b/product_docs/docs/epas/17/images/summary_window_displaying_selected_packages.png
new file mode 100644
index 00000000000..459bd0a99ca
--- /dev/null
+++ b/product_docs/docs/epas/17/images/summary_window_displaying_selected_packages.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4823d7dcb6cd69945edf5ce074748e61683539e6d06d5cb91c403f517daa36b7
+size 107084
diff --git a/product_docs/docs/epas/17/images/the_proxy_servers_dialog.png b/product_docs/docs/epas/17/images/the_proxy_servers_dialog.png
new file mode 100755
index 00000000000..3b5c76bd9c9
--- /dev/null
+++ b/product_docs/docs/epas/17/images/the_proxy_servers_dialog.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f26ab5caf958119b8c6843262de4e2d33f6f966aca556dda8f6b11a855f19739
+size 5612
diff --git a/product_docs/docs/epas/17/images/the_stackBuilder_plus_module_selection_window.png b/product_docs/docs/epas/17/images/the_stackBuilder_plus_module_selection_window.png
new file mode 100644
index 00000000000..b0a60a603bc
--- /dev/null
+++ b/product_docs/docs/epas/17/images/the_stackBuilder_plus_module_selection_window.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b082d664e93feae50bc4eda4e88ac7fe815d81783ba0aba177414e70a6c56db1
+size 74214
diff --git a/product_docs/docs/epas/17/images/the_stackBuilder_plus_welcome.png b/product_docs/docs/epas/17/images/the_stackBuilder_plus_welcome.png
new file mode 100644
index 00000000000..15ab6e100bf
--- /dev/null
+++ b/product_docs/docs/epas/17/images/the_stackBuilder_plus_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ba62871fdf8d225a2d03c0d85598e9e119e6901f42f3a74ed7ec6a6b14f4d45
+size 73197
diff --git a/product_docs/docs/epas/17/installing/index.mdx b/product_docs/docs/epas/17/installing/index.mdx
index 01c455b3135..b3beff4ee50 100644
--- a/product_docs/docs/epas/17/installing/index.mdx
+++ b/product_docs/docs/epas/17/installing/index.mdx
@@ -8,9 +8,9 @@ title: Installing EDB Postgres Advanced Server
 # Leaf template: products/edb-postgres-advanced-server/index.njk
 
 redirects:
-  - /epas/16/epas_inst_linux/
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/
-  - /epas/16/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/
+  - /epas/17/epas_inst_linux/
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/
+  - /epas/17/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/
 
 navigation:
   - linux_x86_64
diff --git a/product_docs/docs/epas/17/installing/linux_arm64/epas_debian_12.mdx b/product_docs/docs/epas/17/installing/linux_arm64/epas_debian_12.mdx
index 3f354f89629..030c2bc4985 100644
--- a/product_docs/docs/epas/17/installing/linux_arm64/epas_debian_12.mdx
+++ b/product_docs/docs/epas/17/installing/linux_arm64/epas_debian_12.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on Debian 12 arm64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_deb12_arm
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_deb12_arm
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/arm64/epas_deb12_arm
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_deb12_arm
 ---
 
 ## Prerequisites
@@ -40,7 +40,7 @@ Before you begin the installation process:
 sudo apt-get -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -48,7 +48,7 @@ To install an individual component:
 sudo apt-get -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
@@ -88,7 +88,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_8.mdx
index 394f8baf56c..1a47732ae56 100644
--- a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_8.mdx
+++ b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_8.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on RHEL 8 ppc64le
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel8_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel8_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel8_ppcle
 ---
 
 ## Prerequisites
@@ -60,7 +60,7 @@ Before you begin the installation process:
 sudo dnf -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -68,20 +68,20 @@ To install an individual component:
 sudo dnf -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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/as16`.
+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-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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -118,7 +118,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx
index 0772be02315..e8358086cd3 100644
--- a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx
+++ b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_rhel_9.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on RHEL 9 ppc64le
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel9_ppcle
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel9_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_rhel9_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel9_ppcle
 ---
 
 ## Prerequisites
@@ -60,7 +60,7 @@ Before you begin the installation process:
 sudo dnf -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -68,20 +68,20 @@ To install an individual component:
 sudo dnf -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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/as16`.
+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-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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -118,7 +118,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_12.mdx b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_12.mdx
index 23d1956bd24..af74507dbf8 100644
--- a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_12.mdx
+++ b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_12.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on SLES 12 ppc64le
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles12_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles12_ppcle
 ---
 
 ## Prerequisites
@@ -51,7 +51,7 @@ Before you begin the installation process:
 sudo zypper -n install edb-as<xx>-server
 ```
 
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 16, the package name would be `edb-as16-server`.
+Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 17, the package name would be `edb-as17-server`.
 
 To install an individual component:
 
@@ -59,18 +59,18 @@ To install an individual component:
 sudo zypper -n install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
 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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -107,7 +107,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_15.mdx
index 50705b7cade..e90bea59edd 100644
--- a/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_15.mdx
+++ b/product_docs/docs/epas/17/installing/linux_ppc64le/epas_sles_15.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on SLES 15 ppc64le
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles15_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/epas_sles15_ppcle
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles15_ppcle
 ---
 
 ## Prerequisites
@@ -52,7 +52,7 @@ Before you begin the installation process:
 sudo zypper -n install edb-as<xx>-server
 ```
 
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 16, the package name would be `edb-as16-server`.
+Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 17, the package name would be `edb-as17-server`.
 
 To install an individual component:
 
@@ -60,18 +60,18 @@ To install an individual component:
 sudo zypper -n install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
 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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -108,7 +108,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_ppc64le/index.mdx b/product_docs/docs/epas/17/installing/linux_ppc64le/index.mdx
index 3af19ebfe9a..5e803bb5b33 100644
--- a/product_docs/docs/epas/17/installing/linux_ppc64le/index.mdx
+++ b/product_docs/docs/epas/17/installing/linux_ppc64le/index.mdx
@@ -8,8 +8,8 @@ navTitle: "On Linux ppc64le"
 # Leaf template: products/edb-postgres-advanced-server/ppc64le_index.njk
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/
-  - /epas/16/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#installing-on-ibm-power-ppc64le
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/ibm_power_ppc64le/
+  - /epas/17/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#installing-on-ibm-power-ppc64le
 
 navigation:
   - epas_rhel_9
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_11.mdx
index 913ddf520a3..dea576194db 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_11.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_11.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on Debian 11 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb11_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb11_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb11_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb11_x86
 ---
 
 ## Prerequisites
@@ -40,7 +40,7 @@ Before you begin the installation process:
 sudo apt-get -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -48,7 +48,7 @@ To install an individual component:
 sudo apt-get -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
@@ -88,7 +88,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_12.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_12.mdx
index 146dc09c637..d384c3c2857 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_12.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_debian_12.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on Debian 12 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb12_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb12_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_deb12_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_deb12_x86
 ---
 
 ## Prerequisites
@@ -40,7 +40,7 @@ Before you begin the installation process:
 sudo apt-get -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -48,7 +48,7 @@ To install an individual component:
 sudo apt-get -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
@@ -88,7 +88,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_8.mdx
index 7a2a860940e..1a49cd97c49 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_8.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_8.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on AlmaLinux 8 or Rocky Linux 8 x
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_other_linux8_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux8_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_other_linux8_x86
 ---
 
 ## Prerequisites
@@ -51,7 +51,7 @@ Before you begin the installation process:
 sudo dnf -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -59,20 +59,20 @@ To install an individual component:
 sudo dnf -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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/as16`.
+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-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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -109,7 +109,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_9.mdx
index 52f218177a4..7e601ca3b89 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_9.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_other_linux_9.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on AlmaLinux 9 or Rocky Linux 9 x
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux9_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_other_linux9_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_other_linux9_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_other_linux9_x86
 ---
 
 ## Prerequisites
@@ -51,7 +51,7 @@ Before you begin the installation process:
 sudo dnf -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -59,20 +59,20 @@ To install an individual component:
 sudo dnf -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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/as16`.
+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-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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -109,7 +109,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_8.mdx
index 21464dd1602..4c89a3b2cc4 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_8.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_8.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on RHEL 8 or OL 8 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel8_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel8_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel8_x86
 ---
 
 ## Prerequisites
@@ -58,7 +58,7 @@ Before you begin the installation process:
 sudo dnf -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -66,20 +66,20 @@ To install an individual component:
 sudo dnf -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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/as16`.
+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-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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -116,7 +116,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx
index 030bdaa1332..6fdeac04ca0 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_rhel_9.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on RHEL 9 or OL 9 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel9_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel9_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_rhel9_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_rhel9_x86
 ---
 
 ## Prerequisites
@@ -58,7 +58,7 @@ Before you begin the installation process:
 sudo dnf -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -66,20 +66,20 @@ To install an individual component:
 sudo dnf -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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/as16`.
+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-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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -116,7 +116,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_12.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_12.mdx
index 0003e2f05a1..f5094b76c07 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_12.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_12.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on SLES 12 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles12_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles12_x86
 ---
 
 ## Prerequisites
@@ -51,7 +51,7 @@ Before you begin the installation process:
 sudo zypper -n install edb-as<xx>-server
 ```
 
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 16, the package name would be `edb-as16-server`.
+Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 17, the package name would be `edb-as17-server`.
 
 To install an individual component:
 
@@ -59,18 +59,18 @@ To install an individual component:
 sudo zypper -n install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
 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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -107,7 +107,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_15.mdx
index ac0bc1b0d6c..4fad14fac46 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_15.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_sles_15.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on SLES 15 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles15_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_sles15_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_sles15_x86
 ---
 
 ## Prerequisites
@@ -52,7 +52,7 @@ Before you begin the installation process:
 sudo zypper -n install edb-as<xx>-server
 ```
 
-Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 16, the package name would be `edb-as16-server`.
+Where `<xx>` is the version of the EDB Postgres Advanced server you are installing. For example, if you are installing version 17, the package name would be `edb-as17-server`.
 
 To install an individual component:
 
@@ -60,18 +60,18 @@ To install an individual component:
 sudo zypper -n install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
 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).
+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/as16/bin/edb-as-16-setup initdb
+sudo PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as17/bin/edb-as-17-setup initdb
 
-sudo systemctl start edb-as-16
+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.
@@ -108,7 +108,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
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
index a198834ced3..af7da8b3bfd 100644
--- 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
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on Ubuntu 20.04 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu20_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu20_x86
+  - /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
@@ -40,7 +40,7 @@ Before you begin the installation process:
 sudo apt-get -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -48,7 +48,7 @@ To install an individual component:
 sudo apt-get -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
@@ -88,7 +88,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
diff --git a/product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_22.mdx
index b1fcf9882c3..fc0eaf0a68f 100644
--- a/product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_22.mdx
+++ b/product_docs/docs/epas/17/installing/linux_x86_64/epas_ubuntu_22.mdx
@@ -6,8 +6,8 @@ title: Installing EDB Postgres Advanced Server on Ubuntu 22.04 x86_64
 # the documentation team will update the templates accordingly.
 
 redirects:
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu22_x86
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu22_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/epas_ubuntu22_x86
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86/epas_ubuntu22_x86
 ---
 
 ## Prerequisites
@@ -40,7 +40,7 @@ Before you begin the installation process:
 sudo apt-get -y install edb-as<xx>-server
 ```
 
-Where `<xx>` 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`.
+Where `<xx>` 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:
 
@@ -48,7 +48,7 @@ To install an individual component:
 sudo apt-get -y install <package_name>
 ```
 
-Where `package_name` can be any of the available packages from the [available package list](/epas/16/installing/linux_install_details/rpm_packages/).
+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
 
@@ -88,7 +88,7 @@ Connect to the `hr` database inside psql:
 ```
 \c hr
 __OUTPUT__
-psql (16.0.0, server 16.0.0)
+psql (17.0.0, server 17.0.0)
 You are now connected to database "hr" as user "enterprisedb".
 ```
 
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 bae4f092ad8..84ea3b1dd6e 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
@@ -9,7 +9,7 @@ navTitle: "On Linux x86"
 
 redirects:
   - ../03_using_a_package_manager_to_install_advanced_server
-  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/
+  - /epas/17/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/
 
 navigation:
   - epas_rhel_9
diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/enquote_literal.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/enquote_literal.mdx
new file mode 100644
index 00000000000..a8b7df9d42f
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/enquote_literal.mdx
@@ -0,0 +1,33 @@
+---
+title: "ENQUOTE_LITERAL"
+---
+
+The `ENQUOTE_LITERAL` function wraps single quotes around a string unless the string is already enclosed in single quotes.
+
+Only an even number of single quotes are allowed in the string, excluding the enclosing quotes.
+
+```sql
+ENQUOTE_LITERAL(str VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters
+
+`str`
+
+ The string to be wrapped in single quotes.
+
+## Examples
+
+```sql
+edb=# SELECT sys.DBMS_ASSERT.ENQUOTE_LITERAL('literal without ''''quotes') FROM DUAL;
+      enquote_literal       
+----------------------------
+ 'literal without ''quotes'
+(1 row)
+
+edb=# SELECT dbms_assert.ENQUOTE_LITERAL('''ab''') FROM dual;
+ enquote_literal 
+-----------------
+ 'ab'
+(1 row)
+```
diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/enquote_name.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/enquote_name.mdx
new file mode 100644
index 00000000000..7a90786fb83
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/enquote_name.mdx
@@ -0,0 +1,53 @@
+---
+title: "ENQUOTE_NAME"
+---
+
+The `ENQUOTE_NAME` function wraps quotation marks around a string, unless the input is already enclosed in quotation marks. All quotation marks within the string are appended with an quotation mark.
+
+The following table shows examples of how quotes are handled.
+
+| Input  | `dolower` parameter | Output    |
+| ------ | ------------------- | --------- |
+| ab"c   | TRUE                | "ab""c"   |
+| "abc"  | TRUE                | "abc"     |
+| "a"bc" | TRUE                | "a""bc"   |
+| ABC    | TRUE                | "abc"     |
+| ABC    | FALSE               | "ABC"     |
+| aBc    | TRUE                | "abc"     |
+| aBc    | FALSE               | "aBc"     |
+
+
+```sql
+ENQUOTE_NAME(str VARCHAR2, dolower boolean := TRUE) RETURN VARCHAR2;
+```
+
+## Parameters
+
+`str`
+
+ The string to be wrapped in quotation marks.
+
+`dolower`
+
+ Optional. If TRUE, alphabetic characters in the input string that are not wrapped in quotation marks are converted to lower case. If FALSE, input strings are not converted to lower case.
+
+ Default is TRUE. Input not enclosed in quotes are converted to lower case.
+
+## Examples
+
+```sql
+edb=# SELECT SYS.DBMS_ASSERT.ENQUOTE_NAME('  ""ObjectName  ') FROM DUAL;
+     enquote_name     
+----------------------
+ "  """"objectname  "
+(1 row)
+
+edb=# SELECT 'test' || SYS.DBMS_ASSERT.ENQUOTE_NAME('  "ObjectName"  ') || 'test' FROM dual;
+         ?column?         
+--------------------------
+ test  "ObjectName"  test
+(1 row)
+
+edb=# EXEC DBMS_OUTPUT.put_line(SYS.DBMS_ASSERT.ENQUOTE_NAME('"REMAIN QUOTED and SAME CASE"'));
+"REMAIN QUOTED and SAME CASE"
+```
diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/examples.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/examples.mdx
new file mode 100644
index 00000000000..27a04cf1a35
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/examples.mdx
@@ -0,0 +1,80 @@
+---
+title: "Examples for SQL injection"
+navTitle: "Examples"
+---
+
+The following examples demonstrate some approaches for using `DBMS_ASSERT` to help prevent SQL injections.
+
+```sql
+edb=# CREATE TABLE open_tab_dbassert (
+  code        VARCHAR2(5),
+  description VARCHAR2(50)
+);
+CREATE TABLE
+
+edb=# INSERT INTO open_tab_dbassert VALUES ('ONE', 'Description for ONE');
+INSERT 0 1
+edb=# INSERT INTO open_tab_dbassert VALUES ('TWO', 'Description for TWO');
+INSERT 0 1
+
+edb=# CREATE TABLE secret_tab_dbassert (
+  code        VARCHAR2(5),
+  description VARCHAR2(50)
+);
+CREATE TABLE
+
+edb=# INSERT INTO secret_tab_dbassert VALUES ('CODE1', 'SECRET 1');
+INSERT 0 1
+edb=# INSERT INTO secret_tab_dbassert VALUES ('CODE2', 'SECRET 2');
+INSERT 0 1
+
+edb=# CREATE OR REPLACE PROCEDURE get_open_data_dbassert(p_code IN VARCHAR2) AS
+  l_sql     VARCHAR2(32767);
+  c_cursor  SYS_REFCURSOR;
+  l_buffer  VARCHAR2(32767);
+BEGIN
+  DBMS_OUTPUT.put_line('Raw input format: (' || p_code || ')');
+  l_sql := 'SELECT description FROM open_tab_dbassert WHERE code = ''' || p_code || '''';
+ DBMS_OUTPUT.put_line(l_sql);
+  OPEN c_cursor FOR l_sql;
+  LOOP
+    FETCH c_cursor INTO  l_buffer;
+    EXIT WHEN c_cursor%NOTFOUND;
+    DBMS_OUTPUT.put_line(l_buffer);
+  END LOOP;
+  close c_cursor;
+  l_buffer:=null;
+
+  DBMS_OUTPUT.put_line('Input with DBMS_ASSERT : DBMS_ASSERT.ENQUOTE_LITERAL(' || p_code || ')');
+  l_sql := 'SELECT description FROM open_tab_dbassert WHERE code = ' || sys.DBMS_ASSERT.ENQUOTE_LITERAL(p_code);
+ DBMS_OUTPUT.put_line(l_sql);
+  OPEN c_cursor FOR l_sql;
+  LOOP
+    FETCH c_cursor INTO  l_buffer;
+    EXIT WHEN c_cursor%NOTFOUND;
+    DBMS_OUTPUT.put_line(l_buffer);
+  END LOOP;
+  close c_cursor;
+END;
+CREATE PROCEDURE
+
+--Output
+edb=# EXEC get_open_data_dbassert('ONE'' OR ''1''=''1');
+Raw input format: (ONE' OR '1'='1)
+SELECT description FROM open_tab_dbassert WHERE code = 'ONE' OR '1'='1'
+Description for ONE
+Description for TWO
+Input with DBMS_ASSERT : DBMS_ASSERT.ENQUOTE_LITERAL(ONE' OR '1'='1)
+ERROR:  numeric or value error
+CONTEXT:  edb-spl function get_open_data_dbassert(character varying) line 19 at assignment
+
+edb=# EXEC get_open_data_dbassert('ONE'' UNION SELECT description FROM secret_tab_dbassert WHERE ''1''=''1');
+Raw input format: (ONE' UNION SELECT description FROM secret_tab_dbassert WHERE '1'='1)
+SELECT description FROM open_tab_dbassert WHERE code = 'ONE' UNION SELECT description FROM secret_tab_dbassert WHERE '1'='1'
+SECRET 1
+SECRET 2
+Description for ONE
+Input with DBMS_ASSERT : DBMS_ASSERT.ENQUOTE_LITERAL(ONE' UNION SELECT description FROM secret_tab_dbassert WHERE '1'='1)
+ERROR:  numeric or value error
+CONTEXT:  edb-spl function get_open_data_dbassert(character varying) line 19 at assignment
+```
\ 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/01a_dbms_assert/index.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/index.mdx
new file mode 100644
index 00000000000..2cbb542a6d1
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/index.mdx
@@ -0,0 +1,28 @@
+---
+title: "DBMS_ASSERT"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+navigation:
+- enquote_literal
+- enquote_name
+- noop
+- qualified_sql_name
+- schema_name
+- simple_sql_name
+- sql_object_name
+- examples
+---
+
+The `DBMS_ASSERT` package lets you sanitize and validate user input to help guard against SQL injections in applications. The following table lists the supported functions:
+
+| Function             | Return type     | Description                                           |
+| ---------------------| --------------- | ----------------------------------------------------- |
+| `ENQUOTE_LITERAL`    | `VARCHAR2`      | Wraps a string in single quotes                       |
+| `ENQUOTE_NAME`       | `VARCHAR2`      | Wraps quotation marks around a string                 |
+| `NOOP`               | `anycompatible` | Returns the input value without any checking          |
+| `QUALIFIED_SQL_NAME` | `VARCHAR2`      | Checks if the input string is a qualified SQL name    |
+| `SCHEMA_NAME`        | `VARCHAR2`      | Checks if the input string is an existing schema name |
+| `SIMPLE_SQL_NAME`    | `VARCHAR2`      | Checks if the input string is a simple SQL name       |
+| `SQL_OBJECT_NAME`    | `VARCHAR2`      | Checks if the input string is a qualified SQL identifier of an existing SQL object |
+  
+See [Examples for SQL injection](examples) for some demonstrations of how to use `DBMS_ASSERT`.
\ 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/01a_dbms_assert/noop.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/noop.mdx
new file mode 100644
index 00000000000..1cb685a7cd4
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/noop.mdx
@@ -0,0 +1,32 @@
+---
+title: "NOOP"
+---
+
+The `NOOP` function returns a string without any checking.
+
+```sql
+NOOP(str <anycompatible>) RETURN <anycompatible>;
+```
+
+## Parameters
+
+`str`
+
+ The input string.
+
+## Examples
+
+```sql
+edb=# SELECT sys.DBMS_ASSERT.NOOP('Literal with ''''two single'''' quotes.') FROM DUAL;
+                noop                 
+-------------------------------------
+ Literal with ''two single'' quotes.
+(1 row)
+
+edb=# SELECT sys.DBMS_ASSERT.NOOP('Literal with no quotes.') FROM DUAL;
+          noop           
+-------------------------
+ Literal with no quotes.
+(1 row)
+```
+
diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/qualified_sql_name.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/qualified_sql_name.mdx
new file mode 100644
index 00000000000..f71c29bf425
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/qualified_sql_name.mdx
@@ -0,0 +1,40 @@
+---
+title: "QUALIFIED_SQL_NAME"
+---
+
+The `QUALIFIED_SQL_NAME` function determines whether the input string is a qualified SQL name. 
+
+Use the following grammar to represent a qualified SQL name.
+
+```
+<simple qualified name>  => <simple name> ['.' <simple name>]
+<dblink name>            => <simple qualified name> ['@' <conn string>]
+<conn string>            => <simple name>
+<qualified name>         => <simple qualified name> ['@' <dblink name>]
+```
+
+## Parameters
+
+`str`
+
+ The input string. A quotation mark is allowed within the input string.
+
+## Examples
+
+```sql
+edb=# SELECT SYS.DBMS_ASSERT.QUALIFIED_SQL_NAME('schema_name."object_name"@dblink_name') FROM DUAL;
+          qualified_sql_name           
+---------------------------------------
+ schema_name."object_name"@dblink_name
+(1 row)
+
+
+edb=# SELECT SYS.DBMS_ASSERT.QUALIFIED_sql_name('こんにちは') FROM DUAL;
+ qualified_sql_name 
+--------------------
+ こんにちは
+(1 row)
+
+edb=# SELECT dbms_assert.qualified_sql_name('db1".etc"');
+ERROR:  invalid qualified SQL name
+```
\ 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/01a_dbms_assert/schema_name.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/schema_name.mdx
new file mode 100644
index 00000000000..32f9c8aceb7
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/schema_name.mdx
@@ -0,0 +1,33 @@
+---
+title: "SCHEMA_NAME"
+---
+
+The `SCHEMA_NAME` function determines whether the input string is an existing schema name. An error occurs if the input value is not a valid schema name. 
+
+```sql
+SCHEMA_NAME(str VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters
+
+`str`
+
+ The input string. White space is trimmed from the string unless that white space is contained within quotation marks. Mixed case is allowed. 
+
+The input string is converted to lower case by default. If you want to search for a case-sensitive name, enclose it in quotation marks.
+
+## Examples
+
+```sql
+edb=# SELECT SYS.DBMS_ASSERT.SCHEMA_NAME(current_database() || '."SCHEMA1"') FROM DUAL;
+ schema_name 
+-------------
+ edb."SCHEMA1"
+(1 row)
+
+edb=# SELECT SYS.DBMS_ASSERT.SCHEMA_NAME('"SCHEMA1"') FROM DUAL;
+ schema_name 
+-------------
+ SCHEMA1
+(1 row)
+```
diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/simple_sql_name.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/simple_sql_name.mdx
new file mode 100644
index 00000000000..b7cd0c8d308
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/simple_sql_name.mdx
@@ -0,0 +1,35 @@
+---
+title: "SIMPLE_SQL_NAME"
+---
+
+The `SIMPLE_SQL_NAME` function determines whether the input is a simple SQL name. 
+
+
+```sql
+SIMPLE_SQL_NAME(str VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters
+
+`str`
+
+ The input string. White space is trimmed from the string. Mixed case is allowed. A quotation mark is allowed within the string.
+
+## Examples
+
+```sql
+edb=# SELECT SYS.DBMS_ASSERT.SIMPLE_SQL_NAME('ABCD789$#_zxcvbnm') FROM DUAL;
+  simple_sql_name  
+-------------------
+ ABCD789$#_zxcvbnm
+(1 row)
+
+edb=# SELECT SYS.DBMS_ASSERT.SIMPLE_SQL_NAME('"12 valid name"') FROM DUAL;
+ simple_sql_name 
+-----------------
+ "12 valid name"
+
+edb=# SELECT dbms_assert.simple_sql_name('    sch1.a1   ');
+ERROR:  invalid SQL name
+(1 row)
+```
diff --git a/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/sql_object_name.mdx b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/sql_object_name.mdx
new file mode 100644
index 00000000000..5d8f34027e3
--- /dev/null
+++ b/product_docs/docs/epas/17/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01a_dbms_assert/sql_object_name.mdx
@@ -0,0 +1,74 @@
+---
+title: "SQL_OBJECT_NAME"
+---
+
+The `SQL_OBJECT_NAME` function determines whether an input string is a valid SQL object accessible to the current user. An error is thrown otherwise.
+
+The function first checks the database name, then the schema name, and then other SQL objects in the following order:
+
+1. Table, view, materialized view, index, sequence, foreign table, partition-table, type, object type
+1. Function, procedure, aggregate, routine
+1. Packages
+1. Synonym
+1. Trigger
+1. Queue, queue table
+1. Event trigger
+
+Only objects in the current database can be verified by this function. It validates names to four levels: `dbname.schema_name.object_name.object_member`. The function verifies that an actual database object exists for the first three levels. For the fourth level, `object_member`, only the syntax is verified.
+
+For example, if the input is `table_name.column_name`, the function validates `table_name` by searching through database objects in the current search path. After finding the `table_name`, the function validates the basic syntax of `column_name` and does not check if the column actually exists. Similarly, in the case of `package_name.member_name`, after the function finds the package name in the search path, it validates only the basic syntax of `member_name`.
+
+```sql
+SQL_OBJECT_NAME(str VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters
+
+`str`
+
+ The input string.
+
+## Examples
+
+```sql
+edb=# CREATE TABLE t1_dbassert (a INT);
+CREATE TABLE
+edb=# SELECT SYS.DBMS_ASSERT.SQL_OBJECT_NAME('t1_dbassert') FROM DUAL;
+ sql_object_name 
+-----------------
+ t1_dbassert
+(1 row)
+
+-- The column_name is only syntax verified
+edb=# SELECT dbms_assert.sql_object_name('t1_dbassert.col1');
+ sql_object_name  
+------------------
+ t1_dbassert.col1
+(1 row)
+
+edb=# SELECT dbms_assert.sql_object_name('t1_dbassert.1col');
+ERROR:  invalid object name
+
+CREATE OR REPLACE package pkg_dbassert AS
+    i_dbassert NUMBER;
+    PROCEDURE proc_dbassert;
+    FUNCTION func_dbassert(i INT) RETURN NUMBER;
+    t1_table_dbassert t1_dbassert;
+    CURSOR cur(c1 t1_dbassert.a%TYPE) IS SELECT a FROM t1_dbassert;
+    TYPE trec_dbassert IS RECORD ( a INTEGER, b INTEGER );
+    r trec_dbassert := NULL;
+END;
+
+edb=# SELECT DBMS_ASSERT.SQL_OBJECT_NAME('pkg_dbassert.i_dbassert') FROM DUAL;
+     sql_object_name     
+-------------------------
+ pkg_dbassert.i_dbassert
+(1 row)
+
+edb=# SELECT DBMS_ASSERT.SQL_OBJECT_NAME('public.pkg_dbassert.i_dbassert') FROM DUAL;
+        sql_object_name         
+--------------------------------
+ public.pkg_dbassert.i_dbassert
+(1 row)
+
+```